18:00:17 #startmeeting gluon 18:00:18 Meeting started Wed Aug 16 18:00:17 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:21 The meeting name has been set to 'gluon' 18:00:31 #topic Roll Call 18:00:38 #info Bin Hu 18:00:41 #info JinLi 18:00:46 Hi Bin 18:00:49 Hi Jin 18:01:29 looks like only you and I. so let's quickly discuss those patches 18:01:37 sure 18:01:42 #topic Pike Status 18:02:06 #info Bin cut the stable/pike branch, and tagged 1.0.5 18:02:22 #info There are 4 outstanding patches 18:02:29 hi 18:02:40 Hi paul 18:02:56 Hi Paul 18:03:06 #info Patch 1: Gluon object-level authorization 18:03:22 #link https://review.openstack.org/#/c/482752/ 18:03:34 #info Patch 2: Policies in yaml 18:03:39 #info Kamil Renczewski 18:03:50 #link https://review.openstack.org/#/c/486254/ 18:03:54 Hi Kamil 18:04:00 Hi Kamil 18:04:02 Hi 18:05:07 #info Bin, Jin and Tin discussed offline, and concluded that for Gluon, because the APIs are generated from YAML, putting policies in YAML is a more flexible way for Gluon 18:05:32 #info Default policies will be in base.yaml. 18:06:28 #info Policies for new services (new YAML) will be defined in the same YAML. In this case, service-specific policies defined in YAML will be used 18:06:53 #info If new YAML doesn't contain service-specific policies, default policies in base.YAML will be used 18:07:45 #info Jin will finalize the coding in above 2 patches this week based on the way to go 18:08:11 #info Patch 3: WIP: Resolve warnings in Sphinx documentation 18:08:20 #link https://review.openstack.org/#/c/491544/ 18:08:39 #info This patch seems completed. 18:09:15 @jinli, I saw your comments and new patchset uploaded by Omar. 18:09:21 Do you have more comments? 18:09:55 I think this patch should be ok, I just have some questions. 18:10:00 let me discuss with Omar 18:10:16 then we can merge it later this week 18:10:33 sounds good to me. So I will wait for your signal 18:10:50 Tin reviewed it and gave a +1, Tin is the one who discovered this issue 18:11:15 Tin gave +1 in patch 5 18:11:53 I see. Now it is patchset 6. 18:12:18 I am glad we fix this issue. it causes random errors and fail jenkin once a while 18:12:34 Can you discuss with Omar, and check with Tin regarding your questions on patchset 6? 18:12:42 sure, 18:12:48 If you are good, we can merge it later this week 18:12:54 ok 18:13:35 #info Jin has some comments. Jin will discuss with Omar and double check with Tin. 18:14:00 #info If everything is fine, it will be approved. Bin will take action to merge it. 18:14:29 #info Patch 4: The para into "add_model()“ should be changed to model in function ”build_api()“ 18:14:59 #link https://review.openstack.org/#/c/492916/ 18:15:19 any comments on this patch? 18:16:04 that load_model_for_service(service) is a singleton, so it doesn't make that much difference to replace it with model. 18:16:39 the patch is ok, less confusing 18:17:01 great 18:17:43 If no more comments, I suggest we approve it. 18:19:28 #info Group approved it. Bin will take the action to merge it in master and cherrypick to stable/pike 18:19:48 I think that's all outstanding patches. 18:21:29 Kamil, do you feel we can do a PoC in Sydney with Contrail really working with ODL? 18:21:47 I think yes 18:22:01 Great. 18:22:22 Georg is still on family leave. 18:22:25 I didn't discuss details about Sydney summin with Sukhdev yet 18:22:45 So we need to agree on scenario first 18:22:55 I will draft the demo scenario, and share with you 18:23:03 OK, great 18:23:16 Then we can see which are doable, and which are stretch 18:24:27 Input from Georg is also important once he comes back 18:25:17 Let me put together the scenario first, and we can discuss it further. 18:25:28 Sure 18:25:39 #topic AOB 18:25:45 We're working on same lab as previously? 18:26:00 #info Group discussed a potential PoC/demo in Sydney summit 18:26:21 Yes, the same lab is working as I checked last week. 18:26:31 In Germany 18:26:40 I will need to re-deploy Contrail 18:27:05 We're using now R4.0 branch, previously was R3.1 18:27:23 Surely, because this time, we want to see the API calls go through Contrail, and through ODL 18:27:45 And we also need to re-deploy Gluon once we have stable Pike version 18:29:03 #info We need to: 18:29:18 #info 1. Complete Gluon Pike stable version 18:29:26 #info 2. Re-deploy Gluon 18:29:49 #info 3. Re-deploy Contrail (4.0) 18:30:09 #info 4. Double check Lab's availability 18:30:24 #info 5. perhaps re-deploy ODL and ONOS 18:30:57 #info 6. Ensure API call flows through Contrail, ODL and ONOS 18:31:22 #info Bin will draft the demo scenarion first, and share with everyone for further discussion 18:31:56 anything else? 18:32:05 I am good 18:32:19 great and thank you. 18:32:44 If nothing else, we can adjourn our meeting for now 18:33:01 #info Meeting adjourned 18:33:06 #endmeeting