18:00:00 <bh526r> #startmeeting gluon
18:00:01 <openstack> Meeting started Wed Jul 26 18:00:00 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:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:05 <openstack> The meeting name has been set to 'gluon'
18:00:08 <bh526r> Hi Kamil
18:00:19 <pcarver> hi
18:00:21 <bh526r> #topic Roll Call
18:00:26 <bh526r> #info Bin Hu
18:00:43 <pcarver> #info Paul Carver
18:00:50 <krenczewski> #info Kamil Renczewski
18:01:11 <bh526r> #topic Admin Update
18:01:41 <bh526r> #info Bin plans to attend PTG on 09/11-09/15. Does anyone else plan to attend?
18:02:20 <bh526r> #info Otherwise, no other update
18:02:37 <bh526r> #topic Pike Release Update
18:03:50 <bh526r> #info Bin followed up with Sukhdev, and waiting for further update regarding Neutron related tasks
18:04:31 <bh526r> #info In addition, there are 2 patched approved since our last meeting on June 28:
18:04:49 <bh526r> #info One is "Fix incorrect commands adding Gluon service to Keystone"
18:04:50 <Sukhdev> bh526r: I will reply later today
18:05:00 <bh526r> Thank you Sukhdev
18:05:19 <bh526r> #link https://review.openstack.org/#/c/474812/
18:05:42 <bh526r> #info The other one is "Update documentation for Contrail installation"
18:05:57 <bh526r> #link https://review.openstack.org/#/c/476509/
18:06:20 <bh526r> #info There are 7 new patches submitted for review
18:06:40 <bh526r> #info (1) Update the documentation link for doc migration
18:06:51 <bh526r> #link https://review.openstack.org/#/c/486511/
18:07:16 <jinli> info JinLi
18:07:57 <bh526r> #info This patch updates the link of OpenStack docs in our various documentation to match the new OpenStack doc structure
18:08:07 <bh526r> #info It is quite straightforward.
18:08:41 <bh526r> #info Please take a look, and see if you have any comment
18:09:41 <bh526r> #info There are two +1. If there is no comment, I suggest to approve it.
18:10:40 <bh526r> #info No comments, this is approved. Bin will take action to merge it.
18:11:50 <bh526r> #info (2) Update formatting in Contrail docs
18:12:05 <bh526r> #link https://review.openstack.org/#/c/482963/
18:12:34 <bh526r> #info This patch improves the formatting in contrail installation procedure.
18:13:07 <bh526r> #info It is quite straightforward.
18:13:19 <bh526r> #info There are two +1.
18:13:35 <bh526r> #info If there is no further comment, I suggest to approve it.
18:16:00 <bh526r> #info No comments, this is approved. Bin will take action to merge it.
18:17:05 <bh526r> #info (3) Rule to code
18:17:24 <bh526r> #link https://review.openstack.org/#/c/483613/
18:18:22 <bh526r> #info This patch only moves rule definitions from policy.json to code. Policies definitions e.g. "create_ports" or "get_ports" will still be defined in the policy.json file.
18:18:33 <bh526r> #info In the future, policy definitions will be auto generated from model's yaml files[1]. Then policy definitions will be removed from the policy.json file.
18:18:52 <bh526r> #info There are three +1.
18:19:13 <bh526r> #info If there is no other comment, I suggest to approve it.
18:21:50 <bh526r> #info No comments, this is approved. Bin will take action to merge it.
18:22:36 <bh526r> #info (4) Add configuration option for policy.json file path
18:22:52 <bh526r> #link https://review.openstack.org/#/c/481771/
18:23:14 <bh526r> #info There are 2 comments, all are editorial / typo
18:23:24 <jinli> will need to fix the typo
18:23:32 <jinli> good catch bin
18:23:55 <bh526r> Thank you Jin.
18:24:24 <bh526r> #info Except those 2 editorial typos, please review if you have any comment
18:24:54 <bh526r> #info Jin will upload a new patchset to fix the typo.
18:26:04 <bh526r> #info If there is no other comment by Friday July 28, assuming new patch will be uploaded at that time, this patch will be approved. Bin will take action to merge it
18:26:51 <bh526r> #info (5) Set environment variables for protonclient
18:27:08 <bh526r> #link https://review.openstack.org/#/c/482728/
18:27:49 <bh526r> #info There is 1 editorial comment
18:28:20 <jinli> I will fix it today together with the previous one
18:28:29 <bh526r> Great, thank you Jin
18:28:41 <bh526r> #info Jin will upload a new patchset to fix the typo.
18:28:58 <bh526r> #info Except those 2 editorial typos, please review if you have any comment
18:29:20 <bh526r> #info If there is no other comment by Friday July 28, assuming new patchset will be uploaded at that time, this patch will be approved. Bin will take action to merge it
18:29:53 <bh526r> #info (6) Gluon object-level authorization
18:30:07 <bh526r> #link https://review.openstack.org/#/c/482752/
18:30:39 <bh526r> #info There are 3 editorial comments
18:31:07 <pcarver> What's the purpose of the .bak file?
18:31:07 <jinli> bin let's test this one together on Friday before we merge it
18:31:28 <jinli> Paul that's the original file
18:32:01 <pcarver> but what's it for?
18:32:11 <pcarver> Why is it in the commit?
18:32:43 <jinli> we will remove it after we run test, it is just there for comparing code
18:33:24 <pcarver> but that's what Git is for
18:34:20 <pcarver> Git already has a backup of all past states of the repository, so what's the point of committing a copy of file to the version control history?
18:34:21 <jinli> agree, I will remove it after we run test case on Friday
18:35:04 <jinli> I keep it there so I can open these two files at the same time in editor
18:35:26 <jinli> while I modifying the code
18:36:17 <bh526r> Hi
18:36:25 <pcarver> you don't need to add it to the commit in order to do that
18:36:41 <bh526r> sorry that I was disconnected from network for a few minutes
18:37:02 <bh526r> and I didn't blame our u-verse
18:37:20 <bh526r> Where are we at?
18:37:36 <jinli> bin let's test this one together on Friday before we merge it
18:37:37 <jinli> <pcarver> What's the purpose of the .bak file?
18:37:37 <jinli> <jinli> Paul that's the original file
18:37:37 <jinli> <pcarver> but what's it for?
18:37:37 <jinli> <pcarver> Why is it in the commit?
18:37:38 <jinli> <jinli> we will remove it after we run test, it is just there for comparing code
18:37:39 <jinli> <pcarver> but that's what Git is for
18:37:41 <jinli> <pcarver> Git already has a backup of all past states of the repository, so what's the point of committing a copy of file to the version control history?
18:37:44 <jinli> <jinli> agree, I will remove it after we run test case on Friday
18:37:47 <jinli> <jinli> I keep it there so I can open these two files at the same time in editor
18:37:48 <jinli> <jinli> while I modifying the code
18:37:50 <jinli> <bh526r> Hi
18:37:52 <jinli> <pcarver> you don't need to add it to the commit in order to do that
18:37:56 <jinli> <bh526r> sorry that I was disconnected from network for a few minutes
18:37:58 <jinli> <bh526r> and I didn't blame our u-verse
18:38:05 <bh526r> Thank you Jin
18:38:21 <bh526r> Ok, let's test it on Friday
18:38:52 <bh526r> #info (7) Policies in yaml
18:39:17 <bh526r> #link https://review.openstack.org/#/c/486254/
18:39:29 <bh526r> #info This one is still a work in progress
18:39:32 <jinli> same thing here, we will need to test it on Friday and clean up code before merge
18:40:06 <bh526r> Yup, and perhaps need to rebase based on 3 merges today.
18:40:14 <jinli> @paul, thank you for your suggestions, will pay attention to that.
18:41:04 <bh526r> #info (6) and (7) need further work and review.
18:41:28 <bh526r> That's all from my side
18:41:42 <bh526r> Anything else or any update from anyone else?
18:41:52 <bh526r> #topic AOB
18:42:50 <bh526r> If no other update or nothing else from your side, we can adjourn the meeting and give back everyone 15 minutes
18:43:12 <bh526r> #info Nothing else
18:43:24 <bh526r> #info Meeting adjourned
18:43:31 <bh526r> #endmeeting