yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03293
[Bug 1192316] [NEW] extraroute API should provide more than just an update method
Public bug reported:
I am looking at extraroute in the context of this blueprint:
https://blueprints.launchpad.net/quantum/+spec/nvp-extra-route-extension
And I wonder whether we should support proper CRUD operations.
The way it is implemented today does not totally make sense to me. The
extension does support just UPDATE, but actually, this is not a *true*
update (i.e. the update of existing route's attributes): it's just a
bulk create/delete of routes in one go.
I think it would be better if we added CRUD operations to manage single
routes and keep the bulky update for backward compatibility.
This is just a request for comment, depending on people's sentiment I
can convert this to a blueprint and carry out the work to align the API
and other's plugin implementations.
** Affects: quantum
Importance: Undecided
Assignee: Armando Migliaccio (armando-migliaccio)
Status: Opinion
** Tags: api
** Changed in: quantum
Status: New => Opinion
** Changed in: quantum
Assignee: (unassigned) => Armando Migliaccio (armando-migliaccio)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1192316
Title:
extraroute API should provide more than just an update method
Status in OpenStack Quantum (virtual network service):
Opinion
Bug description:
I am looking at extraroute in the context of this blueprint:
https://blueprints.launchpad.net/quantum/+spec/nvp-extra-route-
extension
And I wonder whether we should support proper CRUD operations.
The way it is implemented today does not totally make sense to me. The
extension does support just UPDATE, but actually, this is not a *true*
update (i.e. the update of existing route's attributes): it's just a
bulk create/delete of routes in one go.
I think it would be better if we added CRUD operations to manage
single routes and keep the bulky update for backward compatibility.
This is just a request for comment, depending on people's sentiment I
can convert this to a blueprint and carry out the work to align the
API and other's plugin implementations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1192316/+subscriptions
Follow ups
References