Wednesday, 2016-06-29

*** sacharya_ has quit IRC00:00
*** hvprash_ has quit IRC00:00
*** markvoelker has quit IRC00:01
*** kbyrne has joined #openstack-meeting-400:01
*** markvoelker has joined #openstack-meeting-400:02
*** markvoelker has quit IRC00:02
*** markvoelker has joined #openstack-meeting-400:02
*** piet has quit IRC00:03
*** ajmiller has quit IRC00:03
*** hshan has quit IRC00:04
*** ajmiller has joined #openstack-meeting-400:04
*** salv-orl_ has quit IRC00:05
*** salv-orlando has joined #openstack-meeting-400:05
*** shaohe_feng has quit IRC00:08
*** shaohe_feng has joined #openstack-meeting-400:09
*** salv-orlando has quit IRC00:10
*** piet has joined #openstack-meeting-400:12
*** thorst has joined #openstack-meeting-400:13
*** doonhammer has joined #openstack-meeting-400:13
*** shaohe_feng has quit IRC00:18
*** shaohe_feng has joined #openstack-meeting-400:18
*** doonhammer has quit IRC00:18
*** thorst has quit IRC00:21
*** julim has quit IRC00:27
*** shaohe_feng has quit IRC00:28
*** asingh has quit IRC00:29
*** shaohe_feng has joined #openstack-meeting-400:29
*** mriedem_away is now known as mriedem00:37
*** shaohe_feng has quit IRC00:39
*** shaohe_feng has joined #openstack-meeting-400:39
*** mbound has joined #openstack-meeting-400:44
*** limao has joined #openstack-meeting-400:48
*** mbound has quit IRC00:49
*** shaohe_feng has quit IRC00:49
*** shaohe_feng has joined #openstack-meeting-400:50
*** feipeng1 has quit IRC00:50
*** uck has joined #openstack-meeting-400:53
*** uck has quit IRC00:53
*** kbyrne has quit IRC00:57
*** thorst has joined #openstack-meeting-400:59
*** shaohe_feng has quit IRC00:59
*** spzala has joined #openstack-meeting-401:01
*** shaohe_feng has joined #openstack-meeting-401:02
*** spzala has quit IRC01:06
*** shaohe_feng has quit IRC01:09
*** shaohe_feng has joined #openstack-meeting-401:10
*** sacharya has joined #openstack-meeting-401:11
*** iceyao has joined #openstack-meeting-401:11
*** salv-orlando has joined #openstack-meeting-401:12
*** pvaneck has quit IRC01:12
*** iceyao_ has joined #openstack-meeting-401:13
*** zhurong has joined #openstack-meeting-401:13
*** Jeffrey4l has joined #openstack-meeting-401:15
*** iceyao has quit IRC01:16
*** Sukhdev has quit IRC01:18
*** iurygregory has quit IRC01:18
*** shaohe_feng has quit IRC01:22
*** salv-orlando has quit IRC01:22
*** limao_ has joined #openstack-meeting-401:22
*** shaohe_feng has joined #openstack-meeting-401:22
*** yamahata has joined #openstack-meeting-401:22
*** openstack has joined #openstack-meeting-401:24
*** ChanServ sets mode: +o openstack01:24
*** ddieterly has quit IRC01:28
*** shaohe_feng has quit IRC01:30
*** shaohe_feng has joined #openstack-meeting-401:30
*** iurygregory has joined #openstack-meeting-401:31
*** xingchao has joined #openstack-meeting-401:33
*** vishnoianil has joined #openstack-meeting-401:36
*** piet has quit IRC01:37
*** woodster_ has quit IRC01:39
*** shihanzhang has quit IRC01:39
*** shaohe_feng has quit IRC01:40
*** s3wong has quit IRC01:41
*** shaohe_feng has joined #openstack-meeting-401:41
*** thorst has quit IRC01:43
*** thorst has joined #openstack-meeting-401:44
*** ddieterly has joined #openstack-meeting-401:47
*** daneyon has quit IRC01:50
*** shaohe_feng has quit IRC01:50
*** shaohe_feng has joined #openstack-meeting-401:51
*** thorst has quit IRC01:52
*** shaohe_feng has quit IRC02:01
*** shaohe_feng has joined #openstack-meeting-402:01
*** yamahata has quit IRC02:02
*** iyamahat has quit IRC02:02
*** spzala has joined #openstack-meeting-402:03
*** ddieterly has quit IRC02:04
*** spzala has quit IRC02:08
*** shaohe_feng has quit IRC02:11
*** shaohe_feng has joined #openstack-meeting-402:11
*** hvprash has joined #openstack-meeting-402:12
*** asingh has quit IRC02:14
*** salv-orlando has joined #openstack-meeting-402:16
*** hvprash has quit IRC02:17
*** zhurong has quit IRC02:20
*** shaohe_feng has quit IRC02:21
*** zhurong has joined #openstack-meeting-402:21
*** shaohe_feng has joined #openstack-meeting-402:21
*** salv-orlando has quit IRC02:24
*** bobh has joined #openstack-meeting-402:25
*** baoli_ has quit IRC02:25
*** sacharya_ has joined #openstack-meeting-402:26
*** sacharya has quit IRC02:28
*** mriedem has quit IRC02:28
*** bobh has quit IRC02:30
*** shaohe_feng has quit IRC02:31
*** raddaoui has joined #openstack-meeting-402:32
*** spzala has joined #openstack-meeting-402:34
*** shaohe_feng has joined #openstack-meeting-402:34
*** woodard has quit IRC02:37
*** woodard has joined #openstack-meeting-402:39
*** woodard_ has joined #openstack-meeting-402:41
*** woodard has quit IRC02:42
*** shaohe_feng has quit IRC02:42
*** armax_ has joined #openstack-meeting-402:42
*** shaohe_feng has joined #openstack-meeting-402:42
*** armax has quit IRC02:44
*** armax_ is now known as armax02:44
*** yamahata has joined #openstack-meeting-402:49
*** numans has quit IRC02:49
*** woodard_ has quit IRC02:50
*** thorst has joined #openstack-meeting-402:50
*** shaohe_feng has quit IRC02:52
*** shaohe_feng has joined #openstack-meeting-402:53
*** thorst has quit IRC02:57
*** shaohe_feng has quit IRC03:02
*** shaohe_feng has joined #openstack-meeting-403:03
*** uxdanielle has quit IRC03:05
*** shaohe_feng has quit IRC03:12
*** shaohe_feng has joined #openstack-meeting-403:13
*** krtaylor has joined #openstack-meeting-403:18
*** krtaylor has quit IRC03:20
*** sacharya_ has quit IRC03:20
*** sacharya has joined #openstack-meeting-403:20
*** salv-orlando has joined #openstack-meeting-403:21
*** shaohe_feng has quit IRC03:23
*** shaohe_feng has joined #openstack-meeting-403:23
*** salv-orlando has quit IRC03:26
*** numans has joined #openstack-meeting-403:30
*** yamamot__ has joined #openstack-meeting-403:32
*** shaohe_feng has quit IRC03:33
*** shaohe_feng has joined #openstack-meeting-403:34
*** ajmiller has quit IRC03:36
*** ajmiller has joined #openstack-meeting-403:36
*** gongysh has joined #openstack-meeting-403:39
*** spzala has quit IRC03:42
*** spzala has joined #openstack-meeting-403:43
*** shaohe_feng has quit IRC03:43
*** shaohe_feng has joined #openstack-meeting-403:44
*** tfukushima has joined #openstack-meeting-403:46
*** iyamahat has joined #openstack-meeting-403:46
*** vikasc has joined #openstack-meeting-403:47
*** spzala has quit IRC03:47
*** sacharya has quit IRC03:49
*** sacharya has joined #openstack-meeting-403:49
*** bryan_att has quit IRC03:53
*** shaohe_feng has quit IRC03:53
*** shaohe_feng has joined #openstack-meeting-403:54
*** salv-orlando has joined #openstack-meeting-403:54
*** thorst has joined #openstack-meeting-403:55
*** xingchao has quit IRC03:57
*** padkrish has joined #openstack-meeting-404:00
*** salv-orlando has quit IRC04:00
*** thorst has quit IRC04:03
*** shaohe_feng has quit IRC04:04
*** shaohe_feng has joined #openstack-meeting-404:04
*** yantarou has quit IRC04:10
*** yantarou has joined #openstack-meeting-404:11
*** xingchao has joined #openstack-meeting-404:12
*** xingchao has quit IRC04:14
*** shaohe_feng has quit IRC04:14
*** shaohe_feng has joined #openstack-meeting-404:15
*** zhurong has quit IRC04:18
*** zhurong has joined #openstack-meeting-404:19
*** shaohe_feng has quit IRC04:24
*** shaohe_feng has joined #openstack-meeting-404:25
*** zhurong has quit IRC04:28
*** zhurong has joined #openstack-meeting-404:29
*** armax has quit IRC04:29
*** salv-orlando has joined #openstack-meeting-404:30
*** markvoelker has quit IRC04:31
*** salv-orlando has quit IRC04:33
*** Sukhdev has joined #openstack-meeting-404:34
*** shaohe_feng has quit IRC04:34
*** shaohe_feng has joined #openstack-meeting-404:35
*** gongysh has quit IRC04:43
*** spzala has joined #openstack-meeting-404:43
*** shaohe_feng has quit IRC04:45
*** shaohe_feng has joined #openstack-meeting-404:45
*** spzala has quit IRC04:48
*** shaohe_feng has quit IRC04:55
*** shaohe_feng has joined #openstack-meeting-404:55
*** njohnston is now known as njohnston|sleep04:56
*** pcaruana has quit IRC04:58
*** yamamot__ has quit IRC04:59
*** salv-orlando has joined #openstack-meeting-404:59
*** sacharya has quit IRC05:00
*** thorst has joined #openstack-meeting-405:01
*** spzala has joined #openstack-meeting-405:01
*** zhurong has quit IRC05:04
*** shaohe_feng has quit IRC05:05
*** shaohe_feng has joined #openstack-meeting-405:05
*** salv-orlando has quit IRC05:06
*** spzala has quit IRC05:06
*** zhurong has joined #openstack-meeting-405:07
*** thorst has quit IRC05:08
*** numans has quit IRC05:13
*** salv-orlando has joined #openstack-meeting-405:14
*** xingchao has joined #openstack-meeting-405:14
*** shaohe_feng has quit IRC05:15
*** shaohe_feng has joined #openstack-meeting-405:16
*** xingchao has quit IRC05:20
*** hdaniel has joined #openstack-meeting-405:23
*** shaohe_feng has quit IRC05:26
*** shaohe_feng has joined #openstack-meeting-405:26
*** numans has joined #openstack-meeting-405:27
*** iyamahat has quit IRC05:31
*** markvoelker has joined #openstack-meeting-405:32
*** padkrish has quit IRC05:34
*** GB21 has joined #openstack-meeting-405:35
*** padkrish has joined #openstack-meeting-405:35
*** shaohe_feng has quit IRC05:36
*** shaohe_feng has joined #openstack-meeting-405:36
*** markvoelker has quit IRC05:37
*** yamamot__ has joined #openstack-meeting-405:38
*** xingchao has joined #openstack-meeting-405:39
*** GB21 has quit IRC05:44
*** shaohe_feng has quit IRC05:46
*** outofmemory has quit IRC05:47
*** shaohe_feng has joined #openstack-meeting-405:47
*** numans has quit IRC05:48
*** padkrish has quit IRC05:50
*** oshidoshi has joined #openstack-meeting-405:52
*** nkrinner_afk is now known as nkrinner05:54
*** shaohe_feng has quit IRC05:56
*** padkrish has joined #openstack-meeting-405:56
*** iceyao has joined #openstack-meeting-405:57
*** shaohe_feng has joined #openstack-meeting-405:57
*** tfukushima has quit IRC05:59
*** iceyao_ has quit IRC05:59
*** tfukushima has joined #openstack-meeting-405:59
*** numans has joined #openstack-meeting-405:59
*** tfukushima has quit IRC06:00
*** tfukushima has joined #openstack-meeting-406:00
*** javeriak has joined #openstack-meeting-406:02
*** spzala has joined #openstack-meeting-406:02
*** thorst has joined #openstack-meeting-406:05
*** shaohe_feng has quit IRC06:07
*** spzala has quit IRC06:07
*** iceyao has quit IRC06:08
*** shaohe_feng has joined #openstack-meeting-406:09
*** iceyao has joined #openstack-meeting-406:12
*** thorst has quit IRC06:12
*** GB21 has joined #openstack-meeting-406:13
*** pcaruana has joined #openstack-meeting-406:16
*** shaohe_feng has quit IRC06:17
*** shaohe_feng has joined #openstack-meeting-406:18
*** pcaruana is now known as pcaruana|afk|06:19
*** Sukhdev has quit IRC06:24
*** shaohe_feng has quit IRC06:27
*** shaohe_feng has joined #openstack-meeting-406:30
*** markvoelker has joined #openstack-meeting-406:33
*** markvoelker has quit IRC06:37
*** shaohe_feng has quit IRC06:37
*** shaohe_feng has joined #openstack-meeting-406:38
*** amotoki has joined #openstack-meeting-406:39
*** iyamahat has joined #openstack-meeting-406:41
*** shaohe_feng has quit IRC06:48
*** pcaruana|afk| is now known as pcaruana06:49
*** shaohe_feng has joined #openstack-meeting-406:50
*** iceyao has quit IRC06:50
*** iceyao has joined #openstack-meeting-406:51
*** lelouch_ has joined #openstack-meeting-406:51
*** padkrish has quit IRC06:53
*** jed56 has joined #openstack-meeting-406:53
*** belmoreira has joined #openstack-meeting-406:56
*** raddaoui has quit IRC06:57
*** shaohe_feng has quit IRC06:58
*** shaohe_feng has joined #openstack-meeting-406:58
*** padkrish has joined #openstack-meeting-406:59
*** piet has joined #openstack-meeting-407:02
*** spzala has joined #openstack-meeting-407:03
*** padkrish has quit IRC07:07
*** spzala has quit IRC07:08
*** shaohe_feng has quit IRC07:08
*** shaohe_feng has joined #openstack-meeting-407:08
*** thorst has joined #openstack-meeting-407:10
*** iberezovskiy|off has quit IRC07:17
*** degorenko has quit IRC07:17
*** thorst has quit IRC07:17
*** degorenko has joined #openstack-meeting-407:18
*** shaohe_feng has quit IRC07:18
*** shaohe_feng has joined #openstack-meeting-407:19
*** zeih has joined #openstack-meeting-407:25
*** saju_m has joined #openstack-meeting-407:26
*** iberezovskiy has joined #openstack-meeting-407:27
*** shaohe_feng has quit IRC07:29
*** piet has quit IRC07:29
*** dshakhray_ has joined #openstack-meeting-407:29
*** dtardivel has joined #openstack-meeting-407:29
*** GB21 has quit IRC07:30
*** shaohe_feng has joined #openstack-meeting-407:30
*** zhurong has quit IRC07:30
*** ajmiller has quit IRC07:33
*** zhurong has joined #openstack-meeting-407:33
*** ajmiller has joined #openstack-meeting-407:34
*** markvoelker has joined #openstack-meeting-407:34
*** amotoki has quit IRC07:37
*** markvoelker has quit IRC07:38
*** shaohe_feng has quit IRC07:39
*** shaohe_feng has joined #openstack-meeting-407:40
*** amotoki has joined #openstack-meeting-407:43
*** vnogin has quit IRC07:46
*** vnogin_ has joined #openstack-meeting-407:46
*** zeih has quit IRC07:49
*** shaohe_feng has quit IRC07:49
*** shaohe_feng has joined #openstack-meeting-407:50
*** saju_m has quit IRC07:51
*** saju_m has joined #openstack-meeting-407:52
*** zeih has joined #openstack-meeting-407:53
*** shaohe_feng has quit IRC07:59
*** iberezovskiy has quit IRC08:00
*** degorenko has quit IRC08:00
*** shaohe_feng has joined #openstack-meeting-408:00
*** elisha_r has joined #openstack-meeting-408:00
elisha_r#startmeeting vitrage08:01
openstackMeeting started Wed Jun 29 08:01:17 2016 UTC and is due to finish in 60 minutes.  The chair is elisha_r. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
openstackThe meeting name has been set to 'vitrage'08:01
*** Wendy_ has joined #openstack-meeting-408:01
*** lhartal has joined #openstack-meeting-408:02
*** ohad has joined #openstack-meeting-408:02
*** ihrachys has joined #openstack-meeting-408:03
*** kashyap has left #openstack-meeting-408:03
*** degorenko has joined #openstack-meeting-408:03
*** degorenko has quit IRC08:04
*** spzala has joined #openstack-meeting-408:04
*** alexchadin has joined #openstack-meeting-408:05
lhartalhi :)08:06
*** nbloom has joined #openstack-meeting-408:06
elisha_rHi Everyone!08:06
*** eyalb has joined #openstack-meeting-408:07
elisha_rOur agenda today:08:07
eyalbhi08:07
elisha_rOPNFV summit updates08:07
*** degorenko has joined #openstack-meeting-408:07
elisha_rsorry... Our agenda today:08:08
elisha_r* OPNFV summit updates08:08
elisha_r* Status and updates08:08
elisha_r* Open Discussion08:08
*** idan_hefetz has joined #openstack-meeting-408:08
elisha_r#topic OPNFV summit updates08:08
*** openstack changes topic to "OPNFV summit updates (Meeting topic: vitrage)"08:08
idan_hefetzHi all08:09
elisha_rSo, we had a great summit. We had a booth there, demonstrating how Vitrage can implement the Inspector component of the OPNFV Doctor project08:10
*** spzala has quit IRC08:10
*** shaohe_feng has quit IRC08:10
*** iberezovskiy has joined #openstack-meeting-408:10
elisha_rWe had about 100+ people that came to hear about Vitrage08:10
*** shaohe_feng has joined #openstack-meeting-408:11
elisha_rMany people asked questions. Among other things, they were very interested in the UI, how templates are defined, and integration with other components08:11
elisha_rWe were also interviewed to TelecomTV. Will post the interview link here once it's published.08:12
*** zhurong has quit IRC08:12
*** emalin has joined #openstack-meeting-408:12
elisha_rAlso, we had meetings with a new OPNFV project called VES, which deals with VNF monitoring, and with collectd, a monitoring daemon which is part of DPDK.08:13
*** prazumovsky has joined #openstack-meeting-408:14
elisha_rOverall, we got very good feedback both from Doctor and the community as a whole.08:14
elisha_rThat's it.08:14
*** danoffek has joined #openstack-meeting-408:14
emalinvery nice08:15
*** thorst has joined #openstack-meeting-408:15
lhartalgrate news :)08:15
nbloomWell done, good job, keep up the good work!!!08:15
eyalb+108:15
lhartal+208:15
elisha_r#topic Status and updates08:16
*** openstack changes topic to "Status and updates (Meeting topic: vitrage)"08:16
*** zhurong has joined #openstack-meeting-408:18
lhartalI have an update08:18
lhartalLast week I added new ALP – vitrage template list08:18
lhartalALP = API :)08:18
lhartalIt list all templates loaded from /etc/vitrage/templates dir08:19
*** shaohe_feng has quit IRC08:20
*** shaohe_feng has joined #openstack-meeting-408:20
elisha_rnice!08:20
lhartalif template failed during loading, it will show an error status and a message with explanation08:21
danoffekNice. do we have any future plans for additional Templates related APIs ?08:22
lhartalplease be aware that from newton - the id field renamed to name08:23
*** thorst has quit IRC08:23
*** prazumovsky has left #openstack-meeting-408:23
lhartal@danoffek: yes. hopefully next week I will add new API: vitrage template show08:24
danoffekThanks08:24
lhartalIt will show the content of specific template08:24
lhartalDo you have a future wish for templates APIs?08:25
danoffekNot that I can think of now, thanks.08:26
lhartalgreat!! that's all08:27
danoffekI have a general idea about template generic editing VIA api, but not yet.08:27
elisha_rcool. Anyone else?08:27
elisha_rok08:27
*** iyamahat has quit IRC08:28
elisha_r#topic Open Discussion08:28
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:28
*** danoffek has left #openstack-meeting-408:28
elisha_rAnyone have a topic to discuss?08:28
*** iceyao has quit IRC08:28
lhartalI have updates for Vitrage UI08:29
*** wanghua has joined #openstack-meeting-408:29
lhartalcurrently, we want to improve the topology screen08:30
*** shaohe_feng has quit IRC08:30
lhartalwe going to add improvments to the sunburst itself08:30
*** iceyao has joined #openstack-meeting-408:30
*** shaohe_feng has joined #openstack-meeting-408:31
lhartallageng for the colors in the sunburst08:31
lhartallageng = legend08:31
*** GB21 has joined #openstack-meeting-408:31
lhartaland breadcrumb at the top of the screen08:32
lhartalto make it more simple to navigate08:32
lhartaland now we are working on improvements for the Entity Graph.. more updates in the next meeting08:34
elisha_rcool :)08:34
elisha_rI'll just update that we hope to make some changes soon to the names of the panels in the vitrage UI08:34
*** markvoelker has joined #openstack-meeting-408:34
elisha_rSpecifically, "Entities" will become "Entity Graph", while "Topology" (sunburst) will become "Hierarchies"08:35
elisha_rAny additional proposals are welcome08:35
elisha_roops - my mistake08:36
elisha_rmeant that the enitity graph will now become "Topology"08:36
elisha_rthats it08:36
elisha_ranyone else?08:36
*** sshnaidm has joined #openstack-meeting-408:36
elisha_rok, thanks everyone. bye08:37
lhartalread you next week :)08:37
elisha_r:)08:37
elisha_rbye08:37
elisha_r#endmeeting08:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:37
openstackMeeting ended Wed Jun 29 08:37:50 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-29-08.01.html08:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-29-08.01.txt08:37
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-06-29-08.01.log.html08:37
*** elisha_r has quit IRC08:37
*** ohad has quit IRC08:38
*** markvoelker has quit IRC08:38
*** zeih has quit IRC08:40
*** shaohe_feng has quit IRC08:40
*** shaohe_feng has joined #openstack-meeting-408:41
*** anilvenkata has joined #openstack-meeting-408:45
*** dshakhray_ has quit IRC08:46
*** shaohe_feng has quit IRC08:51
*** shaohe_feng has joined #openstack-meeting-408:51
*** alexstav has joined #openstack-meeting-408:55
*** alexchadin has quit IRC08:57
*** zhurong has quit IRC08:58
*** gongysh has joined #openstack-meeting-408:58
*** gzhai-mobl has joined #openstack-meeting-408:58
*** diga has joined #openstack-meeting-408:59
*** ostroverkhov has joined #openstack-meeting-408:59
*** ostroverkhov has quit IRC09:00
*** zhurong has joined #openstack-meeting-409:00
*** shaohe_feng has quit IRC09:01
*** shaohe_feng has joined #openstack-meeting-409:02
*** nbloom has quit IRC09:02
*** spzala has joined #openstack-meeting-409:06
gzhai-moblIs this watcher meeting now?09:06
*** tfukushima has quit IRC09:08
*** zeih has joined #openstack-meeting-409:10
*** spzala has quit IRC09:11
*** shaohe_feng has quit IRC09:11
*** shaohe_feng has joined #openstack-meeting-409:12
*** zeih has quit IRC09:15
*** alexchadin has joined #openstack-meeting-409:15
*** spzala has joined #openstack-meeting-409:16
*** yujunz has joined #openstack-meeting-409:16
*** iceyao has quit IRC09:17
*** zhurong has quit IRC09:20
*** spzala has quit IRC09:20
*** thorst has joined #openstack-meeting-409:20
*** shaohe_feng has quit IRC09:21
*** coolsvap has joined #openstack-meeting-409:24
*** shaohe_feng has joined #openstack-meeting-409:24
*** iceyao has joined #openstack-meeting-409:24
*** zeih has joined #openstack-meeting-409:26
*** gongysh has quit IRC09:27
*** thorst has quit IRC09:28
*** yujunz has quit IRC09:29
*** shaohe_feng has quit IRC09:32
*** xingchao has quit IRC09:32
*** shaohe_feng has joined #openstack-meeting-409:32
*** petergurinov has joined #openstack-meeting-409:33
*** xingchao has joined #openstack-meeting-409:33
*** GB21 has quit IRC09:35
*** amotoki has quit IRC09:37
*** shaohe_feng has quit IRC09:42
*** alexchadin has quit IRC09:42
*** alexchadin has joined #openstack-meeting-409:42
*** shaohe_feng has joined #openstack-meeting-409:43
*** eyalb has quit IRC09:47
*** vnogin_ has quit IRC09:50
*** salv-orlando has quit IRC09:50
*** amotoki has joined #openstack-meeting-409:50
*** ajmiller has quit IRC09:52
*** vikasc has quit IRC09:52
*** ajmiller has joined #openstack-meeting-409:52
*** shaohe_feng has quit IRC09:52
*** shaohe_feng has joined #openstack-meeting-409:52
*** GB21 has joined #openstack-meeting-409:53
*** vnogin has joined #openstack-meeting-409:55
*** _ody has quit IRC09:56
*** petergurinov has quit IRC09:57
*** shaohe_feng has quit IRC10:02
*** alexchadin has quit IRC10:03
*** shaohe_feng has joined #openstack-meeting-410:03
*** vikasc has joined #openstack-meeting-410:05
*** coolsvap has quit IRC10:07
*** coolsvap has joined #openstack-meeting-410:08
*** limao_ has quit IRC10:09
*** javeriak has quit IRC10:12
*** coolsvap has quit IRC10:13
*** shaohe_feng has quit IRC10:13
*** shaohe_feng has joined #openstack-meeting-410:13
*** spzala has joined #openstack-meeting-410:16
*** javeriak has joined #openstack-meeting-410:17
*** gzhai-mobl has quit IRC10:18
*** emalin has quit IRC10:18
*** spzala has quit IRC10:22
*** salv-orlando has joined #openstack-meeting-410:22
*** shaohe_feng has quit IRC10:23
*** amotoki has quit IRC10:23
*** thorst has joined #openstack-meeting-410:25
*** shaohe_feng has joined #openstack-meeting-410:26
*** salv-orlando has quit IRC10:27
*** dshakhray_ has joined #openstack-meeting-410:32
*** thorst has quit IRC10:33
*** amotoki has joined #openstack-meeting-410:33
*** shaohe_feng has quit IRC10:33
*** iceyao has quit IRC10:34
*** shaohe_feng has joined #openstack-meeting-410:36
*** markvoelker has joined #openstack-meeting-410:36
*** sambetts|afk is now known as sambetts|deadlin10:36
*** ajmiller has quit IRC10:37
*** ajmiller has joined #openstack-meeting-410:37
*** sambetts|deadlin is now known as sambetts|halfher10:38
*** GB21 has quit IRC10:38
*** sambetts|halfher is now known as sambetts|HAK10:38
*** sambetts|HAK is now known as sambetts|HFK10:38
*** markvoelker has quit IRC10:40
*** sambetts|HFK is now known as sam|schrodinger10:41
*** sam|schrodinger is now known as sambetts|cat10:42
*** shaohe_feng has quit IRC10:43
*** amotoki has quit IRC10:44
*** diga has quit IRC10:45
*** shaohe_feng has joined #openstack-meeting-410:46
*** zenoway has joined #openstack-meeting-410:47
*** GB21 has joined #openstack-meeting-410:48
*** coolsvap has joined #openstack-meeting-410:49
*** yamamot__ has quit IRC10:49
*** shaohe_feng has quit IRC10:54
*** shaohe_feng has joined #openstack-meeting-410:54
*** javeriak has quit IRC10:56
*** salv-orlando has joined #openstack-meeting-410:56
*** mfedosin has joined #openstack-meeting-410:58
*** salv-orl_ has joined #openstack-meeting-410:59
*** amotoki has joined #openstack-meeting-411:02
*** xingchao has quit IRC11:03
*** salv-orlando has quit IRC11:03
*** alexchadin has joined #openstack-meeting-411:04
*** shaohe_feng has quit IRC11:04
*** mfedosin has quit IRC11:04
*** shaohe_feng has joined #openstack-meeting-411:04
*** salv-orl_ has quit IRC11:05
*** xingchao has joined #openstack-meeting-411:05
*** xingchao_ has joined #openstack-meeting-411:06
*** xingchao has quit IRC11:07
*** alexchadin has quit IRC11:08
*** alexchadin has joined #openstack-meeting-411:10
*** shaohe_feng has quit IRC11:14
*** shaohe_feng has joined #openstack-meeting-411:15
*** spzala has joined #openstack-meeting-411:18
*** mfedosin has joined #openstack-meeting-411:18
*** spzala has quit IRC11:23
*** shaohe_feng has quit IRC11:24
*** shaohe_feng has joined #openstack-meeting-411:25
*** irenab has quit IRC11:29
*** v1k0d3n has joined #openstack-meeting-411:29
*** limao has joined #openstack-meeting-411:30
*** zeih has quit IRC11:30
*** zeih has joined #openstack-meeting-411:34
*** ddieterly has joined #openstack-meeting-411:34
*** shaohe_feng has quit IRC11:35
*** shaohe_feng has joined #openstack-meeting-411:35
*** zeih has quit IRC11:35
*** javeriak has joined #openstack-meeting-411:36
*** markvoelker has joined #openstack-meeting-411:37
*** limao has quit IRC11:37
*** zeih has joined #openstack-meeting-411:38
*** irenab has joined #openstack-meeting-411:40
*** markvoelker has quit IRC11:41
*** ddieterly has quit IRC11:41
*** thorst has joined #openstack-meeting-411:42
*** zeih has quit IRC11:43
*** amotoki has quit IRC11:44
*** alexstav has quit IRC11:45
*** alexchadin has quit IRC11:45
*** shaohe_feng has quit IRC11:45
*** alexchadin has joined #openstack-meeting-411:45
*** shaohe_feng has joined #openstack-meeting-411:45
*** zeih has joined #openstack-meeting-411:46
*** numans has quit IRC11:48
*** ddieterly has joined #openstack-meeting-411:50
*** shaohe_feng has quit IRC11:55
*** shaohe_feng has joined #openstack-meeting-411:56
*** banix has joined #openstack-meeting-411:57
*** yamamoto has joined #openstack-meeting-411:57
*** alexchadin has quit IRC11:58
*** alexchadin has joined #openstack-meeting-411:59
*** banix has quit IRC12:03
*** shaohe_feng has quit IRC12:05
*** shaohe_feng has joined #openstack-meeting-412:06
*** ddieterly has quit IRC12:07
*** zeih has quit IRC12:07
*** markvoelker has joined #openstack-meeting-412:08
*** hvprash has joined #openstack-meeting-412:08
*** GB21 has quit IRC12:08
*** baoli has joined #openstack-meeting-412:10
*** salv-orlando has joined #openstack-meeting-412:10
*** GB21 has joined #openstack-meeting-412:11
*** hvprash_ has joined #openstack-meeting-412:12
*** vishwanathj has joined #openstack-meeting-412:13
*** vikasc has quit IRC12:13
*** salv-orlando has quit IRC12:14
*** hvprash has quit IRC12:15
*** xingchao_ has quit IRC12:16
*** shaohe_feng has quit IRC12:16
*** shaohe_feng has joined #openstack-meeting-412:17
*** spzala has joined #openstack-meeting-412:19
*** hvprash_ has quit IRC12:20
*** spzala has quit IRC12:24
*** ovobora has joined #openstack-meeting-412:25
*** shaohe_feng has quit IRC12:26
*** baoli has quit IRC12:26
*** alexchadin has quit IRC12:26
*** shaohe_feng has joined #openstack-meeting-412:27
*** iceyao has joined #openstack-meeting-412:28
*** ddieterly has joined #openstack-meeting-412:30
*** baoli has joined #openstack-meeting-412:30
*** baoli has quit IRC12:35
*** v1k0d3n has quit IRC12:35
*** zenoway has quit IRC12:35
*** woodard has joined #openstack-meeting-412:36
*** shaohe_feng has quit IRC12:36
*** vishwanathj has quit IRC12:37
*** shaohe_feng has joined #openstack-meeting-412:37
*** salv-orlando has joined #openstack-meeting-412:39
*** ddieterly is now known as ddieterly[away]12:41
*** hvprash has joined #openstack-meeting-412:46
*** zenoway has joined #openstack-meeting-412:46
*** ovobora has quit IRC12:46
*** salv-orlando has quit IRC12:46
*** shaohe_feng has quit IRC12:46
*** shaohe_feng has joined #openstack-meeting-412:47
*** salv-orlando has joined #openstack-meeting-412:48
*** gongysh has joined #openstack-meeting-412:48
*** dkehn is now known as dkehn_12:49
*** idan_hefetz has left #openstack-meeting-412:50
*** yuli_s has quit IRC12:51
*** alexchadin has joined #openstack-meeting-412:51
*** bobh has joined #openstack-meeting-412:52
*** hvprash has quit IRC12:55
*** hvprash has joined #openstack-meeting-412:55
*** alexchadin has quit IRC12:56
*** shaohe_feng has quit IRC12:57
*** shaohe_feng has joined #openstack-meeting-412:57
*** gmann has joined #openstack-meeting-412:57
*** hvprash has quit IRC12:59
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Jun 29 13:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today for Nova API?13:00
Kevin_Zhengo/13:00
gmanno/13:00
*** alaski has joined #openstack-meeting-413:01
alex_xuvery quiet today, US have holiday recently?13:01
gmannhummm13:02
alaskino, but there's one coming up next monday13:02
*** GB21 has quit IRC13:02
*** zenoway has quit IRC13:02
alex_xualaski: so next week will more quiet than today :)13:03
alex_xuanyway, let's running the meeting13:03
alaskivery likely :)13:03
alex_xuwe didn't have action from previous meeting13:03
alex_xu#topic API priorities13:03
*** openstack changes topic to "API priorities (Meeting topic: nova api)"13:03
alex_xufor policy discovery, we have a bunch of patches waiting for review13:03
alex_xualaski: any important update on that?13:04
*** bobh has quit IRC13:04
alaskithe patches are merging, but there are still a few up13:04
alaskiit's looking pretty good for completing13:04
alaskithat's all13:04
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-in-code13:04
*** pmesserli has joined #openstack-meeting-413:04
alex_xuwow, most of them are merged13:04
*** woodster_ has joined #openstack-meeting-413:05
alex_xualaski: i guess the last thing is the cmd for policy discovery, right?13:05
gmannalaski: there will be policy generator tox env right, which merge the existing policy file with default one ?13:05
alaskiyeah, we have been pushing last week and this week13:05
alaskialex_xu: that, and what gmann just mentioned13:05
alex_xualaski: gmann cool13:05
gmannnice13:06
alaskiI think claudiub had a patch up for the discovery cmd13:06
alex_xugood progress at here13:06
alex_xufor api ref13:06
alaskihttps://review.openstack.org/#/c/322944/ for reference13:06
*** banix has joined #openstack-meeting-413:06
* edleafe comes in late13:06
woodster_o/13:06
alex_xualaski: thanks13:07
gmannalaski: thanks, ll check tomorrow morning.13:07
*** shaohe_feng has quit IRC13:07
alex_xufor api-ref, i didn't see any news, except a set of patch waiting for review13:07
gmannalex_xu: yea, little bit slow progress we have on those.13:08
*** shaohe_feng has joined #openstack-meeting-413:08
gmannalex_xu: if you can look this one  - https://review.openstack.org/#/c/326975/13:08
gmannalex_xu: I will start giving some time on those next week may be13:08
alex_xugmann: will try to reach that asap13:08
gmannalex_xu: Thanks :)13:09
alex_xu we have hackathon in China next week, i may spend some time on that also13:09
alex_xugmann: np13:09
alex_xufor proxy api deprecation, i have a set of patches up at here13:09
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/deprecate-api-proxies13:10
gmannalex_xu: cool, can you get more developer on that in hackathon?13:10
alex_xugmann: i will try that, hope i can attract some developers13:10
Kevin_Zhengi will join13:10
gmann+113:10
alex_xuKevin_Zheng: you are cool :)13:11
*** spzala has joined #openstack-meeting-413:11
*** ihrachys has quit IRC13:11
*** banix has quit IRC13:11
alex_xuAll the patches for proxy api deprecation at here13:11
alex_xubut it needs a rebase13:11
*** mriedem has joined #openstack-meeting-413:12
*** automagically has joined #openstack-meeting-413:12
*** njohnston|sleep is now known as njohnston13:12
* mriedem joins late13:12
gmannalex_xu: Thanks. ll look into those13:12
alex_xubut I want to leave a space for non-priority features, so rebase after tomorrow, and hope people take a look at those patches are good for merge together or not13:12
alex_xugmann: thanks13:12
*** automagically has left #openstack-meeting-413:12
johnthetubaguyalex_xu: gmann: I mean to say, I hope OSIC folks can get back on that api-ref stuff post feature freeze13:13
*** ihrachys has joined #openstack-meeting-413:13
alex_xujohnthetubaguy: cool :)13:13
gmannjohnthetubaguy: very nice.13:13
*** javeriak has quit IRC13:14
alex_xujohnthetubaguy: mriedem the patch for proxy deprecation are on the gerrit, hope you guys can take a look at, then we find a time later or next week to merge them all13:14
johnthetubaguyyeah, feels like we sneak that in post freeze?13:15
alex_xujohnthetubaguy: yea13:15
mriedem+1 on that13:16
mriedemi don't want that to go too long though13:16
alex_xuthe last for api prorities is extension deprecation, but sdague isn't here. most of activity patches are merged looks like.13:17
alex_xumriedem: cool13:17
*** sdake has joined #openstack-meeting-413:17
*** shaohe_feng has quit IRC13:17
alex_xui think we can check with sdague about extension deprecation when he is back13:17
mriedemextension deprecation or folding?13:17
*** hvprash has joined #openstack-meeting-413:17
alex_xumriedem: they are on some bp?13:18
*** shaohe_feng has joined #openstack-meeting-413:18
alex_xus/some/same/13:18
mriedemi think so yeah13:18
alex_xufor now, it should be folding13:18
johnthetubaguyI think the spec deferred some bits of it to ocata, which seemed about right13:18
mriedemsort of related, https://review.openstack.org/#/c/334053/ needs to be cleaned up13:19
alex_xujohnthetubaguy: yea, right13:19
mriedemi could do it, or it could wait for friday13:19
*** yujunz has joined #openstack-meeting-413:19
johnthetubaguymriedem: are we doing a python-novaclient release soon?13:19
mriedemjohnthetubaguy: we just did one to get tags support out13:20
mriedem2 weeks ago13:20
mriedemwe'd do a release after ^ though13:20
gmannmriedem: we need proxy API deprecation also on client side right?13:20
mriedemandreykurilin has some things he wants to release for deprecations too13:20
johnthetubaguyright, I was wondering if we were holding that up13:20
mriedemproxy api deprecation in the client, we were going to discuss at the summit13:20
mriedems/summit/meetup/13:20
gmannok13:20
johnthetubaguymakes sense13:20
alex_xuok13:20
mriedemthere are some notes in the etherpad on that https://etherpad.openstack.org/p/nova-newton-midcycle13:21
mriedemL2413:21
gmannmriedem: nice, Thanks.13:21
gmannI will try to attend if get budget from company13:21
alex_xucool13:22
*** sdake_ has joined #openstack-meeting-413:22
*** sdake has quit IRC13:22
alex_xulooks good at here, so any more question on api priorities? if not, let's move on13:22
alex_xui guess the answer is let's move on13:24
alex_xu#topic open13:24
*** openstack changes topic to "open (Meeting topic: nova api)"13:24
alex_xu#link https://review.openstack.org/#/c/305369/13:24
alex_xualaski: your turn13:24
*** ddieterly has joined #openstack-meeting-413:24
alaskiI wanted to bring that up to get the reaction to versioning responses13:25
alaskiI wasn't sure if that was a level Nova was planning to get to13:25
mriedemwha13:26
alex_xuat least for now, we can implement different repsonse code with write another new method13:26
*** sdake has joined #openstack-meeting-413:26
johnthetubaguyyeah, I think we have done that be adding new methods, actually maybe we haven't done that much yet13:27
alaskisorry, should have been more specific. response codes, not just reponses13:27
alex_xuso we didn't have very strong requirement for that decorator13:27
*** sdake_ has quit IRC13:27
*** anilvenkata has quit IRC13:27
mriedemright what alex_xu said13:27
alaskiokay13:27
alaskiso that's one aspect, the decorator isn't needed13:27
mriedemwe also have separate versioned methods for the expected_errors decorator also13:27
*** shaohe_feng has quit IRC13:27
*** mbound has joined #openstack-meeting-413:28
alaskiso we do actually microversion response code changes? I wasn't sure on that13:28
alaskiI mean I wasn't sure we made those changes13:28
johnthetubaguyI think the rules say we have to for success codes, or new error codes?13:28
alex_xuyes, we do13:28
gmannyea, we did for keypair but along with other changes13:28
alaskiokay, cool13:29
mriedemsame for hypervisors https://review.openstack.org/#/c/326940/16/nova/api/openstack/compute/hypervisors.py13:29
mriedemi posted a comment in the change13:29
alaskithanks13:29
alaskithat was it13:29
mriedemi'd prefer we are being explicit about the stuff we do within the methods themselves13:29
johnthetubaguy#link http://docs.openstack.org/developer/nova/api_microversion_dev.html#when-do-i-need-a-new-microversion13:30
mriedemrather than magically version a response in a decorator13:30
*** shaohe_feng has joined #openstack-meeting-413:30
alex_xumriedem: +113:30
johnthetubaguy+1 on explicit, where practical13:30
gmann+1, much readable/debugable also13:30
edleafeusing a decorator for this seems slick, so probably not a good idea13:31
alex_xuyea13:31
mriedemok, i left a -113:31
alaskiagreed on explicit. I haven't reviewed much of the API changes though which is why I wanted to ask about that review13:31
alex_xuif no more question, let's go next item13:31
*** oomichi_ has joined #openstack-meeting-413:32
mriedemalaski: cdent would probably throw this into a nova-ism for wonky confusing magic wsgi13:32
edleafemriedem: heh13:32
mriedemi don't disagree though13:32
alaskitrue13:32
*** zeih has joined #openstack-meeting-413:32
*** cleong has joined #openstack-meeting-413:33
alex_xu#link https://review.openstack.org/#/c/326326/13:33
alex_xuKevin_Zheng: your turn13:33
Kevin_Zhengthanks13:33
Kevin_ZhengI was working on add pagination and timestamp filter for os-instance-actions13:34
Kevin_Zhengalex suggested that for timestamp filter we should use updated_at instead of created_at13:34
Kevin_Zhengwhich is good13:35
Kevin_Zhengbut currently this field is mostly empty13:35
Kevin_Zhengexcept error occors13:35
mriedemsort by updated_at first, created_at second?13:36
Kevin_Zhengshould we sync updated_at to created_at when it is created?13:36
mriedemwe don't do that for anything else13:36
mriedemso that would be odd13:36
alex_xuthat is due to the new event added to instance-action, the new event is separated db record, so the update_at of instance-action won't update13:36
Kevin_Zhengand also, we only called record_action start13:36
Kevin_Zhengrecord_action_finish has never been called13:36
alex_xuactually we can sort with updated_at first, then created_at13:37
mriedemhrm13:37
mriedemwhen we create a new instance action event, we could bump the updated_at on the parent instance action13:37
mriedemjust a thought13:37
alex_xumriedem: yea13:37
Kevin_Zhengyes13:37
*** shaohe_feng has quit IRC13:38
Kevin_Zhengso shoud we do it in a separate patch?13:38
Kevin_Zhengas bug?13:38
*** shaohe_feng has joined #openstack-meeting-413:38
mriedemthat seems like a decent separate bug fix13:39
Kevin_ZhengOK then13:39
*** zeih has quit IRC13:39
*** hdaniel has quit IRC13:39
mriedemalaski: any issues with that?13:39
mriedemyou're the action event guy13:39
alaskifrom a mechanical pov no, that seems fine13:40
alaskibut because events are exposed that might be weird from a ux pov13:40
alaskiare not*13:40
mriedemthey are13:40
mriedeminstance action details13:40
mriedemdoffm had to deal with it i think13:40
alaskionly for admins, at least by default13:40
*** ddieterly is now known as ddieterly[away]13:40
alex_xuso do we still need sync create_at and updated_at? or just sort updated_at first then created_at13:40
mriedemhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/instance_actions.py#L8813:41
alaskimriedem: line 8513:41
Kevin_ZhengI think if we want to show updated_at in the response, we have to sync13:41
mriedemalaski: yeah13:41
Kevin_Zhengotherwise updated_at will be empty13:41
mriedemi'm just wondering if ordering by updated_at,created_at will look weird13:42
alex_xuKevin_Zheng: we need expose that, otherwise user didn't know how to fill the marker parameter13:42
Kevin_Zhengalex_xu: then I suggest we sync that, looks like other projects do that, like heat13:42
alaskiI'm on the side of setting updated_at when creating the action13:43
mriedemi think that's weird13:43
mriedemit's a hack for our sorting, which we otherwise wouldn't do13:44
edleafemriedem: what if it was named 'last_touched'?13:44
*** alexchadin has joined #openstack-meeting-413:44
mriedemgross13:44
alaskiI've always thought we should do it generally13:44
alaskiif we're not going to do that then basing it off of action-events is the next best thing I think13:44
mriedemalaski: as in updating updated_at on the instance action when creating an event for that action?13:45
alaskimriedem: yes13:45
mriedemmaybe this is a ML item13:46
* mriedem wishes sdague were here for sage advice13:46
alaskiit's on the ML13:46
mriedemtouche13:46
alex_xui think sync create_at and update_at are not just for this patch, it is about all the db model. How about sort updated_at,create_at first. Then discuss create_at and update_at later.13:46
alaskihttp://lists.openstack.org/pipermail/openstack-dev/2016-June/098299.html13:46
* alaski also misses sdague here13:47
mriedemi'm trying to think of other parent/child resources like this where we'd update updated_at when changing the child13:47
alex_xuemm...I wish another adivce from sdague for next page also :(13:47
mriedemlike instance group member and instance group13:47
*** shaohe_feng has quit IRC13:48
mriedemi need to read the ML and digest there really13:48
mriedemjust got online13:48
*** shaohe_feng has joined #openstack-meeting-413:48
*** xarses has quit IRC13:48
alaskiyeah, I don't think we do this anywhere else13:48
alaskialex_xu: I agree that this is a more general thing than just instance actions, syncing updated/created13:50
alaskiI'm not sure I understand sorting by updated_at, created_at though. Is updated_at ever set?13:50
alex_xualaski: yea13:50
alex_xuin the beginning, it is not. it will better after Kevin_Zheng fix the sync of action-event's updated_at to action's update_at13:51
mriedemhttps://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L596813:51
mriedem^ action finish updates the action13:52
Kevin_Zhengyes but this has never been called by any API13:52
alaskiyeah, it's not used yet13:52
alex_xuwhy that isn't used?13:53
alaskibecause it's not trivial to determine when an action is finished13:53
*** diga has joined #openstack-meeting-413:53
alaskiso it hasn't happened yet13:53
alaskithere's a proposed, but not approved, spec to do it13:53
*** hanrong1 has joined #openstack-meeting-413:53
mriedemis that the backlog spec on tasks?13:54
alaskimy only real concern with basing it off of action-event syncing is that every action needs at least one event then13:54
alaskimriedem: fortunately not, it's specifically about instance-actions13:54
*** raddaoui has joined #openstack-meeting-413:54
alaskihttps://review.openstack.org/#/c/256743/ I think13:55
mriedemi'm not sure why every action would require at least one event13:55
*** ddieterly[away] is now known as ddieterly13:55
mriedemyou create the action, you create the event + update the parent action13:55
alaskiotherwise updated_at wouldn't ever get set13:55
mriedemthat's fine if we order by updated_at,created_at13:55
alaskiyeah, if created_at is included that works13:56
* alex_xu reminds 4 mins left13:56
mriedemwe've got 4 minutes left13:56
mriedemyeah :)13:56
alaskimaybe it was https://review.openstack.org/#/c/248248/ I was thinking of13:56
mriedemhow about we table this for now, and move it to the ML13:56
alaski+113:56
Kevin_Zhengsure13:56
alex_xu+113:56
Kevin_ZhengThanks alto13:56
Kevin_Zhengalot13:57
alex_xuok, if no more question, let's close the meeting13:57
*** tsufiev has joined #openstack-meeting-413:57
gmann1 have one.13:57
gmann#link https://review.openstack.org/#/c/335349/213:57
gmannjohnthetubaguy: alex_xu i agree we need version bump here13:57
gmannbut m thinking it is worth to bump version for this?13:58
alex_xugmann: yes, i guess not13:58
gmannor we leave that as it is and do if someone really complain13:58
*** shaohe_feng has quit IRC13:58
alex_xuso keep it as for now13:58
gmannbecause only cinder is user13:58
alex_xugmann: yea, i prefer that13:58
gmannalex_xu: ok, cool13:58
alex_xuok, we have to close the meeting now13:59
*** shaohe_feng has joined #openstack-meeting-413:59
alex_xuthanks all!13:59
alex_xu#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Wed Jun 29 13:59:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-29-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-29-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-06-29-13.00.log.html13:59
gmannThanks13:59
mriedemi'm not sure i agree with not bumping the version on a response change, regardless of the user13:59
alaskiKevin_Zheng: alex_xu mriedem just for the record I'm fine either way on the instance-actions thing, though I do have my preference.14:00
*** jinquan1 has joined #openstack-meeting-414:00
acabot#startmeeting watcher14:01
openstackMeeting started Wed Jun 29 14:01:22 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
acabothi14:01
sballe_o/14:01
*** gzhai2 has joined #openstack-meeting-414:01
*** tsufiev has left #openstack-meeting-414:01
jinquan1hi14:01
digahi14:01
gzhai2hi14:01
acabotagenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#06.2F29.2F201614:01
hanrong1hi14:01
*** yamamoto has quit IRC14:02
jed56hi14:02
dtardivelhi14:02
*** vincentfrancoise has joined #openstack-meeting-414:02
edleafe\o14:02
vincentfrancoiseo/14:02
hvprashhi14:02
tkaczynskihi14:02
*** v1k0d3n has joined #openstack-meeting-414:02
acabot#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:02
*** hdaniel has joined #openstack-meeting-414:02
sballe_One more person joined the meetup: Digambar Patil14:03
*** michaelgugino has joined #openstack-meeting-414:03
jed56welcome14:03
acabotwelcome Digambar14:03
jinquan1+114:03
gzhai2welcome14:03
sballe_+114:03
hvprashwelcome14:03
acabotworking for Intel ?14:03
sballe_no14:04
vincentfrancoisewelcome14:04
sballe_I am assuming it is diga14:04
sballe_diga: who are you working for?14:04
digathanks acabot14:04
digaPersistent14:04
sballe_cool!14:04
digasballe_: My name is Digambar14:04
diga:)14:04
acabotthx for the intro14:05
digaThank you all14:05
sballe_diga: Yes i know. I was refering to your IRC nickname14:05
*** vishnoianil has quit IRC14:05
digasballe_: yep :)14:05
acabot#info Watcher packages are available for Red Hat & Debian14:05
gzhai2Good news!14:06
*** zenoway has joined #openstack-meeting-414:06
acabotso danpawlik working on puppet packaging managed to have watcher packages for RDO & Debian (experimental)14:06
michaelguginowhere are the packages being hosted?14:06
acabotshould we update our user doc to mention these packages ?14:06
acabotmichaelgugino : https://packages.debian.org/experimental/python-watcherclient for deban14:07
vincentfrancoiseacabot: I would say yes14:07
vincentfrancoisewe currently have a "Installing from Source" and a "Installing from packages: PyPI"14:07
*** gmann has quit IRC14:07
jed56+114:08
acabotok lets create a a new section for it14:08
vincentfrancoiseso that would seem kind of logic to add a "Installing from packages: Debian" and so son14:08
sballe_+114:08
vincentfrancoises/son/on14:08
acabot#action vincentfrancoise add a section "installing from packages" in user guide14:08
gzhai2Do we need check debian/redhat doc for watcher?14:08
*** shaohe_feng has quit IRC14:08
acabotgzhai2 : what do you mean ?14:09
gzhai2debian/redhat should have their own openstack doc.14:09
jed56gzhai2: yes it a good idea to check the doc with the packages14:09
gzhai2install from rpm, and how to config it.14:09
*** shaohe_feng has joined #openstack-meeting-414:09
acabotanyone wants to test packages ?14:10
sballe_what version of RDO and debian is Watcher included in?14:10
dtardivelacabot: I can test Debian ones14:10
*** alexstav has joined #openstack-meeting-414:10
acabotsballe_ : its not included...its available14:10
*** alaski has left #openstack-meeting-414:10
jed560.2714:10
*** zeih has joined #openstack-meeting-414:11
acabot#action dtardivel test Watcher debian packages and update the install doc if needed14:11
jed560.26 sorry14:11
gzhai2I can try redhat14:11
acabotactually I since Debian has 0.27 & RDO 0.26 :-)14:11
dtardiveljed56: watcher : python-watcher (0.27.0-2)14:11
jed56ah yes :p14:11
acabotyes this is because RDO wants final release so 0.2614:12
*** oomichi_ has quit IRC14:12
*** ddieterly is now known as ddieterly[away]14:12
acabot#info 2 weeks away from submission deadline, please register as speakers in , we also need to complete descriptions14:12
*** tonytan4ever has joined #openstack-meeting-414:12
acabot#link https://etherpad.openstack.org/p/Watcher_abstracts_barcelona201614:12
sballe_acabot: I will work on the abstracts this week.14:12
acabotI would like to have 3 speakers for each presentation14:13
sballe_+114:13
hvprashthx for reminding. will update it14:13
acabot#action sballe_ work on the abstracts for Barcelona summit14:13
sballe_https://etherpad.openstack.org/p/Watcher_abstracts_barcelona201614:13
acabotsballe_ : thx14:13
*** mbound has quit IRC14:13
acabotdont forget that if the presentation is accepted, every speaker will get a free pass ;-)14:14
*** iyamahat has joined #openstack-meeting-414:14
acabot#info a first draft of mid-cycle agenda is available14:14
*** xingchao has joined #openstack-meeting-414:14
acabot#link https://etherpad.openstack.org/p/newton-watcher-midcycle14:14
acabotfeel free to add topics you would like to discuss14:15
edleafeacabot: Did Watcher contributors not get ATC passes?14:15
acabotthere is still a lot of space in the agenda14:15
acabotedleafe : actually yes14:15
*** breton_ is now known as breton14:15
acabotedleafe : some of them at least14:15
jed56edleafe: yes14:16
*** sdake has quit IRC14:16
*** padkrish has joined #openstack-meeting-414:16
jed56we have14:16
edleafeOK, good. That's one of the benefits of being in the big tent :)14:16
jed56edleafe: +114:16
sballe_+114:16
acabotedleafe : yes it is but to my understanting, it was related to the previous cycle...14:16
*** jmckind has joined #openstack-meeting-414:16
edleafePrevious, and current up to the date they send out the ATC codes14:17
acabotedleafe : ok14:17
acabot#info Watcher should respect the Nova policies spec has been discussed with the Nova scheduler team14:17
edleafeSince Watcher was in before then, I figured you should be good14:17
*** uxdanielle has joined #openstack-meeting-414:17
*** sdake has joined #openstack-meeting-414:17
*** sdake has quit IRC14:17
*** vishnoianil has joined #openstack-meeting-414:17
acabot#link https://review.openstack.org/#/c/329873/14:17
*** zenoway has quit IRC14:17
acabotedleafe : thx Ed for adding it to the agenda14:18
acabot#link http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-06-27-14.00.log.html14:18
*** padkrish_ has joined #openstack-meeting-414:18
michaelguginoI have already received ATC from other projects, fyi14:18
acabotas next steps, bauzas suggests that we drop a line about watcher in Nova mid-cycle agenda #link https://etherpad.openstack.org/p/newton-nova-scheduler14:18
michaelguginofor this cycle, I mean.14:18
*** shaohe_feng has quit IRC14:19
sballe_acabot: +114:19
edleafeacabot: yes, this will certainly be discussed at the midcycle14:19
acabotand we submit a backlog spec #link http://specs.openstack.org/openstack/nova-specs/specs/backlog/14:19
*** klamath has joined #openstack-meeting-414:19
*** shaohe_feng has joined #openstack-meeting-414:19
acabotto explain our problem14:19
*** sdake has joined #openstack-meeting-414:19
edleafeNo schedule is set yet, but when it is, it would probably be a good time to come join us14:20
edleafesince we'll be in the same building14:20
edleafe:)14:20
acabotedleafe : do you think having a backlog spec on Nova side is a good way to progress ?14:20
*** ddieterly[away] is now known as ddieterly14:20
edleafeSure - it will give people some background14:20
acabotok14:20
jed56ok14:21
*** padkrish has quit IRC14:21
acabot#action jed56 acabot submit a backlog spec for Nova regarding policies management in Watcher14:21
acabotany other announcement ?14:21
acabot#topic Review Action Items14:21
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:22
acabotUpdate the continuously optimization spec needs reviews from core as its already implemented14:22
acabot#link https://review.openstack.org/#/c/330021/14:22
acabotsballe_ : can you look at it and W+1 ?14:22
sballe_yes14:22
acabot#action sballe_ review https://review.openstack.org/#/c/330021/14:22
acabotCluster model objects wrapper needs reviews from core14:23
acabot#link https://review.openstack.org/#/c/287019/14:23
*** sc68cal has quit IRC14:23
sballe_ok add me to this one too14:23
acabot#action sballe_ jwcroppe review https://review.openstack.org/#/c/287019/14:23
acabotGraph model describing virtual and physical elements in a data center & Consolidation of multiple Action-plans into a single one need reviews14:23
acabot#link https://review.openstack.org/#/c/298891/14:23
acabot#link https://review.openstack.org/#/c/298871/14:24
*** spotz_zzz is now known as spotz14:24
acabotsballe_ : we have to discuss about the implementation of these specs from Intel14:24
*** sogabe has joined #openstack-meeting-414:24
sballe_I'll review those too since I am preparing a talk about Intel's contribution to Watcher14:24
acabotsballe_ : I will add it to midcycle agenda14:24
sballe_make sense. the person implementing them will be at the mid-cycle14:25
acabot#action sballe_ review https://review.openstack.org/#/c/298891/ & https://review.openstack.org/#/c/298871/14:25
sballe_and so will Thijs14:25
acabotsballe_ : great ;-)14:25
*** sc68cal has joined #openstack-meeting-414:25
jed56I'm starting to review 29887114:25
acabotmoving to Watcher14:25
acabot#action jed56 review https://review.openstack.org/#/c/298871/14:25
acabotEnable strategy parameters is in progress, test feedback requested14:26
acabot#link https://review.openstack.org/#/c/297556/14:26
*** nkrinner is now known as nkrinner_afk14:26
acabotvincentfrancoise : I think you are still testing it dont you ?14:26
*** pkoniszewski has quit IRC14:26
vincentfrancoiseacabot: actually it was more dtardivel who was doing the testing on this14:26
dtardivelacabot: I tested it on devstack as well14:27
gzhai2dtardivel: any issue?14:27
dtardivelno, except data output format on console. Please see the last review14:27
acabot#action gzhai2 add a new PS to https://review.openstack.org/#/c/297556/14:28
acabotAdd continuously optimization needs reviews from core14:28
*** pkoniszewski has joined #openstack-meeting-414:28
acabot#link https://review.openstack.org/#/c/321411/14:28
acabotI this this has been reviewed and so can be merged asap14:28
acabots/this/think14:28
acabotalong with the spec :-D14:29
*** shaohe_feng has quit IRC14:29
acabotAdd scoring engines to database and API layers needs reviews14:29
jed56acabot: IMHO, we will be able to merged it soon14:29
acabot#link https://review.openstack.org/#/c/330382/14:29
*** xarses has joined #openstack-meeting-414:30
jed56you can add me14:30
vincentfrancoiseI did some reviews on this one14:30
acabottkaczynski : you just submited a new PS, still waiting for reviews I suppose14:30
*** shaohe_feng has joined #openstack-meeting-414:30
acabot#action jed56 review https://review.openstack.org/#/c/330382/14:30
sballe_add me 214:30
acabot#action sballe_ review https://review.openstack.org/#/c/330382/14:30
tkaczynskiI think I need to add some tests before it can be made +214:31
acabottkaczynski : ok14:31
acabotdo you know your current coverage ?14:31
*** amotoki has joined #openstack-meeting-414:31
tkaczynskiI will try to do this this week, so we can close that. Vincent sent me the coverage. can I get that locally too?14:31
vincentfrancoisetkaczynski: yes14:32
jed56tkaczynski:  tox -e cover14:32
tkaczynskigreat, thanks14:32
acabot#action tkaczynski add tests for https://review.openstack.org/#/c/330382/14:32
acabotAdd policies for API access control to watcher project needs reviews14:32
acabot#link https://review.openstack.org/#/c/334163/14:32
jed56we should add a new rule in the gate each new patchset have to improve the code coverage :p14:32
sballe_+114:33
acabothanrong1 : thx for this 1st contribution to watcher !14:33
acabothanrong1 : you also need to add tests ;-)14:33
vincentfrancoisejed56: I tried to find some coverage ratcheting jobs but there was none14:34
*** syjulian has joined #openstack-meeting-414:34
acabotAdd rally-jobs folder to get rally support needs new tests14:34
jed56vincentfrancoise: okay :)14:34
acabot#link https://review.openstack.org/#/c/333371/14:34
acabota lot of tests missing today !14:34
dtardivelacabot: yes I asked to hanrong1 to push a new pachset on watcher-dasboard which is able to handle watcher policies14:35
*** vishnoianil has quit IRC14:35
hanrong1acabot:  Thank you for all help14:35
acabot#action hanrong1 submit a new PS on watcher-dashboard to handle policies14:35
tkaczynskithanks guys for my reviews too! :)14:35
hanrong1 hanrong1: I will submit a new patch set for tests.14:36
acabot#action hanrong1 submit a new patch set for tests on https://review.openstack.org/#/c/334163/14:36
acabotEnable strategy parameter needs a new PS14:36
acabot#link https://review.openstack.org/#/c/29755714:36
acabot#action gzhai2 submit a new PS for https://review.openstack.org/#/c/29755714:37
acabotAdd scoring engine commands needs reviews14:37
acabot#link https://review.openstack.org/#/c/330385/14:37
acabot#action jed56 sballe_ review https://review.openstack.org/#/c/330385/14:37
acabotsame reviewers for the CLI ;-)14:38
acabotAdd support continuously-optimization needs a new PS14:38
*** amotoki has quit IRC14:38
acabot#link https://review.openstack.org/#/c/327095/14:38
acabotanyone know the IRC nick for Vladimir ?14:39
acabotdtardivel : can you review https://review.openstack.org/#/c/327095/ as you will be working on the dashboard ?14:39
*** shaohe_feng has quit IRC14:39
*** shaohe_feng has joined #openstack-meeting-414:39
dtardivelacabot: yes of course14:40
vincentfrancoiseacabot: he's not connected but that was something like ostroverkhov14:40
acabot#action dtardivel review https://review.openstack.org/#/c/327095/14:40
acabotvincentfrancoise : an easy one ;-)14:40
acabotI forgot to mention WIP around https://review.openstack.org/#/q/topic:bp/persistent-audit-parameters14:41
acabothvprash michaelgugino : are you waiting for reviews on your code ?14:42
hvprashacabot, yeah its in progress. hoping for review next week :)14:42
hvprashwe are not yet done14:42
acabothvprash : ok thx14:42
michaelguginono, I'm not.  There are some good reviews already, I am going to work on the patch this week14:42
acabotgreat14:42
acabot#topic Blueprint/Bug Review and Discussion14:42
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:42
acabot#info our current milestone is Newton-2  (due July 11th)14:43
acabot#link https://launchpad.net/watcher/+milestone/newton-214:43
*** yamamoto has joined #openstack-meeting-414:43
*** petergurinov has joined #openstack-meeting-414:43
*** armax has joined #openstack-meeting-414:43
acabotas we are 2 weeks away from the release, we need to focus on code reviewing and bug fixes14:43
acabotwe should probably postpone to Newton-3 https://blueprints.launchpad.net/watcher/+spec/persistent-audit-parameters14:44
acabotand https://blueprints.launchpad.net/watcher/+spec/cluster-model-objects-wrapper14:44
acabottkaczynski : what about https://blueprints.launchpad.net/watcher/+spec/scoring-module ?14:45
acabothvprash : what do you think about your BP ?14:45
hvprashI need to add more details on our use case14:45
hvprashthen we could discuss14:46
vincentfrancoiseacabot: does that mean we shouldn't accept any pending changeset from these BPs?14:46
*** amotoki has joined #openstack-meeting-414:46
vincentfrancoisebecause the 1st part of my BP could be merged before then I believe14:46
acabotvincentfrancoise : no the idea is to focus our effort on completing BPs14:46
hvprashacabot, assuming you are asking about this https://blueprints.launchpad.net/watcher/+spec/workload-prioritization-qos14:46
tkaczynskiacabot: I'm working on it and making progress. will have code for review soon, maybe next week?14:46
acabothvprash : this one will be discussed during the mid-cycle as its a 'large-scope" BP14:47
hvprashyes14:47
acabottkaczynski : ok as the freeze will be end of next week, I dont think we will be able to have it in this release14:48
tkaczynskiacabot: strictly speaking probably not, but soon after. is that okay?14:48
*** lhartal has quit IRC14:49
acabotvincentfrancoise : we will merge Part 1 if there is no dependency with parts 2 & 314:49
acabottkaczynski : in that case it will be Newton-3, I'm fine with that14:49
tkaczynskibut we can merge first 2 changesets14:49
*** shaohe_feng has quit IRC14:49
vincentfrancoiseacabot: no there's none, that's why I already pushed the doc regarding this part14:49
jed56acabot: there is no dependency14:49
*** padkrish_ has quit IRC14:50
*** shaohe_feng has joined #openstack-meeting-414:50
acabotgood to know, in this case we will merge vincentfrancoise & tkaczynski current code14:50
acabot10 minutes left for open discussions14:50
acabot#topic Open Discussion14:51
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:51
acabotGlobal Requirement: is watcher-dashboard project automatically sync with OS Global Requirements ?14:51
digaacabot: I am setting up watcher. I am going through the doc it seems you have lot of planned things. I would like to contribute to this project as I have some ideas also but I will start with adding bug fixes or whichever you think better place for me to start14:51
acabot#undo14:51
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f2b3608a490>14:51
acabotI forgot to mention that we have bugs open in triaged state14:51
digaokay14:52
*** zeih has quit IRC14:52
sballe_diga: I am also setting up watcher in my own lab s14:52
acabotdiga : please have a look at https://launchpad.net/watcher/+milestone/newton-214:52
hanrong1dtardivel: Is adding policies to watcher-dasboard a  part of BP watcher-policies14:52
acabotwe should have low-hanging-fruit14:52
dtardivelacabot: we should sync watcher-dashboard, as discusses with vincentfrancoise  offline.14:53
dtardivelhanrong1: yes14:53
digaacabot: that should be good starting place14:53
acabotdiga : https://bugs.launchpad.net/watcher/+bugs?field.tag=low-hanging-fruit14:53
digasballe_: I am setting it with devstack but it seems watche many configuration params14:53
acabotdtardivel : are you still talking about policies ?14:53
sballe_diga: yeah same here14:54
*** alexchadin has quit IRC14:54
*** zeih has joined #openstack-meeting-414:54
digaacabot: thanks I will pick some14:54
dtardivelacabot: sorry. sync with globla requirements14:54
acabotok let me move back to open discussions14:54
acabot#topic Open discussion14:54
*** openstack changes topic to "Open discussion (Meeting topic: watcher)"14:54
acabotGlobal Requirement: is watcher-dashboard project automatically sync with OS Global Requirements ?14:54
dtardivelacabot: yes it should be :)14:55
acabotdtardivel vincentfrancoise : ok so you agreed that we should do it14:55
acabotany comment on this ?14:55
*** anilvenkata has joined #openstack-meeting-414:55
vincentfrancoisedtardivel: +114:55
acabot#action dtardivel add OS global requirements to watcher-dashboard14:56
*** zeih has quit IRC14:56
acabotHow to deal with packaging (puppet) when updating conf parameters ?14:56
acabotwe probably need danpawlik on this14:56
acabotthe problem is that we need to maintain puppet recipes now14:57
acabotand Watcher parameters are still evolving14:57
jed56acabot: IMHO,we have to carefully write the "deployer impact" section in the specs14:58
acabotjed56 : ok14:58
jed56acabot: how to notify the pupper maintainers ?14:59
acabotwe will probably discuss it again in the rc-final version as packaging will be tested14:59
jed56s/pupper/puppet14:59
*** iyamahat has quit IRC14:59
jed56do we need to create bugs  ?14:59
dtardiveljed56: acabot there is no specific tag in commit message related to packaging14:59
jed56dtardivel: ah :(15:00
*** shaohe_feng has quit IRC15:00
*** piet has joined #openstack-meeting-415:00
*** shaohe_feng has joined #openstack-meeting-415:00
acabot#action acabot ask packaging team how to deal with parameters15:00
*** dshakhray_ has quit IRC15:00
acabottime to end15:00
acabotthx15:00
*** ulik has joined #openstack-meeting-415:00
acabot#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Jun 29 15:00:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-29-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-29-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-06-29-14.01.log.html15:00
sballe_bye15:00
*** PerfectChaos has joined #openstack-meeting-415:00
vincentfrancoisebye15:00
*** rainya has joined #openstack-meeting-415:00
tkaczynskibye15:00
*** trozet has quit IRC15:01
*** danpawlik has joined #openstack-meeting-415:01
jed56bye15:01
serverascode#startmeeting operators_telco_nfv15:01
openstackMeeting started Wed Jun 29 15:01:26 2016 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
gzhai2bye15: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
serverascode#topic rollcall15:01
*** openstack changes topic to "rollcall (Meeting topic: operators_telco_nfv)"15:01
serverascodeif anyone is here for the ops telcom/nfv meeting let me know :)15:01
*** michaelgugino has left #openstack-meeting-415:01
ulik#info Uli Kleber15:01
ulikHi, I am from OPNFV15:02
*** vincentfrancoise has left #openstack-meeting-415:02
serverascodehi ulik :)15:02
ulikThank you for the email reminder ... sometimes hard to find things in openstack15:02
*** hanrong1 has quit IRC15:03
serverascodeyeah for sure :)15:03
serverascodewe'll wait a few min to see if anyone else shows up, we are still a new group15:03
uliksorry I didn't join earlier after the BOF at Austin15:03
serverascodeno worries :) it was a busy week15:03
PerfectChaosOps hat on and ready to go~15:04
*** yamahata has quit IRC15:04
serverascodeah cool15:04
serverascodemaybe one more min then we'll get started15:05
*** rainya_ has joined #openstack-meeting-415:05
serverascode#topic last meeting actions15:05
*** openstack changes topic to "last meeting actions (Meeting topic: operators_telco_nfv)"15:05
serverascodeso we had two actions from last week15:06
serverascode#link http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-15-15.00.html15:06
serverascodeACTION: serverascode to email to operators list when we know when the opnfv ops bof will be (serverascode, 15:16:36)15:06
serverascodeI did email the list when we found out when the bof was so that was done15:06
serverascodeand then15:06
serverascodeACTION: PerfectChaos to try writing a first version of a group mission statement or purpose (serverascode, 15:33:22)15:07
serverascodewas the second15:07
serverascodePerfectChaos how did that go? :)15:07
*** petergurinov has quit IRC15:07
PerfectChaosIt was... like I said at the time, I'm not used to that sort of writing, so it's very much a first draft as a starting point...15:07
*** vhoward has joined #openstack-meeting-415:07
*** yujunz has quit IRC15:07
serverascodeyeah for sure, it's just a "strawman/person" as they say15:07
*** rainya has quit IRC15:07
serverascodeit's not easy that is for sure15:08
*** danpawlik has quit IRC15:08
PerfectChaosOkay, let's get it showing up in the minutes...15:08
*** asingh has joined #openstack-meeting-415:09
serverascodesure15:09
PerfectChaos#info Very much a first draft of the mission statement, as a starting point for discussion and consideration:15:09
*** sacharya has joined #openstack-meeting-415:09
PerfectChaos#info The OpenStack Operators Telecom and NFV Working Group aims to effect enhancements to OpenStack which benefit operators specifically running telecommunication services and Network Function Virtualization (NFV) on top of OpenStack. These services have their own particular problems and challenges which are less obvious to those not running them, and therefore are less likely to receive developer attention. The Working Group thus aims to15:09
*** gongysh has quit IRC15:09
PerfectChaos#info To achieve this, with each release the group identifies the issues most commonly faced by telecommunications and NFV operators and for each ensures that action is being taken to address it in an appropriate way, including liaising with developers, raising and highlighting bug reports and chasing up pending work. For each release the Working Group will produce a record of issues identified, what is being done to resolve them and an ex15:09
PerfectChaos...that's your lot.15:10
*** shaohe_feng has quit IRC15:10
serverascodeok, might have got cut off at the end there, "and an ex..."15:10
*** shaohe_feng has joined #openstack-meeting-415:10
serverascodebut that definitely looks like a great start15:11
PerfectChaos#info If that got cut off, it should conclude: For each release the Working Group will produce a record of issues identified,  what is being done to resolve them and an expected timescale for improvement.15:11
ulikyes. Great start.15:11
*** daneyon has joined #openstack-meeting-415:11
*** syjulian has left #openstack-meeting-415:11
serverascodeok, so what I think I'll do is take that and put it into an etherpad and send it out to the ops list and get some comments perhaps and we can revisit next meeting :)15:11
serverascodethanks so much PerfectChaos15:12
* PerfectChaos nods15:12
PerfectChaosNo problem.15:12
uliksorry for my not knowing. Should I be on some mailing list to receive that?15:12
serverascoderight, being this an an openstack ops working group, it's best to also be on the operators list15:13
serverascode#link http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators15:13
*** cdelatte has joined #openstack-meeting-415:13
serverascodeit's yet another mailing lits, but we'll be figuring out a good tag for emails so they can be filtered15:13
serverascodethe ops list is actually fairly low traffic15:13
serverascodeany other thoughts on this topic?15:14
serverascodewill wait about a min15:14
ulikI can deal with that.15:15
ulikActually I didn't subscribe because I thought it was cloud datacenter operators there.15:15
serverascodeit's really for anyone who designs, deploys, operators, maintains openstack clouds, could be in test as well such as OPNFV15:15
*** janki has joined #openstack-meeting-415:15
*** sacharya_ has joined #openstack-meeting-415:16
PerfectChaosIt seems to be a mix of anybody who does anything remotely Ops-y.15:16
serverascodethere are lots of little clouds out there too15:16
serverascodeyeah for sure15:16
*** piet has quit IRC15:16
*** trozet has joined #openstack-meeting-415:16
serverascode#topic opnfv summit bof15:16
*** openstack changes topic to "opnfv summit bof (Meeting topic: operators_telco_nfv)"15:16
*** pcaruana has quit IRC15:17
serverascodejust to quickly mention the bof, opnfv was kind enough to offer a table for a bof, but there was only a couple of us there15:17
serverascodespecifically myself and shinto who couldn't make it today15:17
serverascodewe also had an openstack community panel with myself, the tacker ptl, and the neutron ptl15:17
serverascodenot too much else to mention, but thanks to opnfv for the support :)15:18
serverascode#topic mailing list tag15:18
*** openstack changes topic to "mailing list tag (Meeting topic: operators_telco_nfv)"15:18
*** sacharya has quit IRC15:18
ulikI can communicate that with the OPNFV community.15:18
ulikAre there any good inputs from the BOF? I missed a lot of such sessions in Berlin.15:18
serverascodegreat thanks ulik :)15:19
serverascode#link https://etherpad.openstack.org/p/opnfv-ops-bof15:19
serverascodenot so much, as it was just me and shinto talking about openstack and telecoms and such15:19
serverascodeI took a few notes15:19
serverascodein that link above15:20
ulikSo OPNFV folks were not on the BOF :(15:20
serverascodetechnically no :)15:20
*** shaohe_feng has quit IRC15:20
ulikpity. We have to get better there.15:20
serverascodeno worries, it's still early for this wg, as well as OPNFV, and openstack in telecoms15:21
serverascodeit's going to take some work :)15:21
*** ming__ has joined #openstack-meeting-415:21
serverascodeI jumped topics too early :)15:21
serverascodebut one thing I want to do is set a good tag for the ops mailing list, ie. you put [something] in your email subject15:22
ulikI'll put this on my personal goals on the OPNFV side.15:22
serverascodethat's awesome ulik :)15:22
ulikYes. [something] is a nice tag :D15:22
serverascodeI was thinking [ops-telecom] would be simple, anyone have any ideas?15:22
*** ming__ has quit IRC15:22
serverascodeis that seems ok then I think we just run with that for awhile15:23
ulikI still find "ops" misleading.15:23
serverascodeah, right, the telecom operators issue15:23
ulikWhat about [telco-nfv]15:23
serverascodeyeah, [telecom-nfv] would be fine with me, the only thing is that the openstack foundation told me to use telecom instead of telco15:24
serverascodeso [telco-nfv] works?15:24
serverascodeI mean [telecom-nfv]15:24
ulikI would expect so. But one thought. It might be interesting if we15:25
*** shaohe_feng has joined #openstack-meeting-415:25
ulikcan use the same tag also on OPNFV mailing lists.15:25
serverascodefor sure, that's a good idea15:25
serverascodeand [telecom-nfv] would work there as well?15:26
ulikSince all OPNFV thinks they are [telecom-nfv], that might be not helpful on their side.15:26
serverascodeah, right15:26
*** Lingli has joined #openstack-meeting-415:26
ulikBut having [openstack-something] in a openstack mailing list might be weird.15:26
ulikSo I don't know how to resolve.15:26
serverascodehmmm15:26
PerfectChaosIt may be that the contexts are disparate enough that we should just use separate tags, then?15:27
ulikProbably.15:27
*** Sukhdev has joined #openstack-meeting-415:27
ulikThen let's try [telecom-nfv]15:27
PerfectChaosIn terms of filters, I don't think it makes it any more or less complicated whether they're the same or not.15:27
uliktrue15:27
serverascoderight15:27
serverascodeok, so perhaps we start with [telecom-nfv] for the openstack ops list and work on what we might be able to use on the opnfv list15:28
*** antongribok has joined #openstack-meeting-415:28
ulikI will recommend to OPNFV people then to join OpenStack-operators list and listen to [telecom-nfv] tag.15:28
serverascode#agreed use [telecom-nfv] for the openstack operators email list15:28
ulikMaybe we can attract some more guys.15:29
ulikShould I tell them something else?15:29
*** v1k0d3n has quit IRC15:29
serverascodeno that sounds great15:29
*** padkrish has joined #openstack-meeting-415:29
serverascodeok, great15:30
*** shaohe_feng has quit IRC15:30
serverascode#action serverascode set [telecom-nfv] tag15:30
serverascode#topic open discussion15:30
*** openstack changes topic to "open discussion (Meeting topic: operators_telco_nfv)"15:30
vhowardWanted to ask if anyone would like to help with the ops/arch guides, we have a meeting tomorrow and here is the wiki...always looking for folks to help out/chime in https://wiki.openstack.org/wiki/Documentation/OpsGuide15:31
*** amotoki has quit IRC15:31
vhowardthanks15:31
ulikfeel free to action me to share this with OPNFV folks.15:31
ulik:D15:31
serverascode#action ulik share operators list and tag with OPNFV folks15:31
*** shaohe_feng has joined #openstack-meeting-415:31
serverascodehi vhoward :)15:31
serverascodeyeah the ops/arch guide is interesting, I was thinking one of the things that would come out of this wg would be documentation perhaps15:32
*** pcaruana has joined #openstack-meeting-415:32
serverascode#info ops/arch guide team having a meeting Thu June 3015:33
serverascodeanyone else have any other topics to discuss?15:34
vhowardawesome thank you15:34
*** saju_m has quit IRC15:34
serverascodewill wait another minute or so15:35
serverascodevhoward I will try to come by the ops/arch meeting :)15:35
serverascodeulik, PerfectChaos thanks so much for coming by today, and for your help15:35
ulikI will try to join as regularly as I can.15:36
*** padkrish has quit IRC15:36
serverascodeok ending meeting :)15:36
ulikNice meeting you guys. Sorry I didn't meet u f2f in Berlin .... :(15:36
serverascode#endmeeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:36
openstackMeeting ended Wed Jun 29 15:36:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-29-15.01.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-29-15.01.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-06-29-15.01.log.html15:36
serverascodethanks everyone!15:36
PerfectChaosNo problem.15:37
*** PerfectChaos has left #openstack-meeting-415:40
*** shaohe_feng has quit IRC15:41
*** shaohe_feng has joined #openstack-meeting-415:41
*** sridhar_ram has quit IRC15:42
*** sridhar_ram has joined #openstack-meeting-415:43
*** belmoreira has quit IRC15:43
*** pbourke has quit IRC15:43
*** pbourke has joined #openstack-meeting-415:44
*** Lingli has quit IRC15:45
*** piet has joined #openstack-meeting-415:45
*** amotoki has joined #openstack-meeting-415:45
*** gongysh has joined #openstack-meeting-415:46
*** Lingli has joined #openstack-meeting-415:46
*** david-lyle has quit IRC15:46
*** cbouch has joined #openstack-meeting-415:48
*** vishnoianil has joined #openstack-meeting-415:50
*** shaohe_feng has quit IRC15:51
*** yamahata has joined #openstack-meeting-415:51
*** shaohe_feng has joined #openstack-meeting-415:52
*** AlanClark has joined #openstack-meeting-415:52
*** trozet has quit IRC15:54
*** ddieterly is now known as ddieterly[away]15:57
*** inc0_ has joined #openstack-meeting-415:57
*** cdelatte has quit IRC15:57
*** Rockyg has joined #openstack-meeting-415:58
*** Lingli has quit IRC15:58
*** cdelatte has joined #openstack-meeting-415:59
*** pbourke-mobile has joined #openstack-meeting-415:59
*** amotoki has quit IRC15:59
*** mandre has joined #openstack-meeting-415:59
sdake#startmeeting kolla16:00
openstackMeeting started Wed Jun 29 16:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
sdake#topic rollcall16: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
sdake\o/ ;)16:00
inc0_o/16:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:00
mandreola16:00
SergeyLukjanovo/16:00
coolsvap\o/16:00
inc0_SergeyLukjanov, nice to see you:)16:00
pbourke-mobileHi16:00
*** kfox1111_ has joined #openstack-meeting-416:00
*** ddieterly[away] is now known as ddieterly16:01
akwasnieHi16:01
Jeffrey4lo/16:01
*** vhosakot has joined #openstack-meeting-416:01
vhosakoto/16:01
*** trozet has joined #openstack-meeting-416:01
*** shaohe_feng has quit IRC16:01
sdake#topic announcements16:01
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:01
*** zeih has joined #openstack-meeting-416:01
sdake1. midcycle is July 12, 13th at Ansible HQ16:01
sdakemake sure to book travel asap16:01
*** wirehead_ has joined #openstack-meeting-416:02
sdakeunder 14 days the fares go up16:02
wirehead_o/16:02
*** shaohe_feng has joined #openstack-meeting-416:02
sdakeany other announcements?16:02
britthousero/16:02
coolsvapmost of the images are pushed to kolla repo on docker hub16:02
britthouserBarcelona hotels are available...just FYI.16:03
sdake#topic review backlog / bug backlog / blueprint backlog16:03
*** openstack changes topic to "review backlog / bug backlog / blueprint backlog (Meeting topic: kolla)"16:03
sdakewe have a tremendous amount of work in our backlog16:03
sdakemost of the reviews without -1's seem to be moving quckly16:03
sdakewe have approximately 200 bugs outstanding16:04
sdakestruggling to handle the workload myself - need help with triage16:04
sdakewe have about 80 blueprints outstanding16:04
*** GB21 has joined #openstack-meeting-416:04
sdakeanyone have solutions to these problems? :)16:04
vhosakotsdake: I'll triage them today and pick some16:05
*** iceyao has quit IRC16:05
coolsvapwe need some more active participation during reviews16:05
sdakei was looking more for solutions to managing the workload16:05
coolsvapif you see the bug change it there itself16:06
mandreother than spending time doing code review and triage bugs, I don't see how to decrease the backlog16:06
vhosakotsdake: we're talking about managing n2 workload right?  https://launchpad.net/kolla/+milestone/newton-216:06
sdakevhosakot yup but there are a slew of bugs in n1 that i haven;t moed over yet16:06
*** alexstav has quit IRC16:06
sdakebecause clicking launchpad sucks16:07
sdakeand there are hundreds of them16:07
coolsvapwe need to move from n116:07
sdakei do about 30 a d ay ;)16:07
*** jmckind_ has joined #openstack-meeting-416:07
*** gongysh has quit IRC16:07
coolsvapsdake, i take the action to triage all n1 bus16:07
coolsvapbugs16:07
sdakewht i'm getting at is i'd like all the core reviewers to be active in hepling out on all this activity16:07
coolsvapand move them appropriately16:07
vhosakotok, let us first move high-priority bugs from n1 to n2 and fix outstanding n1 bugs... we can share this effot16:07
sdakeopen bugs should not be in n1, n1 is closed16:07
sdakethe reality is this project is very large now and too much work for one person to handle lal of launchpad16:08
sdakewe have 300+ people contributors in the last year16:08
*** GB21 has quit IRC16:08
sdakeif there is anything you cn do to help out on a continual basis, that owudl be great16:08
*** coolsvap_ has joined #openstack-meeting-416:08
sdakeone tie mwork is helpful16:08
sdakedont get me wrong16:09
sdakebut i'm looking for a permanent solution :)16:09
*** ajmiller has quit IRC16:09
sdakei was also thinking it might be time to have the non-nuclear spec option (only require 2 +2s) for new work - we can discuss more at midcycle16:09
sdakebut start thinking about it16:09
*** ajmiller has joined #openstack-meeting-416:09
*** xingchao has quit IRC16:09
coolsvap_sorry got disconnected16:09
coolsvap_i think we need people to constantly do this16:09
coolsvap_rather than doing it once16:09
sdakecoolsvap_ ++16:10
wirehead_Create a day-by-day rotation where members of core pick a day to triage like your life depended on it?16:10
*** ulik has quit IRC16:10
*** jmckind has quit IRC16:10
sdakei think if we just accept triage as part of our workload it would help me alot )16:10
*** banix has joined #openstack-meeting-416:10
sdakeok enough  compaining16:11
sdakeif you can help - please do ;)16:11
sdakeif you can't, I understand16:11
mandreI've not been the most active contributor lately... sorry for that.16:11
coolsvap_sdake, ++16:11
sdakeSergeyLukjanov you want to go next or shoudl we do our midcycle brainstorming next16:11
sdakeSergeyLukjanov up to you16:11
*** coolsvap has quit IRC16:11
*** shaohe_feng has quit IRC16:11
SergeyLukjanovsdake as you wish16:11
sdake#topic universal containers16:12
*** oshidoshi has quit IRC16:12
*** openstack changes topic to "universal containers (Meeting topic: kolla)"16:12
sdakeso the idea of universal containers - I think the core team is all in agreement that we want that model16:12
*** shaohe_feng has joined #openstack-meeting-416:12
sdakethat is why we have na abi today16:12
inc0_SergeyLukjanov, you're up16:12
sdakeithink if I read the review correctly the problelm is around separte repos16:12
pbourke-mobileCan you define that?16:12
sdakeof which ther ehasn't been a real good explination of the 5 ws of that16:12
SergeyLukjanovbased on the current discussion it seems like one of the most arguable topics is repo per component and so I think it should be moved out of current spec16:13
sdake(what/where/when/how/why)16:13
sdakeespecially the why16:13
*** mliima has joined #openstack-meeting-416:13
SergeyLukjanovthe main points from my side are about containers - deployer separation and bootstrap separation16:13
inc0_SergeyLukjanov, agree, so as for universal containers, that was one of things we tried to do from day 116:13
inc0_technically current containers should be deployer-agnostic16:14
inc0_which was partially proven by both tripleo and mesos16:14
sdakedefine deployer separation SergeyLukjanov16:14
SergeyLukjanovinc0_ yeah, I understand, it's as always about different point of views16:14
inc0_bootstrap separation - I'd leave this out till we figure out what would be architecture of separated one16:14
sdakeyou mean extracting the ansible code to a separate repo?16:14
inc0_also we need to keep upgrades working16:15
SergeyLukjanovsdake #1 separate repos and #2 no ansible bootstraping16:15
SergeyLukjanovif keep it short16:15
sdakeseparate repo is doable16:15
pbourke-mobileAnsible is not required for bootstrapping16:15
sdakei dont understand the no ansible bootstrapping16:15
sdakewe dont rqeuire that at all16:15
SergeyLukjanovsdake but it's embedded into containers?16:15
inc0_yeah, for convenience16:16
sdakeansible is embedded in olla-toolbox true16:16
inc0_so you start container with BOOTSTRAP env16:16
sdakeother then that it is not16:16
*** HenryG has quit IRC16:16
inc0_and kolla-toolbox for stuff like creation of users16:16
kfox1111_yeah. there is no ansible in the containers other then the kolla-toolbox container.16:16
*** HenryG has joined #openstack-meeting-416:16
inc0_but if you want to do this all on your own, totally doable, just don't spawn container with BOOTSTRAP env16:16
kfox1111_which you shouldn't need if you are doing orchestration with puppet.16:16
*** coolsvap_ is now known as coolsvap16:17
sdakeSergeyLukjanov but yuor goal isn't puppet orchestration, right?16:17
kfox1111_I've manully spawned a ceph with kolla containers and horizon. :)16:17
SergeyLukjanovokay, but still containers contains bootstraping16:17
sdakeit does contain bootstrapping16:17
Jeffrey4lbootstraping is just run a one-shot container then remove it. it is nothing to do with ansible.16:17
pbourke-mobileYou can disable that16:17
inc0_SergeyLukjanov, optional...why is that wrong?16:17
kfox1111_yeah. and that boostrap shoudl go I think.16:17
sdakein order to use it, you have to specify BOOtSTRAP env var16:17
pbourke-mobileWith one env var16:17
sdakeif you do not it does nothing16:17
SergeyLukjanovsorry for the bad wording - I mean not *Ansible* bootstraping but bootstraping itself16:18
sdakekfox1111_ have to tihnk about upgrades in that model16:18
SergeyLukjanovwhile different tools used for deployment - different bootstraping approaches used16:18
SergeyLukjanovas well as different topologies and configurations16:18
sdakei am not keen on external bootstrapping or database management16:18
sdaketoo easy for schemas to get out of sync16:18
inc0_SergeyLukjanov, and it's totally possible even now16:18
kfox1111_sdake: sure. I'm not sure bootstrapping is the best way to do upgrades anyway though.16:18
SergeyLukjanovinc0_ it's possible but mixed with containers itself16:19
inc0_as I said, dont run containers with BOOTSTRAP env16:19
kfox1111_I think the bootstrap thing shoudl be a different container. like a k8s job. spawn, let it run, then destroy.16:19
wirehead_Yeah, to look at some of the bootstrapping I’ve helped make work in kolla-kubernetes, I’m not sure you can treat bootstrapping as a separable issue.16:19
inc0_SergeyLukjanov, so let's say mariadb16:19
inc0_you can just run mariadb with predefined volumes16:19
SergeyLukjanovbut you'll still have bootstrap scripts in containers and they are located in the same folder with Dockerfile and managed together16:19
inc0_kolla_bootsrap would create root user and such16:19
wirehead_It’s significantly safer to do it in a consistent fashion from inside of the containers than it is to insist that it meet some magical definition of separable.16:19
sdakeSergeyLukjanov are you concerned that someone would trigger that bootstrap code?16:20
*** david-lyle has joined #openstack-meeting-416:20
*** rhallisey has joined #openstack-meeting-416:20
rhalliseyhey16:20
pbourke-mobileHey Ryan16:20
wirehead_e.g. MariaDB containers probably need the same consistent set of CLI tools to provision themselves.16:20
inc0_SergeyLukjanov, so all you guys have to do in separate project is to make sure you're aligned with bootstrap method out there16:20
kfox1111_wirehead_: I'm more worried from the standpoint of, something desides to do something overly clevor and reinints something it shouldnt.16:20
inc0_also I think you can't really bootstrap mysql outside of container16:20
inc0_as no root user exists16:21
SergeyLukjanovsdake my concern is that it's a deployment tool specific code inside containers, it isn't most critical thing, but IMO it makes containers more deployment tool agnostic16:21
kfox1111_I had a horible experience with a mythtv client desiding the server database should be upgraded once. :/16:21
*** piet has quit IRC16:21
pbourke-mobileIts not ansible specific though16:21
*** david-lyle has quit IRC16:21
sdakeit isn't deployment tool sepcific, its part of  the universal container model16:21
kfox1111_SergeyLukjanov: agreed. but, maybe the solution is, if enough deployment tools add bootstrap code to the containers, it get really generic.16:21
inc0_SergeyLukjanov, since it's possible to use different deploy, let's just revisit separation of bootsrap later ok?16:21
*** tung_doan has joined #openstack-meeting-416:21
*** david-lyle has joined #openstack-meeting-416:21
inc0_I mean, it works , it's there16:21
pbourke-mobileSergey why do you say it is16:21
inc0_and whatever you want to do, is possible16:22
*** shaohe_feng has quit IRC16:22
wirehead_Well, let’s be clear.  OpenStack has historically been hard to ugprade.  With the icehouse and Havana releases floating around being good examples of how bad it can be.16:22
sdakeinc0 mr positive :)16:22
inc0_well, in scope of external bootsrap;)16:22
*** shaohe_feng has joined #openstack-meeting-416:22
SergeyLukjanovpbourke-mobile it is b/c it supports only topologies and configs supported by specific deployment tool16:22
kfox1111_wirehead_: I've upgraded clouds from Essex all the way up to Mitaka. Yes, its really hard. :)16:22
inc0_unless it isn't (like mariadb) then you have perfectly working bootsrap for you;)16:22
*** ddieterly is now known as ddieterly[away]16:22
pbourke-mobileIts bash env vars16:22
*** david-lyle has quit IRC16:22
SergeyLukjanovpbourke-mobile it couldn't be supporting all cases (and shouldn't IMO)16:22
pbourke-mobileCould not be more agnostic16:23
*** david-lyle has joined #openstack-meeting-416:23
kfox1111_I'm for external bootstrap as much as possible. there may be cases where internal might make sense.16:23
*** sogabe has quit IRC16:23
*** tung_doan has quit IRC16:23
kfox1111_to be clear though, like in the spec, external orchestration. internal binaries.16:23
inc0_SergeyLukjanov, do you have any use-case in mind that is not achievable with our current arch?16:23
Jeffrey4lSergeyLukjanov, how to init the mariadb /var/lib/mysql file without the container, without the bootstrap script?16:23
*** uck has joined #openstack-meeting-416:23
SergeyLukjanovactually the mariadb case is good one - it's a situation when some bootstraping embedded is good16:23
kfox1111_Jeffrey4l: ceph for example with k8s.16:23
SergeyLukjanovlike users creation, it's more about container bootstrap16:24
kfox1111_the bootstrap code currently assumes it will make new id's with every run. if you run it in a k8s job and it fails,16:24
SergeyLukjanovnot service/component bootstrap16:24
kfox1111_it will keep creating osd id after id after id.16:24
*** turvey has left #openstack-meeting-416:24
inc0_ok, I'm lost, what's container bootsrap?16:24
*** david-lyle has quit IRC16:25
*** cdelatte has quit IRC16:25
sdakehttps://github.com/openstack/kolla/blob/master/docker/heat/heat-api/extend_start.sh#L5-L1716:25
SergeyLukjanovI'm not saying about removing code that creates user for example or code that is needed each time you running container16:25
*** david-lyle has joined #openstack-meeting-416:25
sdakeyou mean the code that parses the json file16:25
SergeyLukjanovsdake good sample - I mean such kind of code - https://github.com/openstack/kolla/blob/master/docker/heat/heat-api/extend_start.sh#L5-L1716:26
inc0_SergeyLukjanov, so heat-manage db_sync has to be in container right?16:26
sdakeyes, but if KOLLA_BOOTSTRAP is not deffined, nothign happens16:26
rhalliseyso triggering db sync externally?16:27
inc0_I dont think it's possible rhallisey16:27
sdakeits possible if you make one bootstrap contianer16:27
inc0_I mean, we could do docker exec -it heat-api heat-manage db_sync16:27
SergeyLukjanovinc0_ yup16:27
Jeffrey4li agree. we should move the heat related use create to ansible. but the heat-manage db_sync should leave there.16:27
kfox1111_I think what I'd like to see there, is KOLLA_BOOTSTRAP section moved to its own shell script.16:27
inc0_SergeyLukjanov, so I'm ok with tht16:27
*** ihrachys has quit IRC16:27
kfox1111_then you can docker run CONTINER /bootstrap16:27
rhalliseyinc0_, ansible docker could handle that16:28
inc0_it could16:28
rhalliseywe do it already16:28
SergeyLukjanovinc0_ or run container that will have that entrypoint will be needed command16:28
inc0_there are several ways to do it16:28
inc0_or that16:28
sdakereasonable idea kfox16:28
Jeffrey4linc0_, we even has no heat-api container, before bootstrap. how to to use docker exec ?16:28
kfox1111_then puppet or ansible or k8s jobs can run it.16:28
inc0_Jeffrey4l, we do...16:28
sdakeheat_bootstrap is started from heat_api contianer16:28
inc0_anyway, we can have bootstrap container as sdake said16:28
inc0_there are ways16:28
SergeyLukjanovwe can run a separated container "heat-bootstrap" with entrypoint command "heat-manage db_sync"16:29
sdakepersonally i'd prefer bootstrap happen all at once16:29
kfox1111_or, yeah. split it to a different container.16:29
inc0_SergeyLukjanov, one thing tho..instead of having separat econtainer16:29
rhalliseysdake, idk if it matters16:29
inc0_we have container with or without env16:29
inc0_doesn't make us build one additiona container16:29
inc0_that will be run once16:29
inc0_since all the tools are there16:29
Jeffrey4lyes it doesn't matter. the bootstrap container will be removed after it exit.16:29
SergeyLukjanovyup16:30
sdakei'd prfer to keep things simple nad not require docker exec to bootstrap containers tho16:30
kfox1111_inc0_: take the heat example again, heat-manage db_sync is a thing that happens during upgrades as well as bootstrap.16:30
kfox1111_the rest of it shouldn't ever be called outside of a bootstrap though.16:30
inc0_yeah, that too16:30
Jeffrey4lkfox1111_, yup.16:30
kfox1111_so thats where mixing orchestration with bootstrapping kind of worries me.16:30
rhalliseysdake, yes but the counter to that is removing it from the extend start makes things simpler16:30
inc0_SergeyLukjanov, how critical this issue is for you16:30
inc0_?16:30
inc0_can we revise it on summit or sth?16:30
SergeyLukjanovit's not the highest for sure :)16:30
sdakei guess i dont understand what the pain is about haing a BOOTSTRAP environment variable conditionallly execute code16:31
inc0_cool, I'm cool with any improvement proposals16:31
pbourke-mobilesdake ++16:31
rhalliseyless automagic i suppose16:31
SergeyLukjanovthe general issue of having ansible and containers in a same repo is more important for me16:31
rhalliseySergeyLukjanov, it's a topic for the midcycle16:31
sdakethe reason it is like that fwiw, is to facilitate backporting16:31
*** itisha has joined #openstack-meeting-416:31
inc0_SergeyLukjanov, reason we didnt separate yet is simply because it's irreversable16:32
*** shaohe_feng has quit IRC16:32
SergeyLukjanovjust a random thing - what's about making option no not "COPY bootstrap.sh" in Dockerfile?16:32
inc0_but moment we arrive to prod-readiness of kolla-k8s16:32
*** shaohe_feng has joined #openstack-meeting-416:32
sdakeif the repos are split backporitng becomes extremely dificult16:32
inc0_we are revising this issue16:32
inc0_SergeyLukjanov, negative16:32
kfox1111_sdake: there is also a general op thing where I want to make sure what I deploy isn't going to do something unexpected.16:32
inc0_you would create 2 different docker images16:33
kfox1111_just looking at the code, shows up the bootstrap stuff which looks very dangerious. (which it is)16:33
kfox1111_so I have to audit the scripts much more carefully.16:33
inc0_remember build is separate from deploy16:33
kfox1111_if they were seperate, then its easier to ignore.16:33
rhalliseykfox1111_, technially you would have to always audit something16:33
kfox1111_yes, but the amount is differnet. for example, I deploy horizon containers directly on one of my clouds today.16:33
inc0_SergeyLukjanov, so differet question, why you don't want ansible in tree specifically?16:33
inc0_what use case it prevents you from achieving?16:34
kfox1111_if the bootstrap scripts were seperate from the containers I'm running, I wouldn't have to review them at all.16:34
SergeyLukjanovkfox1111_ +116:34
sdakekfox1111_ they could still be broken if separate16:34
sdakeand would require review16:34
rhalliseykfox1111_, what about review the ansible code16:34
kfox1111_so, I do really like the idea of making, say, a heat-bootstrap container that all it is is heat-api with the bootstrap code added.16:34
kfox1111_rhallisey: yeah. that scares me a bit too. thats why I'm working on kolla-k8s. :)16:35
rhalliseyha16:35
*** piet has joined #openstack-meeting-416:35
kfox1111_there's a lot of code in the ansible stuff, and I have a hard time knowing if its safe or not.16:35
kfox1111_while k8s provides a layer of isolation.16:35
SergeyLukjanovinc0_ it's about need to dig into the ansible code in addition to containers itself and too coupled reference implementation16:35
inc0_kfox1111_, I have bad news for you then man... we're looking at ansible in k8s;)16:35
Jeffrey4lkfox1111_, are u meaning the heat-bootstrap container? or heat-bootstrap images?16:35
kfox1111_hense the, "I want to run kolla-ansible genconfig as non root" for example.16:35
inc0_SergeyLukjanov, so code is logically separate alread16:36
inc0_y16:36
sdakethe only thing that is not separate is the json file16:36
kfox1111_kfox1111_: sry. ment images I think.16:36
*** pcaruana has quit IRC16:36
inc0_one of reason we keep it there is, as you've said, reference implementation16:36
SergeyLukjanovsdake rhallisey folks, I'll not be able to be on the midcycle, will be there anny posibility to join remotely?16:36
kfox1111_inc0_: yeah, but I expect that to be a lot simpler as k8s does alot of lifting itself.16:36
inc0_so far ansible is only way to deploy kolla in prod ready way16:36
sdakeya we will have remote participation16:36
SergeyLukjanovsdake cool16:37
*** pbourke-mobile has quit IRC16:37
rhalliseykfox1111_, idk if you've seen my new spec16:37
rhalliseybase on the poc16:37
kfox1111_I'm ok with ansible orchestrating things. It just needs to be simple enough I can get my head around it.16:37
sdakeok so in conclusion16:37
kfox1111_rhallisey: yeah. I have. I commented I think.16:37
*** pbourke-mobile has joined #openstack-meeting-416:37
inc0_once we'll have alternative on that front, we agreed to keep things as they are16:37
rhalliseykfox1111_, ok cool16:37
sdakethere are two issues - bootstrap is integrated into the containers - ansible is in repo16:37
*** pbourke-mobile has quit IRC16:37
inc0_to limit deployers confusion16:37
sdakeansible in or out of repo has been hotly debated in the pasat16:38
sdakei dont care at this point16:38
sdakein the past i did16:38
sdakei do have concerns about backports and maintenance in general16:38
inc0_SergeyLukjanov, long story short, still open depate and I think it's rather matter of when than if16:38
sdakeas for bootstrapping - if someone invents a beetter bootstrap mechnaism and makes it work throughout the current code base wfm :)16:38
*** pbourke_ has joined #openstack-meeting-416:38
rhalliseyI think the contianers themselves should be at a point where what you expect is what you get.  Having flags in the scripts it doesn't 100% guarantee that16:38
SergeyLukjanovsdake agree about backports, such changes can make it unmaintainable16:38
* rhallisey can write a spec16:38
kfox1111_I think if it prevents another kolla competetor from spawning, moving ansible code to kolla-ansible is a reasonable thing, since we've been debating it for a while now anyway.16:38
inc0_but since it's only way that works today, we keep it for now16:39
sdakekfox1111_ it doesn't stop any competitor16:39
inc0_SergeyLukjanov, if you guys would like to help with kolla-k8s and accelerate it's way to success16:39
rhalliseykfox1111_, I think the technically reasons be enough tbh16:39
sdakestackanetes took kolla containers and merged them into their project16:39
inc0_providing valid alternative to ansible16:39
inc0_this discussion can be accelerated16:40
*** xingchao has joined #openstack-meeting-416:40
sdakeok well we need to get to brainstomring - since midcycle is only 2 weeks out16:40
SergeyLukjanovinc0_ we're going with own k8s based impl and I want mainly to use kolla images in future as I believe it's very good to have universal containers and not duplicate work on them. we can review further what will be achieved, let's say on summit16:40
sdakeya duplicating the containers is a huge waste of time16:41
kfox1111_SergeyLukjanov: why not contribute to kolla-k8s?16:41
*** cdelatte has joined #openstack-meeting-416:42
kfox1111_there's still a lot of room to participate there.16:42
*** shaohe_feng has quit IRC16:42
kfox1111_I think some of the tripleo folks are too.16:42
rhalliseycould build the same logic into kolla-kube16:42
rhalliseyso it could be consumed by any project16:42
*** shaohe_feng has joined #openstack-meeting-416:43
sdakekfox1111_ from my understanding mirantis has already made up its mind on this topic16:43
kfox1111_yeah.16:43
rhalliseybut kolla-kube is the central hub prof development16:43
SergeyLukjanovsdake kfox1111_ that's correct, it was done significantly before the last summit16:43
rhalliseyit's just olive branch.  The community is open for collaboration :)16:43
kfox1111_sdake: sure, but I want to have the discussion out in the open to ensure other folks picking something to contribute to, know the difference.16:43
sdakei think people willl natureally be drawn to kollla in this case, as this is our core mission16:44
sdakenot afraid of competition16:44
kfox1111_yup. kolla-k8s just wants to produce the best, open solution to openstack on containers using k8s. everyone's welcome.16:45
sdakeya dont see need for competition either fwiw :)16:45
kfox1111_+1. I can't stop them. Just incuraging otherwise.16:45
*** rainya_ has quit IRC16:45
sdakeok brainstomring - running out o time :)16:45
sdake#topic midcycle planning16:46
sdake#link https://etherpad.openstack.org/p/kolla-newton-midcycle16:46
*** openstack changes topic to "midcycle planning (Meeting topic: kolla)"16:46
rhalliseydoes kolla-kube have a slot? Or did I miss it?16:46
sdakeeveryone - please add items, i will schedule as best as possible16:46
*** xingchao has quit IRC16:46
SergeyLukjanovthx folks for the discussion, very appreciate16:46
rhalliseySergeyLukjanov, thanks!16:47
*** rainya has joined #openstack-meeting-416:47
*** ddieterly[away] is now known as ddieterly16:48
*** cdelatte has quit IRC16:48
sdakebtw, I want to spend a moment to inform folks of what is happening related to governance of the project16:49
*** padkrish has joined #openstack-meeting-416:49
sdakei have been a ptl for 5 years of my life, and think kolla is in pretty fantastic shape, so I am not running for ptl again (unless nobody else does)16:49
sdakeIve been training 3 people who may or may not intend to run - who nkows :)16:50
sdakeplan to stay on core for 1-2 years16:50
britthouser!16:51
inc0_wow sdake16:51
sdakeany questions16:51
inc0_I'll just say...thanks for all the work and getting us here!16:51
britthouseryeah...huge thanks!16:51
sdakeyou guys did all the work16:51
sdakei did a bit myself16:51
akwasnieThanks sdake!16:51
sdakebut definately team thing16:51
vhosakot!16:52
sdakeanyway - im not gone yet - 3 month left in the cycle16:52
rhalliseysdake, ya thanks for the leadership16:52
sdakebut I dont want people thinking I'm flaking out when I'm training people16:52
sdakei intend to finish strong this cycle ;)16:52
*** jinquan1 has quit IRC16:52
rhalliseysdake, I remember when the project was just us 2 :)16:52
sdakewell there was daneyon :)16:52
*** shaohe_feng has quit IRC16:52
sdake3 :)16:52
sdakesort of16:52
rhallisey316:52
rhalliseymeetings were lonely16:53
*** shaohe_feng has joined #openstack-meeting-416:53
*** padkrish has quit IRC16:53
mandresdake, wow! thanks for all the hard work16:53
rhalliseysdake, did kolla-kube already happen as a topic?16:53
sdakerhallisey no16:53
sdake#topic kolla-kube16:53
*** openstack changes topic to "kolla-kube (Meeting topic: kolla)"16:53
*** derekjhyang has joined #openstack-meeting-416:53
sdakei thought you meant midcycle not meeting :)16:53
*** pbourke_ has quit IRC16:54
wirehead_So, we’ve got a patch up that we’ve been playing with that installs enough bits of kolla-k8s to run Horizon and Keystone and do it multi-host.16:54
wirehead_And I spent some time yesterday deleting nodes and watching as everything magically came back up.16:54
*** rainya has quit IRC16:54
kfox1111_sdake: thanks for all the hard work.16:55
inc0_wirehead_, mariadb and rabbitmq behave?16:55
nihiliferthank you sdake16:55
sdakekfox1111_ again, styaing on the core team for 1-2 years :)16:55
wirehead_MariaDB behaves.  I haven’t done RabbitMQ yet. https://review.openstack.org/#/c/335215/16:55
rhalliseywirehead_, so for action items, we need a doc to show how to accomplish this16:55
wirehead_Basically, first thing I did was kill MariaDB a few times.16:55
rhalliseyidk if there is one yet16:55
rhalliseysince this requires ceph/shared storage + skydns16:56
kfox1111_maybe we need to start a doc for what's expected of a k8s cluster.16:56
kfox1111_k8s installed, skydns setup, ceph deployed (possibly with kolla-ansible)16:57
wirehead_Yeah, sbezverk and I have been chatting about SkyDNS in particular.16:57
kfox1111_(and maybe pv's precreated)16:57
rhalliseywhatever it is, we need to have everything laid out with explanations16:57
kfox1111_As to me, the pv precreation is a k8s provided thing.16:57
kfox1111_yeah.16:57
rhalliseyanother thing, a spec I wanted to bring upo16:58
wirehead_I agree.  dcwangmit01 posted that mostly as a “Hey, is this the right direction”16:58
rhalliseyhttps://review.openstack.org/#/c/335279/116:58
sdaket-1 minute16:58
rhalliseysdake, roger16:58
rhalliseythat spec is to orchestrate k8s using anisble16:58
rhalliseyit's something the comunity needs to debate16:58
rhalliseyread through and drop some comments pls :)16:58
rhalliseydone!16:59
kfox1111_rhallisey: The comment I made about the cli stuff still existing is inline with what I said above in this channel about wanting to be able to manually orchestrate as needed.16:59
rhalliseykfox1111_, I'll get to it later16:59
*** salv-orl_ has joined #openstack-meeting-416:59
kfox1111_k.16:59
rhalliseykfox1111_, actually I think I did respond to your comment16:59
*** padkrish has joined #openstack-meeting-416:59
rhalliseyI take that back I missed it16:59
kfox1111_draft? :)17:00
kfox1111_I draft things more then I'd like to admit. :/17:00
rhalliseyya let me revisti :)17:00
sdakemeeting time over :)17:00
sdake#endmeeting17:00
kfox1111_kk17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
sdakethanks for coming17:00
openstackMeeting ended Wed Jun 29 17:00:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-29-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-29-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-06-29-16.00.log.html17:00
rhalliseythanks :)17:00
*** rhallisey has left #openstack-meeting-417:00
*** wirehead_ has left #openstack-meeting-417:00
*** padkrish has quit IRC17:01
*** coolsvap is now known as coolsvap|dinner17:01
*** mriedem is now known as mriedem_lunch17:01
*** krotscheck is now known as krotscheck_vaca17:01
*** krotscheck_vaca is now known as krot_vaca_jul1917:01
*** salv-orlando has quit IRC17:02
*** padkrish has joined #openstack-meeting-417:02
*** shaohe_feng has quit IRC17:03
*** javeriak has joined #openstack-meeting-417:03
*** pbourke_ has joined #openstack-meeting-417:04
*** diga has quit IRC17:04
*** pbourke_ has quit IRC17:05
*** shaohe_feng has joined #openstack-meeting-417:05
*** saju_m has joined #openstack-meeting-417:06
*** sdake_ has joined #openstack-meeting-417:08
*** Sukhdev has quit IRC17:09
*** sdake has quit IRC17:10
*** Jeffrey4l has quit IRC17:11
*** sarob has joined #openstack-meeting-417:11
*** sarob has quit IRC17:13
*** shaohe_feng has quit IRC17:13
*** sarob has joined #openstack-meeting-417:13
*** shaohe_feng has joined #openstack-meeting-417:13
*** mliima has left #openstack-meeting-417:17
*** piet has quit IRC17:19
*** coolsvap|dinner has quit IRC17:20
*** pvaneck has joined #openstack-meeting-417:21
*** shaohe_feng has quit IRC17:23
*** shaohe_feng has joined #openstack-meeting-417:24
*** ddieterly is now known as ddieterly[away]17:25
*** uck has quit IRC17:26
*** boden has joined #openstack-meeting-417:27
*** uck has joined #openstack-meeting-417:27
dougwigo/17:27
bodeno/17:28
derekjhyango/17:28
*** sarob has quit IRC17:28
*** zeih has quit IRC17:28
*** sarob has joined #openstack-meeting-417:28
HenryGo/17:29
saju_mo/17:30
HenryGI wonder if armax is around too?17:30
dougwig#startmeeting networking_lib17:30
openstackMeeting started Wed Jun 29 17:30:14 2016 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:30
*** openstack changes topic to " (Meeting topic: networking_lib)"17:30
dougwighi all.17:30
openstackThe meeting name has been set to 'networking_lib'17:30
dougwig#topic Announcements17:30
*** openstack changes topic to "Announcements (Meeting topic: networking_lib)"17:30
dougwignew core reviewers -- starting last night, anyone neutron stadium core can +2, and any driver can +A.  please be aware of the public interface rules, especially when merging.17:30
*** johnsom has joined #openstack-meeting-417:31
HenryGMost of the rules are in the devref.17:31
*** sarob has quit IRC17:31
dougwigfor anyone doing releases, which is usually me or HenryG, we need to come up with a script or something to audit the new interfaces. more cooks means more merging, and once it hits pypi, we're stuck with it for literally years.17:31
bodenare there existing scripts that do this elsewhere that you know of?17:32
*** sarob has joined #openstack-meeting-417:32
dougwigno, or i'd have used them to add a unit test to prevent destructive interface changes.  :)17:32
bodenI can take a stab at such a script if you like17:33
*** javeriak_ has joined #openstack-meeting-417:33
dougwigpleaes.17:33
*** shaohe_feng has quit IRC17:33
dougwigplease17:33
*** shaohe_feng has joined #openstack-meeting-417:34
*** pc_m has joined #openstack-meeting-417:34
dougwiganother announcement, ireland is approaching.17:34
dougwig#topic  hacking check policy17:34
*** openstack changes topic to "hacking check policy (Meeting topic: networking_lib)"17:34
dougwigboden, you have the floor17:34
boden#link https://review.openstack.org/#/c/333500/17:34
*** javeriak has quit IRC17:34
*** salv-orl_ has quit IRC17:34
bodenthere’s some discussion about how we proceed with new hacking checks that might break consumers who use our checks.factory()17:35
*** salv-orlando has joined #openstack-meeting-417:35
bodenthe obvious: consumers break and ignore (via flake8) until they can comply17:35
bodenany other ideas?17:36
HenryGIMO it is kind of OK to break such things since it does not break anything user-facing17:36
dougwigthat's not very library friendly, though.17:36
HenryGBut the goal is to get our library into a friendlier form17:37
dougwigwe could make an internal private factory and an external one.17:37
bodenis this a call for a mini-interface around our checks :)17:37
dougwigas a dev, if "pip install -U" breaks me, i get annoyed. maybe that's just me.17:37
*** julim has joined #openstack-meeting-417:38
bodenagreed, but on the other hand the check goes un-noticed17:38
dougwigthose checks serve two purposes...  checking the lib code itself, and providing reuse for subprojects (especially the 'no neutron' check.)17:38
dougwigright, and this is a neutron library, so i guess we're allowed to be a bit opinionated.17:38
*** piet has joined #openstack-meeting-417:38
dougwigand they can always opt to not use the neutron-lib checks at all.17:38
dougwigor use their own factory.17:39
bodenyep, today we have a large amount of folks using it17:39
bodenfyi17:39
dougwigwe could run a few key pep8's, like neutron, on every change. it'll make it hard to merge hacking checks, since it'll be a two-step shuffle.17:39
bodendougwig I was thinking that too17:40
bodenI’d at least like to know if neutron pep8 breaks17:40
dougwigi was already looking into running neutron's unit tests last night, so this would be similar.17:40
bodendoes it make sense to perhaps build a small API aound our checks to make it easier for consumers to use them, or just assume they can use the public check functions as they see fit?17:41
dougwigi personally think the latter is fine.17:41
bodenworks for me17:41
bodenso we should probably doc this approach (devref) to get some further input during the patch review17:42
bodenthis approach == for hacking checks17:42
*** sarob has quit IRC17:43
bodenI’ll make sure 333500 has such details17:43
*** spzala has quit IRC17:43
dougwigok, that works.17:43
*** spzala has joined #openstack-meeting-417:43
bodennext topic, I think17:43
dougwig#topic new target project to deliver as part of our newton work since lbaas now has a spin-off17:43
*** openstack changes topic to "new target project to deliver as part of our newton work since lbaas now has a spin-off (Meeting topic: networking_lib)"17:43
*** shaohe_feng has quit IRC17:44
dougwigthis came up this past week; with lbaas moving into octavia, it likely isn't a good target for the initial pass of the lib.17:44
HenryGWhich are the candidates?17:44
dougwigwe can pick another *aas, though they will likely fare similarly; perhaps an ml2 driver?17:44
*** shaohe_feng has joined #openstack-meeting-417:44
*** anilvenkata has quit IRC17:44
HenryGHow about a networking-foo that's in the stadium?17:45
dougwigthis is the list that i work against when making a lib change:17:45
dougwighttps://www.irccloud.com/pastebin/QsoIDs4N/17:45
bodenI was thinking we should use a stadium proj?17:45
bodenhttps://github.com/openstack/neutron-specs/blob/master/specs/newton/neutron-stadium.rst17:45
dougwigi would say ovn, but they're a core plugin, not ml217:45
*** cbouch has quit IRC17:46
HenryGovn is now ml217:46
HenryGthey converted17:46
dougwighow about ovn and l2gw as the new targets?17:46
bodennetworking-l2gw?17:46
dougwigjinx17:46
HenryGsounds good to me17:47
HenryGWe can keep an eye on dynamic-routing too17:47
bodenworks for me17:47
dougwigok, sounds like a decision17:47
HenryG+117:47
boden+117:48
dougwig#topic Do we really want to run with the forbid eventlet patch17:48
*** openstack changes topic to "Do we really want to run with the forbid eventlet patch (Meeting topic: networking_lib)"17:48
*** spzala has quit IRC17:48
HenryGarmax approved it17:48
bodenI’m more curious about this than anything else :)17:48
dougwigin the lib, i think the answer is yes.17:48
dougwigthough eventlet now supports py3, so maybe it's not as evil as others thought it was.17:48
dougwigmoving on17:48
dougwig#topic neutron-lib callbacks and OVO17:49
*** openstack changes topic to "neutron-lib callbacks and OVO (Meeting topic: networking_lib)"17:49
dougwigwho's was this?17:49
bodendougwig: me17:49
dougwigthe floor is yours17:49
bodenI think the bullet in the wiki sums it up17:49
bodenpaste—> I'm going to try and kick the tires a bit more on neutron-lib callbacks. In particular I'm thinking of proposing a backwards compatible change in neutron that can use OVO. The thought is to get neutron on-board with a new callback API that can support OVO, then get that support into neutron-lib, etc. For example 279734 that Paul did, but no longer has bandwidth to drive.17:49
*** spzala has joined #openstack-meeting-417:50
bodenthoughts?17:50
dougwigi would suggest pinging armax and getting his thoughts on this one.17:50
bodenack17:50
HenryGboden: sounds good to me, but keep in close sync with armax17:50
dougwigdefinitely an area that needs tackling.17:50
bodensounds good; thx17:50
*** doonhammer has joined #openstack-meeting-417:51
dougwig#topic Open discussion17:52
*** openstack changes topic to "Open discussion (Meeting topic: networking_lib)"17:52
dougwigHenryG: is the base db stuff in yet?17:52
HenryGNo, I am preparing a patch for neutron core first, because some things need to be shuffled there17:52
*** AlanClark has quit IRC17:53
dougwigok.  let us know when it's there.17:53
HenryGShuffling after moving to lib is fraught with perils17:53
dougwiganything else today?17:53
HenryGJust a quick note on api-ref17:54
*** vhosakot has left #openstack-meeting-417:54
HenryGWe should add it as a weekly topic17:54
*** shaohe_feng has quit IRC17:54
*** lelouch_ has quit IRC17:54
HenryGAkihiro is driving it17:54
*** mriedem_lunch is now known as mriedem17:55
*** shaohe_feng has joined #openstack-meeting-417:55
bodenadmittedly I need to read up on that topic :)17:55
*** sdake_ has quit IRC17:55
bodennothing else from me17:55
bodenoh, I’ll be out next Monday17:56
HenryGThe work is going to be a lot of low-hanging-fruit to get all the APIs correctly documented.17:56
bodenand perhap Tuesday; but not sure on Tue17:56
dougwigHenryG: ok, i don't see amotoki online.  any update on api ref?17:56
HenryGLast I heard he is preparing an example on how to update/correct an API.17:56
bodenhttps://review.openstack.org/#/c/330890/17:57
HenryGFrom that template folks can go wild I assume17:57
* njohnston has an item, if now is a good time17:57
dougwigwe might need to adjust this meeting time if he needs to attend.17:57
dougwiggiven that it's 3am where he is.17:58
HenryGack, I will check with him17:58
dougwigalright, let's get out of here.17:59
dougwig#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Wed Jun 29 17:59:12 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-29-17.30.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-29-17.30.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-06-29-17.30.log.html17:59
njohnstond'oh, I guess I won't bring that up then17:59
dougwignjohnston: oops, did i miss something?17:59
njohnstondougwig: I'll ping you directly17:59
dougwignjohnston: egad, sorry.  let's talk in #openstack-neutron18:00
*** s3wong has joined #openstack-meeting-418:00
*** pc_m has left #openstack-meeting-418:00
*** degorenko is now known as _degorenko|afk18:03
*** padkrish has quit IRC18:03
*** shaohe_feng has quit IRC18:04
*** iyamahat has joined #openstack-meeting-418:05
*** shaohe_feng has joined #openstack-meeting-418:05
*** padkrish has joined #openstack-meeting-418:07
*** hdaniel has quit IRC18:07
*** yamamoto has quit IRC18:07
*** hvprash_ has joined #openstack-meeting-418:10
*** hvprash__ has joined #openstack-meeting-418:12
*** hvprash has quit IRC18:13
*** shaohe_feng has quit IRC18:14
*** janki_ has joined #openstack-meeting-418:14
*** shaohe_feng has joined #openstack-meeting-418:15
*** marst has joined #openstack-meeting-418:15
*** hvprash_ has quit IRC18:16
*** julim has quit IRC18:16
*** janki has quit IRC18:16
*** janki_ is now known as janki18:16
*** padkrish has quit IRC18:17
*** saju_m has quit IRC18:17
*** saju_m has joined #openstack-meeting-418:18
*** padkrish has joined #openstack-meeting-418:18
*** ddieterly[away] is now known as ddieterly18:19
*** mrhillsman has quit IRC18:21
*** ajmiller has quit IRC18:22
*** ajmiller has joined #openstack-meeting-418:22
*** hvprash__ has quit IRC18:24
*** hvprash has joined #openstack-meeting-418:24
*** shaohe_feng has quit IRC18:25
*** shaohe_feng has joined #openstack-meeting-418:27
*** iyamahat has quit IRC18:30
*** sambetts|cat is now known as sambetts|afk18:33
*** uck has quit IRC18:33
*** shaohe_feng has quit IRC18:35
*** shaohe_feng has joined #openstack-meeting-418:36
*** daneyon has left #openstack-meeting-418:37
*** amotoki has joined #openstack-meeting-418:41
*** uxdanielle has quit IRC18:42
*** xingchao has joined #openstack-meeting-418:44
*** shaohe_feng has quit IRC18:45
*** shaohe_feng has joined #openstack-meeting-418:46
*** amotoki has quit IRC18:47
*** julim has joined #openstack-meeting-418:47
*** xingchao has quit IRC18:49
*** mfedosin has quit IRC18:53
*** padkrish has quit IRC18:55
*** shaohe_feng has quit IRC18:55
*** padkrish has joined #openstack-meeting-418:56
*** shaohe_feng has joined #openstack-meeting-418:56
*** ajmiller has quit IRC18:56
*** ajmiller has joined #openstack-meeting-418:56
*** julim has quit IRC18:58
*** notmyname has quit IRC19:01
*** uxdanielle has joined #openstack-meeting-419:01
*** Sukhdev has joined #openstack-meeting-419:01
*** sambetts|afk has quit IRC19:02
*** dasanind has joined #openstack-meeting-419:02
*** vnogin has quit IRC19:03
*** jokke_ has quit IRC19:03
*** dasanind has left #openstack-meeting-419:03
*** sambetts has joined #openstack-meeting-419:04
*** notmyname has joined #openstack-meeting-419:04
*** jokke_ has joined #openstack-meeting-419:05
*** shaohe_feng has quit IRC19:06
*** shaohe_feng has joined #openstack-meeting-419:06
*** yamamoto has joined #openstack-meeting-419:08
*** ALUVial has joined #openstack-meeting-419:10
*** woodard has quit IRC19:12
*** woodard has joined #openstack-meeting-419:13
*** woodard has quit IRC19:13
*** woodard has joined #openstack-meeting-419:14
*** sdake has joined #openstack-meeting-419:14
*** vnogin has joined #openstack-meeting-419:15
*** shaohe_feng has quit IRC19:16
*** janki has quit IRC19:16
*** shaohe_feng has joined #openstack-meeting-419:17
*** yamamoto has quit IRC19:19
*** klindgren_ has joined #openstack-meeting-419:21
*** ihrachys has joined #openstack-meeting-419:25
*** wxy__ has quit IRC19:25
*** ALUVial has quit IRC19:25
*** wxy__ has joined #openstack-meeting-419:26
*** shaohe_feng has quit IRC19:26
*** shaohe_feng has joined #openstack-meeting-419:27
*** mandre has left #openstack-meeting-419:27
*** cdelatte has joined #openstack-meeting-419:30
*** ajmiller has quit IRC19:31
*** ajmiller has joined #openstack-meeting-419:32
*** cdelatte has quit IRC19:32
*** javeriak_ has quit IRC19:32
*** uck has joined #openstack-meeting-419:32
*** cdelatte has joined #openstack-meeting-419:33
*** cdelatte has quit IRC19:33
*** javeriak has joined #openstack-meeting-419:34
*** shaohe_feng has quit IRC19:36
*** shaohe_feng has joined #openstack-meeting-419:37
*** piet has quit IRC19:38
*** zeih has joined #openstack-meeting-419:40
*** shaohe_feng has quit IRC19:47
*** mriedem1 has joined #openstack-meeting-419:47
*** piet has joined #openstack-meeting-419:49
*** mriedem has quit IRC19:49
*** shaohe_feng has joined #openstack-meeting-419:49
*** mriedem1 is now known as mriedem19:51
*** ddieterly is now known as ddieterly[away]19:56
*** shaohe_feng has quit IRC19:57
*** shaohe_feng has joined #openstack-meeting-419:57
*** Guest20454 is now known as mgagne19:58
*** mgagne has joined #openstack-meeting-419:58
RockygHey, folks!19:59
*** amotoki has joined #openstack-meeting-420:02
*** amotoki has quit IRC20:06
*** shaohe_feng has quit IRC20:07
*** shaohe_feng has joined #openstack-meeting-420:07
*** zeih has quit IRC20:09
*** iyamahat has joined #openstack-meeting-420:15
*** shaohe_feng has quit IRC20:17
*** shaohe_feng has joined #openstack-meeting-420:18
*** julim has joined #openstack-meeting-420:19
*** ddieterly[away] is now known as ddieterly20:19
*** ajmiller_ has joined #openstack-meeting-420:23
*** uxdanielle has quit IRC20:24
*** ajmiller has quit IRC20:25
*** asettle has joined #openstack-meeting-420:26
*** iyamahat has quit IRC20:28
*** shaohe_feng has quit IRC20:28
*** shaohe_feng has joined #openstack-meeting-420:28
*** dtardivel has quit IRC20:37
*** shaohe_feng has quit IRC20:38
*** shaohe_feng has joined #openstack-meeting-420:38
*** tonytan4ever has quit IRC20:40
*** Rockyg has quit IRC20:40
*** piet has quit IRC20:44
*** shaohe_feng has quit IRC20:48
*** shaohe_feng has joined #openstack-meeting-420:48
*** boden has left #openstack-meeting-420:50
*** asettle has quit IRC20:51
*** ajmiller_ has quit IRC20:51
*** padkrish has quit IRC20:52
*** andymaier has joined #openstack-meeting-420:56
*** woodard_ has joined #openstack-meeting-420:56
*** asettle has joined #openstack-meeting-420:57
*** andymaier has quit IRC20:58
*** shaohe_feng has quit IRC20:58
*** shaohe_feng has joined #openstack-meeting-420:59
*** woodard has quit IRC21:00
*** ediardo has left #openstack-meeting-421:00
*** uck has quit IRC21:01
*** javeriak has quit IRC21:03
*** padkrish has joined #openstack-meeting-421:06
*** woodard has joined #openstack-meeting-421:08
*** shaohe_feng has quit IRC21:09
*** shaohe_feng has joined #openstack-meeting-421:09
*** javeriak has joined #openstack-meeting-421:10
*** asettle has quit IRC21:11
*** woodard_ has quit IRC21:12
*** woodard has quit IRC21:13
*** cleong has quit IRC21:14
*** inc0_ has quit IRC21:15
*** shaohe_feng has quit IRC21:19
*** shaohe_feng has joined #openstack-meeting-421:20
*** thorst has quit IRC21:21
*** amotoki has joined #openstack-meeting-421:22
*** baoli has joined #openstack-meeting-421:24
*** amotoki has quit IRC21:26
*** shaohe_feng has quit IRC21:29
*** saju_m has quit IRC21:29
*** shaohe_feng has joined #openstack-meeting-421:30
*** baoli has quit IRC21:39
*** spotz is now known as spotz_zzz21:39
*** shaohe_feng has quit IRC21:39
*** shaohe_feng has joined #openstack-meeting-421:40
*** tsymanczyk has joined #openstack-meeting-421:41
*** saju_m has joined #openstack-meeting-421:42
*** thorst has joined #openstack-meeting-421:46
*** xingchao has joined #openstack-meeting-421:47
*** ddieterly is now known as ddieterly[away]21:47
*** shaohe_feng has quit IRC21:50
*** shaohe_feng has joined #openstack-meeting-421:50
*** thorst has quit IRC21:50
*** xingchao has quit IRC21:51
*** mbound has joined #openstack-meeting-421:51
*** baoli has joined #openstack-meeting-421:52
*** mbound_ has joined #openstack-meeting-421:53
*** baoli has quit IRC21:54
*** padkrish has quit IRC21:54
*** woodard has joined #openstack-meeting-421:55
*** spzala has quit IRC21:55
*** spzala has joined #openstack-meeting-421:55
*** mbound has quit IRC21:57
*** piet has joined #openstack-meeting-421:57
*** jmckind_ has quit IRC21:58
*** spzala has quit IRC22:00
*** shaohe_feng has quit IRC22:00
*** shaohe_feng has joined #openstack-meeting-422:01
*** uck has joined #openstack-meeting-422:01
*** rcaballeromx has joined #openstack-meeting-422:03
*** baoli has joined #openstack-meeting-422:05
*** baoli has quit IRC22:06
*** mbound_ has quit IRC22:06
* rcaballeromx is waiting for Documentation User Guides Team Meeting22:06
*** mbound has joined #openstack-meeting-422:06
*** uck has quit IRC22:07
*** mriedem has quit IRC22:07
*** thorst has joined #openstack-meeting-422:07
*** mriedem has joined #openstack-meeting-422:07
*** mriedem has quit IRC22:07
*** baoli has joined #openstack-meeting-422:08
*** baoli has quit IRC22:08
*** padkrish has joined #openstack-meeting-422:08
*** ihrachys has quit IRC22:08
*** mbound has quit IRC22:08
*** mbound has joined #openstack-meeting-422:08
*** itisha has quit IRC22:10
*** shaohe_feng has quit IRC22:10
*** shaohe_feng has joined #openstack-meeting-422:11
*** cdelatte has joined #openstack-meeting-422:12
*** banix has quit IRC22:14
*** spzala has joined #openstack-meeting-422:14
*** ddieterly[away] is now known as ddieterly22:15
*** baoli has joined #openstack-meeting-422:17
*** baoli has quit IRC22:18
*** asingh has quit IRC22:18
*** ajmiller has joined #openstack-meeting-422:19
*** cdelatte has quit IRC22:19
*** shaohe_feng has quit IRC22:20
*** shaohe_feng has joined #openstack-meeting-422:21
*** baoli has joined #openstack-meeting-422:21
*** rtheis has quit IRC22:22
*** saju_m has quit IRC22:23
*** ajmiller has quit IRC22:28
*** ajmiller has joined #openstack-meeting-422:28
*** baoli has quit IRC22:28
*** shaohe_feng has quit IRC22:31
*** shaohe_feng has joined #openstack-meeting-422:31
*** baoli has joined #openstack-meeting-422:34
*** minwang2 has joined #openstack-meeting-422:34
*** baoli has quit IRC22:35
*** asingh has joined #openstack-meeting-422:35
*** saju_m has joined #openstack-meeting-422:36
*** minwang2 has quit IRC22:37
*** limao has joined #openstack-meeting-422:40
*** shaohe_feng has quit IRC22:41
*** shaohe_feng has joined #openstack-meeting-422:41
*** sdake_ has joined #openstack-meeting-422:42
*** cdelatte has joined #openstack-meeting-422:42
*** amotoki has joined #openstack-meeting-422:42
*** sdake has quit IRC22:45
*** ddieterly is now known as ddieterly[away]22:47
*** ddieterly[away] has quit IRC22:47
*** amotoki has quit IRC22:47
*** baoli has joined #openstack-meeting-422:48
*** baoli has quit IRC22:49
*** sdake_ has quit IRC22:49
*** cdelatte has quit IRC22:51
*** shaohe_feng has quit IRC22:51
*** shaohe_feng has joined #openstack-meeting-422:52
*** baoli has joined #openstack-meeting-422:55
*** inc0 has joined #openstack-meeting-422:55
*** inc0 has quit IRC22:55
*** baoli has quit IRC22:56
*** thorst has quit IRC22:58
*** baoli has joined #openstack-meeting-422:58
*** gzhai2 has left #openstack-meeting-422:58
*** thorst has joined #openstack-meeting-422:59
*** salv-orl_ has joined #openstack-meeting-422:59
*** baoli has quit IRC22:59
*** sdake has joined #openstack-meeting-423:01
*** shaohe_feng has quit IRC23:01
*** shaohe_feng has joined #openstack-meeting-423:02
*** salv-orlando has quit IRC23:03
*** sdake has quit IRC23:04
*** limao has quit IRC23:05
*** thorst has quit IRC23:07
*** antongribok has quit IRC23:10
*** antongribok has joined #openstack-meeting-423:10
*** banix has joined #openstack-meeting-423:10
*** baoli has joined #openstack-meeting-423:11
*** piet has quit IRC23:11
*** mriedem has joined #openstack-meeting-423:11
*** shaohe_feng has quit IRC23:12
*** baoli has quit IRC23:12
*** woodard has quit IRC23:12
*** shaohe_feng has joined #openstack-meeting-423:12
*** rcaballeromx has left #openstack-meeting-423:14
*** padkrish has quit IRC23:15
*** marst has quit IRC23:15
*** rcaballeromx has joined #openstack-meeting-423:16
*** pmesserli has quit IRC23:16
*** padkrish has joined #openstack-meeting-423:17
*** iyamahat has joined #openstack-meeting-423:18
*** piet has joined #openstack-meeting-423:18
*** hvprash has quit IRC23:19
*** padkrish has quit IRC23:20
*** antongribok has quit IRC23:20
*** shaohe_feng has quit IRC23:22
*** shaohe_feng has joined #openstack-meeting-423:22
*** uck has joined #openstack-meeting-423:27
*** baoli has joined #openstack-meeting-423:28
*** baoli has quit IRC23:29
*** saju_m has quit IRC23:29
*** iyamahat has quit IRC23:31
*** shaohe_feng has quit IRC23:32
*** shaohe_feng has joined #openstack-meeting-423:32
*** Lingli has joined #openstack-meeting-423:32
*** ajmiller has quit IRC23:33
*** dingboopt has joined #openstack-meeting-423:34
*** ajmiller has joined #openstack-meeting-423:34
*** daneyon has joined #openstack-meeting-423:38
*** ajmiller has quit IRC23:39
*** daneyon_ has joined #openstack-meeting-423:39
*** ajmiller has joined #openstack-meeting-423:39
*** shaohe_feng has quit IRC23:42
*** shaohe_feng has joined #openstack-meeting-423:43
*** daneyon has quit IRC23:43
*** Lingli has quit IRC23:45
*** mbound has quit IRC23:48
*** xingchao has joined #openstack-meeting-423:48
*** shaohe_feng has quit IRC23:53
*** shaohe_feng has joined #openstack-meeting-423:53
*** sacharya_ has quit IRC23:56

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