Thursday, 2015-03-05

*** claired has joined #openstack-meeting-400:03
*** Rockyg has quit IRC00:07
*** markvoelker has quit IRC00:07
*** s3wong_ has joined #openstack-meeting-400:15
*** s3wong has quit IRC00:15
*** Aish has joined #openstack-meeting-400:16
*** carl_baldwin_ has joined #openstack-meeting-400:17
*** s3wong__ has joined #openstack-meeting-400:18
*** s3wong_ has quit IRC00:18
*** carl_baldwin has quit IRC00:19
*** carl_baldwin_ is now known as carl_baldwin00:19
*** wojdev has quit IRC00:19
*** s3wong__ has quit IRC00:20
*** s3wong__ has joined #openstack-meeting-400:20
*** s3wong__ has quit IRC00:24
*** s3wong has joined #openstack-meeting-400:24
*** watanabe_isao has joined #openstack-meeting-400:27
*** SridharRamaswamy has quit IRC00:34
*** carl_baldwin has quit IRC00:34
*** shwetaap has quit IRC00:40
*** SridharRamaswamy has joined #openstack-meeting-400:47
*** ajmiller has quit IRC00:49
*** galstrom_zzz is now known as galstrom00:52
*** claired has quit IRC00:55
*** chuckC_ has quit IRC00:58
*** galstrom is now known as galstrom_zzz01:03
*** carl_baldwin has joined #openstack-meeting-401:07
*** markvoelker has joined #openstack-meeting-401:08
*** SumitNaiksatam has quit IRC01:11
*** markvoelker has quit IRC01:13
*** markvoelker has joined #openstack-meeting-401:15
*** salv-orlando has quit IRC01:16
*** s3wong has quit IRC01:16
*** markvoelker has quit IRC01:20
*** hareeshp has joined #openstack-meeting-401:22
*** carl_baldwin has quit IRC01:27
*** hareeshp has quit IRC01:27
*** Aish has left #openstack-meeting-401:27
*** bobmel has quit IRC01:27
*** bobmel has joined #openstack-meeting-401:28
*** dims has quit IRC01:43
*** mwang2__ has quit IRC02:06
*** dannywilson has quit IRC02:10
*** vishwana_ has joined #openstack-meeting-402:16
*** markvoelker has joined #openstack-meeting-402:16
*** vishwanathj has quit IRC02:21
*** zz_zz_zz_zz_ja- has quit IRC02:21
*** zz_ja has joined #openstack-meeting-402:21
*** markvoelker has quit IRC02:21
*** hareeshp has joined #openstack-meeting-402:23
*** zz_ja has quit IRC02:24
*** SridharRamaswamy has quit IRC02:25
*** zz_ja has joined #openstack-meeting-402:26
*** ChuckC has joined #openstack-meeting-402:26
*** VW_ has joined #openstack-meeting-402:30
*** dims has joined #openstack-meeting-402:39
*** sarob has joined #openstack-meeting-402:42
*** VW_ has quit IRC02:44
*** sarob has quit IRC02:47
*** shwetaap has joined #openstack-meeting-402:49
*** yamahata has quit IRC03:00
*** ChuckC has quit IRC03:01
*** rm_work is now known as rm_work|away03:02
*** ChuckC has joined #openstack-meeting-403:06
*** eghobo has quit IRC03:08
*** markvoelker has joined #openstack-meeting-403:17
*** pmesserli has joined #openstack-meeting-403:20
*** pmesserli has quit IRC03:21
*** markvoelker has quit IRC03:22
*** SumitNaiksatam has joined #openstack-meeting-403:32
*** galstrom_zzz is now known as galstrom03:33
*** watanabe_isao has quit IRC03:35
*** SumitNaiksatam has quit IRC03:38
*** sigmavirus24 is now known as sigmavirus24_awa03:47
*** VW_ has joined #openstack-meeting-403:52
*** watanabe_isao has joined #openstack-meeting-403:52
*** VW_ has quit IRC03:52
*** VW_ has joined #openstack-meeting-403:53
*** shwetaap has quit IRC04:04
*** shwetaap has joined #openstack-meeting-404:05
*** SumitNaiksatam has joined #openstack-meeting-404:08
*** salv-orlando has joined #openstack-meeting-404:16
*** markvoelker has joined #openstack-meeting-404:19
*** salv-orlando has quit IRC04:21
*** yamahata has joined #openstack-meeting-404:22
*** dims has quit IRC04:22
*** markvoelker has quit IRC04:23
*** ivar-lazzaro has joined #openstack-meeting-404:24
*** ivar-laz_ has quit IRC04:27
*** ivar-lazzaro has quit IRC04:29
*** galstrom is now known as galstrom_zzz04:36
*** fnaval has quit IRC04:40
*** sarob has joined #openstack-meeting-404:44
*** sarob has quit IRC04:49
*** VW_ has quit IRC04:52
*** ajmiller has joined #openstack-meeting-404:54
*** shwetaap has quit IRC04:54
*** eghobo has joined #openstack-meeting-404:57
*** shwetaap has joined #openstack-meeting-404:59
*** carl_baldwin has joined #openstack-meeting-405:08
*** carl_baldwin has quit IRC05:08
*** shwetaap has quit IRC05:10
*** dannywilson has joined #openstack-meeting-405:11
*** dannywilson has quit IRC05:16
*** markvoelker has joined #openstack-meeting-405:20
*** dims has joined #openstack-meeting-405:23
*** markvoelker has quit IRC05:25
*** ppetit has joined #openstack-meeting-405:27
*** dims has quit IRC05:28
*** ppetit has quit IRC05:29
*** vishwana_ has quit IRC05:35
*** ppetit has joined #openstack-meeting-405:38
*** eghobo has quit IRC05:39
*** eghobo has joined #openstack-meeting-405:39
*** ppetit has quit IRC05:40
*** eghobo_ has joined #openstack-meeting-405:47
*** eghobo has quit IRC05:51
*** ttx has quit IRC06:07
*** ttx has joined #openstack-meeting-406:19
*** hareeshp has quit IRC06:19
*** markvoelker has joined #openstack-meeting-406:22
*** markvoelker has quit IRC06:27
*** kun_huang has joined #openstack-meeting-406:36
*** ppetit has joined #openstack-meeting-406:54
*** nkrinner has joined #openstack-meeting-407:07
*** salv-orlando has joined #openstack-meeting-407:14
*** salv-orlando has quit IRC07:19
*** markvoelker has joined #openstack-meeting-407:22
*** evgenyf has joined #openstack-meeting-407:24
*** salv-orlando has joined #openstack-meeting-407:27
*** markvoelker has quit IRC07:28
*** pkoniszewski has joined #openstack-meeting-407:34
*** ppetit_ has joined #openstack-meeting-407:37
*** numan has joined #openstack-meeting-407:46
*** sarob has joined #openstack-meeting-407:47
*** sarob has quit IRC07:53
*** eghobo_ has quit IRC07:58
*** mwang2 has joined #openstack-meeting-408:02
*** kobis has joined #openstack-meeting-408:03
*** mwang2 has quit IRC08:07
*** ppetit has quit IRC08:08
*** ppetit_ is now known as ppetit08:08
*** matrohon has joined #openstack-meeting-408:08
*** wojdev has joined #openstack-meeting-408:09
*** wojdev has quit IRC08:20
*** markvoelker has joined #openstack-meeting-408:25
*** markvoelker has quit IRC08:29
*** salv-orlando has quit IRC08:33
*** ttx has quit IRC08:34
*** ttx has joined #openstack-meeting-408:34
*** wojdev has joined #openstack-meeting-408:40
*** sbalukoff has quit IRC08:43
*** sbalukoff has joined #openstack-meeting-408:55
*** dims has joined #openstack-meeting-409:01
*** salv-orlando has joined #openstack-meeting-409:05
*** dims has quit IRC09:06
*** yamahata has quit IRC09:07
*** watanabe_isao has quit IRC09:15
*** wojdev has quit IRC09:24
*** markvoelker has joined #openstack-meeting-409:26
*** wojdev has joined #openstack-meeting-409:28
*** markvoelker has quit IRC09:31
*** igordcard has joined #openstack-meeting-409:49
*** sarob has joined #openstack-meeting-409:50
*** sarob has quit IRC09:54
*** salv-orlando has quit IRC09:59
*** numan has quit IRC10:08
*** markvoelker has joined #openstack-meeting-410:27
*** markvoelker has quit IRC10:31
*** dstanek has quit IRC10:33
*** wojdev has quit IRC10:44
*** wojdev has joined #openstack-meeting-410:46
*** jcook has quit IRC10:51
*** dims has joined #openstack-meeting-410:55
*** salv-orlando has joined #openstack-meeting-411:00
*** markvoelker has joined #openstack-meeting-411:28
*** wojdev has quit IRC11:32
*** markvoelker has quit IRC11:32
*** salv-orlando has quit IRC11:42
*** rfolco has joined #openstack-meeting-411:52
*** evgenyf has quit IRC12:21
*** ppetit has quit IRC12:25
*** evgenyf has joined #openstack-meeting-412:26
*** markvoelker has joined #openstack-meeting-412:29
*** evgenyf has quit IRC12:31
*** markvoelker has quit IRC12:34
*** evgenyf has joined #openstack-meeting-412:37
*** markvoelker has joined #openstack-meeting-412:38
*** ppetit has joined #openstack-meeting-412:45
*** wojdev has joined #openstack-meeting-412:50
*** sarob has joined #openstack-meeting-412:53
*** salv-orlando has joined #openstack-meeting-412:56
*** banix has joined #openstack-meeting-412:57
*** sarob has quit IRC12:57
*** ppetit has quit IRC13:07
*** jckasper has quit IRC13:08
*** ajmiller_ has joined #openstack-meeting-413:21
*** [1]evgenyf has joined #openstack-meeting-413:22
*** ajmiller has quit IRC13:24
*** evgenyf has quit IRC13:25
*** [1]evgenyf is now known as evgenyf13:25
*** bobmel has quit IRC13:27
*** bobmel has joined #openstack-meeting-413:28
*** banix has quit IRC13:31
*** ppetit has joined #openstack-meeting-413:35
*** dstanek has joined #openstack-meeting-413:46
*** dims has quit IRC13:51
*** dims has joined #openstack-meeting-413:52
*** zz_ja is now known as ja13:59
*** jckasper has joined #openstack-meeting-414:01
*** klamath has joined #openstack-meeting-414:06
*** klamath has quit IRC14:06
*** galstrom_zzz is now known as galstrom14:07
*** klamath has joined #openstack-meeting-414:07
*** shwetaap has joined #openstack-meeting-414:08
*** wojdev has quit IRC14:10
*** banix has joined #openstack-meeting-414:11
*** ppetit has quit IRC14:16
*** wojdev has joined #openstack-meeting-414:27
*** VW_ has joined #openstack-meeting-414:28
*** shwetaap1 has joined #openstack-meeting-414:28
*** shwetaap has quit IRC14:31
*** ja has quit IRC14:38
*** ekhugen has quit IRC14:38
*** pkoniszewski has quit IRC14:39
*** ekhugen has joined #openstack-meeting-414:39
*** ja has joined #openstack-meeting-414:40
*** ekhugen has quit IRC14:44
*** ja has quit IRC14:44
*** ekhugen has joined #openstack-meeting-414:45
*** ja has joined #openstack-meeting-414:46
*** wojdev has quit IRC14:46
*** chuckC_ has joined #openstack-meeting-414:46
*** chuckC_ has quit IRC14:48
*** ativelkov has joined #openstack-meeting-414:50
*** krykowski has joined #openstack-meeting-414:50
*** jckasper has quit IRC14:57
*** carl_baldwin has joined #openstack-meeting-414:57
*** ivasilevskaya has joined #openstack-meeting-414:58
*** ivasilevskaya has left #openstack-meeting-414:59
*** ppetit has joined #openstack-meeting-414:59
*** sigmavirus24_awa is now known as sigmavirus2414:59
*** lakshmiS has joined #openstack-meeting-414:59
*** ivasilevskaya has joined #openstack-meeting-414:59
*** stevelle has joined #openstack-meeting-414:59
*** krtaylor has quit IRC14:59
sigmavirus24Glance meeting?15:00
*** TravT_ has joined #openstack-meeting-415:00
ativelkovo/15:00
krykowskisounds good15:00
*** Olena has joined #openstack-meeting-415:00
kragnizyah15:00
ivasilevskayao/15:00
TravT_o/15:00
sigmavirus24Where is our fearless leader?15:00
*** jckasper has joined #openstack-meeting-415:00
lakshmiSo/15:00
Olenao/15:00
krykowskio/15:00
mfedosino/15:01
sigmavirus24nikhil_k:15:01
sigmavirus24nikhil_k:15:01
sigmavirus24;)15:01
nikhil_k#startmeeting Glance15:01
openstackMeeting started Thu Mar  5 15:01:24 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: Glance)"15:01
openstackThe meeting name has been set to 'glance'15:01
kragnizo/15:01
sigmavirus24o/15:01
stevelleo/15:01
ativelkovo/15:01
mfedosino/15:01
*** aventerav has joined #openstack-meeting-415:01
nikhil_khttps://etherpad.openstack.org/p/glance-team-meeting-agenda15:01
*** rosmaita has joined #openstack-meeting-415:01
TravT_o/15:02
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, mclaren, mfedosin, nikhil_k, rosmaita, sigmavirus24, sabari, TravT, zhiyan15:02
ivasilevskayao/15:02
nikhil_k(for all those not already here)15:02
rosmaitanikhil_k: should probably paste that in #openstack-glance15:02
rosmaitao/15:02
kragnizrosmaita: too late!15:02
nikhil_kdid too! thanks for the pointer :)15:02
Olenao/15:03
nikhil_kseems like we've a small agenda but a few other items to be covered nonetheless in today's meeting15:03
nikhil_k#topic k3 status15:03
*** openstack changes topic to "k3 status (Meeting topic: Glance)"15:03
nikhil_k(jitter beinb observed, apologize the delay in messages)15:04
nikhil_khttps://etherpad.openstack.org/p/kilo-glance-k315:04
*** mclaren has joined #openstack-meeting-415:04
nikhil_kPlease keep a special note on15:04
nikhil_kGlance images output sorting in v215:04
nikhil_kthat one needs a API minor version bump15:04
nikhil_k(for server side changes)15:05
*** wayne__ has joined #openstack-meeting-415:05
nikhil_kTravT_: did we get any more input on https://review.openstack.org/#/c/107676/ ?15:05
nikhil_kativelkov: is blocked on it15:05
TravT_Steve spent all afternoon on it.15:05
nikhil_khuh :/15:06
TravT_he's looking at different ways to handle it15:06
TravT_but I guess there isn't a reason to block it15:06
*** aventerav has left #openstack-meeting-415:06
*** ppetit_ has joined #openstack-meeting-415:06
TravT_we'll just have to figure out how to make it work.15:06
nikhil_kTravT_: ok, thanks. is he on IRC?15:06
TravT_no, i'm trying to track him down this morning.15:07
nikhil_kTravT_: may be ativelkov and mfedosin can chat with him..15:07
ativelkovThe idea behind that spec is that it is not exclusive, it's just one way of doing things. If at some point we even decide to do not do them in semver way, then no harm will be done15:07
nikhil_ksure, you all please co-ordinate and do let me know so that we can try to get that one in today15:07
*** freerunner has joined #openstack-meeting-415:07
TravT_the only troublesome part of that is the release tag handling.15:07
TravT_but that is a semver issue15:08
*** jecarey has joined #openstack-meeting-415:08
nikhil_kativelkov: the thing is pep440 might not be very neat for elastic search style (java code) but may fit in just fine..15:08
*** banix has quit IRC15:08
TravT_steve figured out a way that he thinks will work with queries, but it is kind of ugly.15:08
ativelkovnikhil_k: the proposal has some bits reserved - so we may easily (without compatibility breaking) add that pep-440-style pre-release tags easily15:08
sigmavirus24nikhil_k: pep440 is ruled out either way15:08
sigmavirus24it was an early suggestion that no one has brought up since it was excluded15:09
nikhil_kcool15:09
TravT_steve just came online...15:09
ativelkovi.e. we can do "Linux-compatible semver" (the one Monty has made for pbr) easily using the same data structure15:09
ativelkovwhich is actually a good old semver + pep440-style pre-release tags15:10
mfedosinativelkov, will it be compatible with the standard btw?15:10
*** smc7 has joined #openstack-meeting-415:10
ativelkovmfedosin: define standard :)15:10
*** jokke_ has joined #openstack-meeting-415:10
nikhil_kativelkov: makes sense, we'd get to spec then soon15:10
sigmavirus24mfedosin: all versioning standards are incompatible with each other. that's the point15:10
nikhil_kyep15:11
nikhil_k(for approval - if sigmavirus24, rosmaita have time. flavio is not here)15:11
sigmavirus24approval of the spec?15:11
mfedosinI like how they do things in pbr, if we have the same it'll be good15:12
* sigmavirus24 is working on $WORK things for the most part15:12
sigmavirus24mfedosin: that was also ruled out15:12
jokke_why pbr was actually ruled out?15:13
ativelkovThe idea was to add semver (2.0) for now and start adding support for others afterwards15:13
jokke_I think I missed that15:13
sigmavirus24mfedosin: the conclusion of the spec was to limit the versioning capability to a defined "standard" that subsets of multiple developer communities follow as opposed to a standard that entire communities follow15:13
sigmavirus24*entire developer communities15:13
sigmavirus24Because none of the discussed versioning systems support every versioning system available (although pbr's semver-pep440 hybrid can sort of work with debian/ubuntu/fedora/etc.)15:13
ativelkovjokke_: it was not completely ruled out, but the concern was that it is very openstackish standard, while artifacts are not only openstack things15:14
sigmavirus24The need for SemVer is to be able to sort in the database and because it provides constraints on the number of components in the version string15:14
sigmavirus24ativelkov: although the early consumers of artifacts will only be openstack from what I'm hearing from Jay Pipes and others15:15
jokke_ativelkov: oh? So to whom we're doing this if not OS?15:15
ativelkovso we may add pbr support as the second available format15:15
ativelkovnot only OS15:15
ativelkove.g. Murano is generic Application Catalog, so Murano Applications are written by other developers, not  from OS-community. Probably they are not written in Python15:16
jokke_ativelkov: ok, cool. That was actually the reason why I was personally pro pbr as it seems to be "the" OS way ;)15:16
ativelkovThe services which consume artifacts are OS-services. But the artifacts themselves are not15:17
ativelkoveven VM Images are not OS-specific stuff :)15:17
nikhil_k(about to say)15:17
ativelkovThere is just a single concern: "version" is a generic artifact property, but we will end up with letting artifact plugin developers to specify their preferred versioning standard. That's fine unless plugin developers decide to change the standard between different plugin versions15:18
jokke_ativelkov: but isn't it more important then that the service consumers can deal with our versioning sematics than the actual content of the artifact? (just a thought)15:18
*** pkoniszewski has joined #openstack-meeting-415:18
*** ChuckC has quit IRC15:19
nikhil_kjokke_: please remember this is experimental and extensible15:19
nikhil_k(though, good to bring it up early)15:19
ativelkovjokke_: the semantics (i.e. the actual meaning behind the version) is up to the plugin/service. We only care about sorting and filtering15:19
*** pennerc has joined #openstack-meeting-415:19
ativelkovunfurtunately different standards have different view even on sorting and filtering15:20
*** yamahata has joined #openstack-meeting-415:20
ativelkovAnyway, I'll add a spec on the generic extensibility of version field (i.e. some programmatic ways of adding new versioning standards later) - and an implementation of pbr-style versioning based on it15:21
ativelkovbut that goes to L already15:21
nikhil_kativelkov: thanks! We'd open L after (I think)15:22
ativelkovfor now we do really need semantic_version to land to global_requirements15:22
nikhil_kativelkov: the issue is we need to wait and see how it's actually being used rather then extending it in that direction now15:22
*** hemanthm has joined #openstack-meeting-415:22
sigmavirus24ativelkov: you'll need to bother requirements-core then15:22
ativelkovotherwise all our patches have -1 from jenkins, which is a bit not good15:22
nikhil_kyep15:23
ativelkovsigmavirus24: I did. They say "we need the spec approved"15:23
nikhil_ksigmavirus24: are we doing your BP in K https://blueprints.launchpad.net/glance/+spec/pass-targets-to-policy-enforcer ?15:23
sigmavirus24nikhil_k: I'll try to work on it tonight but I have $WORK things to do during the day15:23
nikhil_ksigmavirus24: yeah, I posted a comment on that review but later found our dependency with CIS15:23
sigmavirus24nikhil_k: we can get a partial implementation in but I'm not sure we'll get everything n15:23
nikhil_ksigmavirus24: ok, thanks.15:24
sigmavirus24Also there are changes in the queue that make that BP a moving target15:24
ativelkovrosmaita: I think the semver spec had a +2 from you, it got removed when I fixed couple of nits. Could you please put it back please? :)15:24
*** banix has joined #openstack-meeting-415:24
sigmavirus24I think it's the CIS changes and the activate/deactivate changes that are currently following the wrong practice15:24
rosmaitaativelkov: will do it right now15:24
nikhil_k#info From the looks, we _may_ get FFE for CIS, Artifacts15:24
mfedosinwhat about sorting?15:25
nikhil_kBut we got a thumbs up from API-WG on deactive spec!?15:26
*** jgrimm has joined #openstack-meeting-415:26
*** krtaylor has joined #openstack-meeting-415:26
*** ajmiller_ is now known as ajmiller15:26
nikhil_k(deactivate)15:26
*** jgrimm has left #openstack-meeting-415:26
sigmavirus24nikhil_k: you got acquiescence that it was Glance's choice to make15:26
sigmavirus24elmiko found old examples that worked in your favor15:26
sigmavirus24The opinion has changed since then on the ML after Flavio pointed out a few things15:27
sigmavirus24So it wasn't approval, it was "We've talked about this for three meetings and every possible solution presented was met with 'No' so we give up"15:27
rosmaitasigmavirus24: the vote should have been more carefully worded, then15:27
rosmaitathis is a big problem if we are going to re-litigate every change15:28
sigmavirus24rosmaita: if you're going to decide on something at a summit and simply want a rubber stamp, don't bring it to the API-WG15:28
sigmavirus24Also my complaints about activate/deactivate are simply in it using policy enforcer wrong (which I think is leading to this discussion)15:28
sigmavirus24(Because currently, everything is using the policy enforcer wrong)15:28
rosmaitasigmavirus24: it was very carefully discussed, and the counter agruments were not very convincing.  we can take this offline15:28
nikhil_kthanks!15:29
nikhil_kkragniz: how about your BP https://blueprints.launchpad.net/glance/+spec/swift-retry-wait ?15:29
nikhil_khttps://review.openstack.org/#/c/146437/15:29
mclarenI think I'm getting some traction on the swiftclient changes15:30
kragniznikhil_k: mclaren is currenly looking at moving that logic into swiftclient15:30
nikhil_kmclaren: can we get those -1s removed?15:30
nikhil_kkragniz: ah ok15:30
kragniznikhil_k: so that's on hold for a while15:30
nikhil_kmclaren: sorry, misunderstood15:30
nikhil_kthanks!15:30
kragnizI'll -W to make it clearer15:31
nikhil_kseems like sabari fixed the tests https://review.openstack.org/#/c/148426/ https://blueprints.launchpad.net/glance/+spec/vmware-store-multiple-datastores15:31
mclarenif the swiftclient changes go in we'll still nee[C[C[C[Cd a small bit of work on the glance side15:31
nikhil_kmclaren: that's happening in K?15:31
mclarenDunno. The changes need to merge and a new swiftclient release too15:32
mclaren(I'd like it to though)15:32
sigmavirus24It's too early for notmyname to be up probably but we should see if swift can tell us the feasibility of that15:32
jokke_mclaren: that's to get the config options passed to the swiftclient, right? (the glance change needed)15:33
*** krykowski has quit IRC15:33
mclarenIf the changes go in we can also potentially simplify the CooperativeReader fix15:33
kragnizjokke_: yes, that would happen in glance_store15:34
mclarenjokke_: removal of the retry_iter15:34
nikhil_khmm15:34
kragnizthen a glance patch to add to the default config15:34
jokke_I don't think that would be a problem even shortly after FF if they go past it15:34
nikhil_kjokke_: we cannot extend doc freeze date (I think) or it's difficult bargain15:35
jokke_nikhil_k: ah darn ... forgot them :(15:35
nikhil_k#info Please merge doc related changes on or before Mar12th15:35
jokke_nikhil_k: does Doc freeze same time as oslo?15:36
nikhil_kmclaren:  thanks.  We should decide on landing it in Kilo may be on Mar10th?15:36
mclarennikhil_k: sure15:37
nikhil_kjokke_: worth checking, but it seems 19th from this15:37
nikhil_khttps://wiki.openstack.org/wiki/Kilo_Release_Schedule15:37
jokke_nikhil_k: yeah 19th is the general freeze, oslo freezez week earlier as in 12th15:37
nikhil_kjokke_: err, forgot the mention that the string freeze is mentioned as 19th there15:37
ativelkovBTW, do we observe feature proposal freeze?15:38
jokke_*puuh* so we have two weeks instead of week with those :)15:38
nikhil_kativelkov: same as code freeze, 12th15:39
nikhil_k(per project basis)15:39
nikhil_kjokke_: :)15:39
jokke_nikhil_k: so do we freeze @ 12th or @ 19th?15:40
nikhil_k#info I've suggested ativelkov et.al. and TravT_ et.al. to make smaller changes found in their features as a part of bugs after k3 (during RCs). Excludes. security issues found, 500s founds, doc, API etc ImpactFlags missing.15:40
nikhil_kjokke_: 12th is project freeze and week for FFEs and bugs before rc115:41
nikhil_kthat's to ensure that we're not missing the entities mentioned in the info I pasted above15:41
ativelkovAgreed. We've also stopped pushing new patchsets to prevent rebases15:41
mfedosinnikhil_k, ++15:41
sigmavirus24ativelkov: thank you. Thanks makes review efforts far simpler15:42
nikhil_kplease be on the look out, this spec needs a doc change in glance (https://review.openstack.org/#/c/148426/) so does zhiyan's BP https://blueprints.launchpad.net/glance/+spec/store-capabilities15:42
nikhil_kmoving on, unless there's something more..15:43
nikhil_k#topic Reviews/Bugs/Releases15:44
*** openstack changes topic to "Reviews/Bugs/Releases (Meeting topic: Glance)"15:44
nikhil_kWe'd client and store releases recently15:44
jokke_yeii15:45
nikhil_kIf any features have client related changes that should go in Kilo please ping sigmavirus24, kragniz , zhiyan , hemanthm , flavio or me for adding in the https://trello.com/b/GFXMXxsP/openstack-glance15:45
*** jcook has joined #openstack-meeting-415:45
nikhil_kThat will ensure visibility15:45
*** galstrom is now known as galstrom_zzz15:45
jokke_or me ;)15:46
nikhil_k(That's it from me on this one)15:46
nikhil_kjokke_: yes, sorry...15:46
jokke_np15:46
nikhil_kespecially jokke_ (please send him a lot of pings) ;)15:46
nikhil_kHe's our stability hero, afterall!15:47
jokke_yeah, more I add them in there, the less I get spam stuff being changed :P15:47
sigmavirus24jokke_: heh15:47
nikhil_k#topic Open Discussion15:48
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"15:48
jokke_I have couple of things I forgot to put on the agenda15:48
jokke_1) Log Working Group had first meeting yesterday, looking for liaisons in projects ... I marked myself down already ... if someone else insists feel free to change :D15:49
jokke_2) With the logging please, please, please read this: http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html15:49
*** krtaylor has quit IRC15:50
jokke_3) As it does not seem to have effect on the participants could we please stop this 1hr alternating on the meetings? It's just annoying and confusing15:50
rosmaitajokke_: +1 to all15:51
hemanthmI don't mind as long as nikhil_k is send courtesy reminders :)15:51
nikhil_k#startvote can we please stop this 1hr alternating on the meetings?15:51
openstackBegin voting on: can we please stop this 1hr alternating on the meetings? Valid vote options are Yes, No.15:51
openstackVote using '#vote OPTION'. Only your last vote counts.15:51
nikhil_k#vote Yes15:51
rosmaita#vote Yes15:51
hemanthm#vote yes15:51
ativelkov#vote yes15:51
jokke_#vote Yes15:52
mfedosin#vote Yes15:52
kragniz#vote yes15:52
ativelkovIf we stop, what is the fixed time then?15:52
ativelkovBoth are ok for me, just curious15:52
nikhil_kativelkov: 14.30 UTC?15:52
jokke_Either one of the existing ones is better than current\15:52
mclarenI think one was better for Zhi Yan?15:53
lakshmiS#vote yes15:53
mclarenbut can't remember15:53
ivasilevskaya#vote Yes15:53
Olena#vote Yes15:53
jokke_I think Zhi Yan prefers as early as possible due to TZ15:53
kragnizmclaren: I'm guessing the earlier one15:53
mclarenok15:53
*** cloudnull has joined #openstack-meeting-415:54
nikhil_kI think TravT_ is affected but is being overwhelmed by majority15:54
TravT_In a week time changes15:54
TravT_so it won't be so bad15:54
nikhil_ksigmavirus24: lakshmiS TravT_ ^15:54
nikhil_kah ok15:54
jokke_TravT_: even better then ;)15:54
nikhil_k#endvote15:55
sigmavirus24#vote yes15:55
openstackVoted on "can we please stop this 1hr alternating on the meetings?" Results are15:55
nikhil_koops15:55
sigmavirus24;)15:55
* sigmavirus24 is distracted this morning15:55
ativelkovSeems like the bot prefers alterations15:55
nikhil_k#action nikhil_k to send email to ML for readjusting the meeting time to 14:00UTC15:55
kragnizativelkov: the bot just can't make up its mind15:55
jokke_that was all from me this time15:55
mfedosinfolks, Zhi Yan asked me to know, is there a possibility to direct access glance_store from Nova as it mentioned in the spec https://blueprints.launchpad.net/glance/+spec/create-store-package15:56
jokke_I'd like to also assume that the review cleanup is ok as no more e-mails for over 2 weeks now on the mailchain ;)15:56
mfedosinbecause I don't know how to show it in the developer documentation15:57
jokke_mfedosin: the lib is out there, Nova can use it if they want to15:57
*** b3rnard0 has joined #openstack-meeting-415:57
nikhil_kemail from jokke_ about Log Working Group, http://osdir.com/ml/openstack-dev/2015-03/msg00328.html15:57
sigmavirus24jokke_: have you not seen the one John Griffith started about auto-abandon?15:57
mfedosinjokke_, nice, thank you15:57
kragnizjokke_: have you read the other threads on it?15:57
sigmavirus24jokke_: the community seems mostly against it15:57
sigmavirus24s/mostly/majority/15:57
*** odyssey4me has joined #openstack-meeting-415:58
kragnizjokke_: (last email about half an hour ago)15:58
jokke_sigmavirus24: I'd disagree ... the few loud one is community seems to be drumming the same message against it ;)15:58
jokke_"ones are" even15:58
kragnizanyway, we're out of time15:59
TravT_thanks everyone16:00
jokke_thnx!16:00
*** Sam-I-Am has joined #openstack-meeting-416:00
mclarenciao16:00
pennercthnx16:00
*** mclaren has quit IRC16:00
kragnizthanks16:00
nikhil_kThanks all!16:00
*** pennerc has left #openstack-meeting-416:00
nikhil_k#endmeeting16:00
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."16:00
openstackMeeting ended Thu Mar  5 16:00:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-05-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-05-15.01.txt16:00
*** ativelkov has left #openstack-meeting-416:00
*** jokke_ has left #openstack-meeting-416:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-03-05-15.01.log.html16:00
*** BjoernT has joined #openstack-meeting-416:00
*** TravT_ has quit IRC16:00
*** Olena has quit IRC16:00
b3rnard0hello16:00
*** lakshmiS has quit IRC16:00
*** mattt has joined #openstack-meeting-416:01
d34dh0r53good morning b3rnard016:01
cloudnullhello16:01
mattt\o16:01
*** ivasilevskaya has left #openstack-meeting-416:01
odyssey4meo/16:02
BjoernTHi16:02
*** krtaylor has joined #openstack-meeting-416:02
palendaeMorning16:02
d34dh0r530/16:02
b3rnard0#startmeeting OpenStack Ansible Meeting16:02
openstackMeeting started Thu Mar  5 16:02:53 2015 UTC and is due to finish in 60 minutes.  The chair is b3rnard0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:02
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:02
*** pkoniszewski has quit IRC16:03
b3rnard0#topic Agenda & rollcall16:03
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:03
odyssey4meo/ :)16:03
cloudnullpresent16:03
b3rnard0#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:03
*** smc7 has quit IRC16:03
b3rnard0i be present16:03
Sam-I-Amyo16:04
*** andymccr has joined #openstack-meeting-416:04
stevellepresent16:04
sigmavirus24o/16:05
*** shwetaap1 has quit IRC16:05
sigmavirus24<< "present"16:06
b3rnard0#topic Review action items from last week16:06
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:06
b3rnard0cloudnull continue pinging jhesketh about creating a separate repo and other things -- updates?16:07
*** rosmaita has left #openstack-meeting-416:07
cloudnulli pinged , i know what to do, i've not done it because i took time off.16:07
cloudnullso i failed.16:07
cloudnull:)16:07
b3rnard0np. i'll keep it open as an action item16:08
cloudnullill try and get everything in by end of week16:08
sigmavirus24we must all do the communal dance of shame in a circle around cloudnull16:08
cloudnullhahaha16:08
*** carl_baldwin has quit IRC16:08
odyssey4mehaha!16:08
b3rnard0#action cloudnull continue pinging jhesketh about creating a separate repo and other things16:08
b3rnard0odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project? -- updates?16:09
odyssey4meMy bad - haven't done it. I'll get it done this evening.16:09
b3rnard0k, keeping that one open as well16:10
odyssey4meI'll join cloudnull in the walk of shame. :p16:10
Sam-I-Amslackers16:10
b3rnard0#action odyssey4me Solicit feedback from the mailing list as to whether os package management should be part of the project?16:10
* cloudnull joining the dance of shame 16:10
*** smc7 has joined #openstack-meeting-416:10
b3rnard0git-harry help odyssey4me on blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration -- updates16:10
odyssey4meI did update the blueprint though. :)16:10
b3rnard0don't see mister harry on here. did you received aid from him on this task?16:11
*** smc7 has left #openstack-meeting-416:11
odyssey4meNo update from me - git-harry did do some investigation, but I think got diverted. We'll have to carry it.16:12
*** git-harry has joined #openstack-meeting-416:12
b3rnard0k16:12
b3rnard0#action git-harry help odyssey4me on blueprint https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:12
b3rnard0finally16:12
git-harryodyssey4me: has left the building.16:13
b3rnard0andymccr to fix https://bugs.launchpad.net/openstack-ansible/+bug/1424808 in 10.1.3 -- updates? i'm assuming this is still in your queue16:13
sigmavirus24git-harry: just in time to dodge information16:13
openstackLaunchpad bug 1424808 in openstack-ansible juno "Add nova configuration options image_cache_manager_interval" [Low,Triaged] - Assigned to Andy McCrae (andrew-mccrae)16:13
andymccrb3rnard0: its been fixed/pr'd16:13
sigmavirus24b3rnard0: there's an open review for that iirc16:13
andymccri think its not merged yet because we had some issues yesterday but its pending merge16:13
b3rnard0andymccr: awesome. at least we got one action item resolved!16:13
andymccrjust doing my job b3rnard0. just doing my job16:14
* b3rnard0 hands andymccr a beer16:14
odyssey4meIt merged into master within the last half hour I think.16:14
odyssey4meIt needs a back port now.16:14
andymccrjuno backport already merged16:14
*** rackertom has joined #openstack-meeting-416:14
cloudnull#link: https://review.openstack.org/#/c/159929/16:15
b3rnard0we don't have a lot on the agenda today so i'm going straight to the bug we were still triaging this Tuesday. any thoughts, cloudnull?16:15
cloudnull^ merged just a few min ago .16:15
cloudnullsounds good. then to bps16:15
b3rnard0#topic Bugs16:16
*** openstack changes topic to "Bugs (Meeting topic: OpenStack Ansible Meeting)"16:16
b3rnard0#link https://bugs.launchpad.net/openstack-ansible/+bug/142665516:16
openstackLaunchpad bug 1426655 in openstack-ansible juno "neutron_agents_container GnuTLS recv error" [Undecided,Incomplete]16:16
b3rnard0i think we didn't finish triaging this bug16:16
cloudnulllooks like it was a transient issue16:16
Sam-I-Amdarn transients16:17
BjoernTright we dropped this bug pretty much16:17
odyssey4meTransient or a host issue.16:17
*** ChuckC has joined #openstack-meeting-416:17
cloudnullthe guy nexus indicated it was resolved on redeploy?16:17
odyssey4meThe reporter has pretty much indicated as much.16:17
*** ChuckC has quit IRC16:18
*** fnaval has joined #openstack-meeting-416:18
cloudnullso i'd say mark it as invalid and leave it as such . thoughts?16:18
*** ChuckC has joined #openstack-meeting-416:18
odyssey4meAgreed.16:18
stevelle+116:18
cloudnulldone.16:19
b3rnard0#chair cloudnull16:19
openstackCurrent chairs: b3rnard0 cloudnull16:19
b3rnard0just in case i cut out as my internet has been spotty16:19
cloudnullif there are no other bugs that we want to talk about lets move on to blueprints.16:19
b3rnard0#topic Blueprints16:20
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:20
cloudnullwe have 4 open bps that are marked for discussion16:20
cloudnullso lets talk about those.16:20
odyssey4meWe could do with more blueprints. :)16:20
cloudnullpalendae you around ?16:20
*** shwetaap has joined #openstack-meeting-416:21
palendaecloudnull: yep16:21
cloudnullhows https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation16:21
b3rnard0#link https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation16:21
palendaeStalled for now as I work on gating stuff.16:21
cloudnullkk . can some of our cores review and comment on it.  I'll set aside some time today to do the same.16:22
odyssey4meWill do.16:22
palendaeI think the blueprint itself is fine from my POV, but no implementation happening right now16:23
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/apt-package-pinning16:23
*** sdake_ has joined #openstack-meeting-416:23
stevellepalendae: do you have an idea of how complete that role is for our needs today?  80%?16:23
sdake_o/16:23
BjoernTI actually wrote a script to setup the bridges, I don't see it as critical anymore (network-generation)16:23
cloudnullodyssey4me hows that coming a long ?16:23
b3rnard0#action odyssey4me cloudnull to provide feedback/review on https://blueprints.launchpad.net/openstack-ansible/+spec/improved-network-generation16:23
cloudnullhey sdake_16:23
palendaeBjoernT: Cool. I'd like to do it still, but good to know16:23
odyssey4meWaiting for input. The blueprint wash prayed after last week's discussion.16:23
sdake_apologies for being late, off by 1 error :(16:24
odyssey4meA standing question is whether this even belongs in the project.16:24
cloudnullno worries sdake_ , welcome :)16:24
odyssey4meThe mission of the project needs clarity.16:24
ApsuBjoernT: We've got probably 6 scripts/various plays/approaches by different folks for doing network config. I wrote an Ansible module I was trying to upstream called "interfaces" that would allow reconfiguration of the file, for instance16:24
ApsuI think palendae's goal was to pick something as a common point to build from16:25
palendaeApsu: Correct16:25
odyssey4meIs it focused on deploying openstack, or a full environment which is production ready?16:25
palendaeApsu: We nuked the interfaces stuff that was in the repo because it was poorly documented and had a bunch of flaws16:25
BjoernTpalendae: apsu: We are so "lazy" now, not even wanting to specify the interfaces . So I did automate it based on that each node has a fixed offset16:25
BjoernTto specify each interface in jason is even too much, we want to keep the configs the same across all deployments so 172.29.236.51 is infra01, 52 infra02 and so on16:26
BjoernTthen it's easy to automate16:26
BjoernTwe can talk about this offline16:26
cloudnullso BjoernT can you sync up with palendae  on that16:26
palendaeYes please :)16:26
BjoernTyepp16:26
odyssey4meI'm confused. Are we talking about the network configs blueprint now, or apt pinning?16:26
palendaeodyssey4me: apt pinning, sorry16:26
cloudnulland now back to apt pinning :)16:27
b3rnard0#action BjoernT to help palendae on apt pinning16:27
stevelleodyssey4me: there may be an "it depends" answer on whether this belongs or not.  It would help gating and lets the project find a tempo that matches the larger OpenStack community, but different groups may want a different solution16:27
BjoernTb3rnard0: ok16:28
*** evgenyf has quit IRC16:28
odyssey4meI've come to a conclusion that a deployed can do  very good job of solving this problem without pinning an instead using a frozen apt repo. Less moving parts.16:28
palendaeb3rnard0: Actually BjoernT will be working with me on networks, we hijacked the discussion16:28
b3rnard0lol k16:28
Sam-I-Amnetworks, pinnings, its all the same16:28
BjoernTI do apt pinning too, lol16:28
odyssey4me*deployer16:28
b3rnard0#action BjoernT to help palendae on networks16:28
*** salv-orlando has quit IRC16:29
palendaeodyssey4me: So are you thinking the deployers are taking responsibilities for freezing the repos?16:29
palendaeOr providing a repo freezer in place of the pinning?16:29
*** chuckC_ has joined #openstack-meeting-416:29
git-harryDo we have anything that defines the scope of this project?16:29
odyssey4meYeah. It makes more sense than burdening the project with keeping track of packages to pin.16:29
*** chuckC_ has quit IRC16:29
sdake_palendae in our models, we belive that to be the case16:29
*** daneyon has joined #openstack-meeting-416:30
sdake_our = kolla project models16:30
odyssey4meFor RPC specifically I have a solution and am soliciting feedback, but that's outside of this project's remit IMO.16:31
palendaesdake_: So deployers responsible for freezing in your model?16:31
sdake_palendae ya the service providers or their vendors16:32
odyssey4megit-harry: not to my knowledge, and I think we need to define it16:32
git-harryodyssey4me: yup, it might short circuit some of these conversations16:32
matttsdake_: my personal opinion is that is the correct approach16:33
odyssey4mePerhaps it'd be useful to get some help to facilitate a discussion around it?16:33
cloudnullyes that'd be helpful.16:34
odyssey4meSomeone who has helped put together charters for openstack projects, and is also outside of rax.16:34
palendae^16:34
odyssey4mePerhaps ttx can assist or recommend?16:35
git-harry?16:35
git-harryNot sure that's what we need16:35
sdake_openstack calls it a manifesto16:35
sdake_but imo you do that after 6 months of open dev16:35
git-harryWe just need to define the technical scope of the project16:35
sdake_otherwise it shuts out contributors16:35
BjoernTI think we from support have a  view on apt pinning, can we talk about it in a meeting?16:35
palendaeI'd like to get alternative views on it, separate from RPC16:35
palendaeRPC is a deployer, os-ansible-deployment/openstack-ansible is what they deploy16:36
BjoernTThat's fine16:36
palendaeBut yeah BjoernT, we can have internal meetings16:36
sdake_is rpc a repo?16:36
palendaesdake_: Rackspace Private Cloud16:36
sdake_oh rackspace private cloud right16:36
sdake_ya got it sorry duh ;)16:36
odyssey4meBjoernT: if we could discuss that separately that'd be great - you have an email from me on the topic16:36
BjoernTye sI do16:37
cloudnullso lets put together a an etherpad regarding project scope and solicit feedback on the ml regarding its contents.16:37
d34dh0r53+116:37
odyssey4meGood plan. :)16:38
b3rnard0anyone in particular who will do that?16:38
cloudnullill put together the draft. but it should be a living doc .16:38
odyssey4meI think perhaps that should be done an agreed to before we go further with any blueprint feedback discussions.16:38
*** salv-orlando has joined #openstack-meeting-416:39
stevelleI'm concerned that might unnecessarily block other work16:39
BjoernTyea I agree16:39
odyssey4meIt doesn't have to stop anything, but it is a crucial guide for deciding how to approach solving the problems.16:40
stevelleI agree, for the pinning blueprint, we need to answer the question of scope.  I am not sure we do for networking or configuration16:40
*** freerunner has left #openstack-meeting-416:41
odyssey4meWe can still put together ideas and work on them.16:41
cloudnull#action cloudnull to create osad project manifesto as public etherpad and solicit feedback from the ML16:41
odyssey4meTunable configs is clearly openstack specific, so yes.16:42
cloudnulli agree we can still work on BPs and discus them without having a specific guideline doc in place.16:42
cloudnullso lets talk about https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:43
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/tunable-openstack-configuration16:43
odyssey4meNetwork config is a grey area - but if it's implemented in a way that doesn't bind the deployer to using it, then it should be fine.16:43
cloudnullodyssey4me have you and git-harry though more about this ?16:44
cloudnullhe was going to help on that right? or am i remembering incorrectly ?16:44
git-harrycloudnull: I've had a look at it16:44
git-harryI think we should set hash_behaviour = merge16:45
cloudnullwhy?16:45
*** carl_baldwin has joined #openstack-meeting-416:45
Sam-I-Amodyssey4me: yeah. different people are going to kick their hosts differently.16:45
git-harryso the config can be sorted in the vars and dicts don't get replaced16:45
git-harrythen we can have simple templates that spit it out16:46
cloudnullbut that can and will effect the entire stack. so setting that will likely have consequences across the board.16:47
cloudnullto quote ansible docs "We generally recommend not using this setting unless you think you have an absolute need for it, and playbooks in the official examples repos do not use this setting"16:47
Sam-I-Amodyssey4me: as an open project, we really cant dictate what people do with their networking16:47
git-harryYes, it may16:47
git-harryso we would need to test16:47
cloudnulldo you think you have cycles to go and see if that makes the world explode? and can you put together an example of the hash merge for config?16:48
odyssey4meIt's either that or we have vars for our defaults and a specific dict for uncatered-for tuna lea.16:48
odyssey4me*tunables16:48
cloudnullthat'd be helpful if we can make that go without major impact.16:48
git-harryI have started doing that already16:49
*** krtaylor has quit IRC16:49
git-harryI'll try and finish it by next week. The broken gate was blocking me yesterday16:50
*** yamahata has quit IRC16:50
cloudnullyes i think the broken gate was blocking all of OS yesterday :)16:50
git-harryaye16:50
cloudnullok. so git-harry you are working on a different thread regarding the same functionality as it pertains to that BP?16:51
cloudnullso as to not duplicate efforts can you and odyssey4me sync up on that, if you've not already ?16:52
git-harrycloudnull: yes, I'm testing a different implementation16:52
odyssey4meYeah, can do.it might actually be useful to have two implementation options to compare.16:53
cloudnulli agree.16:53
odyssey4meNot full ones, obviously. Just a single service.16:53
cloudnullso we have 8 min left. lets open up the discussion to anything.16:53
sdake_may I ask a Q16:53
sdake_regarding scope16:53
cloudnullshoot.16:53
b3rnard0#topic Open discussion16:53
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:54
sdake_I see ansible play books deploy16:54
sdake_would the project be open to "maintaining" the deployment16:54
sdake_in otherwords, validating the ha and making sure things stay operational16:54
sdake_I guess the correct term for this would be orchestration, whereas os-ansible-deploy is workflow16:55
odyssey4meI'm not sure I understand.16:55
sdake_so have 3 controller nodes16:55
sdake_nova dies on controler node16:55
palendaesdake_: Are you thinking something like monitoring?16:55
sdake_want to validate that16:55
sdake_ya all about HA16:55
sdake_but I dont want to just monitor I want to take corrective action16:55
sdake_is that in or out of scope?16:55
palendaeSure16:55
cloudnulli think adding in the functionality to operationally maintain the stack makes sense.16:55
palendaeI think right now that's out of scope16:55
palendaeIn terms of automatically correcting16:56
odyssey4meYou mean add deeper functional testing?16:56
palendaeBut we also haven't formally laid down a scope16:56
sdake_so if someone came along and wrote that code, it would be -2? :)16:56
palendaeodyssey4me: I think this is around keeping production systems up16:56
sdake_right keeping the production system in an operational state via monitroing and corrective ha action16:56
cloudnullsdake_ no, I would not automatically -2. but depending on the impact i may ask for a blueprint.16:57
odyssey4meOk, so more of adding stuff like monit to check and auto respond?16:57
git-harryI'd say that was out of scope of this project16:57
sdake_ok process is fine, just curious if that is like "nah that is someone elses problem" :)16:57
matttsdake_: yeah i'd think that's more in the deployer's realm16:57
sdake_ya monit is an option16:57
sdake_ok thanks, that was the only scope question I had - actually I have a slew more but we are out of time :)16:58
odyssey4meI would say that adding an external Ansible role which does that in an example play or readme would be great.16:58
cloudnull+116:58
odyssey4meBut not add it in this code tree.16:58
b3rnard0sdake_: if you have more agenda items to discuss, feel free to add them to the agenda meeting for next week16:58
stevellesdake_: I'd like to see the other scope questions as they may help with one of the action items16:58
matttyeah i'd love to see that work w/ os-ansible-deployment, but i'd also think it'd be an external component16:58
Apsusdake_: Since most of the project participants are currently the same folks using this for our employer's product, it's definitely a challenge we're tackling. But where we draw the scope line and how we decide inclusion are in definite need of discussion and nailing down.16:59
sdake_sure we can follow up in #openstack-ansible channel if you like16:59
sdake_^^ b3rnard016:59
ApsuDefinitely do ask those questions in some form so we can get that input16:59
cloudnullyup we're out of time.16:59
matttApsu: yeah nothing at this point is a hard no, that's for sure16:59
cloudnull#endmeeting17:00
*** openstack changes topic to "Zuul check queue stuck due to reboot maintenance window at one of our cloud providers - no need to recheck changes at the moment, they won't move forward."17:00
openstackMeeting ended Thu Mar  5 17:00:05 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-05-16.02.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-05-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-05-16.02.log.html17:00
b3rnard0thanks everyone17:00
cloudnullthanks everyone !17:00
Sam-I-Amgood stuff17:00
*** Sam-I-Am has left #openstack-meeting-417:00
*** krtaylor has joined #openstack-meeting-417:01
*** git-harry has left #openstack-meeting-417:01
*** dannywilson has joined #openstack-meeting-417:01
*** rackertom has left #openstack-meeting-417:06
*** vishwanathj has joined #openstack-meeting-417:06
*** vishwanathj has quit IRC17:06
*** galstrom_zzz is now known as galstrom17:08
*** dannywilson has quit IRC17:11
*** dannywilson has joined #openstack-meeting-417:11
*** yamahata has joined #openstack-meeting-417:12
*** odyssey4me has left #openstack-meeting-417:13
*** wayne__ has quit IRC17:15
*** kobis has quit IRC17:17
*** yamahata has quit IRC17:18
*** yamahata has joined #openstack-meeting-417:19
*** igordcard has quit IRC17:20
*** nkrinner has quit IRC17:22
*** vishwanathj has joined #openstack-meeting-417:26
*** krtaylor has quit IRC17:31
*** matrohon has quit IRC17:34
*** krtaylor has joined #openstack-meeting-417:37
*** carl_baldwin_ has joined #openstack-meeting-417:38
*** carl_baldwin has quit IRC17:40
*** stevelle has left #openstack-meeting-417:42
*** carl_baldwin has joined #openstack-meeting-417:42
*** carl_baldwin_ has quit IRC17:43
*** galstrom is now known as galstrom_zzz17:50
*** galstrom_zzz is now known as galstrom17:58
*** ivar-lazzaro has joined #openstack-meeting-417:59
*** ivar-lazzaro has quit IRC17:59
*** ivar-lazzaro has joined #openstack-meeting-417:59
*** dannywilson has quit IRC18:00
*** mwang2 has joined #openstack-meeting-418:01
*** sbalukoff has quit IRC18:06
*** eghobo has joined #openstack-meeting-418:08
*** ppetit_ has quit IRC18:14
*** SridharRamaswamy has joined #openstack-meeting-418:15
*** SumitNaiksatam has quit IRC18:24
*** ppetit_ has joined #openstack-meeting-418:25
*** SumitNaiksatam has joined #openstack-meeting-418:28
*** ppetit has quit IRC18:29
*** ppetit_ is now known as ppetit18:29
*** SumitNaiksatam has quit IRC18:43
*** krtaylor has quit IRC18:45
*** cloudnull has left #openstack-meeting-418:45
*** SumitNaiksatam has joined #openstack-meeting-418:48
*** galstrom is now known as galstrom_zzz18:49
*** carl_baldwin_ has joined #openstack-meeting-418:52
*** carl_baldwin has quit IRC18:53
*** carl_baldwin_ is now known as carl_baldwin18:53
*** wojdev has joined #openstack-meeting-418:54
*** ppetit_ has joined #openstack-meeting-418:58
*** krtaylor has joined #openstack-meeting-418:59
*** dims_ has joined #openstack-meeting-419:01
*** dims has quit IRC19:04
*** galstrom_zzz is now known as galstrom19:05
*** ivar-lazzaro has quit IRC19:05
*** SumitNaiksatam has quit IRC19:06
*** SumitNaiksatam has joined #openstack-meeting-419:08
*** wojdev has quit IRC19:09
*** sdake_ has quit IRC19:09
*** sdake_ has joined #openstack-meeting-419:10
*** carl_baldwin_ has joined #openstack-meeting-419:11
*** ppetit_ has quit IRC19:12
*** carl_baldwin has quit IRC19:13
*** carl_baldwin_ is now known as carl_baldwin19:13
*** sbalukoff has joined #openstack-meeting-419:17
*** wojdev has joined #openstack-meeting-419:17
*** b3rnard0 has left #openstack-meeting-419:22
*** ivar-lazzaro has joined #openstack-meeting-419:28
*** smc7 has joined #openstack-meeting-419:29
*** dannywilson has joined #openstack-meeting-419:32
*** rm_work|away is now known as rm_work19:34
*** ppetit has quit IRC19:38
*** wojdev has quit IRC19:43
*** dims_ has quit IRC19:44
*** jckasper has quit IRC19:44
*** dims has joined #openstack-meeting-419:45
*** jckasper has joined #openstack-meeting-419:45
*** wojdev has joined #openstack-meeting-419:48
*** vishwanathj has quit IRC19:48
*** sarob has joined #openstack-meeting-419:56
*** sarob has quit IRC19:57
*** sarob has joined #openstack-meeting-419:58
*** wojdev has quit IRC19:58
*** sarob has quit IRC20:00
*** sarob has joined #openstack-meeting-420:01
*** vishwanathj has joined #openstack-meeting-420:03
*** wojdev has joined #openstack-meeting-420:03
*** wojdev has quit IRC20:22
*** carl_baldwin_ has joined #openstack-meeting-420:36
*** carl_baldwin has quit IRC20:38
*** carl_baldwin_ is now known as carl_baldwin20:38
*** ivar-laz_ has joined #openstack-meeting-420:38
*** ivar-lazzaro has quit IRC20:41
*** ajmiller has quit IRC20:43
*** matrohon has joined #openstack-meeting-420:44
*** david-lyle_afk has joined #openstack-meeting-420:45
*** david-lyle_afk has quit IRC20:47
*** david-lyle_afk has joined #openstack-meeting-420:47
*** ivar-laz_ has quit IRC20:58
*** ivar-lazzaro has joined #openstack-meeting-420:59
*** salv-orlando is now known as ihate-salv-orlan20:59
*** ivar-lazzaro has quit IRC21:00
*** ivar-lazzaro has joined #openstack-meeting-421:00
*** ihate-salv-orlan is now known as salv-orlando21:00
*** ibiris is now known as ibiris_away21:03
*** david-lyle_afk is now known as david-lyle21:03
*** rfolco has quit IRC21:10
*** shwetaap has quit IRC21:13
*** shwetaap has joined #openstack-meeting-421:15
*** carl_baldwin_ has joined #openstack-meeting-421:23
*** carl_baldwin has quit IRC21:24
*** carl_baldwin_ is now known as carl_baldwin21:24
*** jecarey has quit IRC21:41
*** SumitNaiksatam has quit IRC21:48
*** SumitNaiksatam has joined #openstack-meeting-421:50
*** ivar-lazzaro has quit IRC21:53
*** wojdev has joined #openstack-meeting-421:55
*** ivar-lazzaro has joined #openstack-meeting-421:57
*** wojdev has quit IRC22:00
*** ivar-lazzaro has quit IRC22:01
*** ja is now known as zz_ja22:08
*** wojdev has joined #openstack-meeting-422:14
*** jecarey has joined #openstack-meeting-422:17
*** ivar-lazzaro has joined #openstack-meeting-422:24
*** ivar-lazzaro has quit IRC22:32
*** eghobo has quit IRC22:33
*** wojdev has quit IRC22:34
*** wojdev has joined #openstack-meeting-422:43
*** smc7 has quit IRC22:53
*** banix has quit IRC22:56
*** daneyon_ has joined #openstack-meeting-422:56
*** daneyon has quit IRC22:59
*** shwetaap has quit IRC23:03
*** jckasper has quit IRC23:04
*** fnaval has quit IRC23:13
*** fnaval has joined #openstack-meeting-423:14
*** ChuckC is now known as ChuckC_23:19
*** VW_ has quit IRC23:21
*** daneyon has joined #openstack-meeting-423:24
*** VW_ has joined #openstack-meeting-423:25
*** ChuckC_ is now known as ChuckC23:26
*** klamath has quit IRC23:27
*** daneyon_ has quit IRC23:28
*** sigmavirus24 is now known as sigmavirus24_awa23:32
*** claired has joined #openstack-meeting-423:34
*** claired has quit IRC23:35
*** matrohon has quit IRC23:40
*** SumitNaiksatam has quit IRC23:41
*** SumitNaiksatam has joined #openstack-meeting-423:43
*** SumitNaiksatam has quit IRC23:47
*** wojdev has quit IRC23:49
*** SumitNaiksatam has joined #openstack-meeting-423:50
*** VW_ has quit IRC23:51
*** openstack has joined #openstack-meeting-423:52
*** ChanServ sets mode: +o openstack23:52
*** ivar-lazzaro has joined #openstack-meeting-423:57

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