Wednesday, 2016-11-02

*** apuimedo has quit IRC00:25
*** Julien-zte has joined #openstack-meeting-400:30
*** limao has joined #openstack-meeting-400:31
*** limao has quit IRC00:32
*** limao has joined #openstack-meeting-400:32
*** Julien-zte has quit IRC00:36
*** Julien-zte has joined #openstack-meeting-400:37
*** baoli has joined #openstack-meeting-400:47
*** baoli has quit IRC00:48
*** suhani has joined #openstack-meeting-400:50
*** baoli has joined #openstack-meeting-400:50
*** baoli_ has joined #openstack-meeting-400:51
*** Julien-zte has quit IRC00:52
*** Julien-zte has joined #openstack-meeting-400:53
*** baoli has quit IRC00:55
*** baoli_ has quit IRC00:56
*** tovin07 has joined #openstack-meeting-401:05
*** suhani has quit IRC01:08
*** Julien-zte has quit IRC01:19
*** Julien-zte has joined #openstack-meeting-401:20
*** sgu has joined #openstack-meeting-401:30
*** baoli has joined #openstack-meeting-401:33
*** zhurong has joined #openstack-meeting-401:36
*** stewie925 has quit IRC01:45
*** singlethink has joined #openstack-meeting-401:45
*** sgu has quit IRC01:47
*** s3wong_ is now known as s3wong01:47
*** sneti has joined #openstack-meeting-401:48
*** s3wong has quit IRC01:48
*** thorst has quit IRC01:55
*** thorst has joined #openstack-meeting-401:56
*** baoli has quit IRC01:59
*** baoli has joined #openstack-meeting-401:59
*** baoli has quit IRC02:04
*** thorst has quit IRC02:04
*** syed_ has quit IRC02:05
*** armax has quit IRC02:26
*** caowei_ has joined #openstack-meeting-402:52
*** dave-mccowan has quit IRC02:57
*** shaohe_feng has quit IRC03:00
*** thorst has joined #openstack-meeting-403:02
*** Jeffrey4l has joined #openstack-meeting-403:07
*** thorst has quit IRC03:10
*** alij has joined #openstack-meeting-403:10
*** markvoelker has quit IRC03:41
*** JRobinson__ is now known as JRobinson__afk03:42
*** hemanthm|bbl is now known as hemanthm03:48
*** coolsvap has joined #openstack-meeting-404:08
*** thorst has joined #openstack-meeting-404:09
*** alij has quit IRC04:12
*** thorst has quit IRC04:15
*** JRobinson__afk is now known as JRobinson__04:31
*** alij has joined #openstack-meeting-404:33
*** khushbu has joined #openstack-meeting-404:34
*** alij has quit IRC04:36
*** alij has joined #openstack-meeting-404:39
*** markvoelker has joined #openstack-meeting-404:42
*** alij has quit IRC04:43
*** limao has quit IRC04:44
*** markvoelker has quit IRC04:48
*** khushbu has quit IRC05:04
*** limao has joined #openstack-meeting-405:04
*** thorst has joined #openstack-meeting-405:12
*** thorst has quit IRC05:20
*** prateek has joined #openstack-meeting-405:23
*** alij has joined #openstack-meeting-405:41
*** alij_ has joined #openstack-meeting-405:58
*** alij_ has quit IRC06:00
*** alij has quit IRC06:01
*** JRobinson__ has quit IRC06:11
*** revon has quit IRC06:12
*** shaohe_feng has joined #openstack-meeting-406:19
*** thorst has joined #openstack-meeting-406:19
*** nkrinner_afk has quit IRC06:21
*** alij has joined #openstack-meeting-406:22
*** nkrinner has joined #openstack-meeting-406:23
*** alij has quit IRC06:23
*** alij has joined #openstack-meeting-406:24
*** thorst has quit IRC06:25
*** mohankumar has joined #openstack-meeting-406:32
*** limao has quit IRC06:36
*** limao has joined #openstack-meeting-406:38
*** julim has quit IRC06:38
*** irenab has joined #openstack-meeting-406:40
*** markvoelker has joined #openstack-meeting-406:44
*** limao has quit IRC06:48
*** atuly has joined #openstack-meeting-406:49
*** markvoelker has quit IRC06:50
*** noama has quit IRC06:51
*** noama has joined #openstack-meeting-406:53
*** noama_ has joined #openstack-meeting-406:53
*** noama has quit IRC06:54
*** noama_ has quit IRC06:54
*** noama has joined #openstack-meeting-406:54
*** noama_ has joined #openstack-meeting-406:54
*** noama_ has quit IRC06:54
*** noama has quit IRC06:55
*** noama has joined #openstack-meeting-406:55
*** noama has quit IRC06:57
*** noama has joined #openstack-meeting-406:57
*** noama has quit IRC07:00
*** noama has joined #openstack-meeting-407:01
*** iyamahat has quit IRC07:04
*** yifei has quit IRC07:09
*** belmoreira has joined #openstack-meeting-407:10
*** yifei has joined #openstack-meeting-407:10
*** nkrinner has quit IRC07:13
*** nkrinner has joined #openstack-meeting-407:19
*** irenab_ has joined #openstack-meeting-407:19
*** irenab has quit IRC07:22
*** thorst has joined #openstack-meeting-407:23
*** nkrinner has quit IRC07:23
*** nkrinner has joined #openstack-meeting-407:24
*** limao has joined #openstack-meeting-407:24
*** limao_ has joined #openstack-meeting-407:27
*** limao has quit IRC07:28
*** limao has joined #openstack-meeting-407:29
*** thorst has quit IRC07:30
*** limao_ has quit IRC07:31
*** limao has quit IRC07:32
*** limao_ has joined #openstack-meeting-407:32
*** limao_ has quit IRC07:33
*** ricolin has joined #openstack-meeting-407:45
*** janonymous has joined #openstack-meeting-407:46
*** ricolin has quit IRC07:47
*** ricolin has joined #openstack-meeting-407:47
*** ricolin_ has joined #openstack-meeting-407:48
*** ricolin has quit IRC07:48
*** ricolin_ has quit IRC07:49
*** ricolin has joined #openstack-meeting-407:49
*** ifat_afek has joined #openstack-meeting-407:50
*** yuli_s has quit IRC07:54
*** eyalb has joined #openstack-meeting-407:58
ifat_afek#startmeeting vitrage08:01
openstackMeeting started Wed Nov  2 08:01:27 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
openstackThe meeting name has been set to 'vitrage'08:01
ifat_afekHi everyone :-)08:01
eyalbhi08:02
*** yujunz-zte has joined #openstack-meeting-408:03
ifat_afek#topic Barcelona recap08:03
*** openstack changes topic to "Barcelona recap (Meeting topic: vitrage)"08:03
ifat_afekBarcelona summit was extremely successful!08:04
ifat_afekHere are links to the recorded sessions:08:04
*** limao has joined #openstack-meeting-408:04
ifat_afek#link https://www.openstack.org/videos/video/demo-openstack-and-opnfv-keeping-your-mobile-phone-calls-connected08:04
ifat_afek#link https://www.openstack.org/videos/video/nokia-root-cause-analysis-principles-and-practice-in-openstack-and-beyond08:05
ifat_afek#link https://www.openstack.org/videos/video/ptls-and-cores-we-are-not-as-scary-as-you-think-organized-by-the-women-of-openstack08:05
ifat_afek#link https://www.openstack.org/videos/video/fault-management-with-openstack-congress-and-vitrage-based-on-opnfv-doctor-framework08:05
ifat_afekIn addition, we had Vitrage hands-on lab that was supposed to be recorded, and three design sessions.08:05
ifat_afekThe keynote demo with Doctor made a huge impression. The feedback we got was that it was the best demo in the keynotes this year. I think that as a result of this demo, more people came to Vitrage booth and to the hands-on lab.08:06
ifat_afekeyalb: thanks for your help in the keynotes!08:06
*** yamahata has quit IRC08:07
eyalbI sent an email to the rdo mailing list08:07
eyalbupdated them about vitrage08:07
eyalbI also pushed another package review for the dashboard08:07
eyalband I started working on the puppet integration project that is needed for rdo08:08
eyalbthats all08:08
ifat_afekeyalb: that’s great, thanks08:08
*** JRobinson__ has joined #openstack-meeting-408:08
*** mohankumar has quit IRC08:08
ifat_afekand did you understand that red hat are currently working on it?08:09
eyalbyes they started working on this08:09
*** elisha_r has joined #openstack-meeting-408:10
elisha_rhi - sorry I got here late08:10
ifat_afekgreat08:10
ifat_afekit’s very important for vitrage installation08:10
ifat_afekWe had a meeting the next day with Doctor team, and we agreed that the next step should be to finish Vitrage installation using TripleO and then to support Vitrage installation using Apex OPNFV installer.08:11
ifat_afekAnd for that we need to have the rdo ready08:11
ifat_afekWe understood that there are currently some issues with Apex, so we need to wait some time before we can start working on this integration.08:11
*** markvoelker has joined #openstack-meeting-408:13
*** alij has quit IRC08:13
elisha_rso I'll update briefly about the session we had on the principles of RCA08:13
elisha_rThe session took place late Thursday, but we still had a nice crowd08:14
*** anilvenkata has joined #openstack-meeting-408:15
elisha_rthe session went well, overall, except for the fact that we had some technical glitches with the PPT... :)08:15
ifat_afek:-)08:15
*** alij has joined #openstack-meeting-408:16
elisha_rwe gave an overview of what RCA is all about, and the motivation behind what we do in vitrage, which we coined "automated expert judgement". I think that working on preparing this session helped me, at least, to clarify our current focus in vitrage, within the world of RCA08:16
elisha_rThen Ifat presented a LIVE (!!) demo, which went very well, as well as discussing the future steps of Vitrage08:17
elisha_rAfter the session we had a few interesting questions, which were not recorded, so I'll review them here08:18
elisha_rfirst, we were asked about handling multi-tenancy, specifically in cases where the Admin is not supposed to know or care what the tenanats are doing within their VMs08:18
elisha_rI answered that part of this is already supported in the multi-tenancy support added recently, before the summit08:19
elisha_rhowever, it's possible that we would need to enhance this support for such cases, since currently the Admin sees everything08:19
*** markvoelker has quit IRC08:19
elisha_rAlternatively, one coud run several vitrage instances, one for customer, one for admin, each with its own set of relevant datasources08:20
elisha_rI think Vitrage should support the first option, but for full flexibility you might need the second no matter what08:20
elisha_rI know there were a few more questions, about how simple it would be to add a new datasource. But don't recall the details08:21
elisha_rthat's it as far as I can recall08:21
ifat_afekI was asked several times (after this session and in other times) about Vitrage-Aodh integration08:21
ifat_afekI explained that Aodh are the alarm manager, and have no intention of doing RCA. We have a POC of raising Vitrage alarms in Aodh, but it’s not working well at the moment08:23
ifat_afekI think it’s extremely important to finish this integration. I realized there is a real need for people to get Vitrage alarms using Aodh08:23
ifat_afekMoving on - Our design sessions were very interesting and productive. Among the issues that we discussed:08:24
ifat_afek•RCA history08:24
ifat_afek•Graph log inspector08:24
ifat_afek•Benchmark for Vitrage evaluator08:24
ifat_afek•Vitrage UX08:24
ifat_afek•Vitrage-Aodh Integration08:24
ifat_afek•Vitrage-Congress integration08:24
ifat_afekLink to the design sessions etherpad:08:24
ifat_afek#link https://etherpad.openstack.org/p/vitrage-barcelona-design-summit08:25
ifat_afekWe also had Vitrage hands-on lab, which succeeded beyond our expectations. Over 40 people came by to work in this lab, and many stayed after the end08:27
ifat_afekThis session was supposed to be recorded as well, but we can’t find the video. doffek is checking it08:27
*** thorst has joined #openstack-meeting-408:27
ifat_afekLast thing (I think) - we had Vitrage demos in Nokia booth in the market place. The booth was crowded all day long.08:28
*** alij has quit IRC08:28
ifat_afekThat’s what I had to say :-) Anything else?08:29
ifat_afekSo we’re done08:33
eyalbbye08:33
ifat_afekBye!08:33
elisha_rbye08:33
ifat_afek#endmeeting08:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:34
openstackMeeting ended Wed Nov  2 08:34:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-02-08.01.html08:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-02-08.01.txt08:34
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-02-08.01.log.html08:34
*** elisha_r has left #openstack-meeting-408:34
*** thorst has quit IRC08:35
*** sshnaidm has quit IRC08:35
*** sshnaidm has joined #openstack-meeting-408:39
*** ifat_afek has left #openstack-meeting-408:49
*** dtardivel has joined #openstack-meeting-408:51
*** GB21 has joined #openstack-meeting-408:55
*** noama has quit IRC08:57
*** noama has joined #openstack-meeting-408:58
*** matrohon has joined #openstack-meeting-409:00
*** limao has quit IRC09:00
*** alij has joined #openstack-meeting-409:03
*** reedip has quit IRC09:03
*** mohankumar has joined #openstack-meeting-409:05
*** zhurong has quit IRC09:06
*** limao has joined #openstack-meeting-409:08
*** tinwood has quit IRC09:14
*** yujunz-zte has quit IRC09:15
*** tinwood has joined #openstack-meeting-409:15
*** GB21 has quit IRC09:15
*** myatsenko has joined #openstack-meeting-409:17
*** Julien-zte has quit IRC09:28
*** thorst has joined #openstack-meeting-409:32
*** reedip has joined #openstack-meeting-409:35
*** thorst has quit IRC09:39
*** ricolin has quit IRC09:39
*** markvoelker has joined #openstack-meeting-409:41
*** markvoelker has quit IRC09:46
*** JRobinson__ has quit IRC09:49
*** reedip has quit IRC09:56
*** limao has quit IRC10:01
*** tovin07 has quit IRC10:06
*** matrohon has quit IRC10:08
*** reedip has joined #openstack-meeting-410:09
*** alij has quit IRC10:11
*** matrohon has joined #openstack-meeting-410:12
*** alij has joined #openstack-meeting-410:14
*** lazy_prince has quit IRC10:17
*** sambetts|afk is now known as sambetts10:18
*** alij has quit IRC10:19
*** harbor_log is now known as potdirect10:22
*** lazy_prince has joined #openstack-meeting-410:25
*** alij has joined #openstack-meeting-410:29
*** alij has quit IRC10:30
*** alij has joined #openstack-meeting-410:30
*** cdelatte has quit IRC10:32
*** numans has joined #openstack-meeting-410:32
*** yifei has quit IRC10:33
*** portdirect has joined #openstack-meeting-410:34
*** thorst has joined #openstack-meeting-410:37
*** potdirect has quit IRC10:37
*** mohankumar has quit IRC10:43
*** thorst has quit IRC10:45
*** portdirect has quit IRC10:48
*** alij has quit IRC10:56
*** alij has joined #openstack-meeting-410:57
*** rtheis has joined #openstack-meeting-410:57
*** alij has quit IRC10:57
*** alij has joined #openstack-meeting-410:57
*** atuly has quit IRC11:09
*** portdirect has joined #openstack-meeting-411:10
*** cdelatte has joined #openstack-meeting-411:11
*** spotz is now known as spotz_zzz11:12
*** alij has quit IRC11:13
*** rtheis_ has joined #openstack-meeting-411:13
*** rtheis_ has quit IRC11:13
*** alij has joined #openstack-meeting-411:13
*** rtheis_ has joined #openstack-meeting-411:13
*** rtheis has quit IRC11:14
*** GB21 has joined #openstack-meeting-411:15
*** matrohon has quit IRC11:16
*** GB21 has quit IRC11:33
*** dave-mccowan has joined #openstack-meeting-411:35
*** baoli has joined #openstack-meeting-411:38
*** baoli_ has joined #openstack-meeting-411:42
*** caowei_ has quit IRC11:42
*** markvoelker has joined #openstack-meeting-411:42
*** nkrinner has quit IRC11:44
*** baoli has quit IRC11:45
*** markvoelker has quit IRC11:46
*** nkrinner has joined #openstack-meeting-411:47
*** cdelatte has quit IRC11:47
*** thorst has joined #openstack-meeting-411:49
*** anilvenkata has quit IRC11:49
*** mohankumar has joined #openstack-meeting-411:51
*** nkrinner has quit IRC11:54
*** anilvenkata has joined #openstack-meeting-411:58
*** icey-travel is now known as icey12:00
*** cdelatte has joined #openstack-meeting-412:00
*** prateek has quit IRC12:01
*** krtaylor has joined #openstack-meeting-412:03
*** apuimedo has joined #openstack-meeting-412:07
*** nkrinner has joined #openstack-meeting-412:07
*** anilvenkata has quit IRC12:25
*** apuimedo has quit IRC12:25
*** celebdor has joined #openstack-meeting-412:25
*** alij has quit IRC12:31
*** baoli_ has quit IRC12:34
*** baoli has joined #openstack-meeting-412:36
*** markvoelker has joined #openstack-meeting-412:41
*** sshnaidm is now known as sshnaidm|afk12:45
*** julim has joined #openstack-meeting-412:48
*** celebdor has quit IRC12:48
*** cdent has joined #openstack-meeting-413:00
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Nov  2 13:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
cdento/13:00
Kevin_Zhengo/13:00
johnthetubaguyo/13:00
*** mohankumar has quit IRC13:01
alex_xuok, let us start the meeting13:01
alex_xu#topic update from summit13:01
*** openstack changes topic to "update from summit (Meeting topic: nova api)"13:01
*** gmann__ has joined #openstack-meeting-413:01
alex_xujohnthetubaguy: the only one priority task for the API is the query parameter validation?13:01
johnthetubaguythat sounds about correct13:02
johnthetubaguyalthough there is no separate freeze date this time around13:02
alex_xujohnthetubaguy: ok, cool, let us focus on it for this very short release cycle13:02
gmann__and proxy API and extension tide up things ?13:02
gmann__alex_xu: johnthetubaguy i can help on extension code cleanup if sdague need help on this13:03
johnthetubaguyso here is the thing...13:03
johnthetubaguycells v2 is kinda blocked by not having good validation on the filter/sort params for instances13:03
johnthetubaguyso thats a good thing to focus on13:04
johnthetubaguywe should still make progress on all those other loose ends and tidyups13:04
gmann__+113:04
johnthetubaguyincluding agreeing the capabilities API with API WG13:04
alex_xuso for the proxy API, we can continue image-metadata, due to the spec already merged, right?13:04
*** pmesserli has joined #openstack-meeting-413:05
johnthetubaguy#link http://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/deprecate-image-meta-proxy-api.html13:05
johnthetubaguyyeah13:05
alex_xuah, cool13:05
*** alij has joined #openstack-meeting-413:06
johnthetubaguythere is also this one: http://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/flavor-root-disk-none.html13:06
*** aderyugin has quit IRC13:06
alex_xuok, I didn't notice that one13:06
johnthetubaguyhttp://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/detach-boot-volume.html13:07
johnthetubaguyso there are some good features lined up there13:07
johnthetubaguygenerally fixing up the boot from volume situation, I guess13:07
alex_xucool13:08
johnthetubaguyso got distracted from summit update...13:08
gmann__yea, this seems nice. it will provide more nice management on volume things13:08
johnthetubaguy#link https://etherpad.openstack.org/p/ocata-nova-summit-api13:08
johnthetubaguy#link https://review.openstack.org/#/c/38655513:09
johnthetubaguywe should all review the above capabilities proposal13:09
alex_xujohnthetubaguy: for the query parameter validation, we only fix the validation for server list/detail, do we need to add validation for other api which have query parameters13:09
*** aderyugin has joined #openstack-meeting-413:09
johnthetubaguyalex_xu: not for the priority, but I think we should look at all the sort/filter params to start with13:09
gmann__alex_xu: johnthetubaguy are we going to do validation for SHOW api also in case some bogus id is mentioned in query URL ?13:10
alex_xujohnthetubaguy: i see now, server list/detail is priority, try others if we have time13:10
gmann__alex_xu: johnthetubaguy or something can be taken after wards13:10
johnthetubaguythats already done I assume?13:10
johnthetubaguyfor the instance uuid I mean13:10
gmann__seems no, i saw 1 tests in tempest sending special char as id and expecting 404 error13:11
alex_xui'm not sure we should validate that id, if people input bogus id, then API just return not found, that looks like correct13:11
gmann__johnthetubaguy: for SHOW server API i think no, we just try to fetch the given id13:11
gmann__alex_xu: i was thinking to return 400 and avoid to look into DB13:12
johnthetubaguyOK, so I am not sure which bit you mean13:12
johnthetubaguyanyways, feels less important that the filter/sort things13:12
*** zz_zz_ja has quit IRC13:12
gmann__like this. /v2.1/server?query id#$@@13:12
johnthetubaguygmann__: I think 404 is fine for an invalid uuid I guess13:12
gmann__johnthetubaguy: yea we can talk later13:12
johnthetubaguygmann: oh, thats the server list that we are talking about right?13:13
johnthetubaguythats just a filter13:13
johnthetubaguyshow is /server/<uuid> in my head13:13
gmann__sorry just SHOW yea, server/*&^13:13
johnthetubaguyanyways, do we have someone sorting out the specs for all the filter/sort params?13:14
johnthetubaguyalex_xu has the base one, I guess13:15
johnthetubaguy#link https://review.openstack.org/#/c/388518/13:15
alex_xuthat needs a separated spec?13:15
alex_xujohnthetubaguy: yea13:15
johnthetubaguyoh, maybe not, let me check13:15
johnthetubaguyah, so I think we need a spec for the microversion change to the server's API that adds all the parameter validation13:16
johnthetubaguywe also need to talk about what we are doing for older microversions, I think13:16
johnthetubaguyI think we just ignore things that are not allowed in the new list?13:17
gmann__johnthetubaguy: in old microversion ?13:17
alex_xujohnthetubaguy: yes, i think that is the first step, and without microversion13:17
alex_xuand fix this bug without microversion https://bugs.launchpad.net/nova/+bug/160903913:17
openstackLaunchpad bug 1609039 in OpenStack Compute (nova) "Should not be able to sort instances based on joined tables" [High,In progress] - Assigned to Zhenyu Zheng (zhengzhenyu)13:17
*** coolsvap has quit IRC13:18
alex_xustrict the validation won't be the ocata thing I guess?13:18
johnthetubaguyyeah, I suppose that could be a bug fix, but I would rather have a spec thats got the details13:18
alex_xujohnthetubaguy: ok13:18
johnthetubaguydoesn't need to be a long one13:19
johnthetubaguyjust think its good to agree the direction for the /servers/... changes for the parameter validation13:19
alex_xuKevin_Zheng: are you interesting on that spec ^ ?13:19
Kevin_Zhengsure i can try13:19
alex_xujohnthetubaguy: yea13:19
*** sshnaidm|afk is now known as sshnaidm13:19
alex_xuKevin_Zheng: thanks, free to ping if you need any help13:20
gmann__then we need to finalize the new allowed list first?13:20
Kevin_Zhengnp13:20
gmann__or fixing this bug for joined tables filter only13:20
*** ralonsoh has joined #openstack-meeting-413:20
johnthetubaguywell, the spec needs to have the list of allowed things really13:20
johnthetubaguyI would rather we do it properly, as this is blocking the cells work13:20
gmann__yea, +113:21
Kevin_Zhenggot it13:21
alex_xuyea13:21
johnthetubaguyit seems close, but maybe I am being optimistic13:22
alex_xuemm...when we have the detail list, then we will know whether we are optimistic13:23
johnthetubaguytrue :)13:23
alex_xu#link https://review.openstack.org/#/c/389003/13:24
alex_xuI update the patch, added the unittest and refactor the code. but I guess not hurry, maybe see more detail before merge13:24
*** matrohon has joined #openstack-meeting-413:25
alex_xuok, so...anything more we want to bring up?13:25
johnthetubaguyI think thats the main bits from the summit13:26
johnthetubaguyParameter validation, capabilities API WG spec, continue loose ends13:26
alex_xua lot of loose ends :)13:28
gmann__yea13:28
alex_xuyea, the nova API code is huge13:28
johnthetubaguyyup yup13:28
alex_xu#topic Open13:28
*** openstack changes topic to "Open (Meeting topic: nova api)"13:28
gmann__and lot number of APIs :)13:29
alex_xuso anything more want to bring up, otherwise let us end the meeting early13:29
johnthetubaguyI guess we need to update the etherpad13:29
johnthetubaguy#link https://etherpad.openstack.org/p/ocata-nova-priorities-tracking13:29
johnthetubaguyadd our new focus areas13:29
alex_xu#action Kevin_Zheng will bring up the spec about the server list query parameters13:29
johnthetubaguycool13:30
alex_xujohnthetubaguy: thanks13:30
alex_xuI will update the etherpad13:30
alex_xuso anything more?13:32
johnthetubaguyI am happy13:33
alex_xu3...13:33
gmann__not from my side13:33
alex_xu2..13:33
alex_xu1.13:33
alex_xuthanks all!13:33
alex_xu#endmeeting13:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:33
openstackMeeting ended Wed Nov  2 13:33:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:33
gmann__thanks all13:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-02-13.00.html13:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-02-13.00.txt13:33
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-02-13.00.log.html13:33
*** gmann__ has quit IRC13:33
*** singlethink has joined #openstack-meeting-413:33
*** klamath has joined #openstack-meeting-413:34
*** klamath has quit IRC13:34
*** klamath has joined #openstack-meeting-413:35
*** baoli_ has joined #openstack-meeting-413:36
*** baoli has quit IRC13:36
*** baoli has joined #openstack-meeting-413:37
*** alij has quit IRC13:37
*** alij has joined #openstack-meeting-413:37
*** baoli__ has joined #openstack-meeting-413:38
*** vhoward has joined #openstack-meeting-413:40
*** baoli_ has quit IRC13:41
*** baoli has quit IRC13:42
*** iyamahat has joined #openstack-meeting-413:42
*** baoli__ has quit IRC13:43
*** baoli has joined #openstack-meeting-413:44
*** atuly has joined #openstack-meeting-413:44
*** cdent has left #openstack-meeting-413:44
*** alij has quit IRC13:44
*** uxdanielle has joined #openstack-meeting-413:52
*** rbak has joined #openstack-meeting-413:56
*** haleyb has quit IRC13:57
*** baoli has quit IRC13:58
*** haleyb has joined #openstack-meeting-413:58
*** baoli has joined #openstack-meeting-413:59
*** yamahata has joined #openstack-meeting-413:59
*** GB21 has joined #openstack-meeting-414:01
*** bobh has joined #openstack-meeting-414:13
*** alij has joined #openstack-meeting-414:14
*** baoli has quit IRC14:15
*** mohankumar has joined #openstack-meeting-414:15
*** baoli has joined #openstack-meeting-414:15
*** baoli_ has joined #openstack-meeting-414:16
*** Guest37512 has quit IRC14:18
*** alij has quit IRC14:19
*** rods has joined #openstack-meeting-414:20
*** baoli has quit IRC14:20
*** julim has quit IRC14:31
*** baoli_ has quit IRC14:32
*** caboucha has joined #openstack-meeting-414:34
*** Rockyg has joined #openstack-meeting-414:35
*** irenab_ has quit IRC14:36
*** alij has joined #openstack-meeting-414:36
*** alij has quit IRC14:36
*** spotz_zzz is now known as spotz14:37
*** julim has joined #openstack-meeting-414:37
*** atuly has quit IRC14:39
*** jed56 has joined #openstack-meeting-414:43
*** Rockyg has quit IRC14:46
*** Rockyg has joined #openstack-meeting-414:47
*** tsufiev has joined #openstack-meeting-414:51
*** tsufiev has left #openstack-meeting-414:52
*** haleyb has quit IRC14:53
*** haleyb has joined #openstack-meeting-414:54
*** syed_ has joined #openstack-meeting-414:55
*** jamemcc has joined #openstack-meeting-414:56
*** bklei has joined #openstack-meeting-414:56
*** Julien-zte has joined #openstack-meeting-414:57
*** GeraldK has joined #openstack-meeting-414:58
*** ad_rien_ has joined #openstack-meeting-414:58
*** mohankumar has quit IRC14:59
dtardivel#startmeeting watcher15:00
openstackMeeting started Wed Nov  2 15:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is dtardivel. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: watcher)"15:00
openstackThe meeting name has been set to 'watcher'15:00
dtardivelhi15:00
*** vincentfrancoise has joined #openstack-meeting-415:00
*** tmetsch has joined #openstack-meeting-415:00
jamemccHi15:00
*** cdelatte has quit IRC15:01
tmetschhi15:01
vincentfrancoiseo/15:01
vincentfrancoiseToday's agenda https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F02.2F201615:01
*** PerfectChaos has joined #openstack-meeting-415:01
jed56Hi15:01
sballe_hi15:01
*** vhoward has quit IRC15:02
serverascodehi are you sure this meeting is now? I think the ops telecom/nfv meteing is in here now unless I have the time wrong15:02
dtardivelacabot, our PTL, is not available for the meeting. vincentfrancoise and me will lead it.15:02
serverascodewas 14:00 UTC not an hour ago?15:02
dtardiveloups15:02
GeraldKi also had expected the OpenStack Operators Telcom/NFV Functional Team bi-weekly meeting on this channel at this point in time15:02
*** talonx has joined #openstack-meeting-415:02
PerfectChaosHi~ I'm with serverascode on this one~15:02
dtardivelsorry, we close it15:03
vincentfrancoisevfrancoise: time change...15:03
dtardivel#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
*** pmesserli has quit IRC15:03
openstackMeeting ended Wed Nov  2 15:03:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
serverascodeok sorry, but yeah you missed it by an hour15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-02-15.00.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-02-15.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-02-15.00.log.html15:03
serverascode#startmeeting operators_telco_nfv15:03
openstackMeeting started Wed Nov  2 15:03:29 2016 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:03
openstackThe meeting name has been set to 'operators_telco_nfv'15:03
serverascode#topic roll call15:03
*** openstack changes topic to "roll call (Meeting topic: operators_telco_nfv)"15:03
*** pmesserli has joined #openstack-meeting-415:03
serverascodehi all!15:03
* PerfectChaos waves15:03
*** vincentfrancoise has left #openstack-meeting-415:04
ad_rien_o/15:04
ad_rien_Hi15:04
GeraldKHi15:04
jamemccHello15:04
serverascodeok great, we have the most ppl ever :)15:04
serverascode#link https://etherpad.openstack.org/p/BCN-ops-telcom-nfv-team15:05
serverascode^ that's the session from last week at at the summit15:05
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:05
serverascode^ that's our agenda page15:05
serverascodeI only have one real thing on the agenda right now, feel free to add to it if you have other things to discuss15:05
serverascodethe one thing was our list of potential projects15:06
serverascodeanyone have any comments/suggestions/ideas before I go into that topic?15:06
jamemccNo - good organization Curtis - lets push forward15:06
serverascodeok15:07
serverascode#topic Potential Projects15:07
*** openstack changes topic to "Potential Projects (Meeting topic: operators_telco_nfv)"15:07
serverascodeso the idea was to follow the large deployment teams lead and fiind a medium to long term project to shepherd through the openstack ecosystem15:08
serverascodethey worked on getting network segments into neutron and were pretty successful15:08
ALUVialo/  (back to lurk mode)15:09
serverascodebasically they found a common feature or issue and worked on it over time15:09
*** matrohon has quit IRC15:09
serverascodeso we have a list of things from the summit at that link above15:09
serverascodeanyone see anything in particular that jumps out as needing to be solved?15:09
GeraldKNFVI benchmarking ref.platform got +415:10
GeraldKRolling/live upgrade has +315:10
serverascoderight there was a lot about benchmarking in that list15:10
serverascodehow about the people in the meeting today? what are your issues or requirements?15:11
ad_rien_Is there a specific use-case that can serve as a guide line ?15:11
GeraldKupgrading is something we (DOCOMO) would be interested in15:12
ad_rien_We can identify a lot of challenges but with a common theme it might be easier to focus and make priorities between those challenges15:12
GeraldKcurrently, we skip releases and would like to improve on this15:12
serverascoderight, and it's not really possible anymore, afaik, to skip releases15:13
serverascodead_rien: what's a common theme? like "benchmarking" is a theme? is that what you mean?15:13
ad_rien_From all the challenges I can see on the etherpad15:13
GeraldK#link http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/rolling-upgrades.html PWG user story on rolling upgrades15:14
ad_rien_I get the feeling that some are rather general (i.e. upgrade is an interesting challenge but not specifc to the NFV WG If I'm right)15:14
PerfectChaosRolling upgrades strike me as something that are generally going to be of interest to anybody15:14
PerfectChaos...yeah, exactly what ad_rien_ just said =315:14
ad_rien_So this is my point.15:14
ad_rien_There are several challenges, all look really interesting but it might make sense to identify the ones that are really specific to the NFV use-cases15:15
GeraldKin contrast to other openstack users, Telcos might prefer not to have very frequent rolling upgrades.15:15
PerfectChaosI guess the thing to consider is - if it's a general problem there are more likely to be other people elsewhere working on them.15:15
GeraldKgot your point.15:16
PerfectChaosWhereas NFV-specific problems are less likely to have people who aren't use out there driving to get them solved15:16
ad_rien_PerfectChaos:  yes exactly my point15:16
*** eyalb has quit IRC15:16
serverascodeok, it seems like there is a bit of a consensus that working on upgrades might not be NFV specific enough15:17
serverascodethat leaves us with benchmarking as a theme, at least in terms of what has been mentioned today15:17
ad_rien_It might become critical/specific but later.15:17
jamemccJust to give it a little more insight I think the possible more NFV related use case comes through with the massive cloud assumption15:18
*** pmesserli has quit IRC15:18
PerfectChaosWell, if the main problems NFV/Telecoms folks are all general problems, then we shouldn't just discard the idea of looking into those. It's down to what those people will find the most useful, right?15:18
*** pmesserli has joined #openstack-meeting-415:18
jamemccIf you go with the assumption that the NFV/Telcom brings with it the massive cloud - then the upgrade of massive cloud has addtional challenges15:18
*** tmetsch has left #openstack-meeting-415:19
jamemccThat said - I think somethign closer to Telcom/NFV is more appropriate15:19
* PerfectChaos nods15:19
ad_rien_Maybe we should start by simple actions/challenges and then increase the complexity step by step.15:19
ad_rien_ForI agree with jamemcc remark but this mean that first you should be able to have an Openstack deployment accros distinct locations15:20
ad_rien_s/ForI/I sorry for the typo15:20
ad_rien_Is there a specific NFV use-case that can help us in our exchange ?15:21
jamemcc@ ad_rien yeah - agreed if I follow - So back to defining the reference implementation?15:21
ad_rien_yes15:21
*** woodster_ has joined #openstack-meeting-415:21
serverascodeby reference implementation...what does that mean?15:22
serverascodeis that kind of like what OPNFV is doing?15:22
ad_rien_What is the OpenStack deployment architecture if you want to address NFV use-cases? How can you instantiate such an architecture?15:22
serverascodeah, ok15:22
serverascodeAt work we have been trying to define NFVi, specifcally around features15:23
ad_rien_is it deployed in one location or across several locations? where are the compute nodes that host the VMs? The control plane? …15:23
ad_rien_serverascode: NFVi ?15:23
ad_rien_i for Infrastructure ?15:24
*** SergeM has joined #openstack-meeting-415:24
serverascodemy impression is that under the ETSI definition, OpenStack is NFV infrastrcture (NFVi) and a VIM15:24
serverascodeVIM = virtualized infrastructure manager15:24
ad_rien_yepp15:25
ad_rien_thanks15:25
ad_rien_so that also something that can help the OpenStack community15:25
serverascodeand it's hard b/c it's really a spectrum of requirements15:25
ad_rien_I get the feelings that our words (i.e. from the network community vs the distributed computing community) differ sometimes15:25
GeraldKETSI NFV003 defines NFVI: totality of all hardware and software components that  build up the environment in which VNFs are deployed15:25
GeraldKso it's more than Openstack and also includes the hardware15:25
serverascodeok thanks GeraldK15:26
GeraldKit also could have multiple VIMs15:26
ad_rien_but you can have different ways to deliver such a NFVi15:26
ad_rien_see in the pad line 3715:26
*** bklei has quit IRC15:27
ad_rien_either a brokering approach where an orchestrator operates several VIMs or a bottom up approach15:27
ad_rien_where OpenStack becomes cooperative enough to be able to natively federate distinct data centers/locations15:28
serverascodeinteresting, so are we discussing reference implementations right now? kind of?15:28
PerfectChaosI think we are, kind of.15:28
ad_rien_I would say yes (at least from my side ;))15:28
GeraldKI believe Telco's want to stay in control so prefer the brokering approach15:29
PerfectChaosThe first step would presumably be deciding how deep the reference implementation goes15:29
ad_rien_There should be different scenarios, a first action can consist of identifying them15:29
serverascodeI almost feel like in order to get any work done we first have to define at least one or two reference implmentations15:29
ad_rien_GeraldK: we work with Orange Labs and BT and the choice is unclear. We are trying to see what are the pros/cons of the different deployment strategies.15:29
serverascodeso that we at least know what we are talking about to one another15:30
GeraldKand then, how different would this be to the reference platform developed by OPNFV? Or, how could we collaborate with OPNFV in it?15:30
serverascodeI was hoping, at some level, that this group could work as a bridge between OPNFV and OpenStack Operators doing NFV15:30
GeraldKto work on the main topic of "NFVI benchmarking" we may not need our own reference implementation, do we?15:31
ad_rien_serverascode:  yes this makes sense15:31
serverascodeno I don't think we need to make our own definition, but we'd have to have some common language to do work in this group15:32
serverascodeok, so we are about 30 minutes into our hour long meeting15:33
* ad_rien_ is looking on google for information on the reference architecture of a OPNFV deployment15:33
serverascodeI think we have discussed three themes so far: 1) upgrades 2) benchmarking and 3) reference implementation definition15:35
GeraldKad_rien_, maybe a good document to check current status of OPNFV is http://artifacts.opnfv.org/opnfvdocs/colorado/docs/documentation/index.html15:36
ad_rien_Maybe a stupid question/comment but is there a link somewhere to clearly understand the differences between OPNFV and OpenStack in terms of internal mechanisms15:36
GeraldKnot sure I get your question. OPNFV is using OpenStack.15:36
ad_rien_ok15:36
ad_rien_Let me reword, what does OPNFV bring?15:37
serverascodethat is a question I hear quite often :)15:37
ad_rien_from my understanding15:37
PerfectChaosBasically, they bring together various pieces that combined make an NFVI. One of those pieces is OpenStack.15:38
ad_rien_OPNFV enables administrators to program the network active equipments (in somehow, an advanced Neutron component)15:38
*** mmedvede has quit IRC15:38
ad_rien_so the reference architecture can be several openstack instances and one OPNFV to deliver a NFVi ?15:39
GeraldKthere are several goals: integrate various upstream projects, act as intermediate body between ETSI NFV work and OpenStack, join forced to push new features to upstream projects, ...15:39
GeraldKad_rien_, OPNFV builds a reference platform including OpenStack, ODL, and others15:40
*** uxdanielle has quit IRC15:40
ad_rien_ok15:40
GeraldKthere was a nice handout on OPNFV in the Summit. let me see if I can find it online15:41
ad_rien_but If I'm correct the working group focused on NFV within the OpenStack ecosystem?15:41
ad_rien_so do we care about ODL and others :-) ?15:41
*** syjulian has left #openstack-meeting-415:41
*** tonytan4ever has joined #openstack-meeting-415:42
serverascodeI think we do have to be aware of SDN systems like ODL, and OVN15:42
*** jovon has joined #openstack-meeting-415:42
serverascodecertainly some NFV deployments will rely on functionality that only SDN can provide15:42
serverascodebut not all deployments will need that. Then there are projects like neutron-sfc15:43
serverascodeoh and vlan aware virtual machines which was just blogged on superuser15:43
ad_rien_serverascode:  sorry for my remarks, it was a bit provocative. I agree we should be aware but we should also focus on OpenStack, shouldn't we?15:43
serverascode#link http://superuser.openstack.org/articles/four-opens/15:43
serverascodead_rien: no worries, not provocative at all15:43
jamemccAgred focus inwards toward OpenStack and represent combined knowledge interest of OPNFV and SDN15:44
jamemccand ETSI15:44
ad_rien_AFAIK, there is not reference architecture for delivering a NFVi with OpenStack, maybe we can try to identify how we can progress on that point?15:44
PerfectChaosSo... since there are a -lot- of different variables which could vary wildly between use-cases even within NFV/telecom use, we'd have a hard time picking one reference implementation which would be consistently useful, I think.15:45
ad_rien_at least as a starting step?15:45
GeraldK#link http://go.linuxfoundation.org/l/6342/2016-10-11/3jhnwr/6342/158966/OPNFV_WhitePaper_Paving_Way_OpenSource_NFV_101016.pdf WhitePaper on OPNFV15:45
PerfectChaosSince people were interested in benchmarking NFVI, would it instead make sense to be thinking about frameworks/infrastructure with which we might be able to test/verify/benchmark different NFVIs?15:45
GeraldKI couldn't find the handout, but the figure are also available in the whitepaper15:46
serverascodeI do think service function chaining (SFC) will probably be a common feature, and with neutron-sfc you don't technically need a 3rd party SDN controller15:46
serverascodeso we could do a reference arch that supports neutron-sfc15:47
ad_rien_We (at Inria) are interested by performing such evaluations15:47
serverascodealso there is some interesting work around "neutron router flavors"15:47
serverascode#link https://specs.openstack.org/openstack/neutron-specs/specs/newton/multi-l3-backends.html15:47
jamemccI think to define reference architecture and combinging wiht what is said about focusing on OpenStack - w are saying what openstack components are included and in what arrangement to get basic NFVi working.15:47
ad_rien_We have access to the Grid'5000 testbed so we can perform experiments in a quite easy manner15:48
ad_rien_jamemcc:  +115:48
jamemccAnd from my perspective this would be across at least 3 separate clouds though perhaps form testing and benchmarking we ought to pick a higher #15:48
GeraldKneutron-sfc is also being discussed in OPNFV (https://jira.opnfv.org/browse/VFNGRAPH-3) but I am not aware of any details on this project15:49
GeraldKIMHO this topic requires some discussion on collaboration with OPNFV. I am sure they would be interested on some collaboration.15:49
serverascodeok, interesting, so I'm feeling a bit of consensus around some kind of "vanilla" or "minimal" NFVi reference architecture, perhaps including neutron-sfc?15:50
*** mmedvede has joined #openstack-meeting-415:50
ad_rien_+115:50
ad_rien_I think I should be able (or at least give a try) to add Orange folks in the loop15:50
*** zz_ja has joined #openstack-meeting-415:51
serverascodeok, so we have about 8 min left15:51
serverascodewhere should we go from here? do we agree this is one area to explore?15:51
GeraldKthe goal should be to get some benchmarking or similar, but not to have "just" a reference architecture.15:51
jamemccAgreed15:52
jamemccand likes it15:52
serverascodeok, and do you think it would be benchmarking some kind of "vanilla" or "minimal" NFVi based on OpenStack projects?15:52
serverascodeso neutron-sfc for example15:53
ad_rien_First step can be a reference architecture, Second step a scenario that inclue neutron-sfc  (maybe we can push such a scenario in Rally) and Three perform some evaluations?15:53
PerfectChaosSee above about benchmarking frameworks - what about, say, coming up with some standard set of benchmarking tests for those evaluations?15:53
PerfectChaos(which could subsequently be run against a different NFVI to see how it performs in comparison, if one was so inclined)15:53
GeraldKwhat I mean is: create a set of (standardized) benchmarks and test those on a reference implementation. but the focus would be the benchmarks.15:53
PerfectChaosRight. Sounds like we're on the same page, then.15:54
GeraldKagreed15:54
*** krtaylor has quit IRC15:54
serverascodecool, there is also a performance working group that we could team up with15:54
ad_rien_PerfectChaos:  can you point once again the link regarding the benchmark ?15:54
serverascodethat would fit in well with the user committee wanting more communication between openstack working gorups15:55
serverascodewe could collaborate with OPNFV and the performance team15:55
serverascodeok so can I say something like we agree that:15:55
ad_rien_We are involved in the performance WG at Inria. If I'm correct here we do not really talk about performance but more on functional benchmarks ?15:55
PerfectChaosad_rien_: Hmm? I didn't have any links on benchmarks?15:55
serverascodeah ok functional vs performance15:56
ad_rien_"PerfectChaos: See above about benchmarking frameworks " - see above ?15:56
PerfectChaosMy assumption was that it would include both functional and performance benchmarks...15:56
ad_rien_ok15:56
*** andymaier has joined #openstack-meeting-415:57
PerfectChaosad_rien_: Oh, I was just referring back to my previous comment "would it instead make sense to be thinking about frameworks/infrastructure with which we might be able to test/verify/benchmark different NFVIs?"15:57
PerfectChaosTo which I think the answer is "we should be thinking about both".15:58
serverascodeok, can I say something like: "We agree that this working group will develop and perform benchmarks on a NFVi reference architecture which we will determine in future meetings"15:58
PerfectChaosThat seems like a good point to start from15:58
GeraldKwhat would be the timeframe for this? and would we focus on this one only or allow a second topic?15:58
*** tonytan4ever has quit IRC15:58
GeraldKbut definitely a good starting point15:58
serverascodeI think we'd have to come up with a timeframe in future meetings15:59
*** tonytan4ever has joined #openstack-meeting-415:59
serverascodewe could certainly work on more than one thing15:59
serverascodeonly about a minute left15:59
GeraldKsure. but roughly? 1 year?15:59
serverascodeprobably something like that, at least a couple releases15:59
serverascodesorry I have to end the meeting!15:59
GeraldKokay15:59
GeraldKbye16:00
*** dkusidlo has joined #openstack-meeting-416:00
serverascode#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov  2 16:00:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-02-15.03.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-02-15.03.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-02-15.03.log.html16:00
serverascodethanks everyone! I'll send an email to the list16:00
serverascodealso I might email the user commitee list too16:00
ad_rien_so talk to you next week ?16:00
serverascodetwo weeks from now currently16:00
ad_rien_I mean sorry in two weeks ?16:00
ad_rien_ok16:00
serverascodethanks again!16:00
ad_rien_thanks for chairing16:00
*** SergeM has quit IRC16:02
*** uck has joined #openstack-meeting-416:03
*** PerfectChaos has quit IRC16:08
*** limao has joined #openstack-meeting-416:08
*** wirehead_ has joined #openstack-meeting-416:10
*** armax has joined #openstack-meeting-416:14
*** larsks has joined #openstack-meeting-416:16
*** baoli has joined #openstack-meeting-416:22
*** julim has quit IRC16:24
*** klamath has quit IRC16:29
*** klamath has joined #openstack-meeting-416:35
*** klamath has quit IRC16:35
*** klamath has joined #openstack-meeting-416:35
*** numans has quit IRC16:36
*** mmedvede has quit IRC16:37
*** nkrinner is now known as nkrinner_afk16:42
*** baoli has quit IRC16:42
*** baoli has joined #openstack-meeting-416:42
*** mmedvede has joined #openstack-meeting-416:45
*** admcleod1 is now known as admcleod16:50
*** tonytan4ever has quit IRC16:50
*** tonytan4ever has joined #openstack-meeting-416:51
*** GeraldK has quit IRC16:51
*** belmoreira has quit IRC16:53
*** celebdor has joined #openstack-meeting-416:58
*** krtaylor has joined #openstack-meeting-416:58
*** celebdor has quit IRC16:59
*** celebdor has joined #openstack-meeting-416:59
*** sshnaidm is now known as sshnaidm|afk17:01
*** mjturek has joined #openstack-meeting-417:06
*** limao has quit IRC17:06
*** talonx has quit IRC17:18
*** harlowja has quit IRC17:21
*** uck_ has joined #openstack-meeting-417:27
*** uck has quit IRC17:27
*** pc_m has joined #openstack-meeting-417:33
*** baoli has quit IRC17:38
*** julim has joined #openstack-meeting-417:43
*** Julien-zte has quit IRC17:44
*** harlowja has joined #openstack-meeting-417:44
*** Julien-zte has joined #openstack-meeting-417:45
*** Julien-zte has quit IRC17:45
*** Julien-zte has joined #openstack-meeting-417:45
*** hemanthm is now known as hemanthm|lunch17:46
*** Julien-zte has quit IRC17:46
*** Julien-zte has joined #openstack-meeting-417:46
*** Julien-zte has quit IRC17:47
*** Julien-zte has joined #openstack-meeting-417:47
*** Julien-zte has quit IRC17:47
*** Julien-zte has joined #openstack-meeting-417:48
*** dkusidlo has left #openstack-meeting-417:48
*** Julien-zte has quit IRC17:48
*** reedip_ has joined #openstack-meeting-417:49
*** Julien-zte has joined #openstack-meeting-417:49
*** Julien-zte has quit IRC17:49
*** Julien-zte has joined #openstack-meeting-417:50
*** Julien-zte has quit IRC17:50
*** vhoward has joined #openstack-meeting-417:53
*** marst has joined #openstack-meeting-417:54
*** ralonsoh has quit IRC18:01
*** Jeffrey4l has quit IRC18:02
*** spotz is now known as spotz_zzz18:04
*** ad_rien_ has quit IRC18:14
*** sshnaidm|afk is now known as sshnaidm18:18
*** GB21 has quit IRC18:24
*** andymaier has quit IRC18:24
*** dasanind_ has joined #openstack-meeting-418:28
*** pc_m has left #openstack-meeting-418:36
*** jed56 has quit IRC18:37
*** hemanthm|lunch is now known as hemanthm18:42
*** marst has quit IRC18:42
*** baoli has joined #openstack-meeting-418:45
*** mdorman has joined #openstack-meeting-418:45
*** matrohon has joined #openstack-meeting-418:50
*** matrohon has quit IRC18:50
*** portdirect is now known as portdirect_away18:51
*** andymaier has joined #openstack-meeting-419:05
*** andymaier has quit IRC19:06
*** celebdor has quit IRC19:07
*** piet has joined #openstack-meeting-419:10
*** wirehead_ has quit IRC19:12
*** wirehead_ has joined #openstack-meeting-419:13
*** ad_rien_ has joined #openstack-meeting-419:16
*** marst has joined #openstack-meeting-419:23
*** uxdanielle has joined #openstack-meeting-419:26
*** mmedvede has quit IRC19:28
*** piet has quit IRC19:30
*** uck_ has quit IRC19:36
*** spotz_zzz is now known as spotz19:36
*** uxdanielle has quit IRC19:42
*** dave-mccowan has quit IRC19:48
*** dave-mcc_ has joined #openstack-meeting-419:48
*** ad_rien_ has quit IRC19:49
*** rtheis_ has quit IRC19:49
*** dtardivel has quit IRC19:54
*** matrohon has joined #openstack-meeting-419:54
*** openstack has joined #openstack-meeting-420:00
*** ChanServ sets mode: +o openstack20:00
*** mmedvede has joined #openstack-meeting-420:04
*** piet has joined #openstack-meeting-420:07
*** iyamahat has quit IRC20:08
*** reedip_ has quit IRC20:09
*** devananda has quit IRC20:12
*** reedip_ has joined #openstack-meeting-420:13
*** mattt has joined #openstack-meeting-420:19
*** mattt has left #openstack-meeting-420:20
*** marst has quit IRC20:25
*** marst has joined #openstack-meeting-420:25
*** uck has joined #openstack-meeting-420:29
*** devananda has joined #openstack-meeting-420:31
*** vhoward has quit IRC20:34
*** reedip_ has quit IRC20:35
*** iyamahat has joined #openstack-meeting-420:36
*** bobh has quit IRC20:37
*** tonytan4ever has quit IRC20:42
*** matrohon has quit IRC20:43
*** matrohon has joined #openstack-meeting-420:43
*** marst_ has joined #openstack-meeting-420:44
*** uck has quit IRC20:44
*** uck has joined #openstack-meeting-420:44
*** marst has quit IRC20:47
*** matrohon has quit IRC20:51
*** matrohon has joined #openstack-meeting-420:51
*** matrohon has quit IRC20:52
*** matrohon has joined #openstack-meeting-420:52
*** matrohon has quit IRC20:53
*** matrohon has joined #openstack-meeting-420:53
*** krtaylor has quit IRC20:55
*** JRobinson__ has joined #openstack-meeting-421:00
JRobinson__hello all, the User Guides team meeting will start now.21:01
JRobinson__I just have one key agenda item to go through today.21:01
*** matrohon has quit IRC21:01
JRobinson__#startmeeting docuserguides21:01
openstackMeeting started Wed Nov  2 21:01:52 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: docuserguides)"21:01
openstackThe meeting name has been set to 'docuserguides'21:01
*** matrohon has joined #openstack-meeting-421:02
JRobinson__At the recent Ocata summit, one of the Docs working groups talked about the legacy commands in the User guides21:02
JRobinson__The etherpad has more details21:03
JRobinson__#link https://etherpad.openstack.org/p/BCN-Docs-UserGuidesWG21:03
JRobinson__the docs PTL also sent out a summary of each working group session to the docs mailing list.21:03
JRobinson__To follow up on the email, the fortnightly User Guide meeting will eventually change to a monthly team meeting.21:07
JRobinson__#topic Legacy to OpenStack client commands21:07
*** openstack changes topic to "Legacy to OpenStack client commands (Meeting topic: docuserguides)"21:07
JRobinson__With the summit recap completed, the issue that needs attention is the legacy command changes21:07
*** uck has quit IRC21:07
*** uck has joined #openstack-meeting-421:08
JRobinson__#link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Legacy_to_OpenStack_command_conversion_table21:09
JRobinson__I have began setting up the checklist table mentioned at Summit.21:09
JRobinson__So far, its Admin guide files21:09
JRobinson__I started with files that already have OpenStack client commands in them21:09
JRobinson__I then moved to step two21:10
JRobinson__Searching through each file for legacy commands21:10
JRobinson__then adding the file to the checklist, along with the commands, and their line location in file.21:11
*** qwebirc42724 has joined #openstack-meeting-421:11
JRobinson__This way, there is an accurate picture of what needs to change.21:11
JRobinson__#topic Open Discussion21:11
*** openstack changes topic to "Open Discussion (Meeting topic: docuserguides)"21:11
JRobinson__Any questions or comments on the process, contact the docs mailing list, or ping me on irc.21:12
*** caboucha has quit IRC21:13
JRobinson__I'll close up this brief recap meeting.21:13
JRobinson__#action JRobinson__ to continue to update table with Admin and User Guide commands.21:14
JRobinson__#endmeeting21:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:14
openstackMeeting ended Wed Nov  2 21:14:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-11-02-21.01.html21:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-11-02-21.01.txt21:14
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-11-02-21.01.log.html21:14
*** sambetts is now known as sambetts|afk21:23
*** dave-mcc_ has quit IRC21:24
*** thorst has quit IRC21:31
*** julim has quit IRC21:40
*** julim has joined #openstack-meeting-421:40
*** ad_rien_ has joined #openstack-meeting-421:46
*** bobh has joined #openstack-meeting-421:50
*** uxdanielle has joined #openstack-meeting-421:50
*** harlowja has quit IRC22:02
*** julim has quit IRC22:11
*** bobh has quit IRC22:12
*** uck has quit IRC22:15
*** matrohon has quit IRC22:18
*** matrohon has joined #openstack-meeting-422:19
*** ad_rien_ has quit IRC22:19
*** klamath has quit IRC22:22
*** jovon has quit IRC22:27
*** mdorman has left #openstack-meeting-422:28
*** flaper87 has quit IRC22:29
*** uck has joined #openstack-meeting-422:30
*** matrohon has quit IRC22:32
*** matrohon has joined #openstack-meeting-422:32
*** pmesserli has quit IRC22:35
*** klamath has joined #openstack-meeting-422:35
*** jingting has quit IRC22:36
*** marst_ has quit IRC22:36
*** jingting has joined #openstack-meeting-422:37
*** hemanthm is now known as hemanthm|away22:38
*** matrohon has quit IRC22:42
*** matrohon has joined #openstack-meeting-422:42
*** qwebirc42724 has quit IRC22:43
*** syed_ has quit IRC22:45
*** singlethink has quit IRC22:47
*** rbak has quit IRC22:47
*** matrohon has quit IRC22:54
*** spotz is now known as spotz_zzz22:59
*** klamath has quit IRC23:00
*** piet has quit IRC23:03
*** david-lyle has quit IRC23:04
*** harlowja has joined #openstack-meeting-423:08
*** thorst has joined #openstack-meeting-423:13
JRobinson__Hello all, The second user guide meeting set for the APAC timezone is ordinarly scheduled to happenin in about 12 minutes,23:17
JRobinson__I'm cancelling the meeting for this fortnight.23:17
JRobinson__The US meeting minutes are available on the User Guide team page:23:18
*** thorst has quit IRC23:18
JRobinson__https://wiki.openstack.org/wiki/User_Guides#MeetingLogs23:18
*** s3wong has joined #openstack-meeting-423:20
*** bobmel_ has quit IRC23:21
*** david-lyle has joined #openstack-meeting-423:30
*** dave-mccowan has joined #openstack-meeting-423:31
*** JRobinson__ has quit IRC23:33
*** uxdanielle has quit IRC23:43
*** uck has quit IRC23:56
*** uck has joined #openstack-meeting-423:57

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