Add tags to core resources
Neutron resources in current DB model do not contain any tags, and
dont have a generic consistent way to add tags or/and any other data by the user.
Adding tags to resources can be useful for management and orchestration in OpenStack, if its
done in the API level and IS NOT backend specific data.
The following use cases refer to adding tags to networks, but the same can be
applicable to any other Neutron resource (core resource and Router):
1) Ability to map different networks in different OpenStack locations to one logically
same network (for Multi site OpenStack)
2) Ability to map Id's from different management/
environments, for example for project Kuryr, map docker network id to neutron network id
3) Leverage tags by deployment tools
Similar to the following nova approved spec:
http://
And in accordance to these guidelines:
http://
This spec propose to support adding tags to Neutron resources which are not meant
to be interpreted by any specific backend implementation.
Blueprint information
- Status:
- Complete
- Approver:
- Akihiro Motoki
- Priority:
- Low
- Drafter:
- Gal Sagie
- Direction:
- Approved
- Assignee:
- Hirofumi Ichihara
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-rc1
- Started by
- Hirofumi Ichihara
- Completed by
- Armando Migliaccio
Related branches
Related bugs
| Bug #1489291: [RFE] Add tags to neutron resources | Fix Released |
| Bug #1552487: Add tag mechanism for network resources | Invalid |
Sprints
Whiteboard
Mar-24-
Mar-9-2016(armax): doc up for review:https:/
Mar-8-2016(armax): needs docs
Mar-3-2016 (armax): code complete as far as as M3 is concerned. Needs docs.
Jan-24-
Jan-24-2016(armax): needs volunteers. If no-one shows up/takes ownership of this one by the next couple of weeks, it will be deferred. I would be happy to be the approver's backup, but I'd have to have some code to look at first :)
Jan-18-2016(armax): no major code nor documentation as of today. Changes of getting in Mitaka are getting slim.
Dec-18-2015(armax): needs new approver/
We need to identify an approver for this work.
This sets some context:
https:/
neutron spec review: https:/
Gerrit topic: https:/
Addressed by: https:/
[WIP] Add tags for neutron resources
Gerrit topic: https:/
Addressed by: https:/
Add filter for resource tag
Addressed by: https:/
Make API framework more flexible for various extensions
API manual: https:/
Addressed by: https:/
Add API test for tag
Addressed by: https:/
Add tag mechanism for resources other than network
Addressed by: https:/
Add tag mechanism for subnet
Addressed by: https:/
Add API test for tag
