yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #42849
[Bug 1093538] Re: Discrepancy between bulk operation doc and implementation
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1093538
Title:
Discrepancy between bulk operation doc and implementation
Status in neutron:
Expired
Bug description:
It seems that the bulk operations are not implemented as documented.
For instance, check create networks: http://docs.openstack.org/api/openstack-network/2.0/content/bulk_create_networks.html
Doc states that the request body should be in the following format:
{
"networks": [
{
"name": "sample_network_1",
"admin_state_up": false
},
{
"name": "sample_network_2",
"admin_state_up": false
}]
}
But actually the request body is submitted as follows:
{
"networks": [
{
"network":
{
"name": "sample_network_1",
"admin_state_up": false
},
}
{ "network":
{
"name": "sample_network_2",
"admin_state_up": false
}
}]
}
This could be a dob bug, a Quantum API bug, or both.
If we deem the way described in the documentation to be the correct
one, than we need to do a non backward-compatible change in the
Quantum API. One might argue however that this change is not backward
incompatible as the API was wrong in the first place, and the fix
should be backported to folsom.
Allowing both ways for specifying a bulk request is also feasible, but in general we should avoid supporting several ways of doing the same thing unless:
- it is not likely to cause confusion on end users
- does not require different code paths to be maintained
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1093538/+subscriptions