0741a0d5a5
Initially when [1] was proposed the idea was to use PARENT_OWNER_* rules for the subnet APIs, in the same way as it is done currently for e.g. FIP PF, QoS rules and some other resources. But after some more thinking about it, it's better to keep NET_OWNER rules for MEMBER and READER. Those rules are basically very similar to the PARENT_OWNER_*, the only difference is that it relies on the "network_id" attribute always. The reason why it's better to have NET_OWNER_* rules and use them for subnets and ports is that subnets and ports are actually top level API resources in neutron. They aren't actually childs of the network so using PARENT_OWNER for them could be missleading and confusing for users. Related-Bug: #2023679 [1] https://review.opendev.org/c/openstack/neutron/+/886231 Change-Id: I52fc92f76842f9f075e9e4c49262785ca099bdf8 |
||
---|---|---|
api-ref | ||
devstack | ||
doc | ||
etc | ||
neutron | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
roles | ||
tools | ||
vagrant/ovn | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
bindep.txt | ||
plugin.spec | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
If you would like to contribute to Neutron, please read the file CONTRIBUTING.rst or see the Neutron contributor guide:
https://docs.openstack.org/neutron/latest/contributor/contributing.html
Get in touch via email. Use [Neutron] in your subject.