Wednesday, 2015-12-16

*** ALUVial has quit IRC00:00
*** Swami__ has quit IRC00:02
*** Swami_ has joined #openstack-meeting-400:03
*** Jeffrey4l has joined #openstack-meeting-400:13
*** xingchao has joined #openstack-meeting-400:25
*** Swami__ has joined #openstack-meeting-400:25
*** Swami_ has quit IRC00:27
*** sridhar_ram1 has joined #openstack-meeting-400:28
*** sridhar_ram has quit IRC00:31
*** david-lyle has joined #openstack-meeting-400:36
*** david-lyle_ has quit IRC00:36
*** banix has joined #openstack-meeting-400:48
*** Jeffrey4l has quit IRC00:51
*** xingchao has quit IRC00:55
*** sripriya has joined #openstack-meeting-400:57
*** salv-orlando has joined #openstack-meeting-401:00
*** sridhar_ram1 is now known as sridhar_ram01:01
sridhar_ram#startmeeting tacker01:01
openstackMeeting started Wed Dec 16 01:01:27 2015 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.01:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:01
*** openstack changes topic to " (Meeting topic: tacker)"01:01
openstackThe meeting name has been set to 'tacker'01:01
sridhar_ram#topic Roll Call01:01
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"01:01
vishwanathjo/01:01
sripriyao/01:01
sridhar_ramwho is here for tacker mtg ?01:01
sridhar_ramvishwanathj: sripriya: hi there!01:01
*** natarajk has joined #openstack-meeting-401:02
prashantD_hi01:02
*** piet has quit IRC01:02
sridhar_ramprashantD_: howdy01:02
sridhar_ramlets give few mins, before we start.01:03
*** u_kozat has quit IRC01:03
*** piet has joined #openstack-meeting-401:04
sridhar_ram#topic Agenda01:05
*** openstack changes topic to "Agenda (Meeting topic: tacker)"01:05
sridhar_ram#link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_16.2C_2015_-_APAC_Timezone01:05
sridhar_ram#topic Annoucements01:05
*** openstack changes topic to "Annoucements (Meeting topic: tacker)"01:05
sridhar_ramTacker Midcycle meetup is planned for end of Jan 201601:05
sridhar_ramthis is a F2F meeting to be held in San Jose, CA01:06
sridhar_ramHere is the poll for possible dates - #link http://goo.gl/forms/8hVPXcmoqz01:06
sridhar_ramPlease provide your inputs!01:07
s3wonghello01:07
sridhar_ramnext.. we are heading towards Holiday season in US01:07
*** ksantoshk has joined #openstack-meeting-401:08
sridhar_rams3wong: hi, we just getting started...01:08
s3wongsridhar_ram: yes01:08
sridhar_ramI won't be available for next two weeks...01:08
sridhar_ram.. any volunteers to run the mtg ?01:08
sridhar_ramor do think we shd skip next two weekly meeting ?01:09
vishwanathji vote for skipping01:09
sripriya+101:09
ksantoshk+101:09
vishwanathjfor some of us we can use the time to do some review01:09
vishwanathjreview -> reviews01:09
natarajk+101:09
sridhar_ramvishwanathj: true, our review queue is quite deep01:09
sripriyayup, and also implementing the bluprints itself01:10
vishwanathj+101:10
sridhar_ramalright.. lets skip. we will reconvene at our usual time on Jan 5th01:11
sridhar_ramanything else to announce / heads up ?01:11
sridhar_ramlets move on...01:11
sridhar_ram#topic Mitaka blueprint updates01:12
*** openstack changes topic to "Mitaka blueprint updates (Meeting topic: tacker)"01:12
*** Swami__ has quit IRC01:12
sripriyasridhar_ram: python jobs are enabled for python-tackerclient01:12
*** mbound_ has quit IRC01:12
*** banix has quit IRC01:12
sridhar_ramsripriya: oh, yeah.. thanks for pointing out and thanks to Yong Sheng from 99cloud01:12
sridhar_ramgongysh: are you here ?01:13
sripriyasridhar_ram: so any new python-tackerclient changes will need to include unit tests coverage01:13
sridhar_ramsripriya: true...01:14
*** armax has quit IRC01:14
sripriyaand also the original device unit test cases will be removed eventually which is currently enabled01:14
sridhar_ramsripriya: I hope we can convert these to "vnf" client test cases01:15
sripriyasridhar_ram: yes, it is actually a "conversion" there should be no other major impacts as it is based on devices01:16
*** xingchao has joined #openstack-meeting-401:16
sridhar_ramlets see if yong sheng joins to take up Efficient VNF placement topic01:16
sridhar_ramsripriya: okay..01:17
*** salv-orlando has quit IRC01:17
sridhar_ramsripriya: do you want to give a quick update on Multi-VIM ?01:18
sridhar_ramsripriya: .. or shd I say multi-site ? ;-)01:18
sripriyasridhar_ram: sure, there have been some great inputs/comments on the spec. I need to upload a new version of spec incorporating these inputs01:19
sripriyasridhar_ram: :-) yes we have transitioned to "multi-site VIM"01:19
sridhar_ramsripriya: I like it :)01:19
natarajkNice01:20
sridhar_ramsripriya: I'm happy to see all those nice discussions..01:20
sripriyasridhar_ram: i understand there were concerns on the term. itself regarding multisite/multiregions/VIMs which we have discussed on the spec,01:20
sripriyasridhar_ram: also we have moved on from VIM O to NFV O as the end goals of this new component is resource management across VIMs as per ETSI doc01:21
*** xingchao has quit IRC01:21
sridhar_ramsripriya: we need to strike a balance between MANO taxonomy and the actual openstack multisite deployments methods01:21
*** zeih has joined #openstack-meeting-401:21
sridhar_ramsripriya: yes, multi-vim is *one* of the building blocks on NFVO01:21
sridhar_ramsripriya: while we are not taking up Resource reservation / allocation .. this feature shd evolve into that in the future01:22
sridhar_ramoverall quite pleased...01:22
sripriyasridhar_ram: the workflow will be pretty much NFVO->VIM->Regions->Availability_Zones->Cells that will constitute as vim selection for VNF placement01:22
sripriyasridhar_ram: agree01:23
sridhar_ramsripriya: wow.. that's quite a level of granular placement control..01:23
sripriyasridhar_ram: :) or it can be just NFVO->VIM (With defaults)01:24
*** afveitch has joined #openstack-meeting-401:24
sridhar_ramsripriya: okay.. keep in mind, there is also automated test complexity and horizon work01:25
sridhar_ramsripriya: .. so we need to keep the scope not run away too much..01:25
sripriyasridhar_ram: yes, with these inputs coming in, i observe there will be lot more work on horizon side as much as the server side01:26
*** zeih has quit IRC01:26
*** tfukushima has joined #openstack-meeting-401:26
sridhar_ramafveitch: hi, we are discussing multi-vim / multi-site..01:26
afveitchok01:27
*** tbh has joined #openstack-meeting-401:27
afveitchsridhar_ram: I am still thinking about the best way to address the things you wrote in your response01:27
sripriyasridhar_ram: i have not through much on the automated test complexity , but if we are doing this with multiple devstack installs, it will be good to understand if this is feasible in openstack jenkins01:28
sripriyathought*01:28
sridhar_ramafveitch: there is also some nomenclature / terminology that's cluttering us a bit..01:28
sridhar_ramsripriya: true, it will be good to check w/ infra team apriori01:28
*** bobh has joined #openstack-meeting-401:28
*** markvoelker has quit IRC01:29
afveitchsridhar_ram: Yes, agreed.  I think if we can align the mapping of the Heat multi region with the MANO docs, it would be good01:29
afveitchsridhar_ram: That is part of what I am working to put into my follow up to comments - then send for general review.01:30
sridhar_ramafveitch: ... bottomline if Tacker support VIM endpoints with multiple Regions along with support for AZ we would've implicitly covered OpenStack multi-site deployments using Regions01:30
sridhar_ramafveitch: .. sure, lets continue the discussion in the gerrit, so that it gets captured in place...01:31
afveitchsridhar_ram: Yes, I think you are correct.  Frankly, I am working to get more familiar with the multi region to be confident in myself in responding01:31
afveitchsridhar_ram: agree with that plan01:31
sridhar_ramafveitch: no worries. You point on "multi-site" is interesting .. in fact, as mentioned in the comment, it will be nice to group all VIMs in a specific "site" .. perhaps even plot them in a google maps enabled dashboard :)01:32
sridhar_ramhope I'm not fantasizing too much :)01:32
afveitchsridhar_ram: a man's reach should exceed his grasp :-)01:33
*** angdraug has quit IRC01:33
sridhar_ramafveitch: perfect! like it01:33
sridhar_ramanything else - major - on multi-site vim ?01:33
afveitchsridhar_ram: not for me, I joined late and will review the log.01:34
sridhar_ramafveitch: sure...01:34
sripriyasridhar_ram: nothing from my end, i will upload a new spec for further discussions01:34
sridhar_ramsripriya: sounds good...01:34
*** Prithiv has quit IRC01:34
sridhar_ramlets move on..01:35
sridhar_ramtbh: do you want to give a quick update on auto-resource creation ?01:35
tbhsridhar_ram, Hi, I want to readdress the comments mentioned in bp01:36
sridhar_ramtbh: which specific one ?01:36
tbhbut sridhar_ram I want to know about what do you mean by template parametrization01:36
*** bobh has quit IRC01:37
sridhar_ramtbh: remember we discussed (perhaps even decided) to create flavors during VNFD creation...01:37
tbhsridhar_ram, yes01:37
sridhar_ramtbh: ... that may not work if some of the properties like num_cpu is parameterized..01:37
sridhar_ramtbh: .. you can create flavors only at vnf-creation time01:38
tbhsridhar_ram, yes, but we thought later of sending those details to heat with out tacker creating it01:38
tbhsridhar_ram, so that will come under vnf creation time, right? but I haven't updated in specs yet01:39
sridhar_ramtbh: ah, yes... do you use heat to create flavor on the fly during vnf instantiation time  ?01:39
tbhsridhar_ram, yes01:40
tbhsridhar_ram, and the scope of flavor is same as vnf01:40
*** gongysh has joined #openstack-meeting-401:40
gongyshhi01:40
sridhar_ramgongysh: hi there, we are discussion auto-resource creation spec from tbh01:41
gongyshcool01:41
sridhar_ramtbh: yeah, that shd work..01:41
sripriyasridhar_ram: tbh: essentially glance image upload is the only case that happpens during vnfd-create operation?01:41
tbhsridhar_ram, sripriya yes01:41
tbhsripriya,  you asked about if about flavor duplicity01:42
gongyshtbh,  how about flavor creation?01:42
tbhsripriya, sridhar_ram  we can have duplicate flavors01:42
tbhgongysh, as sridhar_ram said if the template is parametrized we cannot create flavors at vnfd creation time01:43
sripriyaisnt that redundant for the user, as an operator i dont want to create duplicate flavors for each vnf requests01:43
sripriyatbh: ^01:43
tbhsripriya,  but as we decided earlier flavors are cheap01:44
tbhsridhar_ram,  but template parametrization case will apply for image creation also?01:44
sridhar_ramtbh: agree it was cheap when it was associated with VNFD...01:44
sridhar_ramtbh: no, we shdn't allow that IMO01:44
tbhsridhar_ram, because images are of large sizes01:45
sridhar_ramtbh: .. back to flavors we are now taking about number of flavors -at worst case == number of VDUs in the controller..01:45
sridhar_ramtbh: .. that doesn't look good01:46
sripriyatbh: then i will end up having a huge list of flavors in my deployment which is not preferred (and is ugly) even though the operation is inexpensive01:46
tbhsridhar_ram,  sripriya but we have a solution that we have implemented for this01:46
tbhsripriya,  sridhar_ram  https://review.openstack.org/#/c/252834/01:47
sridhar_ramfolks - lets wrap this discussion and continue in gerrit.. I'd like to discussion Efficient VNF placement01:47
sridhar_ram*discuss01:47
tbhsripriya,  sridhar_ram  heat translator can return the best match for the flavor01:47
tbhsridhar_ram, okay01:47
sripriyatbh: will take a look, thanks01:47
sridhar_ramtbh: that look promising!01:47
sridhar_ram#topic Efficient VNF Placement01:48
*** openstack changes topic to "Efficient VNF Placement (Meeting topic: tacker)"01:48
sridhar_ramgongysh: vishwanathj: hi folks.. can you give a quick update on the scope & where you are ?01:48
*** zeih has joined #openstack-meeting-401:48
*** leecalcote has quit IRC01:48
gongyshsridhar_ram, I have uploaded a spec for it01:48
vishwanathjthanks to gongysh for starting the patchset....01:49
*** piet has quit IRC01:49
sridhar_ramgongysh: link ?01:49
gongyshsridhar_ram,  https://review.openstack.org/#/c/257847/01:49
vishwanathjI plan to add to it and collaborate alongside gongysh01:49
sridhar_ramgongysh: awesome... that's a good kick start.. !01:49
gongyshIt will depend on tbh's resource creation BP01:49
sridhar_ramgongysh: true, and tbh's BP depends on bobh's tosca work.. and that worries me :(01:50
gongyshbut, since we can create flavor already,  just as tbh said, we can begin the coding for flavor creation.01:50
sridhar_ramgongysh: cool..01:51
sridhar_ramgongysh: please work with vishwanathj to split some areas for faster progress...01:51
gongyshwe need testing much. since the openstack CI dose not provide numa and sriov testing host.01:52
sridhar_ramI remember Cisco contributed some CI for sr-iov.. but agree that will be challenging01:52
gongyshvishwanathj,  you can update the https://review.openstack.org/#/c/252834/ to include what tasks you will do.01:52
*** zeih has quit IRC01:53
vishwanathjgongysh, I have some ideas with regards to make the VNFD content for NUMA, CPU Pin, Huge Pages and vCPU topology more generic...shall discuss with you01:53
gongyshvishwanathj, sure01:53
sridhar_rambtw, what are the must-have features ?01:54
vishwanathjgongysh, thanks01:54
sridhar_ramare we shooting to include pci-passthru and sr-iov in this scope01:54
vishwanathjI see it as being called out as stretch for mitaka in the spec01:54
gongyshsridhar_ram,  sriov should be the first thing.01:54
sridhar_ramgongysh: okay.. it will be great to bring it in..01:55
*** bpokorny_ has joined #openstack-meeting-401:55
sridhar_ramgongysh: .. I was not sure about the effort involved01:55
*** tfukushima has quit IRC01:56
* sridhar_ram I hope we can extend this mtg few mins beyond the top of the hour...01:56
* sridhar_ram .. if needed01:56
*** tfukushima has joined #openstack-meeting-401:56
*** bobh has joined #openstack-meeting-401:56
sridhar_ramalright.. that's cool.. I'll let you and vishwanathj march on..01:56
sridhar_ramthis is a crucial feature for Tacker.. ! good luck  :)01:57
*** piet has joined #openstack-meeting-401:57
vishwanathjgongysh, looking forward to collobarating with you and learning from your experience01:57
sridhar_ramanything else on EPA / EVP topic ?01:58
gongyshvishwanathj,  haha, do it together, and make it happen.01:58
vishwanathjmost definitely01:58
*** baohua has joined #openstack-meeting-401:58
gongyshsridhar_ram,  shall we begin coding before spec is merged?01:58
*** ksantoshk has quit IRC01:58
sridhar_ramgongysh: well.. you need some amount of coding to write good blueprints :) .. yes, as long as you are ready to alter as we go!01:59
*** bpokorny has quit IRC01:59
*** dims has quit IRC01:59
sridhar_ramgood to see the blueprint start.. lets continue the discussion in gerrit..01:59
gongyshok02:00
*** bpokorny_ has quit IRC02:00
sridhar_ram#topic Open Discussion02:00
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"02:00
*** salv-orlando has joined #openstack-meeting-402:00
sridhar_ramas discussed earlier.. there is no IRC meeting for next two weeks02:00
sridhar_ramwe will reconvene Jan 5th..02:00
sridhar_ramtacker core will be around to merge patchsets .. so keep the work going!02:00
* sridhar_ram taking two weeks off02:00
sripriyasridhar_ram: are there any priority patchsets that needs to be closed within this week before holidays?02:00
*** tfukushima has quit IRC02:01
sridhar_ramsripriya: nothing pops at this time.. but noticed the queue is deep and we need to keep clearing them ..02:01
sripriyasridhar_ram: ok02:02
sridhar_ramsripriya: .. to keep things manageable02:02
*** leecalcote has joined #openstack-meeting-402:02
s3wongI will be around :-)02:02
sridhar_ramone heads up / request for help - please flag patchsets that need to go to stable/liberty..02:02
sripriyagongysh: any update on the nova patchset if it will merged soon?02:02
sridhar_rams3wong: thanks!02:02
sridhar_ramwill plan to release pypi pkgs for liberty / 0.2.0 in first week of Jan02:03
gongyshsripriya, no luck. network related patch is always slow in nova.02:03
gongyshno network guys in nova cores.02:03
sridhar_ramgongysh: that's bad.. no wonder nova-network --> neutron is in bad state02:03
*** bobh has quit IRC02:04
sripriyagongysh: thanks for update02:04
gongyshsridhar_ram,  it is true.02:04
sridhar_ramgongysh: in fact I want this nova fix in stable/liberty ...02:04
sripriya+102:04
sridhar_ramgongysh: .. is that possible ?02:04
gongyshyes, definitely02:04
gongyshI will push it.02:04
sridhar_ramgongysh: thanks!02:05
*** salv-orlando has quit IRC02:05
sripriyacool!02:05
sridhar_ramgongysh: I'm glad you joined Tacker team!02:05
sridhar_ramanything else team ?02:05
* sridhar_ram we are 5mins overtime02:05
sripriyathats it from me02:05
gongyshsridhar_ram, my pleasure02:05
sridhar_ramalright.. if you taking a break / vacation.. have a nice time and a safe holiday season..02:06
sridhar_ramif you going to work.. happy coding!02:06
sridhar_ramsee you all next year!02:06
afveitchsame to you, bye02:06
sripriyabye! happy holidays!02:06
s3wongbye02:06
vishwanathjHappy holidays everyone, bye02:06
natarajkHappy Holidays, Bye02:07
sridhar_rambye team! lets rock on in 201602:07
gongyshhappy holidays. bye02:07
sridhar_ram#endmeeting02:07
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"02:07
openstackMeeting ended Wed Dec 16 02:07:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-16-01.01.html02:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-16-01.01.txt02:07
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2015/tacker.2015-12-16-01.01.log.html02:07
gongyshsridhar_ram, the meeting time is fixed?02:07
sridhar_ramlets take it up in #tacker channel02:08
*** woodard_ has joined #openstack-meeting-402:08
*** woodard has quit IRC02:08
*** natarajk has left #openstack-meeting-402:10
*** mbound_ has joined #openstack-meeting-402:12
*** sripriya has quit IRC02:15
*** vishwanathj has quit IRC02:15
*** bobh has joined #openstack-meeting-402:16
*** zz_ja has joined #openstack-meeting-402:17
*** xingchao has joined #openstack-meeting-402:17
*** piet has quit IRC02:17
*** mbound_ has quit IRC02:18
*** zz_zz_ja has quit IRC02:18
*** bharathm has quit IRC02:19
*** tfukushima has joined #openstack-meeting-402:21
*** bobh has quit IRC02:22
*** yamamoto has joined #openstack-meeting-402:22
*** yamamoto has quit IRC02:25
*** markvoelker has joined #openstack-meeting-402:29
*** prashantD_ has quit IRC02:33
*** markvoelker has quit IRC02:34
*** yamahata has quit IRC02:36
*** Jeffrey4l has joined #openstack-meeting-402:37
*** sridhar_ram has quit IRC02:37
*** s3wong has quit IRC02:50
*** sdake has joined #openstack-meeting-402:53
*** tbh has quit IRC02:59
*** jab has joined #openstack-meeting-402:59
*** zz_ja has quit IRC03:01
*** bobh has joined #openstack-meeting-403:02
*** leecalcote has quit IRC03:12
*** yamamoto has joined #openstack-meeting-403:12
*** haleyb has joined #openstack-meeting-403:25
*** bobh has quit IRC03:25
*** dims has joined #openstack-meeting-403:45
*** markvoelker has joined #openstack-meeting-403:46
*** neelashah has joined #openstack-meeting-403:47
*** markvoelker has quit IRC03:50
*** bobh has joined #openstack-meeting-403:50
*** leecalcote has joined #openstack-meeting-403:57
*** leecalcote has quit IRC03:59
*** leecalcote has joined #openstack-meeting-404:00
*** armax has joined #openstack-meeting-404:00
*** armax has quit IRC04:07
*** leecalcote has quit IRC04:09
*** amotoki has joined #openstack-meeting-404:16
*** neelashah has quit IRC04:19
*** armax has joined #openstack-meeting-404:20
*** dims has quit IRC04:20
*** tfukushima has quit IRC04:37
*** sdake has quit IRC04:40
*** sdake has joined #openstack-meeting-404:41
*** bobh has quit IRC04:41
*** rbak has quit IRC04:51
*** bharathm has joined #openstack-meeting-405:00
*** eglute_s is now known as eglute05:00
*** bpokorny has joined #openstack-meeting-405:02
*** piet has joined #openstack-meeting-405:11
*** piet has quit IRC05:30
*** zeih has joined #openstack-meeting-405:30
*** banix has joined #openstack-meeting-405:31
*** salv-orlando has joined #openstack-meeting-405:31
*** zeih has quit IRC05:35
*** tfukushima has joined #openstack-meeting-405:45
*** markvoelker has joined #openstack-meeting-405:46
*** salv-orlando has quit IRC05:48
*** salv-orlando has joined #openstack-meeting-405:50
*** markvoelker has quit IRC05:51
*** salv-orl_ has joined #openstack-meeting-405:54
*** salv-orlando has quit IRC05:56
*** bpokorny has quit IRC05:56
*** salv-orlando has joined #openstack-meeting-405:57
*** salv-orl_ has quit IRC05:58
*** salv-orlando has quit IRC06:07
*** salv-orlando has joined #openstack-meeting-406:08
*** tfukushima has quit IRC06:12
*** salv-orl_ has joined #openstack-meeting-406:14
*** salv-orlando has quit IRC06:14
*** banix has quit IRC06:15
*** sripriya has joined #openstack-meeting-406:16
*** javeriak has joined #openstack-meeting-406:18
*** sripriya has left #openstack-meeting-406:19
*** numans has joined #openstack-meeting-406:23
*** javeriak_ has joined #openstack-meeting-406:40
*** salv-orlando has joined #openstack-meeting-406:41
*** javeriak has quit IRC06:41
*** salv-orl_ has quit IRC06:43
*** harshs has joined #openstack-meeting-406:45
*** markvoelker has joined #openstack-meeting-406:47
*** markvoelker has quit IRC06:52
*** armax has quit IRC06:57
*** harshs_ has joined #openstack-meeting-407:01
*** harshs has quit IRC07:01
*** harshs_ is now known as harshs07:01
*** tfukushima has joined #openstack-meeting-407:02
*** salv-orlando has quit IRC07:04
*** vishwanathj has joined #openstack-meeting-407:14
*** xuhan has joined #openstack-meeting-407:25
*** Jeffrey4l has quit IRC07:31
*** salv-orlando has joined #openstack-meeting-407:36
*** mfedosin has joined #openstack-meeting-407:38
*** Jeffrey4l has joined #openstack-meeting-407:44
*** salv-orl_ has joined #openstack-meeting-407:47
*** salv-orlando has quit IRC07:47
*** sdake has quit IRC07:47
*** sdake has joined #openstack-meeting-407:49
*** salv-orlando has joined #openstack-meeting-407:54
*** salv-orl_ has quit IRC07:55
*** salv-orl_ has joined #openstack-meeting-407:57
*** salv-orlando has quit IRC07:57
*** yamamoto has quit IRC08:00
*** yamamoto has joined #openstack-meeting-408:03
*** salv-orl_ has quit IRC08:05
*** yamamoto has quit IRC08:06
*** salv-orl_ has joined #openstack-meeting-408:08
*** Jeffrey4l has quit IRC08:08
*** mfedosin has quit IRC08:10
*** salv-orl_ has quit IRC08:14
*** matrohon has joined #openstack-meeting-408:15
*** yamamoto has joined #openstack-meeting-408:18
*** yamamoto has quit IRC08:18
*** Jeffrey4l has joined #openstack-meeting-408:21
*** xingchao has quit IRC08:23
*** EvgenyF has joined #openstack-meeting-408:24
*** [1]evgenyf has joined #openstack-meeting-408:24
*** Jeffrey4l has quit IRC08:26
*** salv-orlando has joined #openstack-meeting-408:27
*** harshs has quit IRC08:29
*** meteorfox has quit IRC08:31
*** meteorfox has joined #openstack-meeting-408:31
*** bknudson has quit IRC08:31
*** xingchao has joined #openstack-meeting-408:32
*** Jeffrey4l has joined #openstack-meeting-408:38
*** salv-orlando has quit IRC08:38
*** sdake has quit IRC08:39
*** piet has joined #openstack-meeting-408:41
*** zeih has joined #openstack-meeting-408:43
*** amotoki has quit IRC08:45
*** salv-orlando has joined #openstack-meeting-408:45
*** salv-orlando has quit IRC08:46
*** njohnst__ has quit IRC08:47
*** salv-orlando has joined #openstack-meeting-408:47
*** dshakhray has joined #openstack-meeting-408:47
*** [1]evgenyf has quit IRC08:47
*** EvgenyF has quit IRC08:48
*** markvoelker has joined #openstack-meeting-408:48
*** xingchao has quit IRC08:49
*** njohnsto_ has joined #openstack-meeting-408:51
*** markvoelker has quit IRC08:53
*** piet has quit IRC08:54
*** Jeffrey4l has quit IRC08:55
*** dims has joined #openstack-meeting-408:55
*** salv-orlando has quit IRC08:57
*** woodard_ has quit IRC08:58
*** salv-orlando has joined #openstack-meeting-408:59
*** Jeffrey4l has joined #openstack-meeting-408:59
*** baohua has quit IRC09:00
*** vishwanathj has quit IRC09:06
*** mbound_ has joined #openstack-meeting-409:07
*** salv-orlando has quit IRC09:08
*** yamahata has joined #openstack-meeting-409:08
*** Jeffrey4l has quit IRC09:11
*** javeriak_ has quit IRC09:11
*** dims has quit IRC09:13
*** piet has joined #openstack-meeting-409:18
*** aarefiev has quit IRC09:20
*** salv-orlando has joined #openstack-meeting-409:26
*** dshakhray has quit IRC09:31
*** javeriak has joined #openstack-meeting-409:32
*** piet has quit IRC09:34
*** mfedosin has joined #openstack-meeting-409:37
*** bharathm has quit IRC09:45
*** yamamoto has joined #openstack-meeting-409:47
*** fc__ has quit IRC09:50
*** fc__ has joined #openstack-meeting-409:52
*** salv-orlando has quit IRC09:54
*** xuhan has quit IRC10:02
*** EvgenyF has joined #openstack-meeting-410:02
*** [1]evgenyf has joined #openstack-meeting-410:02
*** Jeffrey4l has joined #openstack-meeting-410:04
*** Jeffrey4l has quit IRC10:15
*** Jeffrey4l has joined #openstack-meeting-410:15
*** dshakhray has joined #openstack-meeting-410:24
*** dshakhray has quit IRC10:40
*** salv-orlando has joined #openstack-meeting-410:41
*** dshakhray has joined #openstack-meeting-410:42
*** yamahata has quit IRC10:43
*** tfukushima has quit IRC10:44
*** markvoelker has joined #openstack-meeting-410:49
*** EvgenyF_ has joined #openstack-meeting-410:50
*** [2]evgenyf has joined #openstack-meeting-410:50
*** sambetts-afk is now known as sambetts10:50
*** [1]evgenyf has quit IRC10:51
*** EvgenyF has quit IRC10:51
*** [2]evgenyf is now known as evgenyf10:51
*** markvoelker has quit IRC10:53
*** Jeffrey4l has quit IRC10:58
*** coolsvap is now known as coolsvap|away11:01
*** xingchao has joined #openstack-meeting-411:16
*** bogdando has quit IRC11:16
*** evgenyf has quit IRC11:20
*** EvgenyF_ has quit IRC11:21
*** EvgenyF_ has joined #openstack-meeting-411:21
*** evgenyf has joined #openstack-meeting-411:21
*** yamamoto has quit IRC11:23
*** EvgenyF__ has joined #openstack-meeting-411:31
*** EvgenyF_ has quit IRC11:35
*** bogdando has joined #openstack-meeting-411:40
*** baohua has joined #openstack-meeting-411:43
*** salv-orlando has quit IRC11:47
*** salv-orlando has joined #openstack-meeting-411:47
*** evgenyf has quit IRC11:58
*** EvgenyF__ has quit IRC11:58
*** yamamoto has joined #openstack-meeting-412:00
*** yamamoto_ has joined #openstack-meeting-412:02
*** salv-orlando has quit IRC12:03
*** yamamoto has quit IRC12:05
*** salv-orlando has joined #openstack-meeting-412:09
*** salv-orlando has quit IRC12:11
*** eyalb has joined #openstack-meeting-412:12
*** eyalb has left #openstack-meeting-412:12
*** javeriak has quit IRC12:12
*** baohua has quit IRC12:17
*** baohua has joined #openstack-meeting-412:18
*** baoli has joined #openstack-meeting-412:24
*** baoli has quit IRC12:27
*** javeriak has joined #openstack-meeting-412:30
*** markvoelker has joined #openstack-meeting-412:35
*** woodard has joined #openstack-meeting-412:35
*** woodard has quit IRC12:35
*** yamamoto_ has quit IRC12:36
*** woodard has joined #openstack-meeting-412:36
*** markvoelker has quit IRC12:39
*** _degorenko|afk is now known as degorenko12:41
*** baoli has joined #openstack-meeting-412:41
*** baoli_ has joined #openstack-meeting-412:43
*** afveitch has quit IRC12:44
*** baoli_ has quit IRC12:46
*** baoli_ has joined #openstack-meeting-412:47
*** baoli has quit IRC12:47
*** baoli_ has quit IRC12:51
*** yamamoto has joined #openstack-meeting-412:53
*** javeriak_ has joined #openstack-meeting-412:53
*** yamamoto has quit IRC12:54
*** javeriak has quit IRC12:55
*** javeriak has joined #openstack-meeting-412:56
*** javeriak_ has quit IRC12:58
*** baohua has quit IRC13:01
*** baohua_ has joined #openstack-meeting-413:01
*** baohua_ has quit IRC13:05
*** baohua has joined #openstack-meeting-413:06
*** markvoelker has joined #openstack-meeting-413:09
*** baohua has quit IRC13:12
*** baohua has joined #openstack-meeting-413:12
*** klamath has joined #openstack-meeting-413:16
*** Jeffrey4l has joined #openstack-meeting-413:16
*** klamath has quit IRC13:16
*** klamath has joined #openstack-meeting-413:16
*** cdupont has joined #openstack-meeting-413:17
*** xingchao has quit IRC13:25
*** javeriak has quit IRC13:29
*** matrohon has quit IRC13:36
*** dslev_ has quit IRC13:38
*** piet has joined #openstack-meeting-413:44
*** brunograz has joined #openstack-meeting-413:48
*** delatte has joined #openstack-meeting-413:48
*** dslev has joined #openstack-meeting-413:49
*** xingchao has joined #openstack-meeting-413:51
*** delattec has quit IRC13:52
*** yamamoto has joined #openstack-meeting-413:55
*** piet has quit IRC13:55
*** EvgenyF has joined #openstack-meeting-413:56
*** piet has joined #openstack-meeting-413:56
*** [1]evgenyf has joined #openstack-meeting-413:56
*** gjayavelu has joined #openstack-meeting-413:57
*** FallenPegasus has joined #openstack-meeting-413:57
*** dronshaw has joined #openstack-meeting-413:57
*** bobh has joined #openstack-meeting-413:57
*** njohnsto_ has quit IRC13:58
*** dtardivel has joined #openstack-meeting-414:01
*** vmahe__ has joined #openstack-meeting-414:01
dtardivel#startmeeting watcher14:01
openstackMeeting started Wed Dec 16 14:01:54 2015 UTC and is due to finish in 60 minutes.  The chair is dtardivel. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** jwcroppe has joined #openstack-meeting-414:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
*** amotoki has joined #openstack-meeting-414:02
jwcroppehi14:02
*** yamamoto has quit IRC14:02
sballeo/ I won;t be able to join :-( I am hosting a meeting14:02
jed56hello14:02
jwcroppeo/14:02
brunograzhi14:02
*** amotoki has quit IRC14:02
dtardivelo/14:02
tpeopleso/14:02
cduponto/14:02
edleafe\o14:02
cdupont\o/14:03
*** amotoki has joined #openstack-meeting-414:04
*** amotoki has quit IRC14:04
*** amotoki has joined #openstack-meeting-414:04
*** seanmurphy has joined #openstack-meeting-414:04
*** rbak has joined #openstack-meeting-414:04
*** leecalcote has joined #openstack-meeting-414:05
dtardivelagenda is available on #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#12.2F16.2F201514:05
dtardivelok let's go :)14:06
dtardivel #topic Announcements14:06
cdupontHi dtardivel, I have some requests for this meeting :)14:06
cdupontCould we store more informations in the minutes using #info ?14:07
dtardivelreminder: Mid-cycle eventbrite registration is opened14:07
cdupontbecause after each meeting I am obliged to browse the full log to create my report14:07
dtardivelcdupont: yes i will try14:08
cdupontthanks!14:08
dtardivel#info Mid-cycle eventbrite registration is opened14:08
jwcroppedtardivel: did acabot send on mailing list?14:08
cdupontAlso I was wondering if this meeting could be longer, one hour is short in a launch phase like now14:08
cdupontit's always very rushed and no time for questions...14:09
edleafecdupont: meetings are standard at 1 hour. We can always continue in #openstack-watcher14:09
dtardivelfor b<>com, acabot and jed56 will go to the meeting14:09
*** delattec has joined #openstack-meeting-414:09
jed56jwcroppe I don't think so14:10
*** ekarlso has quit IRC14:10
dtardivelfor bcom, acabot and jed56 will go to the meeting14:10
jwcroppejed56: ok, I think we need to send out on mailing list - I updated the wiki with details as well and he also created the eventbrite14:10
jed56great job thanks14:10
jwcroppe#link https://wiki.openstack.org/wiki/Watcher_mitaka_mid-cycle_meetup_agenda14:11
cdupontthis is April 25 - 29, 2016 in Austin, right14:11
cdupont?14:11
*** vincentfrancoise has joined #openstack-meeting-414:11
jwcroppecdupont: Feb 2-414:11
jed56I have my ticket!14:12
tpeoples#info mid-cycle meetup in Austin Feb 2-4, 201614:12
cdupontOk14:12
*** delatte has quit IRC14:13
dtardivel#action dtardivel send (again ?) the announce to the mailing list14:13
*** brunograz_ has joined #openstack-meeting-414:13
dtardivelnext: we released the mitaka-1 milestone on Watcher14:14
cdupontCould you circulate again the mailing list address?14:14
cdupontits not in the wiki14:15
*** brunograz has quit IRC14:15
dtardivelall fixes committed and targeted into this milestone have been automatically set to 'fix released' state14:15
tpeoplesopenstack-dev14:15
jed56#link http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev14:16
tpeopleswith a [watcher] tag14:16
cdupontOK, there is no mailing list specific to watcher?14:16
cdupontthis is a very high volume mailing :(14:16
*** kproskurin has joined #openstack-meeting-414:17
dtardivelcdupont: you can use the tag as a filter ;)14:17
tpeoplesNo, that's just how the openstack projects do it14:18
seanmurphy#info - announcements pertaining to watcher typically distributed on openstack-dev list with [watcher] as tag14:18
cdupontI see them as [openstack-dev] [watcher]14:19
cdupontI'll create a filter ;)14:19
jwcroppenext topic?14:19
dtardivelacabot has posted a video about Watcher UI #link https://drive.google.com/drive/u/0/folders/0B1KilbTYF00uanZCRE9kQmgzQ2814:20
dtardivelPlease check if you can access to it14:20
*** neelashah has joined #openstack-meeting-414:21
cdupontnope14:21
jwcroppeno access14:21
tpeoplesLooks like we'll have to wait for acabot14:21
cdupont:(14:21
seanmurphythe link appears to be a user specific gdrive link14:21
dtardivelyes I afraid. ok I will find a way to put the video on another location ...14:22
vmahe__I can't read the video either14:23
edleafe*cough*youtube*cough*14:23
dtardivel#action dtardivel give access to video Watcher UI to the community14:23
*** jmckind has joined #openstack-meeting-414:24
dtardivel#topic Review Action Items14:24
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:24
tpeoplesMaybe there's some sweet copyrighted music on it edleafe14:24
tpeoplesdtardivel: did you have a chance to give the devstack plugin another shot?14:25
edleafetpeoples: well, that wouldn't be in the open spirit now, would it? :)14:25
jed56:)14:25
*** vishwanathj has joined #openstack-meeting-414:26
dtardiveltpeoples: I validated the devstack installation with the wather plugin. I need more time to validate the NFS settings for live migration as documented in the patchset14:26
tpeoplescool, good to hear14:26
dtardivelso it is in good progress14:26
*** baohua has quit IRC14:27
dtardivelreview on i18n translation. What is the status ?14:27
tpeoplesi will try to check my email over the holiday break to see if we need a new patchset14:27
vincentfrancoiseWell the first patchset has been merged14:27
brunograz_tpeoples: in a related topic, we've been working on putting Watcher in a container. this is very much a work in progress and I believe that by beginning of next year we have it done14:28
vincentfrancoisewhich added the french locale to Watcher14:28
vincentfrancoise#link https://review.openstack.org/#/c/256591/14:28
*** baohua has joined #openstack-meeting-414:28
tpeoplesvincentfrancoise: i will re-review before i leave for vacation14:28
jwcroppedtardivel: FYI, I need to drop in 2 mins... I will review the pending watcher-specs as well14:28
*** amotoki has quit IRC14:28
vincentfrancoiseAnd there is another one in waiting for reviews14:29
*** yamamoto has joined #openstack-meeting-414:29
vincentfrancoise#link https://review.openstack.org/#/c/257475/14:29
*** yamamoto has quit IRC14:29
tpeoplesbrunograz_: I believe bcom already has a container-based deployment of watcher working14:29
dtardivelbrunograz_: we have project on github named watcher-tools where you will find a complete setup of watcher based on Docker container and ansible :)14:29
tpeopleslet's save that for open discussion14:29
dtardivel#link https://github.com/b-com/watcher-tools14:29
tpeoplesvincentfrancoise:  i am not too worried about the content of the log messages for the i18n work, just the way they are being translated.  we can worry about the content later... jfyi14:30
*** yamamoto has joined #openstack-meeting-414:30
brunograz_tpeoples dtardivel that's pretty cool, it would be good to have it as well in the github description. but yeah true let's leave it for the right topic :)14:31
*** leecalcote has quit IRC14:31
*** leecalcote has joined #openstack-meeting-414:31
dtardivelthere is again some review on progress about refactoring #link https://review.openstack.org/25724914:31
vincentfrancoisetpeoples: you mean the actual messages that are currently logged?14:32
tpeoplesYeah, I'm saying we can improve the actual log strings later, but for the i18n work let's just get them translatable14:33
vincentfrancoiseFor the refactoring bit, most of the work has already been merged14:33
*** rbak has quit IRC14:33
tpeoplesi will review 257249 again before i leave jed56, thanks for respinning14:33
vincentfrancoise#link https://review.openstack.org/#/c/257249/ is the only one remaing14:34
jed56tpeoples thanks14:34
jed56next topic ?14:36
tpeopleswrt the intel thermal PoC - I think that needs some rework before we can merge.  I identified some concerns I had with the approach in the review14:36
tpeoplesthough the concerns I had might also apply to the consolidation algorithm.  I think we need to be using the nova-scheduler to help make decisions on where to migrate to.  Otherwise we lose the benefit of all of the other filters14:38
tpeoplesso for a PoC it's fine not to do that, but IMO it should be14:38
jed56tpeoples : I agree14:38
cdupontare you refering to https://blueprints.launchpad.net/watcher/+spec/outlet-temperature-based-strategy ?14:39
jwcroppetpeoples: right, scheduler for sure needs to be involved14:39
*** sdake has joined #openstack-meeting-414:39
tpeoplesyes cdupont, review is here #https://review.openstack.org/#/c/25718914:39
tpeoplesi also don't like that the resources used is being calculated on the fly (instead of relying on the scheduler ... or some sort of cache within watcher) to get that info14:40
cdupontIs it possible to link the BP to its spec, even if in progress?14:40
*** gjayavelu has quit IRC14:40
cdupontI noticed the spec field is never set, for all the BPs I checked14:41
tpeoplesthat sort of thing ^ won't scale very well14:41
tpeoplesbut again, fine for PoC...14:41
dtardivelcdupont: you can push a first patchset , and set it into Work In Progress (ie workflow = -1)14:42
cdupontOk14:42
jed56tpeoples : I think that can be done through a blueprint ( cache system for nova and ceilometer )14:42
dtardivelvmahe__, what about your review on dynamic action #link https://review.openstack.org/#/c/257494/14:43
tpeoples#action junjie bzhou incorporate review comments into https://review.openstack.org/#/c/25718914:43
tpeoplesyes jed56 , probably14:43
vmahe__I will push a new patch-set very soon14:43
tpeoplesdon't want to tell the intel folks they need to solve all of our problems :)14:43
tpeoplesthat's why i said good for a proof of concept14:44
vmahe__following some discussion with jed56 and vincentfrancoise14:44
*** javeriak has joined #openstack-meeting-414:44
dtardivelok14:44
tpeopleshave you guys had a chance to poke into taskflow any more?14:44
jed56tpeoples : yes a little bi t14:44
vmahe__yes14:45
*** zeih_ has joined #openstack-meeting-414:45
vmahe__it looks great14:45
*** Swami_ has joined #openstack-meeting-414:45
jed56this a great tool but some feature are missing14:45
vmahe__but we need to also have a look to other frameworks such as Mistral or other Python frameworks14:45
*** zeih has quit IRC14:45
tpeoplesjed56: what features and are they deal breakers?14:45
jed56for example you can describe your Flow but you cannot describe some constraints to be solve by the workflow engine ( e.g A need to before B )14:47
jed56you have to describe your workflow by yourself14:47
dtardivelremains 10mn :)14:48
jed56morever there is not a clear separation of concern between the planner and applier14:48
dtardivel#topic Blueprint/Bug Review and Discussion14:48
tpeoplesi imagined we'd have to build the workflow ourself.14:48
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:48
jed56tpeoples : yes but with vmahe14:48
tpeoplesthe planner would essentially build the flow with all of the dependencies, and then the applier would just run the flow using an engine14:49
jed56we think that some tools can do to that built in14:49
*** jwcroppe has quit IRC14:49
*** banix has joined #openstack-meeting-414:49
jed56but this is WiP14:49
jed56:)14:49
jed56I have a PoC with taskflow14:49
tpeoplesok cool14:50
tpeopleswrt the tempest blueprint / work (https://blueprints.launchpad.net/watcher/+spec/tempest-basic-set-up), i passed it to vincentfrancoise  while I am out on vacation14:50
vincentfrancoiseyup14:51
cdupontregarding the BP https://blueprints.launchpad.net/watcher/+spec/watcher-consolidation-grammar14:51
dtardivelabout tempest basic set up #link https://blueprints.launchpad.net/watcher/+spec/tempest-basic-set-up, vincentfrancoise will be able to work on it very soon14:51
cdupontI completed a first draft14:51
cdupontI will upload as soon as I understand how gerrit works :)14:51
jed56cdupont : great  can you push a patchset ?14:52
cdupontyep14:52
jed56cdupont : we can help you on openstack-watcher14:52
cdupontOK14:52
cdupontthanks14:52
*** bknudson has joined #openstack-meeting-414:52
dtardivelcdupont: we can assist you if you need help14:52
jed56cdupont : http://docs.openstack.org/infra/manual/sandbox.html14:53
cdupont#action cdupont  push a patchset for spec https://blueprints.launchpad.net/watcher/+spec/watcher-consolidation-grammar14:54
tpeoplesany other blueprints or bugs to discuss?14:54
dtardivelI think we have to make effort on spec in the few weeks, because refactoring and enhancement coding tasks will be finished soon...14:54
dtardiveland we need spec to make coding :)14:55
jed56in the few weeks : vacations!14:55
cdupontyeah14:55
vincentfrancoiseas you may have noticed, Watcher is now python 3.4 compatible14:55
dtardivelvincentfrancoise: +114:56
vincentfrancoiseSo we have to make sure our tests pass both py27 and py34 gates ;)14:56
tpeoplessweet14:56
tpeoplesopen discussion quick?14:56
dtardivelbrunograz_: containers ?14:57
brunograz_dtardivel: just wanted to pointed out that would be good to have a link in the git repo14:57
brunograz_but we can follow up this in the watcher chat14:58
*** vishwanathj_ has joined #openstack-meeting-414:58
vincentfrancoisebrunograz_: you mean in the readme file?14:58
*** rbak has joined #openstack-meeting-414:58
tpeoplesin regards to accommodations for Austin for the midcycle - a lot of people who visit IBM stay at hotels near the Arboretum.  I'm not sure where jwcroppe is staying specifically.14:58
brunograz_vincentfrancoise: yes14:58
tpeoplesThe Domain is literally across the street from IBM so you'd be able to walk, but the hotels there will be more expensive14:59
*** sdake has quit IRC14:59
brunograz_vincentfrancoise: particularly, I didn;t know abt this other repo14:59
tpeoplesFeel free to message me with any questions14:59
jed56tpeoples : ok14:59
dtardivelok, it's time14:59
dtardivelbye14:59
brunograz_bye14:59
vincentfrancoisebrunograz_: create a wishlist bug and feel free to do it I guess14:59
vmahe__bye14:59
vincentfrancoisebye14:59
tpeoplesAnd I am out on vacation until next year, so ttyl :)14:59
dtardivel#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Dec 16 15:00:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-16-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-16-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-16-14.01.log.html15:00
*** eric__ has quit IRC15:01
jasondotstar#startmeeting vahana15:01
openstackMeeting started Wed Dec 16 15:01:30 2015 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. 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: vahana)"15:01
openstackThe meeting name has been set to 'vahana'15:01
jasondotstar#topic roll call15:02
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:02
jasondotstarwell, this will be an extremely short meeting :-)15:02
jasondotstar#topic General Discussion15:03
*** openstack changes topic to "General Discussion (Meeting topic: vahana)"15:03
jasondotstarI *think* we'll just cancel this week's meeting.15:03
jasondotstargoing once? twice?15:04
*** brunograz_ has left #openstack-meeting-415:04
jasondotstarThx. Until next week.15:04
jasondotstar#endmeeting15:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:04
openstackMeeting ended Wed Dec 16 15:04:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-16-15.01.html15:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-16-15.01.txt15:04
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-16-15.01.log.html15:04
*** dandruta has joined #openstack-meeting-415:04
*** banix has quit IRC15:07
*** vincentfrancoise has left #openstack-meeting-415:07
*** mhoppal has joined #openstack-meeting-415:09
*** mhoppal has left #openstack-meeting-415:09
*** baoli has joined #openstack-meeting-415:10
*** baohua has quit IRC15:10
*** yamahata has joined #openstack-meeting-415:22
*** leecalcote has quit IRC15:26
*** [1]evgenyf has quit IRC15:31
*** EvgenyF has quit IRC15:32
*** julim has quit IRC15:36
*** javeriak_ has joined #openstack-meeting-415:37
*** javeriak has quit IRC15:37
*** cdupont has quit IRC15:40
*** zeih_ has quit IRC15:41
*** piet has quit IRC15:45
*** piet has joined #openstack-meeting-415:45
*** barrett1 has joined #openstack-meeting-415:48
*** pmesserli has joined #openstack-meeting-415:48
*** sdake has joined #openstack-meeting-415:48
*** numans has quit IRC15:50
*** avarner has joined #openstack-meeting-415:50
*** dwalleck has joined #openstack-meeting-415:57
*** zeih has joined #openstack-meeting-415:58
*** sdake has quit IRC16:00
*** zehicle has joined #openstack-meeting-416:01
*** zehicle has quit IRC16:01
*** dwalleck has quit IRC16:02
*** dwalleck has joined #openstack-meeting-416:02
*** zeih has quit IRC16:03
*** banix has joined #openstack-meeting-416:08
*** vishwana_ has joined #openstack-meeting-416:08
*** EvgenyF has joined #openstack-meeting-416:09
*** [1]evgenyf has joined #openstack-meeting-416:09
*** armax has joined #openstack-meeting-416:09
*** vishwanathj has quit IRC16:10
*** leecalcote has joined #openstack-meeting-416:10
*** sdake has joined #openstack-meeting-416:11
*** xingchao has quit IRC16:12
*** sdake has quit IRC16:13
*** devananda has quit IRC16:14
*** sdake has joined #openstack-meeting-416:18
*** ekarlso has joined #openstack-meeting-416:18
*** inc0 has joined #openstack-meeting-416:19
-openstackstatus- NOTICE: Gerrit will be offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html16:20
*** devananda has joined #openstack-meeting-416:22
*** jmckind_ has joined #openstack-meeting-416:22
*** jmckind has quit IRC16:25
*** julim has joined #openstack-meeting-416:26
*** dwalleck has quit IRC16:27
*** pmesserli has quit IRC16:28
*** rhallisey has joined #openstack-meeting-416:30
*** marek_ has joined #openstack-meeting-416:31
*** bpokorny has joined #openstack-meeting-416:31
sdake#startmeeting kolla16:32
openstackMeeting started Wed Dec 16 16:32:25 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:32
*** openstack changes topic to " (Meeting topic: kolla)"16:32
openstackThe meeting name has been set to 'kolla'16:32
sdake#topic rollcall16:32
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:32
rhalliseyhello16:32
sdake\o/ back in the land of the living ;)16:32
nihilifero/16:32
Jeffrey4lo/16:32
jpeelerhi16:32
inc0o/16:32
barrett1o/16:32
*** mzawadzki has joined #openstack-meeting-416:33
ajafohi16:33
marek_hi16:33
*** mzawadzki has quit IRC16:33
sdake#topic midcycle prep16:33
*** openstack changes topic to "midcycle prep (Meeting topic: kolla)"16:34
*** stvnoyes has joined #openstack-meeting-416:34
sdakenot sure when the midcycle will be, probably sometime in late january16:34
britthouser0/16:34
sdakei will soon get a poll going to determine what time works best for people16:34
*** mfedosin has quit IRC16:34
sdakewe need to go ahead and produce our list of sessions for the midcycle now though16:35
sdakethe midcycle will be two days in length16:35
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle16:35
*** javeriak_ has quit IRC16:36
sdakelets spend 10-15 mins on the etherpad putting in our session ideas please16:36
elemoineo/16:37
britthousersessions being working session planning session, both?16:37
inc0britthouser, well, it's midcycle so form is more loose16:38
britthouserthanks inc0...my first one so I wasn't sure16:38
*** banix has quit IRC16:38
sdakei suspect upgrades will be a 4 hour session or more ;)16:39
sdakebut we still need more dmaterial16:39
inc0<hides under the table before 4 hrs of incoming hate>16:40
nihiliferdiagnostics == monitoring?16:40
sdakenihilifer  yes among another things16:40
sdakemoniitoring is a component of diagnostics16:41
inc018 months roadmap planning will not end after 1hr for sure16:41
*** jmckind has joined #openstack-meeting-416:41
sdakediagnostics is a catchall for anything diag related ;)16:41
sdakecan folks do me a solid and sign their names into etherpad please so I know where the session ideas came from16:42
barrett1On the roadmap - want to get ahead of the update cycle run by the Product WG16:42
sdakebarrett1  roger understood - would you mind signing in as a contribu ptop please16:43
sdakeok i'll igve this another 3-5 minutes then we can move on, and have another session next week to catch people that missed this session16:44
barrett1sdake: will do16:44
britthouserthanks rhallisey16:44
rhalliseybritthouser, sure thing :D16:44
*** jmckind_ has quit IRC16:45
inc0I think we can revisit this list on following meeting16:46
sdake#topic mitaka-1 release16:46
*** openstack changes topic to "mitaka-1 release (Meeting topic: kolla)"16:46
sdakeok lets move on :)16:46
barrett1sdake: 1 caveat - I go on sabbatical at the end of this week and will return to work on 1/28. If the midcycle happens earlier in Jan I won't be able to attend. Leong Sun is covering for me and would be able to attend.16:46
*** Leong has joined #openstack-meeting-416:46
sdakebarrett1 understood16:46
sdake#link https://launchpad.net/kolla/+milestone/mitaka-116:47
sdakeso basically because I was out of action I never cut a m1 release16:47
sdakeunfortunately the way the openstack process works for projects not managed by the release team, the PTL is a SPOF in the tagging and release process of milestones16:48
britthouserI think I can break away this week on work on my BP16:48
sdakefortunately its just m1, so its not deadly16:48
britthouserit shouldn't be a large amount of work.16:49
sdakeI am going to cut a m1 on dec 23rd16:49
sdakeI am going to move any blueprints not in good progress or above to mitaka-2 at end of this week (18th)16:49
britthouserok16:50
sdakecan folks that own blueprints please update the state sometime today of whether its good progress, started, implemented, needs code review, etc16:51
sdakeI see magnum in there, and I thought that was done for example16:51
sdakenihilifer  ^^ ? :)16:51
*** javeriak has joined #openstack-meeting-416:51
nihilifersdake: yes, sorry, i forgot to close it16:51
sdakeits all good16:52
sdakeif folks have stuff like this please set to implemented16:52
*** gjayavelu has joined #openstack-meeting-416:52
sdakeunfortunately because it isn't friday yet, we can't discuss mitaka-216:52
sdakebut I'd like mitaka-2's main theme to be upgrades16:52
sdakeany objections?16:53
rhalliseynone16:53
nihilifernope16:53
rhalliseyBPs are all in place16:53
sdakenice16:53
inc0yeah, and I think we got our differences sorted out for now16:53
inc0just request from my side - review nova upgrade code to confirm way we're going to attack upgrades16:53
sdakewill look at it16:54
sdakemy mother broke her l4 vertebrea16:54
*** banix has joined #openstack-meeting-416:54
sdakeso looking after her a bit16:54
sdakebsically my life is a POS atm16:54
britthouseryikes....yeah when it rains it pours!16:54
*** dmsimard has joined #openstack-meeting-416:54
barrett1sdake: Sorry to hear that!16:54
sdakeno doubt16:54
sdakeit could be worse so I count my blessings :)16:54
britthouser=)16:54
sdake#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:55
sdakeok folks, know meeting isn't all that exciting today16:55
nihiliferi actually see 2 points more in agenda16:55
sdakewhich nihilifer ?16:55
nihiliferhttps://wiki.openstack.org/wiki/Meetings/Kolla16:56
nihiliferlet me go to mine16:56
nihilifer#topic kolla-mesos16:56
sdake#endu16:56
sdake#topic kolla-mesos16:56
*** openstack changes topic to "kolla-mesos (Meeting topic: kolla)"16:56
sdakenihilifer only I can set #tpk16:56
nihiliferok, let me share an update16:56
sdakeok nihilifer  all yours ;)16:56
*** gjayavelu has quit IRC16:56
*** blahRus has joined #openstack-meeting-416:56
nihiliferwe currently have a working tool deploying services on marathon and ansible tasks on chronos16:57
*** u_kozat has joined #openstack-meeting-416:57
nihilifercurrently supported services - mariadb, keystone, glance and horizon16:57
nihiliferi think we're in point where people can feel free to take any available component of kolla and try to run it on mesos16:57
nihiliferif you're confused about structure of repository, feel free to ask me directly16:58
inc0nihilifer, can you please write quickstart guide for mesos?16:58
kproskurinand me if nihilifer is away16:58
rhalliseyinc0, good idea16:58
sdakeya docs are fantastic folks :) wtb em :))16:58
nihiliferinc0: sure. you mean quickstart for contributing to kolla-mesos?16:59
jpeelerfor getting up and running16:59
inc0nihilifer, for deploying;)16:59
*** banix has quit IRC16:59
*** harshs has joined #openstack-meeting-416:59
nihiliferfor now thre's quickstart for vagrant and running the kolla-mesos-deploy tool16:59
nihiliferbut ok, i can try to make it more detailed16:59
nihiliferlast but not least16:59
inc0yeah, something that will describe how it all works and so on plz17:00
*** persia has quit IRC17:00
nihiliferwe're looking for reviews from kolla-core guys as well17:00
inc0docs will help...;)17:00
nihiliferand thanks for those who're doing it currently17:00
nihiliferthat's all17:00
nihilifersdake: we can move to the next topic, i think17:00
rhalliseyI mentioned it last meeting.  Add kolla-mesos to your watch list17:01
rhalliseyif you want to help17:01
*** sigmavirus24_awa is now known as sigmavirus2417:01
kproskurinit’s really low trafic right now so it’s easy to get in17:01
sdake#topic open discussion17:01
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:01
marek_I think we have 1 more topic.17:02
sdakethe upgrades?17:02
marek_Upgrading containers - use case & POF implementation plan (https://etherpad.openstack.org/p/kolla_upgrading_containers)17:02
marek_sdake yes17:02
sdake#undo17:02
nihiliferupgrades regarding kolla-mesos17:02
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xa6845d0>17:02
sdake#topic upgrade brainstorm17:02
*** openstack changes topic to "upgrade brainstorm (Meeting topic: kolla)"17:02
sdake#link https://etherpad.openstack.org/p/kolla_upgrading_containers17:03
marek_Ok guys, thanks & let me mention I'm new to Kolla team @ Mirantis so please bear with me.17:03
sdakeoh 5his is mesos specific?17:03
marek_sdake yes17:03
nihilifersdake: yes17:03
sdakeok my apologies, I htought we covered upgrades already :)17:03
nihiliferwell, we'd like to share the similar idea regarding mesos17:04
sdakemarek_ so would you like a brainstorm session or which?17:04
marek_sdake: it's ok. So basically I will work on a simple tool for upgrading mesos apps with new version of Docker images.17:04
*** javeriak_ has joined #openstack-meeting-417:04
*** javeriak has quit IRC17:04
marek_sdake: yes - I've made POF & a plan on etherpad and before I start coding I'd like you to review it.17:04
-openstackstatus- NOTICE: Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html17:04
*** ChanServ changes topic to "Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html"17:04
sdakemarek_  cool so I think instead of just me reviewing, it makes sense for broader community to have a review of the proposed plan17:05
sdakewould you mind sending an email to the mailing list iwth [kolla] tags17:05
sdakerequesting such assistance?17:05
marek_sdake: ok, np.17:05
sdakeso looking over the doc, looks liek you spent some good time on it, hopefully a review will help you out17:06
nihiliferanyone would like to share some thoughts atm?17:06
sdakemake sure to indicate what you are looking to get out of the effort marek_17:06
inc0so, tags17:07
inc0we just battled against using tags as version pointers17:07
inc0I would show you different approach but gerrit is down17:07
*** vmahe__ has quit IRC17:07
nihiliferinc0: so what you propose to use instead of tags?17:08
inc0anyway argument was that people might want to use tags for their own business specific purposes so we shouldn't use it for our logic17:08
nihiliferlabels?17:08
inc0file in container17:08
*** Leong has left #openstack-meeting-417:08
inc0I just made patchset that enables it17:08
inc0that what I will use (probably) in ansible upgrades17:09
inc0and it would be good to keep this aligned17:09
sdakeagree re alignment17:09
nihiliferok, so we'll look on it when gerrit goes back17:09
inc0sure17:09
nihiliferyes, marek_'s idea is very similar to what inc0 proposed in visible yet patch17:10
marek_guys but in general, I'd like to know if the tool I plan to write up will be useful & if this is what we want for upgrades in Mesos env (for starters).17:10
sdake#action marek_ to send email to list to kickoff discussion about merging mesos upgrades with current upgrade plan17:10
inc0yeah let's move it to mailing list17:10
marek_ok17:10
sdakemarek_ I think we just decided the answer to that was we need to have this on the ml17:10
*** FallenPegasus is now known as MarkAtwood17:10
sdake#topic open discussion17:11
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:11
*** leecalcote has quit IRC17:11
sdakeanyone want the floor?17:11
inc0merry christmas everyone!17:11
britthouserMerry Christmas!17:11
sdakeinc0 ;)17:11
sdakehappy holidays !17:11
inc0or happy hannukah17:11
* sdake moar pc then inc017:12
rhalliseymerry christmas17:12
rhallisey:)17:12
barrett1Happy Holidays!17:12
sdakeok folks, remember, cutting a release on teh 23rd, so please try to wr=ap up by then17:12
sdakeat minimum, keep blueprints in corrrect state17:13
sdakethanks for coming17:13
rhalliseythanks17:13
sdake#endmeeting17:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:13
*** xingchao has joined #openstack-meeting-417:13
openstackMeeting ended Wed Dec 16 17:13:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-16-16.32.html17:13
*** rhallisey has left #openstack-meeting-417:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-16-16.32.txt17:13
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-16-16.32.log.html17:13
*** kproskurin has quit IRC17:13
*** xingchao has quit IRC17:18
*** [1]evgenyf has quit IRC17:19
*** EvgenyF has quit IRC17:19
*** yamahata has quit IRC17:21
*** salv-orlando has joined #openstack-meeting-417:21
kevinbentonneutron-lib 4lyfe!17:24
*** vishwana_ is now known as vishwanathj17:27
*** inc0 has quit IRC17:27
*** bharathm has joined #openstack-meeting-417:28
*** sdake has quit IRC17:29
*** javeriak_ has quit IRC17:29
dougwigoh, we have a fanboi17:30
dougwig#startmeeting networking_lib17:30
openstackMeeting started Wed Dec 16 17:30:34 2015 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:30
*** openstack changes topic to " (Meeting topic: networking_lib)"17:30
openstackThe meeting name has been set to 'networking_lib'17:30
dougwigagenda:17:30
dougwighttps://wiki.openstack.org/wiki/Network/Lib/Meetings17:30
dougwig#topic Welcome17:30
*** openstack changes topic to "Welcome (Meeting topic: networking_lib)"17:30
dougwighiya all, who all is around?17:31
kevinbentono/17:31
* HenryG needs a minute17:31
*** Jeffrey4l has quit IRC17:31
* dougwig hands HenryG a minute.17:31
dougwig#topic Announcements17:32
*** openstack changes topic to "Announcements (Meeting topic: networking_lib)"17:32
*** bnemec has quit IRC17:32
dougwigcoordinating work and trying to get relevant info in this wiki page:17:32
dougwighttps://wiki.openstack.org/wiki/Network/Lib/Meetings17:32
*** Swami_ has quit IRC17:32
dougwigthis next part should be fun with gerrit down...17:32
dougwig#topic Finalize callbacks interface17:32
*** openstack changes topic to "Finalize callbacks interface (Meeting topic: networking_lib)"17:32
dougwigkevinbenton, armax, ping17:33
dougwig https://review.openstack.org/#/c/253661/17:33
kevinbentonso i was thinking about this17:33
armaxdougwig: pong17:33
kevinbentonwill neutron-lib have releases?17:33
*** bnemec has joined #openstack-meeting-417:33
dougwigyes, into pypi.17:33
kevinbentonwhat i was hoping is that the first patch just takes exactly what we have for callbacks and move it over17:33
HenryGdougwig: don't troll us with gerrit links now17:33
dougwigneutron will grab it via requirements.txt, via global requirements.17:33
kevinbentonand then we iterate on that17:33
kevinbentonso the changes are easier to understand from what we have now17:34
dougwigi'm ok with that, if you're ok maintaining the old interface if it ever hits pypi ?17:34
*** dandruta has quit IRC17:34
*** salv-orlando has quit IRC17:34
*** degorenko is now known as _degorenko|afk17:34
*** salv-orlando has joined #openstack-meeting-417:34
kevinbentonwell if we need to do a pypi release and this isn't resolved yet, we can temporarily break it for the release17:34
HenryGwhen are pypi releases done? who controls when they are done?17:35
dougwigHenryG: mestery is the release manager for the stadium, and i expect when we say 'go' and then he has time.17:35
kevinbentona random number generator between 1 and 100 runs every hour17:35
kevinbentonif it pulls a 50, a release is done17:35
dougwigkevinbenton: what do you mean? hide the interface in that case?17:35
kevinbentondougwig: yeah17:35
kevinbentondougwig: make it unusable from outside the module with the hidden magic var17:36
dougwigthat's fine.  as long as tests of neutron against neutron-lib master and neutron-lib (latest pypi) are always green, i'm happy.17:37
dougwigdoes anyone object to phasing it in that way?17:37
HenryGsounds good to me17:37
kevinbentondougwig: sounds good17:37
dougwig#action someone make a note in gerrit on this when it's up17:37
dougwig#topic Do we hate pylint?17:37
*** openstack changes topic to "Do we hate pylint? (Meeting topic: networking_lib)"17:37
dougwigthis was 90% a joke, but17:38
armaxdougwig: what would be the note?17:38
kevinbentonso i didn't get to see this review yet17:38
dougwigit costs a lot to maintain, and i've only ever found *ONE* bug on top of flake8 with it.17:38
HenryGI hate 90% of pylint17:38
*** jmckind has quit IRC17:38
kevinbentonarmax: oh, to merge callbacks as they currently exist17:38
dougwigarmax: revert paul's patch to a basic move, with a plan to iterate it in place before release.17:38
armaxthat the typical effort of bootstrapping neutron-lib is to copy and paste and to iterate in tree?17:38
kevinbentonarmax: and then iterate on them so it's easier to understand the change17:38
dougwig#undo17:38
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xaaf9910>17:38
dougwigarmax: want to chime in on that?17:39
*** jmckind has joined #openstack-meeting-417:39
armaxdougwig: that’s fine by me, assumed that we just don’t ‘simply forget’ phase 2 :)17:40
dougwigarmax: i assumed that plan meant that i get to exercise my asshole mode regularly. :)17:40
armaxotherwise neutron-lib becomes a missed opportunity17:40
armaxdougwig: ack17:40
dougwigdo i hear a new tagline in there?  "Neutron: A Missed Opportunity".17:41
dougwigsorry, i'm pulling myself into the weeds.17:41
dougwig#topic Do we hate pylint?17:41
*** openstack changes topic to "Do we hate pylint? (Meeting topic: networking_lib)"17:41
kevinbentonno17:41
kevinbentonnext topic17:41
dougwigso, do we pull in this maintenance nightmare as the status quo, or do we shoot it in the head?  yes, i'm biased.  and i'm also totally cool either no.17:41
kevinbenton:)17:41
dougwigha, timebox is set to 60 seconds.17:41
*** bnemec has quit IRC17:42
kevinbentonso i was thinking we could actually use pylint to enforce some stricter standards17:42
kevinbentonlike method length limits17:42
dougwigwon't your plan of moving then iterating get in the way of that?17:42
kevinbentonand whatnot17:42
HenryGYou can put pylint exceptions in inline comments17:43
kevinbentonright, or make the existing code compliant before enabling the check17:43
armaxpylint is useful when we have 500 contributors against the same repo17:43
armaxwhen we have 5, it becomes easier to have a consistent set of coding guidelines17:44
*** Swami_ has joined #openstack-meeting-417:44
armaxthat said, it can provide a decent safety net for a language like python17:44
HenryGyeah but we are moving over code that was implemented by 500 contributors17:44
*** javeriak has joined #openstack-meeting-417:44
kevinbentonso i vote 'keep status quo' for now. we can always yank it out later17:45
armaxwe could trim down the list of pylint violation checks to those that are clearly bad17:45
HenryGarmax: +117:45
dougwigok, so it stays, sounds like. i expect this wouldn't even be a topic but for my personal change in beliefs over whether it's worth the cost.17:45
*** barrett1 has quit IRC17:45
dougwiglet's move on.17:46
dougwig#topic db modules - what moves, what changes?17:46
*** openstack changes topic to "db modules - what moves, what changes? (Meeting topic: networking_lib)"17:46
dougwigHenryG: how do we figure out how we attack this?17:46
HenryGstill not sure17:46
HenryGI would like to see less dicts, more objects17:46
kevinbentonwhat do we mean by db modules in this regard?17:46
HenryGless mixins, more composition17:47
kevinbentonso not the db models themselves17:47
kevinbentonbut the tools to manipulate them?17:47
dougwigif you look in the wiki link above, under 'db rework', you can see a list of db modules used by just a single subrepo. i can break that down further into objects within those modules, but it becomes a big list, fast.17:47
dougwigeither we move things like the base mixins, or we make something new and update all the subprojects. i'm fine with either approach, but a LOT of modules end up with a dependency chain that ends in neutron.db somewhere, so it's a blocker.17:48
*** yamahata has joined #openstack-meeting-417:48
dougwig(even some stuff in neutron.common, which just seems like a broken dependency chain that should be fixed)17:48
*** rockyg has joined #openstack-meeting-417:48
dougwigok then, let's step back.  do we want to move the mixins and support them alongside something new?  or go straight to something new?17:50
kevinbentonsomething new would be cool17:50
HenryGnot excited about supporting old stuff in the -lib17:51
*** logan- has quit IRC17:51
dougwigok, that's fine, it just adds urgency to getting the 'new' done.  what is everyone envisioning there?  or put another way, what do you *really* hate today, that needs to die in fire?17:51
*** harshs has quit IRC17:52
kevinbentonwell what mixins are used by other projects?17:52
kevinbentonthat would be the first ones to tackle17:52
kevinbentonthose*17:52
dougwigfrom neutron.db import common_db_mixin as base_db17:53
kevinbentonoh17:53
kevinbentonthat17:53
kevinbenton:)17:53
dougwigone quick spot check shows: base_db.CommonDbMixin17:53
HenryGyeah17:53
dougwigi've certainly seen worse subclasses in my life.17:54
dougwigif we're not moving that, what were y'all thinking of instead?17:56
kevinbentonmodel_base can probably go17:56
HenryGok that looks fine I think17:57
dougwigkevinbenton: go, or not move? are subprojects allowed to use the standard attributes table?17:58
* dougwig hands around the coffee pot.17:59
kevinbentondougwig: hmm18:00
dougwigok, let's take this item offline.18:00
kevinbentondougwig: well as long as they aren't adding automatic relations that will affect everyone18:00
kevinbentondougwig: yes, that should be fine18:00
*** xingchao has joined #openstack-meeting-418:01
dougwiglet's move on, we'll talk about this more, maybe in person soon.18:01
dougwig#topic Open discussion18:01
*** openstack changes topic to "Open discussion (Meeting topic: networking_lib)"18:01
dougwigHenryG: i believe you had a question here.18:01
HenryGGerrit is down but the question is there: https://wiki.openstack.org/wiki/Network/Lib/Meetings18:02
dougwigi'm not sure we can block reviews for needing neutron-lib first when it hasn't released yet?  it's not even gated against.18:03
HenryGyeah but those constants are not used anywhere yet18:03
HenryGthey're new constants18:03
kevinbentonbut we don't have to use debtcollector in the constants in neutron18:03
kevinbentonfor new ones at least18:04
*** sambetts is now known as sambetts-afk18:04
dougwigthen why are we adding them?  and will subprojects need them?18:04
kevinbentonwe can let them in and just say they will be in neutron-lib next release18:04
* dougwig shakes fist at gerrit.18:04
dougwigmy removal review will get a merge conflict, so it won't get lost ( https://review.openstack.org/242219 )18:04
*** u_kozat has quit IRC18:05
*** xingchao has quit IRC18:05
HenryGallright, let's let constants go in neutron until we are ready18:06
kevinbentoni think it's fair to immediately move any that were added this cycle too18:06
kevinbentonso we dont' have to debt collect them18:07
dougwigright, i don't think we need to debtcollector the new ones. but i'll have the maintenance item to move the interim stuff.18:07
*** stvnoyes has left #openstack-meeting-418:08
*** numans has joined #openstack-meeting-418:08
HenryGdougwig: are you keeping a list of todo's?18:09
kevinbenton#todo make todo list18:09
dougwigHenryG: in the wiki and in my list of open reviews, yes. i know the constants will get caught, because i'll get a conflict.18:09
HenryGsounds good18:10
HenryGI'll add to the wiki anything without a review or bug yet18:10
dougwiganything else today?  my biggest action item will be to hunt down HenryG and kevinbenton and get more db change details.  today.18:10
dougwigtodo list item to create todo list created.  jk.18:11
kevinbentondougwig: how about neutron.db.api?18:11
dougwigkevinbenton, HenryG: is that good to move, or do we want changes there?18:12
kevinbentondougwig: ah, but that depends on the common_db_mixin18:12
kevinbentondougwig: what's our rule for this kind of stuff?18:12
kevinbentondougwig: can't depend on neutron at all, right?18:12
dougwigkevinbenton: didn't you both say it was ok to move common_db_mixin?18:12
dougwigkevinbenton: must not depend on neutron.  we can move the child dependencies, or sever them.18:13
HenryGkevinbenton: only getobject/s18:13
dougwigthe latter via dup or passing in callbacks.18:13
kevinbentondougwig: we need to go through common_db_mixin and make sure stuff that is only used internally is appropriately named so it looks private18:14
kevinbentonused internally - only used by the mixin itself18:14
dougwigok, can one of you do so, and when?18:14
HenryGI can start later tomorrow or Friday18:15
kevinbentonHenryG: thx18:16
dougwigty.18:16
kevinbentonfor neutron lib, should we start doing internal methods prefixed with double underscore so name mangling takes place?18:16
HenryGseems like a good place to start focus, thanks kevinbenton18:16
dougwigyou hit a python bit of trivia i'm unaware of.  isn't __ for stuff internal to python itself?18:17
kevinbentonno18:17
dougwigooh neat, please tell.18:17
kevinbentonif you prefix a class method with __ it makes it difficult to access18:17
dougwigreally?? why are we not using it more places??18:17
kevinbentonit gets translated18:17
kevinbentonto _classname__method18:18
kevinbentonfor external callers18:18
*** jmckind_ has joined #openstack-meeting-418:18
kevinbentonso it's quite clear you are reaching into the bowels of something18:18
dougwigthat's really good, i'd say yes.18:18
HenryGinteresting, yes18:18
kevinbentonhttps://docs.python.org/2/tutorial/classes.html#private-variables-and-class-local-references18:18
dougwigany py3 issues or something like that?18:18
kevinbentonnot that i'm aware of18:18
HenryGThe oslo folks have been doing libs for some time. Anything we can learn from them?18:19
*** jmckind has quit IRC18:19
kevinbentonso something to note is that it doesn't suggest doing this to prevent people from accessing things18:19
kevinbentonbecause this is python18:19
kevinbenton"we're all adults"18:19
kevinbentonthe convention is just a single underscore means 'internal' and that it might break18:20
*** salv-orlando has quit IRC18:21
HenryGSo a single underscore should suffice really18:21
dougwigswitch it to ruby, so i can just mark it private.18:21
* dougwig hides.18:21
* dougwig inside ruby's private namespace.18:21
kevinbentonyes, and if a subclass tries to override a double-prefix it won't do the normal thing18:21
kevinbentonsince that's actually translated to _classname__method18:22
kevinbentonthey will be different18:22
dougwigso if it's not recommended that we use it, should we? why does it even exist?18:22
kevinbentonit's mainly for classes to ensure they have a reference to the function they defined18:22
kevinbentonand not the one overridden by a subclass in inheritance18:23
kevinbentonso it's really to make things private to a class for inheritance purposes18:23
*** salv-orlando has joined #openstack-meeting-418:23
kevinbentonnot to prevent people from using it18:23
dougwigthat makes sense. at least as much as any of python's namespacing makes sense.  so a single underscore is the right answer for a library.18:23
kevinbentoni'm now regretting bringing it up :)18:24
kevinbentonnow that i'm thinking it through18:24
dougwiganything else before we wrap up for today?  HenryG, i'll ping you offline and setup a time to chat.18:24
HenryGI enjoyed learning about __method kevinbenton18:24
*** viveksa has joined #openstack-meeting-418:24
kevinbentonwe could add an @private decorator that inspects the call stack and ensures it comes from neutron-lib :)18:24
kevinbentonhowever, it will probably come at a terrible performance cost18:24
*** dmsimard has left #openstack-meeting-418:25
HenryGdougwig: ack18:25
kevinbentonone thing that is used by libraries at the module level is the __all__ magic var18:25
kevinbentonit defines what is importable by other modules18:25
dougwigkevinbenton: i mean, if people call and _internal routine and we break it, i won't lose any sleep.18:25
dougwig /and/an/18:25
kevinbentonso we can use that for module-level methods18:25
viveksaHi, I would like to know if there is a way to fetch Meatadata of VolumeSnapshot from DB18:25
kevinbentonviveksa: wrong channel. check out #openstack18:26
viveksathanks18:26
*** viveksa has left #openstack-meeting-418:26
dougwigok, let's wrap up this python tutorial session.  :)18:26
HenryGI wonder if they have an "effective oslo" guide?18:26
kevinbentonnot sure18:27
kevinbentonok18:27
kevinbentonanything else?18:27
*** dshakhray has quit IRC18:29
dougwigok, let's close this.18:29
dougwig#endmeeting18:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:29
openstackMeeting ended Wed Dec 16 18:29:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2015/networking_lib.2015-12-16-17.30.html18:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2015/networking_lib.2015-12-16-17.30.txt18:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2015/networking_lib.2015-12-16-17.30.log.html18:29
*** pc_m has joined #openstack-meeting-418:30
*** baoli has quit IRC18:32
*** ashtokolov has quit IRC18:33
*** briancurtin has quit IRC18:33
*** rbak has quit IRC18:33
*** rbak_ has joined #openstack-meeting-418:33
*** ashtokolov has joined #openstack-meeting-418:34
*** briancurtin has joined #openstack-meeting-418:34
*** yamamoto has quit IRC18:38
*** pc_m has left #openstack-meeting-418:38
*** bnemec has joined #openstack-meeting-418:38
*** yamamoto has joined #openstack-meeting-418:38
*** persia has joined #openstack-meeting-418:39
*** s3wong has joined #openstack-meeting-418:40
*** IlyaG has joined #openstack-meeting-418:42
*** zeih has joined #openstack-meeting-418:44
*** sridhar_ram has joined #openstack-meeting-418:48
*** yamamoto has quit IRC18:48
*** rbradfor has joined #openstack-meeting-418:48
*** zeih has quit IRC18:49
*** david-lyle_ has joined #openstack-meeting-418:49
*** david-lyle has quit IRC18:50
j^2raginbajin: you want to run the meeting?18:52
*** david-lyle_ is now known as david-lyle18:54
*** angdraug has joined #openstack-meeting-418:57
*** javeriak_ has joined #openstack-meeting-418:59
j^2#startmeeting operators_ops_tools_monitoring19:00
openstackMeeting started Wed Dec 16 19:00:54 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"19:00
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'19:00
j^2#chair raginbajin19:01
openstackCurrent chairs: j^2 raginbajin19:01
*** javeriak has quit IRC19:01
j^2hey everyone!19:01
*** jmckind has joined #openstack-meeting-419:01
serverascodehi19:01
j^2I'll give everyone 5ish? mins before starting19:01
j^2#link https://etherpad.openstack.org/p/osops-irc-meeting-2015121619:02
j^2that's the agenda for this meeting19:02
*** bnemec has quit IRC19:04
*** jmckind_ has quit IRC19:04
*** bpokorny_ has joined #openstack-meeting-419:05
j^2:D19:06
*** u_kozat has joined #openstack-meeting-419:06
j^2ok, cool19:06
j^2#topic previous business19:06
*** openstack changes topic to "previous business (Meeting topic: operators_ops_tools_monitoring)"19:06
j^2I had an action item to: j^2 to figure out how to use zuul to validate against the pep819:06
j^2    (python|bash) and rubocop linters19:06
j^2I renabled Christin Benets? gerrit is down so sorry for butchering your name, bashpep8 tests for tools-generic19:07
j^2it seems we need to get the second review in before they can reeable it19:07
j^2i pushed the last fix that mdorman noticed this morning so ideally we'll make progress today19:08
j^2any questions or thoughts on this?19:08
*** bpokorny has quit IRC19:09
serverascodenot from me19:09
j^2nice19:09
*** javeriak_ has quit IRC19:09
j^2mriedem was supposed to get us an old nova spec, i think he posted it to the mailing list, but i don't remember19:09
j^2and it seems he's not in the room so :'(19:09
rockygo/19:10
j^2xavpaice pushed up his tenant script so that's awesome19:10
*** bobh has quit IRC19:10
j^2it got pushed in pretty quickly which is awesome19:10
*** bnemec has joined #openstack-meeting-419:10
j^2i think that's all for previous business, any questions?19:10
*** u_kozat has quit IRC19:10
serverascodenopers19:10
j^2rockyg: :D19:11
j^2ok, cool, on to the new stuff19:11
j^2#topic Talk about releases for repos other than tools-contrib and tools-generic19:11
*** openstack changes topic to "Talk about releases for repos other than tools-contrib and tools-generic (Meeting topic: operators_ops_tools_monitoring)"19:11
j^2now this was an interesting request for EmilienM19:11
EmilienMo/19:11
j^2hi!19:11
EmilienMwe are building rpms in RDO19:12
EmilienMwithout the release but it would really be a nicetohave19:12
EmilienMmuch easier for maintainers19:12
j^2#link https://www.rdoproject.org/packaging/rdo-packaging.html19:12
*** seanmurphy has quit IRC19:12
EmilienMdo you have release management in your project?19:12
j^2#link https://wiki.openstack.org/wiki/Osops19:12
j^2the original agreement: We don't plan on having releases, but we do plan on collecting useful resources for anything ranging from Junior to Senior level administrators.19:13
j^2which may be thrown out now because of osops-coda, but that's a different discussion19:13
j^2There's a challange with this, the repos arn't designed to be rpm friendly19:14
rockygCould we use tags for indicating a specific version?19:14
j^2rockyg: what constitues as a version? that's they move really fast19:15
EmilienMI think you should release often19:15
EmilienMa tag19:15
EmilienMand release notes19:16
j^2and we've moved the https://github.com/openstack/osops-tools-monitoring/tree/master/monitoring-for-openstack in it's own directory now19:16
j^2that won't help with rpms right?19:16
rockygEven just a date tag could do the trick.  Or a version tag that is 0.1.0 if not reviewed, and 1.0 if reviewed and approved?19:16
*** david-lyle has quit IRC19:17
j^2there's another challenge here too, this is putting overhead on the project when we are still in it's infancy. i don't want to scare people away by this not being "painless and automated"19:17
rockygThe tag allows a specific set of files (the tagged build) to be checked out, then the package can be made from that19:17
j^2hence the reason to NOT put releases in19:17
j^2and unfortunatly we don't have quorum here, so we can't make a decision on this :(19:18
*** yamamoto has joined #openstack-meeting-419:18
*** yamamoto has quit IRC19:19
rockygwe could consider writing up a lightweight tagging process for version identification19:19
rockygCould just be a date tag19:19
j^2we need more voices on this, and this is something for Operators to make their life easier, I don't want to make decisions without more input19:19
rockygAgreed.  But we can make a proposal for review19:19
j^2rockyg: that seems reasonable; are there other projects with this?19:19
*** david-lyle has joined #openstack-meeting-419:20
rockygGood question.  I suspect not in OpenStack, but other OS projects do.  I've done some of this before.  I don't think I could write it up this week, but maybe before the first?19:20
j^2rockyg: that' would be awesome. just to see the...level of work and process will be useful to see what this would entail19:21
j^2and if we do it for one of our "core" repos, then we'd probably do it for them all19:21
j^2but that's just me spitballing19:22
rockyg++19:22
*** bpokorny has joined #openstack-meeting-419:22
j^2awesome, any other questions or thoughts? serverascode thoughts?19:22
rockygWe can get comments from ops, release and infra once we have the strawman up.19:22
*** bnemec has quit IRC19:22
j^2rockyg: agreed19:23
rockygcould you do a #action for me for this?  So it gets into the minutes19:23
j^2#action rockyg will write up a way to tag per day for the repos19:24
*** bpokorny_ has quit IRC19:24
*** david-lyle_ has joined #openstack-meeting-419:24
j^2next topic?19:24
*** david-lyle has quit IRC19:24
j^2#topic Talk about osops-coda19:25
*** openstack changes topic to "Talk about osops-coda (Meeting topic: operators_ops_tools_monitoring)"19:25
j^2we have a new project!19:25
j^2HPE has asked us to put coda in our namespace19:25
j^2this was a request at the toyko summit19:25
serverascodewhat's a coda?19:26
*** klindgren has joined #openstack-meeting-419:26
j^2wall of text incoming19:26
j^2Coda is a Horizon dashboard and panel (both share the name) that19:26
j^2facilitates resource clean up of a project once that project is no longer19:26
j^2needed (e.g. A customer cancels their account). It consists of a single19:26
j^2text entry box which allows you to search by project ID and will display19:26
j^2all resources, project info, and user info for the project. Upon pressing19:26
j^2the delete button the user is prompted each time for valid admin19:26
j^2credentials (annoying but a purposeful safe-guard) and will then walk the19:26
j^2list of resources deleting each one and will display the outcome of each19:26
j^2operation in a tabular format. This project started as a stand-alone19:26
j^2Django app inside HP and has been very valuable in operating our public19:26
j^2cloud. It was originally called Scrubber (because that's what it did) but19:26
j^2was renamed to Coda after being ported to Horizon and adapted for Keystone19:26
j^2instead of a proprietary Identity service. It is the intent of HP to open19:26
j^2source our entire suite of tools using a musical theme. Coda was chosen as19:26
j^2the name for this project as a coda in music is a passage that brings a19:26
j^2piece to an end. It is particularly apropos for this use because the19:26
j^2symbol for a coda resembles a cross hair.19:26
j^2i'll give everyone some time to read it19:27
*** dims has joined #openstack-meeting-419:27
*** salv-orlando has quit IRC19:27
*** seanmurphy has joined #openstack-meeting-419:27
serverascodeok, cool, yeah that sounds great19:28
j^2:D19:28
klindgrenJoin in the middle of this - iirc HP lightning talk during the tokyo confrence on this.  iirc it only works if the keystone tenant/project has not yet been deleted.19:28
j^2klindgren: yeah that sounds right19:28
j^2but it's coming to us to make it better :D19:28
j^2this will be posted to the ML when we get the code in the repo19:28
raginbajinSorry I'm late.. meeting ran long.19:28
j^2no worries19:29
klindgrenkk19:29
j^2but i wanted to give everyone a heads up here, it's a great win for us to grow the project more19:29
*** numans has quit IRC19:29
j^2any questions or thoughts?19:29
raginbajinI think that's cool.19:30
*** david-lyle_ has quit IRC19:30
rockygA project of this size will need real release process.  Scripts can be lighter weight, but not a full gui plus19:30
rockygAnd it's really cool.19:31
j^2rockyg: agreed it dove tails with the openstack-monitoring slurping too19:31
*** u_kozat has joined #openstack-meeting-419:31
j^2we only have a couple more topics19:32
j^2continue on?19:32
raginbajinThat project makes sense to have releases.19:32
j^2raginbajin: yep19:32
raginbajingood to move on from me19:33
rockyg++19:33
j^2raginbajin: still waiting to get it in our namespace then we can discuss at a macro scale on the release for them19:33
j^2#topic Notes4chairs19:34
*** openstack changes topic to "Notes4chairs (Meeting topic: operators_ops_tools_monitoring)"19:34
j^2I created a wiki page to help out chairs for this meeting19:34
j^2raginbajin and I have been running them but i want to open it up for more of the group19:34
j^2#link https://wiki.openstack.org/wiki/OSOpsNotes4Chairs19:34
*** vishwanathj_ has quit IRC19:35
j^2crap, that was supposed to be wiki/Osops/Notes4Chairs in our namespace. screwed that one up :'(19:35
j^2oh well19:35
*** bnemec has joined #openstack-meeting-419:35
j^2so I'd like to ask for volunteers for more chairs and i'll post to the ML asking for more19:35
j^2i think we can use it as a way to get more people involed19:35
j^2#action j^2 post to ML for more volunteer chairs for osops meeting19:36
*** bpokorny_ has joined #openstack-meeting-419:36
rockyg++19:36
j^2any thoughts/questions?19:36
rockygwe might actually get more devs, too, with the weekly announcement on the ml19:36
*** banix has joined #openstack-meeting-419:37
*** bpokorn__ has joined #openstack-meeting-419:37
j^2rockyg: can you explain that?19:37
j^2i'm missing something19:37
rockygby sending out weekly meeting announcement on ops ml, it might attract some devs' attention and they would participate19:38
j^2ohhh yeah sorry, i thought there was another announcement i was missing :P19:38
rockygnp19:39
j^2serverascode: any thoughts?19:39
*** bpokorny has quit IRC19:39
j^2otherwise going to the last topic19:39
serverascodenope that sounds good to me19:39
j^2cool19:39
j^2#topic Waiting on so we can add the bashte jobs to tools generic19:39
*** openstack changes topic to "Waiting on so we can add the bashte jobs to tools generic (Meeting topic: operators_ops_tools_monitoring)"19:39
*** MarkAtwood has quit IRC19:40
j^2ok, so when gerrit comes up we are one step away from getting tools-genirc with the bashte job working19:40
j^2#link https://review.openstack.org/#/c/229031/ -> https://review.openstack.org/#/c/229043/19:40
j^2we need those both to pass then we have a gate on tools-generic19:40
j^2this is extremely important19:40
*** bpokorny_ has quit IRC19:40
j^2especially after how, i mentioned our workflow in superuser, thanks to everyone that helped edit the topic19:41
*** marek_ has quit IRC19:41
j^2#link http://superuser.openstack.org/articles/check-out-this-tool-library-for-openstack-operators19:41
j^2but with gerrit down, we are stuck :(19:41
j^2any questions or thoughts?19:42
serverascodeis bashte a tool? I can't find anything about it19:42
j^2i may be butchering the name19:43
rockygmaybe bashate?19:43
j^2http://git.openstack.org/cgit/openstack-dev/bashate/tree/README.rst19:43
serverascodeah ok19:43
j^2it's the "sane" default we agree for bash19:44
j^2#link http://git.openstack.org/cgit/openstack-dev/bashate/tree/README.rst19:44
j^2cool anything else on this topic?19:45
j^2we are at about 15 mins, which i'd like to open to general discussion19:45
serverascodenothing else from me19:46
j^2#topic Open Floor19:46
*** openstack changes topic to "Open Floor (Meeting topic: operators_ops_tools_monitoring)"19:46
j^2klindgren, serverascode, raginbajin, rockyg :D floor is open19:47
*** vhoward has joined #openstack-meeting-419:48
klindgrenI dont think I have everything - due to the holidays and trying to get other work done before EOY19:48
raginbajinI don't have anything19:48
klindgrens/everything/anything19:48
*** jmckind_ has joined #openstack-meeting-419:48
*** david-lyle has joined #openstack-meeting-419:48
serverascodenothing from me either19:49
rockygme too.  too on my plate  ;-)19:49
j^2Sooo.. Star Wars? ;)19:49
rockygMonday.  Freebie tix from netapp19:49
j^2nice19:49
rockygThat's if I've recovered enough from sinus surgery Friday19:50
j^2:D19:50
j^2awesome, well if we're good i'll close the meeting and give everyone 10 mins back19:50
*** jmckind has quit IRC19:50
rockyg++19:50
rockygEverybody have some good holidays19:51
j^2you too rockyg19:51
j^2#endmeeting19:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:51
openstackMeeting ended Wed Dec 16 19:51:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-12-16-19.00.html19:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-12-16-19.00.txt19:51
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-12-16-19.00.log.html19:51
*** bharathm has quit IRC19:51
*** dshakhray has joined #openstack-meeting-419:56
*** banix has quit IRC19:57
*** piet has quit IRC19:57
*** dslev has quit IRC19:58
*** IlyaG has quit IRC19:58
*** sdake has joined #openstack-meeting-419:59
rbradfordid I have the schedule correct for the log working group IRC meeting?20:05
rockygit's an hour later, I think20:07
rockygBut, give me about fifteen and meet me on the operator's channel?20:07
rbradforrockyg, thanks, I thought it was 2000 UTC20:07
rbradforok20:07
*** dtardivel has quit IRC20:07
*** piet has joined #openstack-meeting-420:11
*** sdake_ has joined #openstack-meeting-420:13
*** MarkAtwood has joined #openstack-meeting-420:13
*** sdake has quit IRC20:15
*** avarner has quit IRC20:17
*** dims has quit IRC20:18
*** MarkAtwood has quit IRC20:18
*** dims has joined #openstack-meeting-420:19
*** yamamoto has joined #openstack-meeting-420:19
*** bpokorn__ has quit IRC20:21
*** bpokorny has joined #openstack-meeting-420:22
*** yamamoto has quit IRC20:25
*** bharathm has joined #openstack-meeting-420:38
*** u_kozat has quit IRC20:38
*** jmckind has joined #openstack-meeting-420:41
*** baoli has joined #openstack-meeting-420:41
*** banix has joined #openstack-meeting-420:44
*** jmckind_ has quit IRC20:44
*** jmckind_ has joined #openstack-meeting-420:48
*** jmckind has quit IRC20:50
*** baoli has quit IRC20:51
*** baoli has joined #openstack-meeting-420:52
*** bpokorny_ has joined #openstack-meeting-420:55
*** banix has quit IRC20:57
*** bpokorny has quit IRC20:59
-openstackstatus- NOTICE: Gerrit has been upgraded to 2.11. Please report any issues in #openstack-infra as soon as possible.21:00
*** bnemec has quit IRC21:01
*** bnemec has joined #openstack-meeting-421:01
*** leecalcote has joined #openstack-meeting-421:03
*** baoli has quit IRC21:03
*** baoli has joined #openstack-meeting-421:04
*** leecalcote has quit IRC21:05
*** banix has joined #openstack-meeting-421:06
*** bnemec has quit IRC21:13
*** seanmurphy has quit IRC21:14
*** ajmiller has quit IRC21:14
*** ajmiller has joined #openstack-meeting-421:14
*** baoli has quit IRC21:15
*** baoli has joined #openstack-meeting-421:16
*** julim has quit IRC21:18
*** vhoward has quit IRC21:25
*** zeih has joined #openstack-meeting-421:27
*** baoli has quit IRC21:27
*** bnemec has joined #openstack-meeting-421:27
*** baoli has joined #openstack-meeting-421:27
*** zeih has quit IRC21:32
*** leecalcote has joined #openstack-meeting-421:32
*** leecalcote has quit IRC21:32
*** u_kozat has joined #openstack-meeting-421:34
*** bpokorny_ has quit IRC21:35
*** bpokorny has joined #openstack-meeting-421:35
*** prashantD has joined #openstack-meeting-421:38
*** baoli has quit IRC21:39
*** baoli has joined #openstack-meeting-421:39
*** dronshaw has quit IRC21:39
*** banix has quit IRC21:42
*** baoli has quit IRC21:50
*** baoli has joined #openstack-meeting-421:50
*** daneyon_ has joined #openstack-meeting-421:54
*** dshakhray has quit IRC21:55
*** daneyon_ has quit IRC21:56
*** daneyon_ has joined #openstack-meeting-421:56
*** daneyon has quit IRC21:57
*** MarkAtwood has joined #openstack-meeting-421:58
*** baoli has quit IRC22:05
*** baoli has joined #openstack-meeting-422:06
*** baoli has quit IRC22:08
*** baoli has joined #openstack-meeting-422:09
*** sdake_ has quit IRC22:09
*** xingchao has joined #openstack-meeting-422:16
*** sdake has joined #openstack-meeting-422:17
*** baoli has quit IRC22:18
*** baoli has joined #openstack-meeting-422:19
*** xingchao has quit IRC22:21
*** IlyaG has joined #openstack-meeting-422:23
*** baoli has quit IRC22:24
*** IlyaG has quit IRC22:28
*** IlyaG has joined #openstack-meeting-422:31
*** piet has quit IRC22:34
*** sridhar_ram1 has joined #openstack-meeting-422:36
*** sridhar_ram1 has quit IRC22:37
*** sridhar_ram has quit IRC22:37
*** baoli has joined #openstack-meeting-422:39
*** piet has joined #openstack-meeting-422:39
*** sdake has quit IRC22:41
*** sdake has joined #openstack-meeting-422:41
*** baoli_ has joined #openstack-meeting-422:43
*** sdake has quit IRC22:44
*** baoli has quit IRC22:45
*** rockyg has quit IRC22:48
*** baoli_ has quit IRC22:52
*** baoli has joined #openstack-meeting-422:52
*** JRobinson__ has joined #openstack-meeting-422:52
*** piet has quit IRC22:58
*** neelashah has quit IRC22:58
*** dims has quit IRC23:01
*** sridhar_ram has joined #openstack-meeting-423:02
*** baoli has quit IRC23:03
*** baoli has joined #openstack-meeting-423:04
*** woodard has quit IRC23:11
*** klamath has quit IRC23:11
*** baoli has quit IRC23:15
*** baoli has joined #openstack-meeting-423:16
*** xingchao has joined #openstack-meeting-423:17
*** sigmavirus24 is now known as sigmavirus24_awa23:20
*** xingchao has quit IRC23:21
JRobinson__Good morning all, the User Guide Team meeting is set to start in about 5 minutes.23:24
*** dims has joined #openstack-meeting-423:24
*** baoli has quit IRC23:27
*** baoli has joined #openstack-meeting-423:28
*** sdake has joined #openstack-meeting-423:30
*** sdake has quit IRC23:30
*** sdake_ has joined #openstack-meeting-423:30
*** blahRus has quit IRC23:31
JRobinson__#startmeeting docuserguides23:31
openstackMeeting started Wed Dec 16 23:31:33 2015 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:31
*** openstack changes topic to " (Meeting topic: docuserguides)"23:31
openstackThe meeting name has been set to 'docuserguides'23:31
JRobinson__Morning or Evening All, depending on your location23:31
JRobinson__We're going to get the User Guide Meeting started23:32
*** sdake_ has quit IRC23:32
JRobinson__Who else is available today ?23:32
*** banix has joined #openstack-meeting-423:35
*** u_kozat has quit IRC23:36
JRobinson__The agenda is not lengthy,23:37
JRobinson__so to run through these items:23:37
JRobinson__#info User Guide Tasks are open for patching by contributors23:37
JRobinson__#link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#The_List_of_Tasks23:38
JRobinson__#info Assign yourself a task and investigate the chapter.23:38
JRobinson__The final goal is to reorganize the admin-user and cloud-admin books into one document with a more task based focus23:39
JRobinson__so be on the lookout for places to work the information of the admin-user guide into the cloud-admin content23:39
JRobinson__Next item:23:39
*** baoli has quit IRC23:39
JRobinson__#info Collaboration with Trove and Murano services23:39
*** baoli has joined #openstack-meeting-423:40
JRobinson__I have had some contact with the docs liaisons of these services. The goal here is to incorporate new content into the administrator guide23:40
JRobinson__Anyone able to continue working with these teams - collaboration is welcome here.23:41
JRobinson__#info  Anyone able to help continue working with these teams - collaboration is welcome here.23:41
JRobinson__That's all for User guides.23:42
JRobinson__Just to review:23:42
JRobinson__#topic Work item list is available23:42
*** openstack changes topic to "Work item list is available (Meeting topic: docuserguides)"23:42
JRobinson__ #link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#The_List_of_Tasks23:43
JRobinson__#topic Collaborate with Trove, Murano, Sahara, and other services if needed23:43
*** openstack changes topic to "Collaborate with Trove, Murano, Sahara, and other services if needed (Meeting topic: docuserguides)"23:43
*** uck has joined #openstack-meeting-423:43
JRobinson__#info  Anyone able to help continue working with these teams - collaboration is welcome here.23:43
JRobinson__#topic open discussion23:43
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"23:44
JRobinson__Any other points from anyone reading ?23:44
JRobinson__Okay, time to close this up then.23:45
JRobinson__#endmeeting23:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:45
openstackMeeting ended Wed Dec 16 23:45:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-12-16-23.31.html23:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-12-16-23.31.txt23:45
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-12-16-23.31.log.html23:45
*** egon has joined #openstack-meeting-423:48
*** baoli has quit IRC23:51
*** baoli has joined #openstack-meeting-423:52

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