Thursday, 2015-01-22

*** banix has joined #openstack-meeting-400:00
*** salv-orlando has quit IRC00:01
*** salv-orlando has joined #openstack-meeting-400:01
*** mwang2__ has quit IRC00:02
*** Rockyg has joined #openstack-meeting-400:13
*** banix has quit IRC00:16
*** banix has joined #openstack-meeting-400:19
*** Kerralissa has quit IRC00:20
*** Kerralissa has joined #openstack-meeting-400:21
*** Kerralissa has quit IRC00:25
*** Kerralissa has joined #openstack-meeting-400:25
*** Kerralissa has quit IRC00:28
*** watanabe_isao has quit IRC00:31
*** Kerralissa has joined #openstack-meeting-400:34
*** ChuckC has joined #openstack-meeting-400:35
*** carl_baldwin has quit IRC00:42
*** mwang2 has joined #openstack-meeting-400:48
*** carl_baldwin has joined #openstack-meeting-400:48
*** banix has quit IRC00:53
*** mestery has quit IRC01:19
*** carl_baldwin has quit IRC01:19
*** carl_baldwin has joined #openstack-meeting-401:21
*** Rockyg has quit IRC01:24
*** carl_baldwin has quit IRC01:25
*** emagana has quit IRC01:26
*** emagana has joined #openstack-meeting-401:26
*** salv-orlando has quit IRC01:30
*** emagana has quit IRC01:31
*** banix has joined #openstack-meeting-401:35
*** SridharRamaswamy has quit IRC01:39
*** SumitNaiksatam has quit IRC01:45
*** banix has quit IRC01:49
*** sigmavirus24 is now known as sigmavirus24_awa01:57
*** ChuckC_ has joined #openstack-meeting-401:58
*** banix has joined #openstack-meeting-401:58
*** kragniz_ has joined #openstack-meeting-401:59
*** banix has quit IRC01:59
*** ChuckC has quit IRC02:06
*** kragniz has quit IRC02:06
*** sarob has joined #openstack-meeting-402:09
*** s3wong has quit IRC02:28
*** salv-orlando has joined #openstack-meeting-402:33
*** salv-orlando has quit IRC02:37
*** yamahata has joined #openstack-meeting-402:42
*** sarob has quit IRC02:46
*** Kerralissa has quit IRC02:47
*** yamahata has quit IRC02:53
*** sballe__ has quit IRC02:58
*** VW_ has quit IRC03:01
*** ivar-lazzaro has joined #openstack-meeting-403:21
*** ajmiller has quit IRC03:22
*** ivar-laz_ has quit IRC03:24
*** ivar-lazzaro has quit IRC03:25
*** mwang2 has quit IRC03:29
*** mwang2 has joined #openstack-meeting-403:30
*** sbalukoff has quit IRC03:36
*** yamahata has joined #openstack-meeting-403:45
*** zhiyan has quit IRC03:48
*** zhiyan has joined #openstack-meeting-403:49
*** yamahata has quit IRC03:51
*** yamahata has joined #openstack-meeting-403:51
*** ChuckC_ has quit IRC04:02
*** ChuckC_ has joined #openstack-meeting-404:02
*** yamahata has quit IRC04:02
*** yamahata has joined #openstack-meeting-404:11
*** yamahata has quit IRC04:11
*** yamahata has joined #openstack-meeting-404:11
*** banix has joined #openstack-meeting-404:30
*** carl_baldwin has joined #openstack-meeting-404:36
*** yamahata has quit IRC04:52
*** salv-orlando has joined #openstack-meeting-404:52
*** sbalukoff has joined #openstack-meeting-404:56
*** salv-orlando has quit IRC04:59
*** carl_baldwin has quit IRC05:04
*** mestery has joined #openstack-meeting-405:19
*** banix has quit IRC05:22
*** nuritv has quit IRC05:46
*** SridharRamaswamy has joined #openstack-meeting-405:48
*** SridharRamaswamy has quit IRC05:52
*** SridharRamaswamy has joined #openstack-meeting-405:53
*** salv-orlando has joined #openstack-meeting-405:55
*** salv-orlando has quit IRC06:01
*** numan has joined #openstack-meeting-406:07
*** mestery has quit IRC06:17
*** watanabe_isao has joined #openstack-meeting-406:27
*** watanabe_isao has quit IRC06:32
*** kobis has joined #openstack-meeting-407:00
*** SumitNaiksatam has joined #openstack-meeting-407:05
*** SridharRamaswamy has quit IRC07:18
*** SridharRamaswamy has joined #openstack-meeting-407:27
*** SridharRamaswam1 has joined #openstack-meeting-407:38
*** SridharRamaswamy has quit IRC07:39
*** yamahata has joined #openstack-meeting-407:56
*** salv-orlando has joined #openstack-meeting-408:10
*** matrohon has joined #openstack-meeting-408:10
*** evgenyf has joined #openstack-meeting-408:12
*** salv-orlando has quit IRC08:16
*** yamahata has quit IRC08:30
*** salv-orlando has joined #openstack-meeting-408:39
*** SridharRamaswam1 has quit IRC08:40
*** salv-orlando has quit IRC08:41
*** salv-orlando has joined #openstack-meeting-408:41
*** pkoniszewski has joined #openstack-meeting-408:45
*** zhiyan has quit IRC08:55
*** zhiyan has joined #openstack-meeting-409:01
*** pkoniszewski has quit IRC09:15
*** pkonisze has joined #openstack-meeting-409:15
*** belmoreira has joined #openstack-meeting-409:16
*** pkonisze has quit IRC09:19
*** pkoniszewski has joined #openstack-meeting-409:27
*** pkoniszewski has quit IRC09:38
*** pkoniszewski has joined #openstack-meeting-409:40
*** pkoniszewski has quit IRC09:45
*** mmedvede_ has joined #openstack-meeting-410:12
*** rfolco has joined #openstack-meeting-411:00
*** salv-orl_ has joined #openstack-meeting-411:13
*** salv-orlando has quit IRC11:16
*** salv-orl_ has quit IRC11:45
*** kragniz_ is now known as kragniz11:45
*** salv-orlando has joined #openstack-meeting-411:45
*** igordcard has joined #openstack-meeting-411:49
*** salv-orl_ has joined #openstack-meeting-411:49
*** salv-orlando has quit IRC11:49
*** salv-orl_ has quit IRC11:50
*** salv-orlando has joined #openstack-meeting-411:51
*** evgenyf has quit IRC12:00
*** evgenyf has joined #openstack-meeting-412:38
*** ja_ has joined #openstack-meeting-412:56
*** markvoelker has joined #openstack-meeting-413:19
*** pkoniszewski has joined #openstack-meeting-413:27
*** pkoniszewski has quit IRC13:37
*** VW_ has joined #openstack-meeting-413:58
*** lakshmiS has joined #openstack-meeting-414:04
*** mestery has joined #openstack-meeting-414:15
*** lakshmiS has quit IRC14:19
*** banix has joined #openstack-meeting-414:22
*** krykowski has joined #openstack-meeting-414:25
*** stpierre has joined #openstack-meeting-414:36
*** sigmavirus24_awa is now known as sigmavirus2414:50
*** ativelkov has joined #openstack-meeting-414:50
*** krykowski has quit IRC14:55
*** carl_baldwin has joined #openstack-meeting-414:58
nikhil_k#startmeeting Glance15:00
openstackMeeting started Thu Jan 22 15:00:18 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: Glance)"15:00
openstackThe meeting name has been set to 'glance'15:00
*** krykowski has joined #openstack-meeting-415:00
kragnizo/15:00
ativelkovo/15:00
sigmavirus24o/15:00
*** pennerc has joined #openstack-meeting-415:00
*** ivasilevskaya has joined #openstack-meeting-415:00
sigmavirus24f/goto bops15:00
pennerco/15:00
*** lakshmiS has joined #openstack-meeting-415:00
*** TravT_ has joined #openstack-meeting-415:01
*** yamahata has joined #openstack-meeting-415:01
nikhil_kLet's get started!15:01
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda15:01
nikhil_k#topic Updates15:01
*** openstack changes topic to "Updates (Meeting topic: Glance)"15:01
TravT_o/15:01
nikhil_kThe updates this week are about15:01
nikhil_k1. Mid-cycle meetup schedule ..15:01
nikhil_k2. K-215:02
nikhil_k3. K315:02
nikhil_k#topic Mid-cycle meetup schedule15:02
*** openstack changes topic to "Mid-cycle meetup schedule (Meeting topic: Glance)"15:02
*** rosmaita has joined #openstack-meeting-415:02
nikhil_k#link https://etherpad.openstack.org/p/kilo-glance-mid-cycle-meetup15:02
nikhil_kif you have responded, you must have received an email.15:03
nikhil_kIf anyone has any questions on the venue, directions, topics, schedule, food etc15:03
nikhil_kPlease bring it up now or send an email to me15:04
sigmavirus24How do remote participants request food? /kidding15:04
nikhil_k#action everyone: please respond to the long lunch proposal either way soon15:05
nikhil_kNext.15:05
nikhil_k#topic K-215:05
*** openstack changes topic to "K-2 (Meeting topic: Glance)"15:05
nikhil_khttps://launchpad.net/glance/+milestone/kilo-215:05
nikhil_kWe've a long list of reviews15:06
nikhil_kPlease take a look at them on priority.15:06
nikhil_kIf the code has not major objections, and the spec is consistent with the code proposed it would be merged soon15:06
nikhil_kYou must already have received some feedback15:07
* sigmavirus24 hasn't on the Policy blueprint15:07
nikhil_k#action: everyone, the k2 bugs (if not necessary) can moved to k3 as long as corresponding code does not look in a good shape.15:08
nikhil_ksigmavirus24: that one is dicey15:08
nikhil_klet's see how things go on others in next couple of days15:08
nikhil_kwe need reviewers focused on small set of patches so that at least some get in15:08
sigmavirus24Yeah, I figured mine would be okay for k-3 so I targetted there. Someone moved it to k-2 apparently15:09
nikhil_kIf anyone is worried about a patch not getting in soon, this might be a good time to speak up (or about something getting in that shouldn't be)15:09
*** sabari has joined #openstack-meeting-415:09
nikhil_ksigmavirus24: it was me :P (optimistically prioritizing)15:10
nikhil_kNext.15:10
nikhil_k#topic K315:10
*** openstack changes topic to "K3 (Meeting topic: Glance)"15:10
nikhil_kThe following features/additions/changes have been deferred to k315:11
nikhil_k1. Catalog Service15:11
nikhil_k2. Artifacts15:11
nikhil_kThe deactivation of an image and policy changes *may* get in k2 . (due to some recent developments)15:12
*** hemanth_ has joined #openstack-meeting-415:12
nikhil_kOther specs that have not received any significant reviews yet15:13
nikhil_kThey are just hard to focus on given other major changes that we are planning to adopt this cycle.15:13
*** dboik has joined #openstack-meeting-415:13
nikhil_kThat was the updated part. We can leave some time here for feedback.15:14
nikhil_k*update*15:14
TravT_So, FYI, with catalog service, one of the tasks was to add notifications for metadefs.  You and Brian thought we should break that out.  So, I'll be putting up a spec on that.15:15
sigmavirus24That review is already written, yes?15:15
nikhil_kTravT_: Sounds like a good idea.15:16
sigmavirus24(The actual metadef notification code)15:16
TravT_yes, kamil has a good start on it15:16
krykowskiYup, the implementation is ready (almost?)15:16
nikhil_kIt's fine to start off sluggish and keep a watch on the bugs.15:16
nikhil_kSeems like metadef team has been actively resolving some as well as has been great with specs.15:17
*** numan has quit IRC15:17
nikhil_k(Basically, we would be short of reviewers)15:17
*** kobis has quit IRC15:18
nikhil_k#topic Reviews/Bugs/Releases15:18
*** openstack changes topic to "Reviews/Bugs/Releases (Meeting topic: Glance)"15:18
nikhil_k1. Glance client15:18
nikhil_khttps://launchpad.net/python-glanceclient/+milestone/v0.16.015:18
nikhil_k2. glance_store15:18
nikhil_khttps://launchpad.net/glance-store/+milestone/v0.1.1115:18
nikhil_kThose are the planned ones15:18
nikhil_kkragniz: brought a good point that we should probably release SemVer style15:19
mfedosinwhat about sorting features for v2 in the client?15:19
nikhil_kSo, yeah. Things like that - please mark it on the lp and15:19
nikhil_kleave a message to sigmavirus24 kragniz jokke_ zhiyan or me to add it to the trello board15:20
nikhil_kflapper87 too15:20
nikhil_ksigmavirus24: I kinda stole your topic, did you have anything more important to point out?15:20
nikhil_k(sorry about that)15:20
sigmavirus24Nope. Just wanted to discuss it's progress :)15:21
nikhil_kCool. Looks like reviews for the most part.15:21
kragnizI'm planning on writing release notes for client and store when some of the reviews are merged15:21
nikhil_kkragniz: +115:21
sigmavirus24I thought PBR did that for us or something15:21
kragnizsigmavirus24: not release notes15:22
nikhil_kpersonal touch is always welcoming ;)15:22
kragnizsigmavirus24: we went over this with dhellmann :P15:22
sigmavirus24PBR confuses me15:22
* nikhil_k means that in the modest possible way15:22
nikhil_kWho's next?15:24
stpierreis this a point where i can hop in? i need to find core reviewer(s) for https://review.openstack.org/#/c/145223/15:24
nikhil_kFeature request:-15:24
nikhil_khttps://bugs.launchpad.net/glance/+bug/141121515:24
sigmavirus24Yeah I added that and wanted to bring attention to it. It seems useful but I'm not sure if it is really desirable15:25
*** pkoniszewski has joined #openstack-meeting-415:25
sigmavirus24Also I wanted to make sure no one things that anything other than a glob-like syntax is necessary15:25
nikhil_ksigmavirus24: we've planning to work on the cloning feature for that15:26
sigmavirus24Compiling regular expressions provided by the user seems like a badidea15:26
rosmaita+115:26
rosmaitawe want to push that stuff to the metadata indexing service15:27
sigmavirus24stpierre: I'm not a core but I'll look at that today15:27
nikhil_kstpierre: can we wait just a bit? would like to give some feedback in the open discussion15:28
stpierresure15:28
nikhil_kNext.15:28
nikhil_khttps://bugs.launchpad.net/glance/+bug/1188532 nominated for juno and icehouse15:28
sigmavirus24The OSSA requested someone nominate it for those but we haven't accepted the nominations15:29
sigmavirus24(Or we hadn't as of last night)15:29
sigmavirus24So I wanted feedback as to whether we do want to backport and someone to accept those. I'll backport them today since teh juno branch freeze starts on 30 Jan15:29
nikhil_ksigmavirus24: the duplicate one has more info unfortunately https://bugs.launchpad.net/glance/+bug/138397315:30
nikhil_ksigmavirus24: I'd started work on it yday and could get to it only partially. It's tricky due to the glance_store changes. We can discuss more offline.15:30
*** ajmiller has joined #openstack-meeting-415:30
TravT_That looks like a good one to backport to me15:31
sigmavirus24Okay15:31
sigmavirus24I just wanted to bring it up since the next juno release is not far off15:32
ativelkovMay I for some attention on https://bugs.launchpad.net/glance/+bug/1412802 ?  Quite a nasty bug, and also worths backporting to I-J15:32
nikhil_ksigmavirus24: this is the most active duplicate https://bugs.launchpad.net/glance/+bug/139883015:32
sigmavirus24Oh that's already nominated. Nevermind :)15:33
nikhil_kyeah, lp needs a cleanup there ;)15:33
*** sabari is now known as zz_sabari15:34
nikhil_kativelkov: can we get to you review after sigmavirus24's next one?15:35
TravT_ativelkov: nikhil_k: I'm kind of surprised that is only a medium.  since it is data corruption \ loss.15:35
ativelkovSure, sorry for interrupting15:35
sigmavirus24Next one is just the spec for passing real targets to the policy enforcer (which is now targetted for k-2)15:36
nikhil_kTravT_: be back on that, sorry15:36
* TravT_ shuts mouth too ;)15:36
nikhil_khttps://review.openstack.org/#/c/149112/15:36
sigmavirus24so I'd love feedback on that and early review on the associated review is appreciated. I have ideas for tests as detailed in the spec but haven't added them15:36
sigmavirus24yes, thanks nikhil15:36
nikhil_kawesome, thanks for that pointer sigmavirus24 !15:37
* sigmavirus24 hands torch to ativelkov 15:37
ativelkovThanks sigmavirus24 :)15:37
ativelkovWell, that's a data corruption issue I recently found15:38
ativelkovThe fix is here: https://review.openstack.org/#/c/148574/15:38
ativelkovAs it happens in Icehouse and Juno, I proposed to backport it (which is quite simple: the changed code haven't been modified for a long time)15:39
* sigmavirus24 is reviewing15:40
nikhil_kativelkov: TravT_ : yeah, I think we can mark it critical.15:40
nikhil_kOur initial discussion with ativelkov lead me to believe this was specific to stores, with the values associated to them15:40
*** pkoniszewski has quit IRC15:40
*** cfarquhar has joined #openstack-meeting-415:40
nikhil_kThanks for the pointer TravT_ , much appreciated!15:41
sigmavirus24Should we target that to k-2?15:41
nikhil_kjust did :)15:41
nikhil_kThanks15:42
ativelkovIf more reviews come, we may definetly release it in k215:42
nikhil_kmight be a good idea to focus on critical bug sooner15:42
nikhil_k;)15:42
nikhil_kNeed to sync openstack/common from oslo-incubator:15:43
lakshmiSNeed to sync openstack/common from oslo-incubator for service module - catalog index service requires it for notifications listener15:43
nikhil_klakshmiS: ^ (seems like you)15:43
lakshmiSShould i open a bug to import it?15:43
nikhil_kthat would be great15:43
lakshmiSWe are also looking at the service module to use as a framework for notification refactoring - similar to how ceilometer uses it for notifications.15:43
lakshmiSare there any other ideas on refactoring notifications?15:44
* sigmavirus24 hasn't looked at notifications in depth yet so I can't give useful feedback, yet15:45
krykowskiaccording to current work at notifications for metadata objects https://review.openstack.org/#/c/148546/ which is based on implementation from images15:45
*** pkoniszewski has joined #openstack-meeting-415:46
nikhil_kWe are thinking about some notification refactoring in glance, this might come up in Nova-Glance common session at the mini-summit15:46
lakshmiSis there a agenda for nova-glance common session?15:46
nikhil_kPlease free to float this idea on the summit etherpad, we can try to sneak it in >.>15:46
lakshmiSok15:46
nikhil_k#topic Open Discussion15:47
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"15:47
nikhil_kstpierre: about your spec15:47
nikhil_kLooks like a good improvement. I'm just worried about it clashing with https://review.openstack.org/#/c/125156/ and (possibly) https://review.openstack.org/14133115:48
nikhil_kJust with the code proposal path.15:49
*** dboik has quit IRC15:49
nikhil_kstpierre: if you've a draft ready, we can try to merge it faster than those two.15:49
nikhil_k(unlikely for k2)15:50
*** dboik has joined #openstack-meeting-415:50
stpierrei don't have anything ready yet unfortunately15:50
*** pkoniszewski has quit IRC15:50
*** cloudnull has joined #openstack-meeting-415:51
nikhil_kstpierre: no issues, not a possibility in next 2 weeks. So, anything after than is welcome :)15:51
stpierreokay, i can definitely have something by then15:51
nikhil_ksigmavirus24: would you like to be assigned to https://bugs.launchpad.net/glance/+bug/1398830 backports? (I can help as needed and in review too ;) )15:51
stpierrethe only potentially serious point of contention i see is with the "in-memory cache" in the first spec there; it doesn't describe how the in-memory cache will be populated. but even that should be fairly trivial since my change will just replace the current read/write operations with something consistent and easy :)15:51
stpierreso all i need is a core reviewer to sign on and i can be off and writing code15:52
nikhil_kstpierre: feel free to assign and bug me on this15:52
sigmavirus24nikhil_k: go for it15:52
sigmavirus24i'll assign myself15:52
nikhil_ksigmavirus24: awesome!15:52
sigmavirus24I'm going to prioritize juno though15:52
sigmavirus24because deadlines15:52
stpierrenikhil_k: tyvm15:52
nikhil_k+115:52
nikhil_kstpierre: :)15:53
*** toxick has joined #openstack-meeting-415:53
nikhil_kIf nothing else ...15:54
*** mattt has joined #openstack-meeting-415:55
TravT_looking forward to seeing many of you next week!15:55
sigmavirus24TravT_: ;_;15:55
kragnizTravT_: ;_;15:55
sigmavirus24Also TravT_ sorry I misunderstood your spec. I read it totally wrong :)15:56
TravT_yeah, wish you guys could be there.15:56
TravT_sigmavirus24: no worries15:56
nikhil_kThanks all!15:56
*** git-harry has joined #openstack-meeting-415:56
nikhil_k#endmeeting15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:56
openstackMeeting ended Thu Jan 22 15:56:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-22-15.00.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-22-15.00.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-22-15.00.log.html15:57
*** pmesserli has joined #openstack-meeting-415:57
*** pennerc has left #openstack-meeting-415:57
*** briancurtin has quit IRC15:57
*** odyssey4me has joined #openstack-meeting-415:57
*** andymccr has joined #openstack-meeting-415:57
hughsaundershey15:57
cloudnullhows it15:58
d34dh0r53lo15:58
*** TravT_ has left #openstack-meeting-415:58
*** lakshmiS has quit IRC15:58
odyssey4me|o15:58
*** klamath has joined #openstack-meeting-415:58
sigmavirus24o/15:58
sigmavirus24long time no see odyssey4me and hughsaunders15:58
*** stpierre has left #openstack-meeting-415:58
odyssey4me:p15:59
cloudnullit has been a long time15:59
*** ativelkov has left #openstack-meeting-415:59
*** Sam-I-Am has joined #openstack-meeting-415:59
hughsaundersyar, but apparently people are scheming to fix that16:00
b3rnard0#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Jan 22 16:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is b3rnard0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
*** KLevenstein has joined #openstack-meeting-416:00
*** rosmaita has left #openstack-meeting-416:00
cloudnullso hey everybody16:00
Sam-I-Amhi16:01
b3rnard0#topic RollCall16:01
*** openstack changes topic to "RollCall (Meeting topic: OpenStack Ansible Meeting)"16:01
mattt\o16:01
Sam-I-Amhere16:01
palendaeHello16:01
b3rnard0#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible16:01
odyssey4meo/16:01
cloudnullpresent16:01
hughsaunders\o16:01
andymccr\o16:01
sigmavirus24present16:01
d34dh0r53pre sent16:01
palendaepresent16:01
klamathhere16:01
cfarquharpresent16:01
hughsaundersgit-harry: present16:02
b3rnard0#topic The state of "10.1.2" and "9.0.6", loggin, bugs, ect. - (cloudnull)16:02
*** openstack changes topic to "The state of "10.1.2" and "9.0.6", loggin, bugs, ect. - (cloudnull) (Meeting topic: OpenStack Ansible Meeting)"16:02
*** scarlisle has joined #openstack-meeting-416:02
mancdazpresent16:02
*** briancurtin has joined #openstack-meeting-416:02
cloudnulllooks like I need "apell".16:02
*** evgenyf has quit IRC16:02
cloudnull^see16:03
cloudnullso odyssey4me andymccr , how are we looking towards getting logging all happy ?16:03
*** ivasilevskaya has left #openstack-meeting-416:03
andymccri think the main work that was required has gone in already - courtesy of odyssey4me16:03
andymccrso we should be fine.16:04
b3rnard0#link https://bugs.launchpad.net/openstack-ansible/+bug/139937116:04
odyssey4mecloudnull: one patch left before it's all hunky dorey - https://review.openstack.org/#/c/148623/16:04
odyssey4meessentially the only bit left is that for some reason the swift logs aren't coming through properly - the rsyslog container doesn't send them... I'm still trying to figure out the problem there16:05
cloudnullodyssey4me: is that something that maybe d34dh0r53  can help out with ?16:05
andymccrodyssey4me: i'll look into that because i know i removed the rsyslog containers from being built on the swift storage hosts16:06
*** mestery has quit IRC16:06
odyssey4mesure - in truth anyone who has a working build can help to figure out what the cause is - once I know that it'll be easy to roll in the patch16:06
odyssey4meit may be an aio specific issue, in which case we can ignore it - but I could do with assistance to triage, thanks andymccr16:06
andymccrive got a build almost completed now16:07
andymccrso will be no problem16:07
b3rnard0#action andymccr to investigate why rsyslog container doesn't send swift logs issue16:07
odyssey4meok - we can sort that out before COB tomorrow then16:07
andymccre-z16:07
d34dh0r53let me know if I can assist as well16:07
cloudnullsweet.16:07
b3rnard0#action d34dh0r53 To help andymccr on rsyslog issue16:08
andymccri could use a coffee - milk, 1 sugar :D thanks d34dh0r5316:08
hughsaundershaha16:08
cloudnullso for our open bugs within 9.0.6.16:08
d34dh0r53:) on it's way, may be a little cold when it gets there16:08
b3rnard0#topic 9.0.616:09
*** openstack changes topic to "9.0.6 (Meeting topic: OpenStack Ansible Meeting)"16:09
cloudnullbetween mattt odyssey4me and mancdaz everything looks "in progress"16:09
cloudnullodyssey4me: logging should be good in 9.0.616:09
*** krykowski has quit IRC16:09
cloudnullbecause no swift?16:09
mancdazcloudnull yeah I backported the stuff that was tagged as a potential, after assessing if it was needed16:09
b3rnard0#link https://launchpad.net/openstack-ansible/+milestone/9.0.616:09
mancdazsome of those are outstanding16:09
odyssey4mecloudnull: yep, once I get a working aio on 9.x I'll test all the logging patches and submit them16:10
odyssey4menext week will be backport week, pretty much16:11
cloudnullodyssey4me: https://bugs.launchpad.net/openstack-ansible/+bug/1399387/comments/10 is that being broken out into multiple commits?16:11
cloudnullor will it stay as is?16:12
odyssey4mecloudnull: yes - that'll be reverted and submitted one at a time once openstack infra approves https://review.openstack.org/#/c/149305/16:12
cloudnullkk.16:12
odyssey4methat patch will allow me to patch both the icehouse and juno branches to a point where we have a working aio check on both those branches16:13
*** Apsu has joined #openstack-meeting-416:13
cloudnullsounds good.16:13
odyssey4methen we'll re-enable voting on those branches for the aio check16:13
cloudnullis there anything that is presently in 9.0.6 that needs to have the state changed?16:14
*** krykowski has joined #openstack-meeting-416:14
*** Mudpuppy has joined #openstack-meeting-416:15
cloudnulllike i said, thats a lot of in progress for only one week till release?16:15
cloudnullok16:15
cloudnullon to 10.1.216:15
b3rnard0#topic 10.1.216:16
*** openstack changes topic to "10.1.2 (Meeting topic: OpenStack Ansible Meeting)"16:16
b3rnard0#link https://launchpad.net/openstack-ansible/+milestone/10.1.216:16
mancdazlots of things16:16
cloudnullwhats pressing there? does anyone need help on working these issues?16:16
mancdazI need help in getting the cherry-pick backports approved16:16
matttw/ 9.0.6, some of those in progress are actually fix committed no ?16:17
odyssey4memancdaz I've got your back there.16:17
cloudnullmattt, i assume yes. but i guess we'll have to go through and figure that out16:17
matttcloudnull: i looked at one and it's been merged into icehouse, so that list may not be accurate16:18
mancdazit's the wau lauinchpad tracks the status16:18
odyssey4memattt possibly - we can verify next week I guess16:18
mancdazit's why I wanted to talk about how we do that in launchpad16:18
cloudnullmancdaz we'll get to that .16:18
* mancdaz nods16:18
cloudnullso , with 10.1.2 we need to do lots of backporting . but beyond that everything else looks to be good, right?16:19
mancdazI can go through that list and see if anything targetted for a series has actually merged, even if the bug shows in progress16:19
cloudnullkk thanks mancdaz . we'll need to do that for 9.0.6 an 10.1.216:20
cloudnulli can help out with that too.16:20
b3rnard0#action mancdaz To go through that list and see if anything targetted for a series has actually merged, even if the bug shows in progress (9.0.6 & 10.1.2)16:20
odyssey4mecloudnull: should be fine - essentially we just need people to actually test the build over and over again16:20
mancdazthere's actually not that many juno outstanding with the backport tag16:20
mancdazI did most of the backports last week16:20
mancdazjust need them to be approved/reviewed16:21
odyssey4meonce the aio check is fixed then it'll be automatically tested in principle per commit, which will help16:21
b3rnard0#action cloudnull To help mancdaz with merging help16:21
mancdazwe need help with that help16:21
cloudnullhaha16:21
b3rnard0#topic Prioritizing the "next" milestone for 10.x and 9.x. - (cloudnull)16:22
*** openstack changes topic to "Prioritizing the "next" milestone for 10.x and 9.x. - (cloudnull) (Meeting topic: OpenStack Ansible Meeting)"16:22
cloudnullwe've got quite a few items in the "next" milestone.16:22
cloudnulllink https://launchpad.net/openstack-ansible/+milestone/next16:22
b3rnard0#link https://launchpad.net/openstack-ansible/+milestone/next16:23
cloudnulli'd like to see if we can prioritize them for what will be 10.1.3 and 9.0.716:23
*** salv-orlando has quit IRC16:23
cloudnullstarting with what will be a hot topic item , "F5 Pool Monitoring in Kilo"16:24
cloudnullpresently the f5 monitoring script uses xml for token parsing ,16:24
*** banix has quit IRC16:24
cloudnullthis is gone come kilo.16:24
b3rnard0#link https://bugs.launchpad.net/bugs/139938216:24
cloudnulli'd like to see if we can do something better/different  .16:25
cloudnullApsu: you worked on that, any insight ?16:25
odyssey4mesurely this belong in the set of things which need to be extracted from the generalised open build, as it's specific to the rax deployments16:25
Apsucloudnull: Life is hard trying to process data on an F5, given the CPU limitations and poor forking performance16:26
ApsuSo making use of JSON will be interesting. Also the python version is quite old.16:26
mancdazsome service that runs on the host and checks status locally? It's how galera recommend it's done16:26
mancdazthe f5 then only needs to do a standard http keyword check16:26
ApsuMight look into jshon, if we're still going to do API level checks16:26
cloudnullodyssey4me, it is true that rax does use f5 but that is not specific to rax, anyone that uses an f5 will not be able to in short order.16:26
ApsuAt least as far as pool monitoring based on API availability/modest authenticated requests16:27
cloudnullApsu can we spike within the next milestone to see how we make that better?16:28
ApsuSure.16:28
cloudnulli know that its a wishlist item, but it will be something that we/the project is going to have to deal with sooner than later.16:28
ApsuI'll see about statically-compiled jshon in case it's a quick win and we can parse JSON from the bash script directly16:28
palendaeA thing I'll toss out - does that check have to be done on the F5?16:28
ApsuShould incur the least penalty and not require a custom python version or such16:29
mancdazpalendae yeah that's what I was saying16:29
Sam-I-Ampalendae: i was typing the same question16:29
ApsuWe should definitely look into not16:29
palendaeGiven the limitations, would it be easier to move that monitoring action?16:29
b3rnard0#action Apsu Spike on F5 monitoring16:29
Sam-I-Amvoluntold16:29
ApsuThe F5 needs to know, but it doesn't have to be the place that does token procurement.16:29
mancdazthe f5 can do  a dumb poll, the results of which are generated by a more complex monitor on the host16:29
palendaeCool16:29
d34dh0r53I don't really like the idea of the F5 doing anything other than port level monitoring either16:29
palendae^16:29
Sam-I-Amd34dh0r53: ding16:29
palendaeDoesn't sound like anyone does16:30
ApsuWell that depends on what level of LB intelligence we want.16:30
*** banix has joined #openstack-meeting-416:30
ApsuPort monitoring is great unless the API is spitting out 500s16:30
palendaeCan probably dig deeper later, but something to think about16:30
d34dh0r53Apsu: true that16:30
ApsuPort's open! but broken16:30
*** carl_baldwin has quit IRC16:30
ApsuAnyhow, I'll look into it16:30
cloudnullas for the rest of the wishlist items targeted for "next" , do we want to bring any of them in for the proposed 10.1.3 / 9.0.7 ?16:30
mancdazI actually don't care where the intelligence lives, except that clearly in this case we can't do what we want on the f5, so do it somewher else16:30
d34dh0r53Apsu: in it's current state the script is closing a lot of ports that are functioning correctly16:30
Apsud34dh0r53: That's unrelated to the concept of availability monitoring, just the particular way the script skeleton was filled out so far :P16:31
ApsuWill have that fixed up too, lol16:31
*** banix has quit IRC16:31
d34dh0r53Apsu: cool16:31
mancdazcloudnull as for other wishlist items, I doubt they'd make it into icehouse16:31
mancdazsince we are treating that as a maintenance branch/version now, right?16:32
*** zz_sabari is now known as sabari16:32
matttcloudnull: i'll probably work https://bugs.launchpad.net/openstack-ansible/+bug/1412762 into 10.1.316:32
cloudnullmancdaz we are.16:32
matttwe expose a whole bunch of non-function heat resource types which is a bit janky16:32
mattt*non-functional16:32
cloudnullkk . sounds good16:33
cloudnullif nobody has anything specifically that they want in, ill go through them and file them away accordingly.16:33
b3rnard0#action matt To backport https://bugs.launchpad.net/openstack-ansible/+bug/1412762 into 10.1.316:33
*** LosMyke has joined #openstack-meeting-416:34
*** sabari is now known as zz_sabari16:34
cloudnullok moving on.16:34
b3rnard0#action cloudnull To target greater than wishlist next bugs into future milestones16:34
b3rnard0#topic Triaging bugs, targeting at correct series, targeting series fixes at milestones - getting consensus on how we do it. mancdaz16:34
*** openstack changes topic to "Triaging bugs, targeting at correct series, targeting series fixes at milestones - getting consensus on how we do it. mancdaz (Meeting topic: OpenStack Ansible Meeting)"16:34
cloudnullmancdaz you have the floor .16:35
mancdazok so the way we file/triage/target bugs etc16:35
*** banix has joined #openstack-meeting-416:35
mancdazwhen a bug is first filed, it is auto targetted to trunk16:35
mancdazbut we often need to backport it to icehouse and juno, or just juno16:35
mancdazso what I tend to do is add the juno/trunk/icehouse series16:36
mancdazand then for the milestones, target the relevant series at that16:36
mancdaztrunk would never have a milestone, as we don't actually release anything from master16:36
mancdazI also see bugs being filed, and then a milestone being added to the default (trunk) series16:37
mancdazjust wanted to get consensus on how we do this16:37
mancdazand also at what point we actually target a bug16:37
mancdazie can I decide right now if something is going in to 10.1.2, or do we do the backport now, and later target a handful at a milestone16:37
mancdazI don't know the 'correct' way16:38
mancdazbut just as long as we're all doing it the same way16:38
mancdazam I making sense?16:38
mancdazexample of what I do: https://bugs.launchpad.net/openstack-ansible/+bug/140860816:39
odyssey4mefyi - if you follow the methodology outlined by mancdaz, then the openstack-infra will also auto-update the bug status when your patch merges16:39
mancdazonly for trunk odyssey4me16:39
cloudnullimo once its fixed in trunk it should be backported to its appropriate series.16:40
mancdazwe have to manually change the status of the series16:40
mancdazcloudnull yeah I'm not arguing about wherther we sdhould backport or not16:40
mancdazjust how we track it in launchapd16:40
cloudnulli would think that if the item was fixed outside of the already set milestone, as long as its not a new feature, it should be it should be added to the upcoming milestone.16:41
cloudnulland that would be tracked as such within launchpad.16:42
odyssey4mecloudnull: the advatnage of adding the series is that you can target the series to the particular milestone16:43
odyssey4merather than the trunk fix to a milestone, which means you can't target two milestones16:43
odyssey4meie 9.0.x and 10.0.x16:43
mancdazok so look at my example versus this one https://bugs.launchpad.net/openstack-ansible/+bug/140202816:43
mancdazthis was not targeted to a series16:43
mancdazbut the fix was against trunk16:44
cloudnullah, i see now what you're talking about.16:44
cloudnulli like the mancdaz.16:44
mancdazit was targeted at a milestone for the trunk16:44
mancdazin the way I've been doing it, you'd never target the trunk fix at a milestone, only the series16:45
mancdazas that's where we release16:45
cloudnullso, as we triage issues, add series target to milestone .16:45
cloudnulli like it16:45
b3rnard0do we have agreement on this issue?16:45
hughsaundersgot that #agreed ready b3rnard0?16:45
mancdaz(also please add appropriate backport-potential tags tags)16:46
* odyssey4me likes it - milestones targeted at series makes the backporting tracking easier16:46
mancdazthen release manager can come along and work through the backports16:46
cloudnullthis is what we get for letting b3rnard0 chair a meeting...16:46
cloudnullall opposed ?16:46
Apsucloudnull: It's because he has that standing desk. If he had an actual chair, we'd be golden16:46
b3rnard0#startvote16:47
openstackUnable to parse vote topic and options.16:47
cloudnullthe motion passes...16:47
cloudnullmoving on .16:47
d34dh0r53The eyes have it16:47
hughsaundersaye16:47
b3rnard0#agreed triage issues, add series target to milestone16:47
b3rnard0#topic Airing of grievances16:47
*** openstack changes topic to "Airing of grievances (Meeting topic: OpenStack Ansible Meeting)"16:47
mancdazjust make sure you also add trunk, as otherwise it looks weird16:47
cloudnullso . do we have anything that anyone wants to talk about regarding the project?16:48
cloudnullwe didnt have too many agenda items16:48
cloudnullso i thought it would be nice to open it up to folks if they wanted to discus something.16:49
cloudnulland had neglected to add an agenda item.16:49
toxickCan we skip to the Feats of Strenght?16:49
Apsucloudnull: I've got a lot of problems with you people.16:49
d34dh0r53lol16:49
palendaeThe de-raxification is saved for 'next' correct?16:49
palendaeWhich is the first step in galaxification16:50
Sam-I-Ampalendae: kilo, i think16:50
cloudnullmoving on to the feats of strength16:50
ApsuLog Toss competitors, form a line on the left16:50
cloudnullhowever irc wrestling may be tough.16:50
cloudnullok. if nothing then moving on.16:51
b3rnard0#topic More on genericising deployment roles and code. - (cloudnull)16:51
cloudnulllets move to generizing things for the last 10 minutes16:51
*** openstack changes topic to "More on genericising deployment roles and code. - (cloudnull) (Meeting topic: OpenStack Ansible Meeting)"16:51
cloudnullwhich opens up to palendae16:51
*** sbalukoff has quit IRC16:52
*** cfarquhar has quit IRC16:52
cloudnullso far the plan has been that we will not target 10 or 9 for the removal of the rax bits, moving to kilo will be the first release that has rax bits stripped16:52
palendaeI was more asking about what we decided last time - we had deferred to next16:52
cloudnullwhich will also include the roles as made galaxy compatible though all within the same structure.16:53
cloudnullas we progress through the making of our stack more generic, we will hopfully get to the point where the roles become separate repos.16:54
odyssey4mecloudnull: and using external galaxy roles for infrastructure (non-openstack) where applicable and possible, I guess?16:54
cloudnullodyssey4me: i'd like to say yes, though from what I've seen so far that may be difficult.16:55
cloudnullgranted i've not look everywhere.16:55
ApsuMay be room to improve the existing ones, then.16:55
cloudnulldefinitely .16:56
ApsuMerge in our work to improve both user communities16:56
cloudnullthe rack_roles have been labeled as "abandon ware" so we could try to pick up where they left off or move to other role maintainers.16:57
cloudnullbut i like the idea of being able to consume external roles.16:57
palendaecloudnull: So the os_cloud repo's going to remain as a sketch?16:57
palendaeAnd I'd agree that long term upstream galaxy roles would be great, but I think we'd have to participate in contribs/maintenance then, too16:58
cloudnullas soon as we extract juno from master into the branches ill put through a collapsed pr as WIP.16:58
*** jpmontez has joined #openstack-meeting-416:58
palendaecloudnull: Of all the roles getting split out?16:58
palendaeIt sounded like there was some resistance to that16:59
palendaeSince it's one big chunk16:59
cloudnullpresently it would be a big chunk.17:00
*** dboik has quit IRC17:00
cloudnulllets move this convo into the channel because we're out of time.17:00
hughsaundersit may be impractical to have a stackforge repo for every role, at least immediately - that was my resistance. But I like the idea of using galaxy roles17:00
palendaeok17:00
Sam-I-Amgood meeting y'all17:00
odyssey4medon't forget to end the meeting :)17:00
b3rnard0#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Jan 22 17:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
*** Sam-I-Am has left #openstack-meeting-417:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-22-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-22-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-22-16.00.log.html17:00
*** odyssey4me has left #openstack-meeting-417:01
*** toxick has left #openstack-meeting-417:01
*** krykowski has quit IRC17:01
*** Mudpuppy has left #openstack-meeting-417:01
*** andymccr has left #openstack-meeting-417:02
*** d34dh0r53 has left #openstack-meeting-417:02
*** cloudnull has left #openstack-meeting-417:03
*** IRTermite has joined #openstack-meeting-417:04
*** mestery has joined #openstack-meeting-417:06
*** KLevenstein has left #openstack-meeting-417:08
*** igordcard has quit IRC17:10
*** matrohon has quit IRC17:16
*** banix has quit IRC17:17
*** banix has joined #openstack-meeting-417:18
*** salv-orlando has joined #openstack-meeting-417:24
*** mestery has quit IRC17:25
*** mestery has joined #openstack-meeting-417:25
*** zz_sabari is now known as sabari17:27
*** salv-orlando has quit IRC17:30
*** emagana has joined #openstack-meeting-417:32
*** SumitNaiksatam has quit IRC17:32
*** belmoreira has quit IRC17:41
*** banix has quit IRC17:50
*** david-lyle has joined #openstack-meeting-417:50
*** SumitNaiksatam has joined #openstack-meeting-417:54
*** belmoreira has joined #openstack-meeting-417:58
*** s3wong has joined #openstack-meeting-417:58
*** dboik has joined #openstack-meeting-418:00
*** banix has joined #openstack-meeting-418:01
*** sabari is now known as zz_sabari18:02
*** dboik has quit IRC18:05
*** yamahata has quit IRC18:24
*** jpmontez has quit IRC18:25
*** emagana has quit IRC18:26
*** emagana has joined #openstack-meeting-418:27
*** emagana has quit IRC18:28
*** emagana has joined #openstack-meeting-418:28
*** carl_baldwin has joined #openstack-meeting-418:39
*** sbalukoff has joined #openstack-meeting-418:47
*** dboik has joined #openstack-meeting-418:47
*** SridharRamaswamy has joined #openstack-meeting-418:52
*** zz_sabari is now known as sabari18:56
*** igordcard has joined #openstack-meeting-419:04
*** salv-orlando has joined #openstack-meeting-419:04
*** ivar-laz_ has joined #openstack-meeting-419:05
*** salv-orlando has quit IRC19:06
*** salv-orlando has joined #openstack-meeting-419:06
*** jpmontez has joined #openstack-meeting-419:21
*** jpmontez has quit IRC19:25
*** igordcard has quit IRC19:30
*** igordcard has joined #openstack-meeting-419:31
*** igordcard has quit IRC19:43
*** igordcard has joined #openstack-meeting-419:43
*** carl_baldwin has quit IRC19:45
*** jpmontez has joined #openstack-meeting-419:46
*** carl_baldwin has joined #openstack-meeting-419:46
*** carl_baldwin has quit IRC19:46
*** kobis has joined #openstack-meeting-419:47
*** kobis has quit IRC19:49
*** ivar-laz_ has quit IRC19:50
*** dboik_ has joined #openstack-meeting-419:51
*** dboik has quit IRC19:51
*** ivar-lazzaro has joined #openstack-meeting-419:51
*** dboik_ has quit IRC19:52
*** ivar-lazzaro has quit IRC19:52
*** dboik has joined #openstack-meeting-419:52
*** jpmontez has left #openstack-meeting-419:52
*** ivar-lazzaro has joined #openstack-meeting-419:52
*** salv-orlando has quit IRC19:53
*** banix has quit IRC19:56
*** kobis has joined #openstack-meeting-419:59
*** emagana has quit IRC20:00
*** banix has joined #openstack-meeting-420:06
*** sarob has joined #openstack-meeting-420:18
*** rfolco has quit IRC20:19
*** emagana has joined #openstack-meeting-420:21
*** sabari is now known as zz_sabari20:23
*** ivar-lazzaro has quit IRC20:29
*** matrohon has joined #openstack-meeting-420:29
*** ivar-lazzaro has joined #openstack-meeting-420:31
*** salv-orlando has joined #openstack-meeting-420:35
*** salv-orlando has quit IRC20:36
*** igordcard has quit IRC20:36
*** salv-orlando has joined #openstack-meeting-420:36
*** igordcard has joined #openstack-meeting-420:37
*** sigmavirus24 is now known as sigmavirus24_awa20:40
*** mattt has left #openstack-meeting-420:54
*** belmoreira has quit IRC20:54
*** belmoreira has joined #openstack-meeting-420:54
*** kobis has quit IRC20:58
*** dboik has quit IRC20:58
*** dboik has joined #openstack-meeting-420:58
*** kobis has joined #openstack-meeting-420:59
*** belmoreira has quit IRC20:59
*** salv-orlando has quit IRC21:01
*** salv-orlando has joined #openstack-meeting-421:04
*** zz_sabari is now known as sabari21:05
*** emagana has quit IRC21:06
*** emagana has joined #openstack-meeting-421:06
*** emagana has quit IRC21:11
*** kobis has quit IRC21:12
*** emagana has joined #openstack-meeting-421:24
*** ja_ has quit IRC21:25
*** ChuckC_ has quit IRC21:36
*** ChuckC_ has joined #openstack-meeting-421:36
*** banix has quit IRC21:40
*** pmesserli has left #openstack-meeting-421:42
*** banix has joined #openstack-meeting-421:47
*** banix has quit IRC21:49
*** ChuckC_ has quit IRC21:49
*** ChuckC_ has joined #openstack-meeting-421:50
*** ChuckC_ has quit IRC21:53
*** ChuckC_ has joined #openstack-meeting-421:54
*** emagana has quit IRC22:07
*** emagana has joined #openstack-meeting-422:08
*** emagana has quit IRC22:09
*** emagana has joined #openstack-meeting-422:09
*** emagana has quit IRC22:14
*** emagana has joined #openstack-meeting-422:15
*** salv-orlando has quit IRC22:17
*** emagana has quit IRC22:20
*** matrohon has quit IRC22:24
*** sabari has left #openstack-meeting-422:25
*** emagana has joined #openstack-meeting-422:31
*** emagana has quit IRC22:36
*** emagana has joined #openstack-meeting-422:45
*** ChuckC has joined #openstack-meeting-422:47
*** ChuckC_ has quit IRC22:48
*** emagana has quit IRC22:50
*** salv-orlando has joined #openstack-meeting-422:55
*** salv-orlando has quit IRC22:56
*** salv-orlando has joined #openstack-meeting-422:56
*** jemangs has quit IRC23:05
*** jemangs has joined #openstack-meeting-423:08
*** klamath has quit IRC23:11
*** dboik_ has joined #openstack-meeting-423:18
*** dboik has quit IRC23:21
*** dboik_ has quit IRC23:22
*** emagana has joined #openstack-meeting-423:25
*** watanabe_isao has joined #openstack-meeting-423:26
*** briancurtin has quit IRC23:41
*** briancurtin has joined #openstack-meeting-423:41
*** banix has joined #openstack-meeting-423:45
*** briancurtin has quit IRC23:49
*** david-lyle is now known as david-lyle_afk23:56
*** banix has quit IRC23:56
*** banix has joined #openstack-meeting-423:57
*** banix has quit IRC23:59

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