Wednesday, 2017-04-05

*** bobh has quit IRC00:00
*** thorst has joined #openstack-meeting-400:02
*** rfolco has joined #openstack-meeting-400:03
*** rfolco has quit IRC00:03
*** ntpttr has quit IRC00:03
*** ntpttr has joined #openstack-meeting-400:05
*** uck has quit IRC00:06
*** thorst has quit IRC00:07
*** ntpttr has quit IRC00:09
*** ntpttr has joined #openstack-meeting-400:11
*** yfauser has joined #openstack-meeting-400:14
*** ntpttr has quit IRC00:18
*** ntpttr has joined #openstack-meeting-400:19
*** yfauser has quit IRC00:20
*** woodard has quit IRC00:22
*** woodard has joined #openstack-meeting-400:23
*** ntpttr has quit IRC00:23
*** ntpttr has joined #openstack-meeting-400:25
*** ntpttr has quit IRC00:29
*** ntpttr has joined #openstack-meeting-400:31
*** thorst has joined #openstack-meeting-400:34
*** ntpttr has quit IRC00:36
*** ntpttr has joined #openstack-meeting-400:37
*** thorst has quit IRC00:38
*** foxpup has quit IRC00:38
*** ntpttr has quit IRC00:42
*** Julien-zte has joined #openstack-meeting-400:42
*** hongbin has quit IRC00:43
*** ntpttr has joined #openstack-meeting-400:43
*** zhurong has joined #openstack-meeting-400:45
*** ntpttr has quit IRC00:47
*** tovin07_ has joined #openstack-meeting-400:49
*** ntpttr has joined #openstack-meeting-400:49
*** yifei has joined #openstack-meeting-400:51
*** limao has joined #openstack-meeting-400:53
*** ntpttr has quit IRC00:54
*** ntpttr has joined #openstack-meeting-400:55
*** cathrich_ has joined #openstack-meeting-401:00
*** SerenaFeng has joined #openstack-meeting-401:01
*** ntpttr has quit IRC01:04
*** yifei has quit IRC01:04
*** yifei has joined #openstack-meeting-401:04
*** ntpttr has joined #openstack-meeting-401:05
*** ntpttr has quit IRC01:12
*** ntpttr has joined #openstack-meeting-401:13
*** yfauser has joined #openstack-meeting-401:15
*** ntpttr has quit IRC01:17
*** ntpttr has joined #openstack-meeting-401:19
*** reedip has quit IRC01:20
*** yfauser has quit IRC01:20
*** ntpttr has quit IRC01:23
*** ntpttr has joined #openstack-meeting-401:25
*** ntpttr has quit IRC01:30
*** yfauser has joined #openstack-meeting-401:30
*** amotoki has joined #openstack-meeting-401:31
*** ntpttr has joined #openstack-meeting-401:31
*** yfauser has quit IRC01:35
*** ntpttr has quit IRC01:36
*** ntpttr has joined #openstack-meeting-401:37
*** lyan has joined #openstack-meeting-401:38
*** thorst has joined #openstack-meeting-401:38
*** ntpttr has quit IRC01:42
*** thorst has quit IRC01:43
*** ntpttr has joined #openstack-meeting-401:43
*** s3wong has quit IRC01:44
*** baoli has joined #openstack-meeting-401:44
*** baoli has quit IRC01:45
*** baoli has joined #openstack-meeting-401:46
*** ntpttr has quit IRC01:47
*** ntpttr has joined #openstack-meeting-401:49
*** zhurong has quit IRC01:52
*** ntpttr has quit IRC01:56
*** ntpttr has joined #openstack-meeting-401:57
*** zhurong has joined #openstack-meeting-401:58
*** unicell has quit IRC02:03
*** ntpttr has quit IRC02:04
*** ntpttr has joined #openstack-meeting-402:05
*** erikmwil_ has joined #openstack-meeting-402:12
*** erikmwilson has quit IRC02:12
*** ntpttr has quit IRC02:12
*** ntpttr has joined #openstack-meeting-402:13
*** Sukhdev has quit IRC02:14
*** bobh has joined #openstack-meeting-402:14
*** vikasc has quit IRC02:16
*** ntpttr has quit IRC02:17
*** ntpttr has joined #openstack-meeting-402:19
*** jamemcc has quit IRC02:20
*** bobh has quit IRC02:20
*** jamemcc has joined #openstack-meeting-402:21
*** ntpttr has quit IRC02:23
*** ntpttr has joined #openstack-meeting-402:25
*** gongysh has joined #openstack-meeting-402:27
*** chigang has joined #openstack-meeting-402:29
*** adisky_ has quit IRC02:29
*** yfauser has joined #openstack-meeting-402:31
*** ntpttr has quit IRC02:32
*** vikasc has joined #openstack-meeting-402:33
*** ntpttr has joined #openstack-meeting-402:33
*** yfauser has quit IRC02:36
*** ntpttr has quit IRC02:38
*** zhurong has quit IRC02:38
*** mrunge_ has quit IRC02:39
*** ntpttr has joined #openstack-meeting-402:39
*** thorst has joined #openstack-meeting-402:40
*** mrunge_ has joined #openstack-meeting-402:41
*** ntpttr has quit IRC02:44
*** reedip has joined #openstack-meeting-402:44
*** ntpttr has joined #openstack-meeting-402:45
*** bobh has joined #openstack-meeting-402:46
*** ntpttr has quit IRC02:50
*** ntpttr has joined #openstack-meeting-402:51
*** thorst has quit IRC02:58
*** xiaohhui has joined #openstack-meeting-403:00
*** ntpttr has quit IRC03:01
*** ntpttr has joined #openstack-meeting-403:03
*** chandanc_ has joined #openstack-meeting-403:03
*** lyan has quit IRC03:04
*** ntpttr has quit IRC03:08
*** ntpttr has joined #openstack-meeting-403:09
*** bobh has quit IRC03:10
*** hongbin has joined #openstack-meeting-403:10
*** zhurong has joined #openstack-meeting-403:12
*** Kevin_Zheng has quit IRC03:13
*** chandanc_ has quit IRC03:14
*** links has joined #openstack-meeting-403:16
*** ntpttr has quit IRC03:18
*** ntpttr has joined #openstack-meeting-403:19
*** ntpttr has quit IRC03:24
*** ntpttr has joined #openstack-meeting-403:25
*** ntpttr has quit IRC03:30
*** ntpttr has joined #openstack-meeting-403:31
*** yfauser has joined #openstack-meeting-403:32
*** baoli has quit IRC03:35
*** baoli has joined #openstack-meeting-403:35
*** yfauser has quit IRC03:37
*** Sukhdev has joined #openstack-meeting-403:38
*** ntpttr has quit IRC03:38
*** ntpttr has joined #openstack-meeting-403:39
*** gongysh has quit IRC03:46
*** yfauser has joined #openstack-meeting-403:48
*** ntpttr has quit IRC03:52
*** yfauser has quit IRC03:52
*** ntpttr has joined #openstack-meeting-403:53
*** trinaths has joined #openstack-meeting-403:53
*** baoli has quit IRC03:58
*** ntpttr has quit IRC04:00
*** ntpttr has joined #openstack-meeting-404:01
*** dave-mccowan has quit IRC04:05
*** ntpttr has quit IRC04:06
*** ntpttr has joined #openstack-meeting-404:07
*** limao has quit IRC04:07
*** limao has joined #openstack-meeting-404:08
*** hongbin has quit IRC04:08
*** vks1 has joined #openstack-meeting-404:09
*** tinwood has quit IRC04:10
*** tinwood has joined #openstack-meeting-404:11
*** ntpttr has quit IRC04:11
*** amotoki has quit IRC04:12
*** limao has quit IRC04:12
*** zhurong has quit IRC04:12
*** ntpttr has joined #openstack-meeting-404:13
*** dharinic has quit IRC04:14
*** ntpttr has quit IRC04:18
*** marst has joined #openstack-meeting-404:18
*** ntpttr has joined #openstack-meeting-404:19
*** ntpttr has quit IRC04:23
*** ntpttr has joined #openstack-meeting-404:25
*** SerenaFeng has quit IRC04:27
*** iyamahat has joined #openstack-meeting-404:29
*** ntpttr has quit IRC04:29
*** amotoki has joined #openstack-meeting-404:30
*** ntpttr has joined #openstack-meeting-404:31
*** unicell has joined #openstack-meeting-404:32
*** zhurong has joined #openstack-meeting-404:35
*** ntpttr has quit IRC04:36
*** ntpttr has joined #openstack-meeting-404:37
*** dharinic has joined #openstack-meeting-404:38
*** adisky_ has joined #openstack-meeting-404:39
*** psachin has joined #openstack-meeting-404:39
*** dharinic has quit IRC04:41
*** dharinic has joined #openstack-meeting-404:42
*** ntpttr has quit IRC04:42
*** ntpttr has joined #openstack-meeting-404:43
*** ntpttr has quit IRC04:48
*** amotoki has quit IRC04:48
*** yfauser has joined #openstack-meeting-404:48
*** dharinic has quit IRC04:49
*** ntpttr has joined #openstack-meeting-404:49
*** amotoki has joined #openstack-meeting-404:53
*** yfauser has quit IRC04:53
*** ntpttr has quit IRC04:54
*** thorst has joined #openstack-meeting-404:55
*** ntpttr has joined #openstack-meeting-404:55
*** limao has joined #openstack-meeting-404:56
*** ntpttr has quit IRC05:00
*** thorst has quit IRC05:00
*** ntpttr has joined #openstack-meeting-405:01
*** limao has quit IRC05:01
*** limao has joined #openstack-meeting-405:02
*** lamt has joined #openstack-meeting-405:03
*** ntpttr has quit IRC05:06
*** nkrinner_afk is now known as nkrinner05:07
*** ntpttr has joined #openstack-meeting-405:07
*** ntpttr has quit IRC05:12
*** ntpttr has joined #openstack-meeting-405:13
*** ntpttr has quit IRC05:17
*** amotoki has quit IRC05:19
*** ntpttr has joined #openstack-meeting-405:19
*** iyamahat has quit IRC05:20
*** tonyb_ is now known as tonyb05:25
*** yfauser has joined #openstack-meeting-405:26
*** gongysh has joined #openstack-meeting-405:27
*** ntpttr has quit IRC05:28
*** ntpttr has joined #openstack-meeting-405:29
*** amotoki has joined #openstack-meeting-405:32
*** ntpttr has quit IRC05:36
*** ntpttr has joined #openstack-meeting-405:37
*** anilvenkata has joined #openstack-meeting-405:39
*** lamt has quit IRC05:40
*** ntpttr has quit IRC05:42
*** ntpttr has joined #openstack-meeting-405:43
*** anilvenkata has quit IRC05:45
*** ntpttr has quit IRC05:48
*** janki has joined #openstack-meeting-405:48
*** SerenaFeng has joined #openstack-meeting-405:49
*** ntpttr has joined #openstack-meeting-405:49
*** thorst has joined #openstack-meeting-405:56
*** ntpttr has quit IRC05:56
*** anilvenkata has joined #openstack-meeting-405:56
*** ntpttr has joined #openstack-meeting-405:57
*** Sukhdev has quit IRC05:59
*** jchhatbar has joined #openstack-meeting-405:59
*** thorst has quit IRC06:01
*** ntpttr has quit IRC06:02
*** janki has quit IRC06:02
*** ntpttr has joined #openstack-meeting-406:03
*** jchhatbar is now known as janki06:06
*** aavraham has joined #openstack-meeting-406:08
*** pcaruana has joined #openstack-meeting-406:08
*** ntpttr has quit IRC06:10
*** iyamahat has joined #openstack-meeting-406:11
*** ntpttr has joined #openstack-meeting-406:11
*** ntpttr has quit IRC06:18
*** ntpttr has joined #openstack-meeting-406:19
*** numans_ has quit IRC06:23
*** ntpttr has quit IRC06:24
*** ntpttr has joined #openstack-meeting-406:25
*** numans has joined #openstack-meeting-406:28
*** ntpttr has quit IRC06:30
*** iyamahat has quit IRC06:30
*** ntpttr has joined #openstack-meeting-406:31
*** ntpttr has quit IRC06:36
*** ntpttr has joined #openstack-meeting-406:37
*** kzaitsev_ws has joined #openstack-meeting-406:38
*** ntpttr has quit IRC06:46
*** ntpttr has joined #openstack-meeting-406:47
*** ntpttr has quit IRC06:52
*** ntpttr has joined #openstack-meeting-406:53
*** thorst has joined #openstack-meeting-406:57
*** ntpttr has quit IRC06:58
*** ltomasbo|away is now known as ltomasbo06:58
*** ntpttr has joined #openstack-meeting-406:59
*** thorst has quit IRC07:01
*** ntpttr has quit IRC07:04
*** ntpttr has joined #openstack-meeting-407:06
*** ralonsoh has joined #openstack-meeting-407:12
*** alexchadin has joined #openstack-meeting-407:15
*** ntpttr has quit IRC07:16
*** matrohon has joined #openstack-meeting-407:16
*** ntpttr has joined #openstack-meeting-407:17
*** ntpttr has quit IRC07:24
*** ntpttr has joined #openstack-meeting-407:25
*** vikasc is now known as vikasc|lunch07:31
*** ntpttr has quit IRC07:34
*** ntpttr has joined #openstack-meeting-407:36
*** britthouser8 has joined #openstack-meeting-407:39
*** ntpttr has quit IRC07:40
*** ntpttr has joined #openstack-meeting-407:41
*** britthouser has quit IRC07:42
*** ntpttr has quit IRC07:46
*** matrohon has quit IRC07:47
*** marst has quit IRC07:47
*** ntpttr has joined #openstack-meeting-407:48
*** marst has joined #openstack-meeting-407:48
*** ntpttr has quit IRC07:54
*** ntpttr has joined #openstack-meeting-407:56
*** thorst has joined #openstack-meeting-407:57
*** ifat_afek has joined #openstack-meeting-407:58
*** annarez has joined #openstack-meeting-407:59
*** elisha_r has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage07:59
openstackMeeting started Wed Apr  5 07:59:30 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.07:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:59
*** openstack changes topic to " (Meeting topic: vitrage)"07:59
openstackThe meeting name has been set to 'vitrage'07:59
elisha_rhio07:59
ifat_afekHi :-)07:59
annarezHi!07:59
*** trinaths has left #openstack-meeting-408:00
*** vikasc|lunch is now known as vikasc08:00
*** eyalb has joined #openstack-meeting-408:00
eyalb\0/08:00
*** dwj has joined #openstack-meeting-408:02
*** ntpttr has quit IRC08:02
*** idan_hefetz has joined #openstack-meeting-408:02
idan_hefetzHi!08:03
*** ntpttr has joined #openstack-meeting-408:04
*** usman has joined #openstack-meeting-408:04
ifat_afekToday’s agenda:08:05
ifat_afek•Status and Updates08:05
ifat_afek•Boston Summit08:05
ifat_afek•Open Discussion08:05
ifat_afek#topic Status and Updates08:06
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:06
ifat_afekMy update: I worked a little on the persistent database design. Checked OrientDB and ArangoDB. I tend to prefer OrientDB – it is more commonly used and has a wider set of features.08:06
ifat_afekWhile working on this, the question of how to support RCA history was raised again08:06
ifat_afekOne of the main goals of implementing a persistent graph DB was to support the RCA history, but it is not clear that this is the ideal implementation08:06
ifat_afekThere might be other ways to store and replay the history (e.g. as an event list).08:07
ifat_afekAt the moment I’m not sure that we will have the design ready by Pike-1 (the end of next week).08:07
ifat_afekWho else wants to update?08:08
*** danoffek has joined #openstack-meeting-408:08
danoffekHi Guys08:08
danoffekI'll update08:08
danoffekDidn't work on Vitrage ID for some time now.08:08
danoffekGot back to it, and after some merge conflict, and partially lost code (my vm died), I'm back to working on passing tempest tests08:09
danoffekOnce it's done, we have Vitrage ID.08:09
*** yujunz has joined #openstack-meeting-408:09
ifat_afekToo bad that you lost your code :-(08:09
danoffekYup, but at least we are back to working on it08:10
danoffekSo, most of the tempest failures are currently due to the cluster node08:10
ifat_afekWhat do you mean?08:10
*** ntpttr has quit IRC08:10
*** alexey_weyl has joined #openstack-meeting-408:11
alexey_weylHello08:11
danoffekThe vertex ID / Vitrage ID are no longer fixed keys, instead, they are standard UUIDs. Almost all failed tempest tests (a few dozen) are using the previously hard coded cluster vitrage ID.08:11
danoffekFixing it08:11
alexey_weylHello Friends08:11
ifat_afekOk, thanks08:11
danoffekThat's it08:11
*** ntpttr has joined #openstack-meeting-408:12
ifat_afekCool. Who else wants to update ?08:12
dwjI'll update. I finished implementing the resource list API and posted to gerrit for review.08:12
*** arif-ali has quit IRC08:12
dwj#link https://review.openstack.org/#/c/451778/08:13
*** kzaitsev_ws has quit IRC08:13
ifat_afekGreat, I saw that08:13
ifat_afekYour blueprint was already approved, right? (I don’t remember)08:14
*** arif-ali has joined #openstack-meeting-408:14
dwjlet me check..08:15
ifat_afekFound it08:15
ifat_afek#link https://specs.openstack.org/openstack/vitrage-specs/specs/pike/resource-list-api.html08:15
dwjapproved08:15
ifat_afekGreat08:16
ifat_afekAny other update?08:16
*** arif-ali has quit IRC08:16
* yujunz still working on entity equivalence spec https://review.openstack.org/#/c/451216/08:16
*** ntpttr has quit IRC08:16
yujunzI wonder if I should start coding or wait for final agreement on the spec08:16
ifat_afekLooking08:16
*** arif-ali has joined #openstack-meeting-408:17
*** thorst has quit IRC08:17
*** ntpttr has joined #openstack-meeting-408:18
ifat_afekI’m fine with what you wrote08:18
idan_hefetzHi yujunz, i see you have new changes, but i havent looked yet, i will do so today08:18
ifat_afekidan_hefetz: you were the last one to respond08:19
yujunzOK, thanks. That's all from me08:19
ifat_afekThanks08:19
ifat_afek#topic Boston Summit08:19
*** openstack changes topic to "Boston Summit (Meeting topic: vitrage)"08:19
ifat_afekI submitted four suggestions for Vitrage forum sessions:08:19
ifat_afek#link http://forumtopics.openstack.org/08:19
ifat_afek(look for Vitrage)08:19
ifat_afekI don’t know when we will get the selection results.08:19
ifat_afekBesides that, I’m working on two presentations: the Vitrage Story and the Vitrage project updates.08:20
ifat_afekWe have had some progress with the Vitrage-collectd demo. Intel succeeded to install Vitrage and raise a collectd alarm08:20
ifat_afekNext eyalb and I plan to configure their environment so the alarm will be raised on the right core and be deduced to the vm08:21
ifat_afekThat’s it for me08:21
alexey_weylIs anyone here is coming to Boston?08:21
ifat_afekI am :-)08:22
ifat_afekI know that a few other team members plan to come08:23
ifat_afek#topic Open Discussion08:24
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:24
ifat_afekMost of Vitrage core developers will be on vacation next week (April 10-17), so I think we should cancel the next meeting on April 1208:24
*** ntpttr has quit IRC08:24
ifat_afekAny objection?08:24
ifat_afekOk, I’ll send a cancellation mail08:25
ifat_afekAnything else?08:25
*** ntpttr has joined #openstack-meeting-408:26
*** alexey_weyl has quit IRC08:26
ifat_afekGoodbye then :-)08:26
eyalbbye08:26
elisha_rbye08:26
*** elisha_r has quit IRC08:26
dwjbye08:26
yujunzbye08:26
annarezbye bye08:26
usmanbye08:26
ifat_afek#endmeeting08:26
*** openstack changes topic to " (Meeting topic: ironic_neutron)"08:26
openstackMeeting ended Wed Apr  5 08:26:47 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-04-05-07.59.html08:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-04-05-07.59.txt08:26
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-04-05-07.59.log.html08:26
*** annarez has left #openstack-meeting-408:27
*** ifat_afek has left #openstack-meeting-408:27
*** ntpttr has quit IRC08:30
*** alexchadin has quit IRC08:31
*** ntpttr has joined #openstack-meeting-408:32
*** kzaitsev_ws has joined #openstack-meeting-408:32
*** ntpttr has quit IRC08:38
*** SerenaFeng has quit IRC08:38
*** bogdando has joined #openstack-meeting-408:39
*** ntpttr has joined #openstack-meeting-408:39
*** neiljerram has joined #openstack-meeting-408:39
*** salmankhan has joined #openstack-meeting-408:41
*** reedip has quit IRC08:41
*** ntpttr has quit IRC08:43
*** ntpttr has joined #openstack-meeting-408:46
*** dwj has quit IRC08:46
*** alexchadin has joined #openstack-meeting-408:48
*** zenoway has joined #openstack-meeting-408:49
*** matrohon has joined #openstack-meeting-408:51
*** ntpttr has quit IRC08:52
*** ntpttr has joined #openstack-meeting-408:54
*** matrohon has quit IRC08:57
*** usman has quit IRC08:58
*** danoffek has left #openstack-meeting-409:00
*** ntpttr has quit IRC09:00
*** ntpttr has joined #openstack-meeting-409:02
*** ntpttr has quit IRC09:06
*** psachin has quit IRC09:07
*** ntpttr has joined #openstack-meeting-409:08
*** SerenaFeng has joined #openstack-meeting-409:08
*** sambetts|afk is now known as sambetts09:09
*** psachin has joined #openstack-meeting-409:11
*** thorst has joined #openstack-meeting-409:14
*** ntpttr has quit IRC09:14
*** ntpttr has joined #openstack-meeting-409:16
*** thorst has quit IRC09:18
*** aarefiev_afk is now known as aarefiev09:19
*** bcafarel has quit IRC09:19
*** neiljerram has quit IRC09:21
*** ntpttr has quit IRC09:22
*** neiljerram has joined #openstack-meeting-409:23
*** ntpttr has joined #openstack-meeting-409:23
*** yujunz has quit IRC09:24
*** limao has quit IRC09:25
*** limao has joined #openstack-meeting-409:26
*** bcafarel has joined #openstack-meeting-409:27
*** limao has quit IRC09:30
*** ntpttr has quit IRC09:31
*** ntpttr has joined #openstack-meeting-409:32
*** reedip has joined #openstack-meeting-409:34
*** ntpttr has quit IRC09:36
*** Julien-zte has quit IRC09:36
*** alexchadin has quit IRC09:38
*** ntpttr has joined #openstack-meeting-409:38
*** mchiappero has quit IRC09:42
*** ntpttr has quit IRC09:44
*** idan_hefetz has quit IRC09:45
*** ntpttr has joined #openstack-meeting-409:46
*** ntpttr has quit IRC09:50
*** ntpttr has joined #openstack-meeting-409:52
*** nkrinner has quit IRC09:56
*** ntpttr has quit IRC09:56
*** ntpttr has joined #openstack-meeting-409:56
*** ntpttr has quit IRC10:01
*** bogdando has quit IRC10:02
*** ntpttr has joined #openstack-meeting-410:04
*** tovin07_ has quit IRC10:04
*** SerenaFeng has quit IRC10:07
*** ntpttr has quit IRC10:10
*** ntpttr has joined #openstack-meeting-410:10
*** ntpttr has quit IRC10:17
*** ntpttr has joined #openstack-meeting-410:18
*** rfolco has joined #openstack-meeting-410:21
*** pcaruana|afk| has joined #openstack-meeting-410:21
*** ntpttr has quit IRC10:22
*** pcaruana|afk| has quit IRC10:23
*** pcaruana has quit IRC10:24
*** ntpttr has joined #openstack-meeting-410:24
*** pcaruana has joined #openstack-meeting-410:25
*** amotoki has quit IRC10:26
*** ntpttr has quit IRC10:28
*** ntpttr has joined #openstack-meeting-410:30
*** zhurong has quit IRC10:30
*** ntpttr has quit IRC10:34
*** ntpttr has joined #openstack-meeting-410:34
*** janki has quit IRC10:34
*** jchhatbar has joined #openstack-meeting-410:34
*** gongysh has quit IRC10:35
*** ntpttr has quit IRC10:38
*** pbourke has quit IRC10:39
*** ntpttr has joined #openstack-meeting-410:40
*** pbourke has joined #openstack-meeting-410:41
*** gongysh has joined #openstack-meeting-410:41
*** ntpttr has quit IRC10:50
*** ntpttr has joined #openstack-meeting-410:52
*** ntpttr has quit IRC10:56
*** ntpttr has joined #openstack-meeting-410:58
*** ntpttr has quit IRC11:02
*** ntpttr has joined #openstack-meeting-411:04
*** dave-mccowan has joined #openstack-meeting-411:06
*** alexchadin has joined #openstack-meeting-411:07
*** ntpttr has quit IRC11:10
*** ntpttr has joined #openstack-meeting-411:12
*** neiljerram has quit IRC11:13
*** Julien-zte has joined #openstack-meeting-411:13
*** jchhatbar_ has joined #openstack-meeting-411:14
*** neiljerram has joined #openstack-meeting-411:15
*** thorst has joined #openstack-meeting-411:15
*** jchhatbar_ is now known as janki11:15
*** jchhatbar has quit IRC11:17
*** eyalb has quit IRC11:18
*** thorst has quit IRC11:19
*** dixiaoli has joined #openstack-meeting-411:27
*** dixiaoli has quit IRC11:27
*** ntpttr has quit IRC11:27
*** dixiaoli has joined #openstack-meeting-411:27
*** dixiaoli has quit IRC11:28
*** ntpttr has joined #openstack-meeting-411:28
*** ntpttr has quit IRC11:32
*** ntpttr has joined #openstack-meeting-411:34
*** rwallner has joined #openstack-meeting-411:35
*** rwallner has joined #openstack-meeting-411:35
*** rwallner has quit IRC11:35
*** rwallner has joined #openstack-meeting-411:36
*** gongysh has quit IRC11:37
*** amotoki has joined #openstack-meeting-411:38
*** ntpttr has quit IRC11:38
*** adisky_ has quit IRC11:39
*** ntpttr has joined #openstack-meeting-411:40
*** adisky_ has joined #openstack-meeting-411:40
*** gongysh has joined #openstack-meeting-411:41
*** thorst has joined #openstack-meeting-411:41
*** gongysh has quit IRC11:47
*** ntpttr has quit IRC11:48
*** ntpttr has joined #openstack-meeting-411:50
*** ntpttr has quit IRC11:54
*** ntpttr has joined #openstack-meeting-411:56
*** julim has quit IRC11:57
*** gongysh has joined #openstack-meeting-412:00
*** dtardivel has joined #openstack-meeting-412:02
*** gongysh has quit IRC12:05
*** klamath has joined #openstack-meeting-412:07
*** klamath has quit IRC12:07
*** klamath has joined #openstack-meeting-412:07
*** ntpttr has quit IRC12:08
*** ntpttr has joined #openstack-meeting-412:10
*** vks1 has quit IRC12:10
*** ntpttr has quit IRC12:14
*** ntpttr has joined #openstack-meeting-412:14
*** pshedimb_ has joined #openstack-meeting-412:20
*** revon has quit IRC12:23
*** ntpttr has quit IRC12:25
*** ntpttr has joined #openstack-meeting-412:26
*** woodard has quit IRC12:28
*** woodard has joined #openstack-meeting-412:29
*** aavraham has quit IRC12:30
*** anilvenkata has quit IRC12:31
*** aavraham has joined #openstack-meeting-412:31
*** ntpttr has quit IRC12:34
*** alexchadin has quit IRC12:36
*** ntpttr has joined #openstack-meeting-412:36
*** cathrich_ has quit IRC12:39
*** lamt has joined #openstack-meeting-412:40
*** ntpttr has quit IRC12:40
*** amotoki has quit IRC12:41
*** jichen has joined #openstack-meeting-412:41
*** ntpttr has joined #openstack-meeting-412:42
*** matrohon has joined #openstack-meeting-412:48
*** ntpttr has quit IRC12:48
*** bobmel_ has quit IRC12:49
*** rwallner has quit IRC12:50
*** ntpttr has joined #openstack-meeting-412:50
*** rwallner has joined #openstack-meeting-412:50
*** psachin has quit IRC12:52
*** markvoelker has joined #openstack-meeting-412:55
*** lyan has joined #openstack-meeting-412:55
*** amotoki has joined #openstack-meeting-412:56
*** mriedem has joined #openstack-meeting-412:59
gmann#startmeeting nova api13:00
openstackMeeting started Wed Apr  5 13:00:29 2017 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
gmannHi, who all here today13:00
johnthetubaguyo/13:01
mriedemo/13:01
gmannlet's wait for a min to have sdague and more people in case13:01
gmannlet's start13:02
jicheno/13:02
gmann#topic priorities13:03
*** openstack changes topic to "priorities (Meeting topic: nova api)"13:03
gmannpolicy spec #link https://review.openstack.org/433037 https://review.openstack.org/42787213:03
gmannjohnthetubaguy: your turn13:03
johnthetubaguyreally, its just a please review13:03
johnthetubaguynot a lot of updates13:04
*** julim has joined #openstack-meeting-413:04
johnthetubaguythere is discussion in keystone about the middleware alternative13:04
johnthetubaguythe first one doesn't really conflict with that13:04
*** psachin has joined #openstack-meeting-413:05
johnthetubaguythe second one kinda fights it, depending on how you look at it13:05
gmannscope check one?13:05
*** ntpttr has quit IRC13:05
johnthetubaguyyeah, scope check one is fine13:05
*** haleyb has joined #openstack-meeting-413:05
johnthetubaguythe second one is the additional roles13:05
*** ntpttr has joined #openstack-meeting-413:06
johnthetubaguyanyone got questions on those?13:06
gmanndoes keystone have anything up, spec etc for midleware alternative ?13:06
johnthetubaguyyeah, I can find the link, one sec13:06
johnthetubaguy#link https://review.openstack.org/#/c/452198/13:07
gmannjohnthetubaguy: thanks13:07
johnthetubaguyI am probably the most vocal hater of the current middlewear plan, mostly because it seems to create a heap of issues for operators we just spend time fixing13:08
*** links has quit IRC13:08
johnthetubaguymriedem: do you have the bandthwidth to talk a look at that policy spec again?13:09
mriedemjohnthetubaguy: maybe the first one13:09
johnthetubaguyyeah, the scope one is the important one13:09
johnthetubaguylargely the bit I would like to get folks started on is the improved functional tests13:10
gmannyea those will be nice.13:11
johnthetubaguyI guess its time to move on13:11
gmannpolicy docs are in nice shape and good progress  #link https://review.openstack.org/#/q/project:openstack/nova+branch:master+topic:bp/policy-docs13:12
gmanni think those are almost done with what we have up right now13:12
johnthetubaguyyeah, its looking really close13:12
johnthetubaguy#link https://docs.openstack.org/developer/nova/sample_policy.html13:13
gmannsecurity one was really mess with deprecated APIs and other server one with single policy13:13
gmann#link https://review.openstack.org/#/c/452309/13:13
johnthetubaguymriedem: if I create a specless BP to remove the discoverable rules, would you approved that?13:13
mriedemcontext?13:14
gmannjohnthetubaguy: can you check if my suggestion looks fine or any better way to describe those13:14
mriedemis that just b/c now that extensions are gone,13:14
mriedemdiscoverability doesn't matter?13:14
johnthetubaguymriedem: yeah, sorry, see the sample policy and search for "discoverable"13:14
johnthetubaguyright13:14
johnthetubaguyused to hide extensions existing, but you can't turn any off any more13:14
gmannyea "discoverable" are just used in extension_info right now13:15
mriedemwe don't actually check the policy rule for that anywhere?13:15
johnthetubaguybasically hard code everything to be visiable, and remove the policy13:15
johnthetubaguymriedem: I thought we did13:15
*** ntpttr has quit IRC13:16
gmannmriedem: johnthetubaguy only in exntension_info while showing list of extensions which are not for any use i think13:16
* sdague sneaks in late13:17
johnthetubaguymriedem: you might be right, I can't see them being used anywhere any more13:17
gmann#link https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/extension_info.py#L22513:17
mriedemif context.can(action, fatal=False):13:17
mriedemyeah same thing gmann linked13:17
mriedemthat's where it's checked13:17
johnthetubaguyyeah, just found that too13:18
*** ntpttr has joined #openstack-meeting-413:18
johnthetubaguyseems fine to just return true there13:18
gmannyea13:18
*** limao has joined #openstack-meeting-413:18
*** cathrichardson has joined #openstack-meeting-413:19
mriedemi guess we deprecated extensions at some point https://developer.openstack.org/api-ref/compute/#extensions-extensions-deprecated13:19
mriedemmaybe that was liberty?13:19
mriedemhttps://developer.openstack.org/api-guide/compute/extensions.html13:19
johnthetubaguypossibly13:19
sdagueliberty sounds about right13:20
mriedemso it looks like the only place discoverable is used is the GET /extensions APIs13:20
johnthetubaguyI think the config options got dropped a cycle or two ago13:20
johnthetubaguyyeah13:20
gmannyea13:20
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/remove-discoverable-policy-rules13:20
mriedemand since you can't whitelist/blacklist extensions, they should all be discoverable now?13:20
johnthetubaguyyeah13:20
mriedemok seems fair13:20
mriedemhttps://github.com/openstack/nova/commit/75280e582e6d607b38bc2af9f51f80fd5135453c13:21
mriedemhttps://github.com/openstack/nova/commit/04f8612aa99e618767a85d2f674ecdfc01955ff713:21
mriedemadded the wording13:21
*** limao_ has joined #openstack-meeting-413:21
mriedemso that was newton13:21
johnthetubaguyso I think we keep the API13:22
johnthetubaguyits just killing the policy related to it13:22
johnthetubaguyso its not a distraction from the other policy rules13:22
mriedemyeah13:22
*** mbruzek has joined #openstack-meeting-413:22
mriedemsdague: you fine with this?13:22
sdagueyeh13:22
mriedemthen let it be so13:23
johnthetubaguyits super interesting, if you got back a few cycles, the policy files was a monster (compute.api.py and two API code bases)13:23
johnthetubaguywe have got a long way forward here13:23
*** jchhatbar has joined #openstack-meeting-413:23
sdaguejohnthetubaguy: yeh, it's amazing how progress does happen :)13:23
*** psachin_ has joined #openstack-meeting-413:23
*** limao has quit IRC13:23
mriedembp is approved13:23
johnthetubaguymriedem: thanks13:24
gmanncool, thanks13:24
* gmann mriedem approved before adding Action iteam :)13:24
gmannanything else on priority items ?13:24
*** jchhatbar_ has joined #openstack-meeting-413:24
gmannlet's move then13:25
gmann#topic open13:25
*** openstack changes topic to "open (Meeting topic: nova api)"13:25
mriedemi've got something if no one elsedoes13:25
sdaguemriedem: go for it13:25
gmannapi extension removal  are in good review progress13:25
gmannmriedem: please go ahead13:26
mriedemi've got this spec for removing bdm device name from server create and volume attach POST requests https://review.openstack.org/#/c/452546/13:26
mriedemftersin pointed out in the ML and the spec review,13:26
mriedemabout the image bdm override use case on the server create13:26
*** psachin has quit IRC13:26
mriedemwhich i didn't know was a thing, but apparently ec2 api users care about it b/c people using aws do this a lot13:26
*** ntpttr has quit IRC13:26
mriedemi guess13:26
*** janki has quit IRC13:27
mriedemso,13:27
mriedemi've basically given up on trying to solve the server create part of this for pike,13:27
mriedembut i'm wondering if there is use in still removing device from the volume attach post request,13:27
mriedemsince that doesn't have the image bdm override thing13:27
mriedemfor volume attach, it's just a request parameter field we don't honor, at least not for libvirt13:27
mriedemi can't say for sure how the user-supplied device name works for hyperv, xen or vmware13:28
*** cleong has joined #openstack-meeting-413:28
*** ntpttr has joined #openstack-meeting-413:28
*** psachin_ has quit IRC13:28
*** jchhatbar has quit IRC13:28
mriedemfin13:28
sdaguemriedem: is there something about the wording of the API docs that might help here?13:28
* johnthetubaguy is pondering it13:28
mriedemsdague: in the api docs we say for that field that for libvirt it's not honored13:29
mriedemsince liberty13:29
mriedembut, for example, tempest still passes it in most tests13:29
mriedemhttps://developer.openstack.org/api-ref/compute/?expanded=attach-a-volume-to-an-instance-detail#attach-a-volume-to-an-instance13:29
mriedem"Name of the device such as, /dev/vdb. Omit or set this parameter to null for auto-assignment, if supported. If you specify this parameter, the device must not exist in the guest operating system. Note that as of the 12.0.0 Liberty release, the Nova libvirt driver no longer honors a user-supplied device name. This is the same behavior as if the device name parameter is not supplied on the request."13:29
sdaguemriedem: so, when it's used by EC2, what value is passed?13:30
mriedemthe same thing that the user supplies,13:30
mriedemthe thing about the image bdm override case,13:30
mriedemis that the device_name is used to match the user-supplied bdms in the server create request with any defined in the image metadata13:30
mriedembecause in our shitty data model, we use instance_uuid and device_name as a sort of unique constraint13:31
*** zenoway has quit IRC13:31
mriedemfor an update_or_create operation in the db api13:31
*** zenoway has joined #openstack-meeting-413:31
mriedemso as a hack, you can boot a server with an image that has bdm metadata, and override / customize the bfv experience with your own bdms in the request, iff they match the device names in the image meta13:31
mriedemwhich is a completely terrible ux13:31
mriedembut it's a thing people apparently do13:31
sdagueah, yeh, this bleeds out of the amazon api because it's xen bleed through I htink13:31
*** jchhatbar has joined #openstack-meeting-413:32
mriedemas far as i know, xen might be the only backend that honors the user-supplied device name13:32
sdagueyeh, that's my expectation13:32
*** psachin_ has joined #openstack-meeting-413:32
mriedemthere is that whole is_xen() check in the api code13:32
sdagueyou get a bunch of guest assistance because of xenbus13:33
johnthetubaguyyeah, the device name is defiantly xen specific there13:33
mriedemhttps://github.com/openstack/nova/blob/master/nova/compute/utils.py#L16613:33
johnthetubaguyalthough I am not sure the ordering is any more certain than with KVM, but I could be wrong13:33
sdagueyeh, I don't know, this seem like one of those hard problems to unwind because of the EC2 case13:33
mriedemright, so it seems like solving that ux problem,13:34
mriedemor replacing it,13:34
mriedemis going to require some new thinking on a new api design for that use case,13:34
mriedemand we don't even have a tempest test for this use case today as far as i know,13:34
sdagueyeh13:34
mriedemftersin said it was all regressed a long time ago and ndipanov fixed it13:34
mriedemso i was going to work on a tempest test for this in pike so we don't regress it13:34
*** ntpttr has quit IRC13:34
sdagueit would be helpful if the ec2 folks got more engaged early on in this13:34
mriedemi was thinking we could maybe long-term use the bdm tag as a correlation field for overrides,13:35
*** ostroverkhov has joined #openstack-meeting-413:35
sdagueyeh, the device tagging makes a bunch more sense to me13:35
mriedembut there are things we have to do before that, like actually put the bdm tag in the snapshot meta, and expose bdm tags out of the api13:35
gmannyea tempest has just passing in request (POST server ) #link https://github.com/openstack/tempest/blob/d44b295a168f067e7352895f4ce0ad32a3ec672d/tempest/scenario/test_volume_migrate_attached.py#L5913:35
*** jchhatbar_ has quit IRC13:35
*** janki has joined #openstack-meeting-413:35
mriedemso i'm scrapping the server create idea for pike13:36
*** ostroverkhov has left #openstack-meeting-413:36
mriedemwas wondering about volume attach,13:36
sdaguemriedem: honestly, I'm not super clear I understand the use case rally from the ec2 side. I feel like I'd need to see pictures to imagine all the things they are doing there13:36
mriedembut at this point it's just kind of a distraction and i'm happy to drop it13:36
*** ntpttr has joined #openstack-meeting-413:36
mriedemsdague: ftersin gives an example in the spec review13:36
mriedemhttps://review.openstack.org/#/c/452546/1/specs/pike/approved/remove-device-from-bdm-post-requests.rst@4413:36
mriedemit's not a picture, but a scenario13:36
mriedemso i'll work on a tempest test for it to see that it works and then we have a baseline in case we make changes later13:37
*** psachin_ has quit IRC13:37
*** jchhatbar has quit IRC13:38
sdagueok13:38
sdaguewhile on the topic of BDMs13:39
sdaguehttps://review.openstack.org/#/c/408151/ - is the RAID bdm one13:39
sdaguewhich I really don't want us to do13:39
mriedemi had already -1ed that earlier13:39
mriedemfor the same thing13:39
mriedemraid config is not going to belong in bdms13:39
mriedemjust b/c they are convenient13:39
mriedemimo13:39
sdaguebut, it would be nice to figure out what the actual use case and path forward is for ironic13:40
sdaguemriedem: you want to -2 it then?13:40
*** zenoway has quit IRC13:40
*** ntpttr has quit IRC13:40
mriedemi'd have to go back and read the latest comments first13:40
mriedemi don't want to offend anyone here with a -213:40
*** aavraham has quit IRC13:40
mriedemsince it's roman and ironic people13:40
*** aavraham has joined #openstack-meeting-413:41
mriedemthe easy thing to do is userdata13:41
mriedembut you don't get api validation on that13:41
sdagueyou can't do userdata I don't think13:42
*** ntpttr has joined #openstack-meeting-413:42
sdaguebecause it happens too late13:42
sdagueI think that part of it is also a mismatch between the fact that ironic as a project does let vendor specific stuff directly through to drivers, and we try hard not to do that13:43
mriedemwell that and baremetal is a weird bolt on to nova13:44
sdaguewell, sort of13:44
mriedemi'm referring to resource tracking and scheduling13:44
*** bobmel has joined #openstack-meeting-413:44
mriedemweirdness13:44
sdaguesure13:44
mriedemour api is more biased to xen than bm13:44
sdagueany time you get an abstraction, you are going to lose fidelity13:44
*** aavraham has joined #openstack-meeting-413:44
*** lamt has quit IRC13:45
mriedemi'd have to read this again, but there is also a proposed forum session for raid config13:45
mriedemhttp://forumtopics.openstack.org/cfp/details/1613:45
*** bobmel_ has joined #openstack-meeting-413:46
sdagueah, yeh, that's the HPC folks13:46
sdaguehonestly, that seems like the right conversation location13:46
*** jchhatbar has joined #openstack-meeting-413:46
sdagueI would -2 it until that forum session13:46
mriedemfwiw this is pretty much the reason for the mogan project, for a nova derivative whose API is completely biased toward baremetal use cases13:46
mriedembut that gets everyone riled up13:47
*** jchhatbar_ has joined #openstack-meeting-413:47
mriedemok i noted in the spec13:48
mriedemthat defers this out past pike13:48
*** acabot has joined #openstack-meeting-413:48
*** baoli has joined #openstack-meeting-413:48
mriedemso i've got another thing if we're done with raid13:48
sdagueyeh13:48
mriedemok,13:49
mriedemso in newton i was proposing to deprecate os-interface b/c it's a proxy to neutron to list/show ports,13:49
*** psachin_ has joined #openstack-meeting-413:49
*** bobmel has quit IRC13:49
mriedemand we want to expose vif tags which are stored in the nova virtual_interfaces table, which was historically nova-net only13:49
*** adisky_ has quit IRC13:49
mriedembut with vif tags we use that table for ports too13:49
mriedemso we have this weird case where os-virtual-interfaces is nova-net only, and os-interface is neutron only13:49
*** janki has quit IRC13:49
*** ntpttr has quit IRC13:50
mriedemi think what we want to do is deprecate os-virtual-interface,13:50
mriedembecause it's nova-net only13:50
sdagueyeh13:50
mriedemand as johnthetubaguy pointed out in that deprecation spec of mine,13:50
*** zenoway has joined #openstack-meeting-413:50
mriedemmove the GET from os-virtual-interfaces to os-interface13:50
mriedemand in os-interface, return vif tags (eventually)13:50
*** alexchadin has joined #openstack-meeting-413:51
*** jchhatbar has quit IRC13:51
mriedemnow since we don't have virtual_interfaces in the database for any ports created before newton,13:51
mriedemwe have two options for listing/showing ports in os-interface,13:51
mriedem1. proxy to neutron if the port isn't in the virtual_interfaces table,13:51
mriedem2. use the info_cache, but that's per-instance13:51
* johnthetubaguy shakes head at the amount of work we created for ourselves in merging half baked and competing APIs13:51
mriedemso i'm not sure that works13:51
mriedemjohnthetubaguy: yeah i feel like most of my blueprints lately are about removing code13:52
mriedem:)13:52
*** ntpttr has joined #openstack-meeting-413:52
sdaguemriedem: deleting is always good13:52
mriedemoh wait,13:52
mriedem#2 might not be bad13:52
mriedemso os-virtual-interfaces is only a server extension13:53
mriedemso we have the server_id13:53
johnthetubaguymriedem: sdague: our love of removing code always seems to remind me of this: https://www.youtube.com/watch?v=F9nGyPz9uT013:53
mriedemso in that case, we can get the instance.info_cache and list/show ports from that i think13:53
johnthetubaguy(warning contains british humour, yes spelt like that ^)13:53
johnthetubaguyfor the record we have some tidying up of the info_cache13:54
johnthetubaguysome of it syncs from neutron, some of it only we know13:54
mriedemthis also reminds me,13:54
gmanncan we return vif tags with device or server tag as consolidated tags on server resources and deprecate os-interface ?13:54
mriedemGET /servers/server_id/port_id in os-interface doesn't actually use the server,13:54
mriedemit just goes directly to neutron for the port13:54
mriedemgmann: we can't deprecate os-interface because of the POST and DELETE operatoins13:54
*** zenoway has quit IRC13:55
mriedemto add/remove ports to a server13:55
sdaguemriedem: interesting....13:55
*** tonytan4ever has joined #openstack-meeting-413:55
sdaguedoes neutron every know anything about our server ids? or is it kept unawares?13:55
mriedemsdague: the port.device_id is the owning server13:55
mriedemit's the instance uuid13:55
gmannmriedem: ah yea13:55
mriedemi should step back,13:55
*** cathrichardson has left #openstack-meeting-413:56
mriedemmy long-term goal is to expose bdm tags and vif tags out of the api13:56
mriedemthe bdm tags one is easy, we have os-volume_attachments13:56
mriedemi'm stuck on this vif tag one b/c we have these two competing apis and data models13:56
*** ntpttr has quit IRC13:56
mriedemi *think* the way forward is deprecate os-virtual-interface, and use os-interface, but stop proxying to neutron in os-interface and use the info_cache13:56
*** ostroverkhov has joined #openstack-meeting-413:56
sdaguemriedem: that seems sensible to me13:57
johnthetubaguymriedem: oh yeah, os-volume_attachmens only lists volumes right?13:57
mriedemat some point we might want an action api somewhere to force a refresh of the info_cache13:57
mriedemjohnthetubaguy: yeah via bdms13:57
johnthetubaguyyeah13:57
*** chrisspencer has joined #openstack-meeting-413:57
mriedemi'm actually surprised we don't have a force info cache refresh api13:57
mriedemthat would seem useful13:57
mriedembut i digress13:57
mriedemand we have 2 minutes13:57
gmannor refresh everytime GET comes13:58
gmannyea 2 min left13:58
*** vkmc__ has joined #openstack-meeting-413:58
*** ntpttr has joined #openstack-meeting-413:58
mriedemgmann: but then we get back into that proxy thing13:58
mriedemi'm not sure if that's better than an on-demand forced refresh13:58
mriedemwe periodicaly heal the info cache on the computes anyway13:58
mriedembut yeah it might be a lossy api13:59
gmannyea13:59
*** vincentfrancois1 has joined #openstack-meeting-413:59
mriedemthe network API operations in the compute should also be refreshing the info cache if they change resources tied to an instance13:59
mriedemwe've seen bugs where that doesn't happen, like deleting a floating ip13:59
gmanni wonder user will use that or at least remember to use before getting tags etc13:59
mriedemanyway, i might just brain dump this to the ML first before working o na spec13:59
mriedemsince i'm a bit spec'ed out13:59
gmannanyways 1 min left,13:59
gmannyea14:00
*** licanwei has joined #openstack-meeting-414:00
mriedemwe're out of time14:00
gmannthanks everyone let's jump to nova channel14:00
gmann#endmeeting14:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"14:00
openstackMeeting ended Wed Apr  5 14:00:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-05-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-05-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-05-13.00.log.html14:00
alexchadin#startmeeting watcher14:00
openstackMeeting started Wed Apr  5 14:00:48 2017 UTC and is due to finish in 60 minutes.  The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
*** mriedem has left #openstack-meeting-414:00
*** SergeM has joined #openstack-meeting-414:01
alexchadinwelcome here!14:01
chrisspencero/14:01
vincentfrancois1o/14:01
dtardivelhi14:01
licanweihi14:01
sballe_o/14:01
ostroverkhovo/14:01
pshedimb_o/14:01
alexchadin#info Today's agenda is placed here https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#04.2F05.2F201714:01
alexchadin#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
alexchadinOur current milestone target is Pike-1 due April 10th14:01
acaboto/14:02
alexchadinso we have 5 BPs and 3 bugs for P-114:02
alexchadinI'm not sure that Noisy Neighbor Strategy and gnocchi support will be merged by release time14:03
alexchadinSo I propose to move them to the Pike-214:03
vincentfrancois1alexchadin: Support gnocchi in watcher i not well updated in laucnhpad14:04
vincentfrancois1alexchadin: it's actually well under way14:04
alexchadinpshedimb_ sballe_ what do you think about it?14:04
acabothttps://review.openstack.org/#/q/topic:bp/gnocchi-watcher14:04
alexchadinvincentfrancois1: ok, I've seen your comments14:04
acabotlooks ok for pike-1 no ?14:04
*** SergeM has quit IRC14:04
vincentfrancois1alexchadin: I reckon it can be merged on time14:04
vincentfrancois1acabot: +114:05
*** zenoway has joined #openstack-meeting-414:05
alexchadinyeap, vincentfrancois1 started to review couple of hours ago14:05
sballe_I will let pshedimb_ answer. We are very close. We could merge what we have and then if we see issues fix them as  bugs14:05
sballe_but pshedimb_ has the last word14:05
*** rwallner has quit IRC14:05
alexchadinostroverkhov: what about Versioned Notifications for service object?14:05
alexchadinsballe_: great!14:06
pshedimb_alexchadin, Yeah I can merge whatever I have. But my priority now is to prepare a demo for Boston summit on this.14:06
*** hongbin has joined #openstack-meeting-414:06
sballe_pshedimb_: +114:06
sballe_We want to make sure it works the way we want it do work and that is why we spend extra time testing the behavior and corner cases14:07
vincentfrancois1pshedimb_: push for review what you have so you can get feedbacks14:07
*** galstrom_zzz is now known as galstrom14:07
alexchadinsballe_: pshedimb_ let's make decision this Friday then14:07
pshedimb_So once I receive reviews on the spec and once the spec is approved, I will push in the code change.14:07
sballe_vincentfrancois1: make sense14:07
sballe_pshedimb_: +114:07
pshedimb_vincentfrancois1, You want me to push the code before spec review?14:08
alexchadinpshedimb_: code change will be appointed to P-214:08
alexchadinpshedimb_: push what you already have14:08
alexchadinpshedimb_: just mark it with [WiP] tag14:08
pshedimb_alexchadin, Okay, I'll do it in the next 1-2 days.14:08
pshedimb_Once I integrate with recent changes.14:09
vincentfrancois1alexchadin: +114:09
*** zenoway has quit IRC14:09
alexchadinmove on14:10
alexchadinOpen Discussions topic will be follow after Announcements every even weeks.14:10
ostroverkhovalexchadin: I read the messages, but there are a few questions14:10
alexchadinostroverkhov: ok, I will be in sync with you till the Friday14:11
ostroverkhovalexchadin: ok14:11
alexchadinI hope, nobody will mind about open discussions14:11
alexchadinThere are two hacking rooms for gathering on Summit. #link https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms14:12
alexchadinThey will be filled with roundtables for ad-hoc discussions that projects want to have.14:12
*** zenoway has joined #openstack-meeting-414:12
alexchadinHynes MR 108 and 10914:12
*** bobh has joined #openstack-meeting-414:13
sballe_nice! alexchadin can you add this to our Boston summit etherpad? I am loosing track of all the details14:13
alexchadinI will set time for us when we can gather14:13
*** ishafran has joined #openstack-meeting-414:13
alexchadinsballe_: sure14:13
alexchadin#topic Open Discussions14:14
*** openstack changes topic to "Open Discussions (Meeting topic: watcher)"14:14
alexchadinWe should be prepared for onboarding rooms, where new contributors can come and we may teach them about the project, code, and give them an opportunity to meet established community members.14:14
alexchadinwe will have 90 minutes to show newcomers demo of Watcher and teach them our features/show live demo for everyone14:15
vincentfrancois1alexchadin: what do you think we should prepare? slides?14:15
sballe_alexchadin: one more thing. Did you update the generic Watcher slides from last summit? I am working on my slide set and just used the Watcher main arch slides from last summit. We have new contributors from NEC, and other companies that I would like ot add to the contributor slide.14:16
alexchadinvincentfrancois1: I think we need OpenStack controller and 2 computes at least14:16
vincentfrancois1alexchadin: oh ok, then maybe we need to show multiple Watcher strategies in action14:16
sballe_vincentfrancois1: alexchadin good ideas14:16
alexchadinvincentfrancois1: totally agreed14:16
vincentfrancois1alexchadin: there's also a video on youtube we can use to explain how it works14:17
vincentfrancois1#link https://www.youtube.com/watch?v=FJttohkf0sM14:17
alexchadinsballe_: I haven't worked with slides yet, I will adapt them for Pike and hope to do it with you14:17
sballe_alexchadin: ok14:17
alexchadinvincentfrancois1: we can share video, but it isn't main reason to come for contributors, live demo would be great14:18
*** jichen has quit IRC14:18
vincentfrancois1alexchadin: yes but the animation is good to explain the concept14:19
alexchadinvincentfrancois1: I agree14:19
vincentfrancois1alexchadin: whereas live demos are to show the different use cases14:19
sballe_agreed but video is great if live demo doesn't work14:20
alexchadinvincentfrancois1: we need to place demo on wiki page14:20
vincentfrancois1alexchadin: and also to show it's no bullsh*t14:20
sballe_vincentfrancois1: +114:20
alexchadinI will add appropriate topic on etherpad14:21
alexchadinmove on14:21
alexchadinadisky_ said that rdo-package for python-watcherclient will be prepared by number80 (Haïkel Guémar). We still need to find the ways to prepare watcher package.14:21
alexchadin#link https://bugzilla.redhat.com/show_bug.cgi?id=135097414:22
openstackbugzilla.redhat.com bug 1350974 in Package Review "Openstack python-watcherclient" [Unspecified,Assigned] - Assigned to karlthered14:22
*** ishafran has quit IRC14:23
alexchadinwe still isn't in sync with packages for systems (except of python packages)14:23
alexchadinI will discuss it with adisky_14:23
*** rwallner has joined #openstack-meeting-414:23
alexchadin#action discuss packages issue with adisky_14:24
alexchadin#topic Review Action Items14:24
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:24
alexchadinWatcher specs14:24
alexchadinNoisy Neighbor Strategy has got algorithm description and now is ready to be reviewed #link https://review.openstack.org/#/c/398162/14:24
alexchadinwho would like to take full review here?14:25
alexchadinI may take it since I worked with strategies before14:26
sballe_alexchadin: +1  thx14:26
chrisspencer+114:26
licanwei+114:26
alexchadin#action alexchadin chrisspencer licanwei review https://review.openstack.org/#/c/398162/14:26
alexchadinDefine grammar for workload characterization Chris is waiting for Antoine's answer #link https://review.openstack.org/#/c/377100/14:27
alexchadinseems chrisspencer has got it ;)14:27
acabotdone14:28
alexchadinthank you, acabot14:28
chrisspencerthank acabot14:28
alexchadinBTW, help is appreciated here14:28
alexchadinsballe_: will you take a look?14:29
sballe_sure14:29
alexchadin#action sballe_ review https://review.openstack.org/#/c/377100/14:30
alexchadinSpec for noisy-neighbor-dashboard needs new answers and probable PS #link https://review.openstack.org/#/c/427308/14:30
alexchadinprobably*14:31
pshedimb_+114:31
alexchadin#action pshedimb_ review https://review.openstack.org/#/c/427308/14:31
alexchadinSupport workload fingerprinting needs new PS #link https://review.openstack.org/#/c/448396/14:32
alexchadinAudit tag in VM Metadata needs final core review #link https://review.openstack.org/#/c/391374/14:32
alexchadinhvprash: I like integrating with audit scope14:33
alexchadinI will review it, who else?14:33
alexchadindtardivel: thx for review14:33
acabot+114:33
vincentfrancois1alexchadin: put me in too14:33
*** trinaths has joined #openstack-meeting-414:33
alexchadin#action alexchadin acabot vincentfrancois1 review https://review.openstack.org/#/c/391374/14:34
alexchadinAdd spec for services-versioned-notifications-api bp needs new PS #link https://review.openstack.org/#/c/445817/14:34
*** erikmwilson has joined #openstack-meeting-414:34
*** zenoway has quit IRC14:34
alexchadinvincentfrancois1: I had conversation with ostroverkhov and we decided that we might need to put status checking into new background job14:35
*** zenoway has joined #openstack-meeting-414:35
alexchadinvincentfrancois1: it is useless to send notifications only when we request service status14:36
vincentfrancois1alexchadin: Ah I though it was already the case actually, that's why I was talking about polling in my comment14:36
vincentfrancois1alexchadin: so if there is no such job, then it doesn't make much sense indeed14:37
*** erikmwil_ has quit IRC14:37
alexchadinvincentfrancois1: ok, seems there will be some changes14:37
alexchadin#action alexchadin ostroverkhov work on https://review.openstack.org/#/c/445817/14:38
alexchadinmove on14:38
alexchadinSupport visualizing workload fingerprints needs reviews #link https://review.openstack.org/#/c/448394/14:38
dtardivel+114:39
alexchadin#action dtardivel review https://review.openstack.org/#/c/448394/14:39
alexchadinAdd spec for Cinder model integration needs reviews #link https://review.openstack.org/#/c/450173/14:39
alexchadinvincentfrancois1 already put some comments, who else would like to take a look?14:40
acabotalexchadin : I already looked at it and I have the same comments as vincentfancois114:41
alexchadinI think we will discuss some details from this spec on Summit14:42
alexchadinacabot: thx14:42
vincentfrancois1alexchadin: sure14:42
alexchadinWatcher14:43
alexchadinAdded Actuator Strategy still needs to be taken by someone. Can Vladimir take it?14:43
alexchadin#link https://review.openstack.org/#/c/425110/14:43
vincentfrancois1ostroverkhov: alexchadin: go ahead, it's up for grab14:43
alexchadinostroverkhov: I think you can pick it up, what will you say?14:44
*** trinaths has left #openstack-meeting-414:44
*** zenoway has quit IRC14:44
ostroverkhovalexchadin: ok, i will pick it up14:44
vincentfrancois1alexchadin: just one general remark: the multinode gate is always failing for a month now, we need to fix it14:45
alexchadin#action ostroverkhov take https://review.openstack.org/#/c/425110/ to end it up14:45
*** galstrom is now known as galstrom_zzz14:45
alexchadinvincentfrancois1: let's discuss it on main channel14:45
vincentfrancois1alexchadin: np14:45
alexchadinvincentfrancois1: just remind me sometime14:46
alexchadinAdded suspended audit state needs reviews. Have some tested it yet? #link https://review.openstack.org/#/c/438800/14:46
alexchadinlicanwei: have you tested it in Devstack for example?14:46
licanweiyes14:46
*** ntpttr__ has joined #openstack-meeting-414:46
alexchadinlicanwei: great! I will review it14:47
*** makowals has quit IRC14:47
*** ntpttr__ has quit IRC14:47
alexchadin#action alexchadin review https://review.openstack.org/#/c/438800/14:47
*** marst has quit IRC14:48
*** ntpttr_laptop has joined #openstack-meeting-414:48
licanweiit works well14:48
alexchadinPrevent the migration of VM with 'optimize' False in VM metadata needs final core reviews #link https://review.openstack.org/#/c/443070/14:48
*** vks1 has joined #openstack-meeting-414:48
alexchadinvincentfrancois1: thx for review!14:48
*** Julien-zte has quit IRC14:49
vincentfrancois1alexchadin: you're welcome ;)14:49
alexchadin#action alexchadin review https://review.openstack.org/#/c/438800/14:49
alexchadingnocchi support topic should be reviewed #link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/gnocchi-watcher14:49
alexchadinchrisspencer, licanwei, dtardivel, pshedimb_ will you take it?14:50
licanwei+114:50
pshedimb_+114:50
chrisspencer+114:50
*** Julien-zte has joined #openstack-meeting-414:50
alexchadin#action licanwei pshedimb_ chrisspencer review patchsets of https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/gnocchi-watcher14:51
alexchadinAdded tempest test for workload_stabilization needs to be tested by someone else #link https://review.openstack.org/#/c/393355/14:51
alexchadinlooks like it is up to me14:52
alexchadinvincentfrancois1: I will contact you about it14:52
alexchadinAdd action description needs reviews #link https://review.openstack.org/#/c/450720/14:52
vincentfrancois1alexchadin: ok14:53
alexchadinvincentfrancois1 will you take this commit?14:53
alexchadinto review14:53
*** zenoway has joined #openstack-meeting-414:54
vincentfrancois1alexchadin: I can review  https://review.openstack.org/#/c/393355/14:54
alexchadinvincentfrancois1: you've sent link to your patch ;)14:54
vincentfrancois1alexchadin: as for https://review.openstack.org/#/c/450720/ I'll do it if I have time14:54
vincentfrancois1alexchadin: but no promises :p14:54
*** vks1 has quit IRC14:55
*** ostroverkhov_ has joined #openstack-meeting-414:55
alexchadin#action vincentfrancois1 review https://review.openstack.org/#/c/450720/14:55
alexchadinAdd Watcher JobStore for background jobs needs reviews #link https://review.openstack.org/#/c/449659/14:55
*** ostroverkhov has quit IRC14:55
alexchadinthis PS will be updated soon14:56
alexchadinRun Watcher-API behind mod-wsgi needs new PS #link https://review.openstack.org/#/c/450740/14:56
vincentfrancois1alexchadin: made a quick review of that one14:56
alexchadinwho else will take it?14:56
*** marst has joined #openstack-meeting-414:57
alexchadin#action alexchadin review https://review.openstack.org/#/c/450740/14:57
alexchadinhidekazu proposed new BP today: https://blueprints.launchpad.net/watcher/+spec/zone-migration-strategy14:58
*** zenoway has quit IRC14:58
alexchadinIt isn't clear to me yet, we agreed to wait spec for it from hidekazu side14:59
*** shintaro has joined #openstack-meeting-414:59
*** talonx has joined #openstack-meeting-415:00
*** zenoway has joined #openstack-meeting-415:00
alexchadinwell, let's continue to prepare for Summit15:00
*** sergem has joined #openstack-meeting-415:00
alexchadinhave a nice day!15:00
sballe_bye15:00
pshedimb_bye :)15:00
alexchadinthank you for your attention15:00
alexchadinbye15:00
chrisspencerbye15:00
ostroverkhov_Bye15:00
licanweibye15:01
vincentfrancois1bye15:01
*** yingjun has joined #openstack-meeting-415:01
alexchadin#endmeeting15:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:01
openstackMeeting ended Wed Apr  5 15:01:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-04-05-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-04-05-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-04-05-14.00.log.html15:01
serverascode#startmeeting operators_telco_nfv15:01
openstackMeeting started Wed Apr  5 15:01:25 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
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
*** licanwei has quit IRC15:01
shintarohi15:01
*** ostroverkhov_ has quit IRC15:01
serverascode#topic roll call15:01
*** chrisspencer has left #openstack-meeting-415:01
*** openstack changes topic to "roll call (Meeting topic: operators_telco_nfv)"15:01
serverascodehi shintaro :)15:01
*** Julien-z_ has joined #openstack-meeting-415:01
*** Julien-zte has quit IRC15:01
shintaroo/15:01
serverascodewho else do we have?15:01
talonxHi, joining after a long time15:02
serverascodeI know adiren said he could not make it15:02
serverascodehi talonx :)15:02
uli-kHi, long time no see....15:02
talonxHi :)15:02
talonxBeen a lurker mostly15:02
shintaroI'm in the west coast so much easier to join :)15:02
serverascodehi uli-k :)15:02
sergemhello15:02
serverascodehi sergem :)15:02
serverascodeshintaro what are you up to on the west coast?15:03
shintaroOpenNetworkingSummit in Santa Clara15:03
serverascodeoh cool, I was hoping ot go to that but it didn't work out15:03
serverascodesergem have you been to one of these meetings before?15:03
*** alexchadin has quit IRC15:04
shintarovery inspiring15:04
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:04
sergemI'm serge from Sprint. Sometimes I lurk here.15:04
serverascode^^ that's the agenda if anyone wants to look or add to it, just one thing on it right now and that is some of the upcoming boston forum sessions15:04
sergemI do attend the f2f at openstack15:04
serverascoderight, I think I remember now :)15:05
serverascodeok so we have a few people, please take a second to look at the agenda and add it it, and we shall start at the start :)15:05
shintaroI was wondering how the sessions are selected...15:05
serverascode#topic boston forum sessions15:06
*** openstack changes topic to "boston forum sessions (Meeting topic: operators_telco_nfv)"15:06
serverascodeshintaro I'm not sure how they are selected15:06
*** dharinic has joined #openstack-meeting-415:06
serverascodeanyone know?15:06
serverascode#link http://forumtopics.openstack.org/15:06
serverascodeso to be clear those are submissions, not "accepted" sessions yet15:06
shintaroright15:06
serverascodeI took a look through and added links to a few I thought interesting to NFV15:07
*** ntpttr_laptop has quit IRC15:07
serverascodeprobably the most important is the collaboration session15:07
shintaroWhat I've heard is they are going to have 3 parallel sessions during the Summit15:07
serverascode#link http://forumtopics.openstack.org/cfp/details/6415:07
*** ntpttr_laptop has joined #openstack-meeting-415:07
serverascodethat shintaro wrote up15:07
shintaroyes, Ildiko from the Foundation will help us15:08
serverascode3 parallel, ok that is a good number15:08
sergemIs there something on containers?15:08
*** vks1 has joined #openstack-meeting-415:08
serverascodeyup a few15:08
serverascode"life cycle management..."15:08
serverascodeopenstack via kubernetes...15:09
serverascodemigration to containers...15:09
serverascodekubernetes ops on openstack15:09
serverascodeI think a few more15:09
sergemI couldn't open the link as I don't have ubuntu one login15:10
serverascodeoh really? interesting.15:10
shintarocontainer was a hot topic in the OpsMeetup, too15:10
jamemccHi - Sorry - I'm here now15:10
shintarohi jamemcc15:10
serverascodesergem do you have an "openstack" id?15:10
serverascodelike launchpad?15:10
serverascodeif so that is the same15:11
serverascodehi jamemcc15:11
sergemI see Bin has a topic on contained, microservices15:11
serverascodeah yes, ok iwll add that to our list15:11
serverascodejamemcc we are just looking over the potential forum submissions15:12
*** kzaitsev_ws has quit IRC15:12
jamemccThe containers topic is big for LCOO - I will end up creating a spreadsheet to show which all seem to be in that category - simethign similar to the Ethercalc I created a little earlier - which I put the link in the agenda and is https://ethercalc.openstack.org/=qqdo5sfmri15:13
shintarojamemcc do you know how the sessions are going to be selected?15:13
serverascode#link https://ethercalc.openstack.org/=qqdo5sfmri15:13
*** yfauser_ has joined #openstack-meeting-415:13
jamemccWhat I understand is it's a selection committee of 2 from User Group, 2 from TC and 2 from Foundation15:14
*** psachin_ has quit IRC15:14
jamemccThat was hearsay (twice)15:14
jamemccThen scheduled just liek the presenation topics15:14
*** woodard has quit IRC15:14
*** ntpttr has quit IRC15:15
jamemccI am thinking/hoping that if we can ourselvs be organizing the topics we are interested in and will participate and then give advice ont he order of them - that will help the schedulers a lot15:15
shintarook great. so we just wait and see15:15
jamemccThat was where I was thinking ahveing the List (either as you are doing Curtis) in the Agenda - or in the Ethercalc like I started15:16
jamemccwould be helpful15:16
*** ntpttr has joined #openstack-meeting-415:16
serverascodethe ethercalc looks great jamemcc15:16
serverascodeI think that is a really good idea to work with whoever is selecting the submissions and help out a bit15:17
*** yfauser has quit IRC15:17
serverascodeany other thoughts on the forum session?15:18
serverascodeif not I don't see any other items added except open discussion15:18
shintaroso we prioritise the list?15:18
*** wxy| has joined #openstack-meeting-415:18
shintaroor we announce our interest/intent to join on the list of sessions as a group?15:20
jamemccYeah - makes sense - maybe a +1 approach to get started.15:20
serverascodelooks like there are 124 submissions15:20
shintarowe can start with the list on ethercalc :)15:20
jamemccSome probbly dont' belong on the TelcoNFV WG (our) list15:21
*** lamt has joined #openstack-meeting-415:21
serverascodeyeah for sure, I was just thinking about how many could be accepted if 3 parallel sessions over 4 days... :)15:21
jamemccOne reason is if I saw Neutron I added ot to the list15:21
serverascodeout of curiosity what do you all think of the "blockchain in telelcom"?15:22
serverascodeI don't quite get that one15:22
*** egonzalez has joined #openstack-meeting-415:22
sergemisn't that pretty futuristic?15:22
shintaroI don't get it either15:23
*** ntpttr has quit IRC15:23
jamemccYes - pretty far out there15:23
serverascodeok, that's what I was thinking15:23
sergemthere are probably lots of diverse interest among us. In my company (Sprint), we are focused on VMs. So I am interested in all the container stuff15:23
sergemlike 'migration to containers' is a good one.15:24
*** jchhatbar_ has quit IRC15:24
*** ntpttr has joined #openstack-meeting-415:24
serverascodethat one seems to be about the openstack control plane15:25
serverascode#link http://forumtopics.openstack.org/cfp/details/9615:25
shintaroyes. you have to be careful if it is openstack on container, or container on Openstack15:25
serverascodeheh yeah15:25
*** ntpttr_laptop has quit IRC15:26
sergemAh yes.15:26
serverascodeI will add a comment to that one asking to differentiate15:26
*** zenoway has quit IRC15:26
serverascodeok, any other thoughs on the forum sessions?15:27
*** ntpttr has quit IRC15:28
serverascodeall right, I suppose we just check out the spreadsheet every once and a while and try to keep up with any messages on the mailing list regarding forum sessions15:28
serverascode#topic open discussion15:28
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"15:28
serverascodeif anyone has any other ideas, thoughts, concerns now is the time :)15:29
*** talonx has quit IRC15:29
shintarono form me15:30
shintarofrom15:30
jamemccIn terms of the session "Collaboration between Telecom/NFV related groups15:30
jamemcc"15:30
*** ntpttr has joined #openstack-meeting-415:30
*** Julien-z_ has quit IRC15:31
*** zenoway has joined #openstack-meeting-415:31
jamemccI asked if either or both of Brian Sullivan and Steven Wright of OPNFV could be there and they agreed15:31
*** Julien-zte has joined #openstack-meeting-415:31
*** Julien-zte has quit IRC15:31
serverascodethanks jamemcc, does anyone know if people from OPNFV submitted any of those sessions?15:32
shintarogreat Ildiko said she invited people from ETSI as well15:32
sergemBin is from OPNFV15:32
*** Julien-zte has joined #openstack-meeting-415:33
serverascodesergem, thanks15:33
shintaroResource reservation is from OPNFV as well15:33
shintaro#link http://forumtopics.openstack.org/cfp/details/12615:33
*** Julien-zte has quit IRC15:33
jamemccSeems to me 2 ways the discussion could go - others not in our teams asking us questions or if not - and more helpful we can go through our individual WG goals and look for more ways to collaborate15:33
jamemccJust thinking through it ahead of time15:34
serverascodehmm, and I wonder if some sessions can be double sessions15:34
*** Julien-zte has joined #openstack-meeting-415:34
*** ntpttr has quit IRC15:35
serverascodethe one thing I don't like about the summit is that the first session tends to be questions about the group, just like you mention jamemcc15:35
jamemccCurtis - the Gluon topic is in essence OPNFV and the 1000+ Scale is one of their priorities15:35
*** Julien-zte has quit IRC15:35
jamemccHmm at least one or 2 more - let me cross check - I should have and will add those to the Ethercalc15:35
*** Julien-zte has joined #openstack-meeting-415:35
serverascodeI don't see a gluon one15:35
*** Julien-zte has quit IRC15:36
*** zenoway has quit IRC15:36
*** ntpttr has joined #openstack-meeting-415:36
jamemccSorry - I mean this one: Containerized, Cloud Native Microservice in NFV Networking15:36
jamemccBin Hu15:37
serverascodeah ok15:37
shintarooh that was gluon15:37
*** duonghq has joined #openstack-meeting-415:37
serverascodeok15:37
sergemah, more networking than containers15:37
*** Sukhdev has joined #openstack-meeting-415:40
serverascodethere's also 4 sessions related to vitrage/alarms15:40
serverascodeand I wonder if it would be worhtwhile to propose the nfv collaboration session be a double session15:41
*** yingjun has quit IRC15:41
shintaro+1 40min is way too short15:41
*** iyamahat has joined #openstack-meeting-415:41
serverascodemaybe we should add a column for potential double sessions?15:41
serverascodejamemcc does that make sense to you?15:42
shintarooops I just added the column15:42
serverascodeI think that's a good idea :)15:43
serverascodewon't hurt to ask15:43
shintaroright15:43
serverascodeok anything else?15:44
*** vincentfrancois1 has left #openstack-meeting-415:44
serverascodewell I think that was a good discussion on the forum topics and I think it might help the people who are determining the schedule and submissions15:45
serverascodeso thanks everyone for coming to the meeting today, much appreciated, and hopefully around and after boston we will pick up some steam so to speak :)15:45
jamemccThank you15:45
shintarothank you serverascode15:45
sergemthanks15:46
serverascode:)15:46
serverascode#endmeeting15:46
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:46
openstackMeeting ended Wed Apr  5 15:46:23 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
shintarobye15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-04-05-15.01.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-04-05-15.01.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-04-05-15.01.log.html15:46
*** ntpttr has quit IRC15:46
*** aarefiev is now known as aarefiev_afk15:46
*** shintaro has quit IRC15:46
*** ntpttr has joined #openstack-meeting-415:48
*** mnaser has joined #openstack-meeting-415:50
*** sergem has quit IRC15:50
*** ntpttr has quit IRC15:52
*** woodard has joined #openstack-meeting-415:53
*** ntpttr has joined #openstack-meeting-415:54
*** kfox1111 has joined #openstack-meeting-415:55
*** rockyg has joined #openstack-meeting-415:55
*** rwellum has joined #openstack-meeting-415:56
*** uck has joined #openstack-meeting-415:58
*** inc0 has joined #openstack-meeting-415:59
*** iyamahat has quit IRC15:59
inc0#startmeeting Kolla16:00
openstackMeeting started Wed Apr  5 16:00:26 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
openstackThe meeting name has been set to 'kolla'16:00
sdakefirst16:00
sdakeo/ :)16:00
inc0#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: Kolla)"16:00
inc0w00t!16:00
mnasero/16:00
duonghqo/16:00
inc0repeat after me16:00
*** woodard has quit IRC16:00
inc0w-o-o-t16:01
*** mgoddard has joined #openstack-meeting-416:01
duonghqw-O-0-t16:01
mgoddardo/16:01
rwellumo/16:01
spsurya_w00t16:01
*** woodard has joined #openstack-meeting-416:01
qwango/16:01
*** vhosakot has joined #openstack-meeting-416:01
*** jascott1 has joined #openstack-meeting-416:02
*** hrww has joined #openstack-meeting-416:02
kfox1111o/16:02
hrwwo/16:02
jascott1o/16:02
vhosakoto/16:02
egonzalezw00t o/16:02
*** vishnoianil has joined #openstack-meeting-416:03
inc0#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Kolla)"16:03
inc0I've got nothing, but maybe someone from communi?16:03
sdakehmm16:03
sdakedeadline  for kolla-kubernetes is 4/15/201716:03
sdakefor 0.6.016:03
sdakethat is all :)16:03
inc0kk16:04
akwasnieo/16:04
inc0#topic Non-x86 support patchset (hrw) https://review.openstack.org/43094016:04
*** openstack changes topic to "Non-x86 support patchset (hrw) https://review.openstack.org/430940 (Meeting topic: Kolla)"16:04
hrwwoy16:04
inc0Marcin, you have the floor16:04
hrwwso...16:04
hrwwbase_arch variable got merged last week16:04
mgoddardI sent an email to the ML, but would like to announce our project kayobe which we've recently open sourced. https://github.com/stackhpc/kayobe16:04
hrwwhttps://review.openstack.org/#/q/owner:%22Marcin+Juszkiewicz%22+status:open lists my patches16:05
mgoddardprovides some additional automation around kolla-ansible with a focus on bare metal compute16:05
hrwwmost of them are now easy to merge stuff which will help non-x86 targets16:05
inc0mgoddard: cool, let's talk about it later in the meeting16:05
hrwwfrom selecting repos to taking care of missing packages16:05
mgoddardinc0: sure16:05
hrwwhttp://people.linaro.org/~marcin.juszkiewicz/kolla/ shows state of aarch64/ppc64le/x86-64 builds from some time ago16:06
sdakemgoddard ++ :)16:06
hrwwI am now rebuilding all images on those 3 architectues16:06
hrwwin other words: I need reviewers ;D16:06
*** ntpttr has quit IRC16:07
inc0hrww: since you guys want to re-introduce debian16:07
inc0I'll want gates for it16:07
inc0this is only way we can ensure that it works16:07
duonghqhrww, iirc, you want to bump debian to stretch?16:07
hrwwgnocchi, ceph, ironic-pxe, openstack-base, nova-libvirt, kubernetes are easy to check simple patches16:07
mnaserhrww thats an awesome setup of tables, great to track progress16:08
hrwwinc0: debian. that's next part of agenda16:08
inc0kk16:08
berendtO/16:08
*** ntpttr has joined #openstack-meeting-416:08
inc0let me know when you want to move on to it:P16:08
hrwwhttps://review.openstack.org/430940 patch adds base of non-x86 support - repos etc16:08
hrwwreview and lgtm :D16:08
*** vishnoianil has quit IRC16:08
* hrww done on non-x86 - questions?16:08
hrwwakwasnie?16:09
sdakehrw winning - keep at it dude :)16:09
sdakehrww ^16:09
hrwwok, let's move on to debian16:09
inc0#topic Debian 'stretch' support patchset (hrw) https://review.openstack.org/43445316:10
*** openstack changes topic to "Debian 'stretch' support patchset (hrw) https://review.openstack.org/434453 (Meeting topic: Kolla)"16:10
inc0ok...so, again16:10
inc0gates16:10
inc0debian died because of lack of thereof16:10
hrwwinc0: gates, yes. how can I check do they work in other way then 'someone enable and then recheck recheck recheck'?16:10
sdakeinc0 it really died becasue of lack of a maintainer16:10
sdakea gate is a plus for additional distros16:11
*** rwallner has quit IRC16:11
sdakehrww peopel are workingon the recheck problem16:11
hrwwso far all I know about gates/CI is "sorry, unable to make it at home"16:11
inc0hrww: workgin with gates unfortunately is pita16:11
sdakehrww we know its a problem - it annoys everyone in the community not just you16:11
hrwwsdake: no, I do not mind rechecks16:11
inc0way to do it is to create experimental gates16:12
sdakewell i mind rechecks - its slopy :)16:12
hrwwsdake: the problem for me is how to work on gates without checking how it works16:12
inc0so it won't affect other changes before we can get them to healthy state16:12
hrwwinc0: experimental gates sounds good to me16:12
kfox1111+1. rechecks are a pain and not the right solution.16:12
sdakehrww your next mission - if you choose to accept it - is to make an experimental gate of debian image building16:12
kfox1111it means the 'commons' isn't getting enough love.16:12
hrwwok, ok16:12
*** ntpttr has quit IRC16:12
mnaserimho debian should start as non voting check, then once things are stable, you can remove non voting16:12
sdakehrww we have a whole lot of people that can helpy ou get going16:13
hrwwguys - please - patches first, ok?16:13
inc0mnaser: totally starts from non voting:P16:13
*** aavraham has quit IRC16:13
hrwwwithout patches merged we have nothing to work on16:13
mnaserfyi, i made this as well, it may help finding out how stable things are, we can adjust it for debian - http://grafana.openstack.org/dashboard/db/kolla-failure-rate16:13
sdakemnaser we start with experimenal checks here16:13
hrwwDebian support is 2-3 patches16:13
hrww1. https://review.openstack.org/432787 - enable all ubuntu images for Debian16:13
sdakehrww is there an action requested?16:13
*** mandre has joined #openstack-meeting-416:13
hrwwsdake: english?16:14
sdakesup mandre16:14
sdakehrww are you requesting something of someone in the commnity?16:14
sdakeneed a review or somehting?16:14
inc0order of business is, 1. merge basic support for debian16:14
hrwwsdake: yes, I do need reviews.16:14
*** ntpttr has joined #openstack-meeting-416:14
inc02. in opesntack infra introudce debian jobs (I can help with that)16:14
inc0experimental16:14
sdakehrww ok - lets get ya unblocked - i dont have bandwidth befor efriday to review but others may16:15
hrww2nd patch is https://review.openstack.org/450805 which takes care of rtslib naming16:15
inc0then you publish patch with gates and do recheck experimental to also run debian gates16:15
hrwwand then the problematic one goes16:15
*** sayantan_ has joined #openstack-meeting-416:15
inc0iterate until gates are ready16:15
hrwwhttps://review.openstack.org/434453 - move to Debian 'stretch' (aka 'testing') instead of Jessie (current stable)16:15
inc0after that we remove experimental and keep them healthy16:15
hrwwinc0: to tell the truth I never used kolla ON debian.16:16
inc0I'll review them today, hrww you can start working on gate in infra in the meantime16:16
inc0it doesn't matter16:16
inc0what matters is whats inside container16:16
hrwwyep16:16
inc0ubuntu is similar enough to debian to make it work16:16
hrwwindeed16:16
inc0ubuntu on centos used to be problematic, but this should work16:17
hrwwit works fine16:17
hrwwI built on centos 7 and fedora 2516:17
inc0also I don't think infra even has debian images for gates16:17
akwasniehrww I will also review it16:17
hrwwakwasnie: thx16:17
inc0so ubuntu it is anyway16:17
sdakeinc0 we ca nuse ubuntu images for gates16:17
akwasniehrww np16:17
inc0yeah, that's what I'm saying16:18
hrwwinc0: ok. gates are defined in openstack-project-config repo, right?16:18
inc0yes16:18
*** ntpttr has quit IRC16:18
hrwwok, I have it cloned16:18
inc0cool, let me know if you run into any prblems16:19
mnaserhttps://github.com/openstack-infra/project-config/blob/master/nodepool/nodepool.yaml#L25-L4016:19
hrwwand duonghq asked why I moved to debian/stretch16:19
inc0also people on #openstack-infra are super helpful16:19
mnaserit does look like there is jessie images16:19
mnaserin case that helps make things easier16:19
inc0mnaser: let's keep it ubuntu regardless16:19
mnaserim okay with either, just wanted to provide insight :)16:20
hrwwmnaser: it would need to be jessie-backports probably16:20
inc0hrww: anything else or can we move on?16:20
hrwwmove on16:20
inc0#topic Upgrade gates (inc0)16:20
*** openstack changes topic to "Upgrade gates (inc0) (Meeting topic: Kolla)"16:20
*** ntpttr has joined #openstack-meeting-416:20
inc0ok, so I want to start this effort16:20
inc0few things: https://review.openstack.org/#/c/401003/1016:20
inc0way I see it working is16:21
*** julim_ has joined #openstack-meeting-416:21
inc0once we get pushable registry16:21
inc0we will push our built images up16:21
inc02. introduce new gate for upgrades16:21
*** itisha has joined #openstack-meeting-416:22
hrwwinc0: will registry allow non-x86 images?16:22
inc0that will 1. install latest stable, do smoke test, upgrade, redo tests16:22
mnaserregistry can save any sort of images, just a blob store16:22
hrwwaarch64/kolla/*:4.0.0 etc16:22
inc0hrww: registry won't mind either way, but we'll need to fingure out different name/tag for them16:22
hrwwinc0: I like upgrade testing idea16:22
inc0so that's for today, when zuulv3 lands we make it 5 node multinode16:23
inc0in effect OpenStack gets proper upgrade gating16:23
*** julim has quit IRC16:23
mnaserfyi im sure inc0 had a look at it but it would be nice to have a look at the grenade project and how they do upgrade tests16:23
inc0it's bad16:23
mnaseroh :p16:24
sdakeinc0 always the diplomat :)16:24
inc0lol16:24
*** ntpttr has quit IRC16:24
inc0well grenade will never give us multinode, based of devstack, test single service not proper upgrade path that people will actually use16:25
inc0and is a shellscript16:25
clarkbinc0: hold on16:25
hrwwdevstack... argh.16:25
mnaseroh i just mentioned that it woudl be a 'source of inspiration'16:25
inc0:D16:25
clarkbfirst of all grenade already does multinode upgrade testing16:25
clarkbbut also I'm not sure what zuulv4 and 5 node testing and upgrade testing all have to do with each other (they should be orthogonal)16:26
clarkber v316:26
sdakeclarkb is it based upon devstack?16:26
clarkbsdake: yes it uses devstack's deployment mechanisms to turn on the cloud16:26
mnaserwe cant run grenade (for the most part, i think?) -- but we can at least look at how they solved certain arch. issues we'll run into inevitebly16:26
*** ntpttr has joined #openstack-meeting-416:26
mnaserexample, things like this: https://github.com/openstack-dev/grenade#theory-of-upgrade16:26
inc0well, grenade is orch of upgrade (sort of)16:26
inc0we already have orch of upgrade16:26
sdakeclarkb i see - i think becaseu fo that, wecan't directly reuse grenade, however, we could learn from it with kolla16:26
inc0in kolla-ansible16:26
clarkbsdake: thats fine, my contention is not with you reusing it or not, its with the incorrect data being reported here16:27
clarkb(and with tying unrelated items together that shouldn't be)16:27
mnaserthats exactly what i meant to say: it's something to learn from16:27
sdakeclarkb ya - which is why I asked inc0 to expand with "the alwaasy the diplomat" response :)16:27
inc0ok, I'm sorry then16:27
sdakeclarkb not sure how zuulv4 or v5 got into discussion?16:27
inc0what I'm saying16:27
inc0we do upgrade with kolla-ansible16:27
sdakeclarkb I may have missed that16:27
inc0zuulv3 and 5 node gates16:28
inc0that was typo sdake16:28
mnaserinc0 now while i think upgrade gates are good, we need voting deploy gates beforehand16:28
clarkbinc0 | so that's for today, when zuulv3 lands we make it 5 node multinode16:28
sdakeoh - clarkb that is a dep for kolla to do multinode gating16:28
clarkbsdake: why?16:28
inc0and it got into discussion because I mentioned it as plan forward16:28
inc0well multinode is our main use case16:28
clarkbyou can do multinode gating today16:28
sdakeclarkb because inc0 says we can't get multinode until zuulv3?16:28
clarkband many people do it16:28
*** marst has quit IRC16:28
inc0single node is little more than science project as far as I'm concerned16:28
sdakei see - sound slike we have alot to learn about multinode gating16:29
inc0clarkb: 2 node16:29
clarkbinc0: and 3 and 416:29
inc0can ou do 3 node? I didn't know16:29
*** amotoki has quit IRC16:29
clarkbthe ask ahs been that you start smaller and ramp up16:29
sdakewell why are we waiting  for zuulv3 then?16:29
hrwwhave to go - starts raining and I am at the park now16:29
clarkbsdake: you shouldn't be16:29
hrwwthanks for all and see you later16:29
sdakeclarkb right -t hat was always my understanding 1->2->316:29
*** hrww has quit IRC16:29
inc0well 3 was for mariadb16:29
sdakeclarkb however inc0 indicated we can't ramp up16:29
clarkbif you want to wait thats fine, I just don't want you to think we are blocking you16:29
sdakenode count16:29
inc0regardless, when zuulv3 lands it's going tob e different mechanism16:30
*** matrohon has quit IRC16:30
clarkbbecause we aren;t and many other groups are very successful doing multinode testing today16:30
inc0clarkb: no, it wasn't about blocking16:30
sdakeclarkb the general understanding in the kolla project is zuulv3 is blocking our gating - I think we need t of ix that perception16:30
inc0it was abot not spending time on something that will be obsolete in 2 months16:30
sdakeclarkb rather our multinode gating16:30
sdakeinc0 we don't knwo when zuulv3 will be available16:30
inc0well kolla-k8s has multinode gating16:30
*** ntpttr has quit IRC16:31
clarkbinc0: I really doubt that it will be obsolete (you will learn lots and 95% fo what you do should be reusable) and I also doubt zuulv3 will be available in 2 months16:31
sdakeright 2 nodes - one of the infra core said 2 nodes was the max, although in previous conversations i had heard if we go to 2, we can have 316:31
inc0clarkb: but it will be ansible based so we could reuse lots of it16:31
inc0like inventory16:31
clarkbsdake: yes what we ask is thatyou start small because most of the problems present themselves at 2 nodes and are easier to debug there. Then when tahts working ramp up16:31
sdakeyes, lets stop sending the message in our project "we are waiting on zuulv3" because we don't knwo when zuulv3 will be deployed16:31
sdakeit could be years16:31
mnaseri think the idea here is infra wants to make sure that we're carefully using resources that we're given16:32
inc0clarkb: 3 nodes are for galera, that's why we wanted 316:32
sdakeclarkb kolla-kubernetes deliverable has 2 nodes already - could we get 3, and if so , can we get coaching on how to get to 3 nodes?16:32
mnaser(if you guys dont mind, i think we're getting a bit off track)16:32
inc0but that was my understanding too - 3 is issue for infra16:32
sdakeclarkb we can teach the rest of the cores16:32
*** ntpttr has joined #openstack-meeting-416:32
clarkbsdake: yes, if the 2 node tests are running succesfully we can bump up to 3. You just have to change the node type in the job definition to the 3-node variant16:32
mnasergoing back to upgrade gates, i think its great, but i think we need deploy gates to become voting first before we do taht16:32
sdakeclarkb cool - i'll see about doing that when i return on the 15th16:33
*** baoli has quit IRC16:33
clarkbmnaser: I would agree with that, if the base test set doesn't work then upgrades likely not to work either, you'd build one on the other16:33
sdakeclarkb our 2 node tests run fantastically well in that particular deliverable - when kubernetes itself isn;t broken16:33
inc0well our deploy gates does work...16:33
inc0they're nv but that's simple change16:33
inc0do work*16:34
sdakeok - well i think the answer is "zuulv3 isn't blocking, proceed with multinode gating *now*, port to zuulv3 whenever it comes out"16:34
mnaseralso, if i can suggest this review which i built of Jeffrey4l work -- run tempest instead of some shell scripts: https://review.openstack.org/#/c/402122/16:34
sdakeand ramp up 1 node, to 2 nodes ,to 3 nodes, etc16:34
mnaserwe can tempest to run post deploys, we switch deploys to voting, i think thats a great first step before starting upgrade gates16:34
sdakeclarkb sound good to you?16:34
sdakeinc0 ^^?16:34
inc0yes, sounds good, we need to do aio upgrade regardless16:35
inc0of multinode16:35
sdakeagreed16:35
inc0my initial thought was to wait with just multinode piece for zuulv316:35
mnaser++16:35
sdakeso next step is 2 nodes - to prove that 2 node gating is stable16:35
inc0if we want to add it earlier16:35
sdake(for kolla-ansible deliverable)16:35
inc0sure16:35
mnaserno need to do that, we can do it once our 2 node stuff is happy16:35
inc0that could go to deploy gates16:35
sdakedownside of waiting is we have no clue with zuulv3 will be ready16:35
sdakeadn msot o the work is in our repos16:36
inc0let's do 2 pararell efforts16:36
sdakechanging around the gate scripts16:36
inc01. aio upgrade16:36
inc02. multinode deploy16:36
inc0once both are ready multinode upgrade should be super easy16:36
mnaserand possible 3. make deploy gates voting?16:36
sdake2. 2 node deploy :)16:36
*** ntpttr has quit IRC16:36
sdakesounds good to me inc016:37
inc0mnaser: yeah, we should be good now16:37
inc0although if we move to docker0116:37
inc0that will change logic a bit so maybe lets wait for that for votin16:37
inc0g16:37
mnasercool, as usual, more than happy to help with ci issues... i have a few ideas surrounding scenario based testing (ala puppet-integration)16:37
inc0docker01 - infra hosted docker registry16:38
*** ntpttr has joined #openstack-meeting-416:38
inc0I also have few friends working on persistence testing (spawn a vm, test if it works, upgrade, test if it keeps working)16:38
inc0but, one step at the time plz16:38
inc0ok let's move on16:39
inc0#topic kolla-kubernetes launchpad trcking (sdake) https://launchpad.net/kolla-kubernetes/+milestone/0.6.016:39
*** openstack changes topic to "kolla-kubernetes launchpad trcking (sdake) https://launchpad.net/kolla-kubernetes/+milestone/0.6.0 (Meeting topic: Kolla)"16:39
sdakeindeed16:39
sdakeif folks could ope nthat up16:39
sdakeplz16:39
sdakethese are the blueprints for april 15th deadline16:40
sdakethi should give us a pretty solid imrpovement over 0.5.016:40
sdakeif anyone wants to change blueprint prioiritie feel free16:41
sdakeplease keep blueprints up to date16:41
*** cathrichardson has joined #openstack-meeting-416:41
sdakeand use release notes so people know what we actually release in an update16:41
sdakeany quesitions?16:41
*** cathrichardson has quit IRC16:41
*** bobmel_ has quit IRC16:41
*** cathrichardson has joined #openstack-meeting-416:41
mnasercool progress :> hopefully we can see it come more alive soon16:41
sdakethese are all on teh march to a 1.0.0 release16:42
sdakemnaser rwellum got kolla-kubernetes running today and eanlin has had it running for  afew days based upoon the deploy doc16:42
mnaserawesome #progress16:42
sdakemnaser there are 20 reviewers on the deploy doc - so seems like there is interest :)16:42
sdakeok i'll give it 60 seconds then we can move on16:43
sdakein case pople hae further questions16:43
sdake(or inc0 can you give it 60 secondds) :)16:43
*** sayantan_ has quit IRC16:43
sdakeapril 15th - lets hitit :)16:43
*** baoli has joined #openstack-meeting-416:43
sdakeinc0 can move on now thanks16:43
inc0kk)16:44
sdakeinc0 - mgoddard probably first up on opens16:44
inc0#topic open discussion16:44
*** openstack changes topic to "open discussion (Meeting topic: Kolla)"16:44
inc0yes, I wanted to talk about this, looks awesome16:44
mgoddardgreat :)16:44
mnasersame16:44
inc0so few things16:44
inc01. let's examine how much of this automation can be brought to kolla-ansible16:45
*** ntpttr has quit IRC16:45
inc0since I bet lots of it can be reused16:45
inc02. I propose new section in docs - scenerios16:45
mnaseralso one thing i like about this from a deployer perspective is like16:45
inc0where we'll explain how to deploy certain opesntacks for various use cases16:45
*** vks1 has quit IRC16:45
mnaserthis seems to be an excellent example of .. how do i reuse kolla for my specific usecase16:45
inc0scientific being one of them:)16:45
mgoddard1: agreed.16:45
mnaserbut also making it re-usable16:45
*** ntpttr has joined #openstack-meeting-416:46
mgoddardfor 1, kolla-ansible is currently not doing any significant configuration of the hosts. I thought that was initially a design goal?16:46
mnaserfor all of our deployments, we want to maintain a set of baseline rules, and then we modify a certain few things on top for kolla.   the code that does this causes a lot of extra duplication.  this seems like a good way of reusing kolla with a common set of values16:47
*** vkmc__ has quit IRC16:47
mnasermgoddard there is kolla-ansible bootstrap-server16:47
mnaserbut that assumes an existing server16:47
mnaseraka installed os, etc16:47
inc0mgoddard: yeah, but we can extend our config of the hosts significantly16:47
inc0as long as it's decoupled from actual deployment16:47
mgoddardmnaser: true, although it's optional and incomplete16:47
inc0I'd keep it optional16:47
mgoddardinc0: ok, sounds good16:47
mnaseryep16:47
*** marst has joined #openstack-meeting-416:47
inc0but incomplete is fixable16:47
mgoddardinc0: sure :)16:48
inc0maybe even separate it to new directory16:48
*** limao_ has quit IRC16:48
inc0not sure16:48
inc0just roles is also fine16:48
inc0but we can extend it, I'm all for it16:48
*** limao has joined #openstack-meeting-416:48
mgoddardone issue is that it does tend to get a bit opinionated and site-specific16:48
*** bobmel has joined #openstack-meeting-416:48
inc0mgoddard: that's why we need to get only non-specific to main bootstrap16:49
*** hieulq_ has joined #openstack-meeting-416:49
mgoddardI've tried to keep it flexible but things are inherently less consistent outside of container-land16:49
inc0and rest can live in kaobe or kolla-ansible/contrib and/or docs16:49
inc0ofc16:49
mgoddardok, so what can I do to help facilitate all of this, or at least kick it off?16:50
inc0I'd start with docs16:50
inc0add new doc section for use cases16:50
inc0document scientific use case using kaobe16:50
spsurya_inc0: +116:50
mgoddardpresumably we need to work out what's in scope for kolla-ansible16:50
inc0and we'll go from there16:50
*** ntpttr has quit IRC16:50
inc0together examine what can be reused and maybe create different use case docs16:51
sdakemgoddard we have a bit of capacity problem atm with kolla16:51
sdakemgoddard everyone working their tials off16:51
mgoddardinc0: ok. I'll try to put something together16:51
inc0yes, but this will be extreamlly appreciated16:51
sdakemgoddard yup I think what you have would be a really good fit inside kolla - although dont feel compelled to do it that way :)16:52
mgoddardsdake: I'm sure kolla-k8s is keeping you busy :)16:52
inc0real life guides are what operators love16:52
sdakemgoddard indeed i hae little itme to contribute to the part i'm most proud of - teh ansible implementation16:52
*** ntpttr has joined #openstack-meeting-416:52
inc0we have broaded community to help:)16:52
mgoddardsdake: getting some or all of our work into kolla would be a great result for us16:52
inc0also another thing is if we could get at least docs done before summit16:52
inc0we can talk to operators there to share their love in form of docs;)16:53
mgoddardno point in having separately maintained projects if not necessary16:53
inc0mgoddard: think what you could move to kolla-ansible, you know both projects16:53
*** cathrichardson has left #openstack-meeting-416:53
sdakeinc0 don't force it hto :)16:53
mgoddardok, I'll keep boston as a target in mind16:54
sdakeits really up to you mgoddard16:54
*** limao has quit IRC16:54
inc0one potential wold be another repo split for all the host-based stuff16:54
sdakeinc0++ repo splits are so much fun :)16:54
inc0but that's different discussion16:54
sdakemgoddard as far as mission goes, it does fit in the mission16:54
sdake"deployment tools for openstack clouds"16:54
sdakedeploying the bare metal is part of that16:55
sdakewe have some host scripts already16:55
*** bobmel has quit IRC16:55
sdakethey need some love16:55
mgoddardfrom my perspective it's only a separate project because we have customers with requirements16:55
inc0yeah it's easier to move with local repo16:56
inc0but we can move it to kolla in our own pace16:56
mgoddardbetter to do it the right way than to rush16:56
*** rwallner has joined #openstack-meeting-416:56
inc0ok, few minutes left16:56
*** ntpttr has quit IRC16:56
inc0anything else we want to mention?16:57
mgoddardthat was a great reception of the project, thanks all!16:57
inc0thank you Mark for awesome work!16:57
*** rwallner has quit IRC16:57
*** rwallner has joined #openstack-meeting-416:57
mgoddardstanding on the shoulders of giants - thanks to you all16:58
*** Sukhdev has quit IRC16:58
inc0ok, I'll wrap up meeting then:)16:58
inc0thank you all for coming and let's get back to making cool things work16:58
inc0#endmeeting kolla16:58
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:58
openstackMeeting ended Wed Apr  5 16:58:30 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
*** ntpttr has joined #openstack-meeting-416:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-05-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-05-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-05-16.00.log.html16:58
*** Sukhdev has joined #openstack-meeting-416:59
*** jascott1 has left #openstack-meeting-417:01
*** ntpttr has quit IRC17:02
*** mgoddard has quit IRC17:02
*** egonzalez has quit IRC17:03
*** bobmel has joined #openstack-meeting-417:04
*** ntpttr has joined #openstack-meeting-417:04
*** baoli_ has joined #openstack-meeting-417:05
*** mnaser has left #openstack-meeting-417:06
*** duonghq has quit IRC17:06
*** baoli_ has quit IRC17:07
*** baoli has quit IRC17:07
*** wxy| has quit IRC17:08
*** ntpttr has quit IRC17:08
*** salmankhan has quit IRC17:09
*** ntpttr has joined #openstack-meeting-417:10
*** unicell has quit IRC17:12
*** baoli has joined #openstack-meeting-417:13
*** ntpttr has quit IRC17:14
*** ntpttr has joined #openstack-meeting-417:16
*** cathrichardson has joined #openstack-meeting-417:17
*** cathrich_ has joined #openstack-meeting-417:17
*** galstrom_zzz is now known as galstrom17:18
*** cathrichardson has quit IRC17:22
*** rockyg has quit IRC17:23
*** uck has quit IRC17:25
*** rockyg has joined #openstack-meeting-417:26
*** ntpttr has quit IRC17:27
*** ntpttr has joined #openstack-meeting-417:28
*** hieulq__ has joined #openstack-meeting-417:30
*** freyes has left #openstack-meeting-417:32
*** sambetts is now known as sambetts|afk17:33
*** hieulq_ has quit IRC17:34
*** yfauser_ has quit IRC17:34
*** ntpttr has quit IRC17:35
*** yfauser has joined #openstack-meeting-417:35
*** ntpttr has joined #openstack-meeting-417:36
*** cathrich_ has left #openstack-meeting-417:37
*** yfauser has quit IRC17:40
*** unicell has joined #openstack-meeting-417:41
*** bobh has quit IRC17:42
*** ntpttr has quit IRC17:43
*** ntpttr has joined #openstack-meeting-417:44
*** ntpttr has quit IRC17:49
*** ntpttr has joined #openstack-meeting-417:50
*** vhosakot has quit IRC17:56
*** hieulq__ has quit IRC17:56
*** erikmwilson has quit IRC17:57
*** s3wong has joined #openstack-meeting-417:57
*** erikmwilson has joined #openstack-meeting-417:58
*** ntpttr has quit IRC17:59
*** ntpttr has joined #openstack-meeting-418:00
*** rwallner has quit IRC18:03
*** rwallner has joined #openstack-meeting-418:03
*** rwallner has quit IRC18:04
*** rwallner has joined #openstack-meeting-418:04
*** ntpttr has quit IRC18:04
*** ntpttr has joined #openstack-meeting-418:06
*** krtaylor has quit IRC18:07
*** ralonsoh has quit IRC18:08
*** ltomasbo is now known as ltomasbo|away18:09
*** ntpttr has quit IRC18:11
*** ntpttr has joined #openstack-meeting-418:12
*** cathrichardson has joined #openstack-meeting-418:13
*** cathrich_ has joined #openstack-meeting-418:13
*** ntpttr has quit IRC18:17
*** cathrichardson has quit IRC18:17
*** ntpttr has joined #openstack-meeting-418:18
*** yfauser has joined #openstack-meeting-418:20
*** dtardivel has quit IRC18:20
*** ntpttr has quit IRC18:23
*** ntpttr has joined #openstack-meeting-418:24
*** Sukhdev has quit IRC18:25
*** uck has joined #openstack-meeting-418:25
*** iyamahat has joined #openstack-meeting-418:27
*** ntpttr has quit IRC18:28
*** ntpttr has joined #openstack-meeting-418:30
*** uck has quit IRC18:30
*** rwallner has quit IRC18:32
*** harlowja has quit IRC18:33
*** iyamahat has quit IRC18:35
*** ntpttr has quit IRC18:37
*** ntpttr has joined #openstack-meeting-418:38
*** rwallner has joined #openstack-meeting-418:41
*** rwallner has joined #openstack-meeting-418:41
*** bobh has joined #openstack-meeting-418:42
*** ntpttr has quit IRC18:47
*** bobh has quit IRC18:47
*** ntpttr has joined #openstack-meeting-418:48
*** krtaylor has joined #openstack-meeting-418:51
*** ntpttr has quit IRC18:57
*** ntpttr has joined #openstack-meeting-418:58
*** Sukhdev has joined #openstack-meeting-418:58
*** ntpttr has quit IRC19:02
*** ntpttr has joined #openstack-meeting-419:04
*** lyan has quit IRC19:07
*** ntpttr has quit IRC19:08
*** bobh has joined #openstack-meeting-419:10
*** ntpttr has joined #openstack-meeting-419:10
*** ntpttr has quit IRC19:17
*** ntpttr has joined #openstack-meeting-419:18
*** rockyg has quit IRC19:19
*** ntpttr has quit IRC19:22
*** salmankhan has joined #openstack-meeting-419:23
*** rfolco has quit IRC19:24
*** ntpttr has joined #openstack-meeting-419:24
*** salmankhan has quit IRC19:25
*** salmankhan has joined #openstack-meeting-419:26
*** ntpttr has quit IRC19:29
*** ntpttr has joined #openstack-meeting-419:30
*** ntpttr has quit IRC19:35
*** rwallner has quit IRC19:35
*** rwallner has joined #openstack-meeting-419:36
*** ntpttr has joined #openstack-meeting-419:36
*** ntpttr has quit IRC19:41
*** ntpttr has joined #openstack-meeting-419:42
*** rwallner has quit IRC19:42
*** rwallner_ has joined #openstack-meeting-419:46
*** ntpttr has quit IRC19:47
*** oanson has quit IRC19:47
*** ntpttr has joined #openstack-meeting-419:48
*** rwallner_ has quit IRC19:51
*** ntpttr has quit IRC19:52
*** irenab has quit IRC19:53
*** lihi has quit IRC19:53
*** pshedimb_ has quit IRC19:54
*** ntpttr has joined #openstack-meeting-419:54
*** oanson has joined #openstack-meeting-419:55
*** lihi has joined #openstack-meeting-419:55
*** rwellum has left #openstack-meeting-419:56
*** irenab has joined #openstack-meeting-419:56
*** yfauser has quit IRC19:56
*** yfauser has joined #openstack-meeting-419:57
*** harlowja has joined #openstack-meeting-419:58
*** ntpttr has quit IRC19:58
*** ntpttr has joined #openstack-meeting-420:00
*** pcaruana has quit IRC20:01
*** yfauser has quit IRC20:02
*** iyamahat has joined #openstack-meeting-420:02
*** marst_ has joined #openstack-meeting-420:03
*** marst has quit IRC20:03
*** ntpttr has quit IRC20:05
*** ntpttr has joined #openstack-meeting-420:06
*** cathrich_ has quit IRC20:11
*** iyamahat has quit IRC20:11
*** ntpttr has quit IRC20:13
*** lyan has joined #openstack-meeting-420:14
*** ntpttr has joined #openstack-meeting-420:14
*** ntpttr has quit IRC20:19
*** ntpttr has joined #openstack-meeting-420:20
*** cathrichardson has joined #openstack-meeting-420:21
*** Sukhdev has quit IRC20:21
*** cathrich_ has joined #openstack-meeting-420:22
*** cathrich_ is now known as cathrichardson_20:23
*** ntpttr has quit IRC20:25
*** cathrichardson has quit IRC20:26
*** ntpttr has joined #openstack-meeting-420:26
*** uck has joined #openstack-meeting-420:28
*** ntpttr has quit IRC20:31
*** ntpttr has joined #openstack-meeting-420:32
*** uck has quit IRC20:33
*** lihi has quit IRC20:33
*** lihi has joined #openstack-meeting-420:34
*** ntpttr has quit IRC20:37
*** ntpttr has joined #openstack-meeting-420:38
*** chigang has quit IRC20:39
*** ntpttr has quit IRC20:45
*** woodard_ has joined #openstack-meeting-420:45
*** ntpttr has joined #openstack-meeting-420:46
*** woodard has quit IRC20:49
*** woodard_ has quit IRC20:50
*** thorst has quit IRC20:50
*** thorst has joined #openstack-meeting-420:51
*** ntpttr has quit IRC20:51
*** ntpttr has joined #openstack-meeting-420:52
*** tonytan4ever has quit IRC20:54
*** thorst has quit IRC20:55
*** pshedimb_ has joined #openstack-meeting-420:56
*** ntpttr has quit IRC20:57
*** yfauser has joined #openstack-meeting-420:57
*** ntpttr has joined #openstack-meeting-420:58
*** vishnoianil has joined #openstack-meeting-420:59
*** cleong has quit IRC21:00
*** yfauser has quit IRC21:02
*** ntpttr has quit IRC21:02
*** ntpttr has joined #openstack-meeting-421:04
*** rbak__ has quit IRC21:05
*** mgoddard has joined #openstack-meeting-421:08
*** galstrom is now known as galstrom_zzz21:10
*** galstrom_zzz is now known as galstrom21:11
*** ntpttr has quit IRC21:11
*** itisha has quit IRC21:12
*** ntpttr has joined #openstack-meeting-421:12
*** uck has joined #openstack-meeting-421:16
*** ntpttr has quit IRC21:16
*** thorst has joined #openstack-meeting-421:18
*** ntpttr has joined #openstack-meeting-421:18
*** julim_ has quit IRC21:18
*** thorst has quit IRC21:22
*** galstrom is now known as galstrom_zzz21:22
*** rwallner has joined #openstack-meeting-421:23
*** ntpttr has quit IRC21:23
*** mgoddard has quit IRC21:24
*** ntpttr has joined #openstack-meeting-421:24
*** rwallner has quit IRC21:27
*** ntpttr has quit IRC21:29
*** rfolco has joined #openstack-meeting-421:29
*** haleyb has quit IRC21:29
*** ntpttr has joined #openstack-meeting-421:30
*** ntpttr has quit IRC21:35
*** ntpttr has joined #openstack-meeting-421:36
*** trinaths1 has joined #openstack-meeting-421:38
*** trinaths2 has joined #openstack-meeting-421:38
*** ntpttr has quit IRC21:41
*** trinaths1 has quit IRC21:42
*** ntpttr has joined #openstack-meeting-421:42
*** woodard has joined #openstack-meeting-421:43
*** cathrichardson_ has quit IRC21:45
*** ntpttr has quit IRC21:47
*** ntpttr has joined #openstack-meeting-421:48
*** lyan has quit IRC21:48
*** ntpttr has quit IRC21:53
*** thorst has joined #openstack-meeting-421:53
*** ntpttr has joined #openstack-meeting-421:54
*** Sukhdev has joined #openstack-meeting-421:56
*** mbruzek has quit IRC21:58
*** ntpttr has quit IRC21:59
*** ntpttr has joined #openstack-meeting-422:00
*** salmankhan has quit IRC22:01
*** vishnoianil has quit IRC22:02
*** ntpttr has quit IRC22:05
*** harlowja has quit IRC22:05
*** ntpttr has joined #openstack-meeting-422:06
*** galstrom_zzz is now known as galstrom22:10
*** thorst has quit IRC22:12
*** ntpttr has quit IRC22:13
*** ntpttr has joined #openstack-meeting-422:14
*** ntpttr has quit IRC22:19
*** gongysh has joined #openstack-meeting-422:19
*** ntpttr has joined #openstack-meeting-422:20
*** uck has quit IRC22:24
*** ntpttr has quit IRC22:27
*** yfauser has joined #openstack-meeting-422:28
*** ntpttr has joined #openstack-meeting-422:28
*** baoli has quit IRC22:31
*** yfauser has quit IRC22:32
*** klamath has quit IRC22:34
*** ntpttr has quit IRC22:35
*** ntpttr has joined #openstack-meeting-422:35
*** rbak has joined #openstack-meeting-422:37
*** ntpttr has quit IRC22:40
*** ntpttr has joined #openstack-meeting-422:42
*** krtaylor has quit IRC22:45
*** rbak has quit IRC22:46
*** ntpttr has quit IRC22:46
*** rbak has joined #openstack-meeting-422:48
*** ntpttr has joined #openstack-meeting-422:48
*** marst_ has quit IRC22:52
*** marst_ has joined #openstack-meeting-422:52
*** ntpttr has quit IRC22:53
*** ntpttr has joined #openstack-meeting-422:54
*** cholcombe has quit IRC22:55
*** marst_ has quit IRC22:56
*** thorst has joined #openstack-meeting-422:59
*** julim has joined #openstack-meeting-423:00
*** pshedimb_ has quit IRC23:00
*** ntpttr has quit IRC23:03
*** thorst has quit IRC23:04
*** ntpttr has joined #openstack-meeting-423:04
*** Sukhdev has quit IRC23:06
*** iyamahat has joined #openstack-meeting-423:07
*** bobh has quit IRC23:09
*** ntpttr has quit IRC23:09
*** pshedimb_ has joined #openstack-meeting-423:09
*** ntpttr has joined #openstack-meeting-423:10
*** ntpttr has quit IRC23:15
*** iyamahat has quit IRC23:16
*** galstrom is now known as galstrom_zzz23:16
*** ntpttr has joined #openstack-meeting-423:16
*** gongysh has quit IRC23:20
*** ntpttr has quit IRC23:21
*** ntpttr has joined #openstack-meeting-423:22
*** lamt has quit IRC23:23
*** uck has joined #openstack-meeting-423:25
*** harlowja has joined #openstack-meeting-423:25
*** yfauser has joined #openstack-meeting-423:28
*** ntpttr has quit IRC23:29
*** uck has quit IRC23:30
*** ntpttr has joined #openstack-meeting-423:30
*** baoli has joined #openstack-meeting-423:32
*** rbak has quit IRC23:32
*** yfauser has quit IRC23:33
*** baoli has quit IRC23:33
*** baoli has joined #openstack-meeting-423:34
*** thorst has joined #openstack-meeting-423:34
*** ntpttr has quit IRC23:35
*** Sukhdev has joined #openstack-meeting-423:35
*** ntpttr has joined #openstack-meeting-423:36
*** ntpttr has quit IRC23:41
*** jjung has quit IRC23:42
*** ntpttr has joined #openstack-meeting-423:42
*** yfauser has joined #openstack-meeting-423:44
*** ntpttr has quit IRC23:47
*** ntpttr has joined #openstack-meeting-423:48
*** thorst has quit IRC23:49
*** yfauser has quit IRC23:49
*** krtaylor has joined #openstack-meeting-423:51
*** ntpttr has quit IRC23:55
*** ntpttr has joined #openstack-meeting-423:56
*** yingjun has joined #openstack-meeting-423:59

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