Friday, 2017-06-02

*** tonanhngo has quit IRC00:03
*** tonanhngo has joined #openstack-swift00:04
*** tonanhngo has quit IRC00:08
*** gyee has quit IRC00:30
*** alenavolk has joined #openstack-swift00:30
*** jamielennox is now known as jamielennox|away00:44
*** tovin07_ has joined #openstack-swift00:48
*** neonpastor has quit IRC00:50
openstackgerritClay Gerrard proposed openstack/swift master: Prefer auth_uri in functests configs  https://review.openstack.org/46998400:51
*** alenavolk has quit IRC00:58
*** zhengyin has joined #openstack-swift01:00
*** klamath has quit IRC01:09
*** klamath has joined #openstack-swift01:10
*** klamath has quit IRC01:28
*** klamath has joined #openstack-swift01:29
kota_good morning01:49
*** jamielennox|away is now known as jamielennox02:00
*** alenavolk has joined #openstack-swift02:12
*** alenavolk has quit IRC02:14
*** alenavolk has joined #openstack-swift02:16
*** alenavolk has joined #openstack-swift02:17
*** links has joined #openstack-swift02:22
*** alenavolk has quit IRC02:28
*** alenavolk has joined #openstack-swift02:29
*** alenavolk has quit IRC02:29
*** alenavolk has joined #openstack-swift02:29
*** alenavolk has joined #openstack-swift02:30
*** alenavolk has quit IRC02:30
*** klamath has quit IRC02:44
*** jamielennox is now known as jamielennox|away03:30
*** psachin has joined #openstack-swift03:45
*** oshritf has joined #openstack-swift04:02
*** oshritf has quit IRC04:07
openstackgerritLingxian Kong proposed openstack/swift master: [WIP] Write-affinity aware object deletion  https://review.openstack.org/47015804:36
*** chsc has joined #openstack-swift04:36
*** chsc has joined #openstack-swift04:36
*** jaosorior has joined #openstack-swift04:41
*** chsc has quit IRC04:42
notmynametdasilva: clayg: ^^ FYI on that patch05:03
*** tovin07_ has quit IRC05:11
*** zhengyin has quit IRC05:12
*** zhengyin has joined #openstack-swift05:13
*** rcernin has joined #openstack-swift05:26
*** jeffl has joined #openstack-swift05:26
*** zhengyin has quit IRC05:33
*** zhengyin has joined #openstack-swift05:34
*** ChubYann has quit IRC05:49
*** cshastri has joined #openstack-swift05:50
*** sanchitmalhotra has quit IRC05:59
*** kei_yama has quit IRC06:16
*** skudlik has joined #openstack-swift06:26
*** kei_yama has joined #openstack-swift06:30
*** aselius has quit IRC06:32
*** hseipp has joined #openstack-swift06:42
jeffl\quit06:51
*** jeffl has quit IRC06:51
*** klrmn has quit IRC07:02
*** tesseract has joined #openstack-swift07:04
*** aselius has joined #openstack-swift07:34
*** sanchitmalhotra has joined #openstack-swift07:41
*** hseipp has quit IRC08:13
*** cbartz has joined #openstack-swift08:15
*** jamielennox|away is now known as jamielennox08:21
*** joeljwright has joined #openstack-swift08:22
*** ChanServ sets mode: +v joeljwright08:22
acolesmattoliverau: hi! so sounds like the change at https://review.openstack.org/#/c/450491/13/swift/container/sharder.py@a471 is wrong - we *should* be applying the current meta timestamp to the new pivot range object because we are copying the bytes and object count across to it?08:46
patchbotpatch 450491 - swift - fixup! Add container sharding to Swift containers08:46
*** jamielennox is now known as jamielennox|away08:49
*** oshritf has joined #openstack-swift08:54
*** oshritf has quit IRC09:03
*** oshritf has joined #openstack-swift09:06
*** oshritf has quit IRC09:16
mattoliverauUmm, no shouldn't we be setting a new timestamp because we are grabbing the latest versions of the stats. Tho I agree maybe we should be smarter so we don't always have to send an update09:21
*** bikmak has joined #openstack-swift09:23
*** oshritf has joined #openstack-swift09:25
*** hseipp has joined #openstack-swift09:41
*** aselius has quit IRC09:44
acolesmattoliverau: ok thanks, so looks like that patch is good to squash09:46
*** kei_yama has quit IRC09:49
openstackgerritMerged openstack/swift master: Remove threads_per_disk from object-server.conf manpages  https://review.openstack.org/47001309:53
*** jaosorior is now known as jaosorior_lunch10:01
*** silor has joined #openstack-swift10:04
*** oshritf has quit IRC10:10
*** mat128 has joined #openstack-swift10:45
*** mingyu has joined #openstack-swift10:46
openstackgerritChristopher Bartz proposed openstack/swift master: Exclude containers for account quota  https://review.openstack.org/41423210:48
*** mingyu has quit IRC10:57
*** mingyu_ has joined #openstack-swift10:58
*** mingyu_ has quit IRC11:03
*** mingyu_ has joined #openstack-swift11:08
*** zhengyin has quit IRC11:14
*** mingyu_ has quit IRC11:25
*** Dw_Sn has joined #openstack-swift12:00
Dw_SnHello, I have a n00b question, I want to make my buckets private and generate a signed URL for the user with expire date "QSA / Query String Authentication", I am exposing S3 API and using keystone for auth. what I need to look for ?12:01
*** catintheroof has joined #openstack-swift12:08
Dw_Snis tempurl the answer ? and would it work with no issues along side keystone ?12:16
acolesDw_Sn: sounds like tempurl is what you are looking for, it should work fine alongside keystone auth, make sure tempurl middleware is before (to left of) keystoneauth in the proxy server pipeline conf as per the sample configs12:40
cbartzDw_Sn: tempurl  should work along side keystone. Make sure to set delay_auth_decision = true in the proxy-server.conf . See here https://docs.openstack.org/developer/swift/api/temporary_url_middleware.html  and here https://docs.openstack.org/developer/swift/overview_auth.html#configuring-swift-to-use-keystone12:41
*** jaosorior_lunch is now known as jaosorior13:03
*** mdrabe has joined #openstack-swift13:10
tdasilvagood morning13:12
*** lucasxu has joined #openstack-swift13:20
*** Dinesh_Bhor has quit IRC13:24
*** psachin has quit IRC13:26
*** links has quit IRC13:35
acolestdasilva: o/13:36
tdasilvaacoles: hello! 0/13:36
Dw_Snthanks guys :)13:46
*** skudlik has quit IRC13:49
*** MVenesio has joined #openstack-swift13:51
Dw_Snone final question, in tempurl sig, the key value is the Secret from EC2 ?13:53
*** klamath has joined #openstack-swift14:01
*** klamath has joined #openstack-swift14:01
Dw_Snnevermind found it :) I need to generate a new key :)14:07
*** mingyu has joined #openstack-swift14:14
*** oshritf has joined #openstack-swift14:19
Dw_SnI am sorry again guys, I got a bit lost, I added a key to X-Container-Meta-Temp-URL-Key , do I need to set a full acocunt or cluster key using swift post -m "Temp-URL-Key:MYKEY" ?14:20
*** mingyu has quit IRC14:34
*** lucasxu has quit IRC14:34
*** lucasxu has joined #openstack-swift14:36
*** oshritf has quit IRC14:41
Dw_SnI added the Temp-URL-Key and still getting Username/Password Authentication failed..14:44
*** catintheroof has quit IRC14:45
acolesDw_Sn: it shouldn't be necessary to have an account temp-url-key as well as container14:49
Dw_Snacoles: I am following the links sent and now I have only Temp-URL-Key but getting auth failed14:49
Dw_SnI can see Meta Temp-Url-Key: XXXXXXXXXXXXXXX when I do swift stat14:50
acolesDw_Sn: to confirm container key is set, 'swift stat <container name>' will show the temp url key14:50
acolesDw_Sn: ok you got it :)14:50
Dw_Snacoles: mmm okay I will add it to the container only and see14:52
Dw_Snacoles: maybe I need to have it on both ?14:53
Dw_Snacoles: so I set Temp-URL-Key and container level one " same key" works perfectly now :)14:56
*** cshastri has quit IRC14:58
*** ^andrea^ has joined #openstack-swift15:02
Dw_Snthanks acoles cbartz15:05
cbartzyw15:05
*** rcernin has quit IRC15:05
Dw_Snone final question :) the temp_url_sig and other one, can't be modified to look like amazon AWS s3 one :) ?15:07
*** bikmak has quit IRC15:10
*** klrmn has joined #openstack-swift15:11
acolesDw_Sn: glad it worked, but I don't think you should need both account and container level keys set to access an object in the same container as the container key is set15:14
acolesDw_Sn: re s3, no idea sorry15:14
timburkeDw_Sn: swift3 supports s3-style pre-signed requests15:17
*** gyee has joined #openstack-swift15:27
*** lucasxu has quit IRC15:38
openstackgerritClay Gerrard proposed openstack/swift master: Prefer auth_uri in functests configs  https://review.openstack.org/46998415:45
*** klamath has quit IRC15:45
^andrea^can I install swift, (on CentOS 7) without installing the whole openstack environment?15:56
^andrea^Hi (first of all) :-D15:56
*** cbartz has left #openstack-swift15:58
etiennemeHi you probably want keystone too for the auth :)15:58
^andrea^OK, so I can use only the bits I need from openstack, without installing EVERYTHING...15:59
^andrea^I'll investigate further, thanks16:00
*** tesseract has quit IRC16:00
etiennemeYep16:00
*** aselius has joined #openstack-swift16:01
*** eckesicle has joined #openstack-swift16:02
Dw_Sntimburke: sorry, in which sense ? using same values as S3 ?16:02
jrichli^andrea^ : You can setup swift standalone.  And if you only want to setup a swift cluster for testing, you can use https://github.com/swiftstack/vagrant-swift-all-in-one16:02
Dw_Snacoles: don't know, I tired to have either one of them, didn't work at all :/16:02
Dw_Sntimburke: file.pdf?AWSAccessKeyId=XXXXXXXXXXXXXX&Expires=1523458993&Signature=XXXXXXXXXXXXXXXXX what will be AWSAccessKeyID here from swift ?16:04
clarkbclayg: your comments yesterday about how logn it takes to vagrant up a devstack got me looking at the swift functional job. And related to ^andrea^'s question above I thinik taht test job runs all of the default devstack services when ti really only needs keystone and swift. So we might be able to trim that down a bit at least for your use case16:05
acoles^andrea^: you can use swift standalone and many people do, with either keystone or another auth service. Along with jrichli 's suggestion there is a 'swift-all-in-one' guide (for single node experimentation) https://docs.openstack.org/developer/swift/development_saio.html16:05
*** lisek has joined #openstack-swift16:08
lisekHello. Does anybody know why object replicator  doesn't use hashes.pkl for handoff partitions?16:08
*** klrmn has quit IRC16:09
^andrea^thank you all, that should get me started! ;-)16:09
notmynamegood morning16:12
^andrea^and, since I'm here, let me say what I'm trying to achieve and if it makes sense16:12
^andrea^basically I/we supports lots of products/sites for a company16:13
^andrea^and every site has its own single NFS VM16:13
^andrea^so I want to get rid of all the single NFS servers, and replace it with something like swift/ceph/glusterfs...16:13
^andrea^*replace them16:14
notmyname^andrea^: nice16:14
^andrea^object storage seems the way to go, which would rule out glusterfs16:14
notmyname^andrea^: your biggest challenge will be to get the existing users to switch to use an object storage API instead of a filesystem interface16:15
^andrea^ceph seems good too, but there doesn't seem to be any Windows client...16:15
^andrea^notmyname: good point16:16
*** pcaruana has quit IRC16:16
^andrea^I assume glusterfs would be better with that...16:17
*** Dw_Sn has quit IRC16:17
notmynameI think object storage is an obviously better way to manage a bunch of storage (especially when compared to a bunch of NFS servers). you get better scalability, lower cost, higher throughput. all good things16:18
^andrea^but the applications/sites will need to be changed "more"...16:19
notmynamebut I'd be crazy not to acknowledging the realities of how people are using the storage16:19
^andrea^yep16:19
notmynameso here's my high-level summary of your options16:19
notmyname(1) swift. really really great object storage. very stable and mature. does object storage exceptionally well and has a ton of great features. it's object storage only, but there are a few ways of getting a filesystem interface to it (including one proprietary that my employer is making)16:20
notmyname(2) gluster. distributed filesystem. pretty good if you just need a filesystem for your data (of the options I'm listing, I'm least familiar with gluster)16:21
*** chsc has joined #openstack-swift16:21
*** chsc has joined #openstack-swift16:21
^andrea^initially I've also asked the infrastructure guys (I'm the linux guy) for an NFS share coming directly from the storage, but we don't have a NAS header for that... (this was my option 0)16:22
notmyname(3) ceph. another good object storage system, although it was built to solve a different problem than swift. ceph is most commonly used as a block-storage provider, and they've recently made their filesystem features "production ready".16:22
notmynameone thing to note swift ceph is that the data in object, block, and file interfaces is *not* shared (ie you can't store as object and read as filesystem)16:23
notmyname(4) various proprietary object storage systems. don't do this ;-). they're expensive and all have copied both the swift and S3 API16:23
^andrea^how about Windows compatibility?16:25
^andrea^let's say the windows guys could use this storage for a 2TB samba share...16:25
^andrea^ceph says they don't have a Windows client16:25
^andrea^is Swift better at that?16:25
notmynamewindows compat as in running on a windows server or as in the client?16:26
notmynameall of these options are built to run on linux, but the clients that are making the API calls can live anywhere16:26
^andrea^like maybe having a Windows VM using this HA storage cluster16:26
notmynamethere are both open source and proprietary clients on all platforms16:27
^andrea^"mounting" it somehow, and offering as Windows shares to other systems...16:27
^andrea^OK16:27
^andrea^I took enough of your time16:27
notmynameto completely unfairly trivialize the work needed to have a windows client, all it needs to do is make HTTP requests to the storage system16:27
^andrea^thank you, you gave me a very good overview, now I only need to go and study it all :-D16:28
notmynamebut if you're specifically looking for samba clients, if the storage system supports the SMB protocol, then "any" windows SMB client (ie windows itself) would work, right?16:28
clarkbclayg: left comment on that change, I think there is a second place you need to deal with cafile (possibly can be consolidated with the current one?)16:28
notmyname^andrea^: please feel free to stay around and ask questions :-)16:28
claygclarkb: maybe16:28
*** hseipp has quit IRC16:29
*** mdrabe has quit IRC16:30
clayglisek: RE: hashes.pkl on handoffs -> http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-06-02.log.html#t2017-06-02T16:24:5316:30
*** jaosorior has quit IRC16:30
^andrea^that's OK, forget about windows for now, I'm over complicating it... :-)16:31
^andrea^but my primary concern is replacing the NFS single point of failure/unrebootable monsters!16:32
notmyname^andrea^: yep. a noble goal :-)16:32
notmyname^andrea^: what kind of data is on the NFS mounts? is it like home directories? or is it more like shared storage? or is the data even shared between users?16:33
claygthose tracebacks are still coming from swiftclient - i looked at the swift_test_client.Connection and it uses httplib.HTTP[s]Connection's directly... but now I'm seeing it still uses swiftclient to talk to auth - so you're right16:33
claygclarkb: I'm not really *helping* you here you know?16:34
openstackgerritClay Gerrard proposed openstack/swift master: Prefer auth_uri in functests configs  https://review.openstack.org/46998416:41
*** mdrabe has joined #openstack-swift16:44
*** silor1 has joined #openstack-swift16:44
*** silor has quit IRC16:46
*** silor1 is now known as silor16:46
*** mingyu has joined #openstack-swift16:50
^andrea^notmyname: generally they are for shared storage amongst application servers16:52
^andrea^but they could be used for anything really...16:52
^andrea^thanks again for your time16:54
*** mingyu has quit IRC16:54
*** lucasxu has joined #openstack-swift17:00
*** klrmn has joined #openstack-swift17:04
*** joeljwright has quit IRC17:15
notmynameweird (linux) container question: I set up an lxd container, install some stuff (ie swift), shutdown the contaienr, snapshot it, start a second container from the snapshot, and the 2nd does *not* have .pyc files and the version of swift that's installed is reported differently17:19
clarkbclayg: progress! http://logs.openstack.org/74/372374/29/check/gate-swift-dsvm-functional-ubuntu-xenial-nv/f7fc35b/ it ran tests and some of them passed, I think there is another place where the cert needs to be passed though. ile "test/functional/__init__.py", line 1005, in get_url_token17:31
*** mingyu has joined #openstack-swift17:35
*** mingyu has quit IRC17:40
claygyeah that's quite a few more failures than I was seeing locally when I was testing directly w/o the venv17:54
claygclarkb: if I split up the auth_uri config fix form the cacert plumbing - can you add another depends-on to the super test everything change thingy?17:55
clarkbclayg: yup17:56
clarkbclayg: I'm also working on making your functional job run a bit quicker but not running the rest of the cloud (which should make your local reproductions simpler)17:56
notmynamecool17:57
*** geaaru has joined #openstack-swift18:04
notmynametimburke: for https://bugs.launchpad.net/bugs/1695273 sounds like it should be checking that the first element is in swift.valid_api_version18:06
openstackLaunchpad bug 1695273 in OpenStack Object Storage (swift) "Subrequests from ratelimit for /auth/v1.0 considered as proxy-server errors" [Undecided,New]18:06
*** vint_bra has joined #openstack-swift18:12
timburkenotmyname: i'd need to look at where we recommend placement wrt cname_lookup and domain_remap before feeling comfortable with that change18:18
timburke...aaaand we don't. make recommendations, that is. :-/18:20
claygclarkb: I feel like I already have my local config only setup swift & keystone (and tempest I guess) - it's not that quick18:32
*** catintheroof has joined #openstack-swift18:38
*** mingyu has joined #openstack-swift18:41
*** lucasxu has quit IRC18:52
*** catintheroof has quit IRC19:02
*** lucasxu has joined #openstack-swift19:04
clarkbhrm I would expect it to be much quicker if just those services19:04
*** klrmn has quit IRC19:08
*** klrmn has joined #openstack-swift19:08
*** gyee has quit IRC19:14
*** gyee has joined #openstack-swift19:17
claygyeah - idk, maybe I keep my laptop busy doing other things - the game seems to build nodes in ~20mins19:18
clayg*gate19:19
*** mingyu has quit IRC19:19
clarkbya but that 20 minutes is all the services too. ANyways think I sorted out the problem with my initial attempt at trimming it down for the functional tests. Now to see if the run19:19
*** mingyu has joined #openstack-swift19:20
*** eckesicle has quit IRC19:21
*** ChubYann has joined #openstack-swift19:43
*** mingyu has quit IRC19:52
*** mingyu has joined #openstack-swift19:53
*** wasmum has joined #openstack-swift19:55
*** mingyu has quit IRC19:57
clarkbclayg: ok https://review.openstack.org/470383 and https://review.openstack.org/470421 should result in what we got at http://logs.openstack.org/83/470383/2/check/gate-swift-dsvm-functional-ubuntu-xenial-nv/4edd279/console.html (10 minute devstack time)20:00
patchbotpatch 470383 - openstack-infra/devstack-gate - List swift and keystone in feature.yaml20:00
patchbotpatch 470421 - openstack-infra/project-config - Only run swift and keystone in swift func jobs20:00
clarkbnotmyname: ^ you maybe interested in those cahngse just to make sure I don't berak anything based on assuming only keystone and swift are necessary there20:01
*** wasmum has quit IRC20:03
*** silor has quit IRC20:11
*** rcernin has joined #openstack-swift20:12
openstackgerritThiago da Silva proposed openstack/swift master: Return 404 on a GET if tombstone is newer  https://review.openstack.org/37115020:13
*** wasmum has joined #openstack-swift20:14
*** silor has joined #openstack-swift20:18
openstackgerritClay Gerrard proposed openstack/swift master: Prefer auth_uri in functests configs  https://review.openstack.org/46998420:20
openstackgerritClay Gerrard proposed openstack/swift master: Add support for cacert plumbing via cafile in the test.conf  https://review.openstack.org/47042720:20
openstackgerritClay Gerrard proposed openstack/swift master: Prefer auth_uri in functests configs  https://review.openstack.org/46998420:23
openstackgerritClay Gerrard proposed openstack/swift master: Add support for cacert plumbing via cafile in the test.conf  https://review.openstack.org/47042720:24
notmynameclarkb: oh I'm interested :-)20:28
notmynamebeen following your conversations with clayg20:28
clarkbclayg: gerrit says 470427 is on top of patchset 6 of 469984 not patchset 7 (I think you can just hit the reabse button in gerrit to fix)20:30
claygi only updated the commit message - does it have to be "fixed" ?20:31
clayg... i mean I'll hit the button - i love buttons20:31
openstackgerritClay Gerrard proposed openstack/swift master: Add support for cacert plumbing via cafile in the test.conf  https://review.openstack.org/47042720:32
clarkbgerrit wo't let you merge if you dep on an old patchset20:32
claygBOOM20:32
clarkbbceause only the current patchset can merge in gerrit20:32
claygoh, ok - guess that'd be a bummer if it had a +A on it then...20:32
*** lucasxu has quit IRC20:45
claygclarkb: i keep loosing the change with all the depends - will you let me know when it fails?  I'll try to classify the ~20 failures and see if which thing to fix next gets us the biggest bang for our buck20:46
*** lucasxu has joined #openstack-swift20:47
clarkbclayg: can do, there is a test backlog so it hasn't even started the functest job yet20:47
*** lucasxu has quit IRC20:48
*** lucasxu has joined #openstack-swift20:48
*** lucasxu has quit IRC20:49
claygtdasilva: timburke: jrichli: you folks are all generally nicer/more-helpful than I am and I'm kinda petered out - I know at somepoint clarkb is going to need us to take on lp bug #1667833 - can I guilt anyone else into stealing time from other stuff to work on swift SSL functests in the gate?20:49
openstackLaunchpad bug 1667833 in OpenStack Object Storage (swift) "func tests must not assert accept-ranges on 304" [Undecided,New] https://launchpad.net/bugs/166783320:49
*** mat128 has quit IRC21:10
openstackgerritPavel Kvasnička proposed openstack/swift master: WIP: Objects are deleted from additional handoffs  https://review.openstack.org/47044021:12
claygPavelK!!!!  you're... not in here....21:12
claygHow you gunna be *working on swift* and your not online.  Also this can *not* be normal hours for you?21:13
mattoliverauPavelK is the Phantom of the Swift channel21:27
*** geaaru has quit IRC21:27
clarkbclayg: http://logs.openstack.org/74/372374/30/check/gate-swift-dsvm-functional-ubuntu-xenial-nv/a811a96/21:32
clarkbFailed: 2021:32
claygnice!21:32
clarkbhttp://logs.openstack.org/74/372374/30/check/gate-swift-dsvm-functional-ubuntu-xenial-nv/a811a96/console.html#_2017-06-02_21_26_00_776751 seems like maybe apache doesn't likethe inputs?21:37
*** MVenesio has quit IRC21:39
*** mdrabe has quit IRC21:47
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873622:09
*** zacksh_ has joined #openstack-swift22:31
*** klamath has joined #openstack-swift22:33
*** sgundur| has joined #openstack-swift22:35
*** tonanhngo has joined #openstack-swift22:38
*** rcernin has quit IRC22:39
*** ejat is now known as fenris22:39
*** fenris is now known as ejat22:39
*** sgundur has quit IRC22:40
*** rickflare has quit IRC22:40
*** rickflare2 has joined #openstack-swift22:40
*** zacksh has quit IRC22:40
*** portante has quit IRC22:42
*** mtreinish has quit IRC22:42
*** portante has joined #openstack-swift22:44
*** mvk has quit IRC22:47
*** mtreinish has joined #openstack-swift22:47
*** klamath has quit IRC22:49
*** mingyu has joined #openstack-swift22:54
*** mingyu has quit IRC22:57
*** mvk has joined #openstack-swift22:59
*** ianychoi has quit IRC22:59
*** ianychoi has joined #openstack-swift23:01
claygumm... so my /opt/stack/logs/s-*.log I think is *not* the place to go see logs on devstack23:10
clarkbclayg: correct, with everything running under systemd now the logs go to journald23:11
clarkbclayg: you can get them via journalctl -u devstack@s-proxy for example23:12
claygis there a journalctl list-all-units?23:12
clarkbor journalctl -u 'devstack@*' for all the services23:12
clarkbclayg: there is with systemctl23:12
clarkbsystemctl list-units23:12
portanteclayg: so swift has stopped logging to syslog when run under systemd?23:13
clarkbportante: sort of, if syslog is installed and enabled as a service most distros automatically have journald pipe into it23:14
*** zacksh_ is now known as zacksh23:14
clarkband I think swift may directly syslog? beacuse it doesn't oslo.logging23:14
portanteclarkb: it uses python logging, too, iirc23:15
portanteand that is configured to send to syslog23:15
claygok, i guess I didn't know/understand what the -u was about - `journalctl devstack@s-*` was my first guess :\23:15
portanteso who ever is listening on /dev/log (or the like) will get log messages23:15
clarkbclayg: the -u restricts the journalctl output to the listed unit(s) which also accepts a globbing string23:16
clarkbfwiw the logs devstack collects definitely end up in journald Jun 02 21:15:39.033955 ubuntu-xenial-citycloud-la1-9113089 systemd[1]: Started Devstack devstack@s-object.service.23:18
clarkband should also end up in syslog if rsyslog is installed and enabled on ubuntu and rhel iirc23:18
portanteis journald listening to /dev/log?23:19
clarkbI don't know.23:20
portanteso on RHEL journald listens to /dev/log, and handles all syslog messages incorporating them into the journald23:21
portantethen rsyslog uses the imjournal module to pull them out of the journald into traditional /var/log files23:21
portantenot sure how ubuntu configures that23:22
portantefedora uses to do that, but now has dropped rsyslog by default23:22
clayg`journalctl -u devstack@s-* -f` is my new fav23:24
*** vint_bra has quit IRC23:45
*** chsc has quit IRC23:51

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!