18:00:21 #startmeeting gluon 18:00:22 Meeting started Wed Mar 22 18:00:21 2017 UTC and is due to finish in 60 minutes. The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:25 The meeting name has been set to 'gluon' 18:00:34 #topic Roll Call 18:00:44 #info Bin Hu 18:01:13 #info Paul Carver 18:01:31 Hi Paul 18:01:36 hi 18:01:51 #info Kamil Renczewski 18:02:02 Hi Kamil 18:02:08 Hi Bin 18:02:40 Georg is on a business trip, so he will miss the meeting today 18:02:54 Hi everyone 18:02:58 #info JinLi 18:03:05 Hi Jin 18:03:06 Hi All! This is Robert 18:03:15 #info Admin Update 18:03:23 #topic Admin Update 18:03:34 Hi Robert 18:04:18 #info No update 18:04:34 #topic Bug Fix Patch 18:04:41 Let's discuss an easy one 18:05:07 #info Jin submitted a patch to remove unused import statements 18:05:22 #link https://review.openstack.org/#/c/446776/ 18:05:35 Any comments? 18:06:09 #info Tin Lam commented, and Jin uploaded a patchset 2 18:06:45 Any objection to approve and mege it? 18:07:34 #info Team consensus is to approve and merge it 18:07:42 #info Bin will take the action 18:09:08 #topic PoC Status 18:09:34 #info (1) Lab Status 18:10:00 #info Gluon was deployed to Pharos Lab in Germany, and basic verification was done 18:10:28 #info Kamil is working on deploying Mechanism Driver for Contrail in the same OpenStack environment 18:11:03 #info to achieve the interoperability between Contrail and other SDN-Cs through Gluon 18:11:18 Kamil, any more update? 18:11:26 I've fixed the env 18:11:37 great 18:11:44 but Juniper node is still as deleted 18:12:13 Georg suggest tu create another VM 18:12:16 Do you mean the Compute Node or the virt-manager node? 18:12:26 I am nt sure how much resources I can assign to it 18:12:36 The compute node 18:12:57 You can set up the virt-manager node first for Contrail 18:13:20 I was trying to re-add the compute node, but Fuel complains about not able to sync time 18:13:29 I am sending you the spreadsheet that we discussed in December regarding resources for each SDN-C, including Contrail 18:13:37 I see. 18:13:40 It is probably related to network config issure that I can't explain 18:13:56 Thanks 18:13:59 We are bringing up ONOS in the Huawei node, and will need to work with Georg on getting a BGP session with ODL 18:14:57 Ok, so if Contrail is to use separate node outsize the fuel env 18:15:16 then does we need its compute node? 18:17:26 Let me send you another architecture diagram of lab setup 18:18:49 Kamil, I sent you both the lab architecture diagram and sheet of resource allocation 18:19:01 Got it, thank you 18:19:41 Under the same openstack environment, each SDN-C will run on a VM, which is managed by virt-manager 18:20:19 So SDN-C is outside of OpenStack environment. For example, Contrail is running separate on a VM of virt-manager 18:20:47 But Contrail's Mechanism Driver should be deployed in OpenStack Controller node 18:20:56 correct 18:21:29 Then Mechanism Driver will work with Contrail that runs on a separate VM 18:22:37 Compute Node, which is part of OpenStack environment, will host the Guest VM, which attaches ports and networks managed by SDN-C 18:23:01 Ok, got it 18:23:58 For example, user creates port and network via Contrail, and then boot a VM with that port and network on the Compute Node assigned to Contrail 18:24:39 The assignment of Compute Node is just to make sure that each participant has its resource to boot Guest VM 18:24:58 And not to over use others' resources 18:25:10 OK 18:25:54 Ideally, we shouldn't care about Compute nodes. Whoever needs to boot VM, just boot it and let Nova to schedule it. 18:26:08 But our resources are very limited (CPU, RAM and disk) 18:27:04 So we have such resource allocation to make sure everyone has minimum resources to run its SDN-C and Guest VM within our very limited resource pool 18:27:50 Kamil, anything else do you need in order to continue and complete setup of Contrail with Gluon? 18:28:07 I think that is all 18:28:11 Thanks 18:28:24 Great, thank you Kamil. and look forward to hearing your good news 18:28:57 Then once Georg is back, he may help with the Compute Node issue. 18:29:35 #info Kamil gets necessary information to continue and complete the setup 18:29:46 Robert, are you still here? 18:29:58 How about your 2nd lab in Santa Clara? 18:31:29 Looks like we lost Robert 18:32:14 #info Status of 2nd Lab in Santa Clara is unknown. Will follow up with Robert 18:32:59 #info (2) L3VPN API - Parameter List for BGP Peering 18:33:22 #info Georg is on business trip. Will follow up with Georg once he is back to office 18:33:41 #info (3) SFC YAML 18:34:21 #info Georg mentioned in OPNFV NetReady meeting last week that someone has worked on a simple SFC YAML 18:34:35 #info We need more information. Need to follow up with Georg 18:34:54 #info (4) P2P YAML 18:36:04 #info Sukhdev and Ian had a very good discussion in Juniper on last Friday. Sukhdev will document the solution, which will naturally supports P2P 18:36:15 #info (5) Contrail Status 18:36:25 #info We already covered it. Thank you Kamil 18:36:43 #info (6) PoC Scenario Description 18:36:51 #info We already discussed it last week 18:37:00 #link http://eavesdrop.openstack.org/meetings/_gluon/2017/_gluon.2017-03-15-18.00.html 18:37:13 #info Bin will document it and put it on wiki 18:37:25 Hi Folks 18:37:31 Hi Sukhdev 18:37:48 Heard a ping on my laptop did not know what it was :-) 18:38:35 I mentioned that you and Iab had a very good discussion on last Friday, and you will document the solution. 18:38:42 An update of the 2nd lab: I am putting hardware together and will configure the topology next 18:38:59 I used your name "Sukhdev" in my message 18:39:18 perhaps it generated a "ping" in your laptop? 18:39:48 haleyb : yes - that was it 18:39:56 Great, thank you Robert 18:40:02 bh526r : If you need me, I will be around 18:40:25 Sure. I know you are busy, and will document it next week. So don't worry :) 18:42:00 #info Robert is back, and reported that he is putting hardware together for 2nd lab in Santa Clara, and will configure the topology next 18:42:55 OK, we have several items to follow up with Georg. 18:43:21 #topic Planning for Gluon Pike Release 18:43:26 #link Planning for Gluon Pike Release 18:43:36 #link https://wiki.openstack.org/wiki/Gluon/Tasks-Pike 18:44:18 #info All please review and sign up 18:44:49 #topic Planning for Forum in Boston 18:45:07 #link https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV 18:45:37 #info Bin proposed a topic of "Containerized, Cloud Native Microservice in NFV Networking (Gluon)" there 18:45:59 #info Now the formal submission window is open. 18:46:12 #info Bin will work with Session Chair to get it submitted 18:47:06 #info This is an additional topic, besides a proposal of Service Modeling Method by Georg and Bin, which has been accepted for Summit 18:47:55 Does anyone else have new topics? 18:48:39 bh526r: hi 18:48:51 Hi ildikov 18:48:54 bh526r: we now opened the official submission for the Forum 18:49:04 Yes, that's great 18:49:07 bh526r: this is the form: http://forumtopics.openstack.org/cfp/create 18:49:21 Cool 18:49:35 bh526r: and here you can find guidelines and hints for proposals: https://wiki.openstack.org/wiki/Forum 18:50:12 Sure. I will work with Jamey to submit it. Jamey is trying to organize the submissions 18:50:23 bh526r: it is important to have a moderator for the session you propose, so I wanted to reach out to you regarding the one that's on the etherpad already 18:51:00 bh526r: to give a heads up on the official proposal period and to ensure you are prepared to submit the session 18:51:27 bh526r: also one of the main purposes of the Forum is having discussions that involves both the developers and the users/operators 18:52:16 Thank you ildikov. Will "Telecom & NFV" be one session? Or each topic be a separate session? 18:52:43 bh526r: I think it will be separate 18:53:22 Cool. Do you have suggestion of the session chair/moderator for the session I proposed? 18:53:59 bh526r: so when you propose yours having the subject and goals as a standalone topic there would be the way to go 18:54:44 bh526r: and also try to highlight how the users will be involved in the discussion, what they will benefit and what you expect from them and what you wish to discuss 18:54:56 bh526r: will you or anyone from the team be there? 18:55:00 I see. Thank you for the hints. 18:55:09 Yes, I will be in Boston. 18:55:33 bh526r: would you be comfortable with moderating? 18:56:28 I should be fine. And usually it is better to have 2 moderators. Will you be able to help too if your time permits? 18:57:16 bh526r: yes 18:57:51 bh526r: I will need to look into the schedule as you pointed out, but I plan to attend the Telecom/NFV ones 18:58:11 bh526r: the deadline for submissions is April 2nd if I remember correctly 18:58:21 ildikov: great, thank you for help. So I will get it submitted as soon as possible (after talking with Jamey) 18:58:29 bh526r: feel free to ping me if you have any questions or need help before submitting 18:58:33 Yes, it is April 2nd 18:58:42 Sure, definitely Ildikov 18:58:45 bh526r: sounds great, thank you! 18:58:53 Thank you too 18:59:30 We are on top of the hours 18:59:36 That's all from my side 18:59:49 If nothing else, we can adjourn the meeting 18:59:56 #info Meeting adjourned 19:00:03 #endmeeting