Thursday, 2015-02-12

*** emagana has quit IRC00:02
*** markvoelker has quit IRC00:03
*** emagana has joined #openstack-meeting-400:08
*** VW_ has joined #openstack-meeting-400:11
*** emagana has quit IRC00:12
*** SridharRamaswamy has joined #openstack-meeting-400:14
*** emagana has joined #openstack-meeting-400:26
*** banix has quit IRC00:27
*** VW_ has quit IRC00:30
*** banix has joined #openstack-meeting-400:35
*** sballe__ has quit IRC00:37
*** markvoelker has joined #openstack-meeting-400:52
*** banix has quit IRC00:55
*** VW_ has joined #openstack-meeting-400:55
*** markvoelker has quit IRC00:57
*** markvoelker has joined #openstack-meeting-400:59
*** banix has joined #openstack-meeting-401:01
*** ChuckC has quit IRC01:02
*** ChuckC has joined #openstack-meeting-401:03
*** markvoelker has quit IRC01:04
*** banix has quit IRC01:25
*** Aish has quit IRC01:26
*** banix has joined #openstack-meeting-401:31
*** banix has quit IRC01:32
*** sarob has quit IRC01:36
*** sarob has joined #openstack-meeting-401:38
*** markvoelker has joined #openstack-meeting-401:40
*** sarob has quit IRC01:43
*** sigmavirus24 is now known as sigmavirus24_awa01:43
*** ChuckC_ has joined #openstack-meeting-401:46
*** watanabe_isao has quit IRC01:47
*** ChuckC has quit IRC01:49
*** mwang2_ has quit IRC01:55
*** dannywilson has quit IRC01:58
*** dannywilson has joined #openstack-meeting-401:58
*** SridharRamaswamy has quit IRC02:00
*** VW_ has quit IRC02:01
*** watanabe_isao has joined #openstack-meeting-402:07
*** VW_ has joined #openstack-meeting-402:08
*** salv-orlando has quit IRC02:15
*** banix has joined #openstack-meeting-402:19
*** VW_ has quit IRC02:23
*** dannywilson has quit IRC02:23
*** sarob has joined #openstack-meeting-402:39
*** sarob has quit IRC02:44
*** cgoncalv1s has joined #openstack-meeting-402:47
*** cgoncalves has quit IRC02:52
*** emagana has quit IRC02:53
*** Aish has joined #openstack-meeting-402:53
*** emagana has joined #openstack-meeting-402:54
*** jckasper has joined #openstack-meeting-402:57
*** emagana has quit IRC02:58
*** david-lyle is now known as david-lyle_afk02:59
*** yamahata has quit IRC03:06
*** salv-orlando has joined #openstack-meeting-403:16
*** VW_ has joined #openstack-meeting-403:17
*** salv-orlando has quit IRC03:21
*** sarob has joined #openstack-meeting-403:29
*** evgenyf has joined #openstack-meeting-403:30
*** evgenyf has quit IRC03:34
*** salv-orlando has joined #openstack-meeting-403:36
*** salv-orlando has quit IRC03:40
*** salv-orlando has joined #openstack-meeting-403:41
*** yamahata has joined #openstack-meeting-403:53
*** salv-orlando has quit IRC03:57
*** salv-orlando has joined #openstack-meeting-404:01
*** salv-orlando has quit IRC04:05
*** VW_ has quit IRC04:06
*** VW_ has joined #openstack-meeting-404:08
*** fnaval has quit IRC04:33
*** salv-orlando has joined #openstack-meeting-404:37
*** ivar-lazzaro has quit IRC04:38
*** salv-orlando has quit IRC04:41
*** fnaval has joined #openstack-meeting-404:48
*** salv-orlando has joined #openstack-meeting-404:59
*** salv-orlando has quit IRC05:02
*** salv-orlando has joined #openstack-meeting-405:05
*** VW_ has quit IRC05:08
*** sarob has quit IRC05:09
*** bobmel_ has joined #openstack-meeting-405:11
*** salv-orlando has quit IRC05:12
*** bobmel has quit IRC05:14
*** banix has quit IRC05:15
*** salv-orlando has joined #openstack-meeting-405:15
*** Aish has left #openstack-meeting-405:19
*** VW_ has joined #openstack-meeting-405:27
*** sarob has joined #openstack-meeting-405:28
*** salv-orlando has quit IRC05:30
*** sarob has quit IRC05:32
*** VW_ has quit IRC05:39
*** salv-orlando has joined #openstack-meeting-405:40
*** carl_baldwin has joined #openstack-meeting-405:46
*** salv-orlando has quit IRC05:52
*** carl_baldwin has quit IRC06:04
*** salv-orlando has joined #openstack-meeting-406:08
*** salv-orlando has quit IRC06:15
*** salv-orlando has joined #openstack-meeting-406:16
*** numan has joined #openstack-meeting-406:18
*** salv-orlando has quit IRC06:18
*** salv-orlando has joined #openstack-meeting-406:21
*** salv-orlando has quit IRC06:25
*** radek has joined #openstack-meeting-406:40
*** salv-orlando has joined #openstack-meeting-406:49
*** fnaval has quit IRC06:52
*** fnaval has joined #openstack-meeting-406:52
*** salv-orlando has quit IRC06:56
*** fnaval has quit IRC06:56
*** pkoniszewski has joined #openstack-meeting-407:01
*** sarob has joined #openstack-meeting-407:30
*** sarob has quit IRC07:34
*** bobmel_ has quit IRC07:48
*** bobmel_ has joined #openstack-meeting-407:48
*** numan has quit IRC07:48
*** numan has joined #openstack-meeting-407:48
*** pkoniszewski has quit IRC07:49
*** pkoniszewski has joined #openstack-meeting-407:49
*** salv-orlando has joined #openstack-meeting-408:11
*** wojdev has joined #openstack-meeting-408:17
*** watanabe_isao has quit IRC08:43
*** matrohon has joined #openstack-meeting-408:46
*** evgenyf has joined #openstack-meeting-409:00
*** kobis has joined #openstack-meeting-409:18
*** jckasper has quit IRC09:22
*** mwang2 has joined #openstack-meeting-409:27
*** mwang2 has quit IRC09:32
*** wojdev has quit IRC09:51
*** wojdev has joined #openstack-meeting-409:51
*** salv-orlando has quit IRC10:53
*** rfolco has joined #openstack-meeting-410:55
*** yamahata has quit IRC10:59
*** kobis has quit IRC11:25
*** salv-orlando has joined #openstack-meeting-411:27
*** markvoelker has quit IRC11:34
*** asselin__ has quit IRC11:52
*** kobis has joined #openstack-meeting-412:08
*** wojdev has quit IRC12:28
*** salv-orlando has quit IRC12:29
*** markvoelker has joined #openstack-meeting-412:35
*** markvoelker has quit IRC12:40
*** kobis has quit IRC12:51
*** kobis has joined #openstack-meeting-412:51
*** markvoelker has joined #openstack-meeting-412:59
*** galstrom_zzz is now known as galstrom13:01
*** jckasper has joined #openstack-meeting-413:02
*** salv-orlando has joined #openstack-meeting-413:03
*** markvoelker has quit IRC13:05
*** jckasper has quit IRC13:10
*** jckasper has joined #openstack-meeting-413:10
*** kobis has quit IRC13:25
*** kobis has joined #openstack-meeting-413:25
*** abhishekk has joined #openstack-meeting-413:34
*** wojdev has joined #openstack-meeting-413:34
*** klamath has joined #openstack-meeting-413:38
*** klamath has quit IRC13:38
*** klamath has joined #openstack-meeting-413:39
*** galstrom is now known as galstrom_zzz13:39
*** wojdev has quit IRC13:44
*** ativelkov has joined #openstack-meeting-413:50
*** rosmaita has joined #openstack-meeting-413:57
*** jokke__ has joined #openstack-meeting-413:57
*** jokke__ is now known as jokke_13:57
*** kobis has quit IRC13:57
*** lakshmiS has joined #openstack-meeting-413:58
*** kobis has joined #openstack-meeting-413:58
nikhil_k#startmeeting Glance14:00
openstackMeeting started Thu Feb 12 14:00:00 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
jokke_o/14:00
ativelkovo/14:00
abhishekko/14:00
mfedosino/14:00
rosmaitao/14:00
lakshmiSo/14:00
nikhil_khttps://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
zhiyano/14:00
nikhil_kWelcome all, good morning, afternoon, evening to all in resp. TZ!14:00
*** sigmavirus24_awa is now known as sigmavirus2414:01
rosmaitazhiyan: hope you are feeling better!14:01
sigmavirus24o/14:01
nikhil_kLet's get the party started14:01
*** ivasilevskaya has joined #openstack-meeting-414:01
nikhil_k#topic Abandoning stale PS from review14:01
*** openstack changes topic to "Abandoning stale PS from review (Meeting topic: Glance)"14:01
nikhil_kwas that you jokke_ ?14:01
jokke_Yup14:01
*** cgoncalv1s is now known as cgoncalves14:01
zhiyanrosmaita: thanks! I'm better now.14:01
nikhil_kjokke_: please take over14:02
jokke_I would like to adopt the principle some other projects like Nova is using14:02
*** TravT_ has joined #openstack-meeting-414:02
jokke_so if PS has been inactive for 3 weeks + we just abandon it to keep the review list clean and fresh14:02
jokke_I think we have at the moment year(s) old changes still on the list14:02
nikhil_kshould we get a vote here and then take to ML if necessary?14:03
mfedosinhm, before I would say it's a bad idea, but now, when we have lots of active reviewers I'm okay with it14:03
*** wayne_ has joined #openstack-meeting-414:04
jokke_mfedosin: ok let me refrase a bit ... lets say there is change that has bunch of -1 and the author just has not acted on those, so effectively already abandoned the change14:04
sigmavirus24jokke_: right, I think that's something that needed to be clarified14:05
jokke_If the change has 5 +1 and +2 we're not gonna drop it just because last activity was 21 days14:05
ativelkovso, not just inacative, but inactive with negative feedback or broken tests, right?14:05
jokke_but taking this on would help us to identify those changes that would be ready & good to go in14:05
pkoniszewskio/14:05
sigmavirus24ativelkov: I think negative review is enough14:05
sigmavirus24Passing tests don't mean very much if no one wants the change :)14:05
nikhil_kativelkov: yes, only with a -1 (though even from jenkins)14:06
jokke_ativelkov: yeah I think either one of those would be good enough trigger14:06
jokke_nikhil_k: well formatted!14:06
nikhil_kalso, I think we can do this on Glance but not on some repos like glance-specs14:06
sigmavirus24jokke_: I'm wondering about changes with a bunch of +1s during which Jenkins was broken and no one rechecked them14:06
nikhil_k(as some specs would mean carry over to next cycle and will sit for a more than 3 weeks in some cases)14:07
jokke_sigmavirus24: if author does not care enough to recheck the change in 3 weeks, I think it's good to drop ... specially when the owner can revive any abandone change later on if needed14:07
jokke_nikhil_k: yes, I think -spec is special cupcake anyways14:08
*** salv-orlando has quit IRC14:08
ativelkovYes, and this should not happen during freezes: if we are close to release, some changes may lack attention for some time14:08
jokke_sigmavirus24: or anyone else in that matter14:08
*** salv-orlando has joined #openstack-meeting-414:08
TravT_3 weeks seems slightly short.  is that what all the other projects did?14:09
jokke_ativelkov: ++ I think this needs bit of game eye on holiday seasons, around freeze etc.14:09
nikhil_kativelkov: hmm, good point14:09
TravT_i was just thinking of holiday14:09
mfedosinand why exactly 21 days or not 28 or 14?14:09
sigmavirus24Yeah I think an etherpad detailing the exact procedure should be the next step and have it sent to the ML? I think everyone here is in favor14:09
kragnizo/14:09
ativelkovmfedosin: cause 21 is 3x7, and 3+10 is 10, which is cool14:09
jokke_I'm not proposing that we will do automated script or anything like that, but this would be just mandate for cores to clean up the list for those oldies no-one seems to care about14:09
sigmavirus24We're all just nitpicking the details and finer mechanics so that's better suited for the ML14:10
nikhil_kheh, I think that is probably a rythm within openstack of 3 weeks14:10
*** VW_ has joined #openstack-meeting-414:10
mfedosinfast rhythm btw14:11
nikhil_kjokke_: sigmavirus24 : ok, how about a email is sent to the ML and we announce a reminder in next weeks meeting for all those interested to respond accordingly14:11
mfedosinokay, I don't mind just was a little bit curious14:11
nikhil_kmfedosin: so, we've 6 weeks long intermediate milestones14:11
jokke_nikhil_k: will try to get the etherpad/e-mail out there today or tomorrow latest14:11
nikhil_k(like k-1, k2, etc.)14:12
nikhil_kjokke_: Thanks!14:12
sigmavirus24#action jokke_ to put together an etherpad and send a message to the mailing list14:12
nikhil_ksigmavirus24: thanks, was just about to :)14:12
zhiyanjokke_: i think automated script is better...14:12
sigmavirus24=P14:12
jokke_mfedosin: consistency14:12
*** pennerc has joined #openstack-meeting-414:13
*** salv-orlando has quit IRC14:13
pkoniszewskiNova abandons  patches that are >4 weeks old, maybe we should keep the same time14:13
TravT_btw is it 3 weeks since patch submitted or 3 weeks since first negative review?14:13
jokke_pkoniszewski: is it 4?14:13
jokke_TravT_: last activity14:13
pkoniszewskiit is 4, e.g., https://bugs.launchpad.net/nova/+bug/1246201/comments/2214:13
openstackLaunchpad bug 1246201 in OpenStack Compute (nova) "Live migration fails when the instance has a config-drive" [High,In progress] - Assigned to Tony Breeds (o-tony)14:13
mfedosinTravT_, from las activity I suppose14:13
ativelkovTravT_: since the last owner's activity14:13
mfedosin*last14:13
sigmavirus24Can we move on?14:14
jokke_pkoniszewski: ok, thanks for catching that, 4 weeks it would be then ;)14:14
nikhil_kauthor's or committer's ?14:14
nikhil_kso, let's drill down on the details in the etherpad14:14
jokke_yes14:14
jokke_move on please14:14
nikhil_k#topic CLI Sorting Argument Guidelines14:14
*** openstack changes topic to "CLI Sorting Argument Guidelines (Meeting topic: Glance)"14:14
nikhil_khttps://review.openstack.org/#/c/145544/14:14
mfedosinthey're approved and it's nice14:15
nikhil_kmfedosin: not yet14:15
nikhil_kfyi ^ , there is a api-wg spec that has been approved14:15
nikhil_kthat is - https://review.openstack.org/#/c/145579/14:15
nikhil_kso, for everyone to be on the look out for this change. Seems like it'd not affect anyone directly14:16
*** wojdev has joined #openstack-meeting-414:16
* ativelkov bookmarks to check if artifacts API complies with it14:16
nikhil_kbut we will be having some changes on the g-api side that would involve minor version bump14:16
jokke_There is no +A but looks pretty stronly that this will be the merging iteration of that spec ;)14:16
mfedosinI heard we need a spec in glance for this14:16
sigmavirus24At worst, the change that would affect people is allowing multiple sort-keys which is already in progress14:16
sigmavirus24mfedosin: I didn't get to it yesterday since I was trying to re-review the k-3 specs that are important14:17
nikhil_kmfedosin: yes, to document all the related links and the changes that would be made to Glance and the client14:17
mfedosinI can write it today14:17
sigmavirus24I'm also in meeting hell this morning but I can try to get to it this afternoon14:17
nikhil_kas those are not evident in that spec14:17
sigmavirus24Thanks mfedosin14:17
mfedosinsigmavirus24, welcome :)14:17
nikhil_kok, moving on. thanks for the input everyone14:18
nikhil_k#topic Cross-Repo Dependencies in Zuul14:18
*** openstack changes topic to "Cross-Repo Dependencies in Zuul (Meeting topic: Glance)"14:18
sigmavirus24#action mfedosin to write an sorting spec for changes in glance-api14:18
nikhil_khttp://osdir.com/ml/openstack-dev/2015-02/msg00785.html14:18
jokke_So just heads up for everyone who missed that e-mail in mailing list14:18
kragnizthis is so cool!14:18
ativelkovso, we may now set dependencies between commit to python-*client and API commit? Cool14:19
jokke_there is cross repo dependency mechanism introduced with "Depends-On: <Gerrit change ID>" on commit message14:19
zhiyanit's really great.14:19
nikhil_kI believe this is documented in the openstack infra manuals14:19
*** pennerc has quit IRC14:20
nikhil_k#link http://docs.openstack.org/infra/manual/developers.html#cross-project-dependencies14:20
jokke_ativelkov: yes, we can make dependency chains to have client change depending on glance change depending on glance_store change14:20
*** pennerc has joined #openstack-meeting-414:20
sigmavirus24I want to say we should all thank fungi but I know they didn't work on it alone14:20
mfedosinwow, I really need that14:20
nikhil_kSo, I would strongly encourage all developers and reviewers to look into the manual14:20
jokke_++14:20
fungii definitely did not ;)14:20
TravT_\o/14:20
nikhil_kfungi: woot!14:20
zhiyanfungi: :)14:21
fungijeblair did pretty much all of the implementation14:21
fungii merely reviewed most of it and nodded14:21
jokke_fungi: kudos for both of you ;)14:21
fungimmm, actually that documentation link is for the wrong thing i think14:21
fungicross-repo dependency is what we're calling the depends-on bits14:22
fungibut i may need to re-read the manual now14:22
fungiahh, yep, we cleaned that up, so it's the right thing now14:22
TravT_so it says "another project" can the same thing be used within a project (sometime dependencies aren't all lined up - multiple dependencies)14:22
nikhil_khuh, intersting14:22
jokke_TravT_: between any two repo14:23
sigmavirus24TravT_: isn't that the idea for dependent patches?14:23
sigmavirus24Why not just rebase your patch on the patch it depends on?14:23
nikhil_kfungi: ok, as I think it says cross project so was hoping that is all openstack wide and not confined to a program14:23
fungiright, within the same project just make them naturally dependent series within git14:23
sigmavirus24Also, this seem to be getting off topic14:23
jokke_nikhil_k: as said any two repo14:23
fungicross-repo dependencies using the depends-on line are for when you need dependencies between changes (either because you don't want one merging before the other, or want them to be tested together in some integration test suite)14:24
nikhil_kjokke_: I was just asking as he said earlier that it was wrong link14:24
TravT_patches aren't always necessarily sequential with multiple workstreams dependent on multiple patches14:24
jokke_nikhil_k: k14:24
fungibut specifically between different git repositories14:24
TravT_ok14:24
TravT_thx14:24
fungianyway, sorry to hijack14:24
jokke_TravT_: read the e-mail ... it's all expained there ;)14:24
* fungi gets back to his regularly-scheduled morning14:24
*** david-lyle_afk is now known as david-lyle14:25
nikhil_kfungi: thanks :)14:25
nikhil_k(for the info)14:25
nikhil_k#topic Liberty Summit planning14:25
*** openstack changes topic to "Liberty Summit planning (Meeting topic: Glance)"14:25
nikhil_kjokke_: ?14:25
kragnizwe didn't get any lizards :(14:25
jokke_So first of all ... we have name \\o \o/ o// o/714:25
sigmavirus24Yeah but it isn't the name we needed, it's the name we deserved14:25
nikhil_ksigmavirus24: lol, batman fan much?14:26
sigmavirus24=P14:26
jokke_second of all ... Should we kick off planning for the summit ... end of MAy will be sooner than anyone expects14:26
nikhil_kjokke_: I think we can wait until the end of cycle before we do that14:27
jokke_nikhil_k: any objections to make our well proven etherpad and start collecting stuff together to ease the planning and avoiding the last minute rush again?14:27
nikhil_kLike for juno we had enough time after j314:27
*** abhishekkk has joined #openstack-meeting-414:27
sigmavirus24Doesn't hurt to start the etherpad now14:27
nikhil_kjokke_: yes, but this time I am hoping that the feature / psedo feature groups would update the etherpad proactively14:28
nikhil_kI may send a reminder email every so often14:28
nikhil_ksigmavirus24: I think we've 2 already would like to avoid more14:28
jokke_sigmavirus24: that's what I thought and I noticed Doug was giving a shout for oslo one earlier so thought to bring it up14:28
sigmavirus24fair enough :)14:28
nikhil_k#info K3 etherpad https://etherpad.openstack.org/p/kilo-glance-k314:28
nikhil_kkragniz: do you have the whiteboard link handy?14:29
sigmavirus24https://etherpad.openstack.org/p/glance-whiteboard14:29
sigmavirus24#link https://etherpad.openstack.org/p/glance-whiteboard14:29
* sigmavirus24 steals kragniz's thunder14:29
kragnizsigmavirus24 beat me too it14:29
sigmavirus24nikhil_k: it's just a wafer thin etherpad, certainly it's okay (Monty Python reference)14:29
nikhil_k#info Whiteboard is not used for review priority, rather just for informal discussions14:29
*** abhishekk has quit IRC14:29
nikhil_ksigmavirus24: heh14:30
nikhil_k#topic glance_store Releases14:30
*** openstack changes topic to "glance_store Releases (Meeting topic: Glance)"14:30
nikhil_kwe are waiting on14:30
nikhil_khttps://review.openstack.org/#/c/141665/14:30
nikhil_kand14:31
nikhil_khttps://review.openstack.org/#/c/137416/14:31
zhiyanhttps://review.openstack.org/#/c/137416/ just get +Aed14:31
sigmavirus24zhiyan: excellent. I was wondering when we'd ever get that approved =P14:31
nikhil_knice!14:31
nikhil_kzhiyan: please update the blueprint status accordingly14:32
zhiyanhowever, i'm not sure if i can put https://review.openstack.org/#/c/136039/ on the list as the latest (to me) one14:32
nikhil_kappreciate the effort there14:32
zhiyannikhil_k: sure14:32
*** krykowski has joined #openstack-meeting-414:32
nikhil_k#info try to review https://review.openstack.org/#/c/136039/ before next Tuesday else it will be postponed to next glance_store release14:32
zhiyannikhil_k: thanks for review/support14:33
nikhil_k:)14:33
nikhil_k#topic client release14:33
*** openstack changes topic to "client release (Meeting topic: Glance)"14:33
kragniznikhil_k: so glance_store release is probably next tuesday?14:33
nikhil_khttps://launchpad.net/python-glanceclient/+milestone/v0.16.014:33
jokke_nikhil_k: so the plan is to release at 18th?\14:33
nikhil_kkragniz: hopefully, I deferrred it from this week to next to help reviewers relax a bit (right after k2)14:33
* kragniz updates whiteboard14:34
jokke_nikhil_k: good call also ref stable capping14:34
nikhil_kAbout the client: do we need to clean up the dependent bugs for the next release?14:35
kragnizdependant as in currently targeted for 0.16.0?14:36
nikhil_kSeems like no objections?14:36
*** abhishekk has joined #openstack-meeting-414:36
nikhil_k#info Nikhil to clean up bugs related to the client for it's next release. Please contact if you need something to be released urgently.14:36
nikhil_kAlso, is anyone willing to volunteer to verify if we've no change that makes api backward incompatible14:36
kragnizI can head up this one, since I think I was the last to complain about it14:37
jokke_nikhil_k: could you rephrase that ...14:37
nikhil_kjokke_: So, the concern that would brought up was..14:37
jokke_nikhil_k: sorry ... got you14:37
kragniz(mostly with semver stuff)14:37
nikhil_kwe need to ensure that the client releases need to be semantically correct14:37
jokke_ah14:38
kragnizwe don't *need* to, but it would be nice14:38
nikhil_kI'm trying to identify if there are enough who actually care about this (by that I mean are affect by this)14:38
sigmavirus24I care about this14:38
wayne_I posted this bug to the mailing list yesterday: https://review.openstack.org/#/c/154229/14:38
nikhil_kand you're affected?14:38
jokke_kragniz, nikhil_k: well tbh it's easier to do before rather than after they have been released14:38
*** abhishekkk has quit IRC14:38
nikhil_kwayne_: ok, we should get to it in the open discussion14:39
kragnizI also care about this14:39
kragnizjokke_: what do you mean?14:39
nikhil_kSo, all those who care about this -14:39
*** TravT_ has quit IRC14:39
nikhil_kare you all willing to ensure that the client release is tagged appropriately in the launchpad14:40
*** banix has joined #openstack-meeting-414:40
nikhil_kthat would involve creating a release for minor version change and tagging bugs to it14:40
kragniztotes14:40
*** TravT has joined #openstack-meeting-414:40
sigmavirus24yep14:40
jokke_kragniz: it's easier to fix some inconsistencies if we find them now rather than after they've been out for a one release already14:41
nikhil_kand if there are api back incompatible changes, then the release version is updated accordinly14:41
jokke_consistency vs. backwards compatibility14:41
kragniznikhil_k: we can update release names/versions on launchpad?14:41
kragnizI forget if you can change those14:41
kragnizor create a new one and retarget14:42
nikhil_kkragniz: it would be manual and tiresome process ( I believe) but not 100% on that14:42
sigmavirus24Launchpad has an API, but let us never speak of it14:42
*** pennerc has left #openstack-meeting-414:42
nikhil_kok, I will move on for now14:42
kragnizsigmavirus24: I had a look at it once14:42
kragniz...once14:42
sigmavirus24kragniz: never again14:42
nikhil_kLet's discuss this offline, with all those who have time for this14:42
kragniznikhil_k: sounds good14:42
nikhil_k#topic k2 released.14:43
*** openstack changes topic to "k2 released. (Meeting topic: Glance)"14:43
nikhil_kk2 released.14:43
nikhil_kcopy paste fail14:43
nikhil_khttps://bugs.launchpad.net/bugs/141280214:43
openstackLaunchpad bug 1412802 in Glance juno "copy-from broken for large files and swift" [Critical,In progress] - Assigned to Alexander Tivelkov (ativelkov)14:43
nikhil_kthat bug just made in time and is an important one14:43
ativelkovThanks to all the reviewers14:44
nikhil_kthanks to jokke_ who was available outside of this regular work hours for seeing this through14:44
nikhil_kI hope that we will get a better velocity in k314:44
jokke_nikhil_k: NP ... just wanted to avoid k1 all over again ;)14:45
nikhil_kreviews waiting for k3 are at  https://launchpad.net/glance/+milestone/kilo-314:45
nikhil_kjokke_: true that!14:45
*** pennerc_ has joined #openstack-meeting-414:45
nikhil_k#topic code cleanup14:45
*** openstack changes topic to "code cleanup (Meeting topic: Glance)"14:45
nikhil_klooking for volunteers to look into this https://review.openstack.org/#/c/145223/14:45
nikhil_kseems like we've some stale code14:46
nikhil_k(possibly create a spec and see it working)14:46
nikhil_kthat was it14:46
jokke_My guts are telling that we have loads of it14:46
zhiyani'd like to have a look14:46
nikhil_kthanks zhiyan14:46
nikhil_k#topic Review request for Reload configuration file on SIGHUP signal14:46
sigmavirus24== jokke_14:46
*** openstack changes topic to "Review request for Reload configuration file on SIGHUP signal (Meeting topic: Glance)"14:46
zhiyandue to i done before refacotrings14:46
nikhil_kabhishekk: ?14:46
abhishekknikhil_k: hi14:47
abhishekkjust saw its marked in k314:47
nikhil_kah ok, any significant change?14:47
abhishekkno, I want some early feedback14:47
* sigmavirus24 left feedback yesterday14:47
abhishekkand approval for spec14:47
zhiyannikhil_k: actually i trend to believe we could to remove file queue and 'cleanup' logic14:47
nikhil_kah ok, yes. It's marked for early k314:47
zhiyandue to from juno we start to use db queue fully14:48
nikhil_k#topic Open discussion14:48
*** openstack changes topic to "Open discussion (Meeting topic: Glance)"14:48
zhiyani will check the spec and left things for discussion..14:48
nikhil_kzhiyan: sure, can we get an informal proposal out , something that can be done in k3?14:48
nikhil_kwayne_: glad that you brought it up14:49
ativelkovWhat about backports of https://bugs.launchpad.net/bugs/1412802 to J/I?14:49
openstackLaunchpad bug 1412802 in Glance juno "copy-from broken for large files and swift" [Critical,In progress] - Assigned to Alexander Tivelkov (ativelkov)14:49
nikhil_khttps://review.openstack.org/#/c/154229/14:49
zhiyansure thing, i'd like to...it's on my list, thanks for propose it up for a formal spec!14:49
wayne_Regarding bug https://review.openstack.org/#/c/154229/, are there any objections to me doing this?14:49
nikhil_kwayne_: did you get a response back on/from the ML yet?14:49
kragnizativelkov: I know stuart is trying to come up with a smaller fix14:50
jokke_ativelkov: you have any update on those backports?14:50
wayne_no response yet.14:50
nikhil_kativelkov: yes, please try to review a related patch in glance_store14:50
nikhil_kwayne_: ok, let's give it another couple days. We can sync up on #openstack-glance on Mon14:51
ativelkovkragniz: jokke_: nikhil_k: that's what I wanted to ask - this is a patch in glance_store14:51
nikhil_kativelkov: but not for icehouse14:51
wayne_ok14:51
ativelkovit means it will be available in the next glance_store release14:51
sigmavirus24wayne_: do I understand correctly that that was done in k-{1,2} ?14:51
ativelkovnikhil_k: yes, it is not compatible with I, and I don't know if we may use newer glance_store with J - is it backwards compatible?14:52
nikhil_kk114:52
nikhil_ksigmavirus24: ^14:52
nikhil_kah14:52
nikhil_kativelkov: let's mark the glance_store release blocked by that14:52
*** mbgalt has joined #openstack-meeting-414:52
sigmavirus24nikhil_k: so, perhaps I'm missing something, but aren't those alpha/beta-ish releases? Backwards incompatible changes between them is to be expected14:52
nikhil_kzhiyan: np14:52
sigmavirus24If I'm not misunderstanding, I'll reply to the ML with my thoughts on it so I can stir the pot for Wayne14:53
wayne_sigmavirus24: yes K114:53
nikhil_ksigmavirus24: right, so we got blessings from ttx14:53
nikhil_kJust trying to confirm if no one else if affected by this14:53
jokke_glance_store is not currently capped on Juno\14:53
sigmavirus24nikhil_k: yeah, I'll respond on the ML then14:53
zhiyannikhil_k: pkoniszewski do you think we can do it in k3 on time? https://review.openstack.org/#/c/147264 can you share some status info with me?14:53
wayne_sigmavirus: thanks14:54
nikhil_ksigmavirus24: cool, we are not expecting anyone besides horizon to be using it for now14:54
nikhil_kbut you never know14:54
nikhil_kjokke_: that may change though, right?14:55
jokke_nikhil_k: ofc it may ... I was just confirming that it's not ... so if we are planning to release glasnce_store that breaks Juno, we need to do something about that fact14:56
nikhil_kzhiyan: I think we need that in k314:56
pkoniszewskizhiyan: I'm sure we can, change is really small - it exposes new flag over API so it is backward compatible14:56
zhiyanok..will check it asap14:57
nikhil_kzhiyan: I think we need to get some reviews on https://review.openstack.org/#/c/148213/ along with the spec14:57
*** carl_baldwin has joined #openstack-meeting-414:57
nikhil_kto avoid the metadef tags like error again14:57
sigmavirus24Yeah we might want to cap stable/juno's g-r to be safe until we can test it so -infra doesn't get really mad at us14:57
sigmavirus24=P14:57
*** qwebirc68886 has joined #openstack-meeting-414:58
jokke_sigmavirus24: infram is small problem on that :P14:58
zhiyannikhil_k: indeed, that's what i worried about..unlike the case in j-314:58
nikhil_k:)14:58
sigmavirus24jokke_: right, but they've been dealing with problems like this repeatedly lately and I'm sure their patience is wearing thin. I don't want to add any more grey hairs to their heads14:58
sigmavirus24They're all good people and reducing their stress is something we can help with =)14:59
jokke_sigmavirus24: tru dat14:59
ativelkovsigmavirus24: you suggest to cap it to the currently released version?14:59
jokke_sigmavirus24: there was quite a heated discussion at X-Project meeting yesterday14:59
sigmavirus24ativelkov: until we can show that it won't break stable/juno14:59
jokke_and there has been quite heated discussions on the mailing list14:59
kragnizwe're out of time15:00
kragnizlast thing - we should now have pretty glance logs in devstack!15:00
nikhil_kyep15:00
sigmavirus24I think a pre-emptive cap will be good until we can test it out. There's no reason to break the gate for anyone integrating with glance15:00
kragniz#link https://review.openstack.org/#/c/155024/15:00
jokke_yup ... thnx!15:00
nikhil_kThanks all!15:00
sigmavirus24Thanks everyone15:00
kragnizthanks15:00
abhishekkthank you15:00
ativelkovthanks!15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Feb 12 15:00:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
*** abhishekk has quit IRC15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-12-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-02-12-14.00.log.html15:00
*** TravT has left #openstack-meeting-415:00
*** lakshmiS has quit IRC15:00
zhiyanthanks15:01
*** jokke_ has left #openstack-meeting-415:01
*** pennerc_ has quit IRC15:01
*** qwebirc68886 has quit IRC15:02
*** krykowski has quit IRC15:03
*** dboik has joined #openstack-meeting-415:08
*** pkoniszewski has quit IRC15:11
*** wayne_ has quit IRC15:12
*** salv-orlando has joined #openstack-meeting-415:14
*** salv-orlando has quit IRC15:17
*** dboik_ has joined #openstack-meeting-415:28
*** numan has quit IRC15:28
*** dboik_ has quit IRC15:28
*** dboik_ has joined #openstack-meeting-415:29
*** asselin has joined #openstack-meeting-415:30
*** dboik has quit IRC15:31
*** opsvision has joined #openstack-meeting-415:41
*** ivasilevskaya has left #openstack-meeting-415:48
*** salv-orlando has joined #openstack-meeting-415:54
*** cloudnull has joined #openstack-meeting-415:55
*** b3rnard0 has joined #openstack-meeting-415:56
*** rackertom has joined #openstack-meeting-415:57
*** rosmaita has left #openstack-meeting-415:59
*** odyssey4me has joined #openstack-meeting-415:59
*** BjoernT has joined #openstack-meeting-415:59
b3rnard0#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Feb 12 16:00:10 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
cloudnullhello !16:00
odyssey4meo/16:00
b3rnard0#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:00
mancdazhi16:00
BjoernTHi16:00
b3rnard0#topic RollCall16:00
*** openstack changes topic to "RollCall (Meeting topic: OpenStack Ansible Meeting)"16:00
cloudnullpresent16:00
*** Sam-I-Am has joined #openstack-meeting-416:00
Sam-I-Amhi16:00
b3rnard0hello16:00
palendaePresent16:01
serverascodehere16:01
rackertomHello16:01
mancdazpresent16:01
*** andymccr has joined #openstack-meeting-416:01
b3rnard0#topic Review action items from last week16:02
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:02
cloudnullok, lets get started.16:02
cloudnullfirst up hughsaunders to start reading inventory-manage.py16:03
mancdazhe's not present16:03
odyssey4meI think that was a bit of a laugh anyway. He did say that it needn't carry.16:04
cloudnullso ill assume not. :)16:04
cloudnullb3rnard0 use link shortener at next meeting16:04
cloudnull^ .doit()16:04
b3rnard0#link http://tinyurl.com/pzhdxev16:04
cloudnullnext: "d34dh0r53 : to help with review of https://review.openstack.org/#/c/152753/"16:04
d34dh0r53in progress16:04
*** LosMyke has joined #openstack-meeting-416:04
*** git-harry has joined #openstack-meeting-416:05
cloudnullon that review, has anyone had time to review it? besides odyssey4me  and d34dh0r5316:05
d34dh0r53nothing major so far other than the multiple physical drive failure in the aio that we discovered16:05
odyssey4meandymccr has been doing some work with it16:05
andymccri got it working at least, after a few issues which i think are fixed now?16:06
cloudnullandymccr pointed out an issue with the dynamic inventory this morning, so ill have that pushed up this morning.16:06
cloudnulli have to do a rebase though before i can do it16:06
andymccrsince its all encompassing i think we need to decide how we're gonna do this16:06
cloudnulli think thats fair .16:07
andymccreither we need to just get this through (after a bit of testing) or we need to try split it up. but we should probably pick cos as it stands people are going to be spinning wheels with no real result16:07
odyssey4merelated topic, I'm working on doing the deraxification in https://review.openstack.org/155342 - perhaps you should rebase on top of that to make your monster patch less monster?16:07
cloudnulli was going to bring that up here too.16:07
b3rnard0#info related topic, I'm working on doing the deraxification in https://review.openstack.org/155342 - perhaps you should rebase on top of that to make your monster patch less monster?16:07
*** galstrom_zzz is now known as galstrom16:08
*** salv-orlando has quit IRC16:08
odyssey4menote - it's not fully tested yet, so don't bother just yet... I'm trying out installs now16:08
cloudnullso the de-raxing is just as large as the "moster patch"-tm16:08
odyssey4meyep, but it's focused on doing one thing only - so that your patch can focus on doing the other thing16:08
hughsaundersnot really16:08
cloudnulldo we really think that piecing out into multiple patches is better ?16:08
git-harryyes16:09
cloudnullhow?16:09
hughsaundersodyssey4me's patch is mostly renames and removes, so its easier to see whats going on16:09
odyssey4methis patch should focus on de-raxing and putting in a migration plan - your patch can focus on converting to ansible roles16:09
cloudnullthis is true.16:09
andymccri would even say stuff like moving out to use multiple user_secrets/user_variables etc files should be a separate patch in itself16:10
*** fnaval has joined #openstack-meeting-416:10
git-harry^agree16:10
odyssey4me+1 andymccr16:10
cloudnullbut it also leaves master broken until its fixed. which is done in the original review16:10
mancdazit also makes changelogs easier to generate16:10
hughsaunders+284, -49915 vs +30089, -7705116:10
andymccri think stealth committing several things isn't ideal. but we need to commit to one way or the other in this instance - or we end up with people doing different things where only 1 will be used and its a waste essentially.16:10
odyssey4mewhen the de-rax patch is no longer wip it'll be a working install16:10
b3rnard0#info andymccr: i would even say stuff like moving out to use multiple user_secrets/user_variables etc files should be a separate patch in itself16:10
cloudnullin addition the already available patch passes our gating and tempest tests which we dont have in our current releases.16:11
cloudnullso its better tested than what we have presently16:11
andymccrim concerned about upgrading existing installs16:11
andymccrand bug regression16:11
odyssey4meyeah, but the patch may have regressions which are very hard to spot right now16:11
git-harryWe've not been adding tests when things are fixed16:12
odyssey4mebesides, I think everyone needs more time because the patch entirely changes the way the install works16:12
cloudnullgit-harry we presently have no tempest tests running16:12
odyssey4meit'd be easier to review if it was broken up a bit more - and the patch didn't also include extra features along the way ;)16:12
Sam-I-Ami sense docs changes :)16:12
*** rromans has joined #openstack-meeting-416:13
*** KLevenstein has joined #openstack-meeting-416:13
palendaeSam-I-Am: There will be whenever this work merges, no matter what patch it comes from16:13
odyssey4meSam-I-Am high level of doc impact for both16:13
git-harrycloudnull: I thought we had some16:13
Sam-I-Amand upgrades might become more interesting16:13
cloudnullgit-harry no, we have qe16:13
cloudnulladditionally tempest in its present state will not run , it cant ssh to a built instance.16:13
*** wojdev has quit IRC16:13
cloudnullthe test fail no matter what .16:13
git-harrytesting is not just tempest16:14
cloudnullagreed16:14
*** salv-orlando has joined #openstack-meeting-416:14
mancdazregardless of the state of this particular patch, isn't it more about the principle of massive patches versus smaller iterative patches16:14
cloudnullso i think that its easier to understand the patches when we split it out. but i also think we're just prolonging the inevitable.16:15
mancdazcloudnull the first part of what you said is important though16:15
odyssey4mesure, it may all end up at exactly what you've produced in the end - but I think more people need time to work through it properly16:15
mancdazit's easier for everyone to understand the changes if they are iterative over a longer time16:15
odyssey4meif it's broken up into smaller patches then it's easier to consume, test and approve16:16
cloudnullwe need to be thinking about how we get to "kilo" and not maintaining our raxisims in this community project.16:17
BjoernTI don't think anyone can review such large patches. We should adopt the same rule a linux kernel dev, no patch > 300k or so. I believe that was the rule, or something similar.16:17
d34dh0r53I agree that small patches are easier to grok, but breaking the mega-patch into an iterative process will require the addition of a lot of constantly changing glue code which IMHO is likely to break and cause problems.16:17
cloudnull^ that16:18
andymccrimo we're trying to achieve like 5 things here. e.g. renaming. galaxy roles, split out user_vars/secrets etc,add some new conf options16:18
andymccrthis doens't mean we won't still have some massive patches16:19
andymccrwe will, but i think there are some pretty clear divisions that aren't going to require glue code16:19
hughsaundersdynamic inventory changes, package building changes16:19
BjoernTRight but we might consider that in the future for new patches16:19
rackertomI've only looked at a small portion of the patch because of its size. But, I'd ask if the cost of teasing out the relationships between several patch chunks and any possible breakage in the CI processes is worth the effort of actually breaking it out.16:20
odyssey4meif the de-rax can happen first I really do feel like it would make the patch less intimidating16:20
cloudnullandymccr i disagree in-order to iteratively  remove our preset bits to be more community focused we're going to have to create a tun of glue16:21
odyssey4meat this stage I'm not informed enough to determine whether the conversion to galaxy roles would require much glue (if any)16:21
cloudnullits a rip and replace.16:22
cloudnullto keep what we have we're going to have to create a lot of glue.16:22
*** jckasper_ has joined #openstack-meeting-416:22
Sam-I-Amas long as the glue smells good16:22
d34dh0r53lol16:22
andymccrcloudnull: can you give an example of the glue?16:22
cloudnullsure.16:22
andymccrmy thinking is if i said to you we're not doing galaxy roles, just remove the raxisms, its something that could be done without glue surely.16:23
cloudnullwe presently dont use any "defaults" in any of roles. instead we overload group vars. in order to make the new and old work together we're going to have to create defaults that set to the old variables.16:23
*** sballe__ has joined #openstack-meeting-416:23
odyssey4meyeah, the only 'glue' would be the migration process for the inventory and variables16:23
cloudnullusing vars_files16:24
*** jckasper has quit IRC16:24
cloudnullbecause of the way we do vars, that will effect everything16:24
andymccrcloudnull: how does that impact the name changing/removal of rax stuff?16:24
cloudnullrpc_* rackspace_*16:24
cloudnullare vars that we use throughout16:24
cloudnulladditionally we created structure that shouldnt exist16:25
cloudnullfurthermore our currect gate checks look at roles for linting which will break on the new roles16:25
andymccrbut we shouldn't change roles - we should just change the naming on vars etc16:26
cloudnullbecause they use a defauls and meta main.yml16:26
andymccrso that rax is gone.16:26
odyssey4mesure, but that'll be handled by the de-rax patch16:26
andymccrthats kind of my point in that we have 1 task "remove the RAX references" not "remove the RAX references and adjust the roles to do some other structuring at the same time because it seems more efficient"16:26
*** yamahata has joined #openstack-meeting-416:26
cloudnullso with our current gating and setup we can not have the two live together .16:26
hughsaunderscloudnull: why would the new roles not pass the lint check?16:27
cloudnullthe lint check should only check the plays.16:28
cloudnullthe plays pull in the role.s16:28
*** crinkle has left #openstack-meeting-416:28
cloudnullif you do a syntax check on a role it will fail because the defaults/main.yml is not a dict16:28
cloudnullsame with meta/main.yml16:29
*** fnaval has quit IRC16:29
*** fnaval has joined #openstack-meeting-416:29
hughsaundersfair, seems like odyssey4me's gate-script-split patch should help with that16:29
palendaeSo the syntax check requires the roles to be galaxy-compliant?16:29
odyssey4meok - side topic of importance... before we can do anything we need everyone to test and be happy with https://review.openstack.org/152965 (gate script changes)... once that's merged then I can change openstack-infra's jobs... then we only need to change the scripts if we want to verify builds, etc16:29
palendaehughsaunders: that one is getting big too16:29
hughsaundersalso fair16:30
odyssey4mepalendae it is done, from my standpoint - I did find a bug in it just before the meeting (specifically with regards to lint testing)16:30
odyssey4mehughsaunders just needs to verify that it suits the tempest and multi-node needs16:31
cloudnullpalendae no it doesn't require it. but in our current stack the roles dont follow ansible best practices which at this point allows the syntax check to pass , because there are no default variable.s16:31
palendaeAh16:31
*** carl_baldwin has quit IRC16:32
odyssey4meI think the basic request for now is simply to allow the de-rax and conversion-to-galaxy-roles to be seperated16:32
b3rnard0#info odyssey4me: ok - side topic of importance... before we can do anything we need everyone to test and be happy with https://review.openstack.org/152965 (gate script changes)... once that's merged then I can change openstack-infra's jobs... then we only need to change the scripts if we want to verify builds, etc16:32
andymccrodyssey4me: its more than that. because there are still 4 other things that happen in the mega-patch16:32
andymccrtheres not much point splitting out 1 thing16:32
andymccrand not the others, because its more a question of approach16:32
andymccrthe mega-patch itself could work fine, and from what ive seen in testing - it does16:33
*** fnaval has quit IRC16:33
cloudnullok, so lets break it up. thats the overwhelming consensus.16:33
b3rnard0#agreed cloudnull: ok, so lets break it up. thats the overwhelming consensus.16:34
odyssey4meI was kind-of thinking that perhaps we break the de-rax out. Get that done. Then we're able to look at the rest of the patch to see what's there. Next week perhaps then we identify what we feel should be added as a subsequent patch (they're new features)16:34
*** dannywilson has joined #openstack-meeting-416:35
odyssey4meit'll also give us all the chance to focus a little more on the patch itself as much of the gating work will be tapering off.16:35
cloudnullok. but we need to get this done before "kilo-3". we'll have failed if we let it go farther than that16:36
cloudnullkilo-3 is march.16:37
b3rnard0#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule16:37
odyssey4memar 19 - a month from now16:37
odyssey4meassuming that we can put time in the next sprint into this, then I would expect that we should be able to meet that deadline quite easily16:37
cloudnullyes, seems like a long time but at our current rate of review / change its not that much time.16:37
hughsaunderswe can all work on it in SAT (if not done by then)16:38
*** dannywilson has quit IRC16:38
*** dannywilson has joined #openstack-meeting-416:38
cloudnullhughsaunders: we should have it done before.16:38
cloudnullwe should be working on solving kilo issues no attempting to genericize.16:39
palendaecloudnull: Hopefully the reviews will go faster if it's smaller patches. That's what people seem to be saying, anyway16:39
cloudnullkk16:39
cloudnullmoving on16:39
b3rnard0#topic Gating16:39
*** openstack changes topic to "Gating (Meeting topic: OpenStack Ansible Meeting)"16:39
cloudnullodyssey4me: patch is looking good .16:40
cloudnullhughsaunders where are we on getting tempest to run ?16:40
*** sarob has joined #openstack-meeting-416:40
cloudnullusing the commit_aio ?16:41
cloudnullhughsaunders anything  ?16:41
hughsaunderscloudnull: had a successful run today: https://review.openstack.org/#/c/154799/12 but not reliable yet16:41
cloudnullwhat's "not reliable yet"16:42
hughsaundersthe build after that failed (patch set 11)16:42
hughsaunderslatest run failed on installing cinder (unrelated) the one before that failed on restarting keystone-apache (port 5k in use)16:44
hughsaundersso currently dealing with annoying failures that aren't actually related to tempest. The last run that got as far as tempest booted an instance, created a volume, attached the volume, but then timed out.16:44
cloudnullthats likley related to ssh timeout.16:45
*** sarob has quit IRC16:45
cloudnullalso i see that we're still hard coding the default networks ?16:45
hughsaunderswas a 504 gateway timeout16:45
*** yamahata has quit IRC16:45
*** yamahata has joined #openstack-meeting-416:46
hughsaundersI moved the cidrs into group_vars/tempest_all so they can be overriden16:46
cloudnullin tempest.conf.j2 i see "default_network = 192.168.74.0/24"16:47
hughsaundersthat will need to be fixed then16:47
cloudnullok, we'll have to look at these issues. Maybe we can port over the role for tempest our of the massive-patch(tm) which will further reduce the size of that patch.16:48
hughsaunderscloudnull: did you change it much?16:48
b3rnard0#info cloudnull: in tempest.conf.j2 i see "default_network = 192.168.74.0/24”; hughsaunders: that will need to be fixed then16:48
cloudnullnot much , but i did map out all of the config options to their appropriate sections.16:49
cloudnulland like i mentioned earlier , the massive patch is currently passing gating using tempest.16:49
cloudnullso i have it functional in that role.16:49
cloudnulldo we have anyone from the rax qe here?16:49
palendaeBjoernT? ^16:50
cloudnullwhat else gating related do we have going on ?16:51
*** ChuckC_ has quit IRC16:51
cloudnullok moving on16:51
BjoernTI'm not officially QE but I kinda fall into the bugs as early adaptor16:51
hughsaunderswork on converting the commit labs to clean up rather than rekick16:51
*** ChuckC_ has joined #openstack-meeting-416:51
*** ChuckC_ is now known as ChuckC16:51
hughsaundersQE are working on converting their nightly labs to rekick16:52
cloudnullok.16:52
cloudnullBjoernT: do you have anything to add to gating?16:52
hughsaundersAlso there is still work to be done to use the same set of pre os-ansible-deployment plays across all the labs16:52
palendaehughsaunders: That's kind of rax-specific no?16:53
BjoernTI have not seen the full potential yet since tempest failed in my cloud environment so too early to say from my perspective16:53
cloudnullkk16:53
BjoernTis tempest supposed to work with 10.1.2 and 9.0.6 ?16:53
hughsaunderstempest should run against both16:54
cloudnullBjoernT: imo it should. buts its a work in progress.16:54
BjoernTok I will check out the error I got offline with someone16:54
cloudnullSo we're almost out of time but i wanted to point out that we have a new bp, if we can get some eyes on it that'd be good. "https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation"16:55
palendaeYeah; I would like people's thoughts on that blueprint16:55
cloudnulldo we have anything else that we want to discus?16:55
*** evgenyf has quit IRC16:55
b3rnard0#info BjoernT: is tempest supposed to work with 10.1.2 and 9.0.6 ?;  hughsaunders: tempest should run against both; cloudnull: BjoernT: imo it should. buts its a work in progress.16:55
b3rnard0#topic Open discussion16:56
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:56
hughsaundersthat bp looks good, may help reduce the amount of code in jenkins-rpc16:56
palendaehughsaunders: Yep, and hopefully other places16:56
b3rnard0#info cloudnull: So we're almost out of time but i wanted to point out that we have a new bp, if we can get some eyes on it that'd be good. "https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation"16:56
*** fnaval has joined #openstack-meeting-416:56
odyssey4meyeah, it does look good16:56
odyssey4methe debops roles also look like they may be usable for other infrastructure in the stack we deploy16:57
cloudnullso cores, lets get eyes on it and prioritize it accordingly.16:57
* odyssey4me nods16:57
cloudnullok so lets call it16:57
b3rnard0#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Thu Feb 12 16:58:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-12-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-12-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-12-16.00.log.html16:58
*** KLevenstein has left #openstack-meeting-416:58
*** git-harry has left #openstack-meeting-416:58
cloudnullthanks all16:58
b3rnard0thanks everyone16:58
*** cloudnull has left #openstack-meeting-416:58
*** odyssey4me has left #openstack-meeting-416:59
*** rackertom has left #openstack-meeting-417:01
*** mbgalt has quit IRC17:04
*** andymccr has left #openstack-meeting-417:07
*** SridharRamaswamy has joined #openstack-meeting-417:10
*** opsvision has quit IRC17:11
*** bobmel has joined #openstack-meeting-417:13
*** SridharRamaswam1 has joined #openstack-meeting-417:13
*** SridharRamaswamy has quit IRC17:14
*** bobmel_ has quit IRC17:15
*** carl_baldwin has joined #openstack-meeting-417:15
*** opsvision has joined #openstack-meeting-417:15
*** banix has quit IRC17:25
*** salv-orlando has quit IRC17:29
*** salv-orlando has joined #openstack-meeting-417:29
*** matrohon has quit IRC17:38
*** kobis has quit IRC17:38
*** ChuckC has quit IRC17:42
*** emagana has joined #openstack-meeting-417:42
*** ChuckC has joined #openstack-meeting-417:42
*** SumitNaiksatam has joined #openstack-meeting-417:52
*** banix has joined #openstack-meeting-417:54
*** mwang2 has joined #openstack-meeting-417:59
*** ivar-lazzaro has joined #openstack-meeting-418:06
*** ivar-lazzaro has quit IRC18:07
*** ivar-lazzaro has joined #openstack-meeting-418:08
*** salv-orlando has quit IRC18:10
*** salv-orlando has joined #openstack-meeting-418:10
*** salv-orl_ has joined #openstack-meeting-418:12
*** salv-orl_ has quit IRC18:12
*** salv-orl_ has joined #openstack-meeting-418:13
*** dboik_ has quit IRC18:13
*** pkoniszewski has joined #openstack-meeting-418:16
*** s3wong has joined #openstack-meeting-418:16
*** salv-orlando has quit IRC18:20
*** dboik has joined #openstack-meeting-418:20
*** dboik has quit IRC18:20
*** dboik has joined #openstack-meeting-418:20
*** b3rnard0 has left #openstack-meeting-418:22
*** SridharRamaswam1 has quit IRC18:24
*** Sam-I-Am has left #openstack-meeting-418:28
*** emagana has quit IRC18:29
*** emagana has joined #openstack-meeting-418:29
*** emagana has quit IRC18:30
*** emagana has joined #openstack-meeting-418:30
*** dboik has quit IRC18:32
*** dboik has joined #openstack-meeting-418:38
*** SridharRamaswamy has joined #openstack-meeting-418:49
*** dboik has quit IRC18:54
*** dboik has joined #openstack-meeting-418:55
*** wojdev has joined #openstack-meeting-419:02
*** dboik has quit IRC19:05
*** dboik has joined #openstack-meeting-419:06
*** banix has quit IRC19:12
*** banix has joined #openstack-meeting-419:14
*** kobis has joined #openstack-meeting-419:20
*** emagana has quit IRC19:26
*** emagana has joined #openstack-meeting-419:26
*** GavinPratt has joined #openstack-meeting-419:27
*** kobis1 has joined #openstack-meeting-419:28
*** kobis has quit IRC19:29
*** emagana has quit IRC19:31
*** emagana has joined #openstack-meeting-419:44
*** sarob has joined #openstack-meeting-419:46
*** emagana has quit IRC19:49
*** emagana has joined #openstack-meeting-419:49
*** emagana has quit IRC19:54
*** wojdev has quit IRC19:54
*** rfolco has quit IRC20:02
*** briancurtin has quit IRC20:07
*** serverascode has quit IRC20:07
*** zhiyan has quit IRC20:08
*** emagana has joined #openstack-meeting-420:09
*** radek has quit IRC20:12
*** s3wong has quit IRC20:12
*** s3wong has joined #openstack-meeting-420:14
*** briancurtin has joined #openstack-meeting-420:17
*** zhiyan has joined #openstack-meeting-420:18
*** serverascode has joined #openstack-meeting-420:18
*** kobis1 has quit IRC20:22
*** mwang2 has quit IRC20:22
*** VW_ has quit IRC20:29
*** salv-orlando has joined #openstack-meeting-420:38
*** salv-orl_ has quit IRC20:41
*** markvoelker has joined #openstack-meeting-420:41
*** qwebirc46669 has joined #openstack-meeting-420:44
*** qwebirc46669 has quit IRC20:44
*** sarob_ has joined #openstack-meeting-420:44
*** sarob_ has quit IRC20:45
*** yamahata has quit IRC20:46
*** qwebirc51741 has joined #openstack-meeting-420:49
*** s3wong has quit IRC20:49
*** qwebirc51741 has quit IRC20:50
*** s3wong has joined #openstack-meeting-420:53
*** mwang2 has joined #openstack-meeting-420:59
*** jckasper has joined #openstack-meeting-421:02
*** jckasper_ has quit IRC21:05
*** jckasper has quit IRC21:07
*** jckasper has joined #openstack-meeting-421:07
*** jckasper_ has joined #openstack-meeting-421:09
*** jckasper has quit IRC21:12
*** banix has quit IRC21:17
*** mwang2_ has joined #openstack-meeting-421:19
*** mwang2 has quit IRC21:22
*** banix has joined #openstack-meeting-421:23
*** emagana has quit IRC21:30
*** emagana has joined #openstack-meeting-421:31
*** emagana has quit IRC21:34
*** emagana has joined #openstack-meeting-421:35
*** sigmavirus24 is now known as sigmavirus24_awa21:55
*** banix has quit IRC21:56
*** emagana has quit IRC22:01
*** pkoniszewski has quit IRC22:01
*** s3wong has quit IRC22:02
*** rromans has left #openstack-meeting-422:03
*** s3wong has joined #openstack-meeting-422:08
*** emagana has joined #openstack-meeting-422:12
*** VW_ has joined #openstack-meeting-422:15
*** salv-orlando has quit IRC22:19
*** s3wong has quit IRC22:19
*** s3wong has joined #openstack-meeting-422:19
*** salv-orlando has joined #openstack-meeting-422:19
*** VW_ has quit IRC22:20
*** yamahata has joined #openstack-meeting-422:25
*** banix has joined #openstack-meeting-422:32
*** carl_baldwin has quit IRC22:40
*** VW_ has joined #openstack-meeting-422:43
*** Sandra_ has joined #openstack-meeting-422:44
*** Sandra_ has quit IRC22:50
*** GavinPratt has quit IRC22:57
*** pleia2 has joined #openstack-meeting-423:08
*** dboik_ has joined #openstack-meeting-423:09
*** dboik has quit IRC23:13
*** dboik_ has quit IRC23:14
*** y-oguchi has joined #openstack-meeting-423:18
*** klamath has quit IRC23:18
*** y-oguchi has quit IRC23:19
*** watanabe_isao has joined #openstack-meeting-423:27
*** watanabe_isao has quit IRC23:28
*** watanabe_isao has joined #openstack-meeting-423:32
*** yamahata has quit IRC23:39
*** openstack has joined #openstack-meeting-423:40
*** ChanServ sets mode: +o openstack23:40
*** VW_ has quit IRC23:49
*** galstrom is now known as galstrom_zzz23:54
*** carl_baldwin has joined #openstack-meeting-423:54
*** salv-orlando has quit IRC23:54
*** krtaylor has quit IRC23:57

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