[Netstack] Quantum authorization
Since gerrit is currently broken WRT sending out notifications of new changes, and since almost no one (and definitely no cores) have commented on my new authz patch, I thought I'd send a quick email to let people know it was up: https://review.openstack.org/#/c/8500/ This completes the work for blueprint authorization-support-for-quantum, as far as I know (please feel free to tell me if I'm wrong! :) -- Kevin L. Mitchell -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
Re: [Netstack] Quantum authorization
Need more cores to review the authz patch (link below). Have a +2 from Dan, just need someone else to +2 and approve… On Thu, 2012-06-14 at 12:02 -0500, Kevin L. Mitchell wrote: > Since gerrit is currently broken WRT sending out notifications of new > changes, and since almost no one (and definitely no cores) have > commented on my new authz patch, I thought I'd send a quick email to let > people know it was up: > > https://review.openstack.org/#/c/8500/ > > This completes the work for blueprint authorization-support-for-quantum, > as far as I know (please feel free to tell me if I'm wrong! :) -- Kevin L. Mitchell -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
[Netstack] Request for comments on a pep8 problem
Yesterday, I submitted https://review.openstack.org/#/c/10736/ to sync up an openstack-common change to policy.py; however, the pep8 configuration for quantum does not match the pep8 configuration for the openstack-common project, and an error is raised. Other projects (in particular, nova) exempt the openstack/common directory from the pep8 check, but I guess Quantum doesn't have that set up, yet. I wanted to check here first, however, before I start working on a patch to accomplish that. So, does anyone have any problem with exempting the openstack/common directory from pep8 checks, since anything in openstack/common has already been checked and tested within the openstack-common project? -- Kevin L. Mitchell -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
Re: [Netstack] Request for comments on a pep8 problem
On Fri, 2012-08-03 at 17:48 +0300, Gary Kotton wrote: > Will you also be fixing the pep8 issues in the common code? When the pep8 running in openstack-common reports the issue, yes, it will make sense to fix it. Since I have already synchronized nova and glance, I'm highly reluctant to make the necessary change. I'll also point out that the particular condition that pep8 is reporting here is all over the place in nova and probably also in glance… -- Kevin L. Mitchell -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
