Thursday, 2015-04-02

*** Swami has quit IRC00:14
*** aduarte has quit IRC00:15
*** banix has joined #openstack-meeting-400:18
*** dannywilson has quit IRC00:18
*** SumitNaiksatam has joined #openstack-meeting-400:31
*** igordcard_ has quit IRC00:32
*** sdake has quit IRC00:32
*** Salman_ has quit IRC00:40
*** salv-orlando has quit IRC00:44
*** banix has quit IRC00:46
*** igordcard has joined #openstack-meeting-400:52
*** banix has joined #openstack-meeting-400:53
*** eghobo has quit IRC00:56
*** watanabe_isao has joined #openstack-meeting-401:16
*** xingchao_ has quit IRC01:21
*** xingchao_ has joined #openstack-meeting-401:25
*** sballe has quit IRC01:28
*** xingchao_ has quit IRC01:28
*** xingchao_ has joined #openstack-meeting-401:29
*** asselin has joined #openstack-meeting-401:31
*** sarob has joined #openstack-meeting-401:32
*** sarob has quit IRC01:33
*** sarob has joined #openstack-meeting-401:33
*** xingchao_ has quit IRC01:34
*** sarob has quit IRC01:35
*** sarob has joined #openstack-meeting-401:35
*** s3wong has quit IRC01:40
*** sarob has quit IRC01:41
*** salv-orlando has joined #openstack-meeting-401:44
*** banix has quit IRC01:46
*** salv-orlando has quit IRC01:49
*** dims_ has joined #openstack-meeting-401:52
*** VW_ has joined #openstack-meeting-401:53
*** sridhar_ram has quit IRC01:58
*** mmedvede has quit IRC02:01
*** dims_ has quit IRC02:03
*** dims_ has joined #openstack-meeting-402:04
*** xingchao_ has joined #openstack-meeting-402:04
*** dims_ has quit IRC02:08
*** xingchao_ has quit IRC02:09
*** sarob has joined #openstack-meeting-402:13
*** sdake has joined #openstack-meeting-402:16
*** sdake has quit IRC02:17
*** sarob has quit IRC02:21
*** sdake has joined #openstack-meeting-402:21
*** sarob has joined #openstack-meeting-402:24
*** bobmel has joined #openstack-meeting-402:25
*** bobmel_ has quit IRC02:28
*** yamahata has quit IRC02:30
*** xingchao_ has joined #openstack-meeting-402:39
*** xingchao_ has quit IRC02:44
*** VW_ has quit IRC02:51
*** rushiagr_away is now known as rushiagr02:52
*** eghobo has joined #openstack-meeting-403:01
*** asselin has quit IRC03:01
*** sbalukoff has quit IRC03:02
*** sdake has quit IRC03:10
*** yamahata has joined #openstack-meeting-403:12
*** rushiagr is now known as rushiagr_away03:13
*** xingchao_ has joined #openstack-meeting-403:15
*** xingchao_ has quit IRC03:19
*** eghobo has quit IRC03:26
*** sarob has quit IRC03:30
*** sarob has joined #openstack-meeting-403:30
*** sarob has quit IRC03:30
*** rm_work|away is now known as rm_work03:31
*** sarob has joined #openstack-meeting-403:32
*** sarob has quit IRC03:37
*** SumitNaiksatam has quit IRC03:38
*** SumitNaiksatam has joined #openstack-meeting-403:38
*** SumitNaiksatam has quit IRC03:40
*** SumitNaiksatam has joined #openstack-meeting-403:42
*** xingchao_ has joined #openstack-meeting-403:48
*** xingchao_ has quit IRC03:54
*** SumitNaiksatam has quit IRC04:07
*** SumitNaiksatam has joined #openstack-meeting-404:07
*** sbalukoff has joined #openstack-meeting-404:11
*** salv-orlando has joined #openstack-meeting-404:16
*** salv-orlando has quit IRC04:20
*** fnaval has quit IRC04:21
*** ibiris_away is now known as ibiris04:21
*** xingchao_ has joined #openstack-meeting-404:24
*** eghobo has joined #openstack-meeting-404:24
*** xingchao_ has quit IRC04:29
*** SumitNaiksatam has quit IRC04:30
*** rm_work is now known as rm_work|away04:32
*** rushiagr_away is now known as rushiagr04:32
*** SumitNaiksatam has joined #openstack-meeting-404:34
*** ibiris is now known as ibiris_away04:36
*** fnaval has joined #openstack-meeting-404:48
*** ibiris_away is now known as ibiris04:53
*** xingchao_ has joined #openstack-meeting-404:59
*** xingchao_ has quit IRC05:04
*** xingchao_ has joined #openstack-meeting-405:33
*** xingchao_ has quit IRC05:39
*** dims_ has joined #openstack-meeting-406:00
*** dims_ has quit IRC06:06
*** rushiagr is now known as rushiagr_away06:07
*** bharath has joined #openstack-meeting-406:08
*** eghobo has quit IRC06:08
*** nkrinner has joined #openstack-meeting-406:09
*** rushiagr_away is now known as rushiagr06:10
*** bharath has quit IRC06:21
*** bharath has joined #openstack-meeting-406:30
*** kobis has joined #openstack-meeting-406:34
*** xingchao_ has joined #openstack-meeting-406:45
*** wojdev has joined #openstack-meeting-406:47
*** xingchao_ has quit IRC06:49
*** rm_work|away is now known as rm_work06:51
*** wojdev has quit IRC06:51
*** wojdev has joined #openstack-meeting-406:58
*** numan has joined #openstack-meeting-407:08
*** bharath has quit IRC07:13
*** salv-orlando has joined #openstack-meeting-407:13
*** xingchao_ has joined #openstack-meeting-407:16
*** sbalukoff has quit IRC07:20
*** salv-orlando has quit IRC07:21
*** xingchao_ has quit IRC07:25
*** sbalukoff has joined #openstack-meeting-407:25
*** GeetikaBatra__ has joined #openstack-meeting-407:31
*** matrohon has joined #openstack-meeting-407:33
*** salv-orlando has joined #openstack-meeting-407:41
*** xingchao_ has joined #openstack-meeting-407:53
*** matrohon has quit IRC07:55
*** xingchao_ has quit IRC07:58
*** numan has quit IRC08:18
*** markvoelker has quit IRC08:18
*** wojdev has quit IRC08:19
*** wojdev has joined #openstack-meeting-408:19
*** wojdev has quit IRC08:19
*** GeetikaBatra__ has quit IRC08:26
*** GeetikaBatra__ has joined #openstack-meeting-408:27
*** xingchao_ has joined #openstack-meeting-408:28
*** xingchao_ has quit IRC08:34
*** yamahata has quit IRC08:37
*** markvoelker has joined #openstack-meeting-408:49
*** numan has joined #openstack-meeting-408:50
*** dims_ has joined #openstack-meeting-408:50
*** markvoelker has quit IRC08:55
*** dims_ has quit IRC08:55
*** watanabe_isao has quit IRC09:02
*** numan has quit IRC09:15
*** ibiris is now known as ibiris_away09:20
*** numan has joined #openstack-meeting-409:28
*** ibiris_away is now known as ibiris09:38
*** numan has quit IRC09:55
*** GeetikaBatra__ has quit IRC09:56
*** dims__ has joined #openstack-meeting-409:56
*** sarob has joined #openstack-meeting-410:00
*** dims__ has quit IRC10:03
*** ptoohill has quit IRC10:03
*** ptoohill has joined #openstack-meeting-410:04
*** sarob has quit IRC10:05
*** dims has joined #openstack-meeting-410:09
*** xingchao_ has joined #openstack-meeting-410:13
*** numan has joined #openstack-meeting-410:14
*** bharath has joined #openstack-meeting-410:14
*** bharath has quit IRC10:18
*** xingchao_ has quit IRC10:19
*** GeetikaBatra__ has joined #openstack-meeting-410:25
*** numan has quit IRC10:27
*** numan has joined #openstack-meeting-410:41
*** xingchao_ has joined #openstack-meeting-410:48
*** markvoelker has joined #openstack-meeting-410:52
*** xingchao_ has quit IRC10:54
*** markvoelker has quit IRC10:57
*** xingchao_ has joined #openstack-meeting-411:24
*** GeetikaBatra__ has quit IRC11:24
*** xingchao_ has quit IRC11:29
*** matrohon has joined #openstack-meeting-411:33
*** GeetikaBatra__ has joined #openstack-meeting-411:39
*** GeetikaBatra__ has quit IRC11:43
*** sarob has joined #openstack-meeting-411:48
*** sarob has quit IRC11:53
*** markvoelker has joined #openstack-meeting-411:53
*** galstrom_zzz is now known as galstrom11:58
*** markvoelker has quit IRC11:58
*** xingchao_ has joined #openstack-meeting-411:59
*** xingchao_ has quit IRC12:05
*** wojdev has joined #openstack-meeting-412:08
*** sdake has joined #openstack-meeting-412:15
*** rfolco has joined #openstack-meeting-412:16
*** sdake_ has joined #openstack-meeting-412:25
*** dims has quit IRC12:25
*** dims has joined #openstack-meeting-412:26
*** sdake has quit IRC12:28
*** markvoelker has joined #openstack-meeting-412:29
*** bknudson has quit IRC12:32
*** bobmel_ has joined #openstack-meeting-412:32
*** xingchao_ has joined #openstack-meeting-412:34
*** bobmel has quit IRC12:37
*** xingchao_ has quit IRC12:39
*** numan has quit IRC12:40
*** numan has joined #openstack-meeting-412:53
*** pkoniszewski has joined #openstack-meeting-412:55
*** klamath has joined #openstack-meeting-413:01
*** klamath has quit IRC13:01
*** klamath has joined #openstack-meeting-413:02
*** erikmwilson has joined #openstack-meeting-413:02
*** xingchao_ has joined #openstack-meeting-413:09
*** ativelkov has joined #openstack-meeting-413:11
*** rushiagr is now known as rushiagr_away13:11
*** bknudson has joined #openstack-meeting-413:13
*** mclaren has joined #openstack-meeting-413:13
*** galstrom is now known as galstrom_zzz13:14
*** xingchao_ has quit IRC13:14
*** VW_ has joined #openstack-meeting-413:17
*** wojdev_ has joined #openstack-meeting-413:32
*** wojdev has quit IRC13:34
*** wojdev_ is now known as wojdev13:34
*** sarob has joined #openstack-meeting-413:37
*** zigo has quit IRC13:38
*** ChuckC has quit IRC13:38
*** sdake has joined #openstack-meeting-413:39
*** wokuma has joined #openstack-meeting-413:41
*** zigo_ is now known as zigo13:41
*** xingchao_ has joined #openstack-meeting-413:41
*** wokuma has quit IRC13:42
*** sarob has quit IRC13:42
*** sdake_ has quit IRC13:43
*** nkrinner has quit IRC13:46
*** xingchao_ has quit IRC13:49
*** joel-coffman has joined #openstack-meeting-413:51
*** wokuma has joined #openstack-meeting-413:51
*** sdake_ has joined #openstack-meeting-413:51
*** joel-coffman_ has joined #openstack-meeting-413:52
*** joel-coffman has left #openstack-meeting-413:52
*** joel-coffman_ has quit IRC13:53
*** bpoulos has joined #openstack-meeting-413:53
*** joel-coffman_ has joined #openstack-meeting-413:53
*** sdake has quit IRC13:55
*** rushiagr_away is now known as rushiagr13:56
*** TravT_ has joined #openstack-meeting-413:56
*** cpallares has joined #openstack-meeting-413:57
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa13:59
flaper87o/13:59
ativelkovo/13:59
mfedosino/13:59
nikhil_k#startmeeting Glance14:00
openstackMeeting started Thu Apr  2 14:00:00 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
hemanthmo/14:00
joel-coffman_o/14:00
nikhil_kAgenda for today:14:00
bpouloso/14:01
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
*** sigmavirus24_awa is now known as sigmavirus2414:01
jokke_o/14:01
flaper87o/14:01
nikhil_kLooks like we've decent turnout..14:01
*** lakshmiS has joined #openstack-meeting-414:01
nikhil_kLet's get started14:01
nikhil_k#topic Kilo RC114:01
*** openstack changes topic to "Kilo RC1 (Meeting topic: Glance)"14:01
nikhil_kQuick updates14:02
nikhil_kSpecs:14:02
*** VW_ has quit IRC14:02
nikhil_k1. We got CIS (Catalog Index Service) merged on server side. Due to client HardDepFreeze we ar not letting any more changes so that is carried over to early(ish) L (as applicable)14:02
cpallareso/14:03
pkoniszewskio/14:03
nikhil_kThere are few related changes to CIS that should go in, like the functional tests. Those were considered not a mandate on feature and can be merged outside of the freeze (in the RC window)14:03
nikhil_kThose*14:03
*** rosmaita has joined #openstack-meeting-414:04
mclareno/14:04
rosmaitao/14:04
lakshmiSo/14:04
nikhil_kseems like we've only one pending for review:14:04
nikhil_khttps://review.openstack.org/#/q/status:open+project:openstack/glance+branch:master+topic:bp/catalog-index-service,n,z14:04
*** xingchao_ has joined #openstack-meeting-414:04
nikhil_kWelcome guys, we're just chatting on RC114:05
jokke_that's an interesting statement ... we demand 20 lines of tests for single line bug fix and then we are willing to merge whole functionalities into release without tests?14:05
nikhil_kWelcome to OpenStack14:05
*** sabari has joined #openstack-meeting-414:06
mfedosinall test are written and passed there14:06
mfedosin*tests14:06
mfedosinhttps://review.openstack.org/#/c/157209/14:06
lakshmiSthe main CIS patch which got merged also had tests14:07
*** VW_ has joined #openstack-meeting-414:07
nikhil_kThe review priority and the community expectations were declared quite in advance. Lack of reviews adds pressure on the stability. We need to find a balance on this and reviewers need to focus on the program priorities. We cannot afford to work on refactors and minor fixus and smaller reviews when the whole features are waiting. We can discuss more about this in the coming weeks..14:08
*** VW_ has quit IRC14:08
nikhil_kArtifacts:14:08
nikhil_khttps://blueprints.launchpad.net/glance/+spec/artifact-repository14:08
*** VW_ has joined #openstack-meeting-414:09
nikhil_kA few merged and a few did not. It's a big change and lots of code. So, we will take what we can get.14:09
TravT_There is a bug fix on cis as well. I'm on mobile. So can't type quick enough. Trying to find.14:10
ativelkovgreat thanks to all the reviewers who made that possible14:10
jokke_ok, do we have funtional artifacts now in the release? (not perhaps doing all that was wanted, but something that can be used?)14:10
nikhil_kThere was some conversation between the rel-mgr and project/feature repr that allowed some reviews merge in Kilo early this week14:10
nikhil_kCan we have funtional tests for artifacts without API merged?14:11
ativelkovjokke_: no, unfortunately not: the REST API commit didn't get enough reviews and was postponed14:11
flaper87Although not backport candidate, we can still work on helping move those forward on L-114:12
flaper87ativelkov: ^14:12
flaper87That should give enough time to complete the client work and stabilize the feature14:12
wokumaTravT: This one? https://review.openstack.org/#/c/16650114:12
ativelkovartifacts has got the DB layer, declarative framework (flaper87 - I remember, we have agreed to refactor it a lot, Ina is already working on it), the plugin loader and some other helper stuff. No domain and REST API commit (the last one binds them all together)14:12
flaper87As I stated in the reviews, the API is more delicate than the database code since it's user facing.14:12
flaper87ativelkov: I started looking at Ina's work, thanks a lot for putting efforts there14:13
flaper87I really appreciate the openness you guys have demostrated14:13
*** ChuckC has joined #openstack-meeting-414:13
nikhil_kflaper87: it's also experimental and to be clearly communicated as subject to change backward incompatible. I hope ativelkov will take care of that14:13
flaper87nikhil_k: yeah, agreed on that!14:14
ativelkovnikhil_k: sure. The documentation (which haven't been merged as well) says that explicitly. But having a client at the moment of API release is a good thing, so we'll try doing that in L114:14
nikhil_kSounds like a plan14:15
*** banix has joined #openstack-meeting-414:15
ativelkovBTW, guys, do you prefer artifacts client to be part of the main python-glanceclient CLI, or should we have a separate command endpoint?14:15
nikhil_kI've also asked ativelkov and his team to create a new spec for L14:15
nikhil_kativelkov: I think we can discuss that on the spec14:16
mfedosinI just know who will be responsible for the client14:16
ativelkovnikhil_k: got it14:16
nikhil_kbetter to get wider audience and hopefully this time earlier in the cycle14:16
jokke_++14:16
flaper87++14:16
ativelkovmfedosin: for its development? I guess that will be us14:16
flaper87so, re the client library, it'd be inconsistent to have the API in glance and the client library elsewhere.14:17
flaper87(if I understood your question correctly)14:17
ativelkovflaper87: no, the library is definetly the same14:17
mfedosinativelkov, yeah, sure :D14:17
ativelkovI mostly speak about CLI endpoint14:17
nikhil_kThere is the place where most (if not all) the comments/bugs on the reviews related to Artifacts are:14:17
nikhil_k#link https://etherpad.openstack.org/p/Artifacts_Reviews14:17
flaper87ativelkov: ah sorry, mmh, I guess the endpoint could be different, OTOH14:18
jokke_ativelkov, mfedosin: please please please, try to not put all what you want to extend on those patches what you have out pending again ... lets try to get what you have ready into the state we can merge sooner the better before extending a lot ... I'd rather see experimental api in L1 than stable api day before FF14:18
ativelkovi.e. should that be "$ glance artifacts-list" or something else, like "glance-artifacts artifacts-list"14:18
nikhil_kflaper87: yeah, I think he means something along the lines of the novaclient (like the module based wrapper)14:18
nikhil_kThough, maintainability wise that sounds trixy14:19
flaper87I'd personaly vote for `glance artifacts-list` for the sake of consistency14:19
ativelkovjokke_: I surely agree. I'd prefer to land the remaining two patches in L1 and then proceed with imporvements/new features/refactoring14:19
ativelkovand, well, less code lines per patch. The lesson is learned :)14:20
ativelkovthanks guys for all your patience in reading that tons of code14:20
nikhil_kativelkov: yes and preferably softer dependencies too14:20
nikhil_k(fewer unneeded rebases ie)14:21
ativelkovyup14:21
nikhil_kThanks!14:21
nikhil_kSo, we are out of the FFE period14:21
ativelkovwell, once most of the base logic is in, we won't have so much dependencies14:21
nikhil_ksure14:22
nikhil_kAt this point, we are looking at only bugs that fit the RC criterion14:22
nikhil_k#topic RC1 blockers14:22
*** openstack changes topic to "RC1 blockers (Meeting topic: Glance)"14:22
jokke_nikhil_k: do you have link to those criteria for refresher to everyone14:23
nikhil_khmm, can't seem to find the link (if there is one)14:24
sigmavirus24yeah hard criteria would be nice14:24
nikhil_kBasically, we are frozen on all the changes related to features, docs, dependencies and such14:24
nikhil_khttps://wiki.openstack.org/wiki/Kilo_Release_Schedule14:25
sigmavirus24also we're still in string freeze, right?14:25
jokke_nikhil_k: ok, mind to type few line summary what we're looking that can qualify on top of any critical/security bugs?14:25
nikhil_kThat has list of the freeze(s)14:25
nikhil_kYeah, trying14:25
*** dvorak is now known as clayton14:25
* flaper87 reads carefully14:25
nikhil_kRC1 would allow more general bugs than other RCs14:26
*** krykowski has joined #openstack-meeting-414:26
TravT_The patch wokuma mentioned above is really important. Metadefs don't load correctly right now. Fresh devstack will yield 0 usable defintions out of box.14:26
nikhil_kSo, anything that's breaking can be merged and if needed we are easier to get an exception (for docs, deps)14:27
nikhil_kRC2 would be the period when we test out tarball rigorously and find stuff to fix14:27
nikhil_kRC3 is limited fixes only14:27
jokke_sure ... and iiuc we can put easy fixes that might not be so critical as soon as something surfaces that mandates next RC anyways14:27
jokke_nikhil_k: so rc1 will be out at 9th?14:28
*** sarob has joined #openstack-meeting-414:28
nikhil_kcan you please elaborate on "that mandates next RC anyways" ?14:28
nikhil_kjokke_: it's usually on Tuesdays (iirc)14:29
jokke_nikhil_k: so when there comes critical bug that will push us to next RC anyways we can and should get other fixes in as well what we manage to fix while doing that one that will demand the next rc14:29
nikhil_kSo, that if there has to be an execption and wait on gate it can be resolve in couple of days and we're packed by Friday14:29
ativelkovfolks, what about fixes in python-glanceclient? Are they postponed now, as we are on dep-freeze and so new releases are not likely now?14:30
nikhil_kjokke_: yes please14:30
jokke_but we should not tag RC4 for fixing typos in docstrings :P14:30
nikhil_kI don't think we get RC4 (at least not yet)14:30
nikhil_kat that time we are looking at backports14:31
nikhil_kand have more restrictions14:31
jokke_ativelkov: we can fix bugs in client and make patch releases, but no new functionality until we can lock the stable client and start developing for Liberty14:31
nikhil_kwhat jokke_ said14:32
ativelkovgot it14:32
nikhil_kThanks to sigmavirus24 :14:32
sigmavirus24huh? what'd I do?14:32
nikhil_k#info We've created more official tags at https://bugs.launchpad.net/glance14:32
ativelkovI am asking because of https://review.openstack.org/#/c/168364/ as it fixes some cinder-related bug14:32
sigmavirus24hah14:32
nikhil_kThere are tags for artifacts, cis, cache etc now14:33
sigmavirus24ativelkov: I thought I had workflow'd that14:33
nikhil_kI wanted to quickly go through the RC1 bugs so that people are aware (online now and otherwise)14:34
nikhil_khttps://bugs.launchpad.net/bugs/141730414:34
openstackLaunchpad bug 1417304 in Glance "Upload/Import image continues consuming glance host cpu/memory/network/disk resources even after the image is deleted" [Undecided,Incomplete]14:34
ativelkovsigmavirus24: nope, there was just a +1 from you at one of the first PS. +2A will be appreciated )14:34
sigmavirus24So following ativelkov's review, quickly, it's introducing new behaviour, but the fact that it didn't exist before is a pretty bad bug14:34
nikhil_kah14:34
jokke_sigmavirus24 & nikhil_k: if there is some "more official" new tags, please update https://wiki.openstack.org/wiki/Bug_Tags#Glance accordingly14:34
nikhil_kjokke_: cool, thanks for the pointer!14:35
sigmavirus24jokke_: will do14:35
nikhil_ksigmavirus24: can we pleae come to it in the bugs topic?14:35
nikhil_kWe're out of time for RC1 and had a security bug people might want to chime in on..14:36
* sigmavirus24 is quiet ;14:37
nikhil_kSorry about that, a bit caught up..14:37
nikhil_kbug/141730414:37
nikhil_kWe need a verdict on that whether we need it in kilo or not14:37
flaper87nikhil_k: that one, I'll get back to it as promised last night14:37
flaper87well, night for me14:37
nikhil_kflaper87: and I had agreed yday that it can wait14:37
flaper87I think we should change the milestone, I can do that after commenting14:38
nikhil_kEveryone please leave you opinion if necessary14:38
jokke_nikhil_k: easy fix, we do not allow deleting image which is on saving status ... if one want's to delete image one should cancel the upload first ;)14:38
nikhil_kjokke_: Please do provide your insight there :)14:38
jokke_will do :P14:38
nikhil_khttps://bugs.launchpad.net/bugs/127669414:38
openstackLaunchpad bug 1276694 in neutron "Openstack services should support SIGHUP signal" [Wishlist,In progress] - Assigned to Elena Ezhova (eezhova)14:38
nikhil_kThat looks merged14:38
nikhil_kand I think we can mark it Committed14:39
jokke_mclaren: do you have still something pending for that?14:39
nikhil_kThe other three in open status are needed and blocking RC1 so please review them before others14:39
mclarenjust the glance-control bit14:39
ativelkovjokke_: what happens if it is in SAVING due to a copy-from external source? Is there a way to cancel that?14:40
mclarenhttps://review.openstack.org/#/c/130222/14:40
*** carl_baldwin has joined #openstack-meeting-414:40
nikhil_kmclaren: Not sure if you got a chance to look at my email - I think we can do that bit in the kilo-potention as a different bug14:40
*** sarob has quit IRC14:40
nikhil_kOther bugs that have potential to go in Kilo are:14:40
nikhil_khttps://bugs.launchpad.net/glance/+bugs?field.tag=kilo-rc-potential14:40
*** pkoniszewski has quit IRC14:41
jokke_ativelkov: I don't think we have abort for that currently, which is not that great loss as the copy-from is v1 functionality and tasks does support abort iiuc14:41
*** sarob has joined #openstack-meeting-414:41
nikhil_kativelkov: sigmavirus24 : Can we mark this with milestone https://bugs.launchpad.net/cinder/+bug/132366014:41
openstackLaunchpad bug 1323660 in Glance "Glance image properties not copied to cinder volume with glance V2 API" [Undecided,In progress] - Assigned to Alexander Tivelkov (ativelkov)14:41
nikhil_k?14:41
nikhil_kHopefully it should merge smoohtly now that it has a +W14:41
nikhil_ksigmavirus24: and if you wanted to go ahead on that bug please do :)14:42
jokke_mclaren: btw thanks for finding the gate broker! All: could we please finally stop issuing requests to random domain brokers from our tests!14:42
ativelkovoh! What was the issue? I missed the solution, but the problem was really nasty14:42
mclarenativelkov: hopefully this https://review.openstack.org/#/c/169889/14:43
flaper87mclaren: ++14:43
mclaren(I never actually reproduced a failure)14:43
jokke_mclaren: me nor flaper87 either14:44
ativelkovoh my...14:44
flaper87FWIW,  I think the problem is weirder than that since the `get_size` catches the BadStoreUri error but still, it's being propagated14:44
flaper87:/14:44
flaper87That's what had me stuck for a bit14:44
flaper87anyway, mclaren's fix should be enough for our CI14:45
nikhil_kOk, guys. Sorry about this, we are running out of time14:45
*** wojdev has quit IRC14:46
nikhil_kIf there are no more bugs to be discussed forkilo-potential can we please run for the next part?14:46
nikhil_kOk, in the interest of time crunch..14:46
nikhil_k(crunch..)14:46
nikhil_k#topic Summit planning14:46
*** openstack changes topic to "Summit planning (Meeting topic: Glance)"14:46
nikhil_k#info Slots: Fishbowl: 4, Work: 8, Sprint: 1 Halfday14:47
* sigmavirus24 won't make it to the sprints14:47
nikhil_kThere was some discussion in the CPL meeting yday about this14:47
ativelkovwhat's the fishbowl?14:47
nikhil_kand we'd added the discussion etherpads for the topics to14:47
flaper87ativelkov: the normal room we've been using14:47
nikhil_k#link  https://wiki.openstack.org/wiki/Design_Summit/Planning14:47
flaper87ativelkov: I mean, the sessions as we know them14:47
nikhil_k#link https://etherpad.openstack.org/p/liberty-glance-summit-topics <- That the Glance specific one14:48
mfedosinativelkov, A fishbowl conversation is a form of dialog that can be used when discussing topics within large groups.14:48
nikhil_kMore info on the summit format (changes):14:48
nikhil_k#link https://openstack.nimeyo.com/521/openstack-dev-vancouver-design-summit-format-changes?show=41714:48
nikhil_kativelkov: ^14:48
nikhil_kOk, moving on to the next14:49
nikhil_k#topic Stable branches14:49
*** openstack changes topic to "Stable branches (Meeting topic: Glance)"14:49
ativelkovgit it, thanks14:49
nikhil_kflaper87: sigmavirus24 and I had a chat yday about glance_store stable branch14:49
nikhil_kseems like we don;t have one currently14:49
nikhil_kSo, the plan was to point on the absolute necessary changes/commits to have after 0.3.0 for a stable branch for juno and kilo14:50
*** sridhar_ram has joined #openstack-meeting-414:50
nikhil_kWe are trying to track that inofficially on14:50
nikhil_khttps://trello.com/b/GFXMXxsP/openstack-glance14:50
nikhil_k(Currently, there is nothing and soon to be added)14:50
flaper87FWIW, there's a -1 on my patch already14:50
flaper87#link https://review.openstack.org/#/c/169661/14:51
nikhil_kawesome14:51
flaper87I'll get back to that soon14:51
nikhil_kClient stable branch14:51
nikhil_kWe did not discuss one yet14:51
nikhil_khowever, my opinion is (based on a quick browse) that we need the same approch here14:52
jokke_yup14:52
nikhil_kThat was it from my side.14:52
nikhil_kI will open up for pending / other discussions14:52
flaper87re the stable branch14:52
nikhil_kopen up the topic14:52
flaper87We were mostly waiting for the cross-project patch to land14:52
nikhil_k:)14:52
flaper87now that it's been merged14:52
nikhil_k#topic Open Discussion14:52
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:52
mfedosinfolks, please, say your thoughts/opinions about db documentation https://review.openstack.org/#/c/164432/ Because we are ready for the next commit :)14:52
flaper87I think we can move forward to creating such branch14:53
bpoulosif we have a suggestion for a summit topic, should we discuss it here or go ahead and put it on the etherpad?14:54
nikhil_kbpoulos: yes please go ahead14:54
jokke_I'd propose both glance_store and python_glanceclient "stable" branches to be named by the version we dedicate for stable backports for stable glance releases14:54
bpouloswe're working on a feature for image signing and encryption supported by glance14:54
bpoulosthis would allow users to verify that their images had not been modified by verifying a signature before booting the image14:54
bpouloswe were wondering if it would be possible to discuss the feature at the summit14:54
flaper87jokke_: as in stable/juno ? or stable/0.3.0 ?14:55
sigmavirus24bpoulos: interesting14:55
jokke_flaper87: stable/0.314:55
sigmavirus24flaper87: the spec prescribes stable/juno kind of stuff iirc14:55
flaper87bpoulos: I'd love to hear more! FWIW, flwang once looked into this, you might want to ping him and see where he was at14:55
jokke_flaper87: and for example 0.3.1 would be just tag on that branch14:55
flaper87jokke_: what sigmavirus24 said14:55
bpoulosflaper87: ok, thanks14:56
ativelkovbpoulos: that's sounds interesting. We have planned similar for artifacts, so it definetely worths discussing more14:56
*** wojdev has joined #openstack-meeting-414:56
jokke_bpoulos: feel free to propose into https://etherpad.openstack.org/p/liberty-glance-summit-topics14:56
bpoulosjokke: alright, i'll add it there14:57
*** VW_ has quit IRC14:57
*** wojdev has quit IRC14:57
jokke_sigmavirus24: i think the biggest problem with using the release names in the libs is that because we do not follow same schedule it can become really messy and confusing quickly, thus I'd prefer using the stable version on the branch name14:58
nikhil_k+1 on jokke_ 's idea14:58
sigmavirus24jokke_: that probably would have been better raised during the discussion of the cross-project spec. I personally agree14:58
jokke_as the requirements refers to the version number as well14:58
nikhil_kbpoulos: +1 on your proposal14:58
sigmavirus24(personally agree with you jokke_ )14:59
mclarenwe should try to make sure everyone does it the same way if possible14:59
flaper87but in the stable branch we would still have the version in the setup.cfg14:59
flaper87right ?14:59
bpoulosnikhil_k: thanks14:59
* flaper87 agrees with jokke_14:59
flaper87I think we should bring that up to a broader audience15:00
flaper87since consistency throughout projects might be important here15:00
jokke_ok time's up and I have next meeting to jump into15:00
jokke_thanks all15:00
nikhil_kThanks all!15:00
*** TravT_ has quit IRC15:00
ativelkovthanks guys, have a good day15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings"15:00
openstackMeeting ended Thu Apr  2 15:00:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
*** lakshmiS has quit IRC15:00
mclarenthanks15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-04-02-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-04-02-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-04-02-14.00.log.html15:00
*** VW_ has joined #openstack-meeting-415:00
*** ativelkov has left #openstack-meeting-415:00
*** wokuma has left #openstack-meeting-415:01
*** cpallares has left #openstack-meeting-415:01
*** mclaren has quit IRC15:01
*** mattt has joined #openstack-meeting-415:01
*** sbalukoff has quit IRC15:03
*** rosmaita has left #openstack-meeting-415:04
*** MarkAtwood has joined #openstack-meeting-415:04
*** bobmel has joined #openstack-meeting-415:14
*** bobmel_ has quit IRC15:17
*** yamahata has joined #openstack-meeting-415:17
*** joel-coffman_ has quit IRC15:24
*** dannywilson has joined #openstack-meeting-415:24
*** ajmiller has joined #openstack-meeting-415:24
*** dannywil_ has joined #openstack-meeting-415:29
*** dannywilson has quit IRC15:29
*** galstrom_zzz is now known as galstrom15:31
*** sridhar_ram1 has joined #openstack-meeting-415:31
*** sridhar_ram has quit IRC15:32
*** git-harry has joined #openstack-meeting-415:32
*** SumitNaiksatam has quit IRC15:37
*** sdake has joined #openstack-meeting-415:38
*** sdake_ has quit IRC15:42
*** eghobo has joined #openstack-meeting-415:46
*** spredzy is now known as spredzy|afk15:47
*** kbyrne has quit IRC15:48
*** kobis has quit IRC15:50
*** emagana has joined #openstack-meeting-415:53
*** numan has quit IRC15:53
*** krykowski has quit IRC15:55
*** alextricity has joined #openstack-meeting-415:55
cloudnullhey guys .16:01
d34dh0r53\0/16:01
*** rromans has joined #openstack-meeting-416:01
alextricityHello!16:01
cloudnull#startmeeting OpenStack Ansible Meeting16:02
openstackMeeting started Thu Apr  2 16:02:11 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. 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
cloudnull#topic Agenda & rollcall16:02
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:02
cloudnullso who is all here :)16:02
alextricityHere16:02
*** rackertom has joined #openstack-meeting-416:03
rromanso/16:03
d34dh0r53pre sent16:03
* cloudnull presente 16:03
rackertomo/16:03
*** Sam-I-Am has joined #openstack-meeting-416:03
Sam-I-Amhi16:03
stevelleo/16:03
*** SumitNaiksatam has joined #openstack-meeting-416:04
cloudnull#topic action items from last week16:05
*** openstack changes topic to "action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
d34dh0r53#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:05
*** xingchao_ has quit IRC16:05
cloudnullthe one from odyssey4me was dropped16:06
cloudnull#item hughsaunders convert that to a spec and resubmit it for approval16:06
cloudnull^ hughsaunders what say you? - I suspect that this was the bp you created. IE https://blueprints.launchpad.net/openstack-ansible/+spec/manage-resolv-conf16:07
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/manage-resolv-conf16:07
cloudnullwelp nevermind , it looks like the bp/spec was abandoned.16:08
cloudnull#link https://review.openstack.org/#/c/168074/16:08
*** igordcard_ has joined #openstack-meeting-416:08
*** carl_baldwin has quit IRC16:08
cloudnulli closed that BP and marked it Obsolete.16:09
*** galstrom is now known as galstrom_zzz16:09
cloudnull#topic Blueprints16:09
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:09
cloudnullalextricity: being that you're the only one on the agenda can you start off talking about the BP/Spec16:09
alextricitySure.16:09
alextricityThe goal is to create discussion around how we can implement ceilo into OSAD16:10
cloudnull#link https://review.openstack.org/#/c/169417/16:10
alextricitycloudnull already have sat down and started talking about the initial setup16:10
alextricitye.g. changes to the openstack_environment.yml, new containers, etc16:11
cloudnullyes.16:11
alextricityThe code is up on the whiteboard16:11
*** galstrom_zzz is now known as galstrom16:11
cloudnull#link https://review.openstack.org/#/c/169417/2/specs/kilo/implement-ceilometer16:11
cloudnull#link http://docs-draft.openstack.org/17/169417/3/check/gate-os-ansible-deployment-specs-docs/f5eda8a//doc/build/html/specs/kilo/implement-ceilometer.html16:12
alextricityRight now I am brainstorming ways we can effeciently deploy ceilometer, with mongodb database backend.16:12
cloudnullso my one question here is how do we test it. ^16:12
alextricityefficiently*16:12
alextricityI was thinking about creating a small play to deploy a basic mongodb server16:12
cloudnulldo we develop an in repo method to deploy mongo, similar to how we are doing mariadb/Galera ?16:13
alextricityBut i'm open to suggestions, as always ;)16:13
alextricityHmmm..I don't know about that cloudnull16:13
andymccrmaybe there are upstream mongo roles?16:13
cloudnullor do we make just enough to get it to work?16:13
cloudnullif there are upstream mongo roles we can pull them in using masters structure to pull in external roles.16:14
andymccryeh that'd be ideal16:14
cloudnull#link https://github.com/stackforge/os-ansible-deployment/blob/master/ansible-role-requirements.yml.example16:14
d34dh0r53+1 to that, implementing and managing a mongo role is not something we should be doing IMHO16:14
alextricityre: upstream roles: definitely. I don't know if you guys are comfortable with have in-repo method for deploying mongodb16:14
cloudnullim comfortable with it. we're doing it with maria and rabbit16:15
*** kbyrne has joined #openstack-meeting-416:15
alextricityI'm leaning towards that idea as well d34dh0r5316:15
alextricityI think we should just do enough to make it work for now16:15
cloudnullmongo is used through the OpenStack. even if i dont like it16:15
cloudnull*throughout16:16
andymccryeh if its not there, and we need ceilometer16:16
sigmavirus24to me, if the upstream roles will accept patches to make them better fit our needs, then yeah16:16
andymccrthen we should look into it.16:16
alextricityWho knows, ceilometer is expected to up their game in Kilo. With Gnocchi, mysql could be a viable solution.16:16
sigmavirus24otherwise, for a short term fix we may have to carry our own16:16
Sam-I-Amdoes ceilometer not work with mysql?16:16
cloudnullwell other services like zaqar are using mongo too16:17
*** mwang2 has joined #openstack-meeting-416:17
cloudnullSam-I-Am it works, kinda16:17
andymccrit works functionally16:17
alextricitylol16:17
cloudnullso we will eventually  need something that implements mongo.16:17
stevellecloudnull: Sam-I-Am I recall mention of 'don't ever use it in production with SQL backend'16:17
cloudnullif we can leverage upstream lets do that16:17
d34dh0r53just afraid our mongo role and the project as a whole will take the blame when ceilometer...16:18
cloudnullalextricity could you do a bit of research on what upstream roles are available. and how we can leverage tehm ?16:18
alextricitycloudnull. Of course.16:18
cloudnulld34dh0r53 this is fair.16:18
alextricityI'll keep adding to the blueprint as I gather more info and get further along in implementing the plays16:18
cloudnullbut ceilometer is a OpenStack namespaced service and we should aim to support deploying all the OpenStack services we can.16:19
d34dh0r53cloudnull: 100% agree with that16:19
andymccrtrue - and really if support is added and nobody uses it then its likely it wont be amazing, but then nobody is using it16:19
Sam-I-Amstevelle: 'dont ever use it in production' ?16:19
cloudnullthis is true.16:19
cloudnullSam-I-Am: see ceilometer16:20
*** frobware has joined #openstack-meeting-416:20
cloudnull:)16:20
*** Bjoern__ has joined #openstack-meeting-416:20
alextricityWhat do you guys think about having the separate db backend?16:20
d34dh0r53pretty sure that is the 2nd definition of ceilometer16:20
alextricitylol16:20
cloudnullalextricity "separate db backend?" ?16:20
andymccralextricity: i think if sql is not a viable option we dont have a choice so much :D16:20
andymccrunless we want to port everything else to use mongo...16:21
cloudnullandymccr for web scale16:21
cloudnull:p16:21
andymccrhow about we just plug it into objectrocket16:21
andymccrlike cloudfiles for glance :D16:21
alextricitycloudnull: If ceilometer is deployed, you'll have the sql db and mongodb for ceilo16:21
stevellecommunity, andymccr :)16:21
cloudnullcertainly . i like the idea of having ceilometer only need a connection string16:21
palendaeandymccr: That config will be in rpc-extras ;)16:21
cloudnullwhich is what we are doing in other services.16:22
palendaeYeah, if we can get it to just needing a connection string, then awesome16:22
cloudnullbut we need a way to test it. which leads to having something that deploys mongo16:22
palendaeYeah16:22
alextricityRight16:22
d34dh0r53unless we test it with objectrocket :p16:22
cloudnullwe could do that but that would have to be an external ci test16:22
palendaeIs that necessarily bad? I'm not aware of the implications around that16:23
alextricityI'm okay with having something that deploys mongo16:23
Sam-I-Amhas anyone looked at the improvements for kilo?16:23
Sam-I-Ami havent even installed it yet16:23
cloudnullme too. and if upstream can do that for us. i think we should look at that.16:23
palendaeThe ceilometer ones? no16:23
stevellefrom hard experience, tuning mongodb in replication is going to require a strategy for where to put the arbiter16:23
stevellealextricity: ^16:23
d34dh0r53Sam-I-Am: I can't until I have docs16:23
alextricitySam-I-Am: I have. Like I said they are expected to beef up their game. I still have to do more research, however.16:24
palendaestevelle: I wonder if our support shouldn't only go so far as using it for testing16:24
palendaeAnd deployers are responsible for Mongo16:24
*** bharath has joined #openstack-meeting-416:24
palendaeThat would be in line with our usage of HAProxy/load balancers16:24
d34dh0r53palendae: which is slowly becoming a thing, not something I want our mongo play to become16:25
cloudnullpalendae that might be fine initially, but with everything else we have, we're targeting production (except HAProxy).16:25
*** banix has quit IRC16:25
cloudnullyet16:25
palendaecloudnull: yeah, true. I wouldn't fight that super hard, because you're right - we manage everything else now16:25
stevellepalendae: with redundant infra nodes, we would by default have too many arbiters16:25
palendaestevelle: I was thinking just for AIOs/gating16:26
stevelleit is still a design challenge16:26
palendaeBut might as well use reference architecture16:26
palendaeFair enough. I don't know enough about Mongo to speak knowledgeably, so I'll pipe down :)16:26
Sam-I-Amstevelle: i thought mongo was smart enough not to need redundancy :)16:26
*** claired has joined #openstack-meeting-416:26
*** claired has quit IRC16:26
d34dh0r53lol16:26
cloudnullSam-I-Am see web scale.16:26
d34dh0r53hahaha16:26
palendaeI thought we were targeting cloud scale16:27
palendaeWeb scale's not good enough16:27
Sam-I-Amspace, the final scale.16:27
cloudnull#link https://www.youtube.com/watch?v=b2F-DItXtZs16:27
palendaecloudnull: Hahaha16:27
stevelletoo soon.16:27
stevellemy wounds have not healed16:27
andymccrvalid question tbh16:28
Sam-I-Amthey never really heal16:28
palendaeRight, stevelle is the Mongo SME16:28
Sam-I-Amthe scabs just keep coming off16:28
alextricitylol16:28
Sam-I-Amstevelle: sounds like you've volunteered yourself16:28
sdakecloudnull epic video have seen it before ;)16:28
*** SumitNaiksatam has left #openstack-meeting-416:28
cloudnullok so, alextricity: more research on how we deploy mongo. stevelle can you sync up with alextricity on some of your mongo SME-ness?16:29
cloudnullsdake ikr?! :)16:29
*** sdake has quit IRC16:29
stevellealextricity: you know where to find me online?16:29
cloudnulland with that update the spec for further review16:29
*** SumitNaiksatam has joined #openstack-meeting-416:30
alextricityUnfortunately I don't know enough about Mongodb to say how all of that is handled. So if we are going to go the route of deploying mongo as part of the plays..it's going to be challeging16:30
alextricitystevelle, no16:30
sigmavirus24alextricity: #openstack-meeting-416:30
sigmavirus24* #openstack-ansible16:30
alextricitylol16:30
*** sdake has joined #openstack-meeting-416:30
sigmavirus24(tab complete fail, I swear)16:30
palendaesigmavirus2: that never happens16:31
alextricitySounds good, we'll definitely sync up16:31
alextricityThanks16:31
Bjoern__I think mongo is a good choice for ceilomter, especially when it comes down to expiring objects (built in). SQL DBs are usually killed with ceilometer16:31
Bjoern__also it's just ceilometer16:31
*** Bjoern__ is now known as BjoernT16:31
sigmavirus24palenda: I don't know what you mean16:32
cloudnullso next BP: https://review.openstack.org/#/c/169189/16:32
cloudnull#link https://review.openstack.org/#/c/169189/16:32
*** yamahata has quit IRC16:32
cloudnullwhich is related to bp https://blueprints.launchpad.net/openstack-ansible/+spec/dynamically-manage-policy.json16:33
cloudnullwhile one is for policy.json and the other is for config files i think there's a lot of overlap16:33
palendaeYeah - I think merging those would be good16:34
cloudnullme too.16:34
stevelleI was of the opinion that treating json as json would be easier16:36
cloudnullim violently opposed to hash merging. but if the concept / idea wins out among cores then i say we execute on it.16:36
cloudnullhowever the bp that Daniel Curran put through and the pseudo code Sudarshan Acharya is working on creates a module which should allow us to add in extra config without having to do hash merging16:36
andymccrcloudnull: do we have another solution? cos i kinda agree with you.16:36
cloudnull#link https://review.openstack.org/#/c/168104/16:36
Sam-I-Amthe spec for neutron plays looks... interesting16:36
Sam-I-Am"have fun"16:37
cloudnullandymccr it presently works only with policy files.16:37
cloudnullbut extending to config using the ConfigParse std lib in Py2.7 should make that go.16:37
andymccrhmm  - i quite like that idea16:37
cloudnullalextricity where's suda ?16:38
alextricityI don't think he knows about these meetings16:38
alextricitywant me to get him in here16:38
alextricity?16:38
cloudnullthrow something at him :)16:38
cloudnullandymccr you mind reviewing that module to make sure its not bat shit crazy ?16:38
cloudnulli like it, i had some inline comments. but i like the concept.16:39
cloudnulland with a bit of clean up i think it could be awesome.16:39
*** b3rnard0 has joined #openstack-meeting-416:39
*** sacharya has joined #openstack-meeting-416:39
cloudnullsacharya: the man the myth the legend.16:39
sacharyahaha16:39
cloudnulloh look b3rnard0 thanks for showing up ....16:40
b3rnard0oh hai16:40
cloudnullsacharya we made some inline comments on your module.16:40
sacharyasaw that… I am fixing those… i was out the last couple of days!16:40
cloudnullalso we've moved all the things to specs. can you re-pull the bp against our specs repo so that we can get some more review on it.16:41
cloudnulltime off sacharya ? UNpossible !16:41
cloudnullno worries. :)16:41
*** Swami has joined #openstack-meeting-416:42
alextricitybrb16:42
cloudnullsacharya: IE https://github.com/stackforge/os-ansible-deployment-specs16:42
cloudnullpulling into https://github.com/stackforge/os-ansible-deployment-specs/tree/master/specs/kilo would be ideal .16:42
cloudnullNext: bp https://review.openstack.org/#/c/169189/16:43
Sam-I-Amyeah, this one :)16:44
cloudnullCores this is a bp targeted 10.x and not master at this time. we know that its a feature add in the rax technical debt branch, but could/should be extendable to master without a lot of work depending on the implementation.16:44
cloudnull i think we can work with Javeria Khan to make that go.16:45
Sam-I-Amare we still adding features to 10?16:46
palendaeYeah, I think so too16:46
Sam-I-Amsomething that might require architectural changes16:46
cloudnullas, by reading the spec, it seems that he has already done most of the work.16:46
Sam-I-Ame.g., how we're doing the lxc/bridge stuff16:46
*** sdake_ has joined #openstack-meeting-416:46
cloudnullSam-I-Am: i dont think so . but we're eventually going to have to re-approach OVS.16:47
cloudnullwhich will require some of those types of changes.16:47
Sam-I-Amif any of these plugins/agents use something outside of linuxbridge16:47
Sam-I-Amwe discussed some of the interesting ovs bits for metal hosts16:48
palendaeI think Javiera's intent was to bring in plumgrid support16:48
palendaeBut that was split into 2 phases - making ml2 replaceable was the first step16:48
Sam-I-Amwhich i think uses linuxbridge16:48
*** daneyon has quit IRC16:49
cloudnullpalendae i think so it seems that using a different neutron plugin makes that more approachable.16:49
palendaecloudnull: If I remember correctly, Javiera was saying plumgrid doesn't support ml216:50
*** sdake has quit IRC16:50
cloudnullSam-I-Am with the addition of the provider_networks ansible module the data structures in master should be far more malleable.16:50
cloudnull#link https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/library/provider_networks16:50
Sam-I-Amcloudnull: this is true16:51
cloudnullWhich came about to help with your OVS tragedy you were working on .16:51
cloudnull:)16:51
*** carl_baldwin has joined #openstack-meeting-416:51
stevellewe are nearly out of time here16:52
cloudnullso getting a few more reviews on that spec would be great.16:52
cloudnullwe are. so lets open up to general discussion .16:52
cloudnull#topic Open discussion16:52
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:52
cloudnullbegin the festivus16:53
d34dh0r53I've got a lot of problems with you people16:53
cloudnull:D16:53
d34dh0r53:)16:53
stevelleI know there are multiple reviews open for moving master to kilo. I wanted to raise osprofiler as a topic16:53
*** yamahata has joined #openstack-meeting-416:53
* cloudnull hands mic to stevelle 16:53
d34dh0r53go16:53
stevelleI feel we should configure the same way, and we had three slightly different ways between heat, glance, and cinder16:54
stevelleit's pretty clear that profiling should be off, but git-harry rightly raised the point that having the middleware in place would be good16:54
cloudnulli think we should, in config, set it off. we expose vars to enable it.16:55
cloudnullby default i think that it should be functional in paste.16:56
*** prometheanfire has joined #openstack-meeting-416:56
stevellefrom there it's less clear. Is the middleware always enabled or configurable?  It looks like we all made our own HMAC secret per-service16:56
sigmavirus24Point of order: We all recognize that without ceilometer having osprofiler configurable to be on by default is kind of ... pointless, right?16:56
stevellesigmavirus24: agreed.  The initial glance bp and work all excluded osprofiler.16:56
cloudnullsigmavirus24: unless there is somethine else, outside of our deployment scope that is consuming those messages.16:57
andymccrhaving it configurable but off by default seems sensible to me.16:57
sigmavirus24cloudnull: pretty sure osprofiler only emits things for ceilometer and I've heard 0 about it being used by anything else (I've looked a lot)16:57
stevelleso each service has it's own hmac, and the middleware is on then?16:57
* sigmavirus24 is just making sure everyone is aware16:57
cloudnullsure.16:58
cloudnullwell that ties back to alextricity  and getting ceilometer as a supportable service .16:58
alextricityYeah :/16:58
stevellelets just try to make sure all the services apply the same style to osprofiler config16:58
cloudnullif he does that, and we have the profiler options, then i think we should be good . right?16:59
*** matrohon has quit IRC16:59
andymccrconsistency would be good.16:59
cloudnull+1 for consistency16:59
d34dh0r53yes16:59
*** fnaval has quit IRC16:59
cloudnullok we're out of time. lets continue this convo in the channel or on the ML.16:59
d34dh0r53thanks all16:59
cloudnullthanks everyone.17:00
cloudnull#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings"17:00
openstackMeeting ended Thu Apr  2 17:00:04 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-04-02-16.02.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-02-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-02-16.02.log.html17:00
*** Sam-I-Am has left #openstack-meeting-417:00
*** prometheanfire has left #openstack-meeting-417:00
*** alextricity has left #openstack-meeting-417:00
*** EmilienM is now known as EmilienM|afk17:01
*** xingchao_ has joined #openstack-meeting-417:05
*** mahipal has joined #openstack-meeting-417:06
*** SumitNaiksatam has quit IRC17:12
*** xingchao_ has quit IRC17:13
*** SumitNaiksatam has joined #openstack-meeting-417:17
*** fnaval has joined #openstack-meeting-417:18
*** s3wong has joined #openstack-meeting-417:20
*** banix has joined #openstack-meeting-417:21
*** galstrom is now known as galstrom_zzz17:24
*** b3rnard0 has left #openstack-meeting-417:30
*** bpoulos has left #openstack-meeting-417:36
*** emagana has quit IRC17:42
*** sdake has joined #openstack-meeting-417:43
*** xingchao_ has joined #openstack-meeting-417:43
*** SumitNaiksatam_ has joined #openstack-meeting-417:45
*** sdake_ has quit IRC17:46
*** sarob has quit IRC17:47
*** SumitNaiksatam has quit IRC17:47
*** SumitNaiksatam_ is now known as SumitNaiksatam17:47
*** sarob has joined #openstack-meeting-417:47
*** xingchao_ has quit IRC17:48
*** sarob has quit IRC17:53
*** ivar-lazzaro has joined #openstack-meeting-418:01
*** sridhar_ram1 has quit IRC18:02
*** pkoniszewski has joined #openstack-meeting-418:02
*** galstrom_zzz is now known as galstrom18:02
*** sdake_ has joined #openstack-meeting-418:19
*** sdake has quit IRC18:23
*** cloudnull has left #openstack-meeting-418:24
*** Swami has quit IRC18:25
*** ibiris is now known as ibiris_away18:29
*** EmilienM|afk is now known as EmilienM18:30
*** sridhar_ram has joined #openstack-meeting-418:30
*** Swami has joined #openstack-meeting-418:41
*** xingchao_ has joined #openstack-meeting-418:47
*** sarob has joined #openstack-meeting-418:49
*** daneyon has joined #openstack-meeting-418:51
*** xingchao_ has quit IRC18:53
*** sarob has quit IRC18:54
*** eghobo_ has joined #openstack-meeting-418:55
*** eghobo has quit IRC18:58
*** kobis has joined #openstack-meeting-419:01
*** galstrom is now known as galstrom_zzz19:05
*** kobis has quit IRC19:06
*** ivar-lazzaro has quit IRC19:06
*** ivar-lazzaro has joined #openstack-meeting-419:07
*** matrohon has joined #openstack-meeting-419:16
*** sdake has joined #openstack-meeting-419:21
*** sdake_ has quit IRC19:24
*** sarob has joined #openstack-meeting-419:27
*** banix has quit IRC19:38
*** banix has joined #openstack-meeting-419:43
*** eghobo_ has quit IRC19:43
*** mwang2 has quit IRC19:51
*** rushiagr is now known as rushiagr_away19:51
*** rushiagr_away is now known as rushiagr19:53
*** xingchao_ has joined #openstack-meeting-419:54
*** xingchao_ has quit IRC19:58
*** sarob has quit IRC20:00
*** ivar-laz_ has joined #openstack-meeting-420:04
*** ivar-lazzaro has quit IRC20:08
*** pkoniszewski has quit IRC20:12
*** mwang2 has joined #openstack-meeting-420:16
*** sdake_ has joined #openstack-meeting-420:20
*** ivar-laz_ has quit IRC20:21
*** ivar-lazzaro has joined #openstack-meeting-420:22
*** rushiagr is now known as rushiagr_away20:23
*** eghobo has joined #openstack-meeting-420:23
*** sdake has quit IRC20:24
*** ivar-lazzaro has quit IRC20:27
*** igordcard_ has quit IRC20:29
*** mwang2 has quit IRC20:37
*** banix has quit IRC20:50
*** galstrom_zzz is now known as galstrom20:52
*** banix has joined #openstack-meeting-420:52
*** rromans has left #openstack-meeting-420:57
*** rfolco has quit IRC20:58
*** xingchao_ has joined #openstack-meeting-420:58
*** mwang2 has joined #openstack-meeting-420:58
*** bharath has quit IRC20:59
*** bharath_ has joined #openstack-meeting-420:59
*** bharath_ has quit IRC21:00
*** bharath has joined #openstack-meeting-421:00
*** dannywilson has joined #openstack-meeting-421:00
*** dannywil_ has quit IRC21:02
*** sdake_ is now known as sdake21:02
*** xingchao_ has quit IRC21:03
*** emagana has joined #openstack-meeting-421:07
*** emagana has quit IRC21:09
*** emagana has joined #openstack-meeting-421:10
*** ajmiller_ has joined #openstack-meeting-421:10
*** fnaval has quit IRC21:13
*** ajmiller has quit IRC21:14
*** emagana has quit IRC21:14
*** emagana has joined #openstack-meeting-421:16
*** sdake_ has joined #openstack-meeting-421:18
*** sdake has quit IRC21:22
*** sbalukoff has joined #openstack-meeting-421:22
*** sdake has joined #openstack-meeting-421:23
*** sdake_ has quit IRC21:27
*** vishwana_ has joined #openstack-meeting-421:32
*** sweston has quit IRC21:33
*** mgagne has quit IRC21:33
*** carl_baldwin has quit IRC21:33
*** sridhar_ram has quit IRC21:35
*** dougwig has quit IRC21:35
*** ttx has quit IRC21:35
*** sweston has joined #openstack-meeting-421:36
*** crinkle_ has joined #openstack-meeting-421:37
*** Hunner has quit IRC21:37
*** rm_work has quit IRC21:37
*** crinkle has quit IRC21:38
*** crinkle_ is now known as crinkle21:38
*** emagana has quit IRC21:38
*** erikmwilson has quit IRC21:38
*** vishwanathj has quit IRC21:38
*** krtaylor has quit IRC21:38
*** hughsaunders has quit IRC21:38
*** mattt has left #openstack-meeting-421:38
*** jckasper has quit IRC21:38
*** jckasper has joined #openstack-meeting-421:39
*** erikmwilson has joined #openstack-meeting-421:39
*** ttx has joined #openstack-meeting-421:39
*** mgagne has joined #openstack-meeting-421:40
*** hughsaunders has joined #openstack-meeting-421:40
*** Hunner has joined #openstack-meeting-421:40
*** rm_work has joined #openstack-meeting-421:41
*** rm_work has quit IRC21:41
*** rm_work has joined #openstack-meeting-421:41
*** krtaylor has joined #openstack-meeting-421:41
*** banix has quit IRC21:43
*** sacharya has quit IRC21:45
*** dougwig has joined #openstack-meeting-421:45
*** fnaval has joined #openstack-meeting-421:46
*** BjoernT has quit IRC21:54
*** matrohon has quit IRC21:58
*** dannywilson has quit IRC21:58
*** dannywilson has joined #openstack-meeting-421:59
*** xingchao has joined #openstack-meeting-422:03
*** klamath has quit IRC22:05
*** xingchao has quit IRC22:08
*** SumitNaiksatam has quit IRC22:12
*** sarob has joined #openstack-meeting-422:13
*** bknudson has quit IRC22:22
*** sigmavirus24 is now known as sigmavirus24_awa22:27
*** VW_ has quit IRC22:33
*** galstrom is now known as galstrom_zzz23:00
*** dannywilson has quit IRC23:03
*** eghobo has quit IRC23:04
*** eghobo has joined #openstack-meeting-423:04
*** xingchao has joined #openstack-meeting-423:05
*** dannywilson has joined #openstack-meeting-423:05
*** xingchao has quit IRC23:14
*** sarob has quit IRC23:16
*** sarob has joined #openstack-meeting-423:23
*** dannywilson has quit IRC23:26
*** sdake_ has joined #openstack-meeting-423:27
*** sarob has quit IRC23:28
*** xingchao has joined #openstack-meeting-423:30
*** sdake has quit IRC23:30
*** sdake has joined #openstack-meeting-423:33
*** sdake_ has quit IRC23:37
*** MarkAtwood has quit IRC23:45
*** eghobo has quit IRC23:51
*** vishwana_ has quit IRC23:58

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