Wednesday, 2016-06-01

*** tonytan4ever has quit IRC00:04
*** prithiv has quit IRC00:05
*** emagana has quit IRC00:06
*** zhurong has joined #openstack-meeting-400:07
*** thorst has joined #openstack-meeting-400:07
*** emagana has joined #openstack-meeting-400:08
*** emagana has quit IRC00:12
*** dims has quit IRC00:14
*** uck_ has quit IRC00:14
*** sacharya has quit IRC00:15
*** dims has joined #openstack-meeting-400:19
*** omnipresent has quit IRC00:21
*** zenoway has joined #openstack-meeting-400:22
*** tonytan4ever has joined #openstack-meeting-400:23
*** zenoway has quit IRC00:26
*** sdake_ has joined #openstack-meeting-400:29
*** sdake has quit IRC00:30
*** bpokorny has quit IRC00:35
*** pvaneck has quit IRC00:36
*** gangil has left #openstack-meeting-400:36
*** tonytan4ever has quit IRC00:39
*** kylek3h has joined #openstack-meeting-400:41
*** dcwangmit01_ has joined #openstack-meeting-400:48
*** piet has joined #openstack-meeting-400:49
*** kylek3h has quit IRC00:49
*** dcwangmit01 has quit IRC00:50
*** spzala has quit IRC00:51
*** sdake has joined #openstack-meeting-400:56
*** vikasc has quit IRC00:57
*** vikasc has joined #openstack-meeting-400:58
*** sdake_ has quit IRC00:59
*** piet has quit IRC01:00
*** sdake has quit IRC01:02
*** piet has joined #openstack-meeting-401:03
*** fitoduarte has quit IRC01:07
*** xingchao has joined #openstack-meeting-401:09
*** vikasc has quit IRC01:13
*** sacharya has joined #openstack-meeting-401:15
*** klamath has quit IRC01:15
*** zhurong has quit IRC01:16
*** klamath has joined #openstack-meeting-401:16
*** zhurong has joined #openstack-meeting-401:17
*** piet has quit IRC01:17
*** yamamoto has joined #openstack-meeting-401:17
*** sacharya has quit IRC01:21
*** yamahata has joined #openstack-meeting-401:23
*** julim has joined #openstack-meeting-401:24
*** _sarob has quit IRC01:30
*** julim has quit IRC01:32
*** kylek3h has joined #openstack-meeting-401:33
*** bobh has quit IRC01:34
*** itisha has quit IRC01:40
*** kylek3h has quit IRC01:40
*** kylek3h has joined #openstack-meeting-401:40
*** sdake has joined #openstack-meeting-401:41
*** sdake has quit IRC01:43
*** sdake has joined #openstack-meeting-401:47
*** sdake_ has joined #openstack-meeting-401:48
*** kylek3h has quit IRC01:49
*** klamath has quit IRC01:50
*** klamath has joined #openstack-meeting-401:50
*** sdake has quit IRC01:51
*** klamath has quit IRC01:53
*** klamath has joined #openstack-meeting-401:54
*** s3wong has quit IRC01:55
*** tfukushima has joined #openstack-meeting-401:58
*** kebray has quit IRC02:00
*** unicell has quit IRC02:02
*** yamamoto has quit IRC02:03
*** kebray has joined #openstack-meeting-402:05
*** zenoway has joined #openstack-meeting-402:08
*** julim has joined #openstack-meeting-402:10
*** zenoway has quit IRC02:12
*** hogepodge has quit IRC02:13
*** bpokorny has joined #openstack-meeting-402:16
*** sacharya has joined #openstack-meeting-402:16
*** hogepodge has joined #openstack-meeting-402:17
*** thorst has quit IRC02:20
*** thorst has joined #openstack-meeting-402:21
*** hogepodge has quit IRC02:21
*** vishnoianil has quit IRC02:25
*** bpokorny_ has joined #openstack-meeting-402:29
*** thorst has quit IRC02:29
*** kylek3h has joined #openstack-meeting-402:30
*** bpokorny has quit IRC02:32
*** antongri_ has joined #openstack-meeting-402:32
*** bpokorny_ has quit IRC02:34
*** thorst has joined #openstack-meeting-402:35
*** antongribok has quit IRC02:36
*** kylek3h has quit IRC02:37
*** thorst has quit IRC02:37
*** yamahata has quit IRC02:43
*** iyamahat has quit IRC02:43
*** cgoncalves has quit IRC02:52
*** yamamoto has joined #openstack-meeting-402:54
*** yamamoto has quit IRC02:54
*** JRobinson__ has quit IRC03:06
*** antongri_ has quit IRC03:10
*** sarob has joined #openstack-meeting-403:16
*** lcastell has quit IRC03:18
*** iyamahat has joined #openstack-meeting-403:21
*** piet has joined #openstack-meeting-403:22
*** kylek3h has joined #openstack-meeting-403:26
*** kylek3h has quit IRC03:31
*** piet has quit IRC03:36
*** thorst has joined #openstack-meeting-403:38
*** lcastell has joined #openstack-meeting-403:39
*** yamamoto has joined #openstack-meeting-403:42
*** jankihc has joined #openstack-meeting-403:42
*** zenoway has joined #openstack-meeting-403:44
*** iyamahat has quit IRC03:45
*** thorst has quit IRC03:46
*** dave-mccowan has quit IRC03:48
*** zenoway has quit IRC03:49
*** padkrish has joined #openstack-meeting-404:03
*** vikasc has joined #openstack-meeting-404:09
*** antongribok has joined #openstack-meeting-404:11
*** iyamahat has joined #openstack-meeting-404:14
*** jankihc has quit IRC04:16
*** jankihc has joined #openstack-meeting-404:17
*** kylek3h has joined #openstack-meeting-404:18
*** sarob has quit IRC04:18
*** yamahata has joined #openstack-meeting-404:19
*** zenoway has joined #openstack-meeting-404:20
*** david-lyle has quit IRC04:21
*** zenoway has quit IRC04:25
*** kylek3h has quit IRC04:25
*** piet has joined #openstack-meeting-404:29
*** s3wong has joined #openstack-meeting-404:31
*** padkrish_ has joined #openstack-meeting-404:36
*** padkris__ has joined #openstack-meeting-404:38
*** padkrish has quit IRC04:39
*** padkrish_ has quit IRC04:41
*** armax has quit IRC04:42
*** thorst has joined #openstack-meeting-404:44
*** piet has quit IRC04:45
*** vikasc has quit IRC04:46
*** vikasc has joined #openstack-meeting-404:47
*** padkrish has joined #openstack-meeting-404:48
*** padkris__ has quit IRC04:50
*** thorst has quit IRC04:51
*** iyamahat has quit IRC04:52
*** tfukushima has quit IRC04:53
*** zenoway has joined #openstack-meeting-404:55
*** jankihc has quit IRC04:57
*** anilvenkata has joined #openstack-meeting-404:57
*** padkrish_ has joined #openstack-meeting-404:59
*** zenoway has quit IRC05:00
*** s3wong has quit IRC05:02
*** emagana has joined #openstack-meeting-405:02
*** padkrish has quit IRC05:03
*** GB21 has joined #openstack-meeting-405:04
*** jankihc has joined #openstack-meeting-405:07
*** padkrish has joined #openstack-meeting-405:10
*** iyamahat has joined #openstack-meeting-405:10
*** padkrish_ has quit IRC05:12
*** kylek3h has joined #openstack-meeting-405:13
*** jankihc has quit IRC05:14
*** irenab has joined #openstack-meeting-405:16
*** fitoduarte has joined #openstack-meeting-405:18
*** kylek3h has quit IRC05:20
*** padkrish_ has joined #openstack-meeting-405:21
*** padkrish has quit IRC05:24
*** hdaniel has joined #openstack-meeting-405:26
*** mohankumar has quit IRC05:28
*** fitoduarte has quit IRC05:29
*** fitoduarte has joined #openstack-meeting-405:30
*** JRobinson__ has joined #openstack-meeting-405:30
*** mohankumar has joined #openstack-meeting-405:31
*** padkrish_ has quit IRC05:32
*** javeriak has joined #openstack-meeting-405:44
*** thorst has joined #openstack-meeting-405:49
*** nkrinner has joined #openstack-meeting-405:49
*** sdake has joined #openstack-meeting-405:52
*** sdake_ has quit IRC05:55
*** thorst has quit IRC05:57
*** nmadhok has quit IRC05:59
*** lcastell has quit IRC05:59
*** jschwarz has joined #openstack-meeting-406:00
*** anilvenkata has quit IRC06:00
*** coolsvap_ has joined #openstack-meeting-406:02
*** unicell has joined #openstack-meeting-406:03
*** paul-carlton2 has joined #openstack-meeting-406:05
*** yamahata has quit IRC06:05
*** kylek3h has joined #openstack-meeting-406:07
*** cgoncalves has joined #openstack-meeting-406:10
*** sdake has quit IRC06:15
*** kylek3h has quit IRC06:15
*** belmoreira has joined #openstack-meeting-406:17
*** lcastell has joined #openstack-meeting-406:17
*** vishwanathj has joined #openstack-meeting-406:19
*** hdaniel has quit IRC06:19
*** zeih has joined #openstack-meeting-406:19
*** unicell1 has joined #openstack-meeting-406:20
*** unicell has quit IRC06:20
*** numans has joined #openstack-meeting-406:21
*** haleyb has quit IRC06:23
*** vishwanathj has quit IRC06:23
*** markvoelker has quit IRC06:24
*** vishwanathj has joined #openstack-meeting-406:24
*** vishwana_ has joined #openstack-meeting-406:25
*** vishwanathj has quit IRC06:29
*** vishwana_ is now known as vishwanathj06:30
*** sarob has joined #openstack-meeting-406:30
*** hogepodge has joined #openstack-meeting-406:31
*** ihrachys has joined #openstack-meeting-406:34
*** sarob has quit IRC06:36
*** emagana has quit IRC06:36
*** dshakhray has joined #openstack-meeting-406:44
*** vishwanathj has quit IRC06:45
*** vishwanathj has joined #openstack-meeting-406:47
*** lcastell has quit IRC06:50
*** haleyb has joined #openstack-meeting-406:50
*** tfukushima has joined #openstack-meeting-406:52
*** zenoway has joined #openstack-meeting-406:53
*** zenoway has quit IRC06:58
*** vishwana_ has joined #openstack-meeting-407:02
*** lcastell has joined #openstack-meeting-407:02
*** vishwanathj has quit IRC07:03
*** kylek3h has joined #openstack-meeting-407:04
*** hdaniel has joined #openstack-meeting-407:07
*** javeriak has quit IRC07:08
*** kylek3h has quit IRC07:09
*** javeriak has joined #openstack-meeting-407:12
*** thorst has joined #openstack-meeting-407:14
*** zenoway has joined #openstack-meeting-407:14
*** jichen has joined #openstack-meeting-407:15
*** thorst has quit IRC07:22
*** bryan_att has joined #openstack-meeting-407:25
*** amotoki has joined #openstack-meeting-407:26
*** vishwana_ has quit IRC07:26
*** danpawlik has joined #openstack-meeting-407:26
*** pcaruana has joined #openstack-meeting-407:26
*** matrohon has joined #openstack-meeting-407:29
*** fwdit has joined #openstack-meeting-407:33
*** iyamahat has quit IRC07:43
*** cwolferh has joined #openstack-meeting-407:44
*** dshakhray has quit IRC07:48
*** andymaier has joined #openstack-meeting-407:52
*** Niham has joined #openstack-meeting-407:57
*** yamahata has joined #openstack-meeting-407:57
*** ifat_afek has joined #openstack-meeting-407:57
*** omnipresent has joined #openstack-meeting-407:58
*** zenoway has quit IRC08:00
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Jun  1 08:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi everyone :-)08:00
*** alexey_weyl has joined #openstack-meeting-408:01
alexey_weylHelllo08:01
alexey_weylwhoooooooooooooooooo08:01
*** Wendy_ has joined #openstack-meeting-408:01
*** eyalb has joined #openstack-meeting-408:01
*** ayah has joined #openstack-meeting-408:02
eyalbHi08:02
ayahhi08:02
*** JRobinson__ has quit IRC08:02
*** lhartal has joined #openstack-meeting-408:03
*** elisha_r has joined #openstack-meeting-408:04
elisha_rhi08:04
lhartalhi all :)08:04
*** zeih_ has joined #openstack-meeting-408:04
ifat_afekCongratulations, Vitrage is now an official OpenStack project!!!08:04
ifat_afek#link http://governance.openstack.org/reference/projects/index.html08:05
alexey_weylwhoooooooooooooooo08:05
*** prithiv has joined #openstack-meeting-408:05
ifat_afek#link http://governance.openstack.org/reference/projects/vitrage.html08:05
elisha_rYessssssssss!!!!08:05
*** doffek has joined #openstack-meeting-408:05
alexey_weylfun fun fun08:05
doffekParty !!!!!!!08:05
ayahgreat news!08:05
eyalb+208:05
alexey_weyl+408:05
*** coolsvap_ has quit IRC08:05
lhartalsuch a good news!!!!!08:05
*** nadav_yakar has joined #openstack-meeting-408:06
lhartalgood for us :)08:06
ifat_afekWe should be really proud of ourselves! thanks everyone who contriburted to this project08:06
ifat_afekAccepting Vitrage into the big tent was discussed in yesterday's TC meeting.08:06
doffekAnd thank you Ifat !!!!08:06
ifat_afek:-)08:06
ifat_afekThe comments we had to our proposal:08:06
alexey_weylWe have made it in less then 7 months :)08:06
ifat_afek* They wanted to call it "RCA service" instead of "RCA Engine". I fixed it.08:07
ifat_afek* They were bothered about multi tenancy issues. Will "regular" users see the entire topology in a public cloud. I said it is in our Newton road map.08:07
ifat_afek* Someone asked about the relation between Vitrage and Telemetry project. I explained that we already have aodh datasource, are working on the aodh notifier together with Aodh team08:07
*** raddaoui has quit IRC08:07
ifat_afekMeeting minutes:08:07
ifat_afek#link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-31-20.02.html08:07
ifat_afekMeeting log:08:08
ifat_afek#link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-31-20.02.log.html08:08
ifat_afekAlso note that our stackalytics has moved to "Official Vitrage":08:08
ifat_afek#link http://stackalytics.com/?project_type=openstack&metric=marks&module=vitrage-group08:08
*** paul-carlton2 has quit IRC08:08
ifat_afekSo now let's start :-)08:09
ifat_afekOur agenda today:08:09
ifat_afek* Status and Updates08:09
doffekparty ?08:09
ifat_afek* Open Discussion08:09
ifat_afekdoffek: sure!08:09
elisha_ris there an IRC icon for beer?08:09
ifat_afek#topic Party :-)08:09
*** openstack changes topic to "Party :-) (Meeting topic: vitrage)"08:09
*** ihrachys has quit IRC08:09
elisha_ris there an IRC icon for beer?08:10
alexey_weylWe have done it!!!!!!!!!!!! :)08:10
*** ihrachys has joined #openstack-meeting-408:11
ifat_afek#topic Status and Updates08:11
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:11
ifat_afekIn the last two meetings we worked on Newton planning. I don't feel there is a need to continue these discussions, but if anyone wishes to discuss it, please do08:11
*** alexchadin has joined #openstack-meeting-408:11
ifat_afek#link https://etherpad.openstack.org/p/vitrage-newton-planning08:11
ifat_afekI'm working on supporting vitrage in liberty08:11
ifat_afekvitrage processes and vitrage dashboard are working (with two minor fixes). Nova and cinder datasources are working, including notifications. I didn't check neutron and nagios yet. Aodh is not working at the moment.08:12
ifat_afekWho else wants to update?08:12
elisha_rI will08:12
elisha_ryesterday I pushed the support for overlapping templates into gerrit08:12
elisha_rI'll add documentation today, and close the blueprint08:13
elisha_rI've added unit tests to extensively tests this feature, but please everyone be on the lookout for strange RCA bugs that might appear, and raise a flag...08:13
elisha_rmoving on08:14
ifat_afekelisha_r: cool08:14
elisha_rwe are preparing for a joint vitrage-doctor booth in the upcoming OPNFV summit later this month (June)08:14
elisha_rif all goes as planned, we should be able to show vitrage integrating, to some basic degree, with zabbix08:15
elisha_rthat's it from me08:15
*** yamahata has quit IRC08:15
alexey_weylI will update about zabbix08:15
*** yamahata has joined #openstack-meeting-408:16
alexey_weylI have succeeded to install zubbix using puppet, so we will have a script that will be able to install zabbix soon.08:16
alexey_weylor a documentation about how to do it in a few steps.08:16
alexey_weylIn addition I have started to work on the Zabbix datasource08:17
alexey_weylI have found a Python API for zabbix08:17
alexey_weylWe are planning to have zabbix datasource till the end of ext week hopefully, because we need for the Doctor summit08:18
alexey_weylthat's it :)08:18
ifat_afekalexey_weyl: that's great08:18
eyalbI will update08:18
eyalbI finished writing all spec file for rpm packaging08:19
eyalbneed to check them and then I will submit them to RDO08:19
*** ihrachys has quit IRC08:19
*** ihrachys has joined #openstack-meeting-408:20
eyalbalso I wrote all puppet scripts and I am pushing them to openstack puppet-vitrage08:20
eyalbthats all08:20
*** thorst has joined #openstack-meeting-408:20
lhartalI  want to update to08:20
lhartalIn the last week I working on the template validation API08:21
doffekFollowing @eyalb work, I'm working on Vitrage installation as part of the tripleO framework.08:21
lhartalI will push today the first stage of it which includes support for CLI/API for validate one template by given its path.08:21
doffekOops, sorry @lhartal, I waited for Eyal to finish...08:22
*** dtardivel has joined #openstack-meeting-408:22
lhartalcurrently we support only syntax validation through API/CLI08:22
lhartaltasks for  next week:08:22
lhartal1. templates validation (more then one template to validate through API/CLI)08:23
lhartal2. adding support for contennt validation08:23
*** paul-carlton2 has joined #openstack-meeting-408:23
lhartal3. Adding status code for validation08:23
lhartal4. I whish to start working on the template list API08:24
lhartalthats all08:24
ifat_afeklhartal: cool, thanks08:24
ifat_afekand thanks doffek too :-)08:24
ifat_afekanyone else has updates?08:24
ifat_afekmoving on08:25
ifat_afek#topic Open Discussion08:25
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:26
ifat_afekanything you would like to discuss?08:26
*** thorst has quit IRC08:27
ifat_afekso I guess we are done. goodbye everyone :-)08:28
lhartalbye bye08:28
alexey_weylbye bye08:28
elisha_rbye08:28
ayahbye08:28
ifat_afek#endmeeting08:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:28
openstackMeeting ended Wed Jun  1 08:28:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-01-08.00.html08:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-01-08.00.txt08:28
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-01-08.00.log.html08:28
*** Wendy_ has quit IRC08:29
*** alexey_weyl has quit IRC08:31
*** doffek has left #openstack-meeting-408:31
*** ihrachys has quit IRC08:32
*** markvoelker has joined #openstack-meeting-408:37
*** lhartal has quit IRC08:40
*** iberezovskiy_afk is now known as iberezovskiy08:41
*** markvoelker has quit IRC08:42
*** lcastell has quit IRC08:42
*** jed56 has joined #openstack-meeting-408:45
*** emagana has joined #openstack-meeting-408:48
yuli_si think there is a bug in default sg rules08:51
*** emagana has quit IRC08:53
*** eyalb has quit IRC08:55
*** lcastell has joined #openstack-meeting-408:57
*** sacharya has quit IRC08:57
*** tfukushima has quit IRC09:04
*** tfukushima has joined #openstack-meeting-409:05
*** GB21 has quit IRC09:06
*** tfukushima has quit IRC09:07
*** yamahata has quit IRC09:08
*** sambetts|afk is now known as sambetts09:09
*** pas-ha has joined #openstack-meeting-409:15
*** pas-ha has left #openstack-meeting-409:18
*** vishwanathj has joined #openstack-meeting-409:24
*** thorst has joined #openstack-meeting-409:25
*** Niham has quit IRC09:25
*** ifat_afek has quit IRC09:25
*** Niham has joined #openstack-meeting-409:25
*** Niham has quit IRC09:26
*** Niham has joined #openstack-meeting-409:27
*** Niham has quit IRC09:28
*** Niham has joined #openstack-meeting-409:28
*** vikasc has quit IRC09:29
*** fitoduarte has quit IRC09:29
*** Niham has quit IRC09:29
*** fitoduarte has joined #openstack-meeting-409:30
*** Niham has joined #openstack-meeting-409:30
*** thorst has quit IRC09:32
*** paul-carlton2 has quit IRC09:32
*** vikasc has joined #openstack-meeting-409:42
*** matrohon has quit IRC09:47
*** kylek3h has joined #openstack-meeting-409:47
*** Jeffrey4l_ has quit IRC09:48
*** kylek3h has quit IRC09:53
*** majklk has quit IRC09:54
*** majklk has joined #openstack-meeting-409:55
*** julim has quit IRC09:55
*** vikasc has quit IRC09:56
*** sacharya has joined #openstack-meeting-409:57
*** ihrachys has joined #openstack-meeting-409:58
*** belmoreira has quit IRC10:00
*** majklk_ has joined #openstack-meeting-410:01
*** Niham has quit IRC10:01
*** Niham has joined #openstack-meeting-410:01
*** sacharya has quit IRC10:03
*** vishwanathj has quit IRC10:03
*** julim has joined #openstack-meeting-410:03
*** majklk has quit IRC10:04
*** _degorenko|afk is now known as degorenko10:06
*** tfukushima has joined #openstack-meeting-410:07
*** dshakhray has joined #openstack-meeting-410:08
*** pbourke_ has quit IRC10:09
*** pbourke_ has joined #openstack-meeting-410:10
*** Niham has quit IRC10:11
*** tfukushima has quit IRC10:12
*** alexchad_ has joined #openstack-meeting-410:23
*** alexchadin has quit IRC10:25
*** thorst has joined #openstack-meeting-410:29
*** thorst has quit IRC10:38
*** tfukushima has joined #openstack-meeting-410:38
*** nadav_yakar has quit IRC10:40
*** alexchad_ has quit IRC10:40
*** zhurong has quit IRC10:40
*** alexchadin has joined #openstack-meeting-410:40
*** anilvenkata has joined #openstack-meeting-410:40
*** kylek3h has joined #openstack-meeting-410:41
*** hvprash has joined #openstack-meeting-410:42
*** hvprash has quit IRC10:42
*** tfukushima has quit IRC10:43
*** hvprash has joined #openstack-meeting-410:43
*** irenab has quit IRC10:43
*** rtheis has joined #openstack-meeting-410:45
*** sdague has joined #openstack-meeting-410:47
*** hvprash has quit IRC10:47
*** kylek3h has quit IRC10:48
*** zeih_ has quit IRC10:49
*** prithiv has quit IRC10:50
*** vishwanathj has joined #openstack-meeting-410:51
*** yamamoto has quit IRC10:55
*** vishwanathj has quit IRC10:56
*** Niham has joined #openstack-meeting-410:56
*** Niham has quit IRC10:57
*** Niham has joined #openstack-meeting-410:58
*** Duan has quit IRC10:58
*** Niham has quit IRC10:59
*** Niham has joined #openstack-meeting-410:59
*** Niham has quit IRC11:00
*** Niham has joined #openstack-meeting-411:01
*** Niham has quit IRC11:01
*** prithiv has joined #openstack-meeting-411:02
*** Niham has joined #openstack-meeting-411:02
*** elisha_r has quit IRC11:12
*** ifat_afek has joined #openstack-meeting-411:14
*** javeriak has quit IRC11:15
*** javeriak has joined #openstack-meeting-411:15
*** alexchadin has quit IRC11:16
*** vishwanathj has joined #openstack-meeting-411:22
*** dshakhray has quit IRC11:24
*** dave-mccowan has joined #openstack-meeting-411:27
*** vishwanathj has quit IRC11:30
*** ifat_afek has left #openstack-meeting-411:31
*** vishwanathj has joined #openstack-meeting-411:31
*** kylek3h has joined #openstack-meeting-411:34
*** vishwanathj has quit IRC11:35
*** fwdit has quit IRC11:37
*** tfukushima has joined #openstack-meeting-411:39
*** irenab has joined #openstack-meeting-411:41
*** thorst has joined #openstack-meeting-411:41
*** kylek3h has quit IRC11:42
*** tojuvone has joined #openstack-meeting-411:42
*** tfukushima has quit IRC11:44
*** baoli has joined #openstack-meeting-411:44
*** zhurong has joined #openstack-meeting-411:49
*** bobh has joined #openstack-meeting-411:50
*** sacharya has joined #openstack-meeting-411:54
*** baoli_ has joined #openstack-meeting-411:59
*** sacharya has quit IRC11:59
*** baoli has quit IRC12:02
*** woodard has joined #openstack-meeting-412:09
*** woodard has quit IRC12:09
*** woodard has joined #openstack-meeting-412:10
*** javeriak has quit IRC12:11
*** sarob has joined #openstack-meeting-412:12
*** Niham has quit IRC12:14
*** hvprash has joined #openstack-meeting-412:15
*** hvprash has quit IRC12:15
*** delattec has joined #openstack-meeting-412:15
*** tojuvone has quit IRC12:17
*** sarob has quit IRC12:17
*** cdelatte has quit IRC12:18
*** Niham has joined #openstack-meeting-412:18
*** mohankumar has quit IRC12:19
*** Niham has quit IRC12:21
*** tfukushima has joined #openstack-meeting-412:22
*** tfukushima has quit IRC12:22
*** tfukushima has joined #openstack-meeting-412:22
*** Niham has joined #openstack-meeting-412:22
*** markvoelker has joined #openstack-meeting-412:24
*** xingchao has quit IRC12:25
*** bobh has quit IRC12:26
*** mohankumar has joined #openstack-meeting-412:27
*** Niham has quit IRC12:27
*** Niham has joined #openstack-meeting-412:27
*** numans has quit IRC12:31
*** tojuvone has joined #openstack-meeting-412:34
*** numans has joined #openstack-meeting-412:39
*** danpawlik has quit IRC12:40
*** kylek3h has joined #openstack-meeting-412:40
*** danpawlik has joined #openstack-meeting-412:40
*** delatte has joined #openstack-meeting-412:52
*** dave-mccowan has quit IRC12:52
*** Jeffrey4l has joined #openstack-meeting-412:53
*** cdent has joined #openstack-meeting-412:55
*** delattec has quit IRC12:55
*** oomichi_ has joined #openstack-meeting-412:58
*** javeriak has joined #openstack-meeting-412:58
alex_xu#startmeeting nova api12:59
openstackMeeting started Wed Jun  1 12:59:47 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:59
*** openstack changes topic to " (Meeting topic: nova api)"12:59
openstackThe meeting name has been set to 'nova_api'12:59
alex_xuhello, who is here today?12:59
Kevin_Zhengo/13:00
*** klamath has quit IRC13:00
jicheno/13:00
oomichi_hi13:00
*** klamath has joined #openstack-meeting-413:00
sdagueo/13:00
johnthetubaguyo/13:00
cdento/13:01
alex_xuhello everyone, i think we can start the meeting13:01
alex_xu#topic actions from previous meeting13:01
*** openstack changes topic to "actions from previous meeting (Meeting topic: nova api)"13:01
alex_xuACTION: johnthetubaguy feedback the decision on separated tool for policy discovery back to the spec13:01
alex_xuthis is done, and the spec already updated13:01
alex_xu#link https://review.openstack.org/28940513:01
alex_xui think claudio_ is just waiting for more feedback13:02
sdagueyeh, I need to provide feedback there shortly13:02
alex_xusdague: cool13:03
*** piet has joined #openstack-meeting-413:03
alex_xui just leave comment about the cmd needn't specify the policy config file.13:03
alex_xubut i guess people didn't look at spec yet, so let us discuss in the spec.13:04
alex_xuACTION: sdague to follow up with dhellman to find the right additional reviewers for oslo.policy changes13:04
sdaguealex_xu: ++13:04
sdaguealex_xu: dims said he would also look at it13:04
alex_xusdague: spec merged, and patch ready for review in oslo.policy side, right?13:04
sdaguedid the spec merge? I hadn't looked recently13:05
*** pmesserli has joined #openstack-meeting-413:05
alex_xusdague: yea, merged, and i reviewed the patch today13:05
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/oslo.policy+branch:master+topic:bp/policy-sample-generation13:05
sdaguegreat13:05
alex_xuACTION: johnthetubaguy to update policy docs to remove user_id references to server actions13:06
alex_xujohnthetubaguy: i didn't check that13:06
alex_xui guess johnthetubaguy in the lunch13:07
alex_xulet me check with him later13:07
alex_xuACTION: johnthetubaguy to reply on bug and ML about the ops issues with user_id13:07
johnthetubaguyno he was just a bit distracted13:07
alex_xusdague: i saw some reply from you, we are good at here?13:07
*** dave-mccowan has joined #openstack-meeting-413:07
sdaguewe've got a detailed response from Tim Bell13:08
johnthetubaguyI haven't made much progress on the docs at all, I am afraid13:08
alex_xujohnthetubaguy: nvm, do you need help? i saw the doc link in the ML, i can do that if you are busy13:08
sdaguewhich is probably enough to write a spec and just say we are only going to do the minimum to make CERN happy (for now)13:08
johnthetubaguyalex_xu: thank you, honestly, thats probably best, took on more than I can do around spec freeze (as usual :()13:09
sdagueeveryone else was given an opportunity to speak up, and didn't in any useful detail13:09
johnthetubaguysdague: yeah, that seems like the best approach for now13:09
alex_xusdague: ok, check the target on Tim mentioned action?13:09
*** sdake has joined #openstack-meeting-413:09
sdague#action sdague to write up a spec about limitted (and deprecated) user_id support in policy in nova13:09
alex_xujohnthetubaguy: no problem, really a lot of people need help on freeze :)13:09
alex_xusdague: thanks, if you need some coding help, i signed up13:10
sdaguealex_xu: yeh, that would be great13:10
sdagueI think we'll just want to be super clear in the spec about what we are going to add13:10
alex_xu#action alex_xu to update policy docs to remove user_id references to server actions13:11
alex_xusdague: ok13:11
*** hvprash has joined #openstack-meeting-413:12
alex_xuok, that is all actions, so we can move on, if no more questions13:12
alex_xu#topic API priorities13:13
*** openstack changes topic to "API priorities (Meeting topic: nova api)"13:13
alex_xufor api-ref, i think we also merged a lot of fix last week13:13
sdagueyeh, we have a number up for review still13:13
sdaguehttp://burndown.dague.org/13:14
alex_xuyeh, but i guess we can merge them in next week13:14
sdagueI also have a review up for a microversion selector (here is the output) https://dague.net/testing/api-ref/13:14
sdaguemugsie and I have been chatting a bit about UX. Neither of us is completely thrilled by it, but the functionality is mostly there13:15
cdentthat's a cool idea13:15
oomichi_sdague: cool13:15
Kevin_Zhengah  this is cool13:15
sdagueso... if anyone else has ideas on presentation ... please speak up13:15
johnthetubaguyah, so that changes the samples?13:15
johnthetubaguy(eventually)13:15
johnthetubaguyand hides the unsupported bits13:15
sdaguejohnthetubaguy: well, the basic theory at this point is anything in a microversion gets a class tag added to it13:16
sdagueand this does hide / show based on that13:16
alex_xuah, it is cool13:16
sdagueright now it is hiding / showing parameters13:16
sdagueand ... the crash dump action13:16
johnthetubaguygotcha, gives us the option to do samples later, if we need13:16
oomichi_sdague: how can we know the differences between microversions on the site?13:17
sdaguethough, taking it out of the TOC is not straight forward, so it stays there13:17
sdagueoomichi_: the default, "All"13:17
mugsiesdague: I have a half baked idea for it right now, let me sit on it for now, but I should have something later on today13:17
sdaguemugsie: cool13:17
alex_xumugsie: cool13:17
johnthetubaguyseems like an awesome start to me13:18
alex_xuyea, sdague makes api-ref awsome every week :)13:19
oomichi_alex_xu: yeah, right :)13:19
sdagueyeh, I'd like to get something merged and out this week so we can play with things. That will probably include mugsie's structured error codes markup as well13:19
alex_xucool13:20
sdagueprobably it on api-ref13:20
jichencool~13:20
*** bobh has joined #openstack-meeting-413:20
johnthetubaguysdague: I wonder about something like this for the selecting the microversion: https://jqueryui.com/slider/#hotelrooms13:20
johnthetubaguybut thats probably overcomplicating it for the moment13:21
*** banix has joined #openstack-meeting-413:22
sdaguejohnthetubaguy: sure, that would be a thing. selector seemed a little more wonky to me, but we can play with that bit pretty easily given the hide show functions13:22
johnthetubaguyyeah13:22
alex_xuok, all of that are cool, i guess we can move on13:23
*** njohnston has quit IRC13:24
alex_xufor removng legacy v213:24
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/remove-legacy-v2-api-code13:24
alex_xuoomichi_: we are very close to remove the code!13:24
oomichi_alex_xu: yeah, almost done13:24
sdagueI think my only question on removing legacy v2 code is if we want to be agreed on the user_id policy spec first13:24
oomichi_alex_xu: some feedback is gotten, and will finish them today13:24
alex_xuoomichi_: cool13:25
alex_xusdague: ok...but already remove a lot of things...13:25
oomichi_sdague: yeah, the last one is holded with your -2 for waiting that13:25
sdaguealex_xu: true13:25
*** kylek3h has quit IRC13:25
sdagueI guess we've deleted so much testing, it probably has gotten broken already anyway13:25
*** kylek3h has joined #openstack-meeting-413:26
sdagueok... I'm fine moving forward, lets get things rebased, then give people time to pile up +2s on it13:26
alex_xucool13:26
alex_xufor api policy, we already talked about it in the beginning13:27
alex_xuanything else we want to talk about at here, otherwise, we will jump to open13:27
*** piet has quit IRC13:27
sdagueno, I think jump to open13:28
alex_xu#topic open13:28
*** openstack changes topic to "open (Meeting topic: nova api)"13:28
sdagueand I'll reask the question to mugsie about mv selector13:28
sdaguebecause I'd like to keep the controls in the bootstrap pallet, as it makes it easier to theme13:29
sdagueand I wonder if a navbar - http://getbootstrap.com/components/#navbar13:29
sdaguewith the drop down would be better13:29
sdagueand we could integrate in the expand all to that ... maybe13:29
*** fitoduarte has quit IRC13:30
*** adduarte has joined #openstack-meeting-413:30
sdagueanyway, maybe for later13:30
sdagueon the specs front13:31
sdaguewe should probably get all the pagination specs approved13:31
alex_xusdague: i remember those are merged13:31
sdaguealex_xu: ok, I hadn't caught up on that yet13:31
sdagueare there other outstanding specs that people are concerned on?13:31
johnthetubaguy+1 that question13:32
sdagueas we are getting towards the end of the non priority freeze13:32
johnthetubaguydeadline is thursday, I believe13:32
alex_xujohnthetubaguy: there is one in the agenda, i guess that is yours?13:32
johnthetubaguyoh, whoops13:32
alex_xu#link https://review.openstack.org/#/c/248248/13:32
*** jichen has quit IRC13:32
johnthetubaguyah, right, I added that13:33
alex_xujohnthetubaguy: sorry, a little late...we have full meeting last few weeks...13:33
johnthetubaguyso it was an idea about making some small progress towards tasks13:33
johnthetubaguyby expanding instance actions a little13:33
johnthetubaguythere are a few specs up on the topic13:33
johnthetubaguyadd finish_time for actions13:34
johnthetubaguyso you know its finished13:34
*** sdake has quit IRC13:34
johnthetubaguyand add instance actions for the API operations that are missing13:34
johnthetubaguy(thats a spearate spec)13:34
*** kylek3h has quit IRC13:35
johnthetubaguybut its a bit late at this point to hope to get those merged13:35
johnthetubaguybut if folks have time, that would be interesting13:35
*** yamamoto has joined #openstack-meeting-413:35
johnthetubaguyprobably something for next cycle I guess?13:35
alex_xu+1 for add instance actiosn for all the api operations13:36
sdagueyeh, that seems pretty reasonable13:36
sdagueI have one quibble over ``running``13:37
sdagueas that implies we know it's still running13:37
sdaguewhich... we really don't13:37
johnthetubaguyyeah, thats fair enough13:37
*** tfukushima has quit IRC13:37
johnthetubaguyif we could get eyes on those that would be great13:37
johnthetubaguyI think its something the OSIC folks could really start to chew on, if we get it approved13:38
sdagueyeh, I just went through it, and it seems pretty well scoped as an incremental change13:38
johnthetubaguycool, so I can make an effort to update that to fix any nits, etc13:38
johnthetubaguythere is also this one: https://review.openstack.org/#/c/256743/13:39
johnthetubaguybut thats the expand coverage bit13:39
*** yuli_s has quit IRC13:39
johnthetubaguythere is this one as well, that take on exposing the data in the API: https://review.openstack.org/#/c/30070413:40
johnthetubaguywhat do you all think we should focus on with that, I am tempted to say that first one?13:40
sdaguejohnthetubaguy: wait... did they do 2 specs?13:41
johnthetubaguythere are kinda three specs going on here, it probably got split up a bit too much13:42
*** brunograz has joined #openstack-meeting-413:42
johnthetubaguybut there is, record in the DB a finish time for an action13:42
johnthetubaguyexpose if an action is finished or not13:42
sdagueok, can we get this all into one?13:42
johnthetubaguyand expand instance actions to other ones13:42
*** brunograz has left #openstack-meeting-413:42
johnthetubaguyyeah, I can take that action for now ish13:42
sdaguebecause I can't really conceptualize these as different parts13:42
sdagueas they seem all very related13:43
alex_xuor separated this https://review.openstack.org/#/c/256743/2/specs/newton/approved/expand-instance-actions-coverage.rst this is pretty easy.13:43
johnthetubaguyso I think the expand the actions is a separate one13:43
johnthetubaguyyeah, the other two should all be together13:43
johnthetubaguyits kinda two steps of the same task13:43
alex_xu+113:44
johnthetubaguyOK, so I will try tidy this up, and ping folks that are still around when thats done13:44
johnthetubaguyit would be nice to make a bit of head way on that this cycle13:44
johnthetubaguyalthough time is crazy tight now13:44
oomichi_yeah, small steps are nice to move forward to task13:45
alex_xuyeah13:46
alex_xuso anything more for open?13:47
cdentto update on the modern microversion stuff, the change in nova merged as 2.27 and here's the review for updating novaclieng: https://review.openstack.org/#/c/323362/  (the functional failure seems unrelated?)13:47
alex_xucdent: cool13:47
alex_xui already added myself as reviewer13:48
*** njohnston has joined #openstack-meeting-413:48
cdentgret thank you13:48
johnthetubaguycdent: I just merged something that claimed to fix those failures13:48
cdentjohnthetubaguy: \o/13:48
johnthetubaguywell, +Wed13:48
alex_xucdent: np13:49
johnthetubaguycdent: https://review.openstack.org/#/c/321916/13:49
cdenti've rebased, we'll see if it makes happy now13:50
alex_xuok, cool, anything more people want to bring up, otherwise, let us free the meeting, back to help on review.13:50
alex_xu3...13:50
alex_xu2..13:51
sdaguesounds good, thanks alex_xu13:51
alex_xu1.13:51
alex_xusdague: np13:51
alex_xuthanks all!13:51
alex_xu#endmeeting13:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:51
*** jmckind has joined #openstack-meeting-413:51
openstackMeeting ended Wed Jun  1 13:51:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-01-12.59.html13:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-01-12.59.txt13:51
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-01-12.59.log.html13:51
*** alexchadin has joined #openstack-meeting-413:52
*** yuli_s has joined #openstack-meeting-413:52
*** klamath has quit IRC13:54
*** klamath has joined #openstack-meeting-413:54
*** sdake has joined #openstack-meeting-413:55
*** njohnston has quit IRC13:55
*** cdent has left #openstack-meeting-413:55
*** sacharya has joined #openstack-meeting-413:56
*** klamath has quit IRC13:56
*** klamath has joined #openstack-meeting-413:57
*** qwebirc42203 has joined #openstack-meeting-413:57
*** luis5tb has joined #openstack-meeting-413:58
*** iyamahat has joined #openstack-meeting-413:59
*** oomichi_ has quit IRC14:00
*** seanmurphy has joined #openstack-meeting-414:00
*** sacharya has quit IRC14:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Jun  1 14:00:32 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
acabothi14:00
alexchadinhi14:00
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#06.2F01.2F201614:01
*** vincentfrancoise has joined #openstack-meeting-414:01
jed56hello14:01
*** yamahata has joined #openstack-meeting-414:01
hvprashhi14:01
vincentfrancoisehi14:02
tkaczynskihi14:02
*** qwebirc42203 has quit IRC14:02
dtardivelhi14:02
*** brunograz has joined #openstack-meeting-414:02
seanmurphyhi14:02
tpeopleso/14:02
brunograzhi14:02
acabothi tpeoples ; good to see you ;-)14:02
acabot#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:02
tkaczynskibig tent :)14:03
acabot#info Watcher has been accepted for the OpenStack big tent14:03
acabotlast night14:03
acabotso congrats to everyone14:03
*** vtech has joined #openstack-meeting-414:03
seanmurphygreat news!14:03
brunograz+114:03
acabot#link https://review.openstack.org/#/c/320941/14:03
sballe_o/14:03
*** jwcroppe has joined #openstack-meeting-414:03
acabot#link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-05-31-20.02.log.html if you want to look at the TC discussion14:04
jwcroppeo/14:04
acabotjust some quotes I'd like to share with you14:04
alexchadinbeautiful!14:04
acabot <johnthetubaguy> lots of operators seemed interested in the project at the ops meetup in manchester14:04
acabot <ttx> I like to think of it as more generally the background process that will apply some long-term optimization policy as you have churn on your resources14:04
acabot <sdague> "cloud defrag"14:04
acabot <jroll> another example use case besides power saving: shuffle things around to get a bunch of empty hypervisors, update kernels on the empties, move things back around to get other empties14:05
*** ostroverkhov has joined #openstack-meeting-414:05
acabot <russellb> "policy based live migration" is what it's called in some other things ...14:05
* johnthetubaguy nods at good highlights picked out there14:05
jwcroppeall very great comments14:05
*** gzhai2 has joined #openstack-meeting-414:05
ttxalso pretty great diveristy achieved pre-officialness14:06
ttxdiversity*14:06
acabotthe only "issue" we had was the tag "diverse-affiliation"14:06
acabotttx : thx ;-)14:06
*** kylek3h has joined #openstack-meeting-414:06
acabotso now we can check metrics on stackalytics #link http://stackalytics.com/?project_type=openstack&metric=commits&module=watcher-group14:07
sballe_+114:07
*** Swami has joined #openstack-meeting-414:07
acabotwe need more contribs to lower bcom contributions under 50%14:08
acabotif we want to get the "diverse-affiliation" tag ;-)14:08
gzhai2:)14:08
acabot#info This achievement has been announced on the ML14:09
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2016-June/096340.html14:09
*** vhoward has joined #openstack-meeting-414:09
alexchadinI'm trying to invite more colleagues to watcher's contributing14:09
acabotI hope it will all help you to get more traction inside companies14:10
acabotlets move to watcher activity now14:10
alexchadinRally peoples are interested in Watcher14:10
acabot#info Newton-1 release has been packaged on May 30th watcher v0.27, python-watcher client v0.23 & watcher-dashboard v0.314:10
acabotall packages are available on pypi & launchpad14:11
tkaczynskibecoming big tent project definitely helps with traction I think14:11
jwcroppe+114:11
hvprash+114:11
acabottkaczynski : I hope so and we will see that in the coming weeks, I would like to have bcom contribs under 50% by our next mid-cycle !14:12
acabot#info seanmurphy published a blog post about Watcher14:12
acabot#link https://blog.zhaw.ch/icclab/employing-openstack-watcher-in-geyser-to-make-openstack-more-energy-efficient/14:12
acabotthx seanmurphy14:12
*** rbak has joined #openstack-meeting-414:13
seanmurphynp - it’s not super high visibility stuff tbh14:13
sballe_that is super. thx14:13
*** zeih has quit IRC14:13
seanmurphybut the bit of work that we’re doing here is within the context of that proj, so we have to promote it a bit14:13
hvprashnice !14:13
tkaczynskido we have release notes somewhere with features released in newton-1 ?14:13
*** kylek3h has quit IRC14:14
acabotI forgot to mention it but I wrote down an article on bcom website #link https://b-com.com/en/news/back-austin-openstack-summit-antoine-cabot-gives-us-news-about-watcher-project14:14
acabottkaczynski : actually no, we rely on launchpad to identify blueprints that have been implemented, we should probably improve this14:14
tkaczynskiacabot: thanks14:15
acabottkaczynski : I will look at it as soon as we have the Watcher doc hosted on openstack.org14:15
tkaczynski+114:15
vincentfrancoisetkaczynski acabot: we should maybe use reno (http://docs.openstack.org/developer/reno/) to generate the release notes14:15
*** emagana has joined #openstack-meeting-414:15
acabot#action acabot look at improving release notes for Watcher / use reno14:16
acabot#info mid-cycle details will be announced on the ML by EOW14:16
acabotsballe_ : how many attendees do you have ?14:16
tkaczynskivincentfrancoise: good idea, but I guess this will require more discipline in putting the right comments in the commits or whatever is used to generate these release notes14:16
sballe_for now 614:16
sballe_so we can use more14:16
sballe_jwcroppe: tpeoples jed56 acabot hvprash and sballe14:17
sballe_I hope to get more people from intel. I just sent them out the notification14:17
acabotok can you send an email on the ML to promote it ?14:17
*** vikasc has joined #openstack-meeting-414:17
sballe_sure14:18
sballe_will do later today14:18
vincentfrancoisetkaczynski: Probably yes, but we already write openstack compliant commit messages so this should help14:18
jwcroppeML activity will help a lot I think - we should also send an 'intro' note maybe now that we're Big Tent?14:18
acabot#action sballe_ send an email on the ML to promote our mid-cycle meetup14:18
acabotjwcroppe : I did http://lists.openstack.org/pipermail/openstack-dev/2016-June/096340.html14:18
acabot#info Watcher puppet repository is now available14:19
acabotthanks to the puppet team14:19
acabot#link https://github.com/openstack/puppet-watcher14:19
sballe_acabot: for the internal intel clluster should edwin and I ask for rally to be installed?14:19
sballe_+1 puppet team14:20
acabotwe are looking for feedback from Rally team14:20
acabotalexchadin : any update on this ?14:20
vincentfrancoisethanks to danpawlik for initiating it as well ;)14:20
alexchadinacabot: yes14:20
jed56IMHO, rally is design to benchmark Openstack14:20
sballe_ok let us know since we are being ask for setup requirements14:20
acabotyes thx to danpawlik (I was looking for his IRC nick...)14:20
alexchadinacabot: I got instructions from Rally team of modifying Rally for Watcher Support14:21
sballe_I agree but I am not a rally expert so not sure what to do if things go wrong14:21
alexchadinI can handle this if you want14:21
sballe_but I can learn :)14:21
hvprashsballe_ what about telemetry ?14:21
jed56alexchadin: what are the modifications they want to perform ?14:21
sballe_edwin asked for ceilomter/monasca14:21
danpawlikwe are community,  each brings a lot for this project :)14:21
sballe_hvprash: ^^14:22
gzhai2alexchadin: Do you have plan to enhance rally for watcher?14:22
hvprashthx sballe_, if any help needed on ceilometer will be happy to14:22
alexchadinjed56: we need WatcherOSClient in rally.osclients.OSClient14:22
alexchadinjed56: gate jobs14:22
alexchadinjed56: contexts14:23
alexchadinjed56: http://rally.readthedocs.io/en/latest/plugins/context_plugin.html14:23
jed56I'm not sure that we need to stress the watcher api14:23
alexchadinjed56: and scenarios http://rally.readthedocs.io/en/latest/plugins/scenario_plugin.html14:23
sballe_acabot: jed56 do we think ceilomter will scal eok for the 30 node test?14:23
alexchadingzhai2: I do14:23
jed56the watcher-api  didn't need to scale a lot14:23
sballe_I would prefer to ask for Ceilomter as the back end then Monasca. I have no real experience with Monasca14:24
*** spotz_zzz is now known as spotz14:24
acabotsballe_ : dtardivel is looking at testing the latest version and ceilometer and probably bench Monasca later on14:24
jed56sballe : I don't think so14:24
sballe_ok perfect14:25
sballe_does anybody remember waht the etherpad was called for this activity?14:25
*** vikasc has quit IRC14:25
*** d0ugal has quit IRC14:25
*** paul-carlton2 has joined #openstack-meeting-414:25
gzhai2https://etherpad.openstack.org/p/watcher-test-environment-specifications14:25
jed56alexchadin:  we need more a tool the generate specifics workloads in the VMs14:25
acabotsballe_ : bookmark this one https://etherpad.openstack.org/p/watcher-etherpads ;-)14:26
sballe_perfect14:26
alexchadinjed56: what kind of loads?14:26
*** raddaoui has joined #openstack-meeting-414:26
alexchadinjed56: CPU, RAM, Disk?14:26
acabotalexchadin : yes if we want to trigger migrations based on CPU load we need to deploy loaded VMs14:27
jed56We can have several scenario depending of the goals14:27
vtechI was using the stress tool for that14:27
vtechthere is a newer version stress-ng14:27
acabotvtech : that's what we did also but its far from reality ;-)14:27
tkaczynskithere are some tools which can generate some specific workloads, like CPU, redis, etc. we used that for demo14:27
jed56tkaczynski: yes filebench for example14:28
tkaczynskiI can try to find our what we used if that helps14:28
seanmurphywe found ceilometer to slow down the watcher api quite a bit - don’t have specifics to hand but can provide some details on the openstack-watcher chat in next day or two - even for a small scenario14:28
tkaczynskiI would need to ask my colleagues14:28
acabotthis is what we need to do now, define what will run in the infra to demonstrate watcher capabilities14:28
vtechstress-ng provides much more control than the original stress - http://kernel.ubuntu.com/~cking/stress-ng/14:28
acabotvtech : thx, I will look at it14:29
jed56The perfect tool can generate noisy neighboor , unbalanceload, etc14:29
sballe_jed56 doo we have one of those14:29
hvprashthere is the google perfkit benchmark. haven't tried it yet though - https://github.com/GoogleCloudPlatform/PerfKitBenchmarker14:29
acabotany other announcement ?14:29
jed56vtech: I agree but they are micro-benchmark14:29
dtardivelacabot: could we create a etherpad about stress and workload tools ?14:29
jed56hvprash:  I tried perfkitbenmark14:30
*** jschwarz_ has joined #openstack-meeting-414:30
hvprashany better ?14:30
sballe_dtardivel: I am adding it to the etherpad for the test env14:30
acabotdtardivel : I would prefer to create a sub-section in https://etherpad.openstack.org/p/watcher-test-environment-specifications14:30
dtardivelacabot: +114:30
sballe_acabot: I am doing that14:30
vtechjed56, sure, I just thought stress-ng worth mentioning...14:30
jed56IMHO, we need some to tool to stress a real infrastructure but also use simulators14:31
acabotsballe_ ok14:31
sballe_jed56, dtardivel feel free to add to the etehrpad14:31
*** Niham has quit IRC14:31
jed56I have a POC which connect the watcher strategies with CloudSIm14:31
sballe_What's CloudSim14:31
*** zeih has joined #openstack-meeting-414:32
jed56#link www.cloudbus.org/cloudsim14:32
jed56this an academic cloud simulator14:32
jed56*is14:32
jed56#link http://beyondtheclouds.github.io/VMPlaceS/14:33
*** jschwarz has quit IRC14:33
acabotsorry but I'd like to come back to the agenda :-)14:33
sballe_lol14:33
acabot#topic Review Action Items14:33
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:33
jed56:-)14:33
acabot#info Add Watcher Continiously Optimization spec has been merged #link Add Watcher Continiously Optimization spec has been merged14:34
acabotalexchadin is working on the implem14:34
sballe_+114:34
alexchadin+114:34
tkaczynski+114:34
acabotAudit parameters should be persistent in Db needs review from core #link https://review.openstack.org/#/c/317130/14:34
*** user154752_ has quit IRC14:34
alexchadinit is ready to review14:35
acabot#action acabot sballe_ jwcroppe review https://review.openstack.org/#/c/317130/14:35
hvprashyeah, need more comments14:35
dtardivelhvprash: I will have a look on it14:35
acabotalexchadin : sorry I missed it14:35
jwcroppewill look14:35
*** d0ugal has joined #openstack-meeting-414:35
hvprashthx14:35
*** user154752 has joined #openstack-meeting-414:36
acabotalexchadin needs more reviewers on https://review.openstack.org/#/c/321411/14:36
sballe_I will look at it too14:36
tpeoplesi'll take a look at that14:36
acabot#info Cluster model objects wrapper has been unassigned from tpeoples #link https://review.openstack.org/#/c/287019/14:36
vincentfrancoiseI can review it14:36
tpeoplesacabot: does vincentfrancoise plan to pick that up? i can help with the implmentation, but don't think i'll be able to drive the whole thing14:37
acabot#action sballe_ tpeoples vincentfrancoise review https://review.openstack.org/#/c/321411/14:37
*** zeih has quit IRC14:37
alexchadinvincentfrancoise: I appreciate this:)14:37
dtardivel#action dtardivel review https://review.openstack.org/#/c/317130/ :)14:38
acabottpeoples : vincentfrancoise plan to work on it as soon as efficacy indicator will be merged but he will need help on implementation14:39
vincentfrancoiseacabot: +114:39
tpeoplesok acabot.. let me get back into the swing of things and i'll start hacking at that like i planned to originally... :( :). when vincentfrancoise frees up he can help out14:39
*** sarob has joined #openstack-meeting-414:40
acabotGraph model describing virtual and physical elements in a data center & Consolidation of multiple Action-plans into a single one need reviews #link https://review.openstack.org/#/c/298891/ https://review.openstack.org/#/c/298871/14:40
jed56acabot you can pick me14:40
acabot#action jed56 review  https://review.openstack.org/#/c/298891/ & https://review.openstack.org/#/c/298871/14:41
acabotlets move to Watcher14:41
acabot#info plugins-parameters has been merged #link https://review.openstack.org/#/q/status:merged+project:openstack/watcher+branch:master+topic:bp/plugins-parameters14:41
*** yujunz has joined #openstack-meeting-414:41
acabot2 new strategies have been merged Workload balance migration strategy implementation & Add Overload standard deviation strategy14:41
acabot#link https://review.openstack.org/#/c/292188/14:41
acabot#link https://review.openstack.org/#/c/292188/14:42
acabot#link https://review.openstack.org/#/c/298891/14:42
acabotWatcher CLI14:42
acabot#info openstackclient-plugin has been merged #link https://review.openstack.org/#/q/topic:bp/openstackclient-plugin14:43
acabotso now you can use watcher with "openstack optimize" CLI ;-)14:43
sballe_+114:43
dtardivelAbout the watcher cli, please have a look on latest documentation. Command syntax has changed !!!14:43
acabotyou can still use both "watcher" and "openstack optimize" command14:44
acabot#link http://factory.b-com.com/www/watcher/doc/python-watcherclient/openstack_cli.html14:44
acabotWatcher puppet14:45
*** sarob has quit IRC14:45
acabotdanpawlik has submited the initial commit https://review.openstack.org/#/c/323864/14:45
*** omnipresent has quit IRC14:45
acabotand need reviewers (if you are familiar with puppet :-))14:46
dtardiveldanpawlik: +114:46
danpawlikacabot: people from puppet are very helpful and I guess there will be no problem in review :)14:46
acabotdanpawlik : ok14:46
acabot#topic Blueprint/Bug Review and Discussion14:47
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:47
*** zenoway has joined #openstack-meeting-414:47
*** lrensing has joined #openstack-meeting-414:47
gzhai2acabot: who can review optimization-threshold?14:47
acabot#info Newton-2 is our next milestone due July 11th (just before the mid-cycle)14:47
acabotgzhai2 : right I missed this one, sorry for that14:47
*** d0ugal has quit IRC14:48
*** mfisch has joined #openstack-meeting-414:48
acabotgzhai2 : still a jenkins issue ?14:48
*** mfisch has quit IRC14:48
*** mfisch has joined #openstack-meeting-414:48
acabotgzhai2 needs reviewers on https://review.openstack.org/#/c/297556/14:48
gzhai2acabot: I think so.14:48
*** d0ugal has joined #openstack-meeting-414:48
*** d0ugal has quit IRC14:48
gzhai2jenkins has py34 and multinode error.14:49
*** d0ugal has joined #openstack-meeting-414:49
acabotwho wants to review https://review.openstack.org/#/c/297556/ ?14:49
vincentfrancoisegzhai2: I have made the review but still in draft for now14:49
gzhai2vincentfrancoise: thanks!14:50
*** kebray has quit IRC14:50
acabotNewton-2 #link https://launchpad.net/watcher/+milestone/newton-214:50
*** krtaylor has joined #openstack-meeting-414:50
acabottkaczynski : deadline is July 11th, are you back on the scoring module ?14:51
*** javeriak has quit IRC14:51
vincentfrancoisegzhai2: There is the question of how to validate the parameters that still bugs me but I will be discussing this with jed56 before posting the review ;)14:51
*** coolsvap is now known as coolsvap|afk14:51
jed56+114:51
gzhai2vincentfrancoise: we can discuss it in watcher chanel after meeting.14:51
tkaczynskiacabot: TAP sprint for the release is finishing next Tuesday (7th June), from Wednesday I'm back 100% to Watcher14:51
sballe_+114:52
jed56tkaczynski: great :)14:52
acabottkaczynski : ok I will keep it for Newton-2 then14:52
vincentfrancoisegzhai2: sure14:52
acabotwe still have an unassigned BP regarding policies #link https://blueprints.launchpad.net/watcher/+spec/watcher-policies14:52
acabotdoes anyone wants to take it ?14:52
tkaczynskiI should be able make some good progress, not sure if finish 100%, documentation etc.14:53
*** hdaniel has quit IRC14:53
vincentfrancoisetkaczynski: break down your changesets so we can validate the code even if you didn't finish the doc14:53
*** njohnston_ has joined #openstack-meeting-414:53
tkaczynskivincentfrancoise: will do my best :)14:54
acabottkaczynski : do you plan to come at the mid-cycle ?14:54
acabot5 minutes left for open discussions14:54
tkaczynskiI would like to, but I need to talk to management about funding14:55
acabot#topic Open Discussion14:55
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:55
acabottkaczynski : still the same issue at Intel ;-)14:55
acabotshould we add puppet repository and watcher-dashboard to project-config to get IRC notifications from CI ?14:55
tpeoplesacabot: regarding the policies BP, shouldn't nearly all of the APIs be admin only? trying to think why an end user should have access, unless we would be using policies for certain types of admins14:55
jed56tpeoples: +114:56
vincentfrancoiseWhy not14:56
tkaczynskiacabot: always :) but I think it makes a sense to look at every dollar spent :) it would definitely help to have meetup somewhere closer14:56
alexchadinI will adapt Rally for Watcher and see what we can got from this14:56
*** pmesserli has quit IRC14:56
acabottpeoples : dtardivel had a look at it a couple of months ago14:56
sballe_tkaczynski: it is at the Intel location. aybe you can visit wih other peopel14:57
acabotcoming back to my original discussion, should we add IRC notifications on our 2 new repos ?14:57
*** pmesserli has joined #openstack-meeting-414:58
jed56acabot yes14:58
tpeoplesmight as well as long as it isn't spammy14:58
sballe_What the Openstak way? we are now an official project14:58
jed56vote ?  :)14:58
acabotI really like to have on IRC but I dont want to spam everyone14:58
dtardiveltpeoples: yes, we could have different types of admin user. We want just to allow an admin to configure rules from a policy file.14:58
tkaczynskisballe_: maybe. I should know more in few days I guess14:58
*** pmesserli has left #openstack-meeting-414:58
tpeoplesdtardivel: sure, that sounds reasonable... just don't think many deployers will utilize that sort of feature14:59
acabot#startvote should we add IRC notifs ? yes, no14:59
openstackBegin voting on: should we add IRC notifs ? Valid vote options are yes, no.14:59
openstackVote using '#vote OPTION'. Only your last vote counts.14:59
tpeoples#vote yes14:59
*** seanmurphy has quit IRC14:59
jed56#vote yes14:59
sballe_#vote yes14:59
acabot#vote yes14:59
dtardivel#vote yes14:59
alexchadin#vote yes14:59
gzhai2#vote yes14:59
hvprash#vote yes14:59
vincentfrancoise#vote yes14:59
acabot#endvote15:00
openstackVoted on "should we add IRC notifs ?" Results are15:00
openstackyes (9): vincentfrancoise, tpeoples, alexchadin, hvprash, jed56, dtardivel, acabot, gzhai2, sballe_15:00
acabotok done15:00
sballe_I am glad we voted ;-)15:00
jed56FYI, I'm starting to develop a POC to avoid to bypass the nova scheduler rules15:00
tkaczynskiacabot: by the way, I was thinking in the meantime about scoring module in Watcher and it seems that I will need to make some changes comparing to what is in the spec15:00
acabot#action dtardivel add watcher-puppet & watcher-dashboard notifs on IRC15:00
tkaczynskiacabot: do I need to update the spec and go through the review again?15:00
*** njohnston_ is now known as njohnston15:00
sballe_jed56: 115:00
acabotwe have to end the meeting15:00
acabotthx15:00
sballe_bye15:00
sballe_thx15:00
hvprashbye15:01
acabot#endmeeting15:01
gzhai2bye15:01
alexchadinbye15:01
vincentfrancoisebye15:01
jed56bye bye15:01
tkaczynskibye15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Wed Jun  1 15:01:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-01-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-01-14.00.txt15:01
*** kylek3h has joined #openstack-meeting-415:01
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-01-14.00.log.html15:01
*** brunograz has quit IRC15:01
*** alexchadin has quit IRC15:01
*** seanmurphy has joined #openstack-meeting-415:03
*** pcaruana has quit IRC15:04
*** ayah has quit IRC15:04
*** jschwarz__ has joined #openstack-meeting-415:05
*** iurygregory has left #openstack-meeting-415:06
*** kylek3h has quit IRC15:08
*** numans has quit IRC15:09
*** jschwarz_ has quit IRC15:09
*** d0ugal has quit IRC15:10
*** zhurong has quit IRC15:11
*** d0ugal has joined #openstack-meeting-415:12
*** antongri_ has joined #openstack-meeting-415:12
*** ostroverkhov has quit IRC15:14
*** antongribok has quit IRC15:15
*** hvprash_ has joined #openstack-meeting-415:16
*** mhoppal has joined #openstack-meeting-415:17
*** mhoppal has left #openstack-meeting-415:17
*** Swami_ has joined #openstack-meeting-415:18
*** hvprash has quit IRC15:20
*** yujunz has quit IRC15:22
*** danpawlik has quit IRC15:22
*** Swami has quit IRC15:22
*** nmadhok has joined #openstack-meeting-415:29
*** nihilifer has joined #openstack-meeting-415:31
*** paul-carlton2 has quit IRC15:31
*** inc0 has joined #openstack-meeting-415:32
*** ihrachys has quit IRC15:33
*** sacharya has joined #openstack-meeting-415:34
*** mbound has joined #openstack-meeting-415:36
*** jschwarz__ has quit IRC15:37
*** coolsvap|afk is now known as coolsvap15:46
*** ostroverkhov has joined #openstack-meeting-415:52
*** Rockyg has joined #openstack-meeting-415:53
*** paul-carlton2 has joined #openstack-meeting-415:54
*** tonytan4ever has joined #openstack-meeting-415:54
*** bpokorny has joined #openstack-meeting-415:54
*** masahito has joined #openstack-meeting-415:54
*** sdake has quit IRC15:54
*** nkrinner is now known as nkrinner_afk15:55
*** kylek3h has joined #openstack-meeting-415:55
*** cbouch has joined #openstack-meeting-415:58
*** paul-carlton2 has quit IRC16:00
*** zeih has joined #openstack-meeting-416:01
*** antongri_ has quit IRC16:01
*** antongribok has joined #openstack-meeting-416:01
*** GB21 has joined #openstack-meeting-416:02
*** kylek3h has quit IRC16:03
*** galstrom_zzz is now known as galstrom16:03
*** vincentfrancoise has left #openstack-meeting-416:04
*** paul-carlton2 has joined #openstack-meeting-416:04
*** anilvenkata has quit IRC16:04
*** uck has joined #openstack-meeting-416:04
*** antongribok has quit IRC16:06
*** zeih has quit IRC16:07
*** vishnoianil has joined #openstack-meeting-416:07
*** vtech has quit IRC16:08
*** mliima has joined #openstack-meeting-416:09
*** ccesario has joined #openstack-meeting-416:09
*** seanmurphy has quit IRC16:09
*** itisha has joined #openstack-meeting-416:10
*** sarob has joined #openstack-meeting-416:10
*** masahito has quit IRC16:11
*** prithiv has quit IRC16:12
*** sacharya has quit IRC16:13
*** sarob has quit IRC16:15
*** sdague has quit IRC16:18
*** armax has joined #openstack-meeting-416:19
*** sdake has joined #openstack-meeting-416:19
*** pbourke-home has joined #openstack-meeting-416:21
*** fsunaval has joined #openstack-meeting-416:23
*** sdake has quit IRC16:23
*** fsunaval has quit IRC16:23
*** prithiv has joined #openstack-meeting-416:23
*** ostroverkhov has quit IRC16:24
*** rhallisey has joined #openstack-meeting-416:27
*** prithiv has quit IRC16:28
*** mandre has joined #openstack-meeting-416:29
*** vhosakot has joined #openstack-meeting-416:30
*** masahito has joined #openstack-meeting-416:30
inc0#startmeeting kolla16:30
openstackMeeting started Wed Jun  1 16:30:45 2016 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
openstackThe meeting name has been set to 'kolla'16:30
inc0hello everyone, show of hands please16:30
akwasniehi16:31
mandreo/16:31
vhosakoto/16:31
coolsvaphello o/16:31
nihilifero/16:31
rhallisey#topic rolll-call ?16:31
pbourke-homeo/16:31
rhalliseyhi!16:31
inc0damn16:31
sbezverko/16:31
rhallisey#topic show-hands16:31
inc0#topic rollcall16:31
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:31
rhallisey:)16:31
masahitohi16:31
*** sdague has joined #openstack-meeting-416:31
rhalliseyhi again!16:31
pbourke-homehi16:32
inc0please re-show of hands;)16:32
sbezverko/16:32
mandre\o16:32
inc0I'm new to running meetings16:32
nihilifer\o16:32
vhosakot\o16:32
jpeelerhi16:32
coolsvaphello |o/ :)16:32
inc0#topic agenda16:32
*** openstack changes topic to "agenda (Meeting topic: kolla)"16:32
*** sdake has joined #openstack-meeting-416:32
*** sarob has joined #openstack-meeting-416:32
inc0agena in wiki is outdated unfortunately16:33
*** wirehead_ has joined #openstack-meeting-416:33
inc0but we'll go through usual stuff16:33
wirehead_o/16:33
inc0#topic Announcements16:33
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:33
inc01. we're past n-116:33
*** adduarte has quit IRC16:33
*** antongribok has joined #openstack-meeting-416:33
inc0https://launchpad.net/kolla/+milestone/newton-116:33
vhosakot_o_ \o\ /o/ _o| |o_16:33
inc0lots and lots of stuff there16:33
sdakeactually newton 1 releases this week16:34
*** antongribok has quit IRC16:34
inc0well its May 30 - Jun 316:34
sbezverkvhosakot is it somehitng like YMCA ;-) ??16:34
vhosakot:)16:34
inc0so yeah, we still have few days16:34
mliimahello \o16:34
inc0please, let everyone take a bug from n-1 list and try to close it16:34
inc0we have tons of bugs confirmed, we need to get this managable16:35
*** _sarob has joined #openstack-meeting-416:35
inc0any other announcements?16:35
sdakeyes16:35
sdakethe most important thing we can do in the next 2 days is make sure mitaka-1 is stable16:35
sdakerather newton-116:35
sdaketia :)16:36
inc0so "tons of bugs" and "take at least one";)16:36
pbourke-homesmall announcement16:36
pbourke-homeoraclelinux gates are now active and green :)16:36
inc0yay16:36
mandrewouhou16:36
*** iyamahat has quit IRC16:36
pbourke-homethanks all for help with that16:36
vhosakotcool!16:36
coolsvappbourke-home, (y)16:37
sdakethan kyou pbourke-home for doing the majority of the work :)16:37
inc0anything else? can we move on?16:37
inc0#topic DSL16:37
*** openstack changes topic to "DSL (Meeting topic: kolla)"16:37
inc0since sdake is up and about, let's have quick discussion about it please16:38
inc0#link https://review.openstack.org/#/c/323612/516:38
*** sarob has quit IRC16:38
sdakei need to leave on the hour16:38
wirehead_I'm going to paste what I said previously: The problem with the DSL is that it requires a certain structure for the generated Dockerfiles but it will be much harder to write inscruitable Elemental.  The problem with jinja2 is that if you aren't carefull, you can cross over into being inscruitable, but you won't worry about things not representable in Elemental down the road.16:38
*** yamahata has quit IRC16:38
*** xingchao has joined #openstack-meeting-416:39
inc0sdake, let's try to get as much discussed as possible16:39
vhosakotI will review the PS16:39
* rhallisey needs to also :)16:39
inc0so my take on it - imho we can't deprecate jinja2 without at least full cycle of deprecation16:39
sdakewhat i'd like is for people to review it on the patch16:39
*** GB21 has quit IRC16:39
sdakedeprecation policies don't apply to internal implementations16:39
inc0it's not internal implementation16:40
mandreit's external sdake16:40
inc0it's somethign that people use and extend16:40
sdake'people' here being 1 or 2 people16:40
sdakeor maybe 1016:40
sdakethe longer we wait the more pain there is in their transition16:40
inc0every operator that I heard from and runs kolla on prod either plan or did changes to dockerfiles or created their own16:40
inc0sdake, that's not true16:40
inc0lots of deployments use things like vendor storage or vendor networking16:41
sdakedeprecation poliices ONLY apply to external interfaces16:41
inc0they will go through pains of writing their dockerfiles16:41
inc0and with upgrade we'll break their env16:41
inc0this IS external interface16:41
inc0so we NEED a deprecation period for it16:42
inc0and that's even if we agree that it's good idea at all, which I'm not convinced about tbh16:42
sdakei disagree with your assertion that it is an external interface, just because people are using it as such16:42
pbourke-homei agree on that tbh16:42
sdakeyou agree on which pbourke-home16:42
wirehead_It's an internal 'accidentally external' interface.16:42
pbourke-homewe are planning to rebase soon and if everything changes to dsl I am pretty certain it will be a blocker16:43
coolsvapwe are not providing dockerfiles we are providing containers16:43
inc0coolsvap, that's a false16:43
*** jichen has joined #openstack-meeting-416:43
inc0we provide dockerfiles which can be built16:43
inc0and really, practiaclity over philosophyu16:43
mandrepeople use our tools to build their images16:43
inc0if we lose deployments "because you shouldn't do this in the first place" we did lose a deployment16:43
coolsvaphttps://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml#n210716:43
pbourke-homeim not totally against the dsl as you know, but the backwards compatibility/stability argument inc0 makes is ringing true with me16:43
pbourke-homeare we not a little beyond sweeping architectural changes16:44
pbourke-homeat this point16:44
inc0and we really CANT make this argument because we didn't provide good way to meet use cases of vendor stuff in mitaka16:44
wirehead_Being overly afraid of sweeping architectural changes has caused much pain and suffering in the OpenStack world.16:44
pbourke-homewirehead_: I would argue the ones made cause more pain16:44
pbourke-homefor the operators16:45
inc0wirehead_, we are operator tool16:45
inc0and a deployment tool16:45
inc0if we break something, it's not just kolla thats broken16:45
inc0its literally everything16:45
sdakethe only thing that even rings viably in your argument is that operators that have cusotmized their dockerfiles16:46
coolsvapi think the argument here should be whether we think DSL is a good way to generate Dockerfiles or not16:46
inc0our first and foremost priority should be stability of a deployment16:46
sdakewont be able to easily move their customizations to a new implementation of the dsl16:46
inc0no sdake that's not only thing16:46
wirehead_That still trebles to the pain of realizing we should have done something now a few years down the road.16:46
inc0I just don't want to say that you're overly confident in "this is easy" part16:46
coolsvapwhy it is and why it is not, what are the potential blockers16:46
sdakeok lets table the deprecation policy now, seems like putting cart before horse16:47
inc0let me give you an example of build.py16:47
sdakethere will be no need for deprecation if we dont do a dsl16:47
sdakeso lets move on to coolsvap 's lline of  reasoning16:47
inc0well, if we agree on doing dsl and add deprecation policy, that means we will support both jinja216:47
inc0and dsl16:47
inc0for time being16:47
inc0and see if dsl flies16:47
vhosakotis there an etherpad for DSL ? where do we write our views ?16:48
*** vtech has joined #openstack-meeting-416:48
sdakevhosakot in the review inc0 linked above16:48
wirehead_vhosakot, there's a blueprint spec.16:48
inc0vhosakot, let's use review16:48
vhosakotah ok cool16:48
coolsvapvhosakot, patch 32361216:48
sdakethere will come a day16:48
sdakeif we dont do the dsl now16:48
inc0blocker for me: maturity of code is important16:48
sdakewhere we will be forced to do it because of the crushing weight of our existing implementation as we scale out the big tent16:48
inc0we have fairly mature stuff now, needs refactoring but it's mature16:48
inc0(it needs refactoring because it matured)16:49
sdakehistory revisionism16:49
inc0I'd call it an experience16:49
sdakewhat really happened is people bolted a bunch of stuff onto builld.py to customize stuff without any concern for consistency16:49
pbourke-homeright now we have one dockerfile per image, and we will be replacing that with one yaml file per image16:50
sdakewe need to make the customization step of build.py separate from building the images16:50
sdakepbourke-home i was thinking one yaml file per container set16:50
pbourke-homethe add on files will only be for customisation right16:50
sdakebut whatever works16:50
inc0sdake, agree on that we need to refactor build.py16:50
sdakepbourke-home the new dsl will be the way to generate the dsl16:50
*** kylek3h has joined #openstack-meeting-416:50
pbourke-homeso are we better off number of file wise16:50
inc0but that doesn't mean throwing it away16:50
wirehead_Also, providing a superior experience for add-on Kolla functionality is probably going to make the pain of the DSL less, IMHO.16:50
*** Swami_ has quit IRC16:50
wirehead_That seems to be something not well thought out so far.16:50
sdakethere are 40 container sets16:50
sdakethere are 115 containers16:50
*** vishwanathj has joined #openstack-meeting-416:50
inc0pbourke-home, we can achieve same thing in jinja16:51
sdakewith the method in the spec, there would be 40 yml files16:51
inc0it's a matter of what we want, technologically we can pull off a lot16:51
pbourke-homeinc0: i know im just addressing the 'we're going to be overwhelmed by big tent' arg16:51
pbourke-homethere are 40 j2 files now though16:51
sdakethere are 115 j2 files16:51
sdakethere woud lbe 40 yml files16:51
inc0yeah, we were limited by "only use if"16:52
sdakebecause heat has heat-api, heat-api-cfn, heat-engine, etc16:52
pbourke-homeah I see16:52
sdakethese are a container set16:52
pbourke-homeyou will compress them16:52
vhosakotyeah, we have 100+ j2 and 100+ Dockerfiles16:52
pbourke-homeyeah that's one nice thing16:52
sdakethe top level directory contains elemental.yml"16:52
wirehead_If we're going to make an issue out of this, a non-sdake representative needs to actually determine how hard it is to translate a service from j2 to yml.16:52
sdakei could compress them into one file but i think per container set is fine16:52
sdakewirehead_ i htink we all think that is trivial16:53
sdakeut i could be wrong16:53
sdakeit takes about 20 minutes per service16:53
pbourke-homeinc0: how would you feel about using a less specific form of dsl16:53
inc0so pbourke-home we can easily refactor our Dockerfiles to make use of full jinja2 potential and compress everything as we like16:53
inc0so I just fail to see any real value in DSL in any form16:53
inc0since we have perfectly working tool now16:53
sdakeinc0 in that cae, jinja2 is a dsl, lets throw it out!16:53
pbourke-homeI think there's value in it16:53
sdakeinc0 it is perfectly workign for existing  requirements16:54
pbourke-homebut the question is is it enough16:54
sdakenot new requirements16:54
rhalliseyinc0, my opinion is similar16:54
inc0it's a dsl that's mature, documented, stable and we already use it16:54
coolsvapi think we can always achieve a whole lot technologically but we need to find the best fit of technology and user experience16:54
*** xingchao has quit IRC16:54
*** vishwanathj has quit IRC16:54
wirehead_Putting on my operator hat, I suspect I'd be able to glean more information faster out of sdake's yaml file than a fully optimized jinja2 template.16:54
*** unicell has joined #openstack-meeting-416:54
sdakeyes recall kolla is a tool targeted at operators16:54
sdakenot jinja2 rocket scientists16:54
sbezverkwhen you look at j2 files and yml files, yaml looks more clean, I think operators will appreciate that if in addition they will be provided documentation16:54
inc0so let's throw it out and create somethign immature, new, buggy and screw everyone who dared to create their own dockerfiles in the process16:54
pbourke-homewirehead_: operators wont want to learn the dsl16:54
inc0pbourke-home, correct me if I'm wrong, that includes Oracle too right?16:54
pbourke-homeinc0: yes16:54
sdakeinc0 i will address everything bu tthe lat part about people who made their own dockerfiles16:55
inc0let me rephrase, is there any operator who has prod deployments who DID not edit any dockerfile?16:55
sdakeinc0 we will have a full testing period of 6 weeks in repo16:55
sdakeplus the rest o fthe cycle16:55
*** unicell1 has quit IRC16:55
inc0well, I've put 7 points in total in review16:55
sdake5 months is plenty of time to harden any mistakes we made16:55
inc0no, it is not, we have tons of bugs, other prority items and such to address16:56
wirehead_pbourke-home, I could say that on the other way around.  Operators wont want to learn our particular set of jinja2 either.16:56
rhalliseysdake, ya but you're talking about hardening mistakes and adding new features16:56
rhalliseythis kinda halts all new features16:56
sdakepbourke-home to that argument, you could label the custom plugin shit we have all over build.py16:56
sdakepbourke-home yet people learn how to use that stuff - necessity is mother of invention and all that16:56
wirehead_There's also creating a concept of an 'external builder'.16:56
inc0wirehead_, jinja2 is really close to what Dockerfile looks like16:56
sdakerhallisey it doesn't halt any new features16:56
inc0well it is how Dockerfile looks like with if statements, for loops and includes16:57
sdakei suspect, during development and review, atleast one docker file will get messed up during dev16:57
*** GB21 has joined #openstack-meeting-416:57
inc0and few other16:57
sdakeand that will need repair16:57
*** iyamahat has joined #openstack-meeting-416:57
wirehead_The present jinja2 is really close to what Dockerfile looks like.  As the jinja2 complexity increases that may not be the case.16:57
inc0it's always just a templating language16:57
rhalliseyI think it will, because we will be strengthening dsl16:57
sdakewirehead_ bingo im right there with you16:57
inc0nothing more16:57
*** unicell has quit IRC16:57
rhalliseymandre, you here?16:57
inc0so sdake let say you start making dsl a mianstream16:58
wirehead_PHP is "just" HTML. :)16:58
rhalliseydid people see what mandre's method for third party plugins was?16:58
mandreI'm pretty much of inc0's opinion16:58
inc0wirehead_, so let's remove php and write our websites in yaml that will generate html16:58
*** kylek3h has quit IRC16:58
wirehead_There's at least 10 implemtations of that for each popular language in Github.16:58
inc0yeah, I don't feel adding another one16:59
inc0none of them were really good ideas, we can iterate examples16:59
sdakemandre of which opinion, that dsl is a bad idea?16:59
inc0so tell me this sdake: let say we agree on DSL16:59
inc0how do we add new container until all DSL is ready?16:59
mandreI believe we can clean up our code base with advanced jinja2, and implement plugins in a nicer way17:00
inc0how do you merge anything without breaking master untill all dsl is ready?17:00
mandrethat the dsl is overkill and not flexible enouth17:00
inc0by all I mean every single container for every single distro and install type17:00
sdakemandre its not just plugins, we need customized binaries installed and customized repos PER COTNAINER17:00
*** vishwanathj has joined #openstack-meeting-417:00
inc0sdake, doable with jinja17:00
inc0easily17:00
sdakemandre your reaching at not flexible enough - you haven't provided any example where it can't work17:00
rhalliseyit's doable17:00
sdakeeither way is doable17:00
rhalliseysdake, his third party plugin patch17:00
inc0sdake, install a package, run a command, install a package17:00
inc0in that order17:01
sdakethe quetion is what is the best way for operators to engage with the project17:01
inc0how do you do it in yaml?17:01
mandreexactly what inc0 said17:01
sdakemandre higher up a level17:01
sdakeinc0 higher up a level17:01
inc0nop17:01
sdakehow does the operator  integrate with it17:01
inc0install a c compiler, compile requirement lib, install a software needing compiled lib17:01
inc0real world example when you might need this order17:02
sdakeyaml lis ordered17:02
mandresdake, you can't control order in which the instructions are run with your dsl17:02
sdakeits not a random ordering of things17:02
inc0but you group install packages together17:02
sdakemandre that is incorrect17:02
inc0so unless you want to do command that install stuff, it's impossible17:02
inc0and if you do then you'll do yaml that has nested dockerfile17:02
sdakei really need to jet soon17:03
*** baoli_ has quit IRC17:03
*** mbound has quit IRC17:03
sdakeand this discussion needs to take place on the review17:03
inc0sdake, indulge me, how do you do it in your yaml?17:03
sdakebut, here is the bottom line from my end17:03
sdakei gotta go I ontt have time at this point to explain it to you17:03
sdakeremember, I said I have to leave ont he hour17:03
sdakeI wrote a spec17:03
sdakeI expect mandre and inc0 to write a spec  as well that meets all the requirements I sset out in the use casees17:03
sdakeI expect the core reviewers to review both of these specs and provide voting17:04
*** yamahata has joined #openstack-meeting-417:04
sdakeif no spec wins, then we will have no customization17:04
pbourke-homei know sdake has to go but I'll just throw this out and he can read later on17:04
sdakeif both specs win, well what can I say, I dont know what to do with this17:04
pbourke-homeI personally would not bother with specs and just do pocs17:04
nihiliferpbourke-home: +117:04
inc0pocs are there really17:04
inc0well give me a bit to polish jinja217:04
pbourke-homeinc0: not enough17:04
coolsvappbourke-home, sdague +117:04
sdakepbourke-home the reason we do specs is to break logjams17:04
nihiliferdunno whether doing pocs instead of specs is "openstack way"17:05
pbourke-homethe dsl is barely functional17:05
sdakespecs blow donkey17:05
pbourke-homeso it doesn't offer answers to the questions been asked here17:05
inc0nihilifer, whichever works, one poc is better than 100 specs imho17:05
nihiliferagree17:05
sdakethe reason is becaue they add a bunch of tiem and complexity to development17:05
*** May-meimei1 has joined #openstack-meeting-417:05
nihiliferlet's get the pocs in "workable" state17:05
pbourke-homeI say this as someone who contributed some code to the dsl poc so its nothing personal17:05
rhallisey2 pocs trial by combat?17:05
pbourke-homeyes17:05
sdakein this case, because inc0 and mandre disagree, and possibly some others (its unclear) we require a spec with a majority vote17:05
inc0that's why we only do specs if we want to throw out our fundamental architecture17:05
*** kylek3h has joined #openstack-meeting-417:06
pbourke-homelet the spec come after17:06
pbourke-homeor in paralell17:06
sdakei want all discussion in one spec17:06
nihiliferwell, i'd like to have 100% working pocs first, then spec voting17:06
sdakeor two specs17:06
sdakebut not all spread out over 20 patches17:06
*** vishwanathj has quit IRC17:06
pbourke-homeone spec and one poc for each17:06
pbourke-homethen vote17:06
nihiliferhmmm... ok17:06
inc0ok, agree17:06
sdakewfm17:07
pbourke-homethey should prob have the same requirements though17:07
inc0thanks pbourke-home17:07
*** May-meimei has quit IRC17:07
pbourke-homethey need to be listed17:07
*** May-meimei1 is now known as May-meimei17:07
mandresounds good17:07
*** banix has quit IRC17:07
sdakeas long as use cases are ALL met in the spec i wrote17:07
pbourke-homeso they aren't solving different problems17:07
pbourke-homeand then saying theirs is the best :)17:07
inc0there is a list in sdake spec17:07
rhalliseyawesome :)17:07
coolsvapagreed17:07
inc0I'll add few of my own17:07
sdakepbourke-home good thinking17:07
sdakeinc0 if you want to add stuff thats fine, but lets keep it implementation agnostic17:07
inc0ofc17:07
sdakei am interested in use cases here17:07
sdakethese are just hte use cases coming out of "my sales channel"17:08
inc0I don't do troyan horses...most of the time17:08
sdakeok brainstorm the midcycle17:08
sdakesessions17:08
sdakeI need a list of sessions17:08
sdakeI have to go now17:08
sdakebbi1hr or so17:08
mliimalgtm, i agree17:08
inc0ok17:08
inc0#topic midcycle brainstorm17:09
*** openstack changes topic to "midcycle brainstorm (Meeting topic: kolla)"17:09
inc0etherpad: https://etherpad.openstack.org/p/kolla-newton-midcycle17:09
inc0so, question guys, do we have venue?17:09
wirehead_or a date, although I might just be behind the power curve there.17:09
rhalliseyinc0, I think still unknown17:09
wirehead_Are we doing it cohosted with an existing midcycle (c.f. operator?)17:10
inc0nothing that I know of17:10
vhosakotI thought Boston and Rayleigh, NC were discussed as venues17:10
inc0well, let's do a brainstorm for sessions17:10
rhalliseyI can try for Westford,MA17:10
rhalliseyvhosakot, ya17:10
vhosakotRaleigh*17:10
vhosakotcool17:10
inc0we also had option for Canada17:11
inc0Lyncos is trying to do that17:11
inc0so let's explore our options, I'll try Texas;)17:11
*** banix has joined #openstack-meeting-417:11
rhalliseyanyone have anything to add to the etherpad for topics :)17:11
inc0although TX in the middle of summer might be hard to bear17:11
*** tonytan4ever has quit IRC17:11
wirehead_Kolla-Kubernetes17:12
rhalliseywirehead_, add it :)17:12
rhalliseyadded it*17:12
wirehead_I've gone biking in TX in the middle of summer.  I fear nothing except running over armadillos.17:14
*** sacharya has joined #openstack-meeting-417:15
*** baoli has joined #openstack-meeting-417:15
*** yamamoto has quit IRC17:15
inc0let's do this till 12.2017:16
inc0so 3 more minutes17:16
*** vishwanathj has joined #openstack-meeting-417:16
wirehead_So, minor rant: I started using Kolla-Kubernetes and Kolla a week or so ago and there have been a bunch of cases where the mainline was broken.17:17
inc0#link https://etherpad.openstack.org/p/kolla-newton-midcycle17:17
inc0wirehead_, let's leave it for open discussion 2 minutes from now;)17:18
inc0I'd like to hear how it's broken17:18
inc0kk, let's leave it for now17:20
*** vishwanathj has quit IRC17:20
inc0we can review it again next week17:20
inc0#topic Open discussion17:20
*** openstack changes topic to "Open discussion (Meeting topic: kolla)"17:20
inc0wirehead_, you have a floor17:20
wirehead_K, so two things I observed.  First, ansible 2.0 being changed in mainline but the docs not being changed.17:20
*** emagana has quit IRC17:20
inc0I think there was patch upstream17:21
inc0not sure tho, but sure, we need to add docs for it17:21
pbourke-homethe docs will lag behind to some extent17:21
pbourke-homeas they're not required as part of a change17:21
inc0it's a master tho so that's understandable17:21
rhalliseyhttps://review.openstack.org/#/c/322361/217:21
wirehead_So, the docs were saying Ansible 1.9.4.  The actual working build at the moment was Ansible 2.0, with a doc patch that said 2.x was OK.17:22
inc0yeah, in master it's expected to have some period between api change and doc change17:23
wirehead_I would disagree with that assertion.17:23
inc0well, that's our policy17:24
inc0since we don't do docs and feature in same patch17:24
rhalliseywell we could be faster17:24
inc0that's always true;)17:24
rhalliseymaybe shouldve required the doc change with the 2.0 change17:24
inc0anything else on your mind wirehead_ ?17:24
wirehead_95% of the time, it's OK to lag the docs.  Not for things of the Ansible magnitude.17:24
inc0well, special cases are not special enough17:25
pbourke-homeIve always wondered about the doc policy tbh17:25
pbourke-homeas to how much sense it makes17:25
pbourke-homeif you change something important, you should document it17:25
inc0me too, but reason is that we won't hold back code for typos in docs17:25
pbourke-hometrue17:25
inc0as code might be blocker for other stuff17:25
wirehead_So, second observation was that I had a regression on Kolla-kubernetes over the weekend.  I'm mostly giving it a pass because month-old-project.17:25
pbourke-homealso I get some people are good devs but just can't document17:25
pbourke-homeit is what it is17:25
rhalliseywirehead_, ya there's no gating yet so it's going to happen here and there17:26
inc0well it as, as yhou said, month old project which we still work on architectural level17:26
wirehead_Yeah, that's mostly a "we should start working on gating" comment.17:27
inc0that is also always true;)17:27
inc0and it holds true to kolla ansible too17:27
inc0our gates sux17:27
inc0not as much as it used to, but still17:27
wirehead_Projects that implement gating earlier move faster.17:27
*** boden has joined #openstack-meeting-417:28
inc0well, we have some openstack infra constrains17:28
pbourke-homei just added a note to the midcycle to dicuss why we still can't make ours gate vote17:28
inc0anyway, 2 minutes left17:28
*** zenoway has quit IRC17:28
inc0ok, thank you guys!17:29
inc0cya all in #openstack-kolla17:29
inc0#endmeeting kolla17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed Jun  1 17:29:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-01-16.30.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-01-16.30.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-01-16.30.log.html17:29
*** wirehead_ has left #openstack-meeting-417:29
*** rhallisey has left #openstack-meeting-417:29
*** inc0 has left #openstack-meeting-417:29
*** pbourke-home has left #openstack-meeting-417:29
dougwigo/17:29
*** unicell has joined #openstack-meeting-417:30
bodeno/  howdy17:30
*** masahito has quit IRC17:30
dougwigHenryG: ping17:31
*** vhosakot has left #openstack-meeting-417:31
dougwig#startmeeting networking_lib17:31
openstackMeeting started Wed Jun  1 17:31:37 2016 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:31
*** vishnoianil has quit IRC17:31
*** openstack changes topic to " (Meeting topic: networking_lib)"17:31
dougwig#topic Announcements17:31
openstackThe meeting name has been set to 'networking_lib'17:31
*** openstack changes topic to "Announcements (Meeting topic: networking_lib)"17:31
*** unicell1 has joined #openstack-meeting-417:31
dougwighenry announced the neutron midcycle in ireland. let me grab a link.17:31
*** fitoduarte has joined #openstack-meeting-417:32
dougwig#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/096255.html17:32
dougwigboden: any chance you'll be coming to that?17:32
bodendougwig, prob not17:33
dougwig#topic Open Discussion17:33
*** openstack changes topic to "Open Discussion (Meeting topic: networking_lib)"17:33
dougwigonly two of us here, and i have nothing new.  boden?17:33
bodenWorking on #link https://bugs.launchpad.net/neutron/+bug/158423717:33
openstackLaunchpad bug 1584237 in neutron "Support local validators" [Wishlist,In progress] - Assigned to Boden R (boden)17:33
bodenAs part of this I plan to make minor updates to neutron-lib attributes.py17:33
*** pc_m has joined #openstack-meeting-417:33
bodenHappy to discuss details here, but a patch is perhaps a better discussion vehicle17:34
bodenFrom last time; I have 3 open reviews and other patches that could go up for review, but am withholding them due to dependency chain17:34
*** unicell has quit IRC17:34
*** mliima has left #openstack-meeting-417:34
bodenTo be transparent; I'm not sure the common agent stuff will get into neutron-lib within the timeframes we discussed previously; the reviews are moving a lil slow : )17:34
dougwigpatch is fine to discuss.17:36
dougwigok, i'll make a point to review today. my current time crunch has gone on *way* longer than I expected.17:36
*** Swami has joined #openstack-meeting-417:36
dougwiganything else you need, besides review time?17:36
bodenI don’t think so17:36
bodenBut; I do have a question17:37
bodenAre neutron changes that depend on neutron-lib gated on a 'release' of the lib, or just on neutron-lib master?17:37
dougwigthey have to wait for a pypi release.17:38
bodenand we usually do that how often?17:38
dougwigso generally i dup in the neutron repo to avoid that, and undo later.17:38
dougwigok, let's get back to coding.17:40
dougwig#endmeeting17:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:40
openstackMeeting ended Wed Jun  1 17:40:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-01-17.31.html17:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-01-17.31.txt17:40
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-01-17.31.log.html17:40
*** boden has left #openstack-meeting-417:40
*** pc_m has left #openstack-meeting-417:41
*** s3wong has joined #openstack-meeting-417:42
*** cbouch has quit IRC17:49
*** javeriak has joined #openstack-meeting-417:49
*** zenoway has joined #openstack-meeting-417:51
*** numans has joined #openstack-meeting-417:51
*** GB21 has quit IRC17:53
*** ccesario has quit IRC17:53
*** javeriak_ has joined #openstack-meeting-417:55
*** jmckind has quit IRC17:55
*** zenoway has quit IRC17:55
*** jmckind has joined #openstack-meeting-417:56
*** javeriak has quit IRC17:56
*** zeih has joined #openstack-meeting-417:56
*** jmckind has quit IRC17:56
*** jmckind has joined #openstack-meeting-417:57
*** zeih has quit IRC18:01
*** tonytan4ever has joined #openstack-meeting-418:04
*** sambetts is now known as sambetts|afk18:04
*** user154752_ has joined #openstack-meeting-418:04
*** cloudtrainme has joined #openstack-meeting-418:05
*** ccesario has joined #openstack-meeting-418:06
*** user154752 has quit IRC18:08
*** nmadhok has quit IRC18:11
*** nmadhok has joined #openstack-meeting-418:11
*** ccesario has quit IRC18:11
*** nmadhok has quit IRC18:16
*** yamamoto has joined #openstack-meeting-418:16
*** jmckind has quit IRC18:19
*** paul-carlton2 has quit IRC18:20
*** Rockyg has quit IRC18:24
*** ccesario has joined #openstack-meeting-418:24
*** degorenko is now known as _degorenko|afk18:24
*** yamamoto has quit IRC18:27
*** bpokorny has quit IRC18:29
*** mbound has joined #openstack-meeting-418:35
*** antongribok has joined #openstack-meeting-418:36
*** ihrachys has joined #openstack-meeting-418:37
*** nmadhok has joined #openstack-meeting-418:38
*** mbound has quit IRC18:40
*** ccesario has quit IRC18:41
*** krtaylor has quit IRC18:41
*** zenoway has joined #openstack-meeting-418:41
*** Jeffrey4l has quit IRC18:42
*** Jeffrey4l has joined #openstack-meeting-418:43
*** evgenyf has joined #openstack-meeting-418:43
*** cloudtrainme has quit IRC18:44
*** numans has quit IRC18:45
*** zenoway has quit IRC18:46
*** stanchan has joined #openstack-meeting-418:46
*** bpokorny has joined #openstack-meeting-418:47
*** ihrachys has quit IRC18:49
*** ihrachys has joined #openstack-meeting-418:52
*** ccesario has joined #openstack-meeting-418:53
*** ihrachys has quit IRC18:55
*** ALUVial has joined #openstack-meeting-418:56
*** ihrachys has joined #openstack-meeting-418:59
serverascode#startmeeting operators_telco_nfv19:00
openstackMeeting started Wed Jun  1 19:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is serverascode. 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_telco_nfv)"19:00
openstackThe meeting name has been set to 'operators_telco_nfv'19:00
*** tonytan4ever has quit IRC19:00
serverascodehi, is anyone here for the operators telco/nfv meeting?19:00
serverascode#topic rollcall19:00
*** openstack changes topic to "rollcall (Meeting topic: operators_telco_nfv)"19:00
*** bertrand_ has joined #openstack-meeting-419:01
*** mriedem has joined #openstack-meeting-419:01
*** karl907 has joined #openstack-meeting-419:01
serverascodelet me know if anyone is here for the meeting, otherwise it'll be a short one :)19:01
*** sridhar_ram has joined #openstack-meeting-419:02
sridhar_ramo/19:02
serverascodesridhar_ram: hi :)19:03
serverascodeI'll give it another 2 or 3 min to see if anyone else shows up19:04
ALUVialo/19:04
serverascodeALUVial: hi :)19:04
serverascodesridhar_ram and ALUVial where are you located?19:05
sridhar_ramserverascode: SF bay area19:05
ALUVialPlano TX19:05
*** chem has quit IRC19:06
*** krtaylor has joined #openstack-meeting-419:06
serverascodeok, well I guess it's just the 3 of us19:06
serverascode#topic meeting times19:07
sridhar_ramserverascode: i remember we had a packed room in AUS Summit !19:07
*** openstack changes topic to "meeting times (Meeting topic: operators_telco_nfv)"19:07
serverascodeGiven that we are all in North America I'm not sure what to do on this topic19:07
serverascodewe can have a second weekly meeting and set that for a time that works better for other areas19:07
serverascodeany thoughts on that?19:07
ALUVialand bang goes my hope for lurking and just listening in19:07
serverascodelol19:07
sridhar_ramserverascode: I don't think we have quorum here..  so, we need to cut this short19:08
serverascodeok, is there any definition of quorum at all?19:08
sridhar_ramserverascode: :)19:08
*** vtech has quit IRC19:09
serverascodeI think maybe this time is good for NA but no where else, I could change it to be earlier, it was mentioned in the etherpad that europe works better on 8 to 1600 UTC19:09
serverascodeor do we just leave it and I try to get more ppl to the next meeting to make some time decisions19:09
ALUVialstill, would have expected a bigger NA turnout.  Is the time really the issue?19:10
*** dtardivel has quit IRC19:10
serverascodeyeah maybe not19:10
*** _sarob has quit IRC19:10
ALUVialconference call to get things going perhaps?19:10
serverascodesome openstack meetings do have con calls19:11
serverascodeI could work on setting something up if that would make sense19:11
*** mbound has joined #openstack-meeting-419:12
*** uck has quit IRC19:12
*** uck has joined #openstack-meeting-419:12
serverascode#action serverascode look into a conference call possibility19:12
serverascodeanything else on meeting time?19:12
sridhar_ramserverascode: it is worth trying.. perhaps a doodle poll  to gauge some interest19:13
serverascodeah yeah, good idea, ok19:13
serverascodeanyone want to take that? or I can19:13
ALUVialyep!19:13
ALUVialI mean - good idea19:13
serverascodeok I can take that19:13
serverascode#action serverascode setup a doodle poll19:13
serverascodeanyone else joined in the last few min?19:14
ALUViali'll ping a couple of people I expected to be on this meeting to see where they were19:14
serverascodecool19:14
*** ihrachys has quit IRC19:14
ALUVialI think they were focused on upcoming OPNFV19:14
serverascodeyeah19:15
serverascode#topic longish term project19:15
*** openstack changes topic to "longish term project (Meeting topic: operators_telco_nfv)"19:15
serverascodeso the large deployment team tends to take on longer term projects to make things better, any thoughts on what we might be able to do that is similar?19:15
serverascodethere are a few issues listed in the etherpad19:15
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda19:16
*** spzala has joined #openstack-meeting-419:17
serverascodeok, like sridhar_ram said, we don't have much for ppl, so that will be something to discuss in future meetings19:17
sridhar_ramserverascode: before embarking on that, do we have an handle on what specs that are in-flight that are NFV related ?19:17
serverascodegood point, I'm not sure, that would be a good question to answer19:18
sridhar_ramserverascode: it will be great if there is a way to "tag" a spec or RFE with "NFV" so that we can get a pulse on what is happening across all the openstack projects for a given release19:18
*** mriedem has left #openstack-meeting-419:19
serverascodethat would make things easier for sure19:20
serverascodesomething someone would have to look into19:20
*** evgenyf has quit IRC19:20
sridhar_ramserverascode: maintain a wiki is not an answer :) I can take action item to go look for one19:21
serverascodeso look for some kind of tag or possibility of tags?19:21
serverascodesomething like that?19:21
sridhar_ramserverascode: yes19:21
serverascode#action sridhar_ram look into some kind of NFV related tag for specs and RFEs19:22
serverascodecool thanks!19:22
serverascodeok moving on I suppose19:22
serverascode#topic OPNFV Summit Berlin 201619:22
*** openstack changes topic to "OPNFV Summit Berlin 2016 (Meeting topic: operators_telco_nfv)"19:22
serverascodeit looks like ALUvial is going19:23
serverascodeI will also be there19:23
*** vishnoianil has joined #openstack-meeting-419:23
sridhar_ramI'll be there as well..19:23
serverascodeok cool -- I was wondering if there would be value in some kind of birds of a feather or some sort of meetup19:23
serverascodeor whether the whole thing is that19:24
ALUVialyep.  also one of my employees, but don't know his handle19:24
serverascodedoes anyone have experience working with OPNFV? I don't19:24
serverascodeI'm not sure how we would setup a bof19:24
*** rtheis_ has joined #openstack-meeting-419:24
sridhar_ramKathy (from foundation mrkt team) is pulling together a design summit session on how to engage OpenStack projects better19:24
serverascodeok and that will be at the OPNFV summit?19:25
ALUVialSomeone going to reach out to her19:26
sridhar_ramyep19:26
*** rtheis has quit IRC19:26
serverascodeok, I could check into that unless someone else wants to19:26
ALUVialKathy who?19:27
sridhar_ramI can loop you in to an ongoing email thread on this subject..19:27
serverascodeok yeah that'd be great, I think it would be worthwhile for openstack operators to meetup at opnfv in some fashion19:27
ALUVialKathy Cacciatore?19:28
sridhar_ramyep19:28
sridhar_ramALUVial: yep19:28
sridhar_ramserverascode:  +2, it will be great to have a session focused on operators...19:28
sridhar_ramthe current session planned is more openstack project focused (nova, neutron, tacker, ...)19:29
* sridhar_ram notes he is the PTL for Tacker19:29
serverascodeah, ok nice :)19:29
serverascodeok so we will work on something for that19:30
serverascode#topic open discussion19:30
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"19:30
serverascodeanyone have any other thoughts or topics?19:30
sridhar_ramnone at this time!19:30
serverascodeif not we can end early19:30
ALUVialnone here.19:30
serverascodeok, well thank you both for coming, we have some action items and I'm sure we'll get better attendance at future meetings19:31
serverascode#endmeeting19:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
openstackMeeting ended Wed Jun  1 19:31:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-01-19.00.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-01-19.00.txt19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-01-19.00.log.html19:31
*** Jeffrey4l_ has joined #openstack-meeting-419:31
sridhar_ramserverascode: ALUVial: can you please PM your email ids ? I'll forward an email thread on OPNFV Summit session19:32
serverascodewill do19:32
ALUVialdone19:33
*** Jeffrey4l has quit IRC19:34
*** andymaier has quit IRC19:34
*** bpokorny has quit IRC19:37
*** auggy has left #openstack-meeting-419:38
*** nmadhok has quit IRC19:43
*** nmadhok has joined #openstack-meeting-419:44
*** evgenyf has joined #openstack-meeting-419:44
*** ALUVial has quit IRC19:45
*** dave-mccowan has quit IRC19:46
*** zenoway has joined #openstack-meeting-419:47
*** pvaneck has joined #openstack-meeting-419:50
*** emagana has joined #openstack-meeting-419:51
*** zeih has joined #openstack-meeting-419:52
*** bpokorny has joined #openstack-meeting-419:54
*** vtech has joined #openstack-meeting-419:57
*** zeih has quit IRC19:57
*** minwang2 has joined #openstack-meeting-419:57
*** javeriak_ has quit IRC19:58
*** karl907 has quit IRC19:58
*** armax_ has joined #openstack-meeting-419:59
*** armax has quit IRC19:59
*** armax_ is now known as armax19:59
*** rockyg has joined #openstack-meeting-420:01
rockygno logwg meeting today20:02
*** dave-mccowan has joined #openstack-meeting-420:04
*** jichen has quit IRC20:05
*** david-lyle has joined #openstack-meeting-420:05
*** avarner has joined #openstack-meeting-420:08
*** jmckind has joined #openstack-meeting-420:09
*** user154752_ has quit IRC20:11
*** zeih has joined #openstack-meeting-420:19
*** zeih has quit IRC20:24
*** bertrand_ has quit IRC20:24
*** tonytan4ever has joined #openstack-meeting-420:34
*** spzala has quit IRC20:43
*** sdake has quit IRC20:49
*** hvprash_ has quit IRC20:50
*** david-lyle has quit IRC20:51
*** armax has quit IRC20:53
*** JRobinson__ has joined #openstack-meeting-420:57
JRobinson__Hi all, I'll start the user guide meeting in a few moments20:58
*** julim has quit IRC21:00
JRobinson__#startmeeting docuserguides21:00
openstackMeeting started Wed Jun  1 21:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: docuserguides)"21:00
openstackThe meeting name has been set to 'docuserguides'21:00
JRobinson__Hi, so who is here for the user guide meeting?21:00
*** david-lyle has joined #openstack-meeting-421:01
JRobinson__Okay, looks like just me. No problems though21:03
JRobinson__This will be a short meeting21:03
JRobinson__#topic action items from last meeting21:03
*** openstack changes topic to "action items from last meeting (Meeting topic: docuserguides)"21:03
JRobinson__#info contact development teams21:03
JRobinson__#info discussed user guide items with the Magnum team. Some progress there21:03
JRobinson__#info IA plan from last meeting still needs action.21:04
*** baoli has quit IRC21:04
JRobinson__There are still consistency edits from the previous user guide plan for mitaka that need attention21:05
JRobinson__#topic IA Plan21:05
*** openstack changes topic to "IA Plan (Meeting topic: docuserguides)"21:05
JRobinson__I noted several editing points that could use some consistency during mitaka21:06
JRobinson__as a result, the guide overall could use a consistency edit21:06
JRobinson__if anyone has ideas or thoughts or things they have noticed that need a change,21:07
JRobinson__#info send IA ideas to the docs mailing list or leave a comment on the user guide task list21:07
*** vhoward has quit IRC21:07
JRobinson__#link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides21:07
JRobinson__#topic link changes21:08
*** openstack changes topic to "link changes (Meeting topic: docuserguides)"21:08
JRobinson__I still have some outstanding link changes to work on since the reorg21:08
JRobinson__#action follow the codesearch results, and update the older specs, ops guide, and other repositories as needed21:08
JRobinson__#link http://codesearch.openstack.org/?q=docs.openstack.org%5C%2Fadmin-guide-cloud&i=nope&files=&repos=21:08
JRobinson__#topic open discussion21:09
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"21:09
*** lrensing has quit IRC21:09
JRobinson__That is all for now. Anything else ?21:09
*** mriedem has joined #openstack-meeting-421:11
*** mriedem has left #openstack-meeting-421:11
*** banix has quit IRC21:12
JRobinson__Alright, thanks all in channel.21:15
JRobinson__#endmeeting21:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:15
openstackMeeting ended Wed Jun  1 21:15:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-21.00.html21:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-21.00.txt21:16
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-21.00.log.html21:16
*** galstrom is now known as galstrom_zzz21:16
*** cznewt has joined #openstack-meeting-421:21
*** mbound has quit IRC21:22
*** uck_ has joined #openstack-meeting-421:32
*** uck has quit IRC21:32
*** kylek3h has quit IRC21:32
*** kylek3h has joined #openstack-meeting-421:34
*** jmckind has quit IRC21:35
*** kylek3h has quit IRC21:36
*** kylek3h has joined #openstack-meeting-421:36
*** kylek3h has joined #openstack-meeting-421:37
*** kylek3h has quit IRC21:42
*** v1k0d3n has quit IRC21:45
*** ostroverkhov has joined #openstack-meeting-421:47
*** zeih has joined #openstack-meeting-421:48
*** sshnaidm has quit IRC21:50
*** sdake has joined #openstack-meeting-421:50
*** sshnaidm has joined #openstack-meeting-421:51
*** zeih has quit IRC21:52
*** sarob has joined #openstack-meeting-421:52
*** _sarob has joined #openstack-meeting-421:53
*** emagana has quit IRC21:53
*** sarob has quit IRC21:57
*** antonym has joined #openstack-meeting-421:58
*** emagana_ has joined #openstack-meeting-421:58
*** emagana_ has quit IRC21:59
*** galstrom_zzz is now known as galstrom22:00
*** sdake_ has joined #openstack-meeting-422:00
*** david-lyle has quit IRC22:01
*** sdake has quit IRC22:03
*** tonytan4ever has quit IRC22:11
*** rbak has quit IRC22:12
*** zeih has joined #openstack-meeting-422:15
*** david-lyle has joined #openstack-meeting-422:16
*** antongribok has quit IRC22:18
*** zeih has quit IRC22:19
*** rockyg has quit IRC22:19
*** sdake_ has quit IRC22:21
*** mbound has joined #openstack-meeting-422:23
*** thorst has quit IRC22:23
*** mbound has quit IRC22:28
*** evgenyf has quit IRC22:29
*** thorst has joined #openstack-meeting-422:30
*** kylek3h has joined #openstack-meeting-422:30
*** sdake has joined #openstack-meeting-422:31
*** rbak has joined #openstack-meeting-422:32
*** darrenc is now known as darrenc_afk22:32
*** cznewt has quit IRC22:33
*** thorst has quit IRC22:34
*** kylek3h has quit IRC22:37
*** spotz is now known as spotz_zzz22:39
*** darrenc_afk is now known as darrenc22:39
*** uck_ has quit IRC22:39
*** yamahata has quit IRC22:45
*** sacharya has quit IRC22:45
*** saggi1 has joined #openstack-meeting-422:49
*** saggi1 has quit IRC22:49
*** thorst has joined #openstack-meeting-422:50
*** ostroverkhov has quit IRC22:52
*** thorst has quit IRC22:54
*** jwcroppe has quit IRC22:56
*** bobh has quit IRC22:57
*** gzhai2 has left #openstack-meeting-423:05
*** yamahata has joined #openstack-meeting-423:05
*** sdague has quit IRC23:07
*** qwebirc30418 has joined #openstack-meeting-423:23
*** kylek3h has joined #openstack-meeting-423:24
*** qwebirc437 has joined #openstack-meeting-423:25
JRobinson__Morning all, I'm going to start the user guide meeting for the APAC region in about 5 minutes23:25
*** qwebirc30418 has quit IRC23:25
*** qwebirc437 has quit IRC23:25
JRobinson__#startmeeting docuserguides23:30
openstackMeeting started Wed Jun  1 23:30:28 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:30
*** openstack changes topic to " (Meeting topic: docuserguides)"23:30
openstackThe meeting name has been set to 'docuserguides'23:30
JRobinson__Hi all, It's time for the APAC user guide meeting. Who is here today?23:30
*** kylek3h has quit IRC23:32
JRobinson__Okay, just me again. I'll summarize the points quickly23:34
JRobinson__#topic action items from last meeting23:35
*** openstack changes topic to "action items from last meeting (Meeting topic: docuserguides)"23:35
JRobinson__#info Contact with Magnum team to start the process23:35
JRobinson__#Working on an IA plan from the editing points brought up in mitaka still needs action23:35
JRobinson__sorry, once again23:35
JRobinson__#info Working on an IA plan from the editing points brought up in mitaka still needs action23:35
JRobinson__#info If anyone has further thoughts for IA changes to the User Guides, You can contact me, the mailing list, or leave a comment on the user guide task list23:37
JRobinson__#link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides23:37
JRobinson__#topic link changes23:38
*** openstack changes topic to "link changes (Meeting topic: docuserguides)"23:38
JRobinson__I still have some outstanding link changes to work on since the reorg23:38
JRobinson__#action follow the codesearch results, and update the older specs, ops guide, and other repositories as needed23:38
JRobinson__#link http://codesearch.openstack.org/?q=docs.openstack.org%5C%2Fadmin-guide-cloud&i=nope&files=&repos=23:38
*** amotoki has quit IRC23:38
JRobinson__^this is an item I could use some help completing. These are edits to urls to match with the guide name changes.23:39
JRobinson__follow the link to see the lsit23:39
JRobinson__^list23:39
*** xingchao has joined #openstack-meeting-423:39
*** _sarob has quit IRC23:39
JRobinson__#topic open discussion23:39
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"23:39
JRobinson__If that's all, I'll end the meeting23:40
*** uck has joined #openstack-meeting-423:40
*** v1k0d3n has joined #openstack-meeting-423:40
JRobinson__Alright, thanks all o/23:43
JRobinson__#endmeeting23:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:43
openstackMeeting ended Wed Jun  1 23:43:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-23.30.html23:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-23.30.txt23:43
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-06-01-23.30.log.html23:43
*** zeih has joined #openstack-meeting-423:43
*** uck has quit IRC23:45
*** zeih has quit IRC23:48
*** minwang2 has quit IRC23:48
*** gothicmindfood has quit IRC23:51
*** zhurong has joined #openstack-meeting-423:52
*** banix has joined #openstack-meeting-423:54
*** sdake_ has joined #openstack-meeting-423:54
*** zhurong has quit IRC23:56
*** sdake has quit IRC23:58
*** gothicmindfood has joined #openstack-meeting-423:59
*** david-lyle has quit IRC23:59

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