Thursday, 2015-08-27

*** sigmavirus24 is now known as sigmavirus24_awa00:06
*** armax has quit IRC00:13
*** padkrish has joined #openstack-meeting-400:14
*** Swami has joined #openstack-meeting-400:16
*** armax has joined #openstack-meeting-400:17
*** Swami_ has quit IRC00:17
*** bnemec has quit IRC00:18
*** cloudtrainme has joined #openstack-meeting-400:29
*** Swami has quit IRC00:35
*** vivek-ebay has quit IRC00:35
*** puranamr has quit IRC00:36
*** sdake has quit IRC00:39
*** padkrish has quit IRC00:43
*** salv-orlando has quit IRC00:43
*** padkrish has joined #openstack-meeting-400:44
*** padkrish has quit IRC00:44
*** wshao has joined #openstack-meeting-400:45
*** padkrish has joined #openstack-meeting-400:45
*** bnemec has joined #openstack-meeting-400:47
*** padkrish has quit IRC00:47
*** xichengc has joined #openstack-meeting-400:50
*** armax has quit IRC00:53
xichengc#info Xicheng Chang00:56
wshao#startmeeting Compass01:00
openstackMeeting started Thu Aug 27 01:00:32 2015 UTC and is due to finish in 60 minutes.  The chair is wshao. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: Compass)"01:00
openstackThe meeting name has been set to 'compass'01:00
wshao#info Weidong01:00
*** cloudtrainme has quit IRC01:01
wshaoLet's give a few minutes.01:01
wshaothe main agenda is to check on Ansible status.01:01
xichengcOK01:01
wshaoxichengc: do you know the current status?01:03
xichengcFrom my part, i have the parameters sorted out.01:04
wshaook. ready to work on the adapter related conf changes?01:04
xichengcand will start writing metadata for the new adapter01:04
xichengcas well as adding adapters01:04
wshaook cool. sounds good.01:04
xichengcbut the adapter confs will still be written in the "old way"01:04
wshaothat is fine.01:06
*** yamamoto has joined #openstack-meeting-401:06
wshaoit is more important to have it in the workflow, making it easy to verify the actual deployment01:06
xichengcwe should wait for baiguoku's update on his part...01:06
wshaook. I will follow up on that.01:07
xichengcwill he join us today?01:07
wshaoFor compass-ci, could you remove the failing job?01:07
wshaoit triggers emails01:07
xichengcI have already removed the failing periodic jobs01:07
*** KunalGandhi has quit IRC01:08
xichengcnow you only see the successful ones.01:08
*** watanabe_isao has joined #openstack-meeting-401:08
xichengcthose failing jobs are based on old dev branch which was deprecated long time ago.01:08
wshaoi see.01:08
wshaoIs compass-ci all good now? with logs available?01:09
wshaoi mean, available through public IPs01:10
*** meimei1 has joined #openstack-meeting-401:10
xichengcyes01:10
wshaoall right, cool.01:10
xichengchttp://12.234.32.108/logs/01:10
xichengcyou need to give status server and log server two domain names01:10
wshaoI will add that.01:10
xichengci also customized the zuul status page a little bit01:11
xichengcwith compass logo and everything01:11
xichengchttp://12.234.32.107/01:11
wshaonice.01:11
wshaomake sure everything is git-trackable01:11
wshaoincluding the zuul config.01:12
xichengcyes, all the changes i made have been added to compass-core/project-config01:12
wshaomeimei1: do you know the status of ansible (for kilo) testing status?01:13
*** chenshuai has joined #openstack-meeting-401:14
meimei1the deployment of all-in-one is failure01:14
chenshuai#info chenshuai01:14
meimei1said by xuhan01:14
*** xuhan has joined #openstack-meeting-401:14
wshaook.01:14
meimei1I am not very familiar01:15
wshaodo you know what the errors are?01:15
xuhandownload galera db failed01:15
xichengcyou mean the upstream os-ansible-deployment?01:15
xuhanyes01:15
xichengcis this the only problem?01:16
wshaoFor this type of errors, you could email us in the openstack-dev mailing list (with [Compass] prefix). or unicast to me.01:16
wshaoi know Chef allows setting of a local repo, or we could do this at the OS installation step. add the local repo with high precedence01:17
xuhanpreviously problems  has been resolved01:18
wshaoxichengc: could you help on this offline?01:18
*** baigk has joined #openstack-meeting-401:18
xichengcwhat do you mean by "chef allows setting of a local repo"?01:18
xichengcyou meant apt repo?01:19
xichengcfor example?01:19
xuhanosad will git clone all openstack repo, at a slower speed.01:19
wshaochef provider allows custom repo setting, as I recall. But in Compass, we config this at the OS level.01:19
xichengcI see.01:19
xichengci remember osad has the repo settings in conf files right?01:20
xichengcor hardcoded in tasks?01:20
wshaobaigk: xichengc's question is for you01:20
xichengcor xuhan01:20
wshaook. let's address the error after the meeting.01:22
wshao I do not have anything else on the agenda. anything else?01:22
*** yamamoto has quit IRC01:22
xichengcI do have something less prioritized though...01:23
wshaosure01:23
*** meimei1 has quit IRC01:24
xichengcif we have time, we should consider giving our 3rd testing suites(zuul, jenkins, gearman) the ability to avoid racing problems.01:24
xichengcfor example, change A + master head works, change B+ master head works, but A+B+master head doesn't01:24
*** yamamoto has joined #openstack-meeting-401:24
xichengczuul actually has the ability to run test against all pending changes to determine the potential failures.01:25
wshaoi see. I am not familiar with this. please write in an email?01:25
xichengcbut scalability could be a problem if we have many contributors.01:25
xichengcsure.01:25
*** s3wong has quit IRC01:26
baigkxichengc: yes, it's in defaults/repo_packages/openstack_clients.yml01:26
xichengcthanks baigk01:26
xichengcwe can discuss offline about this.01:27
*** meimei1 has joined #openstack-meeting-401:27
*** yamamoto has quit IRC01:28
xichengcbaigk01:29
xichengccan we have a short phone call after this?01:29
*** vivek-ebay has joined #openstack-meeting-401:29
baigksome tasks are very slow , like "download lxc","Build all known python packages requirements" and "Create a build report for all known packages within a release"01:30
baigkok01:30
xichengcI will call you on espace01:30
xichengcanything other issues/questions/topics?01:31
xichengcespecially from Shanghai team?01:31
xichengccountdown 501:31
xichengccountdown 401:32
xichengccountdown 301:32
xichengccountdown 201:32
xichengccountdown 101:32
xichengc#endmeeting01:32
*** bharathm has quit IRC01:32
*** dannywilson has joined #openstack-meeting-401:32
xichengcThank you all.01:32
*** wshao_ has joined #openstack-meeting-401:32
xichengcThough I don't think I can end it.01:32
xichengcweidong is back on..01:32
wshao_Done?01:32
xichengcwshao_ please #endmeeting01:32
xichengci am not allowed to01:33
*** dannywilson has quit IRC01:36
*** dannywil_ has joined #openstack-meeting-401:36
wshao_#endmeeting01:36
wshao_Will do it later01:36
*** dannywil_ has quit IRC01:41
*** bnemec has quit IRC01:41
wshao#endmeeting01:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:43
openstackMeeting ended Thu Aug 27 01:43:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/compass/2015/compass.2015-08-27-01.00.html01:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/compass/2015/compass.2015-08-27-01.00.txt01:43
openstackLog:            http://eavesdrop.openstack.org/meetings/compass/2015/compass.2015-08-27-01.00.log.html01:43
*** dims has joined #openstack-meeting-401:43
*** xichengc has quit IRC01:44
*** vivek-eb_ has joined #openstack-meeting-401:47
*** meimei1 is now known as May-meimei01:47
*** cloudtrainme has joined #openstack-meeting-401:48
*** vivek-ebay has quit IRC01:48
*** cloudtrainme has quit IRC01:58
*** armax has joined #openstack-meeting-401:58
*** May-meimei is now known as meimei-May02:02
*** cloudtrainme has joined #openstack-meeting-402:06
*** yamamoto has joined #openstack-meeting-402:10
*** jckasper has joined #openstack-meeting-402:18
*** sbalukoff has quit IRC02:18
*** jckasper has quit IRC02:27
*** KunalGandhi has joined #openstack-meeting-402:28
*** wshao has quit IRC02:30
*** wshao_ is now known as wshao02:30
*** wshao_ has joined #openstack-meeting-402:31
*** wshao_ has quit IRC02:31
*** bharathm has joined #openstack-meeting-402:32
*** vivek-eb_ has quit IRC02:32
*** KunalGandhi has quit IRC02:33
*** KunalGandhi has joined #openstack-meeting-402:34
*** yamahata has quit IRC02:34
*** bharathm has quit IRC02:38
*** salv-orlando has joined #openstack-meeting-402:44
*** salv-orlando has quit IRC02:48
*** dims has quit IRC02:56
*** nhairston has joined #openstack-meeting-403:10
*** vivek-ebay has joined #openstack-meeting-403:13
*** nhairston has quit IRC03:20
*** SimonChung has joined #openstack-meeting-403:30
*** SimonChung1 has joined #openstack-meeting-403:31
*** SimonChung has quit IRC03:34
*** xuhan1 has joined #openstack-meeting-403:42
*** xuhan has quit IRC03:43
*** xuhan1 is now known as xuhan03:43
*** irenab has joined #openstack-meeting-404:00
*** watanabe_isao has quit IRC04:00
*** harshs has quit IRC04:01
*** jerryz has quit IRC04:01
*** ajayaa has joined #openstack-meeting-404:20
*** puranamr has joined #openstack-meeting-404:27
*** vivek-ebay has quit IRC04:33
*** yamamoto has quit IRC04:40
*** jerryz has joined #openstack-meeting-404:44
*** chenshuai has quit IRC04:48
*** puranamr has quit IRC04:50
*** xuhan has quit IRC04:51
*** armax has quit IRC05:01
*** ajayaa has quit IRC05:01
*** salv-orlando has joined #openstack-meeting-405:02
*** nkrinner has joined #openstack-meeting-405:02
*** armax has joined #openstack-meeting-405:05
*** sdake has joined #openstack-meeting-405:05
*** irenab has quit IRC05:05
*** yamamoto has joined #openstack-meeting-405:05
*** sdake_ has joined #openstack-meeting-405:06
*** salv-orlando has quit IRC05:07
*** blakec has joined #openstack-meeting-405:07
*** sdake has quit IRC05:10
*** sdake_ is now known as sdake05:18
*** jpekkari has joined #openstack-meeting-405:20
*** wshao has quit IRC05:24
*** irenab has joined #openstack-meeting-405:28
*** pkoniszewski has quit IRC05:30
*** pkoniszewski has joined #openstack-meeting-405:30
*** lazy_prince has joined #openstack-meeting-405:36
*** xuhan has joined #openstack-meeting-405:38
*** armax has quit IRC05:43
*** dims has joined #openstack-meeting-405:46
*** ajayaa has joined #openstack-meeting-405:49
*** dims has quit IRC05:52
*** xuhan1 has joined #openstack-meeting-405:54
*** xuhan has quit IRC05:55
*** xuhan1 is now known as xuhan05:55
*** blakec has quit IRC05:56
*** xuhan has quit IRC06:04
*** KunalGandhi has quit IRC06:07
*** xuhan has joined #openstack-meeting-406:20
*** fawadkhaliq has joined #openstack-meeting-406:21
*** pkoniszewski has quit IRC06:35
*** fesp has joined #openstack-meeting-406:35
*** wojdev has joined #openstack-meeting-406:36
*** fesp has quit IRC06:37
*** stanchan has joined #openstack-meeting-406:38
*** bharathm has joined #openstack-meeting-406:39
*** xuhan has quit IRC06:40
*** xuhan has joined #openstack-meeting-406:40
*** salv-orlando has joined #openstack-meeting-406:47
*** stanchan has quit IRC06:48
*** numans has joined #openstack-meeting-406:49
*** pkoniszewski has joined #openstack-meeting-406:50
*** salv-orlando has quit IRC06:52
*** KunalGandhi has joined #openstack-meeting-407:03
*** blakec has joined #openstack-meeting-407:05
*** salv-orlando has joined #openstack-meeting-407:06
*** evgenyf has joined #openstack-meeting-407:07
*** blakec has left #openstack-meeting-407:09
*** KunalGandhi has quit IRC07:09
*** zeih has joined #openstack-meeting-407:13
*** zeih has quit IRC07:24
*** sdake has quit IRC07:29
*** zeih has joined #openstack-meeting-407:33
*** jerryz has quit IRC07:33
*** dims has joined #openstack-meeting-407:35
*** pkoniszewski has quit IRC07:38
*** pkoniszewski has joined #openstack-meeting-407:39
*** dims has quit IRC07:40
*** sbalukoff has joined #openstack-meeting-407:43
*** zeih has quit IRC07:44
*** matrohon has joined #openstack-meeting-407:44
*** yamahata has joined #openstack-meeting-407:53
*** xuhan has quit IRC08:07
*** xuhan has joined #openstack-meeting-408:07
*** irenab has quit IRC08:16
*** irenab has joined #openstack-meeting-408:19
*** lakshmiS has joined #openstack-meeting-408:21
*** akwasnie has joined #openstack-meeting-408:44
*** zeih has joined #openstack-meeting-408:48
*** irenab has quit IRC08:50
*** irenab has joined #openstack-meeting-408:51
*** zeih has quit IRC08:58
*** zeih has joined #openstack-meeting-409:01
*** xuhan has quit IRC09:09
*** xuhan has joined #openstack-meeting-409:10
*** xuhan has quit IRC09:12
*** xuhan has joined #openstack-meeting-409:16
*** zeih has quit IRC09:16
*** zeih has joined #openstack-meeting-409:22
*** irenab has quit IRC09:29
*** irenab has joined #openstack-meeting-409:34
*** yamahata has quit IRC09:46
*** dims has joined #openstack-meeting-409:50
*** wojdev has quit IRC09:58
*** wojdev has joined #openstack-meeting-409:59
*** bobmel has joined #openstack-meeting-410:27
*** yamamoto has quit IRC10:56
*** bharathm has quit IRC11:12
*** irenab has quit IRC11:18
*** xuhan1 has joined #openstack-meeting-411:24
*** xuhan has quit IRC11:25
*** xuhan1 is now known as xuhan11:25
*** pbourke has quit IRC11:28
*** pbourke has joined #openstack-meeting-411:29
*** irenab has joined #openstack-meeting-411:30
*** xuhan has quit IRC11:38
*** yamamoto has joined #openstack-meeting-411:41
*** yamamoto has quit IRC11:41
*** yamamoto has joined #openstack-meeting-411:41
*** yamamoto_ has joined #openstack-meeting-411:42
*** yamamoto has quit IRC11:46
*** mmedvede has quit IRC11:58
*** klamath has joined #openstack-meeting-411:59
*** mmedvede has joined #openstack-meeting-412:00
*** rfolco has joined #openstack-meeting-412:04
*** yamamoto_ has quit IRC12:10
*** yamamoto has joined #openstack-meeting-412:11
*** bharathm has joined #openstack-meeting-412:12
*** dims has quit IRC12:14
*** yamamoto has quit IRC12:16
*** bharathm has quit IRC12:17
*** ajayaa has quit IRC12:23
*** dims has joined #openstack-meeting-412:29
*** mmedvede has quit IRC12:29
*** mmedvede has joined #openstack-meeting-412:32
*** amotoki_ has quit IRC12:37
*** wojdev has quit IRC12:40
*** puranamr has joined #openstack-meeting-412:42
*** cloudtrainme has quit IRC12:46
*** puranamr has quit IRC12:50
*** jpekkari has quit IRC12:50
*** puranamr has joined #openstack-meeting-412:52
*** salv-orlando has quit IRC12:53
*** cloudtrainme has joined #openstack-meeting-412:53
*** GB21 has joined #openstack-meeting-412:57
*** baoli has joined #openstack-meeting-412:59
*** yamamoto has joined #openstack-meeting-413:00
*** rfolco has quit IRC13:01
*** lakshmiS has quit IRC13:03
*** aventerav has joined #openstack-meeting-413:05
*** wojdev has joined #openstack-meeting-413:07
*** yamamoto has quit IRC13:08
*** cloudtrainme has quit IRC13:12
*** GB21 has quit IRC13:12
*** GB21 has joined #openstack-meeting-413:14
*** puranamr has quit IRC13:15
*** singlethink has joined #openstack-meeting-413:23
*** salv-orlando has joined #openstack-meeting-413:23
*** sigmavirus24_awa is now known as sigmavirus2413:24
*** cloudtrainme has joined #openstack-meeting-413:25
*** bobmel has quit IRC13:25
*** cloudtrainme has quit IRC13:26
*** bknudson has joined #openstack-meeting-413:33
*** zehicle has joined #openstack-meeting-413:35
*** yamamoto has joined #openstack-meeting-413:37
*** dshakhray has joined #openstack-meeting-413:42
*** xingchao has joined #openstack-meeting-413:43
*** ftcpops has joined #openstack-meeting-413:53
*** kairat has joined #openstack-meeting-413:56
*** yamamoto has quit IRC13:57
*** bpoulos has joined #openstack-meeting-413:58
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, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting, dshakhray14:00
nikhil_k#startmeeting glance14:00
openstackMeeting started Thu Aug 27 14:00:08 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_k#topic agenda14:00
*** openstack changes topic to "agenda (Meeting topic: glance)"14:00
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
jokke_o/14:00
kairat0/14:00
dshakhrayo/14:00
bpouloso/14:00
flaper87o/14:00
nikhil_kThanks jokke_ for setting the agenda for today!14:00
GB21o/14:00
*** sabari has joined #openstack-meeting-414:00
*** cpallares has joined #openstack-meeting-414:00
rosmaitao/14:01
sigmavirus24o/14:01
sabario/14:01
*** bunting has joined #openstack-meeting-414:01
nikhil_kativelkov: around?14:01
mfedosino/14:01
buntingo/14:01
*** bharathm has joined #openstack-meeting-414:02
mfedosinnikhil_k, he's on another meeting14:02
nikhil_kmfedosin: I will let you give us some quick updates on artifacts if that's ok14:02
nikhil_k#topic updates14:02
*** openstack changes topic to "updates (Meeting topic: glance)"14:02
mfedosinokay14:02
nikhil_k#info artifacts updates14:02
mfedosinwe finished the client14:02
nikhil_kawesome14:03
jokke_\\o \o/ o// o/7 ... amazing guys!14:03
mfedosincurrently we got several comments and I'll fix them soon14:03
flaper87mfedosin: wooohoooo14:03
mfedosinalso I finished fixing filtration issues14:03
mfedosinAlex tested murano client today and it works fine14:03
nikhil_kmfedosin: are there any outstanding critical/high bugs to take care of at this point that may or may not be filed?14:04
*** fawadkhaliq has quit IRC14:04
mfedosinI didn't notice them14:04
nikhil_kperfect!14:04
mfedosinone issue with disabling api v3 by default14:04
jokke_mfedosin: and I saw you got your feature branch sorted out14:04
*** mclaren has joined #openstack-meeting-414:05
*** fawadkhaliq has joined #openstack-meeting-414:05
mfedosinwith grenade gate14:05
mfedosinhttps://review.openstack.org/#/c/215709/14:05
*** rfolco has joined #openstack-meeting-414:06
mfedosinI wrote a message to Mr. Dague, but still have no response from him14:06
*** bharathm has quit IRC14:06
mfedosinif you can please take a look how it can be fixed, please14:06
nikhil_klooks like, the erros isn't evident14:07
nikhil_kerror*14:07
*** krtaylor has quit IRC14:07
mfedosinyep, it's somewhere inside shell scripts14:07
mfedosinexactly here https://github.com/openstack-dev/grenade/blob/master/inc/upgrade#L6814:08
nikhil_kwe still have time, release process start tuesday sept 114:08
*** fawadkhaliq has quit IRC14:08
mfedosinff will be on sept 1 too?14:09
jokke_I'm willing to say that we move grenade to non-voting if that's the way to merge it14:09
jokke_ff should be Thu is that 3rd or so ... when L-3 is supposed to be tagged, no?14:09
nikhil_kI don't think people are gunna like it14:09
mfedosindefinitely it's the way :)14:10
nikhil_kwe don't have breaking features coming, so FF wasn't enforced. plus we have been careful with some of the proposals14:10
jokke_I mean if we can't get our experimental API being disabled by default other means :P14:10
mfedosinI hope to find Mr.Dague and listen to his comments14:10
nikhil_kmfedosin: email to ML to help rel-mgrs keep track14:11
mfedosinokay, will do14:11
*** rbak has joined #openstack-meeting-414:11
jokke_thnx mfedosin14:11
jokke_sounds good14:11
sigmavirus24mfedosin: is the API spec done?14:11
nikhil_kwe need to move on for now to give some time for other topics proposed earlier14:11
mfedosinKairat is working on it14:11
sigmavirus24please have them talk to the API-WG to speed this process up14:12
mfedosinsigmavirus24, so it will be done this week14:12
mfedosinsigmavirus24, I got you14:13
*** Bjoern_ has joined #openstack-meeting-414:13
nikhil_k#topic drivers updates14:14
*** openstack changes topic to "drivers updates (Meeting topic: glance)"14:14
nikhil_kAs we discussed the two most likely specs:14:14
nikhil_k1. https://review.openstack.org/19486814:14
nikhil_k2. https://review.openstack.org/17794814:14
nikhil_k1 needs some work and 2 looks in good shape14:14
flaper87The spec for 2 landed14:15
flaper87the code seems to be updated14:15
jokke_brilliant14:15
nikhil_kwe need reviews on14:15
nikhil_khttps://review.openstack.org/#/q/owner:%22Brianna+Poulos%22+status:open+project:openstack/glance,n,z14:15
flaper87Given the fact that we're 2 weeks away from FF, should we still be considering mergint new specs?14:15
* flaper87 should probably keep that for next drivers' meeting14:15
flaper87tl;dr: I think specs should be frozen by now14:16
bpoulosnikhil_k: thanks14:16
* flaper87 stfu14:16
nikhil_kI think both of these are very well discussed and the second one is quite updated. So, they are unikely to cause more trouble.14:16
flaper87bpoulos: great work, btw14:16
*** sdake has joined #openstack-meeting-414:16
bpoulosflaper87: thanks :)14:16
mfedosinfolks, about swift driver. https://review.openstack.org/#/c/207075/14:16
jokke_kudos bpoulos ... that looks good14:16
flaper87nikhil_k: I agree about Image signing, lets move that forward14:16
flaper87I'm worried about the spec that hasn't been merged, regardless of how much it's been discussed.14:16
mfedosinI think I'll publish the code next week14:16
bpoulosjokke_: thank you to you too14:16
flaper87but lets keep that for next week's meeting14:16
mclarenmfedosin: looking at the swift driver spec is on my todo list14:16
nikhil_kmfedosin: jokke_ and I had a chat on the store and client proposals14:17
mfedosinmclaren, thanks!14:17
mclarenmfedosin: I chatted with a swift core about it yesterday14:17
nikhil_kit seems unlikely for us to consider releases for store so the specs related to that haven't been top priority14:17
mfedosinthese are the results of testing https://etherpad.openstack.org/p/multithreaded-swift-tests14:17
mclarenwe have numbers? awesome!14:18
mfedosinthere is no hurry to merge it liberty, and i'm ok to postpone it to M14:18
jokke_nikhil_k: we will need the feature release of glance_store we carve stable/liberty out14:18
nikhil_kwe need to take care of these features after stable is cut14:18
jokke_nikhil_k: and that should be done well before we have release out14:18
nikhil_kmfedosin: we may be able to do this before M starts14:18
nikhil_kjokke_: right14:19
flaper87jokke_: ++14:19
mfedosinmclaren, yes, in average we have 2,5-3 times upload boost14:19
*** zeih has quit IRC14:19
flaper87jokke_: probably even before FF14:19
mfedosinand about 20-30% download14:19
nikhil_kok, if nothing critical on these topics, we need to move on14:20
mfedosinI think we should test the driver properly on scale before merge14:20
jokke_flaper87: store is not that big of an problem as glance is only consumer. But we need to have requirements for that stable release version set by rc114:20
nikhil_k#topic Oslo freezing14:20
*** openstack changes topic to "Oslo freezing (Meeting topic: glance)"14:20
*** cloudtrainme has joined #openstack-meeting-414:21
*** wojdev has quit IRC14:21
flaper87jokke_: it's not, I agree. But having an established workflow would be nice14:21
nikhil_kjokke_: that's you? ^14:21
flaper87jokke_: it'd be even nicer to follow it14:21
flaper87:P14:21
mclarenmfedosin: where the images segmented in swift?14:21
jokke_nikhil_k: yeah14:21
jokke_it's actually this week14:21
jokke_and that was more informational14:21
nikhil_klet me talk about established workflow, appripriate patchesm, review etc once Liberty is out. can't wait. Particularly security risks introduced14:22
jokke_just heads up this is happening so we need to keep eye on reuqirement changes14:22
jokke_so unless questions, next! ;)14:23
flaper87I've been ninja-approving requirements the whole cycle14:23
flaper87FYI14:23
*** yamahata has joined #openstack-meeting-414:23
flaper87after I saw them piling up14:23
nikhil_kjokke_: I think we need to delegate all requirement change to rel-mgrs14:23
flaper87:D14:23
*** yamahata has quit IRC14:23
jokke_nikhil_k: fine by me14:24
nikhil_kall those need to be handled by  them only14:24
jokke_flaper87: that seems to be only way to get them in14:24
*** yamahata has joined #openstack-meeting-414:24
nikhil_kas they shouldn't break other projects14:24
jokke_any +2s gets thrown away by new proposal before +a14:24
*** wojdev has joined #openstack-meeting-414:24
nikhil_kany breaking change would be the blame of single person if not collab with rel-mgrs. it was a big headache last cycle14:25
*** Bjoern_ has left #openstack-meeting-414:25
nikhil_k#topic Feature freeze14:25
*** openstack changes topic to "Feature freeze (Meeting topic: glance)"14:25
nikhil_kThe only two safe features are pointed above14:26
nikhil_kif there is something to bring up, this is the right time to consider everyone's feedback14:27
jokke_nikhil_k: so those two and bugfixes are our top 1 from today onwards?14:27
jcookwhat about the buffered reader change...let me grab linky14:27
jokke_artifacts obviously will live their own life for now14:27
mfedosinand also I want to discuss my suggestion with token expiration14:28
mfedosinhttps://review.openstack.org/#/c/199049/14:28
jcookhttps://review.openstack.org/#/c/120866/14:28
nikhil_kjcook: that may go depending on whether we afford to create store rel after it merges14:28
flaper87note that feature freeze is a dead line for new features14:29
flaper87not bug fixes14:29
nikhil_kthe spec itself looks good and is tried and tested change. it's a contained effort as well and likely not to break the world14:29
flaper87bug fixes can still land14:29
mfedosinshould I right a spec on this proposal?14:29
jcookmfedosin: +1 to having that as a thing14:29
nikhil_kmfedosin: let's discuss that later. I doubt it but good to consider the impact14:30
mfedosin*write14:30
jcookmfedosin: the fix (not necessarily a spec)14:30
mfedosinnikhil_k, sure14:30
nikhil_k#topic glanceclient feature/artifacts branch14:31
*** openstack changes topic to "glanceclient feature/artifacts branch (Meeting topic: glance)"14:31
jokke_that was me again :P14:31
nikhil_kjokke_: please no14:31
jokke_So in short I'd like to propose that we let artifact guys merge to the branch by their own convenience to keep it moving14:32
nikhil_kI think the point of FastTrack was to maintain project wide awareness14:32
nikhil_kand yet enabled faster workflow on artifacts particularly14:32
nikhil_kenable(14:32
jokke_nikhil_k: fair enough ... and I think that's really important on the glance where the code merges to the master14:32
nikhil_k+!14:33
jokke_but it was just a thought ... I have no problem pushing the button on client :D14:33
nikhil_k:)14:33
flaper87If we do that, we should first release the client so we can create the liberty branch from that tag w/o artifacts14:33
mfedosincurrently this branch lives on its own :)14:33
nikhil_kyep14:33
jokke_flaper87: artifacts are not part of liberty release14:33
*** TravT has joined #openstack-meeting-414:33
flaper87jokke_: I know14:33
flaper87that's what I said14:33
flaper87:D14:34
mfedosinand afaik all this code will be moved to muranoclient14:34
jokke_that was the whole point of the feature/artifacts branch :D14:34
flaper87or at least tried to14:34
*** krtaylor has joined #openstack-meeting-414:35
mfedosinI vote for allowing us to merge our code, of course14:35
jokke_mfedosin: I do undertand that you guys have priorities there as well, but I'm seriously expecting you to keep that feature branch up to date ... I'm happily -2'ing any syncs from muranoclient to glanceclient when we're bringing artifacts finally in ;)14:35
flaper87can we discuss this when mitaka dev starts?14:35
mfedosinflaper87, sure14:36
jokke_but I'm really happy to keep the workflow as it is for that branch as well as there is conserns14:36
nikhil_kmfedosin: let's not. it wont be worthy14:36
ativelkovjokke_: we don't plan to sync anything from murano to glance14:36
jokke_ativelkov: thanks ;)14:36
nikhil_k#topic python-glanceclient release14:37
*** openstack changes topic to "python-glanceclient release (Meeting topic: glance)"14:37
jokke_ok to the sore point of the day14:37
nikhil_kmclaren: ^14:37
mclarenok, I guess it's good to talk through this14:37
mclarenA couple of points14:38
mclarenFirst, I think a 1.0.0 release is not just-another-release14:38
*** salv-orlando has quit IRC14:38
mclarenwe should try and squash any bugs which we don't think belong in a 1.0.014:38
mclarenwould it be possible to do something like tag client bugs we'd like to see fixed in 1.0.0?14:39
mclarenburn through them, and then release?14:39
nikhil_kI sorta agree there but we are in a catch22 here14:39
jokke_mclaren: is there something critical still pending? I don't know if you have looked into the release notes review, but there is quite a bunch of bugfixes currently going in14:40
nikhil_kI think 1.0.0 should be pretty solid14:40
flaper87I believe the thing concerning mclaren is the v1 -> v2 change14:40
flaper87am I correct?14:40
mclarenthere's about 5 or 6 things I' personally suggest14:40
flaper87Is there something else?14:40
mclarenIt feels like we're rushing it a bit. For example14:41
mclarenI think we should be going through the commands and figuring out where the backwards non-compatabilities are14:41
*** jckasper has joined #openstack-meeting-414:41
jokke_mclaren: I'm also really disappointed about the fact that I personally gave you heads up 2 days ago when Nikhil sent that e-mail out, and you expressed your concerns publicly an hour before scheduled release14:41
mclarenso that when we notify the community it's easier for them to understand when they need to make changes14:42
mclarenand, if possible, what the change should look like14:42
mclarenI also think we need to give the other projects some time to update their scripts14:43
rosmaitai agree with jokke_ that the timing of the objection isn't ideal, but i also agree with mclaren that a change that breaks triple-O is problematic14:43
nikhil_kso, figuring out back-compat should not be a problem to be sorted out in glance14:43
mclarenreleasing this and breaking several things (we haven't done the audit to figure out what breaks, or notified others so they can do it)14:43
jokke_mclaren: so do you think the projects that has had almost 6 months time to adjust their scripts would do it in next six if we wait again?14:44
mclarenwould cause some consternation14:44
flaper87FWIW, we've already broken puppet because they run on trunk, I believe14:44
flaper87"broken"14:44
nikhil_kas long as we rel as per semantics that suggest so14:44
flaper87One more thing, stable branches are capped, someone running Kilo shouldn't be consuming 1.014:44
flaper87stable branches' requirements*14:44
jokke_flaper87: no, they're broken because one part of them runs trunk another releases14:44
*** zehicle has quit IRC14:44
flaper87jokke_: what did I say?14:44
flaper87anyway14:45
flaper87I think breaking backwards compatibility with this release cannot be avoided but communicating the change properly is important14:45
mclarenAgreed14:46
jokke_++14:46
mclarenI think there may be some things we'd want to consider before 1.0.0, for example14:46
flaper87However, I'd like this release to be part of Liberty and not wait until Mitaka14:46
nikhil_kWho can take the action item for figuring out all the projects that break because of this and fix it before a set date?14:46
mclarenthere are ~30 metadef commands that show up when you just type 'glance'14:46
flaper87nikhil_k: mclaren can :P14:47
mclarenI think it would be neater to move those to sub-commands under a single 'metadef' command. That becomes harder to do if we're not on a major version bump14:47
* flaper87 ducks14:47
mclarennikhil_k: that's not our job. Our job is to communicate this.14:47
rosmaitamclaren: +1 about metadefs ... iirc, the metadefs sub-team did not object to that14:48
*** yamahata has quit IRC14:48
mclarenI think we need to allow people to tag bugs for 1.0.0 and then negotiate what folks think are reasonable14:48
*** lakshmiS has joined #openstack-meeting-414:48
nikhil_kok, who can figure out what all modes of communication we need to adopt besides rel notes that other projects rely on?14:48
flaper87Can we start by sending an email to the OPs mailing list and os-dev ?14:48
flaper87I believe those 2 are enough14:48
mclarenwhile we're doing that we can send a mail to the ml - with a deadline14:49
*** yamahata has joined #openstack-meeting-414:49
flaper87and mention it'll be released as part of "Liberty"14:49
mclarenso actions:14:49
nikhil_kso, if we postpone for such changes then this won't happen in liberty afaict14:49
mclaren1. identify incompatabilies 2. communicate them 3. tag bugs 4. fix bugs 5. release14:50
jokke_just to be realistic here there is lots of things that would be nice to have, but either we do this release in fairly near future or we make the call to postpone the 1.0.0 release. The later case means that we ask rel management to cut our stable/liberty branch from 0.19.0 and backport the bugfixes needed14:50
nikhil_kThat looks neat approach mclaren ! And I can settle with it if we hanve't made a prior commitment for rel with v2 as default14:51
*** dims has quit IRC14:51
*** dims has joined #openstack-meeting-414:51
flaper87I think 1, 2 and 3 gotta happen this week14:52
*** KunalGandhi has joined #openstack-meeting-414:52
flaper87well, it's Thu.14:53
rosmaitahere's a start on the email: https://etherpad.openstack.org/p/glanceclient-1.0.0-warning14:53
nikhil_kor the order of action can be 1. rel notes (high level changes) 2. do in parallel (critical bugs, tagging, identifying incompat and raising on ML as they are found)14:53
jokke_the problem with the client is that we're not the only consumers (or we do not consume it at all) so we need to give time to the projects depending on us to identify the bugs that the release will bring up14:53
jokke_flaper87: and 5. early next14:53
nikhil_kclient rel needs to happen this week14:53
nikhil_kotherwise rel-mgrs will most likely not agree as it breaks the world14:53
mclarenit just feels we're rushing this too much14:54
jokke_nikhil_k: that's my expectation as well14:54
*** jckasper has quit IRC14:54
nikhil_kLike I mentioned this before, we have a conflicting push equally strong requirement for release and no-release. So, let's start with ML.14:54
jokke_nikhil_k: thus either we release, collect the feedback and get the bugs fixed so we have something shiny to start M cycle or we keep 0.19.0 as our last feature release of the client14:55
*** carl_baldwin has joined #openstack-meeting-414:55
nikhil_kjokke_: right14:55
nikhil_kI need to given some time for store rel14:55
*** armax has joined #openstack-meeting-414:55
jokke_for liberty I mean, not for infinite :P14:55
nikhil_kwe can continue client convo on -glance14:55
nikhil_k#topic glance_store release14:55
*** openstack changes topic to "glance_store release (Meeting topic: glance)"14:55
mclarenI'm not sure it's a great idea but we could switch master back to v1 (temporarily) and release that14:56
flaper87mclaren: no, please.14:56
rosmaitamclaren: i think that sends the wrong message14:56
mclarenokok14:56
flaper87:P14:56
*** numans has quit IRC14:56
*** KunalGandhi has quit IRC14:57
nikhil_kjokke_: anything imp on store?14:57
nikhil_kjcook: wanna raise anything here?14:57
jcooknikhil_k: hi14:57
jokke_nikhil_k: this was here just to remind folks that we need to do the feature release for _store as well to get the requirement update done14:57
jcookI have a few tickets that we'd like to get in for liberty14:57
jokke_and basis where we cut our stable branch14:57
*** yamamoto has joined #openstack-meeting-414:58
jcookhttps://review.openstack.org/#/c/170104/14:58
jcookhttps://review.openstack.org/#/c/196240/14:58
jcookhttps://review.openstack.org/#/c/217370/14:58
jcookhttps://review.openstack.org/#/c/207075/14:58
jcookhttps://review.openstack.org/#/c/199049/14:58
jcooksome mfedosin raised already14:58
nikhil_kjcook: jokke_ is our stability liaison and is being stringent on what we can get in to avoid breakage. Now, we don't want to break the world but store is just being consumed by glance, not sure if horizon yet.14:59
jcookoh...this is glance store discussion not oopen discussion14:59
jcooksorry14:59
flaper87nikhil_k: Can we have an etherpad with the reviews we should focus on ?14:59
jokke_as said bugfixes are not in rush yet14:59
jokke_but we need to be feature complete soon15:00
flaper87FF is just for features, not bug fixes15:00
nikhil_khttps://etherpad.openstack.org/p/glance-liberty-3-reviews15:00
flaper87Feature Freeze (FF)15:00
flaper87nikhil_k: danke15:00
nikhil_kwe are out of time!15:00
nikhil_kthanks all!15:00
mclarenthanks15:00
jokke_thanks!15:00
nikhil_k#endmetting15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Aug 27 15:00:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-27-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-27-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-27-14.00.log.html15:00
*** bunting has left #openstack-meeting-415:00
nikhil_kTravT: hi15:00
TravThi nikhil_k15:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Aug 27 15:01:02 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. 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: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
*** sjmc7 has joined #openstack-meeting-415:01
*** bpoulos has left #openstack-meeting-415:01
*** mclaren has quit IRC15:01
TravTwe'll  wait a minute or two.15:01
david-lyleo/15:01
lakshmiSo/15:01
sjmc7o/15:02
*** krtaylor has quit IRC15:02
TravTnikhil_k is sigmavirus24 around today?15:02
TravTdidn't see his name in latter part of glance meeting15:02
sigmavirus24yes sorry15:02
TravToh good15:02
sigmavirus24$work is keeping me distracted15:02
*** yamamoto has quit IRC15:02
TravT$ugh15:02
TravTok agenda here:15:03
TravT#link https://etherpad.openstack.org/p/search-team-meeting-agenda15:03
*** nkrinner has quit IRC15:03
*** kairat has left #openstack-meeting-415:03
*** wojdev has quit IRC15:03
TravT#Mitaka Summit Sessions15:03
TravT#topic Mitaka Summit Sessions15:03
*** openstack changes topic to "Mitaka Summit Sessions (Meeting topic: openstack search)"15:03
TravTso, first of all, we did get a main conference session accepted15:04
TravThttps://mitakadesignsummit.sched.org/event/51d3ca10844052e650c130eebe7264f9#.Vd8ji9NVhBd15:04
TravTIf others are interested in being a part of that, let's talk later.15:04
rosmaitao/15:04
TravThi rosmaita15:04
TravTso, thierry sent out a meeting saying we have to put in a requests for session by August 31st15:05
*** MarkAtwood has joined #openstack-meeting-415:05
TravTRequests for fishbowls vs workrooms vs contributors meetups.15:05
*** MarkAtwood has quit IRC15:06
TravTthere are less sessions overall available for vancouver15:06
rosmaitawe should prob ask for 1 of each?15:06
TravTand less fishbowls.15:06
*** fawadkhaliq has joined #openstack-meeting-415:06
TravTyesterday in the horizon meeting, i put up a topic to have a joint horizon / searchlight session15:06
sjmc7contributor meetup we can organize elsewhere if we have to. fishbowl would be good in case other people are interested in getting involved15:07
TravTdavid-lyle supported it.  thanks david-lyle15:07
TravTother horizoner's seemed good with it.15:07
rosmaitasjmc7: +115:07
TravTthe fishbowls are advertised.15:08
sjmc7right15:08
TravTso, it might bring in cores from other projects15:08
TravTwe'd want them to help review plugins, even if we develop them.15:08
*** evgenyf has quit IRC15:08
*** GB21 is now known as GB21-afk15:08
rosmaitaTravT: +115:09
TravTit also might be 3 of us staring at each other in a big room.15:09
*** SimonChung1 has quit IRC15:09
TravT:P15:09
rosmaitawe're not so bad on the eyes15:10
TravTlol15:10
sjmc7yeah.... i suspect there'll be less people there than vancouver15:10
rosmaitaSearchlight: the best-looking project15:10
TravTsweet!15:10
*** fawadkhaliq has quit IRC15:10
lakshmiSwe need to invite one core from each project to write a plugin for us :)15:10
TravTif we have a fishbowl, it would need to have a good topic... not just a presentation. that's what our main session presentation will be about.15:10
ekarlsooii guys15:10
TravTo/ ekarlso15:11
ekarlsohmm, I can maybe do a plugin for Cue also15:11
ekarlsoseeing that i've worked on that15:11
rosmaitai like lakshmiS idea: deep dive into Searchlight plugins?15:11
TravTthat would make sense.15:11
lakshmiSat the least be a SME for that project and talk to us15:11
TravTand we could send an invite to each project team seeing if 1 person could attend.15:12
sjmc7yeah, that's a good idea15:12
TravTok, so here's what I think is current summary:15:12
TravTRequest:15:12
TravT1 fishbowl: Topic to deep dive into plugins and invite SME from each project15:13
TravT1 Working session for us: (possible ideal topic is multi-region searching)15:13
TravT1 Shared session with horizon15:13
sjmc7works for me15:14
TravTshould we request the contributors meetup slot as well?15:14
sjmc7depends how many of us there'll be there15:14
TravTyeah.15:15
sjmc7if it's 3 of us staring at each other, i at least want to be in a pub15:15
TravTand how if overlaps with the other projects15:15
TravTi think we'll need more time to talk than one working session, but we can try to meet informally as well.15:15
TravTi want to be respectful of the many projects needing slots15:16
*** jwagner_away is now known as jwagner15:16
rosmaita+1 to pub, +1 to multiregion searching session15:17
TravTmaybe i'll add in a request for one more working session but not a request for contributors meetup. we'll do that after hours.15:17
TravT1 fishbowl, 2 working sessions, 1 joint session with horizon.15:18
david-lyleI would expect most of us have conflicts for contributors meetup, so that makes sense15:18
TravTThat may be more than we can get.15:18
TravTokay, going once15:18
TravTtwice15:18
TravTsold15:19
TravT#action TravT send session summit request to ttx15:19
TravT#topic Liberty 3 Deadlines15:19
*** openstack changes topic to "Liberty 3 Deadlines (Meeting topic: openstack search)"15:19
TravTAs usual, end of cycle is upon us, which means at least two things.15:20
TravTPeople are getting frantic15:20
TravTZuul jobs are taking a long time15:20
TravT   Feature Freeze: September 3rd15:20
TravT   RCs Start: September 21st15:20
TravT   Final RC September 9th15:20
TravTI sent an email to thierry seeking advice on how we should handle things15:21
*** GB21-afk has quit IRC15:21
TravTHere are some snippets:15:21
*** singleth_ has joined #openstack-meeting-415:21
TravTGiven how new Searchlight is at this point, I'd say you don't really15:21
TravTneed to enforce a strict feature freeze. If you do, it's a tool to15:21
TravTreduce the risk of introducing regressions by selecting which commits are acceptable as you get closer to the end of the dev cycle.15:21
sjmc7that seems sensible15:22
*** pennerc has joined #openstack-meeting-415:22
TravTI also asked about numbering scheme.  As you all probably know, OpenStack is moving to new scheme15:22
TravTx.x.x15:22
TravTmany will be at 8.0.015:23
TravTin liberty15:23
TravTbut thierry said:15:23
TravTI'd say the first release should be 1.0.0. If it's barely functional,15:23
TravTyou could even number it 0.1.0. Your choice really.15:23
TravTI'm not sure of all the ramifications of choosing one vs the other.15:23
lakshmiS0.1.0 seems like beta15:24
nikhil_k0.1.015:24
nikhil_kseems better15:24
lakshmiSwould horizon use it if its 0.1.015:24
nikhil_kbut then the rel versioning is being matched with cycle afaik15:24
david-lylethe version # doesn't change the level of functionality15:24
nikhil_klike first cycle of incubation was 1.0.0 but not sure if true for all prj15:25
*** singlethink has quit IRC15:25
*** s3wong has joined #openstack-meeting-415:25
david-lylelakshmiS: I would prefer it to come in as a plugin until more mature, honestly15:25
nikhil_krel-mgrs can better suggest the versioning coherent with os projs15:25
david-lylebut horizon is trying to reduce scope15:25
*** s3wong has quit IRC15:26
TravTdavid-lyle plugin external to horizon repo or not?  i think we always talked about it being a plugin, but you initially suggested still being in horizon repo.15:26
david-lyleTravT: I'd be ok with it in /contrib15:26
TravTa plugin panel is easy.15:27
TravTbut plugin search provider for APIs for various tables and global top nav, is a bit diff15:27
david-lyleTravT: I agree, there are some extensibility hooks needed15:28
david-lylewe can take this offline15:28
TravTokay.15:28
david-lylebut my argument is to horizon the version # is not important15:28
david-lylebetter to set valid expectations, IMO15:28
TravTthe point of this topic is actually for us to set a release cadence15:29
*** pennerc has left #openstack-meeting-415:29
david-lyleso let's pop two levels :)15:29
TravTThere are various tags for this in OpenStack governance15:29
TravThttps://github.com/openstack/governance/blob/master/reference/tags/release_independent.rst15:29
TravThttps://github.com/openstack/governance/blob/master/reference/tags/release_cycle-with-milestones.rst15:30
TravThttps://github.com/openstack/governance/blob/master/reference/tags/release_cycle-with-intermediary.rst15:30
TravThttps://github.com/openstack/governance/blob/master/reference/tags/release_managed.rst15:30
TravTA lot to read through there15:31
TravThttps://github.com/openstack/governance/blob/master/reference/tags/release_has-stable-branches.rst15:31
rosmaitai will admit i have only read the first one, but release:independent sounds good to me, at least to start with15:32
david-lylefor where the project is, I think independent makes sense15:32
david-lylethen move to align with release cycle with milestones as it matures15:32
rosmaitaare there any bad implications of that?  we can always change later, right?15:32
david-lylerosmaita: the only one I can think of is packaging15:32
david-lylemost distros would likely not include searchlight with 8.0.015:33
rosmaitagotcha15:33
david-lylebut that may be ok for 0.1.0 ??15:33
TravTa certain company i'm affiliated with is wanting to include it in a release sooner than later15:34
david-lylethat's a knife that cuts both ways15:34
rosmaitawhat would our plan be, then ... 0.1.0, 0.2.0, 0.3.0 and then immediately 9.0.0 ? to make the packaging work, i mean15:34
*** dshakhray has quit IRC15:35
david-lylethat's a better transition than 1.0.0 2.0.0 9.0.015:36
TravTI think we should target releases for the end of cycles.  but, i like the idea of releasing intermediate releases at our own cadence.15:36
david-lyleIronic and Swift are the only two mainstream projects that have independent release cycle15:36
*** singlethink has joined #openstack-meeting-415:36
TravTthis initial release perhaps should be sub-1.0 though15:37
david-lylebut they are standalone as well15:37
*** zehicle has joined #openstack-meeting-415:37
nikhil_kagree15:37
TravTi would not want to have to be held to a perfect API until we've actually integrated several searches from horizon15:37
*** zehicle has quit IRC15:37
david-lylebut a lot of early project start with independent15:37
*** zehicle has joined #openstack-meeting-415:38
david-lyleit gives us more flexibility15:38
*** zehicle has quit IRC15:38
david-lylejust suggestions15:38
*** sdake_ has joined #openstack-meeting-415:38
*** zehicle has joined #openstack-meeting-415:38
*** zehicle has quit IRC15:39
TravTbut we need a release to even let packagers start looking at the project, i believe15:39
*** zehicle has joined #openstack-meeting-415:39
*** zehicle has quit IRC15:39
TravTlet's revisit this in next weeks meeting, but please look through those release tags15:39
*** zehicle has joined #openstack-meeting-415:40
TravTright now, the summary of this discussion seems to be people leaning toward 0.1.0 for first release, timed with liberty.15:40
*** sdake has quit IRC15:40
*** zehicle has quit IRC15:40
*** singleth_ has quit IRC15:40
*** zehicle has joined #openstack-meeting-415:40
rosmaitaso what we're looking for is a tag that indicates not-yet-ready-for-prime-time but nonetheless worthy of being included in a distro15:41
nikhil_kI think that;s the right message15:41
*** zehicle has quit IRC15:41
*** zehicle has joined #openstack-meeting-415:41
nikhil_kbut I think there;s value to double check if we are communicating when our project got incubated with a number of particular style15:41
*** zehicle has quit IRC15:41
TravTalthough15:42
TravTif I read ttx's language again15:42
*** zehicle has joined #openstack-meeting-415:42
TravTI'd say the first release should be 1.0.0. If it's barely functional,15:42
TravTyou could even number it 0.1.0. Your choice really.15:42
nikhil_kyeah15:42
*** zehicle has quit IRC15:42
TravTi don't like the implication that 0.1.0 is barely functional15:42
TravTbut, that said it has not been tested at scale.15:42
*** bnemec has joined #openstack-meeting-415:42
*** zehicle has joined #openstack-meeting-415:43
rosmaitawhat would 0.9.9 mean?15:43
nikhil_kha15:43
*** zehicle has quit IRC15:43
TravTbased on glanceClient discussions, it would mean 5 years in and still not releasable to 1.0?15:43
TravT:P15:43
nikhil_kmeans, we had some alpha rel that never released15:43
*** zehicle has joined #openstack-meeting-415:43
*** zehicle has quit IRC15:44
nikhil_kTravT: I doubt it. py-client consumers run legacy code15:44
*** zehicle has joined #openstack-meeting-415:44
nikhil_kthat's why slowness in upgrade to rel numbers15:44
TravTnikhil_k: just a joke :)15:44
nikhil_kwe should ensure our plugin adopters stick to upstream15:44
*** zehicle has quit IRC15:44
nikhil_kTravT: heh15:44
TravTafter watching some of last meeting15:45
*** zehicle has joined #openstack-meeting-415:45
*** zehicle has quit IRC15:45
nikhil_k(continuing TravT )... feels like there are sad stories to tell15:45
TravT#action All to read release tags.  We'll revisit this next week15:45
*** zehicle has joined #openstack-meeting-415:45
TravT#topic review process15:46
*** openstack changes topic to "review process (Meeting topic: openstack search)"15:46
TravTThank you everybody for the time on Tuesday15:46
*** zehicle has quit IRC15:46
TravTI thought that went really well and we made good progress15:46
*** zehicle has joined #openstack-meeting-415:46
sjmc7yeah, it was good to have everyone together15:46
*** zehicle has quit IRC15:47
TravTwould anybody be available for another hour next Tuesday or Wednesday for similar activities.15:47
nikhil_k++15:47
TravTsame bat cave same bat time15:47
TravT?15:47
nikhil_kthis tuesday starts liberty-3 rel (fyi)15:47
*** zehicle has joined #openstack-meeting-415:47
*** zehicle has quit IRC15:47
nikhil_kfyi -- madness begins, bugs fixes, tagging, gate etc15:47
*** zehicle has joined #openstack-meeting-415:48
TravTso, are you suggesting a different day?15:48
*** jckasper has joined #openstack-meeting-415:48
nikhil_kearlier or later might help more15:48
*** zehicle has quit IRC15:48
nikhil_kgate would be more reliable and faster15:48
*** zehicle has joined #openstack-meeting-415:48
*** zehicle has quit IRC15:49
*** akwasnie has quit IRC15:49
TravTlakshmiS, you have one of the tougher schedules being in India.15:49
*** zehicle has joined #openstack-meeting-415:49
TravTdo you have any suggestions?15:49
*** zehicle has quit IRC15:49
lakshmiSaround this time any day is fine with me15:50
*** zehicle has joined #openstack-meeting-415:50
nikhil_kthat was just some information, being independent of the gate also works :)15:50
*** zehicle has quit IRC15:50
*** zehicle has joined #openstack-meeting-415:51
*** zehicle has quit IRC15:51
*** zehicle has joined #openstack-meeting-415:51
TravT#vote (what day next week works best for another hour review session) ? mon, tue, wed, thur, fri15:51
TravTguess that didn't work.15:51
*** vivek-ebay has joined #openstack-meeting-415:52
nikhil_kstartvote15:52
*** zehicle has quit IRC15:52
rosmaitawhile y'all are discussing times, what is the general feeling about stable branches? or do we think people should always use the most recent? i am inclined to the latter, since we're heavily tied to an external project15:52
rosmaitasorry, didn't mean to interrupt the vote15:52
*** zehicle has joined #openstack-meeting-415:52
*** zehicle has quit IRC15:52
nikhil_krosmaita: since this will be our first rel15:52
TravT#startvote (what day next week works best for another hour review session) ? mon, tue, wed, thur, fri15:52
openstackBegin voting on: (what day next week works best for another hour review session) ? Valid vote options are mon, tue, wed, thur, fri.15:52
openstackVote using '#vote OPTION'. Only your last vote counts.15:52
nikhil_kwe won't need a stable branch at this point15:52
*** pennerc has joined #openstack-meeting-415:53
*** singleth_ has joined #openstack-meeting-415:53
*** zehicle has joined #openstack-meeting-415:53
*** zehicle has quit IRC15:53
rosmaitanikhil_k: right, but i mean for "the future"15:53
TravTnikhil_k +1  i would vote against stable vote until M15:53
nikhil_k#vote fri15:53
david-lyle#vote any15:53
openstackdavid-lyle: any is not a valid option. Valid options are mon, tue, wed, thur, fri.15:53
lakshmiS#vote thu15:53
openstacklakshmiS: thu is not a valid option. Valid options are mon, tue, wed, thur, fri.15:53
lakshmiS#vote thur15:54
david-lyleno but my point was made openstack15:54
TravTlol15:54
*** zehicle has joined #openstack-meeting-415:54
rosmaitawhat time are we thinking?15:54
*** zehicle has quit IRC15:54
sjmc7:) any day is ok for me15:54
*** zehicle has joined #openstack-meeting-415:54
TravT7 PT, 8PT, 9PT i'd think would be some options15:55
*** singlethink has quit IRC15:55
*** zehicle has quit IRC15:55
nikhil_kyeah, actually except tue and thur, others work for me15:55
*** cloudnull has joined #openstack-meeting-415:55
*** zehicle has joined #openstack-meeting-415:55
TravT#endvote15:55
openstackVoted on "(what day next week works best for another hour review session) ?" Results are15:55
openstackfri (1): nikhil_k15:55
openstackthur (1): lakshmiS15:55
rosmaita#vote wed15:55
*** zehicle has quit IRC15:56
TravTI'll send something out.15:56
TravTrunning out of time.15:56
*** zehicle has joined #openstack-meeting-415:56
TravTSo, I listed several items in the agenda15:56
david-lyleso question, has anyone deployed searchlight on an environment for a period of time?15:56
*** zehicle has quit IRC15:56
*** bharathm has joined #openstack-meeting-415:56
TravTbeta ran in HOS env for a number of weeks pre-liberty.15:57
*** zehicle has joined #openstack-meeting-415:57
TravTbut none of the recent stuff15:57
*** zehicle has quit IRC15:57
david-lylewould be good validation before release15:57
TravTwe just had a discussion with our mgmt who said they could have some people help with things like that.15:57
*** zehicle has joined #openstack-meeting-415:57
nikhil_kno luck here yet15:58
TravTgood idea david-lyle15:58
TravT#topic reviews15:58
david-lyleTravT: great15:58
rosmaitai agree15:58
*** zehicle has quit IRC15:58
*** openstack changes topic to "reviews (Meeting topic: openstack search)"15:58
TravTSeveral on agenda15:58
TravTwill highlight one15:58
*** zehicle has joined #openstack-meeting-415:58
TravTPlease, look at nova plugin15:58
nikhil_knova?15:58
TravT    Nova instances plugin https://review.openstack.org/19885215:58
*** zehicle has quit IRC15:58
nikhil_kI started it but couldn't finish review15:58
TravTi beat up steve quite a bit now15:58
sjmc7i feel bruised15:59
*** zehicle has joined #openstack-meeting-415:59
*** zehicle has quit IRC15:59
TravTThere are others to review and some bugs to triage. will copy paste here15:59
TravT    Bug review (Please add any bugs needing attention below) https://bugs.launchpad.net/searchlight15:59
TravT    Critical & High15:59
TravT    Sorting https://review.openstack.org/#/c/206268/15:59
TravT    Other15:59
TravT    https://review.openstack.org/#/c/210759/15:59
TravT    Needs Triage15:59
TravT    Glance images not searchable after update notification: https://bugs.launchpad.net/searchlight/+bug/148678116:00
openstackLaunchpad bug 1486781 in OpenStack Search (Searchlight) "Glance images not searchable after update notification" [Undecided,New]16:00
TravT    Sorting name fields does not behave as expected: https://bugs.launchpad.net/searchlight/+bug/148823616:00
openstackLaunchpad bug 1488236 in OpenStack Search (Searchlight) "Sorting name fields does not behave as expected" [Undecided,New]16:00
*** zehicle has joined #openstack-meeting-416:00
TravT    Blueprint review (Please add any blueprints needing attention below) https://blueprints.launchpad.net/searchlight16:00
*** vivek-ebay has quit IRC16:00
TravT    Essential & High16:00
TravT    Nova instances plugin https://review.openstack.org/19885216:00
TravT    Designate Plugin https://review.openstack.org/#/c/199099/16:00
*** zehicle has quit IRC16:00
TravTOk, thanks everybody!16:00
*** irenab has quit IRC16:00
nikhil_kthanks!16:00
*** sjmc7 has left #openstack-meeting-416:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** VW_ has joined #openstack-meeting-416:00
openstackMeeting ended Thu Aug 27 16:00:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-27-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-27-15.01.txt16:00
*** zehicle has joined #openstack-meeting-416:00
*** Swami has joined #openstack-meeting-416:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-27-15.01.log.html16:00
cloudnullstartmeeting16:00
*** zehicle has quit IRC16:00
*** lakshmiS has left #openstack-meeting-416:01
nikhil_k# missing :)16:01
cloudnullhahaha16:01
cloudnull#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Aug 27 16:01:09 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** zehicle has joined #openstack-meeting-416:01
cloudnullthat worked better.16:01
cloudnullthank nikhil_k :)16:01
*** zehicle has quit IRC16:01
nikhil_k:)16:01
cloudnull#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
cloudnullwho's all here?16:01
*** zehicle has joined #openstack-meeting-416:01
*** evrardjp has joined #openstack-meeting-416:02
*** zehicle has quit IRC16:02
*** odyssey4me has joined #openstack-meeting-416:02
odyssey4meo/16:02
*** Sam-I-Am has joined #openstack-meeting-416:02
d34dh0r53o/16:02
Sam-I-Ammooo.16:02
evrardjpyop16:02
*** zehicle has joined #openstack-meeting-416:02
palendaeo/16:02
Apsuo/16:02
serverascodeo/ (just listening in)16:02
*** zehicle has quit IRC16:02
cloudnull#chair odyssey4me16:03
openstackCurrent chairs: cloudnull odyssey4me16:03
*** zehicle has joined #openstack-meeting-416:03
cloudnullo/ everybody :)16:03
*** b3rnard0 has joined #openstack-meeting-416:03
*** bknudson has quit IRC16:03
cloudnullok lets get started we have a bit to cover today .16:03
*** zehicle has quit IRC16:03
cloudnull#topic Liberty Release Blueprints (note dependencies)16:03
*** openstack changes topic to "Liberty Release Blueprints (note dependencies) (Meeting topic: OpenStack Ansible Meeting)"16:03
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/liberty16:03
*** zehicle has joined #openstack-meeting-416:03
*** zehicle has quit IRC16:04
*** pennerc has quit IRC16:04
cloudnullthree are quite a few des inflight right now.16:04
*** xingchao has quit IRC16:04
*** zehicle has joined #openstack-meeting-416:04
*** puranamr has joined #openstack-meeting-416:04
*** zehicle has quit IRC16:04
cloudnullodyssey4me: you might have a better understanding of where we are at this right now..16:04
odyssey4meyep, so we have some in flight16:05
*** zehicle has joined #openstack-meeting-416:05
odyssey4meincluding16:05
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/remove-upstream-repo-dependency16:05
*** zehicle has quit IRC16:05
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/compartmentalize-rabbitmq16:05
*** prometheanfire has joined #openstack-meeting-416:05
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/upgrade-mariadb-v1016:05
*** xingchao has joined #openstack-meeting-416:05
*** zehicle has joined #openstack-meeting-416:05
odyssey4methen we have a spec for16:05
cloudnull#link https://launchpad.net/openstack-ansible/+milestone/liberty-3 # issues in progress as well for lib-316:05
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/liberty-upgrade-path16:06
*** zehicle has quit IRC16:06
*** sdake_ is now known as sdake16:06
*** blewis has joined #openstack-meeting-416:06
*** zehicle has joined #openstack-meeting-416:06
odyssey4methis bug is pretty key to sort out soon16:06
odyssey4me#link https://bugs.launchpad.net/bugs/148659316:06
openstackLaunchpad bug 1486593 in openstack-ansible trunk "Neutron db migration issue in master" [Critical,New]16:06
*** zehicle has quit IRC16:06
odyssey4meI know that mattt has been working on that, but I think someone may need to take it over from him.16:07
cloudnulli think so too.16:07
*** zehicle has joined #openstack-meeting-416:07
cloudnullidk if i have time work it at this point so someone needs to run point.16:07
*** zehicle has quit IRC16:07
*** BjoernT has joined #openstack-meeting-416:07
cloudnullthis is a migration issue and may not be a major issues / problem however it would be great to be able to leverage some of the soft upgrade processes.16:08
*** zehicle has joined #openstack-meeting-416:08
Sam-I-Ami dont have time for it either :/16:08
Sam-I-Amit is neutrony, however.16:08
*** zehicle has quit IRC16:08
odyssey4memattt may need to pick it up again next week - I know that he's been chatting to the neutron team to figure out a better way to facilitate the upgrades16:08
*** jpeeler has quit IRC16:08
Sam-I-Amneutron needs some other changes for liberty16:08
*** zehicle has joined #openstack-meeting-416:08
evrardjpSam-I-Am: what do you mean, is it planned in the spec?16:09
*** zehicle has quit IRC16:09
odyssey4meI'll chat to him next week and figure out a plan of action for neutron upgrades in the plays.16:09
odyssey4methe issue is that the upgrade process for neutron has changed somewhat16:09
*** zehicle has joined #openstack-meeting-416:09
Sam-I-Amevrardjp: there's a lot of changes to neutron in liberty outside of the db16:09
Sam-I-Amnot for this conversation16:09
Sam-I-Amjust a note16:09
*** zehicle has quit IRC16:09
odyssey4meit gives some nice new features, but there isn't an easy way to parse the tool output to figure out whether an jupgrade is needed16:09
*** KLevenstein has joined #openstack-meeting-416:09
*** vivek-ebay has joined #openstack-meeting-416:10
*** zehicle has joined #openstack-meeting-416:10
cloudnullalso Sam-I-Am: these "other changes" is that something that you may be able to raise on the ML so that we can target what we want to do accordingly without spelling it out here in this meeting ?16:10
odyssey4meit has multiple branches now, and you need to verify several things before you decide what to do16:10
evrardjpit's important because it could be part of the liberty readiness, which means it has to be known for the spec16:10
*** zehicle has quit IRC16:10
*** singleth_ has quit IRC16:10
*** TravT has left #openstack-meeting-416:10
*** zehicle has joined #openstack-meeting-416:10
evrardjpsorry for my intervention if not relevant16:10
*** zehicle has quit IRC16:11
cloudnullnot at all evrardjp,  its relevant .16:11
odyssey4mefor now, just add an action item for me to pick this up with mattt next week16:11
*** zehicle has joined #openstack-meeting-416:11
*** vivek-ebay has quit IRC16:11
*** zehicle has quit IRC16:11
*** s3wong has joined #openstack-meeting-416:12
Sam-I-Ambbl16:12
cloudnull#action follow up with mattt regarding neutron changes16:12
*** zehicle has joined #openstack-meeting-416:12
*** zehicle has quit IRC16:12
cloudnull#action Sam-I-Am to drop note on the ML for OSAD to ensure we're making the proper changes for liberty16:12
cloudnullSam-I-Am:  voluntold :)16:12
evrardjp:)16:12
*** zehicle has joined #openstack-meeting-416:13
*** zehicle has quit IRC16:13
cloudnullIll try to have most of my inflight bps updated for reviews by weekend16:13
*** stevelle has joined #openstack-meeting-416:13
odyssey4meditto16:13
*** zehicle has joined #openstack-meeting-416:13
*** fawadkhaliq has joined #openstack-meeting-416:13
*** zehicle has quit IRC16:14
cloudnullthe https://blueprints.launchpad.net/openstack-ansible/+spec/remove-upstream-repo-dependency bp has reviews and should be ready for core to verify16:14
cloudnullsame with https://blueprints.launchpad.net/openstack-ansible/+spec/upgrade-mariadb-v1016:14
*** bgmccollum has joined #openstack-meeting-416:14
*** zehicle has joined #openstack-meeting-416:14
*** zehicle has quit IRC16:14
cloudnullpalendae:  you able to follow up with the current upgrade bits ?16:15
*** zehicle has joined #openstack-meeting-416:15
*** zehicle has quit IRC16:15
palendaeThe liberty upgrade path? Yeah16:15
cloudnullsweet!16:15
palendaeI thought I pushed an initial patch set, too, let me check16:15
*** zehicle has joined #openstack-meeting-416:15
*** SimonChung has joined #openstack-meeting-416:15
*** zehicle has quit IRC16:16
odyssey4mepalendae yep, although I'm not sure that your spec has had enough reviews yet16:16
palendaeTrue16:16
odyssey4melet me star the specs16:16
*** zehicle has joined #openstack-meeting-416:16
palendaeI would appreciate more16:16
*** bknudson has joined #openstack-meeting-416:16
*** zehicle has quit IRC16:16
cloudnullalso this wip change https://review.openstack.org/#/c/215291/ is in merge conflict at this point16:16
palendaehttps://review.openstack.org/#/c/215291/ was the change16:17
*** zehicle has joined #openstack-meeting-416:17
palendaeYUeah16:17
odyssey4me#link https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment-specs,n,z16:17
palendaeWill rebase it16:17
*** zehicle has quit IRC16:17
cloudnulltyvm sir16:17
*** zehicle has joined #openstack-meeting-416:17
*** zehicle has quit IRC16:18
cloudnullhttps://launchpad.net/openstack-ansible/+milestone/liberty-3 looks like its progressing nicely however as before odyssey4me you should have more context on that16:18
*** zehicle has joined #openstack-meeting-416:18
odyssey4mepalendae if you can remove the TODO's and either replace them with n/a's or some content, then we're good to go16:18
palendaeOk16:18
*** zehicle has quit IRC16:18
odyssey4meyeah, we're doing alright with liberty-316:19
*** zehicle has joined #openstack-meeting-416:19
*** GB21 has joined #openstack-meeting-416:19
odyssey4mein fact I think we've done brilliantly16:19
*** zehicle has quit IRC16:19
cloudnullyes i agree16:19
odyssey4mesome items may have to shift to the next milestone, but that's ok16:19
*** zehicle has joined #openstack-meeting-416:19
*** zehicle has quit IRC16:20
odyssey4meideally we need to start working on changing the deprecated options and doing updates to the conf/policy templates16:20
odyssey4mespeaking of which - this spec needs more reviews16:20
odyssey4me#link https://review.openstack.org/16897616:20
*** zehicle has joined #openstack-meeting-416:20
*** zehicle has quit IRC16:20
odyssey4mecloudnull perhaps a little tl/dr would be useful?16:20
*** zehicle has joined #openstack-meeting-416:21
*** zehicle has quit IRC16:21
cloudnulltl;dr. a new action plugin for ansible that makes it so we can render templates as is done by ansible but also override items in config without having to peramaterize all the things16:21
*** zehicle has joined #openstack-meeting-416:21
cloudnullthe action plugin supports json, yaml, and ini files.16:22
*** zehicle has quit IRC16:22
*** zehicle has joined #openstack-meeting-416:22
*** zehicle has quit IRC16:22
cloudnullthe plugin can be seen / reviewed here https://review.openstack.org/#/c/216790/1/playbooks/plugins/actions/crud_template.py,cm16:22
evrardjpI'll put my comments, but I really like the idea of it16:23
cloudnullwhich is a WIP review to replace the current copy_update plugin16:23
evrardjpcongrats16:23
*** zehicle has joined #openstack-meeting-416:23
*** zehicle has quit IRC16:23
cloudnullthanks evrardjp !16:23
*** zehicle has joined #openstack-meeting-416:24
odyssey4methe idea is to stop adding more and more parameters for overrides, make it simpler for deployers to understand how to add .conf settings they want and to reduce the work we have to do when we're looking at deprecations from cycle to cycle16:24
*** irenab has joined #openstack-meeting-416:24
*** zehicle has quit IRC16:24
cloudnullcurrent naming is crud_template (u have no naming originallity) but that name is subject to change.16:24
*** zehicle has joined #openstack-meeting-416:24
odyssey4mewe'll have to carry current settings/vars for a cycle (liberty) but we can remove them once we ship M16:24
cloudnulls/u have/i have/16:24
cloudnullthats the running thought16:25
*** zehicle has quit IRC16:25
odyssey4meperhaps we should chat about the name now16:25
cloudnullsure16:25
*** zehicle has joined #openstack-meeting-416:25
odyssey4mepersonally I prefer something along the lines of 'template_update' for the module/task and 'update_data' instead of cu_data for the arg16:25
*** zehicle has quit IRC16:25
odyssey4memaybe rather update_template for the module name16:25
evrardjpthe important is to know about this module, not the name...16:26
*** zehicle has joined #openstack-meeting-416:26
palendaeGood names are important16:26
cloudnullfair enough.16:26
*** zehicle has quit IRC16:26
palendae+1 for update_template16:26
evrardjpeasier to remember, so easier to know. I agree16:26
odyssey4meevrardjp sure, but the name and args do affect how easily the purpose is understood16:26
palendaeOr more communicative of intent/purpose16:26
evrardjpupdate_template seems easy to remember16:26
*** zehicle has joined #openstack-meeting-416:26
*** zehicle has quit IRC16:27
cloudnull+1 update_template sounds good to me16:27
*** zehicle has joined #openstack-meeting-416:27
evrardjp0118 999 88199 9119 725 ... 3 (for those who understand "that's easy to remember")... Sorry for this intrusion ;)16:27
*** zehicle has quit IRC16:27
*** zehicle has joined #openstack-meeting-416:28
cloudnullso pleaes review the spec/code its much appreciated.16:28
evrardjpwill do16:28
*** zehicle has quit IRC16:28
cloudnullafter some reviews come through ill update the naming16:28
*** dannywilson has joined #openstack-meeting-416:29
cloudnulland fix other bits noted16:29
*** matrohon has quit IRC16:29
*** dannywilson has quit IRC16:29
*** zehicle has joined #openstack-meeting-416:29
cloudnullmoving on, unless theres something else to note about the spec ?16:29
*** zehicle has quit IRC16:29
cloudnullor other specs ?16:29
*** dannywilson has joined #openstack-meeting-416:29
odyssey4me#link https://review.openstack.org/21377916:29
*** zehicle has joined #openstack-meeting-416:29
*** salv-orlando has joined #openstack-meeting-416:29
odyssey4meI'd like to revise it based on comments this weekend, so please review and comment.16:29
cloudnullkk16:30
*** zehicle has quit IRC16:30
*** zehicle has joined #openstack-meeting-416:30
odyssey4meNote to all that approving the spec will not result in an immediate repo split. It will simply allow us to create new repositories for new roles.16:30
*** zehicle has quit IRC16:30
odyssey4meany splits from the current repo will still require their own blueprint or spec.16:30
cloudnull++16:30
odyssey4me*and16:30
lbragstadodyssey4me: so the roles will exist in each temporarily, right?16:31
odyssey4methis is because the split of each role will require a lot of planning16:31
*** zehicle has joined #openstack-meeting-416:31
*** zehicle has quit IRC16:31
odyssey4melbragstad I'm not sure I understand what you mean?16:31
*** zehicle has joined #openstack-meeting-416:32
*** zehicle has quit IRC16:32
*** zehicle has joined #openstack-meeting-416:32
evrardjpI have a question, what's the plan for future roles? should we plan with the split in mind or include as usual?16:33
*** zehicle has quit IRC16:33
evrardjpbecause there is no mention of real date in the spec16:33
cloudnullevrardjp:  i'd include as usual for now.16:33
*** zehicle has joined #openstack-meeting-416:33
evrardjpok16:33
lbragstadodyssey4me: I think I answer my own question :)16:33
*** xingchao has quit IRC16:33
*** zehicle has quit IRC16:33
*** zehicle has joined #openstack-meeting-416:34
odyssey4meevrardjp it kinda depends on what the role is - if it'll be part of a core deployment, then plan to include right now16:34
*** zehicle has quit IRC16:34
palendae^ I like that plan16:34
odyssey4meif it's independant and optional, then perhaps plan for a separate repo16:34
evrardjpI'll publish a PoC code, and we'll adapt according to16:34
*** zehicle has joined #openstack-meeting-416:34
palendaeAt the moment, OSAD is very much a highly coupled system16:34
odyssey4meeg: there is a rally role in the wings - that should be planned to be seperate16:35
*** zehicle has quit IRC16:35
*** zehicle has joined #openstack-meeting-416:35
*** singlethink has joined #openstack-meeting-416:35
cloudnullevrardjp:  theres no real plan for splitting anything up at this point. and if you have work inflight to add into the main repo I'd keep that going on that. if we get this spec in and we feel its best to create a new repo we'll have to bring it up to the ML , meeting , the maintinaer, etc. . . to do all the work.16:35
*** zehicle has quit IRC16:35
odyssey4me+116:35
*** zehicle has joined #openstack-meeting-416:36
*** zehicle has quit IRC16:36
evrardjpagree, it just needs to be clear for all the possible contributors, and set a date of the possible move, that was my point16:36
cloudnullthe process will be fully transparent. so while I want this to make the project better, like odyssey4me said, its going to take work and planning.16:36
*** zehicle has joined #openstack-meeting-416:36
evrardjpok16:37
odyssey4meyeah, the the moves will take place over an entire cycle - not all in one day16:37
*** zehicle has quit IRC16:37
*** zehicle has joined #openstack-meeting-416:37
odyssey4mewe have to look after our downstream consumers, some of which (like evrardjp) are largely following on a per commit basis16:37
*** zehicle has quit IRC16:38
cloudnull++16:38
*** zehicle has joined #openstack-meeting-416:38
cloudnullmoving on16:38
cloudnull#topic Mitaka Summit Discussion Agenda (input required)16:38
*** openstack changes topic to "Mitaka Summit Discussion Agenda (input required) (Meeting topic: OpenStack Ansible Meeting)"16:38
cloudnull#link https://etherpad.openstack.org/p/openstack-ansible-mitaka-summit16:38
*** zehicle has quit IRC16:38
*** zehicle has joined #openstack-meeting-416:39
cloudnullwe need people to think about and contribute to our efforts at the summit .16:39
*** zehicle has quit IRC16:39
*** zehicle has joined #openstack-meeting-416:39
cloudnullideally id like to see what type of rooms we'll need @ tokyo so i can make the request to ttx sooner than later.16:39
*** zehicle has quit IRC16:40
evrardjpI'll be there16:40
cloudnullsweet!16:40
odyssey4meawesome evrardjp :)16:40
*** zehicle has joined #openstack-meeting-416:40
cloudnullfirst rounds on me :)16:40
evrardjpI have a question about that I'll keep for open topics16:40
*** zehicle has quit IRC16:40
odyssey4mepersonally I think it'd be great to have a fishbowl discussion early on to hash out ideas and thoughts16:41
*** zehicle has joined #openstack-meeting-416:41
cloudnull++ i like the fish bowls16:41
odyssey4methen have a contributors meetup on fri to take the ideas and plot out a roadmap16:41
*** zehicle has quit IRC16:41
cloudnullhowever space is a bit limited in tokyo so access will be limited .16:41
odyssey4methat way we can seperate the critical thought from the creative thought16:41
cloudnulland other projects, like nova, will have more presedence if push comes to shove16:42
*** zehicle has joined #openstack-meeting-416:42
*** zehicle has quit IRC16:42
cloudnullworkrooms should be more available16:42
cloudnulland for sure we'll regester a contributors meetup on friday16:42
odyssey4mealternatively, perhaps we could arrange a fish bowl type session on fri morning, then do a meetup in the afternoon for the rest?16:42
*** zehicle has joined #openstack-meeting-416:42
cloudnullthatll work16:43
*** zehicle has quit IRC16:43
evrardjpIsn't something already planned for Tue?16:43
*** zehicle has joined #openstack-meeting-416:43
odyssey4methat will be nice because it'll give us all a chance to attend presentations and be free to attend other design discussions16:43
*** zehicle has quit IRC16:43
*** zehicle has joined #openstack-meeting-416:44
*** zehicle has quit IRC16:44
cloudnullindeed.16:44
*** zehicle has joined #openstack-meeting-416:44
cloudnulli think , as a deployment project its key for us to participate in the design sessions for other porjects.16:45
*** zehicle has quit IRC16:45
evrardjp+116:45
evrardjpwe need to know what's going on at all times16:45
*** zehicle has joined #openstack-meeting-416:45
cloudnulltheir changes effect us and with our "from source" nature we're able to consume these changes sooner.16:45
*** yamahata has quit IRC16:45
*** zehicle has quit IRC16:46
cloudnullevrardjp:  +116:46
*** zehicle has joined #openstack-meeting-416:46
evrardjpthe important is to let us have the room to understand the changes applied16:46
evrardjpI'm not sure if it's correct english16:46
*** zehicle has quit IRC16:46
evrardjpanyway16:46
evrardjpwe agree16:46
cloudnull:)16:47
odyssey4me:)16:47
evrardjpdecision?16:47
*** zehicle has joined #openstack-meeting-416:47
*** zehicle has quit IRC16:47
evrardjpTue fishball session and small meeting friday?16:47
*** zehicle has joined #openstack-meeting-416:48
*** Sam-I-Am has left #openstack-meeting-416:48
odyssey4meI'm preferring a room all day fri, if we can get it.16:48
*** zehicle has quit IRC16:48
odyssey4meotherwise a fall back to what evrardjp  said16:48
*** zehicle has joined #openstack-meeting-416:48
cloudnull* tuesday 1 fishbowl would be great. wensday 1 workgroup to talk about inflight items and issues that have result ed in bad life choices. friday 1 meetup lasting a couple of hours if possible.16:49
*** KunalGandhi has joined #openstack-meeting-416:50
*** KunalGandhi has quit IRC16:50
odyssey4mesounds good to me16:50
cloudnullidk if people will be available monday but we might be able to team up with some of the guys @ ansible to have a community day again16:50
cloudnulland if so maybe we cut out wed ?16:50
*** KunalGandhi has joined #openstack-meeting-416:50
cloudnullthe community day at vancouver seemed to work out nicely .16:51
odyssey4meI like the idea of having that on the Mon so we don't miss out on so much of the summit16:51
odyssey4meI barely managed to attend anything last summit\16:51
cloudnullyea +116:51
cloudnullok lets get some of this in the etherpad16:52
cloudnulland well make the decision EOD on Friday/Saturday.16:52
*** cloudtrainme has quit IRC16:52
cloudnullbased on general majority from what folks put down there.16:52
*** zehicle has quit IRC16:52
*** krtaylor has joined #openstack-meeting-416:53
odyssey4mecool - will add bits after the meeting16:53
cloudnullk16:53
cloudnull#topic Open discussion16:53
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:53
cloudnullevrardjp:  you had something you wanted to bring up ?16:53
evrardjpyeah, and it's linked to previous discussion16:54
evrardjpI've seen there was 3 ansible meetings here16:54
evrardjphttps://libertydesignsummit.sched.org/16:54
evrardjpam I on the good page?16:54
evrardjpdamn16:54
evrardjpI just realized I'm not on the right one16:54
odyssey4mehaha, that's the last summit16:54
evrardjpI was thinking about lobying16:55
odyssey4mehttps://mitakadesignsummit.sched.org/16:55
evrardjpto gather the community16:55
evrardjpit's not relevant anymore, sorry.16:55
evrardjpNext?16:55
lbragstadif something is put together with the ansible folks for monday, will that be a word of mouth thing?16:56
lbragstadsince nothing officially starts on monday?16:56
cloudnulllast time they added it in shed late16:56
cloudnullim not sure what theyll do, if anything, this go around .16:57
lbragstadok16:57
*** harshs has joined #openstack-meeting-416:57
cloudnullok well then if theres nothing else i think we're done here.16:58
*** sdake_ has joined #openstack-meeting-416:59
*** singleth_ has joined #openstack-meeting-416:59
evrardjpOk thanks for the meeting16:59
*** evrardjp has left #openstack-meeting-416:59
cloudnullthanks everyone17:00
cloudnull:)17:00
cloudnullhave a good one17:00
cloudnull#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Aug 27 17:00:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-27-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-27-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-27-16.01.log.html17:00
*** stevelle has left #openstack-meeting-417:00
*** odyssey4me has left #openstack-meeting-417:01
*** ajmiller has quit IRC17:01
*** afv__ has joined #openstack-meeting-417:01
*** ajmiller has joined #openstack-meeting-417:02
*** singlethink has quit IRC17:02
*** sdake has quit IRC17:02
*** jckasper has quit IRC17:02
*** lazy_prince has quit IRC17:03
*** jpeeler has joined #openstack-meeting-417:03
*** jpeeler has quit IRC17:03
*** jpeeler has joined #openstack-meeting-417:03
*** qwebirc83537 has joined #openstack-meeting-417:04
*** georgewang has joined #openstack-meeting-417:04
georgewang#email17:05
qwebirc83537Hi, in a past reference I see a gotomeeting link. Do we still use it for presentation?17:05
georgewanghelp17:05
*** afv__ has quit IRC17:06
*** KLevenstein has left #openstack-meeting-417:06
*** afv__ has joined #openstack-meeting-417:06
*** nhairston has joined #openstack-meeting-417:07
*** jerryz has joined #openstack-meeting-417:07
*** s3wong has quit IRC17:09
*** nhairston has quit IRC17:13
*** nhairston has joined #openstack-meeting-417:13
*** sdake_ is now known as sdake17:14
*** cloudtrainme has joined #openstack-meeting-417:15
*** afv__ has quit IRC17:15
*** yamahata has joined #openstack-meeting-417:16
georgewangjoin17:17
*** yamamoto has joined #openstack-meeting-417:20
*** bnemec has quit IRC17:21
*** qwebirc83537 has quit IRC17:22
*** irenab has quit IRC17:25
*** sdake_ has joined #openstack-meeting-417:26
*** sdake has quit IRC17:29
*** nhairston has quit IRC17:29
*** evgenyf has joined #openstack-meeting-417:33
*** xingchao has joined #openstack-meeting-417:34
*** jckasper has joined #openstack-meeting-417:34
*** singleth_ has quit IRC17:35
*** vivek-ebay has joined #openstack-meeting-417:35
*** FallenPegasus has joined #openstack-meeting-417:36
*** xingchao has quit IRC17:38
*** SimonChung1 has joined #openstack-meeting-417:41
*** SimonChung has quit IRC17:41
*** s3wong has joined #openstack-meeting-417:45
*** VW_ has quit IRC17:45
*** VW_ has joined #openstack-meeting-417:46
*** dwalleck has joined #openstack-meeting-417:46
*** cloudtrainme has quit IRC17:50
*** jwagner is now known as jwagner_away17:50
*** VW_ has quit IRC17:50
*** vivek-ebay has quit IRC17:51
*** cloudtrainme has joined #openstack-meeting-417:51
*** ftcpops has left #openstack-meeting-417:55
*** dwalleck has quit IRC18:01
*** dwalleck has joined #openstack-meeting-418:01
*** padkrish has joined #openstack-meeting-418:10
*** rfolco has quit IRC18:11
*** singlethink has joined #openstack-meeting-418:15
*** bgmccollum has left #openstack-meeting-418:16
*** scotticus has left #openstack-meeting-418:20
*** GB21 has quit IRC18:30
*** GB21 has joined #openstack-meeting-418:33
*** jwagner_away is now known as jwagner18:33
*** GB21 has quit IRC18:33
*** cpallares has quit IRC18:40
*** cpallares has joined #openstack-meeting-418:46
*** dwalleck has quit IRC18:52
*** xingchao has joined #openstack-meeting-418:55
*** xingchao has quit IRC19:04
*** puranamr has quit IRC19:12
*** puranamr has joined #openstack-meeting-419:13
*** puranamr has quit IRC19:16
*** puranamr has joined #openstack-meeting-419:17
*** puranamr has quit IRC19:17
*** puranamr has joined #openstack-meeting-419:17
*** evgenyf has quit IRC19:21
*** ajmiller_ has joined #openstack-meeting-419:26
*** fitoduarte has joined #openstack-meeting-419:29
*** ajmiller has quit IRC19:30
*** fawadkhaliq has quit IRC19:35
*** ajmiller_ is now known as ajmiller19:42
*** puranamr has quit IRC19:44
*** puranamr has joined #openstack-meeting-419:45
*** matrohon has joined #openstack-meeting-419:45
*** puranamr has quit IRC19:48
*** dwalleck has joined #openstack-meeting-419:57
*** singleth_ has joined #openstack-meeting-419:58
*** singlethink has quit IRC20:01
*** Shamail has joined #openstack-meeting-420:01
*** fawadkhaliq has joined #openstack-meeting-420:06
*** puranamr has joined #openstack-meeting-420:08
*** matrohon has quit IRC20:09
*** FallenPegasus has quit IRC20:10
*** puranamr has quit IRC20:14
*** baoli has quit IRC20:14
*** sarob has quit IRC20:14
*** akwasnie has joined #openstack-meeting-420:15
*** matrohon has joined #openstack-meeting-420:16
*** yamahata has quit IRC20:16
*** padkrish has quit IRC20:20
*** nhairston has joined #openstack-meeting-420:21
*** padkrish has joined #openstack-meeting-420:21
*** FallenPegasus has joined #openstack-meeting-420:22
*** matrohon has quit IRC20:23
*** matrohon has joined #openstack-meeting-420:25
*** sarob has joined #openstack-meeting-420:28
*** Shamail has quit IRC20:29
*** julim has joined #openstack-meeting-420:32
*** nhairston has quit IRC20:32
*** markvoelker has quit IRC20:33
*** IlyaG has joined #openstack-meeting-420:41
*** nhairston has joined #openstack-meeting-420:44
*** dwalleck has quit IRC20:46
*** krtaylor has quit IRC20:46
*** dwalleck has joined #openstack-meeting-420:48
*** cloudtrainme has quit IRC20:49
*** julim has quit IRC20:50
*** julim has joined #openstack-meeting-420:54
*** cloudtrainme has joined #openstack-meeting-420:55
*** fitoduarte has quit IRC20:56
*** yamamoto has quit IRC21:00
*** fawadkhaliq has quit IRC21:00
*** xingchao has joined #openstack-meeting-421:02
*** nhairston has quit IRC21:02
*** xingchao has quit IRC21:06
*** julim has quit IRC21:07
*** IlyaG has quit IRC21:11
*** IlyaG_ has joined #openstack-meeting-421:14
*** dwalleck has quit IRC21:16
*** sdake has joined #openstack-meeting-421:23
*** SimonChung1 has quit IRC21:24
*** SimonChung has joined #openstack-meeting-421:24
*** dwalleck has joined #openstack-meeting-421:25
*** sdake_ has quit IRC21:25
*** akwasnie has quit IRC21:26
*** sdake_ has joined #openstack-meeting-421:26
*** SimonChung has quit IRC21:29
*** SimonChung1 has joined #openstack-meeting-421:29
*** sdake has quit IRC21:30
*** padkrish has quit IRC21:35
*** padkrish has joined #openstack-meeting-421:35
*** padkrish has quit IRC21:40
*** prometheanfire has left #openstack-meeting-421:42
*** krtaylor has joined #openstack-meeting-421:45
*** dwalleck has quit IRC21:45
*** padkrish has joined #openstack-meeting-421:48
*** dwalleck has joined #openstack-meeting-421:48
*** padkrish has quit IRC21:48
*** padkrish has joined #openstack-meeting-421:49
*** jwagner is now known as jwagner_away21:52
*** bharathm has quit IRC21:53
*** bharathm has joined #openstack-meeting-421:53
*** dwalleck has quit IRC21:53
*** dwalleck has joined #openstack-meeting-421:54
*** bharathm has quit IRC21:56
*** bharathm has joined #openstack-meeting-421:56
*** dwalleck has quit IRC21:58
*** yamamoto has joined #openstack-meeting-422:00
*** IlyaG_ has quit IRC22:04
*** yamamoto has quit IRC22:05
*** klamath has quit IRC22:06
*** IlyaG_ has joined #openstack-meeting-422:08
*** IlyaG__ has joined #openstack-meeting-422:09
*** IlyaG_ has quit IRC22:12
*** jckasper has quit IRC22:14
*** padkrish has quit IRC22:15
*** padkrish has joined #openstack-meeting-422:16
*** padkrish has quit IRC22:16
*** padkrish has joined #openstack-meeting-422:17
*** matrohon has quit IRC22:22
*** SimonChung1 has quit IRC22:22
*** SimonChung has joined #openstack-meeting-422:22
*** SimonChung has quit IRC22:23
*** SimonChung1 has joined #openstack-meeting-422:23
*** jwagner_away is now known as jwagner22:24
*** dwalleck has joined #openstack-meeting-422:25
*** bknudson has quit IRC22:26
*** dwalleck has quit IRC22:26
*** IlyaG__ has quit IRC22:27
*** akwasnie has joined #openstack-meeting-422:43
*** yamahata has joined #openstack-meeting-422:47
*** cloudtrainme has quit IRC22:58
*** cloudtrainme has joined #openstack-meeting-422:58
*** singlethink has joined #openstack-meeting-422:59
*** rbak has quit IRC23:02
*** sigmavirus24 is now known as sigmavirus24_awa23:02
*** singleth_ has quit IRC23:03
*** cloudtrainme has quit IRC23:04
*** ajmiller has quit IRC23:04
*** ajmiller has joined #openstack-meeting-423:04
*** SimonChung has joined #openstack-meeting-423:05
*** SimonChung1 has quit IRC23:05
*** SimonChung1 has joined #openstack-meeting-423:06
*** SimonChung has quit IRC23:06
*** xingchao has joined #openstack-meeting-423:06
*** SimonChung has joined #openstack-meeting-423:06
*** SimonChung1 has quit IRC23:06
*** singlethink has quit IRC23:12
*** xingchao has quit IRC23:13
*** VW_ has joined #openstack-meeting-423:16
*** VW_ has quit IRC23:18
*** dims_ has joined #openstack-meeting-423:18
*** akwasnie has quit IRC23:20
*** aventerav has quit IRC23:20
*** dims has quit IRC23:22
*** jwagner is now known as jwagner_away23:25
*** KunalGandhi has quit IRC23:31
*** SimonChung1 has joined #openstack-meeting-423:34
*** SimonChung has quit IRC23:34
*** bnemec has joined #openstack-meeting-423:35
*** KunalGandhi has joined #openstack-meeting-423:36
*** jpekkari has joined #openstack-meeting-423:38
*** dims_ has quit IRC23:38
*** Swami has quit IRC23:45

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