Thursday, 2015-03-12

*** vishwanathj has quit IRC00:00
*** banix has joined #openstack-meeting-400:01
*** Nikolay_St has quit IRC00:08
*** banix has quit IRC00:26
*** shwetaap has joined #openstack-meeting-400:30
*** shwetaap1 has joined #openstack-meeting-400:33
*** shwetaap has quit IRC00:37
*** dannywilson has joined #openstack-meeting-400:44
*** smc7 has joined #openstack-meeting-400:46
*** smc7 has quit IRC00:51
*** rfolco_ has quit IRC00:59
*** marun has joined #openstack-meeting-401:00
*** igordcard_ has quit IRC01:03
*** claired has quit IRC01:04
*** marun has quit IRC01:05
*** ibiris is now known as ibiris_away01:05
*** SumitNaiksatam has quit IRC01:13
*** sigmavirus24 is now known as sigmavirus24_awa01:19
*** markvoelker has quit IRC01:27
*** ivar-laz_ has joined #openstack-meeting-401:27
*** markvoelker has joined #openstack-meeting-401:27
*** wojdev has quit IRC01:29
*** ivar-lazzaro has quit IRC01:30
*** ivar-laz_ has quit IRC01:32
*** markvoelker has quit IRC01:32
*** sdake_ has quit IRC01:42
*** sballe__ has quit IRC01:48
*** bharath_ has quit IRC01:53
*** bharath has joined #openstack-meeting-401:53
*** dims_ has quit IRC01:53
*** ajmiller has joined #openstack-meeting-401:54
*** ajmiller_ has joined #openstack-meeting-401:55
*** ajmiller has quit IRC01:55
*** salv-orlando has quit IRC01:58
*** bharath has quit IRC01:58
*** yamahata has quit IRC01:59
*** s3wong has quit IRC02:07
*** banix has joined #openstack-meeting-402:11
*** jckasper has quit IRC02:13
*** Nikolay_St has joined #openstack-meeting-402:14
*** ivar-lazzaro has joined #openstack-meeting-402:23
*** vishwanathj has joined #openstack-meeting-402:32
*** smc7 has joined #openstack-meeting-402:35
*** smc7 has quit IRC02:40
*** ivar-lazzaro has quit IRC02:43
*** david-lyle is now known as david-lyle_afk02:45
*** sdake_ has joined #openstack-meeting-402:48
*** marun has joined #openstack-meeting-402:53
*** dims_ has joined #openstack-meeting-402:54
*** shwetaap1 has quit IRC02:55
*** shwetaap has joined #openstack-meeting-402:58
*** salv-orlando has joined #openstack-meeting-402:59
*** dims_ has quit IRC02:59
*** jamiem has quit IRC03:05
*** salv-orlando has quit IRC03:10
*** salv-orlando has joined #openstack-meeting-403:19
*** ivar-lazzaro has joined #openstack-meeting-403:19
*** SumitNaiksatam has joined #openstack-meeting-403:22
*** salv-orlando has quit IRC03:23
*** salv-orlando has joined #openstack-meeting-403:24
*** salv-orlando has quit IRC03:29
*** dannywilson has quit IRC03:31
*** fnaval has quit IRC03:36
*** sdake_ has quit IRC03:38
*** banix has quit IRC03:41
*** fnaval has joined #openstack-meeting-403:44
*** shwetaap1 has joined #openstack-meeting-403:55
*** shwetaap has quit IRC03:57
*** SridharRamaswamy has joined #openstack-meeting-404:00
*** Nikolay_St has quit IRC04:05
*** sdake_ has joined #openstack-meeting-404:08
*** shwetaap has joined #openstack-meeting-404:14
*** shwetaap1 has quit IRC04:17
*** jckasper has joined #openstack-meeting-404:17
*** smc7 has joined #openstack-meeting-404:24
*** smc7 has quit IRC04:28
*** ivar-lazzaro has quit IRC04:33
*** ivar-lazzaro has joined #openstack-meeting-404:34
*** SridharRamaswam1 has joined #openstack-meeting-404:36
*** SridharRamaswamy has quit IRC04:38
*** ivar-lazzaro has quit IRC04:39
*** jckasper has quit IRC04:41
*** bharath has joined #openstack-meeting-404:46
*** marun has quit IRC04:47
*** salv-orlando has joined #openstack-meeting-404:49
*** marun has joined #openstack-meeting-404:50
*** sdake__ has joined #openstack-meeting-404:55
*** Nikolay_St has joined #openstack-meeting-404:55
*** sdake_ has quit IRC04:58
*** salv-orlando has quit IRC05:00
*** fnaval has quit IRC05:02
*** yamahata has joined #openstack-meeting-405:04
*** david-ly_ has joined #openstack-meeting-405:04
*** dvorak has quit IRC05:05
*** blogan_ has joined #openstack-meeting-405:06
*** mestery_ has joined #openstack-meeting-405:07
*** SumitNaiksatam has quit IRC05:07
*** sdake__ has quit IRC05:08
*** mestery has quit IRC05:08
*** david-lyle_afk has quit IRC05:09
*** galstrom_zzz has quit IRC05:09
*** blogan has quit IRC05:09
*** galstrom_zzz has joined #openstack-meeting-405:10
*** dvorak has joined #openstack-meeting-405:14
*** SridharRamaswam1 has quit IRC05:17
*** marun has quit IRC05:19
*** marun has joined #openstack-meeting-405:22
*** shwetaap has quit IRC05:23
*** markvoelker has joined #openstack-meeting-405:25
*** Nikolay_St has quit IRC05:26
*** markvoelker has quit IRC05:30
*** marun has quit IRC05:42
*** sdake_ has joined #openstack-meeting-406:02
*** sdake__ has joined #openstack-meeting-406:04
*** ibiris_away is now known as ibiris06:05
*** sdake_ has quit IRC06:08
*** sdake_ has joined #openstack-meeting-406:10
*** numan has joined #openstack-meeting-406:12
*** smc7 has joined #openstack-meeting-406:13
*** sdake__ has quit IRC06:13
*** sdake__ has joined #openstack-meeting-406:14
*** smc7 has quit IRC06:17
*** sdake_ has quit IRC06:18
*** markvoelker has joined #openstack-meeting-406:26
*** yamahata has quit IRC06:26
*** markvoelker has quit IRC06:32
*** dims_ has joined #openstack-meeting-406:32
*** sdake_ has joined #openstack-meeting-406:37
*** dims_ has quit IRC06:38
*** sdake__ has quit IRC06:41
*** sdake__ has joined #openstack-meeting-406:58
*** smc7 has joined #openstack-meeting-407:00
*** sdake_ has quit IRC07:02
*** bobmel has joined #openstack-meeting-407:06
*** sdake__ has quit IRC07:08
*** bobmel_ has quit IRC07:09
*** pkoniszewski has joined #openstack-meeting-407:09
*** ibiris is now known as ibiris_away07:15
*** watanabe_isao has joined #openstack-meeting-407:17
*** garyk has joined #openstack-meeting-407:19
*** salv-orlando has joined #openstack-meeting-407:27
*** markvoelker has joined #openstack-meeting-407:28
*** evgenyf has joined #openstack-meeting-407:32
*** markvoelker has quit IRC07:33
*** salv-orlando has quit IRC07:35
*** salv-orlando has joined #openstack-meeting-407:39
*** garyk has quit IRC07:41
*** garyk has joined #openstack-meeting-407:41
*** salv-orl_ has joined #openstack-meeting-407:42
*** sdake_ has joined #openstack-meeting-407:42
*** salv-orlando has quit IRC07:43
*** salv-orl_ has quit IRC07:46
*** wojdev has joined #openstack-meeting-407:48
*** sdake_ has quit IRC07:49
*** wojdev has quit IRC07:50
*** wojdev has joined #openstack-meeting-407:51
*** sdake has joined #openstack-meeting-407:56
*** kobis has joined #openstack-meeting-407:56
*** salv-orlando has joined #openstack-meeting-408:01
*** salv-orlando has quit IRC08:06
*** matrohon has joined #openstack-meeting-408:11
*** Nikolay_St has joined #openstack-meeting-408:21
*** kobis has quit IRC08:25
*** garyk has quit IRC08:25
*** kobis has joined #openstack-meeting-408:25
*** garyk has joined #openstack-meeting-408:25
*** markvoelker has joined #openstack-meeting-408:29
*** watanabe_isao has quit IRC08:32
*** markvoelker has quit IRC08:34
*** salv-orlando has joined #openstack-meeting-408:34
*** wojdev has quit IRC08:45
*** wojdev has joined #openstack-meeting-408:49
*** sdake__ has joined #openstack-meeting-408:54
*** sdake has quit IRC08:57
*** ibiris_away is now known as ibiris09:05
*** kobis has quit IRC09:09
*** kobis has joined #openstack-meeting-409:18
*** markvoelker has joined #openstack-meeting-409:30
*** smc7 has quit IRC09:34
*** wayne___ has joined #openstack-meeting-409:35
*** markvoelker has quit IRC09:35
*** wojdev has quit IRC09:35
*** asselin has quit IRC09:37
*** asselin has joined #openstack-meeting-409:38
*** sarob has quit IRC09:40
*** wayne___ has quit IRC09:41
*** sarob has joined #openstack-meeting-409:42
*** sarob has quit IRC09:47
*** dims__ has joined #openstack-meeting-409:54
*** salv-orl_ has joined #openstack-meeting-410:18
*** salv-orlando has quit IRC10:20
*** salv-orl_ has quit IRC10:22
*** markvoelker has joined #openstack-meeting-410:31
*** markvoelker has quit IRC10:36
*** sarob has joined #openstack-meeting-410:43
*** sarob has quit IRC10:49
*** garyk has quit IRC11:04
*** kobis has quit IRC11:04
*** garyk has joined #openstack-meeting-411:05
*** kobis has joined #openstack-meeting-411:15
*** markvoelker has joined #openstack-meeting-411:33
*** markvoelker has quit IRC11:37
*** kobis has quit IRC11:39
*** kobis has joined #openstack-meeting-411:41
*** galstrom_zzz is now known as galstrom11:54
*** rfolco has joined #openstack-meeting-411:56
*** salv-orlando has joined #openstack-meeting-412:00
*** salv-orlando has quit IRC12:08
*** salv-orlando has joined #openstack-meeting-412:08
*** markvoelker has joined #openstack-meeting-412:15
*** marun has joined #openstack-meeting-412:17
*** salv-orlando has quit IRC12:20
*** sdake has joined #openstack-meeting-412:23
*** sdake__ has quit IRC12:23
*** ajmiller_ has quit IRC12:26
*** dims__ has quit IRC12:35
*** dims_ has joined #openstack-meeting-412:36
*** galstrom is now known as galstrom_zzz12:37
*** marun has quit IRC12:41
*** sdake has quit IRC12:48
*** sdake has joined #openstack-meeting-412:49
*** lakshmiS has joined #openstack-meeting-412:55
*** klamath has joined #openstack-meeting-413:03
*** klamath has quit IRC13:03
*** klamath has joined #openstack-meeting-413:04
*** rosmaita has joined #openstack-meeting-413:04
*** jamiem has joined #openstack-meeting-413:05
*** smc7 has joined #openstack-meeting-413:07
*** asselin_ has joined #openstack-meeting-413:07
*** cpallares has joined #openstack-meeting-413:07
*** wayne___ has joined #openstack-meeting-413:08
*** mestery_ has quit IRC13:08
*** cpallares has quit IRC13:08
*** smc7 has quit IRC13:12
*** pennerc has joined #openstack-meeting-413:13
pennerc#join openstack-glance13:15
*** pennerc has left #openstack-meeting-413:16
*** mestery has joined #openstack-meeting-413:20
*** shwetaap has joined #openstack-meeting-413:23
*** jckasper has joined #openstack-meeting-413:25
*** Nikolay_St has quit IRC13:33
*** Nikolay_St has joined #openstack-meeting-413:35
*** shwetaap1 has joined #openstack-meeting-413:42
*** shwetaap has quit IRC13:45
*** sarob has joined #openstack-meeting-413:48
*** sigmavirus24_awa is now known as sigmavirus2413:51
*** flaper87 has joined #openstack-meeting-413:52
*** sarob has quit IRC13:53
*** bharath has quit IRC13:53
*** ativelkov has joined #openstack-meeting-413:53
*** aventerav has joined #openstack-meeting-413:58
nikhil_k#startmeeting Glance14:00
openstackMeeting started Thu Mar 12 14:00:01 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
nikhil_khttps://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
kragnizyo yo14:00
kragnizo/14:00
pkoniszewskio/14:00
rosmaitao/14:00
sigmavirus24o/14:00
ativelkovo/14:00
*** Olena has joined #openstack-meeting-414:00
*** cpallares has joined #openstack-meeting-414:01
Nikolay_Stщ.14:01
Nikolay_Sto/14:01
*** TravT has joined #openstack-meeting-414:01
cpallareso/14:01
TravTo/14:01
flaper87o/14:01
Olenao/14:01
*** ivasilevskaya has joined #openstack-meeting-414:01
jokke_o/14:01
ivasilevskayao/14:01
jokke_wow ... we have good participation today :D14:01
mfedosino/14:02
nikhil_kcool, looks like a full house14:02
hemanthmo/14:02
lakshmiSo/14:02
nikhil_k#topic K314:02
*** openstack changes topic to "K3 (Meeting topic: Glance)"14:02
nikhil_khttps://launchpad.net/glance/+milestone/kilo-314:02
nikhil_kSeems like a lot of them merged14:03
nikhil_k(very recently)14:03
nikhil_kA few that we need today merged are14:03
nikhil_khttps://blueprints.launchpad.net/glance/+spec/basic-import-conversion <- point of contact flaper8714:03
jokke_ativelkov: thanks for the docstrings ... made it so much easier to follow14:03
nikhil_khttps://blueprints.launchpad.net/glance/+spec/glance-sorting-enhancements <- POC mfedosin14:03
flaper870/14:04
*** krykowski has joined #openstack-meeting-414:04
ativelkovjokke_: no problem, thanks for pointing that out,I didn't realise that docstrings are under the freeze14:04
nikhil_kA couple that seem to be in trouble may be and should get updated soon:14:04
nikhil_khttps://blueprints.launchpad.net/glance/+spec/deactivate-image <- POC hemanthm , rosmaita14:04
nikhil_khttps://blueprints.launchpad.net/glance/+spec/pass-targets-to-policy-enforcer < poc sigmavirus2414:05
sigmavirus24the spec still needs approval14:05
nikhil_kpkoniszewski: how positive are we to land https://blueprints.launchpad.net/glance/+spec/metadefs-upgrade-by-json-file ? seems a bit trixy at this point I'd say14:05
*** ajmiller has joined #openstack-meeting-414:06
jokke_I don't want to talk anyone down, but I'd like to remind that we have a week to land what we're landing14:06
nikhil_khmm, may be we'd come back to that14:06
pkoniszewskinikhil_k: implementation is ready and covers everything that was mentioned in spec14:07
nikhil_kpkoniszewski: sg, I'd leave it upto you and resp core reviewers to judge that14:08
* flaper87 is fixing the gate failure, it looks like it fails just with testr (yay?)14:08
nikhil_kLike announced earlier I'd ask for FFE on Artifacts and Catalog Index Service14:08
nikhil_kand possibly on something that does not get merged today but the chances of it being in the FFE are very narrow14:08
flaper87to be clear, the gate failure in *my* patch14:09
nikhil_kso, please update your code and ping reviewers for the same14:09
cpallaresflaper87: lol14:09
nikhil_kWe'd start fixing bugs and other things that should follow the freeze creterion before different kinds of freeze next week14:10
flaper87cpallares: :P14:10
*** qwebirc80517 has joined #openstack-meeting-414:10
sigmavirus24nikhil_k: which parts of Artifacts because that's a huge set of patches for us to review in <= 1 week14:10
nikhil_kso, docs , config deprecation, critical bugs that affect the API etc14:10
*** qwebirc80517 has quit IRC14:10
jokke_yeah ... please people if there is anything that has DocImpact, the next 7 days are critical so that we stay in good terms with docs folks :P14:10
nikhil_ksigmavirus24: It'd be good to discuss that on the code14:10
nikhil_k#info jokke_ : please people if there is anything that has DocImpact, the next 7 days are critical so that we stay in good terms with docs folks14:11
nikhil_k(seemed important :P)14:11
jokke_well we do want to give them the time to works what they deserve, right14:12
jokke_=s14:12
nikhil_kThere may be some bugs that can't be tacked in after 19th so please bring important ones to the notices of cores around you14:14
nikhil_ktackled*14:14
nikhil_k(ugh, too many typos)14:14
TravTnikhil_k: @here: pkonizewski's spec may really help us to handle migration / bug fixes on metadata definitions.14:14
ativelkovsigmavirus24: I'd prefer to land all of them, since the feature becomes functional only when the last one is merged14:14
TravTthere are a few updates (sorry I don't have bug for it) to existing definitions that we might need to do.14:14
TravTAnd his spec makes that easier to do from a migration perspective.14:14
sigmavirus24ativelkov: you do realize that's something around >=5000 lines to review when there are far more attainable features that could be merged in the amount of time it will take to effectively review and update artifacts, right?14:14
nikhil_kgotcha14:14
*** kobis has quit IRC14:15
sigmavirus24ativelkov: the specs have been approved. It isn't as if artifacts won't ever be accepted at this point14:15
ativelkovsigmavirus24: I care mostly about Kilo, not about "ever" :)14:17
jokke_Ref ativelkov's note of having the functionality in ... I think that is the most important part. If we do not have the functionality in by the review, we need to have revert plan to pull out the code that gets merged but is not in use for the release. Last thing we want is to have some half baked modules going out with release that does not work14:17
sigmavirus24ativelkov: and I care about kilo's stability, usability, and giving the best experience to the user14:17
nikhil_kjokke_: I don't think that would be bad on the migrations stuff14:17
nikhil_kI believe that it'd be bad*14:18
jokke_thus I have been wondering where these are as I thought we agreed to start pulling the artifacts in soon after k-2 but I haven't heard anything about it before now14:18
jokke_nikhil_k: what do you mean?14:18
nikhil_kI think we should not revert DB migrations14:18
jokke_sigmavirus24: ++14:19
* flaper87 back14:19
sigmavirus24jokke_: the spec was only recently approved. No one was willing to review the code when it was rebased many times a week for the duration of kilo. Review comments were almost always rebased into the past and never addressed14:19
*** qwebirc89060 has joined #openstack-meeting-414:19
jokke_sigmavirus24: well that is fully a Glance issue I've been trying to raise for whole cycle ... it seems that we do not merge specs before the code is ready14:20
nikhil_kSo, this is prolly a learning lesson, I think it would nice to mention here14:20
jokke_sigmavirus24: so spec not approved is really not an excuse to not have the code ready (or at least that has been the message over whole cycle)14:21
*** qwebirc89060 has quit IRC14:21
sigmavirus24jokke_: I agree14:21
nikhil_k#info If your feature code needs reviews, you're responsible for pinging core reviewers and get it reviewed. It'd hardly be possible for everyone to understand when something is ready and when isn't given the amount of code that is proposed and number of cores we've.14:21
nikhil_kjokke_: +1 on that!14:22
flaper87jokke_: on the flip side, some specs definitely need to be discussed before you can start coding14:22
ativelkovThe was ready by the time of mini-summit. But that's 7 dependent commits, a minor issue found in one of them was causing the whole chain to be rebased14:22
flaper87that said, I agree with you14:23
nikhil_kflaper87: I think you're right however what jokke_ is saying that you don't need them approved14:23
nikhil_kyou can discuss and iterate over the design based on the findings14:23
nikhil_kI can mention a few cases on CIS (Catalog Index Service)14:23
jokke_flaper87: my personal take is that poc is absolute max what should be done before the spec is approved and the spec should be approved as soon as the main design points have been agreed, but that does not seem to be the case14:23
lakshmiSjokke_: +114:27
nikhil_kjokke_: do you have examples where these concerns were brought up and not covered by complete design discussion?14:28
sigmavirus24I had tried reviewing artifacts several times before and after the mini-summit ativelkov I still don't think any of my review comments were ever replied to, but it's easy to lose the email notifications (and patch set numbers) when things have been rebased so frequently14:29
jokke_nikhil_k: I can grep the irc logs at some point ... At least in couple of meetings earlier on the cycle14:29
nikhil_ksure that would be good to bring it up to (Active) drivers as feedback for future specs14:29
nikhil_kThe policy has been to keep specs open until after the code has been almost agreed upon barring exceptions that involve FF, 3 year long discussions and approved BPs14:30
nikhil_kmay be we need to know where that's been not handled well14:31
ivasilevskayasigmavirus24, you are not being honest here. I personally saw to addressing all of your comments, especially the declarative framework part)14:31
*** smc7 has joined #openstack-meeting-414:31
jokke_nikhil_k: I was in understanding that the specs were supposed to be the answer for that exact issue ;)14:32
rosmaitai am really concerned about blocking artifacts at this point, especially since it is an optional service with an api marked as EXPERIMENTAL14:33
jokke_nikhil_k: for me the basic understanding was bit like a planning permission for your house ... it's bad idea to build it before you get the stamp on the paper that it's ok to do14:33
nikhil_kjokke_: ok, I don't get you there but would like to correct this situation right away so may be we'd discuss this outside of the meeting unless someone else has feedback14:33
sigmavirus24Haven't we been warned several times by outside developers that EXPERIMENTAL APIs are always well intentioned but are always a disaster?14:33
jokke_nikhil_k: sure14:33
sigmavirus24ivasilevskaya: I still haven't found those replies14:34
nikhil_ksigmavirus24: ativelkov jokke_ ivasilevskaya : I think we need to come to common understanding on this point and back and forth arguments might not help14:34
jokke_rosmaita: I do agree and I'm more than happy to get artifacts in as long as we get them in right ... I would hate to see same circus with ninja approved changes etc. what happened when we rushed glance_store in at last minute14:35
sigmavirus24ivasilevskaya: also, I didn't say they were never replied to, just that I still haven't found them and I'm tired of trying to help artifacts when all prior efforts were ignored14:35
*** marun has joined #openstack-meeting-414:35
nikhil_kso, I'd like to propose something tangible but would like to get some feedback for how we can move 'forward'?14:35
jokke_rosmaita: if it's experimental enough we probably can do non-voting testing for it and just make sure that images stays stables and usable while we landslide the code in14:36
rosmaitajokke_: i don't think it contains anything that would affect images (although it does use the same DB, different tables, though)14:37
nikhil_kjokke_: is it going to have testing that carries vote weight?14:37
ativelkovThere are no actual intersections between images and artifacts. They use the same DB (and thus the same migration chain), but that's the only shared location14:37
nikhil_k(just trying to understand)14:37
nikhil_kativelkov: and we don't have tests from tempest, neutron, etc projects in glance gate and we can ensure that until this code is stable?14:38
jokke_nikhil_k: well the point is that if we bring it in and it breaks the gate it breaks the gate for everything ... if we bring it in and it breaks non-voting tests on gate it's just our problem to get those stabilized14:39
ativelkovnikhil_k: didn't get this part. We do not have tempest tests for artifacts, as we do not have their support in the client yet14:39
nikhil_kjokke_: I'm worried that infra might not like that complication. Because everything would be in py27 run14:39
nikhil_kativelkov: yes, thanks for stating that explicitly14:40
ativelkovWe do only test artifacts as part of DB tests, functional API tests + some unit tests on particular modules such as declarative framework14:40
jokke_nikhil_k: which makes this situation difficult ... that was just proposal to point out one way around this issue14:40
nikhil_kI think that's what jokke_ is worried about no? Otherwise, I'm unsure how to break glance test suite into two parts in the gate14:41
nikhil_kAlso, not to diverge sigmavirus24's original point about code completeness14:41
jokke_nikhil_k: correct ... any of those test being flaky affects our gating from the point they get merged14:42
ativelkovCurrently all the checks are green, as far as I can see14:42
nikhil_kWhere can we discuss some of these concerns? Can we open an etherpad ativelkov sigmavirus24 jokke_ ?14:42
jokke_so we need to have either backout plan if we don't get it all right early enough or find a way not to break the gate bringing that experimental code in14:42
sigmavirus24nikhil_k: mailing list perhaps?14:42
sigmavirus24We can use an etherpad too14:42
sigmavirus24I think there is a greater wealth of knowledge and experience on the ML though14:43
nikhil_kCollaboration works so much better on etherpad and real time feedback too14:43
jokke_++14:43
ativelkovI do have etherpad for Artifact reviews at https://etherpad.openstack.org/p/Artifacts_Reviews14:43
nikhil_khm, true14:43
nikhil_khmm, may be we've sub points for each of those reviews14:43
nikhil_kI think not all of this applied to all reviews14:44
nikhil_kapplies*14:44
jokke_please if we use etherpad, mark your name/nick on the color so we know who has written and what14:44
nikhil_kok, let's move on for now14:44
sigmavirus24jokke_: what if I use someone else's name and color? =P14:44
nikhil_k#action sigmavirus24 and ativelkov to discuss etherpad and ML option for further discussion14:44
nikhil_k#topic Reviews/Bugs/Releases14:45
*** openstack changes topic to "Reviews/Bugs/Releases (Meeting topic: Glance)"14:45
jokke_sigmavirus24: I'll find you and feed you to the sharks ;)14:45
sigmavirus24jokke_: works for me14:45
nikhil_k#info One release planned for glance_store and one for client on either Mon/Tues depending on the state of the patches14:45
jokke_uuh my second favorite topic :D14:45
jokke_can we rant an hour about this as well :D14:45
nikhil_k#info we will look into the option of a stable branch for these that would be cut at Kilo RC314:46
kragnizthese will be the last for kilo?14:46
nikhil_kkragniz: may be, depending on review speed14:46
kragnizokay14:46
nikhil_kPlease add bugs and features for these in the trello board14:46
nikhil_kI'm inclined to move on unless someone wants to say anything14:47
nikhil_k#topic Other14:47
*** openstack changes topic to "Other (Meeting topic: Glance)"14:47
nikhil_khttp://lists.openstack.org/pipermail/openstack-operators/2015-March/006450.html14:48
nikhil_kDo we have a bug for it?14:48
*** sarob has joined #openstack-meeting-414:48
kragnizI don't think so14:49
jokke_I don't think so either ...14:49
nikhil_kI think we can further discuss on the bug once that opens up why 500 is seen14:49
jokke_I'm also not on the ops list so I hear forst time about this issue now14:49
jokke_first14:49
*** carl_baldwin has joined #openstack-meeting-414:49
nikhil_kyeah14:49
jokke_sounds like our grenade testing has failed14:50
sigmavirus24Oh yeah, I think I added that14:50
nikhil_kok, moving on. I think we can leave a note for them to open the bug if they are not here14:50
nikhil_ksigmavirus24: :P14:50
nikhil_kdo we have more info/logs?14:50
sigmavirus24Oh I meant I added that to the agenda14:51
sigmavirus24Not that I posted the message to -operators14:51
nikhil_klooks cryptic and we don't know the data they are pulling from DB so could be anything14:51
sigmavirus24nikhil_k: agreed. I was still curious about other people's thoughts on the matter. If there's something we can figure out how to do better14:51
nikhil_ksigmavirus24: yeah, I figured that you may know them. wrong assumption sorry..14:51
sigmavirus24I can get to know Nathan14:51
nikhil_kthanks!14:52
* sigmavirus24 goes into undercover spy mode14:52
nikhil_kGlance upgradeability14:52
TravTzhiyan: jokke_: any other core please look at: https://review.openstack.org/#/c/159532/ (Provide a way to upgrade metadata definitions).  This is the result of a conversation with Zhiyan on a previous review in K-2.14:52
jokke_sigmavirus24: I would appreciate if you could forward me some meaningful bundle of responses if any coming from that end14:52
nikhil_khttps://blueprints.launchpad.net/glance/+spec/versioned-objects14:52
nikhil_khttps://review.openstack.org/#/c/151194/14:52
nikhil_kI believe that is a review call for the cores14:52
sigmavirus24jokke_: so CC you from the start? got it. =P14:52
pkoniszewskiit's me again!14:52
jokke_sigmavirus24: if that works, good14:52
pkoniszewskiI'm aware that it is a bit late for kilo release to implement objects14:53
jokke_sigmavirus24: I've just seen the lists dropping ccs out14:53
*** numan has quit IRC14:53
*** Nikolay_St has quit IRC14:53
sigmavirus24jokke_: Yeah14:53
pkoniszewskihowever, if we manage to get this in L-release, update will be available from L to M release, it won't work from K to L, so it is imo beneficial to get this in L release14:53
nikhil_kand drivers*14:53
nikhil_kpkoniszewski: agreed. we can move this to L once we open it up14:53
jokke_pkoniszewski: quick recap ... what are you looking for with that?14:53
nikhil_kthanks to jokke_ the review is in place already14:54
*** sarob has quit IRC14:54
nikhil_kpkoniszewski: may be we can rebase it on https://review.openstack.org/#/c/163382/14:54
pkoniszewskijokke_: smooth upgrades between versions14:54
pkoniszewskinikhil_k: sure!14:55
nikhil_kcool14:55
nikhil_k#topic Open Discussion14:55
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:55
TravTwas it ever decided exactly what the rules are for an experimental API ?14:55
nikhil_kThey aren't and I think we should discuss that on [TC] flag if needed14:55
TravTI mean, if you mark an API as experimental, does that mean it doesn't have to provide a 2 release deprecation cycle?14:56
jokke_TravT: I'd say log a lot, document even more and make sure that everybody understands it's not really production stable14:56
jokke_TravT: I think that was pretty much the idea that experimental api might change more rapidly14:56
nikhil_kSo, rosmaita brought up an excellent point in the mid-cycle meetup. We need to blog about it and post in on ML, Social networks and inform peers, users, opers14:57
nikhil_kTravT: however, your original point - what are the rules? They don't seem to be defined14:57
nikhil_kand would be excellent to have14:58
TravTProbably it is up to a project to define then?14:58
nikhil_kI think we missed pointing out the context14:58
jokke_does API wg has any take on that?14:58
nikhil_kThere has been some discussion going on CIS, please see https://review.openstack.org/#/c/161621/14:58
TravTthere is some discussion ... Nikhil beat me to it.14:59
nikhil_kAPI has guidelines and not rules jokke_14:59
*** ajmiller has quit IRC14:59
nikhil_kAPI-WG* sorry ^14:59
jokke_nikhil_k: good ... do they have anything there we can directly steal and adhere to?14:59
kragnizthis had +2A before it required a rebase, so some quick reviews would be nice: https://review.openstack.org/#/c/149344/14:59
TravTit seems to me that usually when we take requests to TC that they may give back guidance, but there aren't a lot of "thou shalt" rules.15:00
nikhil_kTime to call all the discussions outside of the meeting..15:00
rosmaitaif people still have time let's continue this in openstack-glance channel, it is important to discuss15:00
*** BjoernT has joined #openstack-meeting-415:00
nikhil_k== rosmaita15:00
jokke_thanks everybody!15:00
kragnizthanks all15:00
nikhil_kThanks all!15:00
ativelkovthanks15:00
rosmaitasee you in openstack-glance!15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings"15:00
openstackMeeting ended Thu Mar 12 15:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-12-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-12-14.00.log.html15:00
*** ativelkov has left #openstack-meeting-415:00
*** ivasilevskaya has left #openstack-meeting-415:00
*** Olena has quit IRC15:01
*** wayne___ has left #openstack-meeting-415:01
*** jokke_ has left #openstack-meeting-415:02
*** rackertom has joined #openstack-meeting-415:02
*** cpallares has left #openstack-meeting-415:04
*** ajmiller has joined #openstack-meeting-415:11
*** yamahata has joined #openstack-meeting-415:17
*** MarkAtwood_ has joined #openstack-meeting-415:19
*** dannywilson has joined #openstack-meeting-415:20
*** dannywil_ has joined #openstack-meeting-415:22
*** dannywilson has quit IRC15:23
*** david-ly_ is now known as david-lyle15:23
*** rosmaita has left #openstack-meeting-415:24
*** ChuckC has joined #openstack-meeting-415:26
*** Apsu has joined #openstack-meeting-415:27
*** shwetaap1 has quit IRC15:34
*** asselin_ has quit IRC15:36
*** shwetaap has joined #openstack-meeting-415:36
*** daneyon_ has joined #openstack-meeting-415:39
*** daneyon has quit IRC15:42
*** BRD__ has joined #openstack-meeting-415:46
*** BRD__ has left #openstack-meeting-415:46
*** mattt has joined #openstack-meeting-415:53
*** asselin_ has joined #openstack-meeting-415:53
*** alextricity has joined #openstack-meeting-415:54
*** bgmccollum has joined #openstack-meeting-415:54
*** ccrouch has joined #openstack-meeting-415:57
*** b3rnard0 has joined #openstack-meeting-415:57
*** andymccr has joined #openstack-meeting-415:57
*** lakshmiS has left #openstack-meeting-415:58
*** asselin_ has quit IRC16:00
b3rnard0#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Mar 12 16:00:30 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
b3rnard0#topic Agenda & rollcall16:00
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:00
*** BRD__ has joined #openstack-meeting-416:00
b3rnard0#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:00
b3rnard0hello16:01
daneyon_hi16:01
stevellehello16:01
*** carl_baldwin has quit IRC16:01
sdakeo/16:01
sigmavirus24hello16:01
*** cloudnull has joined #openstack-meeting-416:01
cloudnulldamn. DST has me all jacked up. . .16:02
alextricityhey :)16:02
cloudnullhows it16:02
alextricityit good16:02
daneyon_DST usually gives me a 1 week hangover16:02
sdakecloudnull no dst in arizona - recommend moving ;-)16:02
ApsuRoll Call, signing in16:02
cloudnullyea DST is a mess.16:03
cloudnullUTC for the win16:03
cloudnullpresent16:03
b3rnard0presente16:03
rackertomo/16:03
Apsupresentah16:03
b3rnard0#topic Review action items from last week16:03
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:03
BjoernTlol, we all should get rid of dst16:03
cloudnull+900016:03
*** TravT has left #openstack-meeting-416:03
cloudnullcloudnull continue pinging jhesketh about creating a separate repo and other things <- yes should be in review today16:03
cloudnullnext: odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project?16:04
b3rnard0#info cloudnull continue pinging jhesketh about creating a separate repo and other things <- yes should be in review today16:04
b3rnard0don't see jesse. next!16:05
cloudnullodyssey4me16:05
*** odyssey4me has joined #openstack-meeting-416:05
odyssey4meo/16:05
cloudnullnext: odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project?16:05
cloudnull:)16:05
odyssey4meas I recall we agreed to wait until the 'manifesto' was compiled and agreed to before we went back to that16:06
*** vinod_ has joined #openstack-meeting-416:06
cloudnullokiedokie.16:06
cloudnullb3rnard0 carry that.16:06
b3rnard0i'll keep that one open16:06
cloudnullnext: git-harry help odyssey4me on blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:06
palendaeMaybe with the manifesto note16:07
b3rnard0#action odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project?16:07
odyssey4meI would suggest that we take it off the agenda, actually16:07
b3rnard0odyssey4me: your action item or the manifesto?16:07
odyssey4memy action item16:08
odyssey4methe manifesto needs to happen first, before we discuss ancillary items that fit into the grey area16:08
b3rnard0k16:08
ApsuOne does not simply not manifesto.16:08
ApsuFirst rule of manifesto club: write one.16:08
sdakewhich action item - the os package management?16:09
ApsuSoliciting feedback from the mailing list.16:09
cloudnullsdake its a topic about specific package pinning as it pertains to the OS16:09
sdakeoh right16:09
sdakeim familiar with that blueprint nm then :)16:09
cloudnullso "git-harry help odyssey4me on blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration" <- what say you git-harry and odyssey4me16:10
odyssey4meah, so I've updated the blueprint for that16:10
*** pkoniszewski has quit IRC16:10
*** git-harry has joined #openstack-meeting-416:10
odyssey4meI'm working on putting together a PoC using one of the roles to test the concept for review.16:11
cloudnullso i wanted to chat about that a bit.16:11
odyssey4meI've discovered a way to do selective merging which I think will work quite nicely for our needs.16:11
cloudnull i know that git-harry  has a review regarding the testing of hash merging in ansible16:11
daneyon_odyssey4me the #link https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration seems a lot like what tripleo uses for config file mgt.16:11
odyssey4meyeah, that's a comparitive WIP so that we can review both options to compare16:12
b3rnard0#info odyssey4me I'm working on putting together a PoC using one of the roles to test the concept for review. related to https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:12
cloudnullbut we may be able to do something similar to whats spec'd here for config diff https://blueprints.launchpad.net/openstack-ansible/+spec/dynamically-manage-policy.json16:12
git-harrycloudnull: so it doesn't break the check with hash_behaviour = merge16:12
cloudnullwithout implementing hash merging in ansible16:12
cloudnullyea it shouldn't break most of our data structures are lists and strings16:13
stevelleI had some concerns about upgrades to configurations that contain lists16:13
cloudnullbut im kinda against the idea of hash merging as it adds additional "smoke and mirrors" to the deployment process16:13
stevellesuch as middleware lists16:13
git-harryNot really, the vars just have to be considered differently16:14
ApsuWe went down this road before, when we did the first early round of playbook/role variable reorganization and layout redesign.16:14
git-harryand if we don't currently have any affected by the change it's not an issue16:14
ApsuBecause it was difficult to follow or figure out variable priorities and scopes.16:14
cloudnullgit-harry right, but that specifically goes against stated ansible best practices16:14
*** john_a_joyce has joined #openstack-meeting-416:14
odyssey4memy concern with a blanket ansible hash merge is that it affects all plays, including any others a deployer may add to the base we're providing... this is why I prefer a selective merge16:15
git-harrycloudnull: yes, but it's still configurable16:15
ApsuHash merging with multiple data sources merged at different scopes sounds like a great way to get back in that position.16:15
cloudnullgit-harry i think configurable comes at a cost of not adhering to best practices16:15
ApsuI for one would much prefer a more transparent strategy, even if it's dumber, has more steps, and requires more effort to design flexibly.16:15
git-harrybest practise is no more that a guide16:16
cloudnullthis is true16:16
cloudnullbut its a well stated guide16:17
b3rnard0do we want to get through the rest of the action items?16:17
odyssey4mestevelle the basic view that I'm aiming for is that we don't set anything in a conf file if that's the value already set in the code as a default... we only implement the bare minimum we need to put in for the system to work, and we only add stuff that we consider a best practise16:17
ApsuI don't think anyone's suggesting that the best practices are commandments from on high. However, they are expectations that others who interact with us will have. And if we don't adhere to them, we're increasing the cost of participating in our project.16:17
odyssey4meanything else a deployer wants to add, they can do in the tunables16:17
cloudnullas Apsu said in early icehouse we had a similar system which was abandoned due to multiple scopes16:17
ApsuPlus our own cost of understanding our code.16:18
Apsu^16:18
odyssey4meagreed Apsu cloudnull but the method I'm proposing actually simplifies that dramatically - the icehouse method was implementing too much16:18
stevelleodyssey4me: middlewares are particularly tricky as they would include extensions that specific deployments will want, but the defaults have been a bit volatile between releases16:18
Apsuodyssey4me: Well then we'll dig into it and see what we can all agree to.16:19
cloudnulljust to state my position, if its similar to the icehouse method and implements hash merging then I'm kind of against it.16:19
odyssey4meso for now, we're working on a PoC to review - I just haven't had much time to get it done16:19
cloudnullbut ill wait and see from the PoC16:20
cloudnullnext: BjoernT to help palendae on apt pinning16:20
palendaePretty sure that was BjoernT and odyssey4me16:20
odyssey4meah yes, that discussion has been had16:21
odyssey4mewhether that becomes part of the project goes back to the manifesto16:21
cloudnullah , thanks for the superb note taking b3rnard0 :)16:21
sdakemiddleware does what?16:21
sdake(re naifesto)16:21
sdakenano-festo :)16:21
cloudnullhahah16:21
palendaecloudnull: Part of that was my fault for doing some networking cross-chatter during the meeting16:22
sdakewould that maintain the ha state of the deployment?16:22
b3rnard0#info odyssey4me: whether that becomes part of the project goes back to the manifesto16:22
cloudnullpalendae dont take blame from b3rnard016:22
b3rnard0palendae: thanks for making me look bad16:22
Apsu+116:22
palendaewut16:22
palendaeYou do that yourself16:22
Apsu+2, approved16:22
rackertomWe're a team. We do it to each other.16:22
cloudnullnext: BjoernT to help palendae on networks16:22
odyssey4mewe have some success: https://review.openstack.org/16354416:23
b3rnard0#info odyssey4me: we have some success: https://review.openstack.org/16354416:23
odyssey4menext steps would be to get that (and any accompanying fixes) backported16:23
cloudnullsounds good.16:24
palendaeOk, that one - Bjoern and I have had some small discussions via email to look at different implenmentations, but I was mostly focused on gating this last week16:24
BjoernTYes he did get my script what we do, but I think it has nothing to do with aio or so16:24
odyssey4methanks to palendae for getting that done :)16:24
cloudnullnext:  cloudnull to create osad project manifesto as public etherpad and solicit feedback from the ML16:24
palendaeBjoernT: Yeah, I don't think that script is applicable to AIOs16:24
odyssey4mehang on, palendae BjoernT you guys are discussing https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation are you?16:25
cloudnullI've created a rough draft and I need to add some other bits post a few discussions i've had with some folks and I will have it on an etherpad and on the ML later today.16:25
palendaeodyssey4me: I was looking at what BjoernT has created for his environments to see if the blueprint would be of use to him16:25
cloudnull#topic Blueprints16:26
b3rnard0#chair cloudnull16:26
openstackCurrent chairs: b3rnard0 cloudnull16:26
cloudnull#topic Blueprints16:26
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:26
*** rfolco has quit IRC16:26
cloudnulllets go right into that .16:26
b3rnard0#info cloudnull: I've created a rough draft and I need to add some other bits post a few discussions i've had with some folks and I will have it on an etherpad and on the ML later today.16:27
cloudnullback to > https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation16:27
cloudnullpalendae do we think we have something that we can work on that can help facilitate networking hosts configurations that can be put together within a poc?16:28
b3rnard0#link https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation16:28
palendaecloudnull: Right now I'm not quite there, again, gating. Maybe I can look at that during the hackathon16:28
BjoernTIs this print targeted for aio?16:28
ApsuI should probably mention that we have network generation Ansible written and in-use for our dev Jenkins jobs.16:29
palendaeBjoernT: Not necessarily16:29
cloudnullis that something that, with the help from BjoernT, can be worked on?16:29
ApsuSo we should definitely compare.16:29
palendaeApsu: You should, and IMO, I think we should be using an upstream one16:29
cloudnullApsu BjoernT palendae16:29
ApsuAnd perhaps Jenkins is a good place to test the galaxy bits16:29
palendaeWhether we move ours out or use debops's16:29
Apsuyeah16:29
*** matrohon has quit IRC16:30
palendaeApsu: One motivation was that we had not just the Ansible jenkins stuff16:30
odyssey4mewhile I acknowledge that there is value in having this - I don't feel that this belongs in-repo for os-ansible-deployment - this comes back to the manifesto16:30
palendaeBut another in-branch one in os-a-d, too16:30
Apsuodyssey4me: I tend to agree.16:30
Apsupalendae: Yeah16:31
*** salv-orlando has joined #openstack-meeting-416:31
ApsuIt's provisioning, not deployment per se.16:31
odyssey4meI do think there's value in having a PoC done - and perhaps some sort of documentation guide on how one could use it.16:31
palendaeodyssey4me: That's fair. It may just be a thing to test16:31
BjoernTAs I said, in ops we just roll out templates for all the bridges. Having the need of configuring each interfaces inside the rpc_user_config is actually too time consuming for us. That's why I wrote this tiny script which just enumerates through the hosts and just assigns a host ip to each bridge16:31
palendaeYeah, that's another reason, IMO, having an upstream ansible galaxy role would be good16:31
odyssey4mepalendae agreed16:31
palendaeBjoernT: Fair point. I'll try to talk to you a little bit more offline this afternoon. Your script seems to solve your problem well16:32
BjoernTyeah16:32
cloudnullok. so manifesto coming soon and this BP may be mancdaz'd post that release .16:32
palendaeSure thing16:32
odyssey4mein that case, it only makes the case for the removal of any current bits we have in ansible plays/roles that deal with configuring host networking16:32
mancdazwait what?16:32
mancdazwhat did I not yet do?16:33
*** garyk has quit IRC16:33
cloudnullwe might pitch a bp16:33
cloudnullfor which i used the verb, mancdaz'd .16:33
b3rnard0mancdaz: thanks for making my action items look bad16:33
Apsuhaha16:33
*** fnaval has joined #openstack-meeting-416:34
cloudnullso next BP, odyssey4me can you go into a bit more about what your working on with regard to "https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration" ? any blockers and can we get someone else to help out on that, if applicable ?16:35
cloudnulli know that we talked about it already16:35
odyssey4mehmm, at this stage I just need to peg myself down for a few hours to convert the configurations from one method to the other16:35
cloudnullok16:35
b3rnard0#link https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:35
odyssey4methere are an awful lot of config entries to convert, so it takes time16:36
odyssey4methe actual implementation is almost trivial16:36
odyssey4meso yeah, I'll try to find some time before next week to get this PoC done16:36
cloudnullso along those lines we have "https://blueprints.launchpad.net/openstack-ansible/+spec/dynamically-manage-policy.json"16:36
cloudnullthis was coming out of alextricity team16:37
cloudnullwhich is looking to create a configurable policy json system16:37
cloudnulland doing it via an ansible module16:37
cloudnullalextricity is Daniel Curran around ?16:37
b3rnard0#link https://blueprints.launchpad.net/openstack-ansible/+spec/dynamically-manage-policy.json16:38
alextricityNot in IRC, no. I don't know what there thought was there. Sorry :/16:38
alextricityHe's in the office though16:38
*** docaedo has joined #openstack-meeting-416:38
cloudnullFrom what I understand the intent is, they want to use the base template module and allow users to provide key=value as an additional option to override and or deploy additional config within the default policy file as an option.16:40
*** smc7 has left #openstack-meeting-416:41
cloudnullIMO that seems like the most ansible centric approach to deploying extra config on templated files. additionally it seems like a module that could make its way upstream16:41
*** SridharRamaswamy has joined #openstack-meeting-416:41
cloudnulli like the intent of the bp and would love to see that in Kilo. but would also like to get some folks to review it whenever possible.16:41
odyssey4mesounds good - if the module can get built, then it'd be a far better way of handling tunable configurations16:42
cloudnulli believe Daniel Curran is already working on it, but he's not here to ask .16:42
*** daneyon has joined #openstack-meeting-416:42
cloudnullalextricity can you circle up with him on that whenever possible?16:43
stevellethe policy files are a bit different but a similar approach could be applied to configurations16:43
*** rfolco has joined #openstack-meeting-416:43
alextricitysure16:43
cloudnullstevelle for sure. i think that we can handle most of that within the configparse module in the py stdlib .16:43
cloudnullthe trick will be having that done in transport.16:44
b3rnard0#info odyssey4me: sounds good - if the module can get built, then it'd be a far better way of handling tunable configurations16:44
*** daneyon_ has quit IRC16:44
cloudnulli'd imagine something like stringIO can make that go , but i've not looked at it quite yet16:44
ApsuI have a fair bit of experience with that variety of python16:44
ApsuMaybe I could lend a hand16:45
cloudnullsure. you want to get together with alextricity ?16:45
bgmccollumconfig files that allow multiple options of the same name, but different values...how will that be accommodated in the dict?16:46
ApsuSure.16:46
palendaeMultiDict?16:46
ApsuThere's a few data structure options that can accomodate such.16:47
bgmccollumneutron.conf / service_provider as an example16:47
*** yamahata has quit IRC16:47
cloudnullok so moving on .16:48
*** carl_baldwin has joined #openstack-meeting-416:48
cloudnulli'd like to go to "Open discussion"16:48
b3rnard0#topic Open discussion16:49
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:49
cloudnullunless theres something else regarding bugs / reviews16:49
sdakequick Q16:49
palendaeI have a question - do we have a document stating our criteria for core contributors?16:49
palendaeI found https://wiki.openstack.org/wiki/TC_Membership_Models, but not sure that's generally applicable16:49
sdaketrying to organize us some design summit space for VC ODS16:49
b3rnard0oh, BjoernT wanted us to discuss a bug16:49
cloudnullshoot sdake16:49
sdakeit looks like Monday is our only option, will the core team be present monday?16:49
BjoernTyes https://bugs.launchpad.net/openstack-ansible/+bug/139938316:50
openstackLaunchpad bug 1399383 in openstack-ansible juno "General SSL support for all public endpoints including spice" [High,Confirmed]16:50
BjoernTI added a proposal for have a quick fix around public URLs that those are finally SSL16:50
palendaesdake: I think most of the cores will be in San Antonio, TX, not sure if available16:50
matttpalendae: vancouver summit16:50
cloudnulli will be16:50
palendaeNext week?16:50
palendaemattt: ^16:50
palendaeOhhh16:50
palendaenm16:50
sdakethe monday of VC ODS palendae?16:51
palendaeMy bad :)16:51
sdakeI think May 15th16:51
palendaesdake: Yeah, my mistake16:51
palendaeThought you meant next week16:51
sdakethat would be a bit short notice ;)16:51
matttsdake: we haven't locked down travel plans but i can't see people not being there monday if they are going to attend16:51
andymccrwe're highly agile ;P16:51
sdakeonce a manager said "You need to be in china in 2 days - go"16:52
b3rnard0yeah, last time i checked we were agile 1.7816:52
sdakefiguring out a visa was - an expensive expensive challenge16:52
sdakeok thanks that was all I had :)16:52
cloudnullsweet! thanks sdake16:53
sdakeno guarantees yet16:53
BjoernTyes https://bugs.launchpad.net/openstack-ansible/+bug/139938316:54
openstackLaunchpad bug 1399383 in openstack-ansible juno "General SSL support for all public endpoints including spice" [High,Confirmed]16:54
BjoernT^^ back to real stuff16:54
BjoernT:-)16:54
BjoernTWe need to get some traction around SSL and novnc .... and start tackling those bugs16:55
stevelleI feel like this may need a blueprint under our guidelines due to number of moving parts16:55
BjoernTmaybe but fixing the public endpoints, where we need ssl shouldn't be that difficult. I change the endpoints manually now16:56
odyssey4meit's not going to be that simple16:57
BjoernTIf we assume ssl offloading on the F5 yes, what else ?16:57
odyssey4meand from experience I know that implementing SSL and trying to direct internal clients to internal endpoints (non SSL) ends up finding pretty obscure bugs in the clients16:57
odyssey4meBjoernT the project doesn't assume SSL offloading - it can't16:58
Apsu^ that last part is the key point here16:58
ApsuWe can't assume an F5, or SSL offloading. But16:58
odyssey4merax may, but os-ansible-deployment needs to consider the approach more broadly16:58
BjoernTthe whole design is build on F516:58
ApsuThat doesn't mean we can't allow for the configuration flexibility.16:58
ApsuBjoernT: No it's not.16:58
ApsuThe RAX *product* is.16:58
ApsuOS-A-D the project is not.16:59
*** SridharRamaswamy has quit IRC16:59
ApsuBut I still agree we need to be able to set the endpoints more flexibly.16:59
BjoernTwell the project doesn't even include a load balancing component ....16:59
ApsuThat part is reasonable, an easy win, and solves our product deployment needs.16:59
odyssey4meI would recommend that a workaround be used for now, unless someone steps up to work on this soon.16:59
cloudnullso we're out of time.16:59
cloudnulllets bring this convo into the channel17:00
b3rnard0BjoernT: we need to continue discussing this at the bug triage17:00
palendaeb3rnard0: Or in #openstack-ansible17:00
cloudnulllets do it today if you guys have time.17:00
b3rnard0yeah17:00
ApsuMoving to #o-a17:00
palendaeNo need to wait 4 days17:00
b3rnard0#endmeeting17:00
BjoernTb3rnard0 looks like we need to talk internally first17:00
*** openstack changes topic to "OpenStack Meetings"17:00
openstackMeeting ended Thu Mar 12 17:00:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-12-16.00.html17:00
cloudnullthanks everyone17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-12-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-12-16.00.log.html17:00
sigmavirus24thanks17:00
*** odyssey4me has left #openstack-meeting-417:00
*** rackertom has left #openstack-meeting-417:01
*** daneyon has left #openstack-meeting-417:01
*** cloudnull has left #openstack-meeting-417:01
*** KLevenstein has joined #openstack-meeting-417:01
*** krykowski has quit IRC17:03
*** KLevenstein has left #openstack-meeting-417:05
*** andymccr has left #openstack-meeting-417:06
*** Swami has joined #openstack-meeting-417:07
*** yamahata has joined #openstack-meeting-417:09
*** bgmccollum has left #openstack-meeting-417:11
*** kobis has joined #openstack-meeting-417:16
*** sbalukoff has quit IRC17:22
*** evgenyf has quit IRC17:29
*** kobis has quit IRC17:33
*** ivar-lazzaro has joined #openstack-meeting-417:33
*** kobis has joined #openstack-meeting-417:35
*** BRD__ has quit IRC17:37
*** john_a_joyce has quit IRC17:41
*** shwetaap1 has joined #openstack-meeting-417:45
*** bharath_ has joined #openstack-meeting-417:45
*** shwetaap has quit IRC17:48
*** SumitNaiksatam has joined #openstack-meeting-417:59
*** SridharRamaswamy has joined #openstack-meeting-418:01
*** igordcard_ has joined #openstack-meeting-418:02
*** dims__ has joined #openstack-meeting-418:03
*** dims__ has quit IRC18:03
*** alextricity has left #openstack-meeting-418:04
*** kobis has quit IRC18:04
*** dims__ has joined #openstack-meeting-418:04
*** galstrom_zzz is now known as galstrom18:04
*** kobis has joined #openstack-meeting-418:04
*** dims_ has quit IRC18:07
*** dims__ has quit IRC18:09
*** kobis has quit IRC18:15
*** dims has joined #openstack-meeting-418:35
*** numan has joined #openstack-meeting-418:37
*** numan has quit IRC18:37
*** sbalukoff has joined #openstack-meeting-418:42
*** pkoniszewski has joined #openstack-meeting-418:43
*** SridharRamaswamy is now known as sridhar_ram18:48
*** bobmel_ has joined #openstack-meeting-419:06
*** bobmel has quit IRC19:09
*** carl_baldwin has quit IRC19:10
*** garyk has joined #openstack-meeting-419:12
*** sigmavirus24 is now known as sigmavirus24_awa19:27
*** sigmavirus24_awa is now known as sigmavirus2419:28
*** smc7 has joined #openstack-meeting-419:29
*** galstrom is now known as galstrom_zzz19:40
*** marun has quit IRC19:54
*** garyk has quit IRC20:03
*** matrohon has joined #openstack-meeting-420:10
*** carl_baldwin has joined #openstack-meeting-420:48
*** marun has joined #openstack-meeting-420:54
*** ajmiller_ has joined #openstack-meeting-421:00
*** ajmiller has quit IRC21:03
*** rfolco has quit IRC21:04
*** sarob has joined #openstack-meeting-421:06
*** blogan_ is now known as blogan21:12
*** bharath_ has quit IRC21:18
*** bharath has joined #openstack-meeting-421:19
*** aventerav has quit IRC21:22
*** bharath has quit IRC21:24
*** shwetaap1 has quit IRC21:24
*** pmesserli has joined #openstack-meeting-421:25
*** eghobo has joined #openstack-meeting-421:25
*** shwetaap has joined #openstack-meeting-421:27
*** SridharRamaswamy has joined #openstack-meeting-421:31
*** sridhar_ram has quit IRC21:32
*** SridharRamaswamy has quit IRC22:01
*** sigmavirus24 is now known as sigmavirus24_awa22:02
*** SridharRamaswamy has joined #openstack-meeting-422:04
*** sarob has quit IRC22:04
*** eghobo has quit IRC22:10
*** pkoniszewski has quit IRC22:11
*** klamath has quit IRC22:14
*** carl_baldwin has quit IRC22:18
*** SridharRamaswamy has quit IRC22:35
*** pmesserli has quit IRC22:35
*** SridharRamaswamy has joined #openstack-meeting-422:38
*** aventerav has joined #openstack-meeting-422:42
*** dims_ has joined #openstack-meeting-422:46
*** dims has quit IRC22:46
*** SridharRamaswamy has quit IRC22:47
*** SridharRamaswamy has joined #openstack-meeting-422:47
*** aventerav has quit IRC22:52
*** sdake has quit IRC23:00
*** dims_ has quit IRC23:00
*** dims has joined #openstack-meeting-423:00
*** ajmiller_ has quit IRC23:04
*** dims has quit IRC23:05
*** shwetaap has quit IRC23:06
*** SridharRamaswamy has quit IRC23:08
*** SridharRamaswamy has joined #openstack-meeting-423:08
*** kobis has joined #openstack-meeting-423:08
*** SridharRamaswamy has quit IRC23:09
*** matrohon has quit IRC23:10
*** igordcard_ has quit IRC23:12
*** kobis has quit IRC23:12
*** david-lyle is now known as david-lyle_afk23:41
*** smc7 has quit IRC23:51
*** shwetaap has joined #openstack-meeting-423:54
*** ChuckC has quit IRC23:56
*** dannywil_ has quit IRC23:59

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