Wednesday, 2019-04-17

*** dangtrinhnt has joined #openstack-tc00:11
*** jamesmcarthur has joined #openstack-tc00:15
*** jamesmcarthur has quit IRC00:31
*** jamesmcarthur has joined #openstack-tc00:31
*** jamesmcarthur has quit IRC00:35
*** diablo_rojo has quit IRC00:38
*** mriedem has quit IRC00:38
*** diablo_rojo has joined #openstack-tc00:43
*** ricolin has joined #openstack-tc00:56
ricolino/00:57
fungiand now it's office hour01:00
gmanno/01:00
diablo_rojoo/01:09
*** whoami-rajat has joined #openstack-tc01:31
fungisince there's not much else going on, worth mentioning i put together a draft list of project moves/renames for friday based on the rules jroll enumerated: http://paste.openstack.org/show/749402/01:35
fungithe opendev infra team, after great bikeshedding, decided that unofficial projects which don't request their own namespaces are moving to a namespace called "x"01:36
fungialso, if there are any official teams asking to add deliverables in openstack, we should try to get their pending governance changes flushed so they don't get renamed out of the openstack namespace on friday01:38
gmannfungi: it will be 'x' or 'unknown' ? as mentioned in https://governance.openstack.org/tc/resolutions/20190322-namespace-unofficial-projects.html01:41
fungiit will be x. the openstack project doesn't actually have jurisdiction to decide what's happening to non-openstack projects other than to declare they're not able to share the openstack namespace01:43
fungiso "unknown" was a placeholder01:43
fungias well as maybe a suggestion01:43
fungithe opendev infra team ended up wanting to go with something shorter and perhaps less objectionable01:44
gmannk01:45
clarkbya I wanted to go with something that would avoid implying anything01:50
clarkb'unknowm' could be seen as a negtive01:51
fungias opposed to "x" which is how you mark buried treasure on a map ;)01:51
gmanni am just concern about that resolution. nothing else :)01:52
clarkbfungi: makes the spot01:53
clarkber marks01:53
fungithe resolution is fine. any parts which were overreaching can just be considered suggestions01:53
gmannthere are lot of x/*. it might be good to put that list on ML if anyone care about their repo/project01:54
clarkbI sent the list out earlier today01:54
fungiclarkb linked it from the updates he just sent01:54
gmannthanks01:54
fungiit's a bit long to embed directly in an ml post (825 entries)01:54
gmannfor example this one might be needed under openstack somewhere - openstack/upstream-institute-virtual-environment -> x/upstream-institute-virtual-environment01:55
fungiyep, that draft list was intended to solicit feedback01:57
*** Sundar has quit IRC01:58
*** diablo_rojo has quit IRC02:05
gmann'gerrit-dash-creator' was not under infra ?02:06
*** mriedem has joined #openstack-tc02:11
fungii think that's something sdague wrote years ago, wasn't an official infra deliverable02:23
gmannyeah, i  just remember it because recently i fixed +A thing there :)02:25
*** lbragstad has quit IRC02:30
*** diablo_rojo has joined #openstack-tc02:46
*** dangtrinhnt has quit IRC02:59
*** dangtrinhnt has joined #openstack-tc02:59
*** diablo_rojo has quit IRC03:44
*** diablo_rojo has joined #openstack-tc03:44
*** mriedem has quit IRC04:08
*** david-lyle has joined #openstack-tc04:13
*** dklyle has quit IRC04:16
*** e0ne has joined #openstack-tc04:35
*** e0ne has quit IRC04:42
*** e0ne has joined #openstack-tc04:44
*** sapd1 has quit IRC04:50
*** zhurong has quit IRC05:00
*** zhurong has joined #openstack-tc05:07
*** e0ne has quit IRC05:16
*** e0ne has joined #openstack-tc05:40
*** e0ne has quit IRC05:59
*** diablo_rojo has quit IRC06:45
*** tosky has joined #openstack-tc07:29
*** dtantsur|afk is now known as dtantsur07:33
*** e0ne has joined #openstack-tc07:51
*** jpich has joined #openstack-tc08:01
*** e0ne has quit IRC08:38
*** e0ne has joined #openstack-tc08:42
*** e0ne has quit IRC08:43
*** e0ne has joined #openstack-tc08:43
openstackgerritIldiko Vancsa proposed openstack/governance master: Add Upstream Institute training image repo under Docs  https://review.openstack.org/65336008:58
*** e0ne has quit IRC08:58
*** e0ne has joined #openstack-tc08:59
*** e0ne has quit IRC09:02
asettleMorning o/09:09
*** e0ne has joined #openstack-tc09:09
*** zhipeng has joined #openstack-tc09:10
*** e0ne has quit IRC09:37
*** e0ne has joined #openstack-tc09:40
*** e0ne has quit IRC09:46
*** e0ne has joined #openstack-tc09:53
*** e0ne has quit IRC10:27
*** e0ne has joined #openstack-tc10:31
*** e0ne has quit IRC12:00
*** dtantsur is now known as dtantsur|brb12:07
*** e0ne has joined #openstack-tc12:10
openstackgerritAlexandra Settle proposed openstack/governance master: Add PDF doc generation for project docs goal for Train  https://review.openstack.org/64771212:12
*** zhurong has quit IRC12:20
*** e0ne has quit IRC12:34
*** ijolliffe has joined #openstack-tc12:40
*** lbragstad has joined #openstack-tc12:56
*** mriedem has joined #openstack-tc12:57
*** e0ne has joined #openstack-tc12:58
*** dtantsur|brb is now known as dtantsur13:07
*** e0ne has quit IRC13:30
TheJuliaGood mroning13:50
TheJuliaI'm looking through my email and curious if there is a known location for the joint leadership meeting on the 28th13:50
smcginnisHmm, not listed on https://wiki.openstack.org/wiki/Governance/Foundation/28April2019BoardMeeting13:52
TheJuliaYeah :\13:52
smcginnisI would assume it will be in one of the rooms at the conference center, but maybe ttx or one of the other foundation folks know specifics.13:54
ttxAsking around13:59
jrolltc-members: per fungi's message last night, this is the only change which appears to make a deliverable official, we should get that through today. docs ptl is +1 on it: https://review.openstack.org/#/c/653360/14:06
jrollthis would also be nice to get done but the dependencies aren't ready yet: https://review.openstack.org/#/c/649071/14:07
fungifor any we can't get in but want to keep in openstack, we can put them into the ethercalc with a "rename" of foo/openstack to foo/openstack14:11
fungilike, for example, if we are unable to get the governance approvals fast-tracked14:12
fungijust list jroll as the contact for those14:12
jrolllooking again, networking-l2gw-tempest-plugin seems like the only miss (should be in projects.yaml). upstream-institute-virtual-environment has a governance change up to make it official, and the rest appear that they should remain independent (in x/ or otherwise)14:13
fungilonger term, we probably should track things which we want to authorize for inclusion in the openstack namespace, because the opendev team is going to be looking to us for an okay any time someone wants to add or move a project into that namespace in the future too14:13
fungisomeone suggested that moving the openstack/openstack superrepo to x/openstack seemed weird14:14
jrollit seems like our current tools for tracking that are fairly sufficient14:14
fungifrickler: ^ maybe that was you14:14
jrollah, right14:14
ttxfungi: yeah there are a couple of repos we should save so that they don't need to move14:14
ttxI did post to -infra14:14
ttxIf there is agreement there, I can propose the relevant patches14:15
jrollttx: I was about to say I could do that, but go for it :)14:15
fungiildikov also asked that we not move the edge group's repo out of openstack for now (and later we can talk about moving foundation/board repos into a dedicated osf namespace or something)14:15
ttxok14:15
jrollhm, I missed that one14:15
jrollis the edge group's repo not part of a sig or something?14:16
ttxThe edge group one can be moved under FEMDC SIG alright14:16
fungii'll look into why networking-l2gw-tempest-plugin got missed14:16
ttxTheJulia: Board meeting will be at the Hyatt14:16
smcginnisThanks ttx14:16
ttxTheJulia: I'll have more precision once we actually have a room name for it14:16
jrollwell, this seems handled. fungi, ttx, let me know if I can help anywhere here :)14:16
ildikovo/14:18
ildikovyes, I did asked fungi's opinion as that repo is a bit of a special flower and that's what we came up with14:18
ildikovhappy to explore further options if people disagree14:18
fungifor the record, 649071 won't impact the move whether we merge it or not, since we're expressly not moving things listed as legacy openstack projects unless they're already assigned to another confirmed or pilot open infrastructure project14:18
fungiildikov: ttx is suggesting moving it under the fedmc wg14:18
ttxSIG14:19
ttxnot wg14:19
fungier, sig, right14:19
ildikovthat doesn't exist anymore officially14:19
ildikovthat's my only concern with that move14:19
ttxWell, officially, it does14:19
ttxhttps://governance.openstack.org/sigs/14:19
ttxit might be dead, but it still exists "officially"14:20
TheJuliattx: awesome, thanks14:20
ildikovit may have not be removed from there but I remeber we kind of announced in the annual report or somewhere that it got merged into the Edge WG14:20
ildikovmight've missed some administration steps which is unfortunate14:20
ildikovcan look into that14:20
ildikovit's also an OpenStack SIG while the Edge WG is more of an OSF WG but not governed by the board14:21
fungijroll: openstack/networking-l2gw-tempest-plugin isn't in reference/projects.yaml, that's why it's getting evicted in the draft list. do we have a change proposed to add it?14:21
jrollfungi: we don't, I'm happy to make one14:22
ttxwe could move it to osf/ I guess. We already have a couple of things I'd like to move there14:22
fungijroll: thanks! sounds good14:22
ildikovttx: +114:22
csatariFEMDC exists, but suspended its operations to focus more on ECG.14:22
csatariA bit of circular dependency :)14:22
fungittx: we can add osf things to the ethercalc if they're not tracked in openstack/governance and the script will just pick them up14:22
fungialso the ethercalc overrides anything listed in reference/legacy.yaml to cover cases where repos moved or are moving to dedicated namespaces, we just include the legacy list so that anything there doesn't get evicted to the x namespace14:24
jrollfungi: strangely enough, networking-l2gw is retired :)14:24
ttxfungi: ok, if you can remind me the link for the ethercalc I'll do that now14:24
fungijroll: oh! so maybe we simply missed adding it to legacy.yaml when retiring it14:24
fungittx: https://ethercalc.openstack.org/opendev-transition14:24
fungii guess list yourself as the contact for any osf namespace entries14:25
jrollfungi: or we found a corner case - these deliverables were retired as *official* projects from neutron when they evicted the plugins, but are still alive and well14:25
jrollor at least active.14:25
ildikovcsatari: I'll find to sync up with Adrien and crew to see how to administer what's up with it14:25
ildikov*find time :)14:25
csatariok, ildikov. Thanks.14:26
fungijroll: yeah, any repos we take out of reference/projects.yaml need to go in reference/legacy.yaml (that way we also count contributions for them as valid electors for those teams or the tc for a while after an abrupt removal)14:26
openstackgerritThierry Carrez proposed openstack/governance master: Adopt openstack/governance-website as TC repo  https://review.openstack.org/65344614:26
openstackgerritThierry Carrez proposed openstack/governance master: Adopt openstack/arch-wg as TC repo  https://review.openstack.org/65344714:26
jrollfungi: right, but this makes me realize there are projects in legacy.yaml which are unofficial and active. should those be in openstack/ or x/ ?14:27
* ttx adds openstack/openstack while at it14:27
openstackgerritJim Rollenhagen proposed openstack/governance master: Add openstack/networking-l2gw-tempest-plugin to legacy.yaml  https://review.openstack.org/65344914:27
jrollat any rate, this change makes sense ^14:28
jrollbut the question is, do those now-unofficial projects belong in the openstack namespace?14:28
fungijroll: i think it's a bigger discussion, likely related to my ml post about forcing projects which want to continue outside openstack governance to fork so we can retire the copies in our namespace14:28
jrollfungi: probably. skip it for this week, I guess?14:28
fungii think we can solve it after migration14:29
openstackgerritThierry Carrez proposed openstack/governance master: Adopt openstack/openstack as TC repository  https://review.openstack.org/65345014:29
jrollok14:29
ttxildikov: so should I suggest openstack/edge-computing-group -> osf/edge-computing-group with you as contact?14:32
ildikovttx: yes, sounds good14:33
ildikovttx: thank you!!14:33
ttxdone14:34
ildikov\o/ :)14:35
*** david-lyle is now known as dklyle14:35
ttxildikov: the list also contains openstack/upstream-institute-virtual-environment14:38
ildikovttx: proposed a patch today to move it under the docs umbrella14:39
ttxok14:39
jrollthat one is here: https://review.openstack.org/#/c/653360/14:39
ildikovhttps://review.openstack.org/#/c/653366/14:39
ildikovso it lives at the same place as the training-guides repo14:40
ildikovjroll: correct, thanks, I grabbed the wrong link14:41
jrollno worries14:41
gmann'microversion-parse' is the another i feel should be added somewhere but do know where14:42
fungias a fallback, if we want to avoid something moving out of openstack but don't know where we want to track it officially yet, we *can* stick it in the ethercalc "renamed" to itself and that should cause it to not get moved14:44
mnasertc-members: I'd like folks to please pay attention to this review -- https://review.openstack.org/#/c/645361/414:45
fungii just want to make sure, if we do that, we also circle back around after the migration and decide what to do with it14:45
mnaserit has minimal number of votes, but it's pretty big, so I'd be more comfortable with more eyes on it.14:45
* lbragstad is around for questioning if needed14:49
*** AJaeger has joined #openstack-tc14:50
AJaegerjroll, I commented on https://review.openstack.org/#/c/653449 - that plugin repo was never under governance, it was created after the neutron-stadium changes and retirement of the other repo. So, a nice corner case14:52
*** e0ne has joined #openstack-tc14:53
openstackgerritMerged openstack/governance master: Rename Chef OpenStack project and update it  https://review.openstack.org/64835614:55
*** weshay is now known as weshay|rover14:57
gmannfungi: ok but at the end (after migration), it cannot stay as openstack/ because that is not official project right ? so now or later they need to be moved.14:59
fungigmann: well, we need to discuss how we handle projects if they were official repos at any point in the past15:00
fungisince we've had users get confused after we removed active projects from openstack and assume we're still in control of them15:01
mnaserthat's a good point15:02
mnaserwe don't want things to just start randomly 404-ing either :\15:02
mnaserunless we can do a redirect when we remove something15:02
fungiwell, the redirect is part of the problem, in my opinion. i've been leaning toward requiring them to fork, and retiring the copy in our namespace15:02
fungithe readme in the retired repo can then clearly state that the effort is being continued by some people outside of openstack, and where to find them15:03
fungifor example, if we'd retired all the fuel repos and forced them to fork copies into a fuel namespace15:04
fungii think there'd have been far fewer users assuming it was still an openstack project when the copies in the openstack namespace are empty except for a readme15:05
fungiwhereas moving them and leaving a redirect behind means folks pulling from the old git remote never notice, unless they pay attention to the redirect mentioned on stderr by the git utility15:06
fungiso they're still consuming openstack/fuel-whatever as far as they know15:06
fungiand in this new world where we're going to start equating the openstack namespace with official status of some kind, that can be significantly misleading15:07
fungi(i think it's less of a concern for stuff which moved before or during this week, when the meaning of the openstack namespace is still very muddy)15:07
gmannyeah, i agree on that point. there are lot people (specially not involved in community ) needs to know that change.15:08
gmanni mainly concern about 'microversion-parse' which is very much close and only(till now) for openstack microvesion only but not official. let me propose to keep it under openstack/ in ethercal and later we decide if we can add it somewhere like in olso etc15:11
clarkbgmann: cdent repsonded to that and didn't seem to want to move it15:12
clarkber didn't want to move it under openstack/15:12
gmannclarkb: yeah.  I will put my suggestion to his reply if he like. there are more classes i feel we can put under this lib from nova repo if that lib stay somewhere in openstack15:15
jrollAJaeger: bah, that's fun. I'm not sure what to do with it then.15:44
jrollseems like either l2gw should be in x/ or l2gw-tempest-plugin should be in openstack/, I don't know the best way to accomplish (and document) that cleanly15:45
*** adriant has quit IRC15:51
*** adriant has joined #openstack-tc15:53
fungii think we could keep it in openstack for the migration, but then have a bigger discussion about what to do with stuff in legacy.yaml which isn't retired but is still being actively developed while no longer under our governance15:57
fungi(and i know that repo specifically isn't in legacy.yaml, but the same team seems to be caring for it as another one which is)15:58
fungifriday is far from being our only opportunity to move things to different namespaces, just a good opportunity to do any which are easy decisions15:59
*** diablo_rojo has joined #openstack-tc15:59
fungikicking the harder choices down the road a ways so we can focus on other priorities seems a reasonable approach15:59
*** dims has quit IRC16:07
jroll++16:12
*** jpich has quit IRC16:20
*** dtantsur is now known as dtantsur|afk16:24
*** david-lyle has joined #openstack-tc16:24
*** dangtrinhnt_ has joined #openstack-tc16:25
*** dangtrinhnt has quit IRC16:27
*** dklyle has quit IRC16:27
*** dims has joined #openstack-tc16:54
*** dims has quit IRC16:59
*** e0ne has quit IRC17:01
*** dims has joined #openstack-tc17:01
*** ricolin has quit IRC17:04
mnaseras an update on tricircle, I've been in touch with them and they're planning to start using their meeting slot once again17:07
mnaserthe PTL has been taking initiative and trying to also help out with people to get in the IRC channels17:07
mnaserand I think their plan is to start having meetings from now on there17:07
mnaserso slowly but surely, I think with right guidance (and thanks to help from Horace), we'll be able to help support them within our community17:07
gmann\o/17:11
gmannthanks mnaser17:18
fungithat's the best possible outcome17:45
*** david-lyle is now known as dklyle17:55
*** AJaeger has left #openstack-tc18:43
*** e0ne has joined #openstack-tc19:17
*** e0ne has quit IRC19:20
*** e0ne has joined #openstack-tc19:22
*** tjgresha has quit IRC19:33
*** tjgresha_nope has joined #openstack-tc19:33
*** tjgresha_nope has quit IRC19:40
*** tjgresha has joined #openstack-tc19:44
*** tjgresha has quit IRC19:51
diablo_rojo+2 Best possible outcome :)19:56
diablo_rojothanks mnaser!19:56
openstackgerritGhanshyam Mann proposed openstack/governance master: Add IPV6 support and testing goal for Train  https://review.openstack.org/65354520:01
gmanntc-members: i have drafted the IPV6 support and testing goal proposal: https://review.openstack.org/65354520:02
gmannlbragstad: evrardjp: ^^20:02
lbragstadthanks gmann20:03
*** ijolliffe has quit IRC20:03
TheJuliaIs it wrong that I'm excited by just the mention of ipv6 support and testing?20:09
gmannlbragstad: you want to send this to ML for review or you will include in your goal update email20:09
gmannTheJulia: i am just targeting for all services listen on ipv6 and we have testing job to test the same20:10
lbragstadyeah - an update to the mailing list would be good20:10
gmannthere are lot more scenario for ipv6 which can be tested one by one20:10
gmannlbragstad: ok. thanks20:10
lbragstadfwiw - i don't think evrardjp or myself were planning on sending another update about goal progress, at least not this late20:11
lbragstadbut i'll send something out for this specifically, calling for reviews20:11
TheJuliagmann: Well, I _hope_ it may also help us drive towards ensuring that devstack runs or is executed such that there is always working v6 on the test VM20:11
gmannlbragstad: ok20:11
gmannyeah20:12
TheJuliagmann: It mentally goes back to trying to do it for ironic and hitting roadblocks with test VMs what were v4 only :(20:12
mugsiethis will cause some projects to have to test the nova VM IPv6 capabilities as well20:12
TheJulias/nova/neutron/?20:13
mugsiee.g. octavia ssh's  to VMs, and can have VMs call back to the octavia API (which is Ipv6 only will mean the VMs will have to have v6)20:13
gmannyou mean connectivity between VMs over ipv6 ?20:13
mugsieyeah20:13
mugsieVM -> control plane over v6 anyway20:14
TheJuliav6 all the things!20:14
johnsom+1 v6 all the things!20:14
mugsieand heat may fall into that bucket with software deployments as well?20:14
fungia related issue came up ni #openstack-infra earlier today... oslo_service apparently defaults to listening on 0.0.0.0 instead of :: or dynamically identifying available address families20:14
TheJuliado we need v6 all the things stickers?20:14
fungii think we at least need to make sure our stickers are ipv6-ready ;)20:15
mugsiebut it means that the line 34 note may need to be removed to let others test20:15
mugsie(I am ++ on that though :) )20:15
TheJuliafungi: only if I somehow find the arin stickers a friend gifted me20:16
gmannfungi: that might not be aligned with what that goal propose, we need each service to dynamically identify the listening address20:16
fungigmann: yeah, i assume that to be the case20:17
gmannmugsie: that is something i was testing on this https://review.openstack.org/#/c/653161/20:17
TheJuliaI suspect that should be a change oslo_service should make to default to making v6 socket binds20:18
gmannbut i did not find VM assigned the v6 address by neutron or may be more setting we need20:18
clarkbwe actually already do a really good job on this (its definitely not complete but comapred to say docker which completely breaks if you give it an ipv6 address to push to its great)20:18
gmannmugsie: so i mentioned VM connectivity thing out of scope for this goal20:19
TheJulianeutron v6 networking is a little... different and we shouldn't drive chagnes that could negatively impact that experience by creating a focus on v6. The key is going to ensure that the substrate all works completely on v6. I suspect this will align well with many developers.20:20
clarkbthere are (or were) tempest tests that conncet to test VMs over ipv620:21
clarkbwe had to update cirros to get that working iirc20:21
mugsiegmann: but it can't  be out of scope, if we want octavia or similar projects to be able to test20:21
clarkbthe biggest gap is probably what mugsie points out. It is where our services interact with compute resources20:22
clarkbwe also have a job that tests the apis operate over ipv6 too iirc20:22
gmannclarkb: i am trying with IP_VERSION=6 on this - https://review.openstack.org/#/c/653161/ but as you mentioned it might need test image updates20:23
clarkbgmann: there are specific tests that do that already20:23
clarkbor were, maybe we removed them? that would be sad20:23
clarkbthey even spun up multiple VMs and checked ssh between the VMs over ipv6 and not just tempest to the VM20:24
gmannthere were not removed, let me check20:24
TheJuliamaybe instead... the focus should be "I don't want v4 in my openstack"20:24
gmannhttps://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_v6.py20:24
* TheJulia runs to the doctor, bbl20:25
clarkbgmann: my guess is that your chagne fails because not all VMs are told to boot with the v6 network20:25
johnsomWe spin up cirros with IPv6 addresses so we can test IPv6 member servers behind the load balancer.20:25
clarkbbut when they are told to do so it works aiui and we test that20:25
gmannyeah20:25
johnsomFYI: https://review.openstack.org/#/c/611405/20:26
gmannmay be i was little over thinking on those- run tempest with ipv4 and ipv6 and both pass. But it may need lot of work.20:27
gmannbut not complete tempest run is needed to prove openstack VM working on ipv620:27
clarkbno but by testing it as part of the main suite we ensure it is always tested20:28
smcginnisMy experience has been like what TheJulia said - tests can pass fine with IPv6 enabled, but the real issues start when you want to ensure there is nothing at all still using IPv4 somewhere in there.20:29
clarkbsmcginnis: that is unfortunately incredibly difficult to test because we rely on ipv4 to get to the test VMs20:29
gmannclarkb: yeah, let me update my tempest patch to run ipv6 tests which are marked as 'slow' and being skipped in tempest-full.20:30
smcginnisclarkb: Yeah. The only way we were able to do it in a past life was set up an isolated special purpose lab.20:30
clarkbwe could have the test suite disable ipv4 on the test node, disappear for an hour, then turn ipv4 back on so that zuul can ask it if things worked20:30
clarkbbut that is likely to be fragile20:30
*** e0ne has quit IRC20:31
clarkbanother approach may be to firewall or tcpdump and then check if ipv4 was used at all when done for anything otherthan the zuul communication20:32
clarkbif it were me I'd probably set up a job that defaults to ipv6 for things but doesn't try very hard to disable ipv4. Then check a pcap for content on the ipv4 address20:32
clarkbthat will also help you identify what is using ipv4 so that it can be fixed20:33
*** tjgresha has joined #openstack-tc20:34
*** tjgresha has quit IRC20:39
*** tjgresha has joined #openstack-tc20:54
*** tjgresha has quit IRC20:56
*** whoami-rajat has quit IRC21:01
openstackgerritGhanshyam Mann proposed openstack/governance master: Add IPV6 support and testing goal for Train  https://review.openstack.org/65354521:13
*** logan- has quit IRC21:34
*** logan- has joined #openstack-tc21:37
*** mriedem has quit IRC22:10
*** lbragstad has quit IRC22:33
*** lbragstad has joined #openstack-tc22:35
*** jamesmcarthur has joined #openstack-tc23:07
*** jamesmcarthur has quit IRC23:23
*** tosky has quit IRC23:38

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