Wednesday, 2017-02-08

*** pmesserli has quit IRC00:02
*** unicell has joined #openstack-meeting-400:02
*** Julien-zte has quit IRC00:02
*** baoli has quit IRC00:06
*** unicell has quit IRC00:06
*** bobh has joined #openstack-meeting-400:07
*** unicell has joined #openstack-meeting-400:07
*** thorst_ has joined #openstack-meeting-400:08
*** sdake_ is now known as sdake00:10
*** salv-orlando has quit IRC00:11
*** rbak has quit IRC00:12
*** yingjun has joined #openstack-meeting-400:22
*** revon has quit IRC00:23
*** hongbin has quit IRC00:24
*** limao has joined #openstack-meeting-400:26
*** bobh has quit IRC00:35
*** david-lyle has quit IRC00:42
*** delatte has joined #openstack-meeting-400:42
*** delattec has quit IRC00:43
*** thorst_ has quit IRC00:45
*** tovin07 has joined #openstack-meeting-400:49
*** zhurong has joined #openstack-meeting-400:51
*** bobh has joined #openstack-meeting-400:51
*** chandanc_ has joined #openstack-meeting-400:52
*** _ody has left #openstack-meeting-400:53
*** _ody has joined #openstack-meeting-400:53
*** _ody has left #openstack-meeting-400:53
*** yfauser has joined #openstack-meeting-400:53
*** yfauser has quit IRC00:58
*** david-lyle has joined #openstack-meeting-401:04
*** dtardivel has quit IRC01:04
*** chandanc_ has quit IRC01:11
*** yfauser has joined #openstack-meeting-401:13
*** yfauser has quit IRC01:18
*** thorst_ has joined #openstack-meeting-401:19
*** thorst_ has quit IRC01:19
*** premsankar has quit IRC01:20
*** sdake has quit IRC01:24
*** chandanc_ has joined #openstack-meeting-401:27
*** Julien-zte has joined #openstack-meeting-401:30
*** chandanc_ has quit IRC01:32
*** rfolco has joined #openstack-meeting-401:33
*** rfolco has quit IRC01:33
*** yamamoto has quit IRC01:34
*** yamamoto has joined #openstack-meeting-401:38
*** yamamoto has quit IRC01:43
*** baoli has joined #openstack-meeting-401:48
*** yingjun has left #openstack-meeting-401:52
*** rfolco has joined #openstack-meeting-401:57
*** rfolco has quit IRC01:57
*** adisky_ has quit IRC01:59
*** bobh has quit IRC02:00
*** SerenaFeng has joined #openstack-meeting-402:06
*** amotoki has joined #openstack-meeting-402:07
*** unicell has quit IRC02:09
*** xingchao has joined #openstack-meeting-402:09
*** xingchao_ has joined #openstack-meeting-402:10
*** xingchao has quit IRC02:10
*** Syed__ has quit IRC02:15
*** thorst_ has joined #openstack-meeting-402:19
*** thorst_ has quit IRC02:24
*** gongysh has joined #openstack-meeting-402:31
*** gongysh has quit IRC02:32
*** sacharya_ has joined #openstack-meeting-402:34
*** julim has quit IRC02:35
*** sacharya has quit IRC02:36
*** sdake has joined #openstack-meeting-402:40
*** krtaylor has joined #openstack-meeting-402:40
*** yamamoto has joined #openstack-meeting-402:40
*** zhurong has quit IRC02:51
*** s3wong has quit IRC02:52
*** rwallner has joined #openstack-meeting-402:54
*** thorst_ has joined #openstack-meeting-402:55
*** thorst_ has quit IRC02:55
*** rwallner has quit IRC02:58
*** amotoki has quit IRC03:00
*** yamamoto has quit IRC03:01
*** sdake has quit IRC03:01
*** sdake has joined #openstack-meeting-403:03
*** SarathMekala has joined #openstack-meeting-403:06
*** SerenaFeng has quit IRC03:07
*** SerenaFeng has joined #openstack-meeting-403:08
*** vishnoianil has quit IRC03:08
*** amotoki has joined #openstack-meeting-403:10
*** Rockyg has quit IRC03:12
*** bobh has joined #openstack-meeting-403:13
*** _SarathMekala_ has joined #openstack-meeting-403:14
*** yfauser has joined #openstack-meeting-403:15
*** amotoki has quit IRC03:15
*** bobh has quit IRC03:17
*** SarathMekala has quit IRC03:17
*** amotoki has joined #openstack-meeting-403:19
*** yfauser has quit IRC03:22
*** yamahata has quit IRC03:33
*** zhurong has joined #openstack-meeting-403:33
*** iyamahat has quit IRC03:34
*** yfauser has joined #openstack-meeting-403:35
*** armax has quit IRC03:35
*** armax has joined #openstack-meeting-403:36
*** armax has quit IRC03:36
*** adisky_ has joined #openstack-meeting-403:39
*** yfauser has quit IRC03:40
*** amotoki has quit IRC03:40
*** links has joined #openstack-meeting-403:50
*** hongbin has joined #openstack-meeting-403:51
*** xingchao_ has quit IRC03:51
*** xingchao has joined #openstack-meeting-403:51
*** xingchao_ has joined #openstack-meeting-403:53
*** sdake_ has joined #openstack-meeting-403:54
*** ricolin has joined #openstack-meeting-403:55
*** iyamahat has joined #openstack-meeting-403:56
*** thorst_ has joined #openstack-meeting-403:56
*** xingchao has quit IRC03:57
*** sdake has quit IRC03:57
*** thorst_ has quit IRC04:01
*** SerenaFeng has quit IRC04:04
*** zhurong has quit IRC04:04
*** amotoki has joined #openstack-meeting-404:11
*** limao has quit IRC04:18
*** limao has joined #openstack-meeting-404:18
*** hongbin has quit IRC04:27
*** woodard has joined #openstack-meeting-404:28
*** woodard has quit IRC04:28
*** woodard has joined #openstack-meeting-404:29
*** yfauser has joined #openstack-meeting-404:36
*** yfauser has quit IRC04:41
*** sacharya has joined #openstack-meeting-404:43
*** sacharya_ has quit IRC04:43
*** baoli has quit IRC04:46
*** baoli has joined #openstack-meeting-404:47
*** psachin has joined #openstack-meeting-404:49
*** sacharya_ has joined #openstack-meeting-404:56
*** thorst_ has joined #openstack-meeting-404:57
*** sacharya has quit IRC04:57
*** yamahata has joined #openstack-meeting-404:59
*** baoli has quit IRC05:00
*** thorst_ has quit IRC05:02
*** gongysh has joined #openstack-meeting-405:03
*** amotoki has quit IRC05:03
*** amotoki has joined #openstack-meeting-405:04
*** rwallner has joined #openstack-meeting-405:10
*** janki has joined #openstack-meeting-405:12
*** rwallner has quit IRC05:14
*** unicell has joined #openstack-meeting-405:16
*** unicell1 has joined #openstack-meeting-405:23
*** unicell has quit IRC05:23
*** yfauser has joined #openstack-meeting-405:37
*** yfauser has quit IRC05:42
*** sacharya_ has quit IRC05:43
*** salv-orlando has joined #openstack-meeting-405:45
*** unicell1 has quit IRC05:47
*** unicell has joined #openstack-meeting-405:48
*** yfauser has joined #openstack-meeting-405:49
*** salv-orlando has quit IRC05:50
*** yfauser_ has joined #openstack-meeting-405:52
*** yfauser has quit IRC05:54
*** yfauser_ has quit IRC05:56
*** thorst_ has joined #openstack-meeting-405:58
*** thorst_ has quit IRC06:03
*** SerenaFeng has joined #openstack-meeting-406:05
*** unicell1 has joined #openstack-meeting-406:09
*** unicell has quit IRC06:09
*** cartik has joined #openstack-meeting-406:12
*** amotoki_ has joined #openstack-meeting-406:13
*** amotoki has quit IRC06:14
*** zhurong has joined #openstack-meeting-406:22
*** anilvenkata has joined #openstack-meeting-406:25
*** yfauser has joined #openstack-meeting-406:25
*** sdake_ is now known as sdake06:27
*** woodard_ has joined #openstack-meeting-406:32
*** woodard has quit IRC06:32
*** nkrinner_afk is now known as nkrinner06:33
*** padkrish has joined #openstack-meeting-406:35
*** zhurong has quit IRC06:43
*** salv-orlando has joined #openstack-meeting-406:46
*** zhurong has joined #openstack-meeting-406:49
*** salv-orlando has quit IRC06:51
*** rwallner has joined #openstack-meeting-407:00
*** salv-orlando has joined #openstack-meeting-407:02
*** salv-orl_ has joined #openstack-meeting-407:05
*** rwallner has quit IRC07:05
*** zhurong has quit IRC07:05
*** salv-orlando has quit IRC07:09
*** vishnoianil has joined #openstack-meeting-407:12
*** SerenaFeng has quit IRC07:23
*** sdake_ has joined #openstack-meeting-407:24
*** sdake has quit IRC07:26
*** pcaruana has joined #openstack-meeting-407:29
*** david-lyle_ has joined #openstack-meeting-407:37
*** zoukeke has joined #openstack-meeting-407:41
*** alij has joined #openstack-meeting-407:42
*** matrohon has joined #openstack-meeting-407:48
*** salv-orlando has joined #openstack-meeting-407:50
*** alij has quit IRC07:52
*** danoffek has joined #openstack-meeting-407:52
*** alij has joined #openstack-meeting-407:52
*** salv-orl_ has quit IRC07:52
*** alij has quit IRC07:55
*** SerenaFeng has joined #openstack-meeting-407:56
*** yamamoto has joined #openstack-meeting-407:56
*** kavithahr has joined #openstack-meeting-407:56
*** yamamoto has quit IRC07:56
kavithahrcan anyone explain me about kosmos07:57
*** ifat_afek has joined #openstack-meeting-407:57
*** yujunz has joined #openstack-meeting-407:57
*** thorst_ has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Feb  8 08:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi everyone :-)08:00
*** idan_hefetz has joined #openstack-meeting-408:01
idan_hefetzHi!08:01
*** alexey_weyl has joined #openstack-meeting-408:02
alexey_weylShalom :)08:02
ifat_afekToday’s agenda:08:03
ifat_afek•Ocata Release08:03
yujunzHi, I have two meetings at the same time slot. Ping me if any input required from me08:03
ifat_afek•Status and Updates08:03
ifat_afekyujunz: no problem08:03
ifat_afeklast in the agenda:08:03
ifat_afek•Pike Design sessions08:03
*** thorst_ has quit IRC08:04
ifat_afek#topic Ocata Release08:04
*** openstack changes topic to "Ocata Release (Meeting topic: vitrage)"08:04
ifat_afekLast week I tagged vitrage modules:08:04
ifat_afekvitrage 1.5.008:05
ifat_afekpython-vitrageclient 1.1.108:05
ifat_afekvitrage-dashboard 1.1.108:05
ifat_afekThese are our current release candidates. Please don’t push anything to stable/ocata, unless it is an important bug fix. You can use the master branch for Pike development.08:05
ifat_afekThe final release date is at the end of next week, by March 16th. The full Ocata schedule can be found here:08:05
ifat_afek#link https://releases.openstack.org/ocata/schedule.html08:05
ifat_afekAny questions/comments?08:05
*** sdake_ is now known as dake08:05
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekBoston CFP is closed. The following etherpad contains the Vitrage proposals:08:06
ifat_afek#link https://etherpad.openstack.org/p/vitrage-boston-session-proposals08:06
ifat_afekGood luck to us all08:07
ifat_afekMy updates: I wrote two use cases for Doctor manual, trying to push them to their gerrit08:07
ifat_afekNext I’ll update the test script so it will check Vitrage in addition to Congress. And then I’ll have to check it in a Newton devstack with Ocata Vitrage.08:07
ifat_afek(Trying to do both things in parallel…)08:07
ifat_afekWho else wants to update?08:07
*** dwj has joined #openstack-meeting-408:08
*** eyalb has joined #openstack-meeting-408:08
eyalb\o08:08
eyalbI will update08:09
*** alij has joined #openstack-meeting-408:09
eyalbvitrage was merged to the RDO project08:09
*** alij has quit IRC08:09
eyalbso now we have rpms08:09
ifat_afek:)08:09
ifat_afekgreat news!08:09
*** salv-orlando has quit IRC08:10
eyalbstill need to resolve some issues regarding the dashboard in order for it be added to RDO also08:10
yujunzRDO is short for ?08:10
eyalbI am now working on the puppet module so it can be run in RDO also08:10
eyalbacceptance test were added to the puppet-vitrage module08:11
eyalb#link https://www.rdoproject.org/08:11
eyalba repository for artifacts of openstack08:12
yujunzGot it08:12
eyalbthere are still issues with the puppet-openstack-integration08:13
eyalbwhich is another project to run tempest tests08:13
eyalbonce this is done08:13
*** sdake has joined #openstack-meeting-408:14
eyalbI will add the puppet also to RDO so tempest tests will run after an rpm creation08:14
eyalbthats all08:14
yujunzOK, my short update.08:14
yujunzPreparing the trip to design session in Israel.08:15
ifat_afek:-)08:15
eyalbRDO is the RPM Distribution of OpenStack08:15
yujunzI should fly to Tel Aviv right?08:15
ifat_afekWe have only one international airport in Israel ;-) Ben-Gurion08:16
yujunzOK, I guess I need some information on how to get to the hotel. To be folloowed up in email08:17
ifat_afekSure, let’s discuss it in emails08:17
yujunzMeanwhile, I'm reviewing Weiya's proposal on alarm deduction08:17
*** dake has quit IRC08:17
yujunz#link https://review.openstack.org/#/c/42300008:17
ifat_afekYes, you asked us to discuss it in IRC08:18
ifat_afekAnd I thought I’d better ask everyone to read it and think about it in advance, but forgot to do that08:18
ifat_afekBecause it’s a complicated issue08:18
yujunzWeiya is not available today and I think we may need a pre-discussion in a small group before the design session08:18
ifat_afekSure, so let’s try to do it next week. Do you want to discuss via IRC or in another way?08:19
yujunzDo you think it possible to arrange a conference call for it? ifat_afek08:19
yujunzI think we may need a conference call08:19
ifat_afekSure. BTW, why is it important to discuss before the design session?08:19
ifat_afekI just expect a long discussion here08:19
yujunzYes, just because it is long, I think discussion in a small group will be more efficient.08:20
*** yamamoto has joined #openstack-meeting-408:20
yujunzAnd we can share a more mature proposal on the design session08:21
*** padkrish has quit IRC08:21
yujunzTo get something clarified before Weiya goes detail in the design08:21
yujunzTo ensure we are going in the right direction08:22
ifat_afekOk. What is your availability next week?08:22
*** padkrish has joined #openstack-meeting-408:22
yujunzI'll discuss with Weiya and reply to you in Email. Is that oK?08:22
ifat_afekOk08:22
yujunzThanks.08:22
yujunzThat's all from my side08:22
ifat_afekThanks08:23
ifat_afekAnyone else wants to update?08:23
danoffekMy update is that I'm still working on vitrage ID.08:24
ifat_afekOk, thanks08:24
ifat_afekAnyone else?08:24
ifat_afekMoving to the next topic, which we actually started discussing08:25
ifat_afek#topic Pike Design Sessions08:25
*** openstack changes topic to "Pike Design Sessions (Meeting topic: vitrage)"08:25
ifat_afekWe will hold Pike Design Sessions in Israel, on March 6th-9th08:25
ifat_afekYou are all invited to participate and to suggest topics for the discussions. The sessions will be mostly in the mornings, so ZTE colleagues from China can participate remotely.08:25
ifat_afekThe design session etherpad:08:25
ifat_afek#link https://etherpad.openstack.org/p/vitrage-pike-design-sessions08:25
ifat_afekFeel free to edit the agenda and suggest new topics for discussion.08:25
ifat_afekAny other issue to you would like to discuss?08:26
*** yamamoto has quit IRC08:26
yujunzYou mean the design session?08:27
ifat_afekOr anything else08:28
*** nadav has joined #openstack-meeting-408:28
*** david-lyle_ has quit IRC08:28
yujunzThough aodh team is not joining, I think it worth discussion on the generic alarm proposal08:28
yujunzIt seems no conclusion yet, is it?08:28
ifat_afekI think the conclusion is, at least my conclusion is, that Aodh do not see themselves as an alarm manager, and are not interested in the generic alarm feature08:29
ifat_afekBut we can discuss it, why not08:29
ifat_afekWe can think of alternative solutions for an Aodh-Vitrage integration. Since this is a non-trivial topic, I agree that it is worth a discussio08:30
yujunzAgree08:30
*** alij has joined #openstack-meeting-408:31
yujunzThere is requirement of alarm management from vitrage and aodh may offer only part of it. So we need to fill the gaps in some way. That is my understanding of this topic.08:31
ifat_afekMakes sense08:32
*** alexey_weyl has quit IRC08:32
*** stevemar has quit IRC08:33
ifat_afekOk, anything else?08:33
ifat_afekGoodbye then08:35
eyalbbye08:35
*** stevemar has joined #openstack-meeting-408:35
danoffekBy Guys, Ifat, stay happy08:36
*** danoffek has left #openstack-meeting-408:36
ifat_afekdanoffek: always :-) :-)08:36
*** alij has quit IRC08:36
*** eyalb has left #openstack-meeting-408:36
ifat_afek#endmeeting08:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:36
openstackMeeting ended Wed Feb  8 08:36:53 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-08-08.00.html08:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-08-08.00.txt08:36
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-08-08.00.log.html08:36
*** nadav has quit IRC08:39
*** iyamahat has quit IRC08:42
*** yujunz has quit IRC08:43
*** ltomasbo is now known as ltomasbo|away08:44
*** ltomasbo|away is now known as ltomasbo08:44
*** ifat_afek has left #openstack-meeting-408:48
*** mfedosin has joined #openstack-meeting-408:49
*** ralonsoh has joined #openstack-meeting-408:56
*** salv-orlando has joined #openstack-meeting-408:57
*** idan_hefetz has quit IRC09:01
*** ralonsoh_ has joined #openstack-meeting-409:05
*** ralonsoh has quit IRC09:05
*** joedborg has joined #openstack-meeting-409:06
*** amotoki_ has quit IRC09:09
*** dwj has quit IRC09:10
*** zoukeke has quit IRC09:21
*** zoukeke has joined #openstack-meeting-409:21
*** zoukeke has quit IRC09:21
*** zoukeke has joined #openstack-meeting-409:21
*** limao has quit IRC09:24
*** ricolin has quit IRC09:24
*** yfauser has quit IRC09:26
*** yfauser has joined #openstack-meeting-409:27
*** yfauser has quit IRC09:31
*** links has quit IRC09:35
*** woodard_ has quit IRC09:35
*** NachoDuck_ has joined #openstack-meeting-409:38
*** yuli_s has quit IRC09:38
*** ricolin has joined #openstack-meeting-409:38
*** pkoniszewski_ has joined #openstack-meeting-409:38
*** Guest66676 has joined #openstack-meeting-409:41
*** bpetit_ has joined #openstack-meeting-409:41
*** med_` has joined #openstack-meeting-409:43
*** palexster1 has joined #openstack-meeting-409:44
*** topol_ has joined #openstack-meeting-409:44
*** dolphm_ has joined #openstack-meeting-409:44
*** jasondotstar_ has joined #openstack-meeting-409:44
*** dims_ has joined #openstack-meeting-409:44
*** dansmith_ has joined #openstack-meeting-409:44
*** ntpttr_ has joined #openstack-meeting-409:44
*** iberezovskiy_ has joined #openstack-meeting-409:44
*** coreycb` has joined #openstack-meeting-409:44
*** sbadia_ has joined #openstack-meeting-409:45
*** anilvenkata has quit IRC09:45
*** ntpttr has quit IRC09:45
*** dims has quit IRC09:45
*** pkoniszewski has quit IRC09:45
*** cinerama has quit IRC09:45
*** topol has quit IRC09:45
*** palexster has quit IRC09:45
*** dansmith has quit IRC09:45
*** dolphm has quit IRC09:45
*** skraynev has quit IRC09:45
*** med_ has quit IRC09:45
*** jasondotstar has quit IRC09:45
*** bpetit has quit IRC09:45
*** iberezovskiy has quit IRC09:45
*** rosmaita has quit IRC09:45
*** coreycb has quit IRC09:45
*** Guest66666 has quit IRC09:45
*** NachoDuck has quit IRC09:45
*** sbadia has quit IRC09:45
*** sbadia_ is now known as sbadia09:45
*** dolphm_ is now known as dolphm09:45
*** dansmith_ is now known as dansmith09:45
*** rosmaita has joined #openstack-meeting-409:46
*** dansmith is now known as Guest4449209:46
*** cartik has quit IRC09:46
*** NachoDuck_ is now known as NachoDuck09:49
*** joedborg has quit IRC09:51
*** links has joined #openstack-meeting-409:51
*** anilvenkata has joined #openstack-meeting-409:52
*** skraynev has joined #openstack-meeting-409:52
*** kavithahr has quit IRC09:55
*** thorst_ has joined #openstack-meeting-410:00
*** yamahata has quit IRC10:01
*** ralonsoh__ has joined #openstack-meeting-410:02
*** Julien-zte has quit IRC10:03
*** ralonsoh_ has quit IRC10:04
*** padkrish has quit IRC10:04
*** thorst_ has quit IRC10:04
*** SerenaFeng has quit IRC10:05
*** ralonsoh__ is now known as ralonsoh10:06
*** zoukeke has quit IRC10:07
*** yamamoto has joined #openstack-meeting-410:17
*** joedborg has joined #openstack-meeting-410:19
*** yamamoto has quit IRC10:22
*** yfauser has joined #openstack-meeting-410:27
*** joedborg has quit IRC10:27
*** alij has joined #openstack-meeting-410:32
*** yfauser has quit IRC10:32
*** alij has quit IRC10:32
*** sambetts|afk is now known as sambetts10:33
*** joedborg has joined #openstack-meeting-410:34
*** nkrinner is now known as nkrinner_afk10:44
*** salv-orlando has quit IRC10:49
*** links has quit IRC10:50
*** rfolco has joined #openstack-meeting-410:50
*** yfauser has joined #openstack-meeting-410:53
*** pkoniszewski_ is now known as pkoniszewski10:56
*** _SarathMekala_ has quit IRC10:57
*** yfauser has quit IRC10:58
*** links has joined #openstack-meeting-411:06
*** yfauser has joined #openstack-meeting-411:08
*** sdake has quit IRC11:11
*** sdake has joined #openstack-meeting-411:11
*** yfauser has quit IRC11:12
*** nkrinner_afk is now known as nkrinne11:16
*** nkrinne is now known as nkrinner11:16
*** yamamoto has joined #openstack-meeting-411:20
*** yamamoto has quit IRC11:26
*** limao has joined #openstack-meeting-411:33
*** salv-orlando has joined #openstack-meeting-411:33
*** sdague has joined #openstack-meeting-411:38
*** Julien-zte has joined #openstack-meeting-411:42
*** sdake has quit IRC11:43
*** jimbaker has quit IRC11:50
*** limao has quit IRC11:50
*** limao has joined #openstack-meeting-411:50
*** cinerama has joined #openstack-meeting-411:52
*** gongysh has quit IRC11:53
*** ricolin has quit IRC11:54
*** limao has quit IRC11:55
*** brunograz has joined #openstack-meeting-411:59
*** thorst_ has joined #openstack-meeting-412:00
*** thorst_ has quit IRC12:05
*** pbourke has quit IRC12:06
*** pbourke has joined #openstack-meeting-412:07
*** dave-mccowan has joined #openstack-meeting-412:07
*** yfauser has joined #openstack-meeting-412:18
*** yfauser has quit IRC12:23
*** david-lyle has quit IRC12:24
*** salv-orlando has quit IRC12:34
*** yamamoto has joined #openstack-meeting-412:35
*** Julien-zte has quit IRC12:35
*** thorst_ has joined #openstack-meeting-412:41
*** coreycb` has quit IRC12:48
*** coreycb has joined #openstack-meeting-412:48
*** yamamoto has quit IRC12:48
*** rwallner has joined #openstack-meeting-412:50
*** gongysh has joined #openstack-meeting-412:55
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Feb  8 13:00:04 2017 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
*** cdent has joined #openstack-meeting-413:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
cdento/13:00
gmanno/13:00
alex_xucdent: gmann let us wait johnthetubaguy and sdague if they are around13:01
* johnthetubaguy waves13:01
alex_xulet us start the meeting13:02
alex_xu#topic Pike ideas13:02
*** openstack changes topic to "Pike ideas (Meeting topic: nova api)"13:02
alex_xu#link https://etherpad.openstack.org/p/nova-api-pike13:02
alex_xu^ I created an etherpad to collect the idea for Pike13:03
gmannnice, thanks13:03
johnthetubaguydid we want to discussion the policy ideas, I am curious what folks think13:03
alex_xuMatt helps to input some items13:03
johnthetubaguyalso big thank you to alex_xu for reviewing that13:03
alex_xujohnthetubaguy: np13:04
alex_xusure, we can discuss the policy ideas13:04
gmannyea13:04
johnthetubaguyso operator feedback first13:04
johnthetubaguymost folks struggle editing policy right now13:04
johnthetubaguymany of them are forced into re-writing all rules because the want more RBAC levels than we have in the default policy file13:05
johnthetubaguymy thinking is we define a rough end goal for where we want to be, and get that reviewed by operators13:05
johnthetubaguythen we go through each rule, one by one, and make it match the plan13:05
johnthetubaguy...so to the "plan" I have suggested13:06
alex_xu'reviewed by operators' means sending email to operator ML?13:06
johnthetubaguybasically we add more roles, like observer roles, roles for neutron and cinder, operator rules, etc13:06
johnthetubaguyalex_xu: hopefully means talking to them at an ops meetup, at a minimum13:06
johnthetubaguyalex_xu: but thats part of it13:06
gmanni see but there might be lot of roles depends on each operator13:07
johnthetubaguyI really want something we agree on first13:07
gmannor we add common one13:07
*** psachin has quit IRC13:07
johnthetubaguyso there are two things here13:07
johnthetubaguythe name of the role, and the common patterns13:07
johnthetubaguyif we can cover 80% of deployments with the default, thats great13:07
johnthetubaguyfolks will just need to say what the role name is in their keystone, and we take care of the rest, for the 80%13:07
johnthetubaguyfor the 20% we need to add doc strings on each of the rules, so they know what they control13:08
sdagueo/13:08
johnthetubaguybasically, my idea is stop most folks having to change much of the policy file13:08
alex_xuwhether the name of role need to get more widly agreement, so other project can use the same name13:08
*** bobh has joined #openstack-meeting-413:08
johnthetubaguybut also give folks who need to change everything (or audit it) a bit of a helping hand (i.e. no need to read code to work out what each rule means)13:09
*** bobh has quit IRC13:09
johnthetubaguyalex_xu: we actually we need it to be project specific, like nova_operator etc, but yes common patterns are good13:09
johnthetubaguyso I am talking to keystone folks a bit about this, they have started a policy meeting13:09
johnthetubaguythey have a proposal for some roles we could create13:10
sdaguejohnthetubaguy: can you be more specific on folks that are changing policy so much?13:10
*** yfauser has joined #openstack-meeting-413:10
johnthetubaguysdague: I think they want observer roles, and operator roles that are not admin everywhere13:10
sdaguejohnthetubaguy: yeh, I honestly thought we had 5 roles decided on back in tokyo13:10
johnthetubaguysdague: I am hoping we can get access to some specific ones13:10
johnthetubaguysdague: yeah, its basically those13:10
sdagueok, what stands between those hallway conversations and just doing it?13:11
johnthetubaguyupgrade story, the spec I wrote out tried to cover that13:11
*** SerenaFeng has joined #openstack-meeting-413:12
johnthetubaguyI think I have the OSIC folks who are willing to do the work to implement it13:12
sdaguejohnthetubaguy: ok, so... every time I brought this up at ops meetups, people mostly didn't change much in policy13:12
johnthetubaguykinda a follow on from config work that was related13:12
alex_xu++OSIC folks13:12
johnthetubaguysdague: I was told they tried, it failed, and so gave up13:12
sdaguejohnthetubaguy: I guess I need to understand the spec more13:13
johnthetubaguyat the manchester meetup13:13
sdaguemaybe the issue is the following, today, we do policy as "policy_point: can be done by this complicated formula of things"13:13
sdaguevs the way people would think about things:13:13
*** klamath has joined #openstack-meeting-413:13
sdaguegiant list of policy points...13:13
sdagueobserver_can: p1, p2, p4, p813:14
johnthetubaguythats a good point, this is still reversed in my spec13:15
sdagueand... it almost seems like you could add role stanzas like that as an overlay to the existing content13:15
johnthetubaguyp1: observer and admin can, etc13:15
sdagueso that the current stuff is just the current stuff13:15
johnthetubaguysdague: yeah, it should be equivalent13:15
sdagueand the new stuff is new stanzas13:15
sdaguewhich... makes the upgrade a lot more viable for users, right?13:15
johnthetubaguymaybe... need more visualization on it13:16
sdaguejohnthetubaguy: ok13:17
johnthetubaguyI was also talking about renaming the rules (via deprecation aids) to better match the REST API rather than the code13:17
sdagueyeh, which I'm all for13:17
sdaguebut if there is a different upgrade issue, we should probably address that13:17
johnthetubaguymaybe the staging is (1) fix names and docs, (2) look at making what each role does more visible (3) think about adding extra roles13:17
johnthetubaguyit was mostly the "we need to evolve like config" upgrade issue that I was referring too13:18
sdaguejohnthetubaguy: ok cool13:18
sdaguesorry, rewrapping my head on the whole thing13:19
*** salv-orlando has joined #openstack-meeting-413:19
johnthetubaguysdague: totally, been going through that a bit myself13:19
johnthetubaguyFWIW, we really have made a lot of progress at this point13:20
johnthetubaguyno policy file needed by default, defaults in the code, reduced the number of rules by half13:20
sdagueyeh13:20
johnthetubaguywe are in a much better place to move forward now, which is kinda awesome13:20
sdaguethere is still a docs gap though, right?13:20
sdaguepretty much the policy rules only make sense if you go and read the code13:20
johnthetubaguyyeah, and a naming to avoid the docs having to say everything13:20
johnthetubaguyyeah13:20
sdaguewell, the docs should be there anyway13:21
sdaguenames are never as obvious as you think :)13:21
johnthetubaguyyeah, I tried it, its hard13:21
gmanndoc for rules will be as description right ? so that it can be seen from sample file like config one13:21
sdagueyeh13:22
johnthetubaguymy current leaning is towards compute:servers:action:live-migration13:22
johnthetubaguygmann: turns out we have two doc strings in our sample file already13:22
gmannyea :)13:22
sdaguejohnthetubaguy: do we have anything published web side?13:22
johnthetubaguy#link http://docs.openstack.org/developer/nova/sample_policy.html13:22
sdagueum... I wouldn't call that docs :)13:23
johnthetubaguyI mean two of them have strings13:23
sdagueWhat I really expect is:13:23
johnthetubaguybut its totally not docs13:23
sdague- os_compute_api:os-aggregates:set_metadata13:23
sdague   this allows the roles in question to set metadata on aggregates.13:24
gmannhow about embeding policy rule inside api-ref for corresponding APIs13:24
*** rwallner has quit IRC13:24
johnthetubaguysdague: I was meaning the rule near os_compute_api:os-attach-interfaces:create has added some docs already13:24
sdague  default_permissions: admin role only13:24
sdagueok13:24
johnthetubaguygmann: thats mixing operator and API user though13:24
sdagueit's not api-ref for sure13:25
johnthetubaguyyeah, we need to render the default better, like the config stuff13:25
gmannah yea13:25
sdaguebut it should end up with/near the config guide13:25
johnthetubaguybut we all seem agreed with the same as config, you shouldn't need to read the code to understand it13:25
sdagueyeh13:25
gmannyes13:25
johnthetubaguyif we go and add docs, I am tempted to consider a rename, but maybe that is premature?13:26
sdaguejohnthetubaguy: honestly, we can document things first, that would be of immediate help to people13:26
johnthetubaguysdague: thats fair13:26
johnthetubaguyI was wanting to avoid visiting all the rules twice13:26
sdagueI'd rather get us in the habbit of writing down what is instead of assuming we can make a change that means we don't need docs13:26
johnthetubaguybut we have less rules now13:26
johnthetubaguysdague: yeah, we totally need the docs, even with the most perfect of names13:27
sdaguedo we have other topics? I don't want to take over the whole meeting with this13:27
johnthetubaguyyeah, I think we should review the other ideas13:27
alex_xuother items in https://etherpad.openstack.org/p/nova-api-pike13:27
johnthetubaguywell, before we leave...13:28
johnthetubaguyI can add a spec for adding in the docs13:28
johnthetubaguyso folks stop needing to read the code13:28
sdaguejohnthetubaguy: that would be cool, I would be up for helping get that all sorted13:28
johnthetubaguysdague: cool, thanks13:28
johnthetubaguyI think the next step might be making the rules mean something (actually adding targets)13:29
*** iurygregory has joined #openstack-meeting-413:29
johnthetubaguylike admin_or_owner is largely a no op today13:29
johnthetubaguybecause of the deafault rule target13:29
johnthetubaguywe are safe due to the hardcoded DB checks13:29
johnthetubaguyit feels like we should add in the targets, then consider removing the hard coded things once we are happy with our unit tests13:30
johnthetubaguybut thats a separate discussion13:30
sdaguejohnthetubaguy: I thought the hardcoded db checks were mostly gone13:30
johnthetubaguysdague: they are gone for is_admin, they are everywhere for membership in the project13:30
sdagueoh, you mean owner13:30
johnthetubaguysorry, yeah, owner13:31
johnthetubaguythat is not checked in the policy later, even though the rule says its checking13:31
sdagueright13:31
johnthetubaguywe just check context.project_id == context.project_id right now, which is amuzing13:31
sdagueheh13:32
sdagueyeh, well the project scoping like that goes back years13:32
johnthetubaguyalthough there is a separate discussion about that being a good idea, as it keeps policy from making the API interoperable13:32
johnthetubaguyso we totally said we should move on lol, we should do that...13:32
sdague:)13:33
johnthetubaguyturns out that was a conversation stopper13:33
sdaguewhat are team members excited about for the next cycle?13:33
sdaguewhat would they most like to solve13:33
johnthetubaguyhttps://review.openstack.org/#/c/386555/ on capabilities would be awesome13:34
gmannyea that is nice to do13:34
johnthetubaguyquery param schema excites my less, but would be nice13:34
sdaguedo we feel like capabilities can come to a resolution on design for the PTG?13:35
alex_xuquery param schema is just a refactor, so it can be background work for new people13:35
alex_xuso +1 for capabilities13:35
gmannand cleanup extension things as sdague started, make code more easy13:35
*** sdake has joined #openstack-meeting-413:36
*** ricolin has joined #openstack-meeting-413:36
johnthetubaguysdague: so turns out we didn't have many people from keystone or API-wg in the summit session, if we can fix that, maybe?13:36
sdagueI guess the concern I have about capabilities... it relies a lot on link following13:36
sdaguedo we know of any sdk tooling that's regularlly doing that?13:36
johnthetubaguythere is a proposal to remove the link following, for the global scope and per type scope13:37
johnthetubaguythat might be a good idea13:37
sdaguespending some time poking on some other APIs recently, they tend not to expose anything on their API until the SDK also implements it13:37
johnthetubaguyso I keep thinking about to horizon and enabling buttons in the GUI13:37
sdaguejohnthetubaguy: sure, but they aren't writing their own client13:37
sdagueso... I'm fine exposing capabilities13:38
johnthetubaguylike ironic and libvirt based servers, choose which turn on13:38
sdagueI think it's hugely needed13:38
johnthetubaguysdague: they do, I was more thinking efficient calling patterns down that thought path13:38
*** janki has quit IRC13:38
johnthetubaguylink follwing is expensive13:38
sdagueI mostly get concerned that it is useful only if we have sdk drops with the functions13:38
johnthetubaguythats true, would this be adaptive help in the SDK?13:39
johnthetubaguyI guess I am struggling on the consuming part, if I don't think about horizon13:39
*** links has quit IRC13:39
sdagueyeh, I don't know.13:40
cdentwho were the original people or group that said "we need capabilities"?13:40
sdaguecdent: definitely people making guis13:41
johnthetubaguyironic snapshots always fail, why not hide the button, etc13:41
johnthetubaguythe other side was live-resize13:41
johnthetubaguywe expect folks to turn that off, and want that to be discoverable when talking to multiple clouds13:41
johnthetubaguybut thats a little bit of a vanity use case, in some ways13:42
cdentin the stuff I've read, that particular use case is not made as clear as it potentially could be. Instead we end up with discussions on how to make capabilities as (uh) capable as possible13:42
sdagueI know that mordred ended up basically writing crazy autoconf like stuff where he tries a bunch of things in shade because there is no way to figure out that he can't do a thing in advance13:42
sdagueand doesn't want to fail deep in complicated logic13:42
sdaguethis is mostly about OpenStack clouds could do A13:43
sdaguebut some clouds turn off B, C, D for performance, security, hypervisor support reasons13:43
johnthetubaguyright, the how do I get an external IP on my server question13:43
*** matrohon has quit IRC13:44
sdaguecdent: so perhaps the issue is framing the use case a bit better13:44
johnthetubaguymaybe shade is the SDK use case13:44
*** Yumeng__ has joined #openstack-meeting-413:44
sdaguethe way I imagined this was more along the fact that13:45
cdentas a user I'd prefer to ask a "capabilities service" for that information, not go grubbing around in all the projects at several urls. perhaps a service could register it's capabilities at startup or regularly (not deployment)13:45
*** janki has joined #openstack-meeting-413:46
sdaguecdent: yeh13:46
sdaguecdent: that works for top level constructs for sure. It doesn't solve the "this cloud has baremetal and libvirt computes"13:47
sdagueand this compute you have can't be live migrated13:47
cdentI think anything that can be started as "this cloud..." ought to be able to be "registered"13:47
*** licanwei_ has joined #openstack-meeting-413:47
sdaguecdent: sure13:48
cdentand I think anything that says "this <entity, like this compute>" should be in the representation of that entity itself13:48
sdaguecdent: yep, no disagreement there13:48
*** mchiappe1o is now known as mchiappero13:48
johnthetubaguywould aggregated centrally work better, i.e. exposed in each service, but also aggregated (via checking everything in the service catalog, etc), or does that mean we do the work twice?13:48
sdagueok... so where does that leave us, because this seems circular13:48
sdaguewhich probably means the thing being carved off is too big13:49
sdagueand maybe it can be started as something smaller13:49
*** yamamoto has joined #openstack-meeting-413:49
*** julim has joined #openstack-meeting-413:49
johnthetubaguymaybe per endpoint global, and per endpoint type only?13:50
*** salv-orl_ has joined #openstack-meeting-413:50
johnthetubaguyleave the aggregation / central piece for later?13:50
*** matrohon has joined #openstack-meeting-413:50
sdagueor, find a specific problem, like a chunk of code in shade or horizon we'd like to go away, and work backwards on solution to that13:50
johnthetubaguystop the per resource capabilitiy thing at first, just go for the shade and horizon use cases first13:50
sdaguejohnthetubaguy: yeh13:51
johnthetubaguyso horizon just shows all buttons based on VM state, and shade just hard codes13:51
johnthetubaguyso it would be improving both of those to some degree I guess13:51
johnthetubaguymaybe just do the horizon one to start with?13:52
johnthetubaguyironic and VM mixed cloud13:52
johnthetubaguyget the buttons right13:52
* alex_xu reminds 8 mins left13:52
johnthetubaguy(for user operations)13:52
*** salv-orlando has quit IRC13:52
sdaguecdent: from an api-wg perspective, how would you like to / expect to constrain scope so we can get feedback and iterate on something real?13:52
*** chrisspencer has joined #openstack-meeting-413:54
cdentsdague: that's an excellent question. I don't really have a good answer. I agree with you that the current scope is too large, and have said as much on the ongoing review of the capabilities spec. In the context of the api-wg what matters is what a capability looks like and where it is retrieved from13:54
* mordred waves13:54
cdent(and of course that whatever it is, everyone is doing the same thing)13:54
johnthetubaguycdent: OK with doing it per endpoint first, as s stepping stone towards centralised?13:55
cdentjohnthetubaguy: I think that's probably the only way it is likely to happen, but I don't like it that much because it means it will never truly be centralised :)13:55
*** yamamoto has quit IRC13:55
mordredsdague, cdent: so, for several of these things (although admittedly not enough of them) we have flags in os-client-config so that discovery code can be skipped for known clouds13:56
* mordred reminds self to go make a "this cloud requires floating ips" flag13:56
sdaguemordred: code reference?13:56
mordredone sec ...13:56
*** zhurong has joined #openstack-meeting-413:56
sdagueI think that shade might be more concrete than horizon for these discovery routines13:56
johnthetubaguycdent: yeah, I am with you on that13:56
johnthetubaguysdague: assuming they are not harder questions to answer, +113:57
mordredsdague: line 14 and line 16 are both concrete examples:  http://git.openstack.org/cgit/openstack/os-client-config/tree/os_client_config/defaults.json#n1413:57
sdaguecdent: I think that if we can convince keystone folks that more things should flow into service catalog, there is a centralization plan13:57
cdentsdague: yes13:57
johnthetubaguyI think we could argue thats more useful than exposing policy, and so it might be what they are wanting to do13:58
sdaguecdent: so, I think that's the centralizing plan13:58
sdaguemordred: it makes me slightly sad that all the api versions are hardcoded in shade13:59
alex_xuok, we need to close the meeting now13:59
mordredsdague: those are just defaults13:59
sdaguesure13:59
alex_xuwe should back to nova channel13:59
mordredsdague: they're overridable in config - and they also can be auto-discovered13:59
sdaguemordred: ah, ok13:59
mordredsdague: but yes13:59
alex_xuand johnthetubaguy sdague there is patch looking for feedback https://review.openstack.org/430497, that is also mordred faced problem13:59
mordredsdague: like, if your config says "image api version 2" and the cloud only has 1, we'll use 1 but give you a warning13:59
alex_xu#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Feb  8 14:00:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
alex_xusorry~14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-02-08-13.00.html14:00
johnthetubaguyalex_xu: not see that, looking14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-02-08-13.00.txt14:00
*** woodard has joined #openstack-meeting-414:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-02-08-13.00.log.html14:00
mordredalex_xu: that one was fun :)14:00
alex_xumordred: yea14:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Feb  8 14:00:57 2017 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:01
openstackThe meeting name has been set to 'watcher'14:01
acaboto/14:01
Yumeng__hi14:01
pshedimbhi14:01
chrisspencero/14:01
adisky_hi14:01
hvprashhi14:01
acabot#info agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F08.2F201614:01
licanwei_hi14:01
acabotas always feel free to add things in open discussions along the meeting14:02
*** limao has joined #openstack-meeting-414:02
*** vincentfrancoise has joined #openstack-meeting-414:02
vincentfrancoiseo/14:02
*** baoli has joined #openstack-meeting-414:03
acabot#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:03
*** alexchadin has joined #openstack-meeting-414:03
alexchadinHi14:03
acabot#info Watcher has been released in v1.0.014:03
alexchadin:)14:03
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2017-February/111576.html14:03
pshedimbYayy :)14:03
acabotthats a great achievement !14:03
acabotcongrats everybody14:04
vincentfrancoiseacabot: +214:04
alexchadinWe have made it!14:04
hvprashgood work team ! congrats !14:04
acabot#info Watcher Dashboard has been released in v1.0.014:04
acabotso now all our components are in 1.0.0 (watcher, dashboard & CLI)14:05
acabot#info alexchadin is elected as Watcher PTL14:05
*** limao_ has joined #openstack-meeting-414:05
acabot#link http://lists.openstack.org/pipermail/openstack-dev/2017-February/111769.html14:05
hvprashwoo hoo ! congrats alex !14:06
alexchadinI am glad to be part of this project!14:06
acabotI planned to add alexchadin as core reviewer on Watcher specs as our new PTL14:06
acabotdo we agree that we can do it without candidacy on the ML ?14:06
sballe_Morning stick in traffic will be there in 5 minutes14:06
pshedimb+214:06
*** limao has quit IRC14:06
hvprash+214:07
vincentfrancoise+214:07
acabotok14:07
Yumeng__+214:07
acabot#action acabot add alexchadin as spec core reviewer14:07
licanwei_+214:07
alexchadinThank you!14:07
*** caowei has joined #openstack-meeting-414:07
*** cathrichardson has joined #openstack-meeting-414:07
acabotalexchadin : if its OK for you, I will continue leading the IRC meeting until the PTG14:08
acabotalexchadin : and then we will have to build your own agenda ;-)14:08
acabots/we/you14:08
alexchadinYes, i will take this time to get ready for meetings14:09
acabot#info PTG is in 2 weeks, etherpad is open and a 1st draft of agenda is available14:09
acabot#link https://etherpad.openstack.org/p/pike-watcher-ptg14:09
acabotfeel free to add topics in the list, we still have some time left for other topics14:10
pshedimbNo time for lunch during PTG :P14:10
acabotpshedimb : we never eat during meetings ;-)14:11
pshedimbhahaa :D14:11
Yumeng__LoL14:11
acabotpshedimb : actually I dont know exactly how it will be organized but there will probably be a buffet14:11
pshedimbacabot, okay. cool!14:12
*** cathrich_ has joined #openstack-meeting-414:12
*** cathrichardson has quit IRC14:12
acabotbut I tried to put "light" topics at lunch time :-D14:12
acabotagain, it still possible to add topics so feel free to add things you definitely want to have in Pike14:13
pshedimbyes, i will discuss with sballe_ today and add to in etherpad14:13
acabotwe have plenty of BPs to discuss (https://blueprints.launchpad.net/watcher)14:13
hvprashyeah, got some reviews on audit vm metatadata. like to discuss in ptg14:14
acabotso if you have a very important one and you won't be there to explain it, please do it on the etherpad, so that we can take decisions14:14
alexchadinacabot: do you plan to organize video translation?14:15
acabothvprash : added14:15
hvprashthanks :)14:15
acabotalexchadin : I asked for hangout session14:16
vincentfrancoisehvprash: I won't be attending so if you want me to review what we discussed last time about audit vm metadata, make sure you push it before then ;)14:16
acabotalexchadin : but the foundation cannot guarantee the wifi connectivity14:16
hvprashoh ! i thought you will be there. I will work on the PS then14:16
alexchadinacabot: anyway, I will be available in IRC14:16
acabotalexchadin : anyway, I tried to put release related topics between 10am and 2pm14:17
acabotalexchadin : so that you can follow them14:17
acabot#info 3 lightning talks & 1 presentation submitted for Boston summit14:17
acabot#link https://etherpad.openstack.org/p/Watcher_abstracts_boston201714:18
alexchadinacabot: I saw your agenda, thanks :)14:18
acabotI'm surprised that 3 talks have been submitted as lightning talks14:18
acabotFYI, lightning talks replace vBrowBag sessions in previous summit14:18
acabot10 minutes max14:18
acabotthe deadline for submission has been moved to today14:20
*** cdent has left #openstack-meeting-414:20
alexchadinI have submitted Plans for P and Q as presentation14:20
acabotso its still possible to change a lightning talk into a presentation if it makes sense14:20
acabotalexchadin : yes, it is the only one, the 3 others are lightning talks14:21
alexchadinSorry for delaying, I'm on smartphone14:21
acabotYumeng__ : is your talk ok in 10 minutes ?14:21
Yumeng__I'm not sure at this stage14:21
*** dtardivel has joined #openstack-meeting-414:22
Yumeng__I will discuss with licanwei_14:22
Yumeng__And if possible , I will resubmit it14:22
acabotYumeng__ : I think you can just update it14:23
Yumeng__Ok14:23
alexchadin+114:23
*** pmesserli has joined #openstack-meeting-414:23
*** limao_ has quit IRC14:23
acabot#action Yumeng__ check that the submited presentation is a lightning talk or a presentation14:23
*** limao has joined #openstack-meeting-414:24
acabotsballe_ hvprash : your talk is a lightning talk (10 minutes), is that OK for you ?14:24
sballe_hi just got here14:24
sballe_the RDT talk>14:24
sballe_sorry the noisy neighbor talk?14:25
acabotsballe_ : Automating noisy neighbor detection with OpenStack Watcher14:25
hvprashsballe_ yes14:25
*** Julien-zte has joined #openstack-meeting-414:25
sballe_I would have prefered a normal talk but I will take waht i can get14:25
acabotFYI, I will be track chair for Boston summit14:25
sballe_cool!14:25
alexchadinI have to leave IRC, will read talks history this evening.14:25
hvprashi think it should be a normal talk > 10 mins if we are covering case studies too14:25
acabotand there are many lightning talks submitted14:25
sballe_yeah I wanted to ask you about that ... mybe offline14:25
vincentfrancoisealexchadin: bye ;)14:26
sballe_acabot: I didn;t submit it as a lightning talk14:26
alexchadinHave a nice day/evening!14:26
acabotsballe_ hvprash : I would suggest to update it as a presentation14:26
sballe_yeah me too14:26
sballe_can I still do thta?14:26
pshedimbsballe_, yes.14:26
acabotDEADLINE EXTENDED: PRESENTATION SUBMISSIONS FOR OPENSTACK SUMMIT BOSTON UNTIL 11:59PM PST ON FEBRUARY 8, 2017 (7:59 ON FEBRUARY 9, 2017 UTC)!14:26
sballe_ok I will do that right now14:26
pshedimbDeadline has been extended14:26
acabotbefore tonight14:26
acabot#topic Review Action Items14:27
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:27
acabotWatcher specs14:27
acabotAll those specs should be completed and retargeted to Pike14:27
*** Guest44492 is now known as dansmith14:28
sballe_acabot: I am surprised I have it as a presentation14:28
*** zz_ja has quit IRC14:28
acabotso please abandon or update your review in the right folder (pike/approved)14:28
*** dansmith is now known as Guest9404614:28
*** alexchadin has quit IRC14:28
*** cathrich_ is now known as cathrichardson14:28
acabotsballe_ : could be a bug in the track chair tool...14:28
sballe_ok I just checked and resubmitted making sure it was a presentaiton14:29
acabotsballe_ : ok14:29
*** cathrichardson has left #openstack-meeting-414:29
acabot#link https://review.openstack.org/#/c/425204/14:29
sballe_can you give me the link?14:29
acabotsballe_ : open only to track chairs14:29
sballe_ok so I do not udnerstand "so please abandon or update your review in the right folder (pike/approved)"14:30
acabot#action Yumeng__ resubmit in PIke https://review.openstack.org/#/c/425204/14:30
*** julim has quit IRC14:30
acabotsballe_ : sorry, as these specs have not been implemented in Ocata14:30
acabotsballe_ : we need to resubmit them for Pike14:31
sballe_oh sorry! Was still on the old topic ;-)14:31
acabotsballe_ : ;-)14:31
acabot#link https://review.openstack.org/#/c/398162/14:31
pshedimbacabot, Working on the algo.14:32
acabot#action sballe_   resubmit in Pike https://review.openstack.org/#/c/398162/14:32
sballe_acabot: yeah we finally got the system working including live migration ;-)14:32
acabotpshedimb : ok great, we need to have the spec ready in Pike14:32
sballe_acabot: please have pshedimb do the action14:32
pshedimbYes sure.14:32
acabot#undo14:32
openstackRemoving item from minutes: #action sballe_   resubmit in Pike https://review.openstack.org/#/c/398162/14:32
acabot#action pshedimb   resubmit in Pike https://review.openstack.org/#/c/398162/14:33
acabot#link https://review.openstack.org/#/c/391374/14:33
acabot#action hvprash resubmit in Pike https://review.openstack.org/#/c/391374/14:33
pshedimbacabot, sballe_ yeah. will do it.14:33
hvprashacabot: will do14:33
acabot#link https://review.openstack.org/#/c/427308/14:33
sballe_I will review14:33
acabot#action chrisspencer resubmit in Pike https://review.openstack.org/#/c/427308/14:34
acabot#link https://review.openstack.org/#/c/401111/14:34
acabot#action hanrong resubmit in Pike https://review.openstack.org/#/c/401111/14:34
acabot#link https://review.openstack.org/#/c/420612/14:34
acabot#action vincentfrancoise resubmit in Pike https://review.openstack.org/#/c/420612/14:34
acabot#link https://review.openstack.org/#/c/377100/14:34
acabot#action hvprash resubmit in Pike https://review.openstack.org/#/c/377100/14:35
acabot#link https://review.openstack.org/#/c/386293/14:35
chrisspenceracabot: my spec is already submitted under specs/pike/approved do I need to do something differently?14:35
sballe_acabot: just as an FYI chrisspencer will take over the grammar bp from hvprash14:35
*** Guest94046 is now known as dansmith14:35
vincentfrancoiseacabot: I don't know if alexchadin wants to do it since he's the one implementing it14:35
chrisspencersballe_: acabot I will resubmit the grammar bp as well14:35
acabotchrisspencer : sorry I missed it, thats good then :-)14:35
hvprashsballe_ yeah please assign to chris14:35
sballe_lol will do :)14:36
acabot#undo14:36
openstackRemoving item from minutes: #link https://review.openstack.org/#/c/386293/14:36
vincentfrancoiseacabot: but I'll sync with him14:36
acabot#undo14:36
*** Julien-zte has quit IRC14:36
openstackRemoving item from minutes: #action hvprash resubmit in Pike https://review.openstack.org/#/c/377100/14:36
*** mfedosin has quit IRC14:36
acabot#action chrisspencer resubmit in Pike https://review.openstack.org/#/c/377100/14:36
*** Julien-zte has joined #openstack-meeting-414:36
*** Julien-zte has quit IRC14:37
acabot#link https://review.openstack.org/#/c/386293/14:37
acabotlicanwei_ dtardivel : I think https://review.openstack.org/#/c/386293/ should be improved14:37
acabotlicanwei_ : could you resubmit your spec in Pike so that we can work on it again ?14:38
sballe_chrisspencer: what's your launchpad id?14:38
*** Julien-zte has joined #openstack-meeting-414:38
licanwei_acabot: ok14:38
*** Julien-zte has quit IRC14:38
chrisspencersballe_: christopher-m-spencer14:38
acabot#action licanwei_ resubmit in Pike https://review.openstack.org/#/c/386293/14:39
sballe_thx14:39
acabotmoving to Watcher14:39
acabotworkload-balance-tempest needs core final reviews14:39
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:detached/workload-balance-tempest14:39
*** SerenaFe_ has joined #openstack-meeting-414:39
acabot#action alexchadin dtardivel review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:detached/workload-balance-tempest14:39
dtardivel+114:40
*** Julien-zte has joined #openstack-meeting-414:40
acabotAdd Action Notification needs core final reviews14:40
*** Julien-zte has quit IRC14:40
*** fengxia41103 has joined #openstack-meeting-414:40
acabot#link https://review.openstack.org/#/c/427646/14:40
acabot#action vincentfrancoise dtardivel review https://review.openstack.org/#/c/427646/14:40
vincentfrancoiseacabot: already did14:40
acabot#undo14:40
openstackRemoving item from minutes: #action vincentfrancoise dtardivel review https://review.openstack.org/#/c/427646/14:40
acabot#action dtardivel review https://review.openstack.org/#/c/427646/14:41
acabotcheck the state of action plan needs specs rework14:41
acabot#link https://review.openstack.org/#/c/391383/14:41
acabotdynamic-action-description needs a status14:41
*** Swami has joined #openstack-meeting-414:41
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/dynamic-action-description14:41
acabotis hanrong here ?14:41
*** SerenaFeng has quit IRC14:42
acabotor anyone working with hanrong ?14:42
licanwei_me14:42
acabotlicanwei_ : thx, do you know whats the status for this BP ? https://blueprints.launchpad.net/watcher/+spec/dynamic-action-description14:43
licanwei_i dont know14:43
acabotis hanrong working on it or should we give it to someone else as we are resubmitting specs ?14:43
licanwei_sorry14:43
licanwei_i'll confirm it14:43
acabot#action licanwei_ see with hanrong what is the status for https://blueprints.launchpad.net/watcher/+spec/dynamic-action-description14:44
acabotI will probably remove her from the BP at the PTG if we dont get any update until then14:44
acabot#topic Blueprint/Bug Review and Discussion14:45
*** limao has quit IRC14:45
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:45
acabotBug fixing in progress for Ocata-rcfinal targeted for February 16th (all fixed bugs should be backported to stable/ocata branch)14:45
acabot#link https://launchpad.net/watcher/+milestone/ocata-rc-final14:45
*** limao has joined #openstack-meeting-414:45
acabotI retargeted all bugs currently in review in Gerrit to ocata-rcfinal14:45
acabotbut maybe not all of them will be backported to stable/ocata14:46
adisky_acabot: i want to discuss about https://blueprints.launchpad.net/watcher/+spec/stop-action-plan14:46
acabotadisky_ : ok could you please add it to open discussions in the wiki14:47
acabot#topic Open discussions14:47
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"14:47
acabotadisky_ : please go ahead14:47
acabotadisky_ : do you want to be able to stop an action plan14:48
acabots/do/so14:48
adisky_acabot:14:48
adisky_yes14:48
acabotadisky_ : what will happens then, do you want to rollback previous actions ?14:48
acabotadisky_ : because your cluster could be in an unstable state14:49
vincentfrancoiseacabot: +214:49
adisky_acabot: yes, rollback of previous action, abort of ongoing, dont start pending actions14:49
*** dosaboy_ is now known as dosaboy14:50
adisky_acabot: roll-back operation can be left as user's choice14:50
acabotadisky_ : ok in this case you have to check that all previous actions can be rollbacked14:50
adisky_acabot: yes14:51
vincentfrancoiseadisky_: rollbacking is supported by taskflow so it shouldn't be a problem14:51
acabotadisky_ : I think with a basic action plan it could work but we have to think about more advanced strategies (and actions)14:51
adisky_acabot: it is a possible case that, an action plan is in "ONGOING" state from a long time. user may want to stop it.14:52
vincentfrancoiseadisky_: but workflow engines are pluggable so you have to think generic14:52
adisky_vincentfrancoise: ok14:52
acabotadisky_ : I think you can submit a spec so that we can start iterate on it, as suggested by vincentfrancoise, we can first leverage taskflow to do it14:52
adisky_acabot: ok14:53
acabot#action adisky_ submit a spec for https://blueprints.launchpad.net/watcher/+spec/stop-action-plan14:53
acabotShould we enable Watcher dashboard by default ?14:53
acabot#link https://review.openstack.org/#/c/429256/14:53
*** bklei has joined #openstack-meeting-414:54
acabotvincentfrancoise : you deactivated Watcher dashboard a couple of months ago, is the issue still present ?14:54
vincentfrancoiseacabot: if we do, it has to be tested via a gate job14:54
acabotvincentfrancoise : do you mean that we need to add a new gate job for it ?14:55
vincentfrancoiseacabot: I don't know, but that's why I'm saying we should have it covered because no one deploys a devstack everyday to check that out14:55
vincentfrancoiseacabot: could be a new one or we could modify the existing one, whichever is fine by me14:55
acabotchrisspencer yumeng__ : did you deploy watcher dashboard using devstack ?14:56
*** rbak has joined #openstack-meeting-414:56
Yumeng__yes14:56
chrisspenceracabot: yes, I have it running14:56
Yumeng__I have tried14:56
zhuronghello, I have a question, as the stackalytics http://stackalytics.com/report/contribution/watcher-group/180, licanwei from ZTE, had many contribute to watcher, I think he is qualified to be a core member in watcher14:56
*** pmesserli has quit IRC14:57
acabotzhurong : why not, could you please send an email on the openstack-dev mailing list to nominate licanwei ?14:57
*** pmesserli has joined #openstack-meeting-414:58
*** fengxia41103 has quit IRC14:58
adisky_vincentfrancoise : still not able to run any strategy with current devstack deployment due to ceilometer API deprecated, any update on this14:58
zhurongThis should be PTL nominate, I can not do this. :(14:58
acabotzhurong : no no, anyone can nominate a new core14:59
acabotwe dont have time left to discuss ceilometer API issue14:59
vincentfrancoiseacabot: but to be core, existing cores have then to approve it right?14:59
*** PerfectChaos has joined #openstack-meeting-414:59
acabotvincentfrancoise : yes, vote on the ML15:00
*** fengxia41103 has joined #openstack-meeting-415:00
adisky_acabot: ok15:00
acabotI have to end the meeting15:00
acabotthanks15:00
vincentfrancoisebye all15:00
hvprashbye15:00
Yumeng__Bye15:00
acabothave a good day/night15:00
adisky_bye15:00
acabot#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Feb  8 15:00:52 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-02-08-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-02-08-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-02-08-14.00.log.html15:00
sballe_bye15:01
*** chrisspencer has left #openstack-meeting-415:01
pshedimbbye15:01
serverascode#startmeeting operators_telco_nfv15:01
openstackMeeting started Wed Feb  8 15:01:39 2017 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
*** licanwei_ has quit IRC15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:01
openstackThe meeting name has been set to 'operators_telco_nfv'15:01
serverascodehi all, sorry was a bit late15:01
jamemccHi15:01
*** brunograz has left #openstack-meeting-415:02
serverascodehi jamemcc :)15:02
jamemccNo worries15:02
*** vincentfrancoise has left #openstack-meeting-415:02
serverascodeanyone else here for the telecom/nfv meeting?15:02
* PerfectChaos waves15:02
serverascodehi PerfecChaos :)15:02
serverascodewe'll give it another min or so to see who shows up15:03
serverascodeok so maybe just the 3 of us :) might be a nice short meeting15:04
serverascode#topic Boston summit session15:04
*** openstack changes topic to "Boston summit session (Meeting topic: operators_telco_nfv)"15:04
*** Yumeng__ has left #openstack-meeting-415:04
serverascodeI don't have much to add here, I put in a session submission but won't hear back for a while15:04
serverascodeI know adrien did as well for the massively distributed group15:04
serverascodejamemcc did you as well for LCOO?15:05
uli-khi!15:05
serverascodehi uli-k :)15:05
jamemccYes15:05
fengxia41103hello15:05
*** zaneb has left #openstack-meeting-415:05
serverascodehi gengxia4110315:06
serverascodehi fengxia41103 that is15:06
jamemcc2 one for general working group and another as a Birds of a Feather to try to introduce and make LCOO more approachable15:06
fengxia41103hi.. being first time here15:06
*** limao has quit IRC15:06
*** ntpttr_ is now known as ntpttr15:06
fengxia41103I'm a Lenovo engineer, just want to sit in15:06
serverascodeok cool thanks jamemcc, will be good to keep an eye on everyones sessions and maybe work together a bit on it15:06
fengxia41103and learn of this project :)15:06
*** limao has joined #openstack-meeting-415:06
jamemccagreed15:07
jamemccwelcome fengxia4110315:07
fengxia41103thank you jamemcc15:07
serverascodeI don't have anything else for summit session info right now15:07
serverascodethough I should mention they extended the call for presentations, so if you still want to put one in there is time15:08
serverascodealso they are managing the lightening talks insttead of the vbrown bag15:08
serverascodeso there is a lot of room to present15:08
*** ad_rien_ has joined #openstack-meeting-415:08
ad_rien_o/ (sorry for being late)15:09
serverascodehi ad_rien_ :)15:09
jamemccHi15:09
jamemccTHanks for joining15:09
serverascodead_rien_ any thoughts on Boston summit sessions?15:09
ad_rien_Hi (sorry last meeting was a bit longer than expected)15:09
serverascodeLCOO put in a request for a session, and a birds of feather15:09
jamemccThis to some extent (at least for me) is where I get together with you both15:09
ad_rien_?15:10
ad_rien_what do you mean?15:10
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:10
ad_rien_serverascode:  did you already ask for rooms?15:10
serverascodefengxia41103 that is the agenda etherpad15:10
serverascodeI did already put in a submission yes15:10
*** julim has joined #openstack-meeting-415:10
fengxia41103Got it, thank you serverascode15:10
ad_rien_From my side, I sent an email to Erin (but didn't get any answer yet)15:11
jamemccI meant that for me this is a good touch base point between LCOO and Ops-Telco-NFV and Massive Scalable15:11
ad_rien_It was unclear how to perform such a request (i.e. room for face-to-face meetings)15:11
serverascodead_rien_ my impression was you actually put in a request through the CFP system15:11
serverascodebut email might work too15:12
ad_rien_I did both so wait and see.15:12
jamemccAdrien, I can walk you through it if desired- you do it just as if you were requesting a real presentation at the Summit15:12
serverascodeok cool15:12
jamemccok15:12
*** jose-phillips has joined #openstack-meeting-415:13
*** pmesserli has quit IRC15:13
ad_rien_jamemcc:  sorry your point is that we can take part to the BOF of LCOO? so we can discuss possible collaborations between our WG?15:13
ad_rien_s/WG/WGs/15:13
jamemccYes - that's right15:13
*** pmesserli has joined #openstack-meeting-415:13
jamemccThough I think we are also doing that here and we'll get to that today15:13
ad_rien_I think it is valuable definitely15:13
serverascodeok that is a good segue :)15:14
serverascode#topic Discuss LCOO a bit15:14
*** openstack changes topic to "Discuss LCOO a bit (Meeting topic: operators_telco_nfv)"15:14
jamemccjust a sec15:14
jamemccok - related and a little more near term - the Ops Meetup - Did we cover that before15:14
ad_rien_Actually it seems that several (important) members from the community request/agree that having a shared sessions for all WG chair makes sense.15:14
ad_rien_I'm wondering who is going to arrange/animate such a session15:14
serverascodeI'll put the ops meetup on the agenda15:15
serverascodewe haven't discussed it much recently15:15
ad_rien_BTW jamemcc I'm in touch with Abdelhadi Chari that is involved in the Massively Distributed WG (i.e. a few engineers from Orange actually but I'm used to work with Abdelhadi)15:15
serverascodelet's just chat about LCOO briefly what with all the recent emails :)15:15
ad_rien_:)15:16
jamemccGreat - thanks for connecting the thread - I didnt' know that15:16
jamemccOk - brief is ok15:16
*** SerenaFe_ has quit IRC15:16
serverascodeI just see some added sections in the agenda, presumably you added those jamemcc?15:16
jamemccYes - just a few minutes before the meeting15:17
serverascodeif you want to discuss any of those points just go ahead15:17
ad_rien_(Actually we are working with Orange since three years on revising OpenStack to operate Fog/Edge infrastructres, i.e. http://beyondtheclouds.github.io)15:17
jamemccSo the first thing and maybe this is the brief part - Any advice/insight as to the questions that have come up?15:17
*** pmesserli has quit IRC15:17
ad_rien_Which ones (IOW, which are the most important from your point of view)?15:18
jamemccI shoudl ahve had the links ready, let me know and I can find them in a minute or 215:18
serverascodeIt is an interesting situation, I think it's kind of a first for openstack15:18
serverascodemost of the groups have been based on individuals15:19
jamemccGood questions asked about what is this new WG and why does it seem so somilar to Telco NFV and Massive Scalable15:19
ad_rien_Jay is still challenging every change15:19
serverascodehe hasn't emailed for a while15:19
serverascodebut his points are all good15:19
ad_rien_I think this is the way he uses to make things progressing15:19
*** sacharya has joined #openstack-meeting-415:20
ad_rien_There are overlaps between NFV and Massively distributed definitely15:20
serverascodeI think his major thing is to make sure that the core openstack components are considered15:20
jamemccexchanges taht did seem to push forward15:20
*** baoli has quit IRC15:20
ad_rien_serverascode:  you mean?15:20
serverascodeeg the gluon project vs neutron15:20
ad_rien_ok15:20
*** dave-mccowan has quit IRC15:20
serverascodeimproving core systems as opposed to writing something new15:21
ad_rien_sometimes he made some tweets on the fact that OpenStack will dissapear in favor of OpenNFV ;)15:21
ad_rien_but actually this is our position in the massively distributed WG15:21
serverascodeyeah I read those as well15:21
ad_rien_and he made also some remaks a few months ago15:21
ad_rien_and it is clear in the definition of the WG15:22
ad_rien_OpenSTack and Upstream first15:22
ad_rien_the issue is that it takes times15:22
jamemccI guess the fer is that a group like LCOO might be creating new things in a vacumn and seems to me the actionable aspect of that for us here is to make sure we aren't adding to that dynamic with multiple WG and in fact helping to bring more parties together15:22
ad_rien_OpenStack has been historically designed/developed to operate single site cloud infrastructure15:22
*** jose-phillips has quit IRC15:22
serverascodejamemcc: right15:23
ad_rien_Now academics and industry experts agree that clouds should move to a more distributed model. The question is that should we do it with OpenStack or not15:23
ad_rien_Doing without (i.e. developping from sratch) looks to be a non sense15:23
serverascodead_rien_ good point, the massively distributed concept is contentious as well :)15:23
ad_rien_but at the same time we need to have some folks from the core developers that can hear our requests/whishes15:24
ad_rien_otherwise, there will be a fork for sure15:24
serverascodeyes that is a difficult issue15:24
ad_rien_We spoke/exchanged a lot with ttx15:24
ad_rien_but we need to find15:25
ad_rien_additional persons15:25
ad_rien_that argue for such a change in the design15:26
*** hongbin has joined #openstack-meeting-415:26
ad_rien_i.e. ensuring that OpenStack core services can cope with WANwide deployments15:26
ad_rien_IT seems that now more and more persons are interested by that15:26
ad_rien_and not only for NFV/SDN use-cases15:26
*** zz_ja has joined #openstack-meeting-415:26
ad_rien_(don't get me wrong, NFV/SDN use-cases are valuable too ;))15:26
*** nkrinner is now known as nkrinner_afk15:27
ad_rien_I just say that we need additional use-cases that can justify the needs of having clouds operated by the same provider but geographically disrtibuted15:27
serverascodeok, there is a lot of change afoot :)15:27
*** limao_ has joined #openstack-meeting-415:27
serverascodebut we should stick to advice for LCOO if any for this topic15:27
serverascodeanyone have any advice to share?15:27
serverascodeI will just say 1) work upstream 2) work with core components as much as reasonable 3) use openstack community tools as much as possible15:28
*** krtaylor has quit IRC15:28
uli-kI think it is not only about "operated by the same provider".15:28
ad_rien_I  think a valuable goal is to identify what are the missing components or at least the core-services that does not cope with requirements.15:29
ad_rien_and to have strong arguments to say why (for instance performance experiments).15:29
uli-kIt is about sharing the resources of different sites, so somebody can assign workloads flexibly between sites or tie them to a specific site.15:29
ad_rien_uli-k: I agree but this makes the big picture more complex15:29
uli-kI know :(15:29
ad_rien_my idea/vision (that can be wrong) is something like TPC/IP two decades ago15:30
*** SergeM has joined #openstack-meeting-415:30
*** Swami_ has joined #openstack-meeting-415:30
ad_rien_so if OpenStack can natively cooperate like TCP/IP does15:30
*** limao has quit IRC15:30
ad_rien_then each time you plug two openstack deployment they will be able to colloborate in a native manner15:30
*** duonghq has joined #openstack-meeting-415:30
jamemccThanks Curtis15:30
ad_rien_then we can be sure that peering agreement between operatos etc…. will come to the surface15:31
*** caowei has quit IRC15:31
jamemccAdrien, That's a nice simple explanation/start of a user story15:31
ad_rien_AFAIK right now, this is rather not evident to operate a significant number of small DCs15:31
serverascodethat sounds more like federation than distributed15:31
ad_rien_you can use the regions to operate a few DCs but if you consider to deploy a small DC (let's say two racks) in each Network of Point of Presence, then it will become a nightmare to operate that with the region concept15:32
ad_rien_maybe the cells concept can be better (especially with the revision of cell V2) but this is not clear yet… in particular because the cell is just for Nova :(15:32
matrohonad_rien_, if you refer to AS interconnection, eBGP would be a better model I think :)15:33
*** Swami has quit IRC15:33
ad_rien_it depends.. do you want to have a glance repository in every site.15:33
ad_rien_matrohon:  yes15:33
serverascodeok, unfortunately we should probably move on in our agenda15:33
serverascodevery interesting topic though15:33
jamemccIN terms of LCOO next steps we are trying to form functional specialty teams (SME teams) in the areas/groups I listed in the Etherpad.  We'll try to be bringing user stories out of thise teams and in time for the Boston Forum and where applicable (cross project and cross release) through PWG User Story process.15:33
*** iyamahat has joined #openstack-meeting-415:33
ad_rien_jamemcc:  what kind of user stories are you expecting for intance for the container item .15:34
jamemccAs User Stories that seem related to Telco/NF or assive Scalable - I'll bring here as well15:34
ad_rien_?15:34
serverascodeare you planning on the user stories first, then to start actual coding projects?15:34
jamemccThe main one would be to spin up and manage the control plane15:34
jamemccThe details of the User Story would be what personas need what out of all that15:35
jamemccSeems very reaalted to scalable too15:36
serverascodewhat's LMA stand for?15:36
jamemccJust an example - I'm not the one per se to submit the User Story15:37
jamemccLMA is this https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjbqs2k6oDSAhXkjFQKHW7DDNAQFggoMAA&url=https%3A%2F%2Fwww.mirantis.com%2Fblog%2Fmos-7-0-logging-monitoring-alerting-lma-enhancements%2F&usg=AFQjCNFVNx6V_sBxfiXqiXhUc2C3PI-6jQ&sig2=A_5hHwUIO7pTCDZTLYpxEQ15:37
jamemccoops15:37
*** krtaylor has joined #openstack-meeting-415:38
*** dave-mccowan has joined #openstack-meeting-415:38
serverascodeah ok15:38
jamemcchttps://www.mirantis.com/blog/mos-7-0-logging-monitoring-alerting-lma-enhancements/15:38
jamemccBut the team is more about that subject area - kind of a bad example as it seems to suggest the team has alredy chose15:39
serverascodeand is the plan to work on user stories first, then to start to understand what devleopment work needs to be done?15:39
jamemccn the project15:39
*** chem has left #openstack-meeting-415:39
*** duonghq has quit IRC15:39
jamemccYes15:39
*** wxy| has joined #openstack-meeting-415:39
serverascodeok, sounds good to me :)15:40
serverascodeI think you might get some questions around the sub groups15:40
serverascodeas there are some existing working groups in those areas, but not all, but I could forsee questions on that15:41
serverascodeany other thoughts on this topic? should perhaps move onto the milan ops meetup15:41
jamemccok to move on - thanks for feedback15:42
*** julim has quit IRC15:42
serverascode#topic Milan Operators Meetup15:42
*** openstack changes topic to "Milan Operators Meetup (Meeting topic: operators_telco_nfv)"15:42
jamemccAdrien - I'll pass on the notes you put in to those teams as they get started15:42
serverascodeI should first say that I'm not sure I will be attending15:42
ad_rien_jamemcc:  not sure I understood, are you expecting some actions from my side?15:43
serverascodejamemcc are you going? are others from the LCOO going?15:43
jamemccYeah - not clear for me either to attend in Milan15:43
jamemccJust wanted to clear the air15:43
serverascodeI know shintaro from NTT will be there, or I think he will15:43
ad_rien_serverascode:  I will not attend the Milan meeting15:43
serverascodeother than that I'm not sure how many ppl working in NFV related fields will be there15:43
*** julim has joined #openstack-meeting-415:43
serverascodeok so perhaps there is not much to discuss here :)15:44
jamemccok - Adrien - no action needed form you - until the team (assumign we can get started) wants to collaborate - then we'd reach out to you15:44
ad_rien_ok thanks for the clarification15:44
*** limao_ has quit IRC15:45
serverascodeok if no other thoughts on that then next topic...15:45
serverascode#topic Generic NFV Platform Definition document15:45
*** openstack changes topic to "Generic NFV Platform Definition document (Meeting topic: operators_telco_nfv)"15:45
*** caboucha has joined #openstack-meeting-415:45
serverascode#link https://etherpad.openstack.org/p/generic-nfv-platform15:45
serverascodeI am still just entering sections and occasionally writing in that document, and I will just keep doing so over the next while15:45
serverascodeplease feel free to add or edit or suggest or critique :)15:46
*** Swami has joined #openstack-meeting-415:47
serverascodeany thoughts on that at all?15:47
ad_rien_Is CloudRan a NFV use-case?15:47
ad_rien_If yes I think we should invite some Orange folks15:48
*** yamahata has joined #openstack-meeting-415:48
ad_rien_Because we had some discussions and they have a use-case that looks really interesting to illustrate the interest of a disitrbuted infrastructure15:48
serverascodeI'm not super familar with cloudran, what exactly is that?15:48
ad_rien_with all advanced features you can envision15:48
ad_rien_matrohon:  still there ?15:48
matrohonyep15:49
ad_rien_you want to give a few words on that or should I?15:49
*** janki has quit IRC15:49
matrohoncloudran is the same as vRAN :)15:49
ad_rien_ok15:49
ad_rien_thanks:D15:49
matrohonthe ability to manage compnent of 4G/5G design in VM15:49
ad_rien_briefly the idea is to virtualize as much features as possible15:49
matrohonfrom antenna component to backends15:50
*** Swami_ has quit IRC15:50
serverascodewhat kind of special features does that typically require? real time kernel?15:50
ad_rien_some features cannot be deployed in centralized clouds due to latency constraints15:50
ad_rien_whereas other can be put higher in the infrastructure15:50
matrohonsome of those VM will need to be as close as possible to the antenna (law latency) whereas some other might move to a central DC15:50
ad_rien_(lower = edge, ie. at the bottom of the radio base station, higher, means the traditional DC)15:50
*** limao has joined #openstack-meeting-415:51
ad_rien_so ou have placement issues15:51
ad_rien_network issues15:51
ad_rien_etc..15:51
*** Sukhdev has joined #openstack-meeting-415:51
ad_rien_because some VMs should be interconnected (i.e. they exchange messages) while not being located on the same site15:51
serverascodeso cloudran would require a distributed hypervisor type setup?15:51
ad_rien_so you have wanwide-related issues15:51
ad_rien_if by hypervisor you mean openstack yes15:52
ad_rien_if by hypervisor your mean KVM15:52
ad_rien_the answer is no15:52
serverascodeso a separate cloud in the radio base station?15:52
ad_rien_there is different scenarios15:52
ad_rien_you can have only compute nodes deployed at the bottom of radio base stations15:52
ad_rien_and the control services in one centralized cloud15:53
serverascodeI think for this "generic NFV platform" it would probably just start with one single openstack deployment15:53
ad_rien_so only one openstack to operate this infrastructure15:53
ad_rien_exactly15:53
ad_rien_here you have only one openstack15:53
serverascodeok yeah then that is a potential use case sure15:53
ad_rien_(please keep in mind that in our vision, i.e. the massively distribetud WG, there is/will be always one OpenStack)15:53
serverascodeis there one of those use-case diagrams for this model? I know you had a bunch of diagrams15:53
*** cleong has joined #openstack-meeting-415:53
ad_rien_yes15:53
ad_rien_let me find the url15:54
serverascodethe only problem is that the massively distributed doesn't really exist yet, in my mind, right?15:54
matrohona use case that needs to scale to potentially thousand hundreds of compute...15:54
serverascodethere's no code in openstack yet to do that15:55
ad_rien_#link https://docs.google.com/presentation/d/1jJFZejZqgYDxu5FX4K8g3I5zQ87afnjYI4VSRSuCQ6U/edit#slide=id.p different manner to operate distinct DCs15:55
serverascode(5 min letf)15:55
ad_rien_all the architecture deployment that are presented in these google slides15:55
ad_rien_are valid15:55
ad_rien_i.e. you can deploy them now15:55
ad_rien_and it will run15:55
serverascodeok, will take a look :)15:55
ad_rien_the question is that as matrohon mentioned, the scalability15:55
ad_rien_issue15:55
ad_rien_the latency issue15:55
ad_rien_some features that do not run well in a WAN context15:56
ad_rien_etc…15:56
ad_rien_the main issue is that when we discuss with core developer of Openstack15:56
ad_rien_they argue that you can already deal with the use-case we are discussing15:56
ad_rien_by selecting one of the archtecture illustrated in those slides.15:56
ad_rien_what we would like to do is to identify the issues/barriers and show them that they are wrong (or right ;))15:57
serverascodeok, I'd like to leave the last couple of min for open discussion15:57
serverascode#topic open discussion15:57
*** egonzalez has joined #openstack-meeting-415:57
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"15:57
*** inc0 has joined #openstack-meeting-415:57
serverascodeanyone have anything they would like to add?15:57
serverascodePerfectChaos?15:58
serverascodeuli-k?15:58
ad_rien_serverascode:  may I ask you whether you can clarify the difference between distributed and federated (i.e. not now but maybe we can discuss it next time)15:58
serverascodeyeah we will have to discuss that at some point15:58
ad_rien_thanks15:58
serverascodeespecially if our presentation is selected :)15:58
ad_rien_:-P15:58
serverascodefengxia41103?15:59
*** mandre has joined #openstack-meeting-415:59
*** sp_ has joined #openstack-meeting-415:59
*** mgiles has joined #openstack-meeting-415:59
* uli-k happy if we discuss CloudRan, but also no expert.....15:59
serverascode20 seconds left :)15:59
*** bklei_ has joined #openstack-meeting-415:59
PerfectChaosI don't really have anything to discuss this time...15:59
serverascodethanks everyone for this week, lots going on in the NFV and OpenStack world15:59
serverascode#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Feb  8 16:00:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
ad_rien_thanks16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-02-08-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-02-08-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-02-08-15.01.log.html16:00
*** pmesserli has joined #openstack-meeting-416:00
*** fengxia41103 has quit IRC16:00
*** zhubingbing has joined #openstack-meeting-416:00
inc0#startmeeting kolla16:00
openstackMeeting started Wed Feb  8 16:00:28 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
zhubingbingo/16:00
openstackThe meeting name has been set to 'kolla'16:00
*** ad_rien_ has left #openstack-meeting-416:00
inc0#topic rollcall, w00t!16:00
*** openstack changes topic to "rollcall, w00t! (Meeting topic: kolla)"16:00
sdakezhubingbing you jumped the gun :)16:00
inc0you know what to do16:00
sdakew00t16:00
berendto/ woot16:00
egonzalezwoot o/16:01
zhubingbingwoot16:01
krtayloro/16:01
zhubingbingw00t!!16:01
*** bklei_ has quit IRC16:01
zhubingbing-)16:01
akwasnieHi:)16:01
inc0welcome back akwasnie!16:01
*** PerfectChaos has quit IRC16:01
akwasnieFinally!16:01
sdakelong time no see akwasnie - welcome back :)16:01
Jeffrey4lo/16:01
*** PerfectChaos has joined #openstack-meeting-416:01
zhubingbingwelcome back!!16:01
akwasnieThanks! I missed you guys16:01
*** vhosakot has joined #openstack-meeting-416:01
akwasnieI am in Usa now:)16:01
sp_0/16:02
vhosakot0/16:02
*** caowei has joined #openstack-meeting-416:02
egonzalezwelcome o/16:02
*** PerfectChaos has quit IRC16:02
mandreo/16:02
*** srwilkers has joined #openstack-meeting-416:02
*** bklei has quit IRC16:02
inc0right... let's move on, agenda seems busy16:02
inc0#topic announcements16:02
*** SergeM has quit IRC16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
*** gema has joined #openstack-meeting-416:03
*** armax has joined #openstack-meeting-416:03
sdakei've got one16:03
*** klindgren has joined #openstack-meeting-416:03
inc0soo, we are in the middle of pre-release16:03
*** jascott1 has joined #openstack-meeting-416:03
*** duonghq has joined #openstack-meeting-416:03
inc0so I'd encourage everyone to focus on bugs in kolla and kolla-ansible16:03
sdakei am doing a seminar at 2:00 PM MST for 2 hours on all 3 kolla deliverables - see ml for more details :)16:03
inc0so we can deliver another kickass release early March16:03
sdakeon feb 15th that is :)16:03
Jeffrey4lwe may have to create rc1 tag and ocata branch this week.16:03
sdakeand inc0 ^^^ :)16:04
caoweio/16:04
klindgreno/16:04
duonghqo/ sorry for late, my fiber connection has gone by someway16:04
gemao/16:04
inc0ok, let's move on to meeting itself16:04
jascott1o/16:04
krtaylorquick introduction, I'm getting more involved with the intention of making things work on ppc64le architecture16:04
inc0#topic dumb-init  vs tini16:04
Jeffrey4lthen fix bug require a real bug number, and fix master first then back port into ocata branch.16:04
*** openstack changes topic to "dumb-init vs tini (Meeting topic: kolla)"16:04
srwilkerso/16:04
*** Rockyg has joined #openstack-meeting-416:04
*** Syed__ has joined #openstack-meeting-416:04
inc0Jeffrey4l, you're up16:04
pbourkeo/16:04
Jeffrey4lyes.16:04
Jeffrey4lthanks.16:04
Jeffrey4lit is related to this patch https://review.openstack.org/43010816:05
zhubingbingagree jeffrey4116:05
britthouser0/16:05
Jeffrey4lsome background:  docker 1.13 provide init process now.16:05
*** galstrom_zzz is now known as galstrom16:05
Jeffrey4lwhich is using tini16:05
Jeffrey4l#link https://github.com/krallin/tini16:05
Jeffrey4lso i think we should sync with docker use the same init solution?16:06
sdakemy two concerns when Jeffrey4l raised this last night were the license may have been funky - that is not the case - and why fix what isn't broken - which is  open for debate16:06
inc0Jeffrey4l, I'd say not in Ocata16:06
berendtdumb-init has still active upstream?16:06
inc0and in Pike we can explore even pinning to docker 1.1316:06
Jeffrey4lanother reason is: dumb-init 1.2.0 works wired.16:06
sdakeinc0 or introducing entirely new runtimes even ;-)16:07
Jeffrey4lthat why we revert the dumb-init 1.2.0 patch.16:07
*** unicell has joined #openstack-meeting-416:07
Jeffrey4linc0, this is not related the docker 1.13. this patch do not pin kolla to docker 1.13.16:07
inc0we don't know if tini works any better16:07
Jeffrey4lcheck the change, the gate works.16:07
inc0I know, but you're saying docker 1.13 will use it out of the box right16:07
*** marst has joined #openstack-meeting-416:07
inc0?16:07
berendti would prefer to not change as long as dumb-init is working for us16:07
pbourkedumb-init is not working for us16:08
*** duonghq_ has joined #openstack-meeting-416:08
pbourkeits busted in latest relase16:08
pbourketini is the upstream docker solution16:08
berendtbut not yet, right?16:08
*** unicell1 has quit IRC16:08
Jeffrey4lwe hit this issue https://github.com/Yelp/dumb-init/issues/13616:08
inc0so I'm really reluctant to make this kind of change after ocata-3:/16:08
*** duonghq is now known as duonghq__16:09
*** penfold has joined #openstack-meeting-416:09
*** duonghq_ is now known as duonghq16:09
Jeffrey4linc0, if we wanna to pin docker 1.13 use the its init solution.16:09
*** mgoddard has joined #openstack-meeting-416:09
pbourkewe could stick with dumb-init 1.2 till pike16:09
berendtis it not possible to fix dumb-init?16:09
inc0Jeffrey4l, that's my point16:09
Jeffrey4lwe have to run container like "docker run --init xx" a new parameter.16:09
*** flaper87 has joined #openstack-meeting-416:09
sdakewe are not pinning to 1.13 in ocata release :(16:09
inc0we can drop our own init alltogether16:09
inc0not in ocata sda16:09
inc0sdake,16:09
sdakeright16:09
sdakeok all good then :)16:09
Jeffrey4lok. i am fine with that ;)16:09
inc0what we have now, works, issue is with dump-init 1.216:10
inc0which we don't have to use16:10
inc0but that puts dump-init on notice (I recently learned new phrase in English!)16:10
inc0and in Pike we can explore either switching to tini or looksing init completely and pin to docker 1.1316:11
inc0but that will require some discussion in ops community16:11
Jeffrey4lok. i will give a -2 to my patch until Pike.16:11
inc0right, anything else in that topic?16:11
Jeffrey4li am done .16:11
berendtshould we open a blue print for it?16:12
inc0berendt, +1 to that16:12
klindgrenwould tini allow someone to provide a default overide-able start command for each container?16:12
Jeffrey4lklindgren, tini not. but docker 1.13 yes.16:12
*** limao has quit IRC16:12
berendtJeffrey4l: do you open a blueprint for it?16:13
Jeffrey4lthere is a parameter "--init-path" in docker 1.1316:13
inc0klindgren, we could do this with or without tini16:13
Jeffrey4lberendt, np. i will16:13
inc0with templates16:13
*** limao has joined #openstack-meeting-416:13
*** sbezverk has joined #openstack-meeting-416:13
inc0but that's different discussion:) feel free to ping me after meeting and we'll talk about it16:13
Jeffrey4lanother topic is pin docker 1.13. not it is not properly for current. ;)16:13
inc0ok moving on16:14
inc0#topic PTG Schedule finalization16:14
*** openstack changes topic to "PTG Schedule finalization (Meeting topic: kolla)"16:14
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule16:14
inc0still 2 kolla-k8s sessions not filled16:14
*** xingchao_ has quit IRC16:14
inc01 session not filled:)16:15
*** matrohon has quit IRC16:15
*** baoli has joined #openstack-meeting-416:16
sdakewould be nice to know who pink was to provide clrity on that potentially duplicate session16:18
sdakei think operator feedback is not really a design session topci which #5 looks like16:18
vhosakotteam, sorry to say I'll miss the PTG as I'm attending my company's conference in Berlin the same exact days as PTG.  good thing is, I'll be presenting kolla to the customers and will try to get more contributors for us :)16:19
*** salv-orl_ has quit IRC16:19
inc0vhosakot, shame, but alcohol we would drink will only get older this way = better16:20
*** mfedosin has joined #openstack-meeting-416:20
sbezverksdake: hmm I added it and it sounds clear to me16:20
vhosakotinc0: haha :)16:20
sdakesbezverk cool - coud yoou ahve a look and tell me if it is still clear?16:21
krtaylorI guess it is safe to assume that each main number in the etherpad = one 40-50 min session?16:21
inc0sbezverk, that's the issue, everything sounds clear to someone who made it;)16:21
inc0krtaylor, correct16:21
sdakekrtaylor that is what we have done at every midcycle in tehe past ;)16:21
vhosakotare the PTG seesions available on webex or recorded by any chance?16:21
sdakevhosakot inc0 is sorting out remote participation16:21
inc0you'll be able to call into it16:21
inc0but  I don't think we'll record as it's legally iffy16:22
vhosakotsdake: great, yes, I'd love to catch up on videos/recordings please.16:22
krtaylorthanks, just wanted to be clear as I will be in a cab for the first couple :(16:22
vhosakotinc0: cool, calling in is great16:22
*** iyamahat has quit IRC16:23
inc0krtaylor, we can bring you up to speed afterwards16:23
krtaylorthx!16:23
sdakequestion what is day 1 #2 about?16:23
*** david-lyle has joined #openstack-meeting-416:23
inc0sdake, we have some strange wiring between projects now16:23
sdakeso this is cross-repo gating or somethign ele?16:24
inc0kolla using ansible gates, kolla-ansible configs in kolla-k8s16:24
inc0all that stuff16:24
sdakewould like to have some context to prep properly :)16:24
sdakei see - could you add more detials on that one ?16:24
sdakei think the rest ono day 1 are pretty clear16:24
inc0sure16:24
sdakenow for day 2:)16:24
egonzalezyep, looks very confussion by the name16:24
*** zhurong has quit IRC16:25
*** unicell has quit IRC16:25
sdakeday 2 has some topics16:27
sdakerather adjustments16:27
*** woodard has quit IRC16:28
*** woodard has joined #openstack-meeting-416:29
gemamultiarch? where would it go?16:29
gemawaiting list?16:29
gemacoffee break?16:30
*** limao has quit IRC16:30
krtaylorlol16:30
*** limao has joined #openstack-meeting-416:30
*** iyamahat has joined #openstack-meeting-416:31
inc0right, I think schedule looks good16:31
inc0we'll take one more look at it next week16:31
inc0and I'll put hours there:)16:31
*** anilvenkata has quit IRC16:32
*** woodard has quit IRC16:32
inc0#topic release notes (timebox 15min)16:32
*** openstack changes topic to "release notes (timebox 15min) (Meeting topic: kolla)"16:32
sdakeplease for the love of god do release notes for kolla-kubernetes16:32
*** yfauser_ has joined #openstack-meeting-416:32
inc0I'd like everyone to try to recall changes that has been made in this release and confirm that reno notes has been made16:32
sdakea lot of peopel read them and track our progress16:32
inc0now I'm talking about kolla-ansible/kolla;)16:33
sdakeinc0 ahh sorry :)16:33
inc0as we actually release these16:33
Jeffrey4lprepare an etherpad link?16:33
sdakeinc0 right - my statement still stands and I hoep you supoprt it:)16:33
inc0Jeffrey4l, good point, let me do this16:33
zhubingbing+116:34
inc0#link https://etherpad.openstack.org/p/kolla-ocata-release-notes16:34
inc0sdake, there are many ways to track progress, release notes aren't normally meant for this;)16:34
inc0but back on track, let's note what is not in reno and collectively fix these16:35
inc0I'm especially interested in upgrade notes, this has to be up to date16:35
*** yfauser has quit IRC16:36
*** sdake_ has joined #openstack-meeting-416:36
*** padkrish has joined #openstack-meeting-416:37
*** sdake has quit IRC16:38
*** caowei has quit IRC16:38
*** jovon has joined #openstack-meeting-416:39
sdake_can someone link the release notes etherpad, my network dc'ed16:41
berendtsdake_: https://etherpad.openstack.org/p/kolla-ocata-release-notes16:42
sdake_tx16:42
*** limao has quit IRC16:42
*** zhubingbing has quit IRC16:43
*** iyamahat has quit IRC16:48
*** jimbaker has joined #openstack-meeting-416:48
*** jimbaker is now known as Guest3555216:49
*** yamahata has quit IRC16:49
inc0ok we're running out of out timebox:)16:49
inc0few more minutes and let's leave some time for open discussion for a change16:49
*** ricolin has quit IRC16:50
*** galstrom is now known as galstrom_zzz16:50
*** Guest35552 is now known as jimbaker`16:51
inc0allright, so everyone, don't stop after meeting, take a longer look at release notes16:51
inc0these are really really important16:51
inc0especially if some step needs to be made between upgrades16:52
inc0also, we need to fill them so please add missing notes to repo16:52
inc0#topic Open discussion16:52
*** openstack changes topic to "Open discussion (Meeting topic: kolla)"16:52
*** david-lyle has quit IRC16:52
inc08 minutes left, anyone has anything they'd like to share16:52
inc0?16:52
*** Guest66676 is now known as Guest666616:53
gemaI'd like to ask for reviews of this patch: https://review.openstack.org/#/c/430940/16:53
jascott1can day 1 #7 be about helm features we might need also?16:54
*** sacharya has quit IRC16:54
sdake_jascott1 that would be a better use of time I think16:54
*** sacharya has joined #openstack-meeting-416:54
*** salv-orlando has joined #openstack-meeting-416:54
Jeffrey4lgema, how can i get ppc docker base image?16:55
jascott1we might be able to cover it all in the 'helming hour'16:55
*** jimbaker` has quit IRC16:55
*** jimbaker` has joined #openstack-meeting-416:55
*** jimbaker` is now known as jimbaker16:55
Jeffrey4ldoes docker provide this?16:55
gemaJeffrey4l: krtaylor may be able to answer that16:55
krtaylornot off the top of my head, let's discuss after meeting and I'll find out16:56
gemaJeffrey4l: may be worth adding the question to the patch16:56
Jeffrey4lyep.16:56
gemaand bring the conv there16:56
krtaylorbtw, also reviewing that now16:57
gemathanks!16:57
Jeffrey4lOT: dumb-init do not provide ppc edition16:58
inc0meh16:59
inc0well we're removing it anyway;)16:59
inc0ok guys16:59
inc0thank you for coming!16:59
inc0#endmeeting kolla16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Feb  8 16:59:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-08-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-08-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-08-16.00.log.html16:59
*** revon has joined #openstack-meeting-416:59
*** egonzalez has left #openstack-meeting-417:00
*** vhosakot has left #openstack-meeting-417:00
*** mgiles has left #openstack-meeting-417:00
*** jascott1 has left #openstack-meeting-417:00
*** baoli has quit IRC17:03
*** marst_ has joined #openstack-meeting-417:03
*** marst has quit IRC17:03
*** gema has left #openstack-meeting-417:04
*** delattec has joined #openstack-meeting-417:07
*** delatte has quit IRC17:08
*** duonghq has quit IRC17:08
*** wxy| has quit IRC17:10
*** pmesserli has quit IRC17:12
*** david-lyle has joined #openstack-meeting-417:12
*** pmesserli has joined #openstack-meeting-417:12
*** pmesserli has quit IRC17:13
*** pmesserli has joined #openstack-meeting-417:13
*** cwolferh has left #openstack-meeting-417:13
*** woodard has joined #openstack-meeting-417:23
*** armax has quit IRC17:23
*** armax has joined #openstack-meeting-417:24
*** Swami has quit IRC17:27
*** pmesserli has quit IRC17:28
*** pmesserli has joined #openstack-meeting-417:29
*** Sukhdev has quit IRC17:31
*** baoli has joined #openstack-meeting-417:32
*** armax has quit IRC17:32
*** pmesserli has quit IRC17:33
*** topol_ is now known as topol17:33
*** padkrish has quit IRC17:38
*** armax has joined #openstack-meeting-417:39
*** padkrish has joined #openstack-meeting-417:40
*** mgoddard has quit IRC17:40
*** Swami has joined #openstack-meeting-417:42
*** ltomasbo is now known as ltomasbo|away17:52
*** ralonsoh has quit IRC18:02
*** joedborg has quit IRC18:03
*** padkrish has quit IRC18:04
*** pmesserli has joined #openstack-meeting-418:07
*** unicell has joined #openstack-meeting-418:09
*** srwilkers has quit IRC18:12
*** padkrish has joined #openstack-meeting-418:16
*** marst_ has quit IRC18:16
*** iyamahat has joined #openstack-meeting-418:23
*** marst has joined #openstack-meeting-418:25
*** rwallner has joined #openstack-meeting-418:35
*** masteinhauser has quit IRC18:35
*** Kevin_Zheng has quit IRC18:35
*** MarkAtwood has quit IRC18:35
*** yifei_ has quit IRC18:35
*** qwang has quit IRC18:35
*** portdirect has quit IRC18:35
*** robcresswell has quit IRC18:35
*** Dmitrii-Sh has quit IRC18:35
*** duonghq__ has quit IRC18:35
*** jovon has quit IRC18:35
*** kozhukalov has quit IRC18:35
*** dtardivel has quit IRC18:35
*** carl_baldwin has quit IRC18:35
*** wolsen has quit IRC18:35
*** amit213 has quit IRC18:35
*** alex_didenko has quit IRC18:35
*** zeestrat has quit IRC18:35
*** dasanind has quit IRC18:35
*** sindhu has quit IRC18:35
*** dham1 has quit IRC18:35
*** nikhil has quit IRC18:35
*** janonymous has quit IRC18:35
*** meteorfox has quit IRC18:37
*** patrickeast has quit IRC18:37
*** chigang has quit IRC18:37
*** ediardo has quit IRC18:37
*** izaakk has quit IRC18:37
*** cargonza has quit IRC18:37
*** macsz has quit IRC18:37
*** igormarnat_ has quit IRC18:37
*** asingh_ has quit IRC18:37
*** csatari has quit IRC18:37
*** akwasnie has quit IRC18:37
*** raddaoui has quit IRC18:37
*** turvey has quit IRC18:37
*** ildikov has quit IRC18:37
*** padkrish has quit IRC18:38
*** padkrish has joined #openstack-meeting-418:41
*** pasquier-s has quit IRC18:45
*** berendt has quit IRC18:45
*** serverascode has quit IRC18:45
*** ashtokolov has quit IRC18:45
*** RaginBajin_ has quit IRC18:45
*** gmann has quit IRC18:45
*** betherly has quit IRC18:45
*** sridhar_ram has quit IRC18:45
*** aimeeu has quit IRC18:45
*** johnsom has quit IRC18:45
*** vdrok has quit IRC18:45
*** NachoDuck has quit IRC18:45
*** sballe_ has quit IRC18:45
*** hogepodge has quit IRC18:45
*** uli-k has quit IRC18:45
*** aglarendil has quit IRC18:45
*** tdurakov has quit IRC18:45
*** TheJulia has quit IRC18:45
*** yamahata has joined #openstack-meeting-418:46
*** sambetts is now known as sambetts|afk18:47
*** galstrom_zzz is now known as galstrom18:52
*** s3wong has joined #openstack-meeting-418:53
*** Sukhdev has joined #openstack-meeting-418:54
*** dharinic is now known as dharinic|lunch18:58
*** hemanthm is now known as hemanthm|lunch19:10
*** NachoDuck has joined #openstack-meeting-419:21
*** vishnoianil has quit IRC19:21
*** rwallner has quit IRC19:22
*** masteinhauser has joined #openstack-meeting-419:24
*** padkrish has quit IRC19:24
*** julim has quit IRC19:25
*** julim has joined #openstack-meeting-419:27
*** serverascode has joined #openstack-meeting-419:31
*** kozhukalov has joined #openstack-meeting-419:33
*** MarkAtwood has joined #openstack-meeting-419:37
*** sballe_ has joined #openstack-meeting-419:37
*** sridhar_ram has joined #openstack-meeting-419:39
*** dtardivel has joined #openstack-meeting-419:40
*** alex_didenko has joined #openstack-meeting-419:42
*** uli-k has joined #openstack-meeting-419:43
*** Kevin_Zheng has joined #openstack-meeting-419:43
*** padkrish has joined #openstack-meeting-419:43
*** Dmitrii-Sh has joined #openstack-meeting-419:43
*** krtaylor has quit IRC19:45
*** sacharya has quit IRC19:47
*** salv-orlando has quit IRC19:48
*** sacharya has joined #openstack-meeting-419:48
*** dharinic|lunch is now known as dharinic19:49
*** carl_baldwin has joined #openstack-meeting-419:50
*** aglarendil has joined #openstack-meeting-419:51
*** ashtokolov has joined #openstack-meeting-419:51
*** betherly has joined #openstack-meeting-419:51
*** qwang has joined #openstack-meeting-419:53
*** meteorfox has joined #openstack-meeting-419:54
*** pasquier-s has joined #openstack-meeting-419:54
*** MeganR has joined #openstack-meeting-419:55
*** robcresswell has joined #openstack-meeting-419:55
*** dham1 has joined #openstack-meeting-419:56
*** sacharya_ has joined #openstack-meeting-419:56
*** portdirect has joined #openstack-meeting-419:57
*** david-lyle has quit IRC19:57
*** fengxia41103 has joined #openstack-meeting-419:57
*** Dmitrii-Sh_ has joined #openstack-meeting-419:57
*** sacharya has quit IRC19:57
*** yifei_ has joined #openstack-meeting-419:58
*** rwallner has joined #openstack-meeting-419:58
*** spzala has joined #openstack-meeting-419:59
*** spzala has quit IRC19:59
*** chigang has joined #openstack-meeting-419:59
*** tdurakov has joined #openstack-meeting-419:59
*** akwasnie has joined #openstack-meeting-420:00
*** vdrok has joined #openstack-meeting-420:00
*** jovon has joined #openstack-meeting-420:01
*** ildikov_ has joined #openstack-meeting-420:01
*** ildikov_ is now known as ildikov20:01
*** RaginBajin_ has joined #openstack-meeting-420:02
*** aimeeu has joined #openstack-meeting-420:03
*** nikhil has joined #openstack-meeting-420:03
*** TheJulia has joined #openstack-meeting-420:05
*** patrickeast has joined #openstack-meeting-420:05
*** johnsom has joined #openstack-meeting-420:06
*** izaakk has joined #openstack-meeting-420:07
*** vishnoianil has joined #openstack-meeting-420:08
*** wolsen has joined #openstack-meeting-420:08
*** cargonza has joined #openstack-meeting-420:10
*** macsz has joined #openstack-meeting-420:11
*** raddaoui has joined #openstack-meeting-420:11
*** amit213 has joined #openstack-meeting-420:11
*** salv-orlando has joined #openstack-meeting-420:11
*** ediardo has joined #openstack-meeting-420:12
*** igormarnat_ has joined #openstack-meeting-420:13
*** zeestrat has joined #openstack-meeting-420:14
*** janonymous has joined #openstack-meeting-420:14
*** dasanind has joined #openstack-meeting-420:14
*** csatari has joined #openstack-meeting-420:15
*** david-lyle has joined #openstack-meeting-420:15
*** berendt has joined #openstack-meeting-420:15
*** fengxia41103 has quit IRC20:16
*** rfolco has quit IRC20:16
*** asingh_ has joined #openstack-meeting-420:16
*** sindhu has joined #openstack-meeting-420:16
*** gmann has joined #openstack-meeting-420:16
*** turvey has joined #openstack-meeting-420:18
*** hogepodge has joined #openstack-meeting-420:19
*** david-lyle has quit IRC20:20
*** spzala has joined #openstack-meeting-420:21
*** spzala has quit IRC20:21
*** mfedosin has quit IRC20:25
*** padkrish has quit IRC20:27
*** krtaylor has joined #openstack-meeting-420:28
*** matrohon has joined #openstack-meeting-420:28
*** padkrish has joined #openstack-meeting-420:38
*** pcaruana has quit IRC20:43
*** hemanthm|lunch is now known as hemanthm20:47
*** penfold has quit IRC20:48
*** padkrish has quit IRC20:52
*** Dmitrii-Sh has quit IRC20:53
*** sdake has joined #openstack-meeting-420:54
*** salv-orlando has quit IRC20:56
*** sdake_ has quit IRC20:58
*** rbak has quit IRC20:58
*** rbak has joined #openstack-meeting-420:58
*** sp_ has quit IRC21:01
*** padkrish has joined #openstack-meeting-421:03
*** sacharya_ has quit IRC21:05
*** sacharya has joined #openstack-meeting-421:06
*** rwallner has quit IRC21:12
*** rwallner has joined #openstack-meeting-421:13
*** rwallner has quit IRC21:13
*** rwallner has joined #openstack-meeting-421:14
*** rwallner has quit IRC21:14
*** julim has quit IRC21:15
*** pmesserli has quit IRC21:18
*** pmesserli has joined #openstack-meeting-421:18
*** matrohon has quit IRC21:22
*** rwallner has joined #openstack-meeting-421:22
*** pmesserli has quit IRC21:23
*** dave-mccowan has quit IRC21:26
*** rwallner has quit IRC21:27
*** sacharya_ has joined #openstack-meeting-421:29
*** MeganR has quit IRC21:29
*** sacharya has quit IRC21:29
*** Jeffrey4l has quit IRC21:34
*** Jeffrey4l has joined #openstack-meeting-421:34
*** penfold has joined #openstack-meeting-421:38
*** salv-orlando has joined #openstack-meeting-421:40
*** marst has quit IRC21:41
*** padkrish has quit IRC21:43
*** marst has joined #openstack-meeting-421:45
*** dave-mccowan has joined #openstack-meeting-421:45
*** dtardivel has quit IRC21:50
*** thorst_ has quit IRC21:53
*** thorst_ has joined #openstack-meeting-421:53
*** cleong has quit IRC21:55
*** thorst_ has quit IRC21:58
*** rfolco has joined #openstack-meeting-421:58
*** rfolco has quit IRC21:58
*** sdake has quit IRC22:02
*** sdake has joined #openstack-meeting-422:02
*** woodard_ has joined #openstack-meeting-422:06
*** woodard has quit IRC22:09
*** yamamoto has joined #openstack-meeting-422:10
*** woodard_ has quit IRC22:11
*** jovon has quit IRC22:12
*** pmesserli has joined #openstack-meeting-422:16
*** mjturek has quit IRC22:22
*** dave-mccowan has quit IRC22:31
*** sdake_ has joined #openstack-meeting-422:32
*** caboucha has quit IRC22:32
*** baoli has quit IRC22:33
*** sdake has quit IRC22:36
*** padkrish has joined #openstack-meeting-422:42
*** rwallner has joined #openstack-meeting-422:49
*** inc0 has quit IRC22:52
*** rwallner has quit IRC22:53
*** Swami_ has joined #openstack-meeting-422:58
*** Swami has quit IRC23:01
*** Swami_ has quit IRC23:04
*** woodard has joined #openstack-meeting-423:08
*** admcleod_ has joined #openstack-meeting-423:18
*** admcleod has quit IRC23:20
*** iyamahat has quit IRC23:22
*** iyamahat has joined #openstack-meeting-423:22
*** yfauser_ has quit IRC23:25
*** krtaylor has quit IRC23:25
*** zhurong has joined #openstack-meeting-423:30
*** zhurong has quit IRC23:36
*** galstrom is now known as galstrom_zzz23:36
*** woodard has quit IRC23:40
*** pmesserli has quit IRC23:45
*** Swami has joined #openstack-meeting-423:46
*** marst has quit IRC23:46
*** sshnaidm is now known as sshnaidm|off23:48
*** klamath has quit IRC23:52
*** uck has joined #openstack-meeting-423:54
*** baoli has joined #openstack-meeting-423:55

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