At the Barcenlona summit, we discussed disabling n-net everywhere as a
precursor to removal. The only exception for using n-net is as required
for CellsV1 users, which require it as the only out-of-the-box supported
networking option.
We will remove this check and n-net entirely when those users have a
migration path to neutron and cellsv2.
Depends-On: I47f72eac6a7657bf44319fa5d2df18ce62827f6f
Change-Id: I7309afa5230bcaeeeddb554d95c327d3a614ae6e
Currently we only publish the master branch of api-ref to:
http://developer.openstack.org/api-ref/compute
and we have microversion caps for different releases.
It will be better for user to understand if we add
also microversion caps information to the doc.
Change-Id: Ic6c042f68f5d340a68abad6701e65d44e46da3a7
Closes-bug: #1640995
We're going to store the list of requested security group objects
in the request spec so the neutron security group driver code
needs to actually populate that list now for use in the compute API.
As the nova-network and neutron security group API code is basically
the same for populating that list, the backend-specific implementations
are removed and pulled up into the base security group driver API class.
Since we don't want to actually try and persist this list with the
instance object in the nova database we need to add a check in the
compute API to store an empty list, like the old behavior, when
creating the instance. A later change will use the populated list
to store in the RequestSpec.
Part of blueprint cells-scheduling-interaction
Change-Id: I6139eb92f534f010565fde31661382d33463ae58
Add a paragraph which clarifies that a specless blueprint needs to
be approved and the normal process for doing so, with links to
additional information.
Change-Id: I1d4fc40a2e5acb8b63f90e00dc19ee5a65fbe870
We're going to store requested security group objects in the
request spec. nova-network security groups are unique by name
and tenant. Neutron security groups, however, are not unique
by name within a tenant, they are unique by uuid. So to uniquely
store the requested security groups in the request spec we need
to store the neutron-specific id value (which is a uuid) in the
SecurityGroup.uuid field added here.
Since we don't store this in the nova database the uuid value
must be popped during a save() and ignored when creating an
object from a DB primitive.
Part of blueprint cells-scheduling-interaction
Change-Id: I3c3fb8fe9a53155caba49b353c0524f84dc458ff
This completes the body verification for the force_complete
action for server migrations.
This is only supported with microversion >= 2.22 and only for
in-progress live migrations, on unlocked servers that are in
active/migrating status.
There is also a note as not all compute drivers support this
action. See bug 1641753 for details.
Part of blueprint api-ref-in-rst-ocata
Change-Id: I9cd6cf35b4b5828f0f4acde168cda2beedd902f4
Completes the body verification for showing details of a
specific in-progress live migration for a given server.
Part of blueprint api-ref-in-rst-ocata
Change-Id: I5175fc8814cc5c62739273e02e52b81aa6b39b0b
This completes the body verification for listing server
migrations.
Note that the code currently filters such that only in-progress
live migration records are returned. This was also only available
with microversion >= 2.23.
Part of blueprint api-ref-in-rst-ocata
Change-Id: I3a785dad690eee80ec1fd50ebc9fd3f7484dc344
Completes the example verification for the server-migrations API.
Partial-Bug: #1641713
Part of blueprint api-ref-in-rst-ocata
Change-Id: I2234ac402d778553cbebb915943ce1fd0b8d6210
This completes the parameter verification for the server-migrations
API.
Partial-Bug: #1641713
Part of blueprint api-ref-in-rst-ocata
Change-Id: I94ac520b35f4e6a042456c67bc713202fd8c3c91
We don't have any api-ref for server-migrations. os-migrations
is frozen and server-migrations replaces it, but we don't
have any docs for it, so this is a start.
Partial-Bug: #1641713
Part of blueprint api-ref-in-rst-ocata
Change-Id: I3da6ff6a4a0abf2f9c8bae3fb28fe23fdc3b0959
Add support for checking min_unit, max_unit and step_size when
making allocations to the placement API. When the constraints are
violated a new exception InvalidAllocationConstraintsViolated is
raised.
Change-Id: I18596a3c0f2b0049aaccd0f3e73aef90b684c4a8
Closes-Bug: #1623545
Since ceph installation and initial config is done
by devstack-ceph-plugin, duplicate functions could be
safely removed from l-m hook
Change-Id: I23a8a8d414fb43b6758485a5a6df4a771abdefce
The api-ref was saying that the server_id was in the body of the
server metadata requests but it's actually in the path for all
of the requests.
Change-Id: Icdecd980767f89ee5fcc5bdd4802b2c263268a26
Closes-Bug: #1641331