Wednesday, 2016-05-18

*** uck_ has quit IRC00:06
*** shaohe_feng has quit IRC00:08
*** shaohe_feng has joined #openstack-meeting-400:08
*** minwang2 has quit IRC00:10
*** salv-orlando has joined #openstack-meeting-400:14
*** ninag has joined #openstack-meeting-400:14
*** sridhar_ram has quit IRC00:15
*** xingchao has quit IRC00:17
*** shaohe_feng has quit IRC00:18
*** shaohe_feng has joined #openstack-meeting-400:18
*** ninag has quit IRC00:21
*** kylek3h has joined #openstack-meeting-400:23
*** mastermind has quit IRC00:27
*** piet has quit IRC00:27
*** shaohe_feng has quit IRC00:28
*** cloudtra_ has quit IRC00:29
*** shaohe_feng has joined #openstack-meeting-400:29
*** hvprash has joined #openstack-meeting-400:30
*** armax_ has joined #openstack-meeting-400:31
*** piet has joined #openstack-meeting-400:32
*** armax has quit IRC00:33
*** armax_ is now known as armax00:33
*** hvprash has quit IRC00:34
*** salv-orlando has quit IRC00:36
*** bpokorny has quit IRC00:36
*** shaohe_feng has quit IRC00:38
*** zenoway has joined #openstack-meeting-400:39
*** gangil has quit IRC00:39
*** shaohe_feng has joined #openstack-meeting-400:41
*** zenoway has quit IRC00:43
*** aliadil has joined #openstack-meeting-400:43
*** baoli has joined #openstack-meeting-400:46
*** shaohe_feng has quit IRC00:49
*** shaohe_feng has joined #openstack-meeting-400:49
*** Jeffrey4l has quit IRC00:49
*** xingchao has joined #openstack-meeting-400:55
*** bobh has joined #openstack-meeting-400:55
*** kylek3h has quit IRC00:55
*** piet has quit IRC00:55
*** shaohe_feng has quit IRC00:59
*** xingchao has quit IRC00:59
*** shaohe_feng has joined #openstack-meeting-401:00
*** aliadil has quit IRC01:01
*** banix has quit IRC01:02
*** allen_gao has quit IRC01:03
*** armax has quit IRC01:07
*** sacharya has quit IRC01:09
*** shaohe_feng has quit IRC01:09
*** shaohe_feng has joined #openstack-meeting-401:12
*** xingchao has joined #openstack-meeting-401:15
*** pvaneck has quit IRC01:18
*** salv-orlando has joined #openstack-meeting-401:18
*** shaohe_feng has quit IRC01:19
*** IlyaG has joined #openstack-meeting-401:22
*** shaohe_feng has joined #openstack-meeting-401:22
*** IlyaG has quit IRC01:24
*** IlyaG has joined #openstack-meeting-401:24
*** ajmiller has quit IRC01:25
*** shaohe_feng has quit IRC01:30
*** shaohe_feng has joined #openstack-meeting-401:33
*** armax has joined #openstack-meeting-401:34
*** yamahata has quit IRC01:34
*** iyamahat_ has quit IRC01:35
*** salv-orlando has quit IRC01:36
*** banix has joined #openstack-meeting-401:37
*** shaohe_feng has quit IRC01:40
*** shaohe_feng has joined #openstack-meeting-401:41
*** gangil has joined #openstack-meeting-401:43
*** sridhar_ram has joined #openstack-meeting-401:44
*** Jeffrey4l has joined #openstack-meeting-401:45
*** raddaoui has quit IRC01:47
*** sridhar_ram has quit IRC01:48
*** shaohe_feng has quit IRC01:50
*** shaohe_feng has joined #openstack-meeting-401:50
*** reedip__ has joined #openstack-meeting-401:53
*** s3wong has quit IRC01:53
*** hvprash has joined #openstack-meeting-401:55
*** Jeffrey4l has quit IRC01:55
*** tfukushima has joined #openstack-meeting-401:58
*** hvprash has quit IRC02:00
*** ninag has joined #openstack-meeting-402:00
*** shaohe_feng has quit IRC02:00
*** xuan has joined #openstack-meeting-402:01
*** shaohe_feng has joined #openstack-meeting-402:01
*** bobh has quit IRC02:04
*** iyamahat_ has joined #openstack-meeting-402:04
*** ninag has quit IRC02:05
*** bpokorny has joined #openstack-meeting-402:06
*** sdake has quit IRC02:06
*** Jeffrey4l has joined #openstack-meeting-402:08
*** sacharya has joined #openstack-meeting-402:09
*** unicell has quit IRC02:10
*** shaohe_feng has quit IRC02:11
*** shaohe_feng has joined #openstack-meeting-402:11
*** salv-orlando has joined #openstack-meeting-402:12
*** sdake has joined #openstack-meeting-402:12
*** thorst_ has joined #openstack-meeting-402:13
*** bpokorny_ has joined #openstack-meeting-402:14
*** sacharya has quit IRC02:14
*** zhurong has joined #openstack-meeting-402:16
*** bpokorny has quit IRC02:18
*** bpokorny_ has quit IRC02:19
*** shaohe_feng has quit IRC02:21
*** shaohe_feng has joined #openstack-meeting-402:22
*** sdake has quit IRC02:22
*** iyamahat_ has quit IRC02:24
*** gangil has quit IRC02:25
*** shaohe_feng has quit IRC02:31
*** salv-orlando has quit IRC02:32
*** shaohe_feng has joined #openstack-meeting-402:32
*** thorst_ has quit IRC02:36
*** thorst_ has joined #openstack-meeting-402:36
*** nmadhok has quit IRC02:37
*** nmadhok has joined #openstack-meeting-402:37
*** RuiChen has joined #openstack-meeting-402:38
*** thorst_ has quit IRC02:41
*** shaohe_feng has quit IRC02:41
*** shaohe_feng has joined #openstack-meeting-402:42
*** unicell has joined #openstack-meeting-402:43
*** bobh has joined #openstack-meeting-402:50
*** shaohe_feng has quit IRC02:52
*** shaohe_feng has joined #openstack-meeting-402:52
*** baoli has quit IRC02:57
*** nmadhok has quit IRC02:57
*** gangil has joined #openstack-meeting-402:58
*** iyamahat_ has joined #openstack-meeting-402:59
*** shaohe_feng has quit IRC03:02
*** Jeffrey4l has quit IRC03:03
*** shaohe_feng has joined #openstack-meeting-403:03
*** vishwanathj has quit IRC03:05
*** salv-orlando has joined #openstack-meeting-403:05
*** raddaoui has joined #openstack-meeting-403:06
*** sdake has joined #openstack-meeting-403:09
*** RuiChen has quit IRC03:09
*** shaohe_feng has quit IRC03:12
*** tfukushima has quit IRC03:12
*** shaohe_feng has joined #openstack-meeting-403:12
*** bobh has quit IRC03:15
*** iyamahat_ has quit IRC03:17
*** iyamahat_ has joined #openstack-meeting-403:18
*** coolsvap has joined #openstack-meeting-403:22
*** shaohe_feng has quit IRC03:22
*** shaohe_feng has joined #openstack-meeting-403:23
*** iyamahat_ has quit IRC03:24
*** salv-orlando has quit IRC03:28
*** dave-mccowan has quit IRC03:32
*** IlyaG has quit IRC03:32
*** shaohe_feng has quit IRC03:33
*** shaohe_feng has joined #openstack-meeting-403:33
*** Jeffrey4l has joined #openstack-meeting-403:36
*** sdake_ has joined #openstack-meeting-403:37
*** sdake has quit IRC03:40
*** shaohe_feng has quit IRC03:43
*** shaohe_feng has joined #openstack-meeting-403:46
*** piet has joined #openstack-meeting-403:53
*** shaohe_feng has quit IRC03:53
*** sacharya has joined #openstack-meeting-403:53
*** njohnston-- is now known as njohnston__03:54
*** shaohe_feng has joined #openstack-meeting-403:54
*** njohnston__ has quit IRC03:56
*** njohnsto_ has joined #openstack-meeting-403:57
*** njohnsto_ is now known as njohnston__03:57
*** sdake_ has quit IRC03:58
*** sacharya has quit IRC03:58
*** armax has quit IRC03:59
*** padkrish has joined #openstack-meeting-404:01
*** shaohe_feng has quit IRC04:03
*** shaohe_feng has joined #openstack-meeting-404:04
*** salv-orlando has joined #openstack-meeting-404:05
*** samP has joined #openstack-meeting-404:05
*** samP__ has joined #openstack-meeting-404:06
*** samP has quit IRC04:06
*** iyamahat_ has joined #openstack-meeting-404:07
*** sdake has joined #openstack-meeting-404:09
*** samP__ has quit IRC04:13
*** shaohe_feng has quit IRC04:14
*** samP has joined #openstack-meeting-404:14
*** shaohe_feng has joined #openstack-meeting-404:17
*** vishnoianil has quit IRC04:23
*** zhurong has quit IRC04:23
*** shaohe_feng has quit IRC04:24
*** iyamahat_ has quit IRC04:24
*** shaohe_feng has joined #openstack-meeting-404:24
*** salv-orlando has quit IRC04:25
*** amotoki has quit IRC04:26
*** amotoki has joined #openstack-meeting-404:26
*** yamamoto has quit IRC04:30
*** lakshmiS has quit IRC04:32
*** shaohe_feng has quit IRC04:34
*** shaohe_feng has joined #openstack-meeting-404:35
*** piet has quit IRC04:44
*** shaohe_feng has quit IRC04:44
*** shaohe_feng has joined #openstack-meeting-404:45
*** sacharya has joined #openstack-meeting-404:52
*** Jeffrey4l has quit IRC04:53
*** shaohe_feng has quit IRC04:55
*** shaohe_feng has joined #openstack-meeting-404:56
*** zhurong has joined #openstack-meeting-404:57
*** fawadkhaliq has joined #openstack-meeting-404:57
*** salv-orlando has joined #openstack-meeting-404:58
*** javeriak has joined #openstack-meeting-404:59
*** piet has joined #openstack-meeting-404:59
*** matrohon has joined #openstack-meeting-405:00
*** njohnston__ has quit IRC05:01
*** shaohe_feng has quit IRC05:05
*** shaohe_feng has joined #openstack-meeting-405:06
*** sabari- has joined #openstack-meeting-405:06
*** sacharya has quit IRC05:06
*** padkrish has quit IRC05:07
*** njohnsto_ has joined #openstack-meeting-405:08
*** tinx_ has joined #openstack-meeting-405:08
*** mclaren_ has joined #openstack-meeting-405:08
*** davidlenwell has quit IRC05:09
*** sambetts has joined #openstack-meeting-405:11
*** sambetts|afk has quit IRC05:12
*** piet has quit IRC05:12
*** mjturek1 has quit IRC05:12
*** sabari has quit IRC05:12
*** tinx has quit IRC05:12
*** mclaren has quit IRC05:12
*** vsaienko1 has quit IRC05:12
*** sabari- is now known as sabari05:12
*** yamamoto_ has joined #openstack-meeting-405:13
*** mjturek1 has joined #openstack-meeting-405:14
*** banix has quit IRC05:15
*** vishnoianil has joined #openstack-meeting-405:15
*** shaohe_feng has quit IRC05:15
*** shaohe_feng has joined #openstack-meeting-405:16
*** vsaienko has joined #openstack-meeting-405:16
*** njohnsto_ has quit IRC05:17
*** davidlenwell has joined #openstack-meeting-405:17
*** salv-orlando has quit IRC05:18
*** salv-orlando has joined #openstack-meeting-405:18
*** numans has joined #openstack-meeting-405:24
*** shaohe_feng has quit IRC05:25
*** sdake has quit IRC05:26
*** shaohe_feng has joined #openstack-meeting-405:26
*** matrohon has quit IRC05:29
*** javeriak_ has joined #openstack-meeting-405:30
*** javeriak has quit IRC05:32
*** javeriak has joined #openstack-meeting-405:32
*** shaohe_feng has quit IRC05:36
*** javeriak_ has quit IRC05:36
*** shaohe_feng has joined #openstack-meeting-405:36
*** padkrish has joined #openstack-meeting-405:38
*** padkrish has quit IRC05:42
*** javeriak has quit IRC05:43
*** shaohe_feng has quit IRC05:46
*** shaohe_feng has joined #openstack-meeting-405:47
*** javeriak has joined #openstack-meeting-405:50
*** iyamahat has joined #openstack-meeting-405:52
*** shaohe_feng has quit IRC05:56
*** shaohe_feng has joined #openstack-meeting-405:57
*** javeriak has quit IRC05:58
*** zenoway has joined #openstack-meeting-406:00
*** zenoway has quit IRC06:04
*** sacharya has joined #openstack-meeting-406:05
*** david-lyle has quit IRC06:05
*** gongysh has joined #openstack-meeting-406:06
*** shaohe_feng has quit IRC06:06
*** gangil1 has joined #openstack-meeting-406:07
*** anilvenkata has joined #openstack-meeting-406:07
*** shaohe_feng has joined #openstack-meeting-406:07
*** gangil has quit IRC06:07
*** sacharya has quit IRC06:10
*** njohnsto_ has joined #openstack-meeting-406:14
*** gangil1 has quit IRC06:15
*** shaohe_feng has quit IRC06:17
*** shaohe_feng has joined #openstack-meeting-406:17
*** njohnsto_ has quit IRC06:19
*** paul-carlton2 has joined #openstack-meeting-406:19
*** irenab_ has joined #openstack-meeting-406:21
*** Jeffrey4l has joined #openstack-meeting-406:21
*** irenab has quit IRC06:22
*** irenab_ is now known as irenab06:22
*** shaohe_feng has quit IRC06:27
*** javeriak has joined #openstack-meeting-406:27
*** shaohe_feng has joined #openstack-meeting-406:28
*** salv-orlando has quit IRC06:30
*** ricolin has joined #openstack-meeting-406:32
*** shaohe_feng has quit IRC06:37
*** shaohe_feng has joined #openstack-meeting-406:38
*** fwdit has joined #openstack-meeting-406:39
*** majklkcz has joined #openstack-meeting-406:46
*** tfukushima has joined #openstack-meeting-406:47
*** nkrinner_afk is now known as nkrinner06:47
*** shaohe_feng has quit IRC06:47
*** javeriak has quit IRC06:48
*** Jeffrey4l has quit IRC06:50
*** shaohe_feng has joined #openstack-meeting-406:50
*** RuiChen has joined #openstack-meeting-406:52
*** coolsvap has quit IRC06:53
*** coolsvap has joined #openstack-meeting-406:53
*** javeriak has joined #openstack-meeting-406:55
*** shaohe_feng has quit IRC06:58
*** shaohe_feng has joined #openstack-meeting-406:58
*** belmoreira has joined #openstack-meeting-407:02
*** jschwarz__ has joined #openstack-meeting-407:05
*** shaohe_feng has quit IRC07:08
*** zeih has joined #openstack-meeting-407:08
*** shaohe_feng has joined #openstack-meeting-407:09
*** Jeffrey4l has joined #openstack-meeting-407:10
*** salv-orlando has joined #openstack-meeting-407:11
*** javeriak has quit IRC07:12
*** javeriak has joined #openstack-meeting-407:15
*** shaohe_feng has quit IRC07:18
*** zenoway has joined #openstack-meeting-407:19
*** shaohe_feng has joined #openstack-meeting-407:21
*** matrohon has joined #openstack-meeting-407:22
*** jichen has joined #openstack-meeting-407:26
*** gangil has joined #openstack-meeting-407:28
*** zenoway has quit IRC07:28
*** shaohe_feng has quit IRC07:28
*** shaohe_feng has joined #openstack-meeting-407:29
*** _degorenko|afk is now known as degorenko07:30
*** salv-orlando has quit IRC07:31
*** gangil has quit IRC07:33
*** mastermind has joined #openstack-meeting-407:33
*** jichen has quit IRC07:34
*** salv-orlando has joined #openstack-meeting-407:35
*** shaohe_feng has quit IRC07:39
*** shaohe_feng has joined #openstack-meeting-407:39
*** salv-orl_ has joined #openstack-meeting-407:48
*** shaohe_feng has quit IRC07:49
*** shaohe_feng has joined #openstack-meeting-407:50
*** salv-orlando has quit IRC07:52
*** fawadkhaliq has quit IRC07:52
*** fawadkhaliq has joined #openstack-meeting-407:52
*** david-lyle has joined #openstack-meeting-407:57
*** fawadkhaliq has quit IRC07:58
*** fawadkhaliq has joined #openstack-meeting-407:58
*** fawadkhaliq has quit IRC07:58
*** fawadkhaliq has joined #openstack-meeting-407:59
*** shaohe_feng has quit IRC07:59
*** fawadkhaliq has quit IRC07:59
*** fawadkhaliq has joined #openstack-meeting-408:00
*** shaohe_feng has joined #openstack-meeting-408:00
*** fawadkhaliq has quit IRC08:00
*** ifat_afek has joined #openstack-meeting-408:00
ifat_afek#startmeeting vitrage08:01
openstackMeeting started Wed May 18 08:01:07 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
openstackThe meeting name has been set to 'vitrage'08:01
*** fawadkhaliq has joined #openstack-meeting-408:01
ifat_afekHi everyone!08:01
*** jschwarz__ has quit IRC08:01
*** fawadkhaliq has quit IRC08:01
*** fawadkhaliq has joined #openstack-meeting-408:01
*** emalin has joined #openstack-meeting-408:01
emalinhi08:02
emalingood morning08:02
*** fawadkhaliq has quit IRC08:02
*** fawadkhaliq has joined #openstack-meeting-408:02
*** alexey_weyl has joined #openstack-meeting-408:02
alexey_weylHellooooooooooooo08:02
*** fawadkhaliq has quit IRC08:02
*** fawadkhaliq has joined #openstack-meeting-408:03
*** fawadkhaliq has quit IRC08:03
*** elisha_r has joined #openstack-meeting-408:03
elisha_rhi all08:03
ifat_afekOur agenda today:08:04
ifat_afek* Status and Updates08:04
*** fawadkhaliq has joined #openstack-meeting-408:04
ifat_afek* Is Vitrage ready to become an official OpenStack project?08:04
ifat_afek* Newton release planning08:04
*** unicell has quit IRC08:04
ifat_afek* Open Discussion08:04
*** fawadkhaliq has quit IRC08:04
*** fawadkhaliq has joined #openstack-meeting-408:05
ifat_afek#topic Status and Updates08:05
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:05
ifat_afekThere is going to be a joint Doctor-Vitrage-Congress presentation in OPNFV summit in Berlin, in addition to two POC booths, with demos of Vitrage and Congress08:05
*** fawadkhaliq has quit IRC08:05
ifat_afek#link https://www.eventscribe.com/2016/OPNFV/aaSearchByDay.asp?h=Full%20Schedule&BCFO=P|G08:05
ifat_afekAodh constraints of unique alarm name was removed. See here:08:06
*** sacharya has joined #openstack-meeting-408:06
ifat_afek#link https://review.openstack.org/#/c/315590/08:06
ifat_afekAny other updates?08:06
*** fawadkhaliq has joined #openstack-meeting-408:06
*** fawadkhaliq has quit IRC08:06
alexey_weylI will update08:06
*** fawadkhaliq has joined #openstack-meeting-408:06
*** fawadkhaliq has quit IRC08:07
alexey_weylMostly Noam and I had succesfully made the tempest run in the gate08:07
ifat_afekcool!08:07
*** ohad has joined #openstack-meeting-408:08
alexey_weylI am working on inserting Zabbix to Vitrage08:08
*** fawadkhaliq has joined #openstack-meeting-408:08
alexey_weyland it's instalation with puppet08:08
*** mkoushnir has joined #openstack-meeting-408:09
alexey_weylThats it08:09
ifat_afekalexey_weyl: great, that's a first step towards a zabbix datasource08:09
*** shaohe_feng has quit IRC08:09
elisha_rso I'll go next08:10
elisha_rI've been working on the support for overlapping vitrage templates08:10
*** shaohe_feng has joined #openstack-meeting-408:10
elisha_rThe work is going well, I believe it will be done by next weeks IRC08:10
*** sacharya has quit IRC08:10
*** lhartal has joined #openstack-meeting-408:11
mkoushnirMy turn? Tempest alarms finished and will be pushed today, I hope. The rca fist tempest is ready, and the second will be finished in several days.08:12
elisha_rthere is still time for people who want to comment on the proposed design - see the etherpad here: #link https://etherpad.openstack.org/p/vitrage-overlapping-templates-support-design08:12
elisha_rthat's it for me08:12
*** eyalb has joined #openstack-meeting-408:12
eyalbhi08:12
lhartalhi all :)08:12
ifat_afekelisha_r, mkoushnir: thanks :-)08:12
mkoushnir:)08:12
eyalbI will update08:13
eyalbstarted working on vitrage installtion08:13
*** aguyhasnoname has joined #openstack-meeting-408:13
eyalbpushing code to to the puppet-vitrage08:14
eyalbrepo08:14
eyalbthats all08:14
lhartalI also have an update08:14
lhartalI started to work on template validation API/CLI08:15
aguyhasnonamehi guys08:15
lhartalThe API wil linclude two methods:08:16
*** njohnsto_ has joined #openstack-meeting-408:16
lhartal1. template-validation show [template_id]08:16
*** jschwarz__ has joined #openstack-meeting-408:16
lhartalwill validate specific template08:17
lhartal2. template-validation list - validate all templates and returns a list of templated and their status08:17
lhartalthats all for now08:18
ifat_afekcool, thanks08:18
ifat_afekany other updates anyone?08:18
ifat_afekmoving on08:18
ifat_afek#topic Is Vitrage ready to become an official OpenStack project?08:18
*** openstack changes topic to "Is Vitrage ready to become an official OpenStack project? (Meeting topic: vitrage)"08:18
ifat_afekI feel that after all the progress we have made with Vitrage, it is time we apply to the TC and ask to become an official project08:18
ifat_afekOn the technical side, we comply with all OpenStack requirements and do our best to follow their guidelines. On the community side, we have new code contributions from ZTE Corporation, and there is a big interest in the community08:19
ifat_afekRegarding the process: we submit a change in gerrit, asking to add Vitrage to the list of projects:08:19
ifat_afek#link https://github.com/openstack/governance/blob/master/reference/projects.yaml08:19
ifat_afekThe commit message will contain a long description why Vitrage should fit in the big tent08:19
ifat_afekWhat do you think?08:20
*** shaohe_feng has quit IRC08:20
aguyhasnonameI think we are ready.08:20
aguyhasnoname(sorry about the nickname, my name was, for some reason, used)08:20
*** njohnsto_ has quit IRC08:20
alexey_weylI think we are ready for the TC. There are still some minor issues to handle before that, but in general I think that we are ready :)08:21
eyalb+108:21
ifat_afekalexey_weyl: you mean fix the tempest problem?08:21
lhartal+208:21
ohadI think that we are ready for being official project08:21
ohad+108:21
*** shaohe_feng has joined #openstack-meeting-408:22
eyalbLGTM08:23
alexey_weylYes :)08:24
ifat_afekseems like we all agree :-) so I will start working on the official request, and will submit it once our technical issues are solved. hopefully next week08:24
ifat_afek#topic Newton release planning08:24
*** openstack changes topic to "Newton release planning (Meeting topic: vitrage)"08:24
ifat_afekNewton schedule was published:08:24
ifat_afek#link http://releases.openstack.org/newton/schedule.html08:25
ifat_afekWe started discussing Vitrage effort for Newton, let's continue08:25
ifat_afek#link https://etherpad.openstack.org/p/vitrage-newton-planning08:25
ifat_afekI suggest we all open the etherpad, and each of us can add his name next to an item s/he plans to work on08:25
ifat_afekWe also need to make sure there are blueprints for all of these items08:25
*** javeriak has quit IRC08:26
*** salv-orl_ has quit IRC08:27
*** shaohe_feng has quit IRC08:30
*** paul-carlton2 has quit IRC08:30
*** shaohe_feng has joined #openstack-meeting-408:30
ifat_afekthanks everyone for editing the etherpad08:31
ifat_afek(in case the IRC channel seems too quiet ;-))08:32
ifat_afekI guess we can move on08:35
ifat_afekPlease, go ahead and add blueprints in our lanuchpad:08:35
ifat_afek#link https://blueprints.launchpad.net/vitrage08:35
ifat_afek#topic Open Discussion08:35
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:35
ifat_afekAnything you would like to raise?08:35
*** ricolin has quit IRC08:36
*** mbound has joined #openstack-meeting-408:36
ifat_afekso goodbye everyone08:37
eyalbbye08:37
alexey_weylsee ya08:37
*** alexey_weyl has quit IRC08:37
ifat_afek#endmeeting08:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:37
openstackMeeting ended Wed May 18 08:37:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-18-08.01.html08:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-18-08.01.txt08:37
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-18-08.01.log.html08:37
*** eyalb has quit IRC08:38
*** ifat_afek has left #openstack-meeting-408:38
*** pbourke has quit IRC08:38
*** pbourke has joined #openstack-meeting-408:39
*** mkoushnir has quit IRC08:39
*** ricolin has joined #openstack-meeting-408:40
*** shaohe_feng has quit IRC08:40
*** delattec has joined #openstack-meeting-408:40
*** shaohe_feng has joined #openstack-meeting-408:41
*** samP__ has joined #openstack-meeting-408:42
*** Kevin_Zheng_ has joined #openstack-meeting-408:42
*** tdurakov_ has joined #openstack-meeting-408:43
*** akwasnie___ has joined #openstack-meeting-408:43
*** ashtokolov_ has joined #openstack-meeting-408:43
*** carl_baldwin_ has joined #openstack-meeting-408:43
*** raddaoui_ has joined #openstack-meeting-408:43
*** kozhukalov_ has joined #openstack-meeting-408:43
*** unicell has joined #openstack-meeting-408:44
*** eglute_s has joined #openstack-meeting-408:44
*** bapalm_ has joined #openstack-meeting-408:44
*** haleyb_ has joined #openstack-meeting-408:44
*** blogan_ has joined #openstack-meeting-408:44
*** breton_ has joined #openstack-meeting-408:45
*** mfranc213_ has joined #openstack-meeting-408:45
*** FrankZha- has joined #openstack-meeting-408:45
*** Hunner_ has joined #openstack-meeting-408:45
*** Hunner_ has quit IRC08:45
*** Hunner_ has joined #openstack-meeting-408:45
*** FrankZhang has quit IRC08:45
*** sigmavirus24_awa has quit IRC08:45
*** mfranc213 has quit IRC08:45
*** timsim has quit IRC08:45
*** bharathm has quit IRC08:45
*** tdurakov has quit IRC08:45
*** nick-ma has quit IRC08:45
*** carl_baldwin has quit IRC08:45
*** iberezovskiy has quit IRC08:45
*** scotticus has quit IRC08:45
*** skath has quit IRC08:45
*** blogan has quit IRC08:45
*** akwasnie has quit IRC08:45
*** d34dh0r53 has quit IRC08:45
*** med_ has quit IRC08:45
*** chigang_ has quit IRC08:45
*** tpeoples has quit IRC08:45
*** bapalm has quit IRC08:45
*** ChrisPriceAB has quit IRC08:45
*** melwitt has quit IRC08:45
*** cloudnull has quit IRC08:45
*** sbadia has quit IRC08:45
*** pasquier-s has quit IRC08:45
*** raddaoui has quit IRC08:45
*** Kevin_Zheng has quit IRC08:45
*** kozhukalov has quit IRC08:45
*** odyssey4me has quit IRC08:45
*** Hunner has quit IRC08:45
*** briancurtin has quit IRC08:45
*** Adri2000 has quit IRC08:45
*** mhayden has quit IRC08:45
*** ashtokolov has quit IRC08:45
*** jwagner has quit IRC08:45
*** rbradfor has quit IRC08:45
*** eglute has quit IRC08:45
*** mgagne has quit IRC08:45
*** fwdit has quit IRC08:45
*** samP has quit IRC08:45
*** cdelatte has quit IRC08:45
*** haleyb has quit IRC08:45
*** breton has quit IRC08:45
*** melwitt has joined #openstack-meeting-408:45
*** Adri2000 has joined #openstack-meeting-408:45
*** nick-ma has joined #openstack-meeting-408:45
*** skath has joined #openstack-meeting-408:45
*** scott_ has joined #openstack-meeting-408:45
*** med_ has joined #openstack-meeting-408:45
*** d34dh0r53 has joined #openstack-meeting-408:45
*** mgagne has joined #openstack-meeting-408:45
*** Adri2000 has quit IRC08:45
*** Adri2000 has joined #openstack-meeting-408:45
*** med_ has quit IRC08:45
*** med_ has joined #openstack-meeting-408:45
*** sigmavirus24_awa has joined #openstack-meeting-408:45
*** akwasnie___ is now known as akwasnie08:45
*** sigmavirus24_awa has quit IRC08:45
*** sigmavirus24_awa has joined #openstack-meeting-408:45
*** Kevin_Zheng_ is now known as Kevin_Zheng08:46
*** tdurakov_ is now known as tdurakov08:46
*** mhayden has joined #openstack-meeting-408:46
*** jwagner has joined #openstack-meeting-408:46
*** melwitt is now known as Guest3726408:46
*** scott_ is now known as Guest4358508:46
*** mgagne is now known as Guest9229208:46
*** nick-ma has quit IRC08:46
*** nick-ma has joined #openstack-meeting-408:46
*** skath has quit IRC08:46
*** skath has joined #openstack-meeting-408:46
*** odyssey4me has joined #openstack-meeting-408:46
*** sbadia has joined #openstack-meeting-408:46
*** raddaoui_ is now known as raddaoui08:46
*** rbradfor has joined #openstack-meeting-408:46
*** timsim has joined #openstack-meeting-408:47
*** carl_baldwin_ is now known as carl_baldwin08:47
*** bharathm has joined #openstack-meeting-408:47
*** serverascode has quit IRC08:47
*** fkautz has quit IRC08:47
*** ashtokolov_ is now known as ashtokolov08:47
*** cloudkiller has joined #openstack-meeting-408:47
*** kozhukalov_ is now known as kozhukalov08:48
*** marcusvrn_ has quit IRC08:48
*** dougwig has quit IRC08:48
*** palendae has quit IRC08:48
*** tkaczynski has quit IRC08:48
*** iberezovskiy has joined #openstack-meeting-408:48
*** ChrisPriceAB has joined #openstack-meeting-408:49
*** alex_didenko has quit IRC08:49
*** wxy has quit IRC08:49
*** RaginBajin has quit IRC08:49
*** alanmeadows has quit IRC08:50
*** hayatb has quit IRC08:50
*** shaohe_feng has quit IRC08:50
*** raddaoui has quit IRC08:51
*** shaohe_feng has joined #openstack-meeting-408:51
*** palendae has joined #openstack-meeting-408:51
*** tpeoples has joined #openstack-meeting-408:52
*** chigang_ has joined #openstack-meeting-408:52
*** aguyhasnoname has left #openstack-meeting-408:53
*** jschwarz__ has quit IRC08:53
*** samP__ has quit IRC08:53
*** dtardivel has joined #openstack-meeting-408:55
*** pasquier-s has joined #openstack-meeting-408:56
*** alex_didenko has joined #openstack-meeting-408:56
*** mastermind has quit IRC08:56
*** marcusvrn_ has joined #openstack-meeting-408:57
*** fwdit has joined #openstack-meeting-408:58
*** RaginBajin has joined #openstack-meeting-408:59
*** dougwig has joined #openstack-meeting-408:59
*** hayatb has joined #openstack-meeting-409:00
*** shaohe_feng has quit IRC09:01
*** serverascode has joined #openstack-meeting-409:01
*** shaohe_feng has joined #openstack-meeting-409:02
*** tkaczynski has joined #openstack-meeting-409:02
*** wxy has joined #openstack-meeting-409:03
*** fkautz has joined #openstack-meeting-409:03
*** zenoway has joined #openstack-meeting-409:04
*** alanmeadows has joined #openstack-meeting-409:04
*** Duan has quit IRC09:04
*** briancurtin has joined #openstack-meeting-409:05
*** jschwarz__ has joined #openstack-meeting-409:06
*** jschwarz__ is now known as jschwarz09:06
*** salv-orlando has joined #openstack-meeting-409:09
*** iyamahat has quit IRC09:11
*** shaohe_feng has quit IRC09:11
*** unicell1 has joined #openstack-meeting-409:11
*** shaohe_feng has joined #openstack-meeting-409:12
*** unicell has quit IRC09:14
*** Kevin_Zheng has quit IRC09:16
*** Kevin_Zheng has joined #openstack-meeting-409:21
*** shaohe_feng has quit IRC09:21
*** rajen-liyuanzhen has joined #openstack-meeting-409:22
*** javeriak has joined #openstack-meeting-409:27
*** shaohe_feng has joined #openstack-meeting-409:28
*** shaohe_feng has quit IRC09:31
*** shaohe_feng has joined #openstack-meeting-409:32
*** alexchadin has joined #openstack-meeting-409:33
*** dshakhray has joined #openstack-meeting-409:41
*** shaohe_feng has quit IRC09:42
*** shaohe_feng has joined #openstack-meeting-409:43
*** zhurong has quit IRC09:43
*** cloudkiller is now known as cloudnull09:46
*** zhurong has joined #openstack-meeting-409:47
*** fawadkhaliq has quit IRC09:49
*** fawadkhaliq has joined #openstack-meeting-409:50
*** shaohe_feng has quit IRC09:52
*** shaohe_feng has joined #openstack-meeting-409:53
*** markvoelker has joined #openstack-meeting-409:56
*** matrohon has quit IRC09:59
*** sdague has joined #openstack-meeting-410:01
*** markvoelker has quit IRC10:02
*** shaohe_feng has quit IRC10:02
*** mfedosin has joined #openstack-meeting-410:02
*** shaohe_feng has joined #openstack-meeting-410:03
*** gongysh has quit IRC10:03
*** vishnoianil has quit IRC10:06
*** sacharya has joined #openstack-meeting-410:07
*** shaohe_feng has quit IRC10:12
*** sacharya has quit IRC10:13
*** shaohe_feng has joined #openstack-meeting-410:13
*** salv-orlando has quit IRC10:13
*** zhurong has quit IRC10:17
*** tfukushima has quit IRC10:19
*** salv-orlando has joined #openstack-meeting-410:20
*** tfukushima has joined #openstack-meeting-410:20
*** shaohe_feng has quit IRC10:23
*** nmadhok has joined #openstack-meeting-410:23
*** shaohe_feng has joined #openstack-meeting-410:23
*** Jeffrey4l has quit IRC10:25
*** ohad has quit IRC10:29
*** hvprash has joined #openstack-meeting-410:30
*** shaohe_feng has quit IRC10:33
*** shaohe_feng has joined #openstack-meeting-410:34
*** hvprash has quit IRC10:35
*** shaohe_feng has quit IRC10:43
*** elisha_r has quit IRC10:44
*** alexchadin has quit IRC10:48
*** shaohe_feng has joined #openstack-meeting-410:48
*** ricolin has quit IRC10:52
*** shaohe_feng has quit IRC10:53
*** shaohe_feng has joined #openstack-meeting-410:54
*** xingchao has quit IRC10:56
*** GB21 has joined #openstack-meeting-411:02
*** mfedosin has quit IRC11:02
*** shaohe_feng has quit IRC11:04
*** cbouch has joined #openstack-meeting-411:04
*** shaohe_feng has joined #openstack-meeting-411:05
*** tfukushima has quit IRC11:06
*** mancdaz has quit IRC11:09
*** mancdaz has joined #openstack-meeting-411:09
*** Kevin_Zheng has quit IRC11:11
*** rtheis has joined #openstack-meeting-411:11
*** njohnsto_ has joined #openstack-meeting-411:13
*** shaohe_feng has quit IRC11:14
*** shaohe_feng has joined #openstack-meeting-411:15
*** zeih has quit IRC11:15
*** njohnsto_ has quit IRC11:18
*** javeriak has quit IRC11:18
*** javeriak_ has joined #openstack-meeting-411:18
*** cartik has joined #openstack-meeting-411:18
*** shaohe_feng has quit IRC11:24
*** shaohe_feng has joined #openstack-meeting-411:24
*** njohnsto_ has joined #openstack-meeting-411:27
*** cartik has quit IRC11:28
*** zeih has joined #openstack-meeting-411:29
*** javeriak_ has quit IRC11:29
*** zenoway has quit IRC11:31
*** zenoway has joined #openstack-meeting-411:31
*** GB21 has quit IRC11:32
*** GB21 has joined #openstack-meeting-411:33
*** nmadhok has quit IRC11:33
*** shaohe_feng has quit IRC11:34
*** thorst_ has joined #openstack-meeting-411:35
*** zenoway has quit IRC11:35
*** shaohe_feng has joined #openstack-meeting-411:35
*** thorst__ has joined #openstack-meeting-411:35
*** yamamoto_ has quit IRC11:38
*** thorst_ has quit IRC11:39
*** julim has joined #openstack-meeting-411:40
*** shaohe_feng has quit IRC11:45
*** baoli has joined #openstack-meeting-411:45
*** shaohe_feng has joined #openstack-meeting-411:45
*** baoli_ has joined #openstack-meeting-411:46
*** cartik has joined #openstack-meeting-411:49
*** reedip__ has quit IRC11:50
*** baoli has quit IRC11:50
*** ninag has joined #openstack-meeting-411:51
*** matrohon has joined #openstack-meeting-411:53
*** shaohe_feng has quit IRC11:55
*** shaohe_feng has joined #openstack-meeting-411:56
*** ninag has quit IRC11:57
*** zeih has quit IRC11:59
*** baohua has joined #openstack-meeting-412:05
*** shaohe_feng has quit IRC12:05
*** shaohe_feng has joined #openstack-meeting-412:05
*** baohua has quit IRC12:05
*** alexchadin has joined #openstack-meeting-412:07
*** sacharya has joined #openstack-meeting-412:09
*** sigmavirus24_awa is now known as sigmavirus2412:12
*** sacharya has quit IRC12:13
*** shaohe_feng has quit IRC12:15
*** shaohe_feng has joined #openstack-meeting-412:16
*** fawadkhaliq has quit IRC12:17
*** zenoway has joined #openstack-meeting-412:18
*** fawadkhaliq has joined #openstack-meeting-412:18
*** bobh has joined #openstack-meeting-412:18
*** GB21 has quit IRC12:19
*** zeih has joined #openstack-meeting-412:21
*** shaohe_feng has quit IRC12:26
*** degorenko is now known as _degorenko|afk12:26
*** shaohe_feng has joined #openstack-meeting-412:26
*** njohnsto_ has quit IRC12:29
*** jichen has joined #openstack-meeting-412:33
*** shaohe_feng has quit IRC12:36
*** shaohe_feng has joined #openstack-meeting-412:37
*** anteaya has joined #openstack-meeting-412:37
*** salv-orlando has quit IRC12:42
*** javeriak has joined #openstack-meeting-412:42
*** cbouch_ has joined #openstack-meeting-412:45
*** cbouch has quit IRC12:45
*** Kevin_Zheng has joined #openstack-meeting-412:46
*** shaohe_feng has quit IRC12:46
*** woodard has joined #openstack-meeting-412:46
*** shaohe_feng has joined #openstack-meeting-412:47
*** klamath has joined #openstack-meeting-412:47
*** klamath has quit IRC12:47
*** klamath has joined #openstack-meeting-412:48
*** kylek3h has joined #openstack-meeting-412:50
*** bobh has quit IRC12:50
*** nmadhok has joined #openstack-meeting-412:54
*** reedip__ has joined #openstack-meeting-412:54
*** ninag has joined #openstack-meeting-412:55
*** cdent has joined #openstack-meeting-412:56
*** _degorenko|afk is now known as degorenko12:56
*** shaohe_feng has quit IRC12:56
*** shaohe_feng has joined #openstack-meeting-412:57
*** yamamoto has joined #openstack-meeting-412:58
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed May 18 13:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
cdento/13:00
sdagueo/13:00
edleafe\o13:01
jicheno/13:01
alex_xuok, i think we can start the meeting13:01
alex_xu#topic API Priorities13:02
*** openstack changes topic to "API Priorities (Meeting topic: nova api)"13:02
alex_xulet's talk about api-ref13:02
alex_xustill have a lot of patches need review13:02
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-ref-in-rst13:02
alex_xuah, not too much, just less than one page13:03
cdentapologies for not participating in that but I was crunched under trying to get generic resource pools moved forward13:03
sdagueright, we still have a lot of work outstanding13:03
*** matrohon has quit IRC13:03
sdagueI updated the burndown with the list of files and where they stand - http://burndown.dague.org/13:03
alex_xucdent: congrats the resource pool spec merged13:03
cdentalex_xu: one small step in many :)13:04
alex_xuyeah, a lot of work13:04
sdagueso I think on the api-ref front we should decide what must be done before we switch to this being kind of constant background work13:04
sdagueand in my mind I think that's: flavors.inc, servers.inc, versions.inc, metadata.inc13:05
*** pmesserli has joined #openstack-meeting-413:05
sdaguewhich are the more complicated ones13:05
alex_xusdague: +1, at least we can ask people write doc for any new api change in newton13:05
*** njohnsto- has joined #openstack-meeting-413:05
sdaguehowever, I think that if we get those sorted well this week, we're way better than the existing site13:05
alex_xuah, i point to the thing for supporting microversion, but i guess most of thing are done13:06
*** njohnsto- is now known as njohnston--13:06
sdagueyeh13:06
sdaguethere is still a few things we need to poc there13:06
*** baohua has joined #openstack-meeting-413:06
johnthetubaguywhats missing for microverisons now, roughly?13:06
*** baohua has quit IRC13:07
alex_xusdague: do you have list13:07
*** shaohe_feng has quit IRC13:07
johnthetubaguythat max_version patch?13:07
sdaguemax_version is landed13:07
johnthetubaguycool13:07
sdagueand in os-api-ref 0.1.113:07
sdaguethat I released yesterday13:07
sdagueyou can see it in nova patches13:07
*** shaohe_feng has joined #openstack-meeting-413:08
sdaguealex_xu: honestly, I haven't really built a detailed list on the next microversion steps here yet, I've been focussed on the os-api-ref release and getting the content right within the current constraints13:08
sdaguealex_xu: I think you had an old versions.inc patch, right?13:08
alex_xusdague: yes, i had one13:09
alex_xusdague: do we still want that?13:09
sdaguewell, we want something :)13:09
sdagueI went through flavors yesterday13:09
sdagueit took a while13:09
sdagueso, mostly I'm looking to see if we could get volunteers on: servers.inc, versions.inc, metadata.inc for this week13:10
sdagueif not, I'll try to take one a day13:10
sdaguebut splitting that up would be nice13:10
jichenwill spend some time , too13:10
sdaguejichen: cool, thanks13:11
alex_xuah, i already take versions.inc13:11
sdaguealex_xu: great, thank you13:11
sdaguejichen: you want to finish metadata.inc ?13:11
alex_xusdague: np13:11
johnthetubaguyI will make time for the review side13:11
jichensdague: ok, I can13:11
sdaguegreat13:11
alex_xuok, we have plan for this week13:12
sdagueok, I'll poke at servers.inc later this week then. And keep up the work on all the other files as well13:12
*** zeih has quit IRC13:12
sdaguebut those 4 getting landed defines some first stage done and we can do the rest as background during the cycle, and have a final sprint if needed13:12
*** zeih has joined #openstack-meeting-413:12
alex_xuok, cool13:13
sdagueok, I think we're good there. The only other thing to realize is os-api-ref is now a dedicated repo13:13
sdagueso fixes / patches / features should be proposed there13:13
johnthetubaguydo we feel happy getting rid of the old site, once we have those three done?13:13
sdaguejohnthetubaguy: yes, I think so, though anne is still coming up with how all these stitch together13:14
sdagueso I think we'll mostly work with her and follow her lead there13:14
sdaguebut I would feel comfortable with this being the cannonical docs at this point13:14
johnthetubaguysounds good, I guess the key bit is we are not blocking her work their13:14
johnthetubaguyyeah, +113:14
alex_xuok, i think we can move on13:14
sdagueyep13:15
*** mriedem has joined #openstack-meeting-413:15
* mriedem joins late13:15
alex_xufor policy discovery, i saw the spec merged13:15
sdagueawesome13:15
alex_xu#link Embed policy defaults in code13:15
alex_xu#link https://review.openstack.org/29015513:15
alex_xusorry for the wrong link13:16
alex_xui think just waiting Andrew send out the base patch, when he need help on other part, he will reach to us13:16
sdaguesounds great13:17
*** mbound has quit IRC13:17
*** shaohe_feng has quit IRC13:17
alex_xuanything else for policy?13:17
sdaguewhat's the bp topic for that for patches? I'll update the gerrit dash for priority reviews on that13:17
mriedemsdague: doesn't exist yet13:17
mriedemhttps://blueprints.launchpad.net/nova/+spec/policy-in-code13:17
*** thorst__ is now known as thorst_13:17
mriedemsdague: i've already got the needles into laski about it13:17
sdagueok, cool13:18
*** hvprash has joined #openstack-meeting-413:18
mriedemthe oslo policy code has to land and release first13:18
*** shaohe_feng has joined #openstack-meeting-413:18
sdagueok, do we need to help review there as well?13:18
mriedemhttps://blueprints.launchpad.net/oslo.policy/+spec/policy-in-code13:19
mriedemno patches yet that i see in there13:19
alex_xujust saw this patch13:19
mriedemi'll ping jhesketh about approving the bp13:19
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/oslo.policy+branch:master+topic:bp/policy-in-code13:19
sdaguecool, stared it for review13:19
alex_xu#link https://review.openstack.org/30915313:20
*** reedip__ has quit IRC13:20
alex_xuone more spec for policy.json generate13:20
alex_xuok, i think this all for policy, let's move on?13:21
*** hvprash_ has joined #openstack-meeting-413:21
*** bobh has joined #openstack-meeting-413:21
sdagueyes13:22
alex_xuso we can begin to talk about deprecation13:22
sdaguesounds good, I went back through comments last night and here I think are the open issues13:22
sdague* there are a few missing network related things that should be added (fping, net associate) (easy, non controversial)13:23
*** hvprash has quit IRC13:24
sdague* there is an open question about how to help sites not build a bunch of software that's going to break (the big red button question), lets do that last13:24
sdague* there is a question on whether we 404 the network apis at this microversion13:24
sdague(which mriedem does not like)13:24
johnthetubaguyyeah, I kinda like the 404 as a signal that they are going away13:25
mriedemin part because nova-network isn't a proxy api13:25
johnthetubaguyit shouldn't break existing users scripts13:25
mriedembut neither is fping i guess13:25
sdaguejohnthetubaguy: well, it will if they move up the microversion13:25
sdaguemriedem: well fping only works with nova net in most cases13:25
mriedemyeah, so the spec started out being about proxy apis13:26
mriedemand it's easier to think of a big hammer on those13:26
mriedembut other nova-net specific wrinkles makes this mesier13:26
mriedem*messier13:26
johnthetubaguysdague: ack, if they do that for those requests13:26
sdagueok... so, how do we want to navigate this?13:27
mriedemplus as a client do i know or care what backend networking is being used?13:27
johnthetubaguyso what is the alternative for nova-net?13:27
johnthetubaguywe deprecate the APIs after we remove nova-net?13:27
*** shaohe_feng has quit IRC13:27
sdaguemriedem: at some level, yes, because what you can do is quite different13:27
mriedemsdague: yeah i'm sure i could figure it out via trial and error13:27
mriedembut still, that sucks13:27
mriedembut it's latent suck i guess :)13:28
sdaguemriedem: I agree13:28
johnthetubaguymriedem: agreed it sucks13:28
sdaguehence, why we're deprecating nova-net, because eventually you'll know as nova-net isn't an option13:28
mriedemthe problem i have with a 404 on nova-network requests is, with proxies it's easy - go use neutron/cinder/glance/ironic apis13:28
cdentwhat matters more: transitional suck, or eternal suck?13:28
mriedembut with nova-net, you can't use neutron apis13:28
mriedemyou have to use the nova apis for nova-net until that cloud moves to neutron13:28
mriedemso then you have to pin any network-related requests you make < the deprecation microversion13:29
sdaguemriedem: right, which just means you don't get new Nova features in your cloud13:29
johnthetubaguyso security groups and floating ips are the sticking point here?13:29
*** banix has joined #openstack-meeting-413:29
sdaguewhich, I'm not sure why that's an issue13:29
alex_xubut deprecated by microvesion, if user not upgrade to new microversion, so he will be fine13:29
mriedemjust seems like we're pushing a lot of complexity on the client13:29
sdaguemriedem: why?13:29
mriedemsdague: to special case their calls based on microversion13:30
*** mjturek1 has quit IRC13:30
mriedemunless they just cap at this version and don't move ahead13:30
mriedemuntil they are off nova-net13:30
sdaguemriedem: right13:30
sdagueand that's my suggestion13:30
johnthetubaguyI feel like we are warning the client that these old APIs are going away13:30
sdaguethey cap at 2.2513:30
*** shaohe_feng has joined #openstack-meeting-413:30
johnthetubaguyif we don't warn, what do we do when we drop nova-net?13:30
sdagueand they just don't get new nova features until their cloud moves on13:30
sdaguejohnthetubaguy: exactly13:30
mriedemand as a client i can't really do anything about that until the cloud endpoint i'm talking to moves on, or i move on, or i special case my code13:30
sdaguemriedem: right, but just "2.25"13:30
*** tonytan4ever has joined #openstack-meeting-413:31
sdaguewe're assuming this is done with a single global in code13:31
mriedemyeah, but see i really really want 2.40 :)13:31
sdaguethat's tested on that version13:31
johnthetubaguyor keep using v2.0 or v2.1 base version13:31
*** matrohon has joined #openstack-meeting-413:31
sdaguemriedem: well, honestly, too bad13:31
johnthetubaguylike they probably are, since we haven't documented any microversion13:31
sdaguewe're about to actually delete all this code in 2 cycles13:31
mriedemjohnthetubaguy: except novaclient13:31
sdaguecontinuing to make it easy for people to use it up until it's ripped out from under them seems weird13:31
alex_xuemm...one more thing, it is safe for v2.1 compat mode?13:31
sdaguefor the 7% of users still hitting nova-net13:32
*** ddieterly has joined #openstack-meeting-413:32
johnthetubaguymriedem: only the CLI13:32
johnthetubaguymriedem: which we can fix13:32
sdaguewe honestly need to stop treating nova-net sites and users as first class citizens13:32
sdaguenova net is deprecated, they are not any more13:32
johnthetubaguyso here is an alternative...13:32
johnthetubaguytoday: deprecate nova-net13:33
johnthetubaguynext cycle: deprecate the nova-net APIs13:33
johnthetubaguyi.e. give folks a warning its going to get really hard, real soon13:33
mriedemtoday is already done13:33
johnthetubaguyright13:33
sdagueand that means when we delete in P they've only had 6 months warning13:33
sdaguewe deprecated the code that powers those APIs13:33
sdagueI don't understand how those APIs are not also deprecated and blocked in a microversion13:34
mriedemi think people probably need a year at least for this13:34
mriedemlike people are just upgrading to kilo now because it's going end of life13:34
mriedemso i think 6 months is a bit harsh yeah13:34
sdaguemaking APIs first class for deprecated code... just seems like all the wrong messaging13:34
cdentmriedem: if they are only just upgrading to kilo now, then a six month window in master-based time is 18 months?13:35
cdent(in kilo-based time?)13:35
cdentwhich is a _lot_ of time13:35
mriedemcdent: idk, my gut is when they get to newton, we've already ripped out nova-net13:35
mriedembecause they are so far behind13:35
sdaguemriedem: right13:35
*** cloudtrainme has joined #openstack-meeting-413:36
sdagueso, people that far behind, honestly don't get to be part of the conversation.13:36
mriedemso if we're saying people just need to cap in their clients until their cloud moves to nova-net, then i guess i'm fine with that13:36
sdaguemriedem: right, I think that's what we're saying13:36
sdagueat least that's what I'm saying13:36
mriedemwhen i originally read the spec i was thinking people would have to special case their calls13:36
*** Jeffrey4l has joined #openstack-meeting-413:36
mriedemi think we should be very clear about that in the spec13:36
sdaguesure, I can make that clear13:36
sdagueso that was point #313:37
sdagueseems like we have resolution there13:37
sdaguepoint #2 - big red switch13:37
*** shaohe_feng has quit IRC13:37
sdaguei.e. do we provide an easy config option for adminstrators to disable deprecated APIs (all of them, not getting to pick / choose)13:37
*** ddieterly is now known as ddieterly[away]13:38
*** alexchadin has quit IRC13:38
sdaguemostly as a defensive mechanism to help prevent their users from building code against APIs that will go away13:38
sdaguethis is really the meta issue of how to communicate to end user apps they are using deprecated stuff13:38
*** lrensing has joined #openstack-meeting-413:39
alex_xuunless administrator knew that will break the old client.13:39
*** qwebirc39955 has joined #openstack-meeting-413:39
mriedembtw, before we move on from the nova-net thing, no one answered alex_xu's question about v2.1 compat mode13:39
sdagueok, alex_xu what's the question on the v2.1 compat mode?13:39
mriedemactually it wouldn't be a problem13:40
mriedemalex_xu: because that's just a v2.1 request13:40
mriedemnot v2.26 or whatever13:40
alex_xui think we should keep all the proxy api works for v2.1 compat mode. and what happen after we remove nova-net in v2.1 compat mode?13:40
*** shaohe_feng has joined #openstack-meeting-413:40
*** qwebirc68590 has joined #openstack-meeting-413:40
mriedemif we delete the nova-net code, then yes v2.1 compat and everything below the deprecation microversion is busted13:40
sdaguealex_xu: at some point, we have to drop these proxies13:41
mriedemwe can't delete nova-net unless we raise the minimum microversion past the deprecation microversion13:41
mriedemalex_xu: for the proxies, we aren't dropping the code, just giving a 404 after a certain microversion13:41
mriedemto signal13:41
*** aliadil has joined #openstack-meeting-413:41
mriedemso we can eventually raise the minimum required version and then drop the code13:41
sdaguemriedem: that's what concerns me13:41
sdaguebecause what that means is nova-network exists until the T release (at least)13:42
alex_xumriedem: yea, need raise the min version13:42
sdagueand all that code is massively rotted13:42
mriedemsdague: or,13:42
*** qwebirc68590 has quit IRC13:42
mriedemwell,13:42
mriedemi was going to say, it moves out of tree and we just call it, but don't really maintain it,13:42
sdagueright, which is just dumb13:42
mriedembut we would still need to test it i tihnk13:42
sdaguewhich means someone has to fix it13:42
mriedemyeah13:42
sdagueand no one will13:43
mriedemvish might :)13:43
mriedemj/k13:43
*** salv-orlando has joined #openstack-meeting-413:43
sdagueI get that this is a violation of our norms, but it is a special case13:43
mriedemso,13:43
sdaguewe did the same thing with the XML drop13:43
mriedemwe don't need to decide if we're going to drop the code this cycle13:43
sdagueright13:43
sdagueI honestly think the delete is in P13:44
mriedemgetting the deprecation microversion in place doesn't break v2.1 or compat mode13:44
sdagueright13:44
sdaguebut it gets signalling early13:44
mriedemso let's punt on the deleting part13:44
alex_xuif all the network api is extension in legacy v2, i think we can remove then by removing them from the extension api also.13:44
sdagueso we can get people prepared13:44
sdagueok, so... big red switch?13:45
cdentyes13:45
sdaguebecause that's the thing I want to discuss before doing the rev of the spec13:45
*** hvprash_ has quit IRC13:45
sdagueas I think that's the last sticking point13:45
alex_xuok, i'm ok with that, let talk about big red switch13:45
*** bobh has quit IRC13:45
*** hvprash has joined #openstack-meeting-413:45
mriedemi was wondering why deployers that wanted this couldn't just disable the apis via policy?13:46
mriedemthere might have already been a reason that i'm forgetting13:46
sdaguemriedem: because it's super complicated13:46
sdagueand it means that inevitably everyone would do it differently13:46
sdagueso few people actually modify policy13:46
mriedemok, but by the same logic, wouldn't a big red switch put a big x on interop?13:47
sdaguethe situation I'm thinking about is we get to P cycle13:47
johnthetubaguyyeah, most folks always fail at policy changes13:47
sdaguepeople have deployed Newton clouds13:47
alex_xuso...we have red button, which leads to the api return 403...13:47
sdaguewe dropped nova-net in P13:47
sdaguewhich means anything using any of that is broken13:47
*** shaohe_feng has quit IRC13:48
sdaguethe cloud would really like to signal their users early about this13:48
sdagueso they don't have a ton of new software written against newton that is guarunteed to break13:48
sdagueand piss everyone off13:48
*** shaohe_feng has joined #openstack-meeting-413:49
mriedemif you're basing this on the assumption that we drop nova-net in P, i think that has to be sorted out first,13:49
mriedembut go on13:49
*** ddieterly[away] is now known as ddieterly13:49
sdaguewell, we're going to drop something sometime13:49
sdaguemove back 2 releases13:49
sdaguehow do sites manage to premtively help their users no use deprecated apis13:50
* alex_xu reminders 10 mins left13:50
sdagueto help them move forward13:50
johnthetubaguyright, thats my worry13:50
sdaguelet's be honest, deleting stuff is hard, it's always hard13:50
mriedemand if their app is already written using apis from kilo, it's already too late13:50
sdaguemriedem: sure13:50
sdaguebut the longer that exists the worse the problem gets13:51
mriedemso dropping the big red switch will break them - they'd obviously have to give some lead time on that13:51
sdaguesure, which is part of making it an ops switch13:51
mriedemi.e. in 6 months this cloud is going to turn off these apis, so rev your code13:51
sdaguedisable_deprecated_apis=True13:51
sdaguethey could even set that for only 1 set of compute endpoints13:51
sdagueso there is a legacy endpoint, and a clean endpoint13:52
sdagueand people could try their code against the clean endpoint, and see if it works13:52
mriedemi was thinking, what if we deprecate some other api in ocata? if disable_deprecated_apis is a global, then the deprecation in ocata has 0 lead time13:52
sdaguemriedem: yes13:52
cdentI was just going to ask that sdague : so it would be possible to run two different apis: go the default one blow up with a message that says if you insist, reconfigured to use endpoint X ?13:52
*** rbak has joined #openstack-meeting-413:53
mriedembut making the deprecation thing a list is also gross13:53
sdaguemriedem: right, and leads to worse interop13:53
cdents/reconfigured/reconfigure/13:53
sdaguecdent: yeh, API is an n-way service13:53
cdentthat seems like a very sane way to go13:53
cdentas long as the associated messaging was clear13:53
sdagueyou could definitely have multiple of them, talking to the same backend, some with it on and some with it off13:53
mriedemheh, compat mode for the deprecated apis13:54
mriedemwhich have compat mode to v2.013:54
mriedema smelly onion13:54
mriedemi like the multiple endpoint idea though13:54
mriedemas a backdoor13:54
*** irenab has quit IRC13:54
edleafewon't we have to close that backdoor eventually, too?13:55
sdagueedleafe: it's called deleteing the actual code13:55
cdentpresumably the messaging would need to say "the backdoor wil live for N days"13:55
mriedemyeah ,the backdoor is broken when the deprecated apis are gone13:55
mriedemor just don't work anymore13:55
sdagueyep13:55
* alex_xu reminders 5 mins left13:55
mriedemsdague: so before we move forward with something like this, i think it needs advertising on the dev and ops lists13:56
sdaguemriedem: ok, so how do we want to handle the spec then?13:56
sdaguedo an email around this to ops / dev asking for feedback ?13:56
mriedemi think propose what you want for the red switch with the backdoor13:56
mriedemand then yes bring it up in the lists for feedback13:56
*** qwebirc39955 has quit IRC13:57
*** mjturek1 has joined #openstack-meeting-413:57
*** ecelik has joined #openstack-meeting-413:57
*** ostroverkhov has joined #openstack-meeting-413:57
mriedembecause we're providing a way for ops to do something, but we should make sure it's something they'll want or use13:57
mriedemor if we're missing something13:57
sdagueok, and we move forward on the current spec without it for now13:57
sdagueso it can progress13:57
sdaguethen this comes in as ... another spec?13:57
mriedemyeah or that, the kill switch could be a separate spec13:57
*** jmckind has joined #openstack-meeting-413:57
mriedemwe're all on board with the deprecation spec w/o the kill switch i think13:57
sdagueright, I mostly want to make sure we move forward on the proxy deprecation in some form13:57
mriedemso if you want to move that forward, yes13:57
sdagueok, sounds good, I'll redo it based on that feedback (and the other bits above)13:58
mriedemspecs are cheap and plentiful!13:58
sdague* will propose to ops about the kill switch13:58
*** shaohe_feng has quit IRC13:58
*** cbouch__ has joined #openstack-meeting-413:58
sdague* will (at some point) also propose some other extensions to deprecate13:58
*** nmadhok has quit IRC13:58
alex_xucool, i think i will cut the meeting in next minutes13:58
cdentwhat's the link to the spec(s) being discussed?13:58
sdagueas a 3rd spec13:58
sdaguecdent: https://review.openstack.org/#/c/312209/ is the proxy deprecation spec13:59
*** shaohe_feng has joined #openstack-meeting-413:59
cdentthanks sdague13:59
mriedemif you have input on bdm v1 in the dev list please respond13:59
mriedembut i think it falls into the same bit rot category13:59
mriedemwe don't test it13:59
mriedemand it crufts up the bdm code all over nova13:59
*** emalin has quit IRC13:59
*** dave-mccowan has joined #openstack-meeting-413:59
alex_xuok, let's move back to the openstack-nova, i will cut the meeting13:59
mriedemthanks13:59
alex_xuthanks all!13:59
sdagueyep, I think I'm good here, thanks all13:59
alex_xu#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
cdento/13:59
openstackMeeting ended Wed May 18 13:59:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-18-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-18-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-18-13.00.log.html13:59
*** cdent has left #openstack-meeting-414:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed May 18 14:00:05 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
*** jwcroppe has joined #openstack-meeting-414:00
acabothi14:00
dtardivelhi14:00
jed56hi14:00
edleafe\o14:00
ecelikhi14:00
hvprashhi14:00
*** njohnston-- is now known as njohnston__14:00
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#05.2F18.2F201614:00
jwcroppe\o14:00
*** seanmurphy has joined #openstack-meeting-414:00
*** ostroverkhov is now known as xrollla14:00
*** brunograz has joined #openstack-meeting-414:00
xrolllahi14:00
*** linbing has joined #openstack-meeting-414:00
*** vincentfrancoise has joined #openstack-meeting-414:00
vincentfrancoiseo/14:01
*** cartik has quit IRC14:01
acabot#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
seanmurphyhi14:01
*** qwebirc72876 has joined #openstack-meeting-414:01
acabot#info Craton project (fleet management) officially launched and will organize its mid-cycle at the same place & time than Watcher14:02
*** sridhar_ram has joined #openstack-meeting-414:02
*** cbouch_ has quit IRC14:02
*** ninag has quit IRC14:02
*** javeriak has quit IRC14:02
*** petergurinov has joined #openstack-meeting-414:02
*** gzhai2 has joined #openstack-meeting-414:02
*** raddaoui has joined #openstack-meeting-414:02
acabotI had discussion with Jim about this project in Austin, they plan to build a tool to deploy services on very large scale infrastructures14:03
hvprashacabot, i was in that meeting and suggested it14:03
*** vishwanathj has joined #openstack-meeting-414:03
*** qwebirc72876 has quit IRC14:03
sballe_morning14:03
*** nmadhok has joined #openstack-meeting-414:03
acabothvprash : yes, thank you for introducing me, I think this project is interesting and we need to follow where they want to go14:03
*** Liuqing has joined #openstack-meeting-414:04
*** yamahata has joined #openstack-meeting-414:04
gzhai2hi14:04
*** ninag has joined #openstack-meeting-414:04
edleafeSo Watcher, Craton, and Nova all in Hillsboro at the same time?14:04
acabottoday, it is dedicated to very large scale infra but they are interested by the "audit part" of Watcher, I will plan sync time with Craton team in Hilsboro14:04
sballe_acabot: what does deploy at large scale mean?14:04
acabotsballe_: it means more than 1000 nodes14:05
*** jinquan has joined #openstack-meeting-414:05
*** cloudtrainme has quit IRC14:05
sballe_edleafe: I hadn't heard Craton but I knew that Water and nova14:05
acabotsballe_ : https://etherpad.openstack.org/p/craton-meeting-2016-05-1614:06
sballe_but what does deploy mean? manage? are they going to rewrite nova for that? nova doesn't scale to taht scale so are they looking at many noa islands14:06
*** zeih has quit IRC14:06
hvprashsballe_, one of the objective is to collect the metadata.. think like a CMDB14:06
acabotsballe_ : you should look at the etherpad ;-)14:06
sballe_perfect and that is what though. Deploy is just such a buzzword14:07
sballe_I have read the etherpad... and to me it is a CMDB like hvprash points out14:07
sballe_and so deploy is not really in play14:07
hvprashbasically collectiing all the info in a datacenter like network topology, how its connected to the tor etc14:07
*** Jeffrey4l has quit IRC14:08
sballe_hvprash: and we need thta14:08
*** shaohe_feng has quit IRC14:08
acabotsballe_ : I think we need to discuss with them, I hope they will be in Hillsboro14:08
hvprashsballe_, will be interesting to meet them in hillsboro14:08
jed56+114:09
*** ninag has quit IRC14:09
sballe_I agree. Again I hadn't heard they would be there too14:09
*** salv-orlando has quit IRC14:09
*** user154752_ has joined #openstack-meeting-414:09
*** shaohe_feng has joined #openstack-meeting-414:09
acabot#action acabot sync with Craton to define a cross-project meeting during our myd-cycle meetup14:09
*** sacharya has joined #openstack-meeting-414:09
acabot#info I wrote down a commit msg for the big tent that is open to reviews now https://etherpad.openstack.org/p/watcher-big-tent-commit-msg14:09
acabotI plan to submit our project after next meeting (1 week to review the commit msg)14:10
*** iyamahat has joined #openstack-meeting-414:10
acabot#action acabot submit Watcher to the big tent after our next meeting14:11
sballe_acabot: thx I will lok at it14:11
acabot#action sballe_ jwcroppe review https://etherpad.openstack.org/p/watcher-big-tent-commit-msg14:11
*** ninag has joined #openstack-meeting-414:12
edleafeacabot: I'll look it over too. This is great progress!14:12
acabotsync with congress, I wasn't able to attend their meeting last week, did someone attend ?14:12
acabot#action edleafe review https://etherpad.openstack.org/p/watcher-big-tent-commit-msg14:12
jwcroppeacabot: reading now14:12
acabot#info Dont forget that meeting time has changed every 2 weeks starting next week14:13
*** user154752 has quit IRC14:13
acabotany feedback about Congress delegation for VM placement ? #link https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit#14:13
*** sdake has joined #openstack-meeting-414:14
*** sacharya has quit IRC14:14
jed56acabot what kind of feedback do you want ?14:14
*** daneyon has joined #openstack-meeting-414:14
acabotI think the TC will look at it regarding Congress/Watcher overlap so I'd like to have everybody clear the difference between the way we do optimization and the way Congress wants to do it14:15
acabotjed56 : is it the same thing than Watcher ?14:15
sballe_jed56 I looked at it and to me it is enforcing static policies a lot like what Nova should be doing if it had a good architecture14:15
acabotjed56 : but I know your opinion ;-)14:15
*** daneyon_ has joined #openstack-meeting-414:16
jed56Congres has not the same approach but the finality is the same14:16
acabotsballe_ : I agree with you, just to be sure that we share the same opinion in the team14:16
acabot#info Watcher puppet repository creation currently in review https://review.openstack.org/#/c/315431/14:17
*** mriedem has left #openstack-meeting-414:17
acabotany other announcements ?14:17
dtardivelacabot: I'm pushing a new patchset14:17
dtardivelfor puppt14:17
dtardivelfor puppet-watcher14:17
acabotdtardivel : ok thx14:17
*** mbound has joined #openstack-meeting-414:17
acabot#action dtardivel submit a new PS for https://review.openstack.org/#/c/315431/14:18
acabot#topic Review Action Items14:18
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:18
*** AlanClark has joined #openstack-meeting-414:18
*** iyamahat has quit IRC14:18
jed56acabot: regarding congress do we need to add some information in our documentation ?14:18
*** shaohe_feng has quit IRC14:18
*** yamahata has quit IRC14:18
acabotjed56 : for now, I think we need to clarify things in the commit msg for the big tent14:19
jed56okay14:19
acabotWatcher specs14:19
*** shaohe_feng has joined #openstack-meeting-414:19
acabothttps://review.openstack.org/#/c/312143/ needs review from core before EOW14:20
acabot#action acabot jwcroppe sballe_ review https://review.openstack.org/#/c/275474/14:20
*** daneyon has quit IRC14:20
acabotAirflow event based migration strategy spec needs reviews from core #link https://review.openstack.org/#/c/275474/14:20
acabot#action acabot jwcroppe sballe_ review https://review.openstack.org/#/c/275474/14:21
acabotGraph model describing virtual and physical elements in a data center & Consolidation of multiple Action-plans into a single one & Add Watcher Continuosly Optimization spec need reviews14:21
acabotwe need more reviewers on specs14:22
acabotdoes anyone wants to contribute on this ?14:22
gzhai2I can review 31214314:22
*** spotz_zzz is now known as spotz14:23
hvprash+114:23
*** mbound has quit IRC14:23
acabot#action gzhai2 hvprash review https://review.openstack.org/#/c/312143/14:23
*** vhoward has joined #openstack-meeting-414:23
sballe_+114:23
jed56acabot: i will read it14:23
xrolllahi all, I and alexchadin are working on "https://review.openstack.org/#/c/315551/". We've already implemented this to the Watcher, python-watcherclient and are working on the tests at the moment. Watcher-dashboard changes will be done later.14:24
sballe_xrollla: acabot I will take a look at 31555114:24
jinquani will review the Add Watcher Continuosly Optimization spec14:25
*** Guest92292 is now known as mgagne14:25
*** mgagne has quit IRC14:25
*** mgagne has joined #openstack-meeting-414:25
acabot#action sballe_ jinquan acabot review https://review.openstack.org/#/c/315551/14:25
vincentfrancoiseI'll try to review 315551 by EOW14:25
jwcroppereviewing 27547414:25
acabot#action vincentfrancoise review https://review.openstack.org/#/c/315551/14:26
*** sdake has quit IRC14:26
acabothvprash : is https://review.openstack.org/#/c/317130/ still in WIP ?14:26
hvprashacabot, Though the spec is currently WIP, can the core parallel review ? I may need some help understanding the code impact since this is first time I am doing this :)14:26
acabotok14:27
acabot#action jwcroppe sballe_ acabot review https://review.openstack.org/#/c/317130/ in WIP14:27
hvprashi have update the data model impact. was thinking to hhave an audit version table14:27
*** sdake has joined #openstack-meeting-414:27
*** Swami has joined #openstack-meeting-414:27
xrolllasballe_: thanks :)14:27
hvprashthx jwcroppe sballe_14:27
acabotCluster model objects wrapper work items are still missing #link https://review.openstack.org/#/c/287019/ (for a couple of weeks...)14:27
*** ecelik has quit IRC14:28
*** zenoway has quit IRC14:28
acabotjwcroppe : any update on https://review.openstack.org/#/c/287019/ ?14:28
*** shaohe_feng has quit IRC14:29
*** zenoway has joined #openstack-meeting-414:29
*** shaohe_feng has joined #openstack-meeting-414:29
acabot#info https://review.openstack.org/#/q/status:merged+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy has been merged last week14:30
*** linbing has quit IRC14:30
acabotthx vincentfrancoise for this great contribution14:30
edleafeacabot: on the commit message etherpad, how do you want suggested changes added? Strike out the old, and type in the new? Or some other way?14:30
sballe_vincentfrancoise: +114:31
acabotedleafe : Strike out the old, and type in the new14:31
*** mjturek1 has quit IRC14:31
edleafeacabot: ok14:31
*** jschwarz_ has joined #openstack-meeting-414:31
acabot2 strategies need reviews https://review.openstack.org/#/c/292188/ & https://review.openstack.org/#/c/297590/14:32
acabotwho wants to review ?14:32
sballe_me14:32
sballe_I will sepnd the afternon at it14:32
*** ninag has quit IRC14:32
jed56i just finish reviewing 29759014:32
acabot#action sballe_ review implemented strategies https://review.openstack.org/#/c/292188/ & https://review.openstack.org/#/c/297590/14:32
jed56i can review 29218814:32
*** ninag has joined #openstack-meeting-414:33
jinquanican review 29759014:33
acabot#action jed56 review https://review.openstack.org/#/c/292188/14:33
*** zenoway has quit IRC14:33
acabot#action jinquan review https://review.openstack.org/#/c/297590/14:33
*** jschwarz has quit IRC14:33
*** Liuqing has quit IRC14:33
acabotwe also need reviews on openstack-plugin #link https://review.openstack.org/#/q/status:open+project:openstack/python-watcherclient+branch:master+topic:bp/openstackclient-plugin14:34
acabotfor now, only vincentfrancoise & dtardivel have reviewed this code14:34
*** salv-orlando has joined #openstack-meeting-414:35
acabot#topic Blueprint/Bug Review and Discussion14:35
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:35
acabot#info Newton-1 release is due in 10 days so we need to start cleaning on-going BPs14:36
*** daneyon_ has quit IRC14:36
acabot#link https://launchpad.net/watcher/+milestone/newton-114:36
acabotxrollla : I dont think https://blueprints.launchpad.net/watcher/+spec/continuously-optimization will be implemented for Newton-1 right ?14:37
*** ninag has quit IRC14:37
*** jmckind has quit IRC14:37
acabotvincentfrancoise : do you think we will be able to deliver https://blueprints.launchpad.net/watcher/+spec/efficacy-indicator in 10 days ?14:38
*** jmckind has joined #openstack-meeting-414:38
vincentfrancoisehttps://blueprints.launchpad.net/watcher/+spec/efficacy-indicator is wal on its way but it depends on https://blueprints.launchpad.net/watcher/+spec/persistent-audit-parameters14:38
vincentfrancoisewell*14:38
vincentfrancoiseby EOW I should be able to push the code for review14:39
*** shaohe_feng has quit IRC14:39
vincentfrancoisebut the las piece which consist of comparing the strategies cannot be finished because of the dependency14:39
acabotok so I will keep it in Newton-1 for now14:39
vincentfrancoisebut the rest can be merged without persistent-audit-parameters <https://blueprints.launchpad.net/watcher/+spec/persistent-audit-parameters>14:40
*** shaohe_feng has joined #openstack-meeting-414:40
xrolllaacabot: I'll check with alexchadin now14:40
acabotwe really need more code reviewers until next week if we want to have 6 BPs implemented for Newton-114:40
seanmurphyi can help out14:41
seanmurphyi can do one14:41
acabotseanmurphy : do you want to review code as well ?14:41
seanmurphyi can do tis14:41
seanmurphythis14:41
dtardivelacabot: I will review also this one "Added Goals and Strategies to Dashbooard" #link https://review.openstack.org/#/c/301516/14:41
*** sdake_ has joined #openstack-meeting-414:42
acabot#action seanmurphy look at the list of BPs that need reviews on https://launchpad.net/watcher/+milestone/newton-114:42
*** javeriak has joined #openstack-meeting-414:42
sballe_acabot: we just need more reviwer. The more people that give a +1 the less work the cores have to do to give it +214:42
acabot#action dtardivel review https://review.openstack.org/#/c/301516/14:42
acabotsballe_ : yes, +1 is important !14:43
sballe_that is how it worked in Neutron at some points. The cores would do a quick review and basedon all the +1s whould 214:43
acabotsballe_ : we need more +1 :-D14:43
*** sdake has quit IRC14:43
vincentfrancoise+1 ^14:43
acabotseanmurphy : Voljtech has a bug in review https://bugs.launchpad.net/watcher/+bug/1564297 and there is really nothing to do to close it, can he work on it by EOW ?14:44
openstackLaunchpad bug 1564297 in watcher "Add missing cold (non-live) VM migration support" [Wishlist,Triaged] - Assigned to Vojtech Cima (cima-vojtech)14:44
xrolllaacabot: alexchadin considers that for review we will publish it to the next meeting14:44
*** haleyb_ is now known as haleyb14:44
*** daneyon has joined #openstack-meeting-414:44
acabotxrolla : ok in this case I will postpone it to Newton-214:44
acabot#action acabot move https://blueprints.launchpad.net/watcher/+spec/continuously-optimization to Newton-214:44
seanmurphy@acabot - he cannot - he is on vacation right now - we can look at it, but no guarantees it will be done by EOW14:45
acabotseanmurphy : please let me know if he can do it before end of next week (Newton-1 release)14:45
seanmurphyok - will do14:45
vincentfrancoiseseanmurphy: it's just some docstring to modify if I'm not mistaken14:45
*** majklkcz has quit IRC14:46
acabotgzhai2 : any update on https://blueprints.launchpad.net/watcher/+spec/optimization-threshold ?14:46
gzhai2acabot: in rebase.14:46
acabotgzhai2 : I see, can you rebase it ?14:46
gzhai2yes.14:47
acabotthx14:47
acabot#action rebase https://review.openstack.org/#/c/297556/14:47
acabot#action gzhai2 rebase https://review.openstack.org/#/c/297556/14:47
acabot#topic Open Discussion14:47
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:47
acabotwhich keyword should we use in OpenStack official CLI to identify Watcher service (currently infra-optim) ?14:47
acabotdtardivel : can you give us more details ?14:48
gzhai2acabot: Anybody request for OSIC nodes?14:49
dtardivelwith openstackcli, when we introduce  a new plugin, as watcher, we have to use a keyword to indicate command is linked to watcher14:49
vincentfrancoisee.g.14:49
dtardivelfor now, if the patchset proposed by vincentfrancoise we have : openstack infraoptim audit list14:49
*** shaohe_feng has quit IRC14:49
dtardivels/if/in14:49
edleafedtardivel: understood, but 'infra-optim' doesn't sound good14:49
* edleafe needs to think of a better one14:50
vincentfrancoiseedleafe: agreed14:50
jinquanedleafe +114:50
jed56+114:50
dtardivelthe question is: which keywork could be better for watcher command line in openstack CLI.14:50
*** shaohe_feng has joined #openstack-meeting-414:50
dtardivelvincentfrancoise proposed 'optimize'14:50
hvprash+114:50
sballe_+114:51
vincentfrancoiseI would suggest "optmization" to be more precise14:51
edleafedtardivel: yeah, 'optimize' is too subjective14:51
*** cloudtrainme has joined #openstack-meeting-414:51
acabotso it would be "openstack optimize audit list" sounds weird no ?14:51
vincentfrancoiseso it would look like "openstack optimization audit list"14:51
edleafemaybe 'balance'?14:51
jed56openstack watcher audit list ?14:51
sballe_balance is too general14:52
edleafejed56: you can't use code names14:52
jed56edleafe: I didn't know :)14:52
edleafesballe_: so is optimize :-P14:52
hvprashoptimiz* is better i think14:52
dtardivelcongress did it :) openstack congress ....14:52
edleafereally?14:52
sballe_then I vote for watcher14:52
vincentfrancoisecongress is actually the only one to do so14:53
sballe_we could quickly settle on optimize and trademark it14:53
vincentfrancoiseeveryone else is referring to the service it delivers14:53
sballe_so noboy else uses optimization or optimize14:53
jed56sballe_: +214:53
*** coolsvap has quit IRC14:53
vincentfrancoisesballe_: +2 that was my idea with optimization14:53
dtardivelsballe_: +214:53
hvprashsballe_: +214:53
edleafeI would expect some pushback from others on 'optimize'14:53
sballe_lol14:53
*** jwcroppe has quit IRC14:53
*** coolsvap has joined #openstack-meeting-414:54
acabot#startvote Keyword for OpenStack CLI optimize watcher optimization balance14:54
openstackUnable to parse vote topic and options.14:54
edleafenaming is hard14:54
acabot#startvote Keyword for OpenStack CLI ? optimize, watcher, optimization, balance14:54
openstackBegin voting on: Keyword for OpenStack CLI ? Valid vote options are optimize, watcher, optimization, balance.14:54
openstackVote using '#vote OPTION'. Only your last vote counts.14:54
vincentfrancoiseoptimizatoin would be coherent with the remit stated in the big tent commit message14:54
acabot#vote optimize14:55
sballe_#vote optimize14:55
dtardivel#vote optimization14:55
vincentfrancoise#vote optimization14:55
jed56#vote optimize14:55
jinquanirc://chat.freenode.net:6667/#vote optimize14:55
hvprash#vote optimize14:55
edleafe#vote optimize14:55
*** javeriak has quit IRC14:55
*** zenoway has joined #openstack-meeting-414:55
acabot#endvote14:56
openstackVoted on "Keyword for OpenStack CLI ?" Results are14:56
openstackoptimization (2): vincentfrancoise, dtardivel14:56
openstackoptimize (5): hvprash, edleafe, jed56, acabot, sballe_14:56
acabotgo for "optimize"14:56
sballe_+214:56
seanmurphy(we were just abt to vote optimize! ;-)14:56
acabot#action vincentfrancoise update Watcher keywork in CLI by "optimize"14:56
acabotseanmurphy : too slow ;-)14:56
sballe_lol14:57
hvprash:)14:57
acabotshould we already ask for an infra to OSIC before being part of the big tent ?14:57
acabotI think we should wait until we submit Watcher to the big tent14:57
gzhai2ok14:58
sballe_just submit for the big tent and in parallel ask for the cluster14:58
acabotbut gzhai2 said that there are a lot of requests14:58
sballe_gzhai2: has a request in for an internal cluster too14:58
sballe_gzhai2: what's the status on that?14:58
gzhai2pls. just give me test requirements and time.14:59
sballe_acabot: if we submit the request now we get inthe queue14:59
gzhai2I can try to ask for a 30+ nodes in internal cluster.14:59
acabotyes but I cannt mention that we will be in the big tent soon in the form..14:59
acabot30 nodes would be great14:59
*** sacharya has joined #openstack-meeting-414:59
*** shaohe_feng has quit IRC14:59
acabottime to end the meeting14:59
*** FrankZha- is now known as FrankZhang14:59
acabotthx15:00
vincentfrancoisebye15:00
*** matrohon has quit IRC15:00
jinquanbye15:00
acabot#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed May 18 15:00:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
sballe_acabot: let's go over the out ICM to discuss the 30+ nde15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-18-14.00.html15:00
jed56what are the characteristics of the nodes ?15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-18-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-18-14.00.log.html15:00
sballe_bye15:00
*** gzhai2 has left #openstack-meeting-415:00
*** jinquan has left #openstack-meeting-415:00
*** shaohe_feng has joined #openstack-meeting-415:00
*** Kevin_Zheng has quit IRC15:01
*** FrankZhang is now known as FrankZha-15:01
*** tonytan4ever has quit IRC15:01
*** FrankZha- is now known as FrankZhang15:02
*** sridhar_ram has quit IRC15:02
*** anilvenkata has quit IRC15:04
*** mfranc213_ has quit IRC15:04
*** njohnston_ has quit IRC15:04
*** fawadkhaliq has quit IRC15:04
*** petergurinov has left #openstack-meeting-415:04
*** numans has quit IRC15:05
*** banix has quit IRC15:05
*** cbouch_ has joined #openstack-meeting-415:05
*** salv-orlando has quit IRC15:05
*** cbouch__ has quit IRC15:05
*** Sukhdev has joined #openstack-meeting-415:06
*** armax has joined #openstack-meeting-415:06
*** mfranc213 has joined #openstack-meeting-415:07
*** shaohe_feng has quit IRC15:10
*** ninag has joined #openstack-meeting-415:10
*** shaohe_feng has joined #openstack-meeting-415:10
*** daneyon has quit IRC15:12
*** lrensing has quit IRC15:12
*** daneyon has joined #openstack-meeting-415:13
*** ninag has quit IRC15:14
*** ninag has joined #openstack-meeting-415:18
*** fwdit has quit IRC15:18
*** shaohe_feng has quit IRC15:20
*** shaohe_feng has joined #openstack-meeting-415:21
*** ninag has quit IRC15:21
*** ajmiller has joined #openstack-meeting-415:21
*** ninag has joined #openstack-meeting-415:21
*** xrollla has quit IRC15:23
*** fawadkhaliq has joined #openstack-meeting-415:23
*** fawadkhaliq has quit IRC15:23
*** avarner has joined #openstack-meeting-415:23
*** ajmiller_ has joined #openstack-meeting-415:24
*** njohnston__ is now known as njohnston15:25
*** itisha has joined #openstack-meeting-415:26
*** user154752_ has quit IRC15:27
*** ajmiller has quit IRC15:27
*** jschwarz_ has quit IRC15:28
*** daneyon has quit IRC15:30
*** shaohe_feng has quit IRC15:30
*** mhoppal has joined #openstack-meeting-415:30
*** mhoppal has left #openstack-meeting-415:31
*** shaohe_feng has joined #openstack-meeting-415:31
*** salv-orlando has joined #openstack-meeting-415:31
*** user154752_ has joined #openstack-meeting-415:32
*** belmoreira has quit IRC15:32
*** Sukhdev has quit IRC15:34
*** mbound has joined #openstack-meeting-415:34
*** fawadkhaliq has joined #openstack-meeting-415:34
*** avarner has quit IRC15:35
*** gangil has joined #openstack-meeting-415:36
*** schwarzm has joined #openstack-meeting-415:38
*** ajmiller_ has quit IRC15:38
*** Hunner_ is now known as Hunner15:39
*** mhoppal has joined #openstack-meeting-415:39
*** mhoppal has left #openstack-meeting-415:39
*** shaohe_feng has quit IRC15:40
*** majklkcz has joined #openstack-meeting-415:41
*** shaohe_feng has joined #openstack-meeting-415:41
*** salv-orlando has quit IRC15:41
*** ajmiller has joined #openstack-meeting-415:42
*** salv-orlando has joined #openstack-meeting-415:42
*** avarner has joined #openstack-meeting-415:42
*** ninag has quit IRC15:43
*** nkrinner is now known as nkrinner_afk15:43
*** jmckind_ has joined #openstack-meeting-415:44
*** user154752_ has quit IRC15:45
*** jmckind has quit IRC15:48
*** schwarzm has quit IRC15:48
*** shaohe_feng has quit IRC15:51
*** bpokorny has joined #openstack-meeting-415:51
*** bpokorny has quit IRC15:52
*** vhoward has quit IRC15:52
*** blogan_ is now known as blogan15:52
*** shaohe_feng has joined #openstack-meeting-415:52
*** tonytan4ever has joined #openstack-meeting-415:53
*** uck has joined #openstack-meeting-415:53
*** ninag has joined #openstack-meeting-415:54
*** lakshmiS has joined #openstack-meeting-415:55
*** Rockyg has joined #openstack-meeting-415:55
*** Sukhdev has joined #openstack-meeting-415:55
*** lhartal has quit IRC15:56
*** daneyon has joined #openstack-meeting-415:56
*** bpokorny has joined #openstack-meeting-415:57
*** daneyon has quit IRC15:57
*** ninag has quit IRC15:58
*** daneyon has joined #openstack-meeting-415:58
*** ninag has joined #openstack-meeting-415:58
*** mbound has quit IRC16:00
*** shaohe_feng has quit IRC16:01
*** shaohe_feng has joined #openstack-meeting-416:02
*** brunograz has quit IRC16:02
*** minwang2 has joined #openstack-meeting-416:03
*** ninag has quit IRC16:04
*** ninag has joined #openstack-meeting-416:04
*** hvprash_ has joined #openstack-meeting-416:05
*** keekz has joined #openstack-meeting-416:08
*** hvprash has quit IRC16:08
*** ninag has quit IRC16:09
*** ninag has joined #openstack-meeting-416:10
*** shaohe_feng has quit IRC16:11
*** mbound has joined #openstack-meeting-416:11
*** shaohe_feng has joined #openstack-meeting-416:12
*** mbound has quit IRC16:13
*** mbound has joined #openstack-meeting-416:13
*** vincentfrancoise has quit IRC16:15
*** ninag has quit IRC16:15
*** gangil has quit IRC16:16
*** iyamahat has joined #openstack-meeting-416:16
*** nihilifer has joined #openstack-meeting-416:20
*** anteaya has quit IRC16:21
*** shaohe_feng has quit IRC16:21
*** pbourke-mobile2 has joined #openstack-meeting-416:22
*** jmckind_ has quit IRC16:23
*** gangil has joined #openstack-meeting-416:24
*** shaohe_feng has joined #openstack-meeting-416:24
*** inc0 has joined #openstack-meeting-416:26
*** ninag has joined #openstack-meeting-416:27
*** IlyaG has joined #openstack-meeting-416:27
*** zenoway has quit IRC16:27
*** mandre has joined #openstack-meeting-416:28
*** zenoway has joined #openstack-meeting-416:28
*** Jeffrey4l has joined #openstack-meeting-416:28
*** mlima has joined #openstack-meeting-416:29
*** eghobo has joined #openstack-meeting-416:29
*** unicell1 has quit IRC16:30
*** gangil has quit IRC16:30
*** vhosakot has joined #openstack-meeting-416:30
*** nmadhok has quit IRC16:30
*** sdake_ has quit IRC16:31
*** linbing has joined #openstack-meeting-416:31
*** sdake has joined #openstack-meeting-416:31
sdake#startmeeting kolla16:31
sdake#topic rollcalls16:31
openstackMeeting started Wed May 18 16:31:59 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:32
*** openstack changes topic to " (Meeting topic: kolla)"16:32
openstackThe meeting name has been set to 'kolla'16:32
*** openstack changes topic to "rollcalls (Meeting topic: kolla)"16:32
inc0o/16:32
*** shaohe_feng has quit IRC16:32
vhosakoto/16:32
mandre\o/16:32
Jeffrey4lo/16:32
nihilifer\o16:32
*** shaohe_feng has joined #openstack-meeting-416:32
eghoboo/16:32
*** zenoway has quit IRC16:32
jpeelerhi16:32
*** spzala has joined #openstack-meeting-416:33
*** sridhar_ram has joined #openstack-meeting-416:33
*** lakshmiS has quit IRC16:33
mlima\o/16:33
*** nmadhok has joined #openstack-meeting-416:33
*** lakshmiS has joined #openstack-meeting-416:33
coolsvaphello16:33
sdakeo/16:33
sdake#topic announcements16:33
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:34
*** ninag has quit IRC16:34
*** ddieterly is now known as ddieterly[away]16:34
sdake1. I am working on securing us space for midcycle at Ansible HQ in Durham16:34
*** ninag has joined #openstack-meeting-416:34
pbourke-mobile2Hi16:34
sdakeif that falls though ryan has suggested boston as a possibility16:34
sdakei will know by friday if that has fallen through16:34
sdake2. we are getting something like 130 nodes to do kolla scale testing with16:35
sdakeprovided by osic16:35
pbourke-mobile2cool16:35
sdakeinc0  mind adding anything on that topic?16:35
*** linbing has quit IRC16:35
inc0well16:35
inc0it's not official yet16:35
vhosakotyes, Boston is great... near my house! :)16:35
sdakeoh i thought it was16:36
inc0but there is good possibility that we'll get 132 physical nodes to perform tests we want for 3 weeks16:36
vhosakotsdake: is 130 nodes at the gate ?16:36
*** rhallisey has joined #openstack-meeting-416:36
rhalliseyhey16:36
*** Swami has quit IRC16:36
sdakevhosakot no its bare metal accesible via internets16:36
rhalliseysorry a little late16:36
inc0vhosakot, no, its 130 powerful physical servers we'll have ipmi access to16:36
*** njohnston has quit IRC16:37
sdakeby powerful he means 2 xeon processor 256gbram+16:37
dave-mccowano/16:37
vhosakotinc0: sdake: how to we use it ? for dev/unit-testing/local scale testing ?16:37
inc0so we can deploy kolla on them, deploy thousands of vms on it and deploy multi-k kolla on vms;)16:37
sdakeno we have it for a short period - 3 weeks16:37
inc0we need to utilize this time to maximum16:37
sdakei think we need to have further discussions on what we wwant to do with that gear16:37
*** jmckind has joined #openstack-meeting-416:37
sdakeso we can brainstorm in the main topic16:38
*** sridhar_ram has quit IRC16:38
sdakeonto other announcements16:38
vhosakotdeploy multinode on that and run some rally tests16:38
inc0so let's prep tests beforehand, get people working around the clock (thank you timezones) and squeeze as much info as we can16:38
sdakeok lets brainstorm later16:38
mandresounds like a plan16:38
sdake3. mlima is up for core reviewer, please vote or abstain - if you plan to abstain please let me know personally so I wont be expecting your vote one way or another tia ;)16:39
vhosakotcool, later.. need to discuss how to bare-metal boot them first before deployng kolla on them16:39
sdake#topic newton-116:39
*** openstack changes topic to "newton-1 (Meeting topic: kolla)"16:39
*** ddieterly[away] is now known as ddieterly16:40
sdake#ink http://releases.openstack.org/newton/schedule.html16:40
*** ninag has quit IRC16:40
sdakeeveryone has had a nice long two week vacation hopefully after summit16:40
sdakeits time to get to work on our objectives for newton16:40
sdakeeveryone has seen the mailing list mail regarding our commitments made at summit16:41
sdakeI'd like to atleast do that work ;)16:41
sdakenewton 1 is scheduled for the end of May16:41
sdakewe have about 1-2 weeks left, and we haven't done alot of work16:41
*** vishnoianil has joined #openstack-meeting-416:41
sdakethis is normal, as our work is backloaded because we are a relesae:cycle-trailing project16:42
*** shaohe_feng has quit IRC16:42
sdakealso we have a general commitment to the openstack community to release z streams16:42
sdakeprojects typically do these every 45 days16:42
sdakearound milestone deadlines16:42
sdakewe have a slew of bugs in newton-116:43
*** shaohe_feng has joined #openstack-meeting-416:43
sdakewhat i'd suggest is working on bugs that are in newton-1 that are targeted for backporting16:43
sdakeor working on any of our many objectives16:43
sdakeanyone have any questions or is blocked in any way?16:43
vhosakotwhat/where are the bugs targeted for newton-1 ?16:44
coolsvapvhosakot, https://launchpad.net/kolla/+milestone/newton-116:44
vhosakotcool.. thanks!16:44
sdake#link https://launchpad.net/kolla/+milestone/newton-116:44
coolsvapi for one am waiting for some resolution to the rabbitmq but so that we can have some reliance on gates16:44
sdakeby "slew" I mean 200+ :)16:45
coolsvapits really big list16:45
sdakecoolsvap ya both Jeffrey4l and I are working on that porblem16:45
vhosakotit has bp's + bugs16:45
coolsvapsdake, yes16:45
sdake#topic kolla-kubernetes bootstrapping16:46
*** openstack changes topic to "kolla-kubernetes bootstrapping (Meeting topic: kolla)"16:46
sdakeso I'm not sure what Ryan had in mind here16:46
sdaketake it away :)16:46
rhallisey:)16:46
rhalliseyI wanted to have a discussion about bootstrapping in kolla-kube16:46
rhalliseyhttps://review.openstack.org/#/c/304182/16:46
rhalliseylines 79-10816:47
*** ninag has joined #openstack-meeting-416:47
rhalliseythere are 3 scenarios around bootstrapping16:47
rhalliseyI'll highlight the problem with the main discussed aproach16:47
rhalliseythe idea of having a bootstrap task in kolla-kubernetes may be problematic16:48
rhalliseybecause kubernetes handles upgrades in a single operation16:48
rhalliseyscale down -> scale up16:48
rhalliseyif we don't have db_sync built into our container, we can't use kubernetes to handle service upgrades.  It would have to be done by ansible16:49
rhalliseyor some other orchestration16:49
sdakeduring upgrades, kubernetes can't run a special container?16:49
sdakethere surely must be a way to do some migation work16:49
vhosakotrhallisey: so, can we use kubernetes upgrade to do bootstrapping (initialize the db and create user) ?16:50
rhalliseythat would require some orchestreation16:50
*** fawadkhaliq has quit IRC16:50
inc0non trivial one as well16:50
sdakeisn't there a jobs object?16:50
rhalliseyya16:50
*** pbourke-mobile-3 has joined #openstack-meeting-416:50
nihiliferrhallisey: so,  do you see any alternatives more than implementing all the "bootstrap" inside start scripts?16:50
inc0technically we could run db_sync every time16:50
rhalliseysdake, there is, but we can't just run a job when kubernetes thinks it's time to upgrade16:51
*** fawadkhaliq has joined #openstack-meeting-416:51
*** seanmurphy has quit IRC16:51
nihiliferand run every time of course16:51
sdakesounds like a  gap in the kubernetes implementaiton16:51
eghoborhallisey: why not take you initial approach and start the job which will do database upgrade16:51
rhalliseynihilifer, I don't other then orchestration and not using native kubernetes16:51
*** Guest37264 is now known as melwitt16:51
*** nmadhok has quit IRC16:51
sdakeimo we should try to use native k8s as much as possible for kolla-kubernetes16:51
vhosakotyes.. good point16:52
pbourke-mobile-3Could you optionally bootstrap + start in one go16:52
*** ninag has quit IRC16:52
sdakeand if it has gaps we should feed those to upstream to fix them16:52
rhalliseypbourke, yes16:52
nihiliferyes, and if not possible - try to push for features in k8s (i'll have some "announce" on that on the end of meeting ;) )16:52
rhalliseythe solution I'm talking about is:16:52
*** shaohe_feng has quit IRC16:52
*** ninag has joined #openstack-meeting-416:52
*** ninag has quit IRC16:52
rhalliseybootstrapping will bootstrap the db with a special container in the pod.  Then the service runs after16:52
*** ninag has joined #openstack-meeting-416:53
*** banix has joined #openstack-meeting-416:53
*** shaohe_feng has joined #openstack-meeting-416:53
rhalliseyupgarde will do a db_sync in a special container, then services get scaled back up16:53
sdakerhallisey seems like this is more of a ml discussion :)16:53
inc0other issue is, upgrade is more complex than just db_sync16:53
rhalliseyinc0, agreed16:53
inc0for example nova requires some more logic to make it rolling16:53
sdakei'd focus on getting AIO deployed first, upgrade second ;)16:53
rhalliseysdake, ya I agree. Just wanted to highlight this for everyone16:54
sdakethere are a slew of problems with just deploying k8s16:54
eghoborhallisey: could you elaborate pod vs job?16:54
rhalliseyso keep an eye on the spec16:54
*** pbourke-mobile2 has quit IRC16:54
rhalliseyeghobo, pod is a group of running containers. A job is a task the kubernetes wil execute until completion16:54
*** iyamahat has quit IRC16:54
*** fawadkhaliq has quit IRC16:55
rhalliseysdague, ya i agree. I just don't want to make the wrong decision with bootstrapping and have to remake it with upgrades16:55
eghoborhallisey: i know it ;)16:55
*** ninag has quit IRC16:55
sdakerhallisey i think what we need in the upgrade construct is the ability to run a job16:55
*** iyamahat has joined #openstack-meeting-416:55
sdakerhallisey its ok to experiment, i expec thits project will take a long timee to mature16:55
*** ninag has joined #openstack-meeting-416:55
eghoborhallisey: i am curious why do you need upgrade through special pod vs job16:55
sdakelook at all the changes we went through with kolla16:55
rhalliseysdake, ya a job would be ideal.  It would tie it well to inc0's point16:55
sdakesince the beginning we hvae changed architectures atleasst 4 time :)16:56
rhalliseyeghobo, it wouldn't be a special pod. It would be the same pod used during a deployment16:56
vhosakotrhallisey: so, are you saying the native k8s 'upgrade' job can be used to bootstrap services, and a separate task bootstrap.yml is not needed ?16:56
*** Swami has joined #openstack-meeting-416:56
*** Sukhdev has quit IRC16:57
rhalliseyvhosakot, I'm saying that we need to build into these tasks: db_sync, <some upgrade magic> into the deployment template16:57
*** alexchadin has joined #openstack-meeting-416:57
sdake#action rhallisey to start thread related to upgrade of kolla-kubernetes (the openstack part) :)16:57
rhalliseythe deployment template describe the pod16:57
vhosakotah ok16:57
rhalliseysounds good sdake thanks16:57
sdakesure16:58
rhalliseyjust wanted to raise awareness16:58
sdake#topic ansible 2.016:58
*** openstack changes topic to "ansible 2.0 (Meeting topic: kolla)"16:58
sdakewe want it all, and we want it now16:58
rhallisey#link https://blueprints.launchpad.net/kolla/+spec/ansible216:58
Jeffrey4lthis PS works. https://review.openstack.org/31742116:58
rhalliseynice Jeffrey4l16:58
Jeffrey4lmay need some small works.16:58
sdakecool Jeffrey4l already did the job16:59
rhalliseyso based off the patch above, people can start grabbing services  ans converting the tasks16:59
inc0rhallisey, not really, you don't need to convert anything16:59
inc0plays works as used to16:59
rhalliseyoh that will work as is16:59
*** ninag has quit IRC17:00
inc0yup17:00
rhalliseyexcellent17:00
Jeffrey4lcorrect. the gate is green now.17:00
rhalliseycool nice Jeffrey4l17:00
vhosakotnice Jeffrey4l!17:00
inc0however we can do more, ansible 2 have some stuff that we may use17:00
rhalliseygot nothing else17:00
inc0refactor our modules to be more ansible 2'ish17:00
sdakeya the execution strategies17:00
pbourke-mobile-3I think theres some todos around "once we have ansible 2"17:00
rhalliseythought there would need to be some task changing17:00
rhalliseyok well whatever they are, can they be highlighted in the blueprint?17:01
*** sarob has joined #openstack-meeting-417:01
pbourke-mobile-3Set an action and ill have a look17:01
sdakeneed folks to add work items to the blueprint17:01
vhosakotrefactor meaning use the new modules in Ansible 2.0 ?17:01
sdake#action eveyrone to add their ideas for ansible 2.0 to work items in the ansible2 blueprint17:01
vhosakotcool17:02
pbourke-mobile-3Thanks!17:02
sdakevhosakot we are never using ansible's docker module again17:02
sdaketoo painful17:02
sdakei prefer to be in control of our own destiny17:02
vhosakotcool17:02
*** ninag has joined #openstack-meeting-417:02
*** shaohe_feng has quit IRC17:02
*** hvprash has joined #openstack-meeting-417:03
sdake#topic gating is busted17:03
*** openstack changes topic to "gating is busted (Meeting topic: kolla)"17:03
sdakecentos in some way is broken17:03
sdakei think jeffrey4l has a fix17:03
sdakeJeffrey4l mind describing what you knwo about the issue17:04
Jeffrey4lyes. i am still making some test for this.17:04
Jeffrey4lPS 30 show the current issue https://review.openstack.org/#/c/315860/3017:05
*** ddieterly is now known as ddieterly[away]17:05
Jeffrey4lthe hostname is not changed as expected on the centos gate.17:05
*** shaohe_feng has joined #openstack-meeting-417:05
Jeffrey4li have no idea why. :(17:05
Jeffrey4lbecause i can not reproduce it locally.17:06
sdakeour speculation is that ansible hostname module is broken17:06
sdakepossibly related to selinux17:06
*** hvprash_ has quit IRC17:06
sdakebecause shell sudo hostname change works right Jeffrey4l ?17:06
coolsvapi am thinking on similar lines and similarly i am not able to reproduce it locally17:07
Jeffrey4lsdake, correct.17:07
sdakeJeffrey4l ok well lets unblock the gate asap17:07
Jeffrey4lyes.17:07
sdakeand if you want to further debug - revert the patch in your review above17:07
sdake(the patch that fixes teh problem)17:07
sdakethat way you can debug if you like17:07
Jeffrey4lanyway, I will push the workaround soon.17:08
*** tonytan4ever has quit IRC17:08
*** unicell has joined #openstack-meeting-417:08
sdakeJeffrey4l if you can get a shell sudo up for review, and it passes the gate, i'd like quick reviews on it today pls :)17:08
Jeffrey4lroger.17:08
sdakeit is sort of blocking all dev17:08
sdakebecause our core team rightly is trained not to ack changes that don't pass the gate17:08
Jeffrey4li am working on that. the latest PS is trying to fix the gate.17:09
sdake#topic threat analysis17:09
*** openstack changes topic to "threat analysis (Meeting topic: kolla)"17:09
sdakeat summit we had a 4 hour threat analysis session17:09
sdakewe got about half way done17:09
sdakewe identified all the modes of operation of our containers17:09
sdakeand identified the special snowflakes17:09
sdakeif your on this list:17:10
sdake#link https://launchpad.net/~kolla-coresec/+members17:10
sdakeand no longer want to participate in the obtaining the VMT tag because you have other responsibilites now, pleaes let me know asap17:10
sdakeso i can recruit others17:10
sdakewe need a team of 5 people17:10
sdakei'd like people on this team to prioritize this work ahead of other work17:11
sdakeany questions mandre nihilifer inc0 rhallisey ?17:11
*** ninag has quit IRC17:11
sdakethe next step is for everyone on that list to attend the next openstack security meeting17:11
sdakeand attend for 4-6 weeks while we finish the job on TA17:11
sdakeafter our VMT is done, if anyone would like to act as liason to the VMT and security teams (in place of me) I would super appreciate a volunteer17:12
inc0where can we find list of stuff left to be done?17:12
sdakeI am super overloaded with all the liasion stuff going on inside openstack atm17:13
*** shaohe_feng has quit IRC17:13
sdakeinc0 there is no list - something we need to define in the security meeting thursday :)17:13
*** shaohe_feng has joined #openstack-meeting-417:13
inc0ok17:13
sdakeor altnerively on the mailing list17:13
*** gangil has joined #openstack-meeting-417:13
sdakewe need to make some sequence diagrams17:13
sdakeone is already made17:13
sdakeand then someone needs to wrap it up in ap retty document17:14
sdakeI'll be happy to do the wrapping17:14
sdakebut need assistance on the diagrams17:14
mandresecurity team meeting happening on Thu 17:00 UTC17:14
mandrehttp://eavesdrop.openstack.org/#Security_meeting17:14
sdake#topic open discussion17:15
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:15
sdakenihilifer you had soehting you wanted to announce?17:15
*** ninag has joined #openstack-meeting-417:15
sdakeanyone else have open items they would like to discuss?17:16
nihiliferyes. i'd like to say that i will participate in k8s community itself - which includes writing code as well17:16
sdakenihilifer so I think what this means is you will be less involved in kolla17:16
nihiliferso if you have any features you would like to see in k8s, don't hesitate to contact me17:16
*** ninag_ has joined #openstack-meeting-417:16
rhalliseynick-ma, oh sweet17:16
inc0cool17:16
rhalliseynihilifer, nic17:17
rhalliseynice17:17
rhalliseynick-ma, sorry17:17
*** Rockyg has quit IRC17:17
rhalliseyso I talked to an ansible guy I know17:17
nihiliferyes, unfortunately it means i'll be less active in kolla, but i'll try to keep some reviews and commits17:17
nihiliferto not outstand badly from the core team ;)17:17
coolsvapnihilifer, nice all the best!17:17
sdakenihilifer cool - well thanks for your service thus far, and hope you can stick with it, if not I totally understand the two projects at one time thing17:17
rhalliseynihilifer, cool :)17:17
vhosakotnihilifer: cool, and all the best!17:18
*** pbourke-mobile-3 has quit IRC17:18
sdakenihilifer you are a pleasure to work with17:18
sdakebut lets not send him off that easy ;)17:18
rhalliseyansible: ansible guy I know was interested in bringing in our work around the docker module into 2.x17:18
sdakerhallisey interesting17:18
*** hvprash has quit IRC17:18
sdakeexpand plz17:18
nihiliferthanks guys :)17:18
*** hvprash has joined #openstack-meeting-417:19
rhalliseyI spoke to him and summit. He's someone that use to work in openstack17:19
rhalliseyI can start a thread with him17:19
rhalliseygauge his interest17:19
sdakedoes this ansible person have a name?17:19
rhalliseyRyan.. forget his last name17:19
mandreBrady17:19
rhalliseyyes17:19
sdakeyup I hired him17:20
sdakeknow him well :)17:20
rhalliseyya well he was interested in it17:20
*** ninag has quit IRC17:20
rhalliseyso we could work with him if we want to move back to anisble maintaining the module17:20
*** ninag_ has quit IRC17:20
rhalliseywell they do already, but fixing the issues we need17:21
sdakei am not super hot on that idea17:21
sdakefool me once, shame on you fool me twice shame on me17:21
sdakeor something ;)17:21
inc0well tbh there is small chance for us to be this screwed17:21
rhalliseywell I figured I would just throw it out there17:22
inc0as worst case scenerio we can freeze docker version on 1.10 and ansible on whatever is working17:22
sdakerhallisey we got super screwed over by docker and ansible when nobody would fix the mess made17:22
inc0we have features we need already17:22
*** iyamahat has quit IRC17:22
sdakeand it is alot of work to port back over to the ansible modules17:22
sdakewith little  gain17:22
sdakeand alot of pain17:22
rhalliseysdake, we tried to fix the issues and no one listened, but now we do17:22
rhalliseyhave some one that will listen17:23
sdakei get there is an environmental change17:23
sdakemy wife harasses me about  it daily17:23
rhalliseyidk just a thought17:23
*** shaohe_feng has quit IRC17:23
inc0worth to consider imho17:23
sdakebut the docker module is too important to us to be left to others17:23
*** xuan has quit IRC17:23
inc0but well, sdake is true, we'd need to recreate most of tasks17:23
sdakei really dont like pinning17:23
*** shaohe_feng has joined #openstack-meeting-417:23
rhalliseysdake, I mean ansible gains when they make kolla happy17:23
Jeffrey4li do not think it is a good idea back to use the ansible docker17:24
*** xuan has joined #openstack-meeting-417:24
sdakei am fully satisified with ansible17:24
sdakei am not satisified with one cat maintaining modules on which our entire community depends17:24
sdakewhat if he gets hit by an airbus?17:24
rhalliseynot saying it would him, but rather the community may care17:24
Jeffrey4lwe add much feature on kolla_docker.py which ansible guys will not accept it, i think.17:24
rhalliseywho knows17:25
inc0getting hit by airbus is awfully specific way to dier17:25
rhalliseys/would him/would be him17:25
inc0boeings are equally dangerous17:25
vhosakotif we use ansible's docker module, will it replace kolla_docker.py that uses the docker python module.  kolla_docker.py is great17:25
sdakethere is zero wrong with kolla_docker.py17:26
sdakeit does exactly what we need17:26
sdakeand we know how to maintain it17:26
vhosakotyep.. it is awesome17:26
sdakeit is easy to extend17:26
*** sridhar_ram has joined #openstack-meeting-417:26
*** alexchadin has quit IRC17:26
sdakeand it does precisely the job we require and nothing more17:26
vhosakotyes, agreed17:27
sdakelsiten I am as hard core open source as anyone out there17:27
vhosakotwas kolla_docker.py written because ansible's docker module is bad ?17:27
sdakein this case, pragmatism wins17:27
inc0vhosakot, correct17:27
sdakevhosakot broken and unmaintained17:27
sdakecompletely broken17:27
vhosakotah ok..17:27
inc0this bit backport was caused by this17:28
inc0ultimately17:28
sdakeya the charlie foxtrot of the liberty rebranching was caused by ansible not maintaing the docker module properly17:28
vhosakotah I see17:28
Jeffrey4lkolla_docker.py also has a `common_option` param, which reduce the ansible code lines of kolla.17:28
*** boden has joined #openstack-meeting-417:28
sdakeok 1 minute ;)17:29
sdakethanks for coming folks17:29
sdakelets get cracking on newton17:29
*** sarob has quit IRC17:29
*** hvprash_ has joined #openstack-meeting-417:29
sdakewe have already done alot of work in n1 prior to summit17:29
sdaketime to get back to work :)17:29
sdake#endmeeting17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed May 18 17:29:45 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-05-18-16.31.html17:29
vhosakotbye17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-05-18-16.31.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-05-18-16.31.log.html17:29
*** vhosakot has left #openstack-meeting-417:29
*** rhallisey has left #openstack-meeting-417:30
*** mlima has left #openstack-meeting-417:30
*** mandre has left #openstack-meeting-417:30
*** pcm_ has joined #openstack-meeting-417:30
*** unicell has quit IRC17:30
*** unicell1 has joined #openstack-meeting-417:30
dougwig#startmeeting networking_lib17:31
openstackMeeting started Wed May 18 17:31:12 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
*** openstack changes topic to " (Meeting topic: networking_lib)"17:31
dougwigo/17:31
openstackThe meeting name has been set to 'networking_lib'17:31
bodeno/17:31
HenryGo/17:31
dougwig#topic Status17:31
*** openstack changes topic to "Status (Meeting topic: networking_lib)"17:31
*** nmadhok has joined #openstack-meeting-417:32
dougwigmy head has been under a rock this past week, so where are we at?17:32
HenryGI don't have anything new for today, except it might be a good idea to make a minor release.17:32
*** hvprash has quit IRC17:32
bodenI have 2 things... Do we need to discuss the "minor release" first?17:32
dougwigok, do you want me to do that, or do you want to learn how?17:32
HenryGMostly because of the IPv6 constants changes.17:32
HenryGI am always willing to learn.17:33
bodenmore than happy to learn17:33
*** sarob has joined #openstack-meeting-417:33
*** vishnoianil has quit IRC17:33
*** shaohe_feng has quit IRC17:33
*** s3wong has joined #openstack-meeting-417:34
dougwigreleases are a matter of filing one of these: https://review.openstack.org/#/c/306575/ , and then ask ihar or armax to ack it.17:34
*** xuan has quit IRC17:34
*** eghobo has left #openstack-meeting-417:34
dougwigjust don't do them *too* often.17:34
*** shaohe_feng has joined #openstack-meeting-417:34
dougwigwhat are your items, boden?17:35
bodenlast week we talked about investigating moving some of the base agent code into lib17:35
bodenI did a quick write-up here: https://etherpad.openstack.org/p/neutron_lib_base_agent17:35
bodenSince I'm new, I figured it would be good to get your comments... Unless you want me to lead with code (fine by me)17:36
dougwigwhoa, nice writeup.17:36
bodenso either you can try to find time to review that doc + comment, or I can just jump right into some code17:37
bodenwhatever you prefer17:37
HenryGI need time to read it, but don't let that stop you from submitting some code17:38
bodenok sounds good... I jump into some code and keep an eye on the doc as well17:38
bodenthe other item was that I left some comments on https://review.openstack.org/#/c/303867/17:39
dougwigyes, i'll also read it after lunch.17:39
dougwigbut don't let that stop you from code.17:39
dougwigwhat was your other item?17:39
boden^^17:39
dougwigoh, right.  was coding until midnight, i'm foggy.  :)17:39
HenryGYeah, I need to rebase that patch on master now that the DB stuff is being re-thought.17:39
*** ninag has joined #openstack-meeting-417:40
HenryGthanks for your comments there boden17:40
bodenok... if you run low on bandwidth, I'm more than happy to try that "rebase"17:40
bodenwelcome17:40
dougwigfeel free to jump in on rebases.  ping the person on irc if they're online, but if not, just go for it.17:41
dougwigthat's my philosophy, anyway17:42
bodenok, I didn't know if that was kosher17:42
bodenthat's all the status I have17:42
HenryGLet me give it a first pass today, since it is rebase on both lib and core neutron.17:42
bodenI do have a question tho, from our previous topic17:42
*** iyamahat has joined #openstack-meeting-417:42
bodenback on the neutron-lib release topic... once that "release version" patch merges, automation automatically builds + publishes a new neutron-lib to pypi?17:43
*** sridhar_ram has quit IRC17:43
*** anilvenkata has joined #openstack-meeting-417:43
dougwigboden: correct.  it usually happens in minutes.17:43
*** spzala has quit IRC17:43
bodenok nice17:43
*** spzala has joined #openstack-meeting-417:43
dougwigjust be careful of semver.  if we made minor tweaks, make it 0.1.1.  if we added features, it must be 0.2.017:43
*** shaohe_feng has quit IRC17:43
*** shaohe_feng has joined #openstack-meeting-417:44
dougwigalright, any final words, or let's get to coding and reviewing boden's doc.17:44
bodennothing from me17:45
*** ninag has quit IRC17:45
HenryGme neither17:45
*** vhoward has joined #openstack-meeting-417:45
*** ninag has joined #openstack-meeting-417:46
*** dshakhray has quit IRC17:46
*** Jeffrey4l has quit IRC17:46
dougwig#endmeeting17:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:47
openstackMeeting ended Wed May 18 17:47:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:47
dougwigalrighty then17:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-05-18-17.31.html17:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-05-18-17.31.txt17:47
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-05-18-17.31.log.html17:47
*** javeriak has joined #openstack-meeting-417:48
*** boden has left #openstack-meeting-417:49
*** cbouch_ has quit IRC17:50
*** piet has joined #openstack-meeting-417:51
*** shaohe_feng has quit IRC17:54
*** LouisF has joined #openstack-meeting-417:54
*** shaohe_feng has joined #openstack-meeting-417:55
*** pvaneck has joined #openstack-meeting-417:55
*** IlyaG has quit IRC17:58
*** uck has quit IRC17:58
*** dtardivel has quit IRC18:00
*** pcm_ has left #openstack-meeting-418:00
*** yamahata has joined #openstack-meeting-418:00
*** unicell1 has quit IRC18:00
*** unicell has joined #openstack-meeting-418:00
*** bpokorny has quit IRC18:00
*** user154752_ has joined #openstack-meeting-418:02
*** bpokorny has joined #openstack-meeting-418:03
*** shaohe_feng has quit IRC18:04
*** shaohe_feng has joined #openstack-meeting-418:04
*** ddieterly[away] has quit IRC18:05
*** avarner has quit IRC18:06
*** jwagner is now known as jwagner_lunch18:08
*** Sukhdev has joined #openstack-meeting-418:13
*** shaohe_feng has quit IRC18:14
*** shaohe_feng has joined #openstack-meeting-418:15
*** evgenyf has joined #openstack-meeting-418:17
*** tonytan4ever has joined #openstack-meeting-418:18
*** coolsvap has quit IRC18:20
*** bpokorny has quit IRC18:21
*** banix has quit IRC18:24
*** amit213 has quit IRC18:24
*** shaohe_feng has quit IRC18:24
*** shaohe_feng has joined #openstack-meeting-418:25
*** vishnoianil has joined #openstack-meeting-418:25
*** amit213 has joined #openstack-meeting-418:27
*** isq has joined #openstack-meeting-418:27
*** ddieterly has joined #openstack-meeting-418:27
*** bpokorny has joined #openstack-meeting-418:28
*** zenoway has joined #openstack-meeting-418:29
*** sdake_ has joined #openstack-meeting-418:31
*** sdake has quit IRC18:33
*** zenoway has quit IRC18:34
*** shaohe_feng has quit IRC18:35
*** shaohe_feng has joined #openstack-meeting-418:38
*** hvprash_ has quit IRC18:43
*** hvprash has joined #openstack-meeting-418:43
*** sacharya_ has joined #openstack-meeting-418:43
*** zenoway has joined #openstack-meeting-418:44
*** rockyg has joined #openstack-meeting-418:44
*** shaohe_feng has quit IRC18:45
*** shaohe_feng has joined #openstack-meeting-418:46
*** sacharya has quit IRC18:47
*** anteaya has joined #openstack-meeting-418:47
*** sambetts is now known as sambetts|afk18:47
*** sridhar_ram has joined #openstack-meeting-418:53
*** hvprash_ has joined #openstack-meeting-418:53
*** mriedem has joined #openstack-meeting-418:53
*** shaohe_feng has quit IRC18:55
*** hvprash has quit IRC18:55
*** gangil has quit IRC18:56
*** shaohe_feng has joined #openstack-meeting-418:56
*** amotoki has quit IRC18:56
*** anteaya has quit IRC18:57
mriedem#startmeeting operators_ops_tools_monitoring19:00
openstackMeeting started Wed May 18 19:00:40 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"19:00
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'19:00
mriedemRaginBajin can't make it today so i'm running this show19:01
mriedemis anyone around?19:01
rockygo/19:01
rockygslow/light day?19:02
mriedemwell i guess i'll get started19:02
mriedem#link agenda https://etherpad.openstack.org/p/osops-irc-meeting-2016051819:02
mriedem#topic Follow-up on Action Items from last meeting19:02
*** openstack changes topic to "Follow-up on Action Items from last meeting (Meeting topic: operators_ops_tools_monitoring)"19:02
mriedem* Review any additions to the Informal Meetup feedback etherpad19:03
mriedemi don't know what that is19:03
mriedemor where it is19:03
rockygme either at the moment.19:03
mriedem#link https://etherpad.openstack.org/p/AUS-ops-informal-meetup19:03
mriedem#link https://etherpad.openstack.org/p/osops-informal-meetup-feedback19:03
*** daneyon has quit IRC19:03
rockygAnd I don't know if the infra logstash filters were on that or they were this past week.19:03
mriedemthere is nothing in that feedback etherpad19:04
*** IlyaG has joined #openstack-meeting-419:04
*** dshakhray has joined #openstack-meeting-419:04
*** piet has quit IRC19:05
*** shaohe_feng has quit IRC19:05
mriedemok, moving on19:05
*** piet has joined #openstack-meeting-419:06
rockygtrue.19:06
mriedem* Review any follow-ups provided by emails sent to operators list regarding feedback for Nova blueprints19:06
mriedemi don't remember seeing much about this19:06
mriedemmarkus_z was going through old nova wishlist bugs this week and scrubbing those19:06
*** shaohe_feng has joined #openstack-meeting-419:06
mriedemsounded like some were already implemented or had blueprints up19:06
mriedemcoincidentally19:06
rockygcool.19:07
rockygI don't recall seeing anything else on the ops ml about this.19:07
mriedemmoving onto new business19:08
rockygmaybe an info line on the wishlist scrub?19:08
mriedem#info markus_z was going through old nova wishlist bugs this week and scrubbing those19:08
mriedem#topic Additional Participation19:08
rockygthanks19:08
*** openstack changes topic to "Additional Participation (Meeting topic: operators_ops_tools_monitoring)"19:08
mriedem#help How can we get more operators to even participate in email conversations let alone the group?19:08
mriedemgiven the attendance at this meeting....idk19:08
mriedembut i'm not ops19:08
mriedemin nova we really just pick on a few known ops people that hangout in nova and know the code base enough to hack on it and be dangerous19:09
mriedemso we run things by them if we don't get traffic in the ML19:09
rockygAh.  That's good info...19:09
mriedemmoving on from this topic i guess19:10
rockygI think volunteering folks for a session, like the guy who posted the logstash stuff, and advertising his presence might help19:10
mriedemwhich leads me to something the nova team wanted to bring up for ops attention19:11
mriedem#link disabling deprecated APIs by config?: http://lists.openstack.org/pipermail/openstack-operators/2016-May/010482.html19:11
rockygYeah.  I was just reading that on the dev ML19:12
mriedemsdague and i just wanted to bring that up, but it's in the ML19:12
mriedemthere is some reply already from devs19:12
*** sacharya has joined #openstack-meeting-419:12
*** banix has joined #openstack-meeting-419:12
mriedembasically nova is going to be deprecating a bunch of proxy APIs and nova-network specific APIs with a microversion, mearning if you request those APIs >= that microversion you get a 40419:12
mriedemthis to ween people off of them19:13
rockygI think either the original email and a link to the thread (already here) posted to the ops list, or a summary of the thread posted to the ops list will get their attention19:13
keekzmriedem: interesting proposal. i like the idea, +1 from me :)19:13
mriedemthe question is would ops like the ability to kill these APIs regardless of the microversion19:13
keekzre: "[Openstack-operators] disabling deprecated APIs by config?"19:13
rockygplus the config opt to get the 404 at deprecation rather than at eol or not19:14
sdaguerockyg: it was posted to the ops list19:14
mriedemso people don't start writing new things against them just to find out later when they get to a more current microversion that they are busted19:14
rockygsdague, oh.  I get ops in digest form.  Haven't seen it yet.  But haven't read my digest yet, either.19:14
mriedemrockyg: to be clear, you wouldn't get the 404 by default until you're requesting the microversion or higher, i.e. 2.2719:14
mriedemso those using v2.1 wouldn't see this19:15
mriedemthe kill switch idea is to force those APIs to break regardless of microversion19:15
mriedembasically, these deprecated APIs don't work in this cloud, period19:15
rockygmriedem, right.  But, the option to get the 404 would be settable, say in the test cloud or staging cloud19:15
mriedemwell, on this API endpoint19:15
mriedemyes19:15
mriedemper endpoint19:15
*** sacharya_ has quit IRC19:16
mriedemsdague laid out the example uses in the thread19:16
*** kbyrne has quit IRC19:16
*** shaohe_feng has quit IRC19:16
mriedemanyway, this is just an FYI to get feedback19:16
*** Sukhdev has quit IRC19:16
mriedemit's going to be a separate spec from the API deprecation work which is going to happen regardless of the kill switch config ability19:16
rockygThere should be some traffic on the ops ml, unless they all agree with the approach ;-)  Then, silence.19:16
*** nmadhok has quit IRC19:16
sdagueyeh it was cross posted to get feedback there as well19:17
rockygSeparate is best.19:17
mriedemwell, see "how to get better participation here" above :)19:17
mriedemanywho19:17
mriedemthat's all i have19:17
rockygsdague, will you either write a spec or a BP that you can post for ops comment?19:17
mriedemanyone else have anything for this meeting?19:17
sdaguerockyg: right now the email is the proposal19:18
sdagueonce it fleshes out to concensus, there will be a spec in Nova for this add19:18
*** shaohe_feng has joined #openstack-meeting-419:18
rockygExcellent.  That way there is a second chance for comments.19:18
sdaguesure, but comments late are worth less than comments early19:19
mriedembut if no one cares to reply to the thread19:19
mriedemthere is like 0 chance they'll know about the spec and comment on it there19:19
sdaguecomments late are only useful for details, comments early get to shape broad direction19:20
mriedemi.e. we don't get much ops input on specs to begin with19:20
rockygOps tend to want to see concrete so they can see exactly how it may affect them19:20
sdaguerockyg: please read the email19:20
mriedemrockyg: and by then it's too late most of hte time19:20
mriedem*the19:20
mriedemanyway19:20
*** kbyrne has joined #openstack-meeting-419:20
mriedemyes, read the email, everyone and anyone19:20
mriedemanything else here?19:20
sdaguenope19:20
rockygsdague, got through the first three on the thread.  It seems straightforward.  And you've got one comment here already.19:21
*** piet has quit IRC19:21
mriedemalright, ending the meeting19:21
mriedemthanks19:21
mriedem#endmeeting19:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:21
openstackMeeting ended Wed May 18 19:21:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-18-19.00.html19:21
keekzthanks mriedem19:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-18-19.00.txt19:21
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-18-19.00.log.html19:21
rockygThanks!19:21
*** mriedem has left #openstack-meeting-419:21
*** banix has quit IRC19:22
*** sdake_ has quit IRC19:23
*** shaohe_feng has quit IRC19:26
*** shaohe_feng has joined #openstack-meeting-419:26
*** njohnston has joined #openstack-meeting-419:27
*** piet has joined #openstack-meeting-419:27
*** jmckind has quit IRC19:31
*** baoli_ has quit IRC19:34
*** jmckind has joined #openstack-meeting-419:35
*** shaohe_feng has quit IRC19:36
*** shaohe_feng has joined #openstack-meeting-419:39
*** jmckind has quit IRC19:40
*** ninag has quit IRC19:41
*** gangil has joined #openstack-meeting-419:42
*** nmadhok has joined #openstack-meeting-419:44
*** ninag has joined #openstack-meeting-419:45
*** shaohe_feng has quit IRC19:46
*** AlanClark has quit IRC19:47
*** shaohe_feng has joined #openstack-meeting-419:47
*** sdake has joined #openstack-meeting-419:48
*** IlyaG has quit IRC19:49
*** javeriak has quit IRC19:49
*** matrohon has joined #openstack-meeting-419:50
*** fawadkhaliq has joined #openstack-meeting-419:54
*** fawadkhaliq has quit IRC19:54
*** fawadkhaliq has joined #openstack-meeting-419:55
*** anilvenkata has quit IRC19:55
*** yamamoto has quit IRC19:55
*** shaohe_feng has quit IRC19:57
*** jwagner_lunch is now known as jwagner19:58
*** shaohe_feng has joined #openstack-meeting-419:59
*** salv-orlando has quit IRC19:59
rockygIt's close!20:00
rockygIn fact, it's time.  Anyone around for log_wg?20:00
*** TravT has joined #openstack-meeting-420:00
rockygjokke_, rbradfor ?20:00
*** sridhar_ram has quit IRC20:01
*** TravT has left #openstack-meeting-420:01
*** majklkcz has quit IRC20:04
*** shaohe_feng has quit IRC20:07
*** tonytan4ever has quit IRC20:08
*** shaohe_feng has joined #openstack-meeting-420:08
*** fawadkhaliq has quit IRC20:15
*** bobh has joined #openstack-meeting-420:15
*** shaohe_feng has quit IRC20:17
*** shaohe_feng has joined #openstack-meeting-420:18
*** avarner has joined #openstack-meeting-420:19
*** ninag has quit IRC20:21
*** user154752_ has quit IRC20:22
*** ninag has joined #openstack-meeting-420:27
*** shaohe_feng has quit IRC20:27
*** shaohe_feng has joined #openstack-meeting-420:28
*** xingchao has joined #openstack-meeting-420:30
*** sacharya_ has joined #openstack-meeting-420:31
*** dshakhray has quit IRC20:32
*** sacharya has quit IRC20:34
*** shaohe_feng has quit IRC20:38
*** ddieterly is now known as ddieterly[away]20:38
*** shaohe_feng has joined #openstack-meeting-420:38
*** daneyon_ has joined #openstack-meeting-420:39
*** ddieterly[away] is now known as ddieterly20:39
*** gangil has quit IRC20:41
*** gangil has joined #openstack-meeting-420:43
*** JRobinson__ has joined #openstack-meeting-420:44
*** gangil has joined #openstack-meeting-420:45
JRobinson__hello all, the documentation user guide meeting is set to start in about 15 minutes, depending on numbers.20:45
*** gangil has quit IRC20:46
*** IlyaG has joined #openstack-meeting-420:47
*** daneyon_ has quit IRC20:47
*** shaohe_feng has quit IRC20:48
*** shaohe_feng has joined #openstack-meeting-420:49
*** gangil has joined #openstack-meeting-420:53
*** yamamoto has joined #openstack-meeting-420:56
*** shaohe_feng has quit IRC20:58
*** shaohe_feng has joined #openstack-meeting-420:59
*** ninag has quit IRC21:01
JRobinson__#startmeeting docuserguides21:01
openstackMeeting started Wed May 18 21:01:27 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: docuserguides)"21:01
openstackThe meeting name has been set to 'docuserguides'21:01
JRobinson__Hi All, I suspect this will be a short meeting since it's probably just me today.21:02
JRobinson__I have at least one discussion point that should be mentioned in the designated meeting time.21:02
*** yamamoto has quit IRC21:03
*** ddieterly is now known as ddieterly[away]21:05
JRobinson__#topic Working with developer teams to document user information21:05
*** openstack changes topic to "Working with developer teams to document user information (Meeting topic: docuserguides)"21:06
JRobinson__What emerged from discussion with developers at the recent Austin Summit was that there are documentation projects moving forward within the developer documentation21:07
JRobinson__#link http://docs.openstack.org/developer/openstack-projects.html21:08
*** jichen has quit IRC21:08
JRobinson__Specifically, some docs outlines and skeletons are planned or published here at the developer docs page.21:08
*** shaohe_feng has quit IRC21:08
JRobinson__#info I have one question - what are the steps involved in reworking some of the information into the User Guides, when developer projects reach maturity?21:09
*** shaohe_feng has joined #openstack-meeting-421:09
JRobinson__After speaking to some development team's docs liaisons at summit, I had a sense that there was potential for this as a step toward maturity, but how to reach that goal was unclear.21:10
JRobinson__#Action continue speaking to the Murano team on including the current User Guide content and troubleshooting content into the User Guides21:11
*** piet has quit IRC21:11
JRobinson__^This is the main discussion I want to continue for Newton.21:11
*** thorst_ has quit IRC21:12
JRobinson__Any feedback or thoughts from anyone in channel for user guides ?21:12
*** Sukhdev has joined #openstack-meeting-421:12
*** spzala has quit IRC21:13
*** banix has joined #openstack-meeting-421:13
*** spzala has joined #openstack-meeting-421:13
*** ninag has joined #openstack-meeting-421:15
*** thorst_ has joined #openstack-meeting-421:16
*** spzala has quit IRC21:18
*** shaohe_feng has quit IRC21:19
*** woodard_ has joined #openstack-meeting-421:19
*** evgenyf has quit IRC21:19
*** shaohe_feng has joined #openstack-meeting-421:19
*** thorst_ has quit IRC21:20
JRobinson__Okay, if there are no further thoughts on this, I might leave this discussion for now.21:20
*** salv-orlando has joined #openstack-meeting-421:21
JRobinson__#topic Current work items21:21
*** openstack changes topic to "Current work items (Meeting topic: docuserguides)"21:21
JRobinson__#info Checking through leftover editing items, and separating out any Information Architecture (IA) points for the user guides21:21
JRobinson__#Action start this process21:21
*** IlyaG has quit IRC21:22
JRobinson__That is about all for now. Any further questions - please reach out to the openstack docs mailing list.21:22
*** spzala has joined #openstack-meeting-421:22
JRobinson__#link openstack-docs@lists.openstack.org21:23
JRobinson__I check on it in my timezone daily.21:23
*** dave-mccowan has quit IRC21:23
JRobinson__Thanks all.21:23
JRobinson__#endmeeting21:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:23
openstackMeeting ended Wed May 18 21:23:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-05-18-21.01.html21:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-05-18-21.01.txt21:23
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-05-18-21.01.log.html21:23
*** woodard has quit IRC21:23
*** bobh has quit IRC21:23
*** woodard_ has quit IRC21:24
*** JRobinson__ is now known as JRobinson__afk21:27
*** shaohe_feng has quit IRC21:29
*** shaohe_feng has joined #openstack-meeting-421:29
*** ajmiller has quit IRC21:30
*** ajmiller has joined #openstack-meeting-421:30
*** piet has joined #openstack-meeting-421:32
*** aliadil has quit IRC21:32
*** thorst_ has joined #openstack-meeting-421:34
*** lakshmiS has quit IRC21:34
*** ddieterly[away] is now known as ddieterly21:34
*** matrohon has quit IRC21:34
*** rockyg has quit IRC21:35
*** thorst_ has quit IRC21:38
*** matrohon has joined #openstack-meeting-421:38
*** shaohe_feng has quit IRC21:39
*** shaohe_feng has joined #openstack-meeting-421:39
*** klamath has quit IRC21:43
*** sridhar_ram has joined #openstack-meeting-421:43
*** inc0 has quit IRC21:44
*** sridhar_ram has left #openstack-meeting-421:44
*** cloudtrainme has quit IRC21:46
*** rtheis has quit IRC21:47
*** nmadhok has quit IRC21:48
*** daneyon has joined #openstack-meeting-421:49
*** shaohe_feng has quit IRC21:49
*** markvoelker has joined #openstack-meeting-421:51
*** mjblack- has joined #openstack-meeting-421:52
*** markvoelker has quit IRC21:52
*** shaohe_feng has joined #openstack-meeting-421:52
*** markvoelker has joined #openstack-meeting-421:53
*** matrohon has quit IRC21:57
*** piet has quit IRC21:57
*** gangil has quit IRC21:59
*** shaohe_feng has quit IRC22:00
*** bpokorny_ has joined #openstack-meeting-422:00
*** shaohe_feng has joined #openstack-meeting-422:00
*** hvprash_ has quit IRC22:01
*** hvprash has joined #openstack-meeting-422:02
*** sacharya has joined #openstack-meeting-422:03
*** LouisF has quit IRC22:03
*** bpokorny has quit IRC22:04
*** julim has quit IRC22:04
*** sacharya_ has quit IRC22:07
*** klamath has joined #openstack-meeting-422:08
*** shaohe_feng has quit IRC22:10
*** shaohe_feng has joined #openstack-meeting-422:10
*** anteaya has joined #openstack-meeting-422:14
*** klamath has quit IRC22:18
*** gangil has joined #openstack-meeting-422:19
*** shaohe_feng has quit IRC22:20
*** yantarou has quit IRC22:21
*** shaohe_feng has joined #openstack-meeting-422:21
*** gangil has joined #openstack-meeting-422:23
*** yantarou has joined #openstack-meeting-422:24
*** daneyon has quit IRC22:25
*** JRobinson__afk is now known as JRobinson__22:26
*** JRobinson__ has quit IRC22:27
*** itisha has quit IRC22:29
*** shaohe_feng has quit IRC22:30
*** spotz is now known as spotz_zzz22:31
*** shaohe_feng has joined #openstack-meeting-422:31
*** mjblack has quit IRC22:32
*** mjblack- is now known as mjblack22:32
*** bpokorny_ has quit IRC22:33
*** cloudtrainme has joined #openstack-meeting-422:33
*** nmadhok has joined #openstack-meeting-422:36
*** cloudtrainme has quit IRC22:36
*** hvprash_ has joined #openstack-meeting-422:36
*** hvprash has quit IRC22:39
*** ddieterly is now known as ddieterly[away]22:41
*** shaohe_feng has quit IRC22:41
*** kylek3h has quit IRC22:41
*** shaohe_feng has joined #openstack-meeting-422:42
*** nmadhok1 has joined #openstack-meeting-422:45
*** nmadhok has quit IRC22:45
*** ninag has quit IRC22:45
*** ninag has joined #openstack-meeting-422:45
*** IlyaG has joined #openstack-meeting-422:49
*** ninag has quit IRC22:50
*** shaohe_feng has quit IRC22:51
*** shaohe_feng has joined #openstack-meeting-422:52
*** mbound has quit IRC22:54
*** bpokorny has joined #openstack-meeting-422:55
*** yamahata has quit IRC22:58
*** anteaya has quit IRC23:01
*** shaohe_feng has quit IRC23:01
*** shaohe_feng has joined #openstack-meeting-423:02
*** ddieterly[away] is now known as ddieterly23:05
*** markvoelker_ has joined #openstack-meeting-423:05
*** markvoelker_ has quit IRC23:05
*** markvoelker_ has joined #openstack-meeting-423:06
*** markvoelker has quit IRC23:09
*** pmesserli has quit IRC23:10
*** salv-orl_ has joined #openstack-meeting-423:10
*** shaohe_feng has quit IRC23:11
*** ddieterly has quit IRC23:12
*** shaohe_feng has joined #openstack-meeting-423:12
*** sarob has quit IRC23:12
*** salv-orlando has quit IRC23:13
*** sdague has quit IRC23:14
*** spzala has quit IRC23:15
*** spzala has joined #openstack-meeting-423:16
*** spzala has quit IRC23:21
*** shaohe_feng has quit IRC23:22
*** hvprash_ has quit IRC23:22
*** shaohe_feng has joined #openstack-meeting-423:23
*** zenoway has quit IRC23:24
*** zenoway has joined #openstack-meeting-423:24
*** JRobinson__ has joined #openstack-meeting-423:26
JRobinson__Hello all, I'll start the APAC User Guide meeting soon,23:27
*** zenoway has quit IRC23:29
JRobinson__#startmeeting docuserguides23:31
openstackMeeting started Wed May 18 23:31:03 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:31
*** openstack changes topic to " (Meeting topic: docuserguides)"23:31
openstackThe meeting name has been set to 'docuserguides'23:31
JRobinson__Morning all o/ I'll start the APAC version of the User Guide team meeting now23:31
JRobinson__If it's just me, then I'll wrap it up quickly23:31
*** shaohe_feng has quit IRC23:32
JRobinson__#topic Working with developer teams to document user information23:32
*** openstack changes topic to "Working with developer teams to document user information (Meeting topic: docuserguides)"23:32
*** gangil has quit IRC23:34
JRobinson__#info To repeat the information from the USA timezone meeting, I have a question to discuss on working with development teams moving toward maturity23:34
JRobinson__This emerged from the recent Austin OpenStack Summit23:34
JRobinson__#info what are the steps involved in working on and reworking developer docs information to appear in the User Guides23:35
*** shaohe_feng has joined #openstack-meeting-423:35
JRobinson__#action continue speaking to the Murano team on including content into the user guides23:37
JRobinson__This is what was discussed in the meeting earlier today.23:38
JRobinson__Are there any further thoughts or ideas on this?23:38
JRobinson__okay,23:41
JRobinson__#topic Current work items23:41
*** openstack changes topic to "Current work items (Meeting topic: docuserguides)"23:41
JRobinson__#info Checking through leftover editing items, and separating out Information Architecture points for the the User Guide.23:42
JRobinson__#Action start this process23:42
*** Sukhdev has quit IRC23:42
*** shaohe_feng has quit IRC23:42
JRobinson__If there are any user guide questions contact the mailing list, or see our contacts page:23:42
JRobinson__#link https://wiki.openstack.org/wiki/User_Guides23:43
JRobinson__since it's just me today, I'll wrap this up now.23:43
*** shaohe_feng has joined #openstack-meeting-423:43
JRobinson__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 May 18 23:43:49 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-05-18-23.31.html23:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-05-18-23.31.txt23:43
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-05-18-23.31.log.html23:43
*** mjblack- has joined #openstack-meeting-423:45
*** IlyaG has quit IRC23:45
*** bobh has joined #openstack-meeting-423:46
*** salv-orl_ has quit IRC23:46
*** Sukhdev has joined #openstack-meeting-423:48
*** mjblack- has quit IRC23:48
*** mjblack- has joined #openstack-meeting-423:48
*** mjblack- has quit IRC23:49
*** Swami has quit IRC23:49
*** mjblack- has joined #openstack-meeting-423:50
*** shaohe_feng has quit IRC23:52
*** markvoelker has joined #openstack-meeting-423:53
*** mbound has joined #openstack-meeting-423:55
*** shaohe_feng has joined #openstack-meeting-423:55
*** mjblack- has quit IRC23:55
*** mjblack- has joined #openstack-meeting-423:56
*** zenoway has joined #openstack-meeting-423:56
*** markvoelker_ has quit IRC23:56
*** mjblack has quit IRC23:57
*** mjblack- is now known as mjblack23:57
*** lakshmiS has joined #openstack-meeting-423:57

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