* Servers in certain states will have network_info but it may change,
(eg. rescheduled build on another host). The extension allows the
operator to hide the address information in those states
* Fixes bug LP 1089092
Change-Id: Ie843e34a41c77903b201b45c5b67a6f75334cb5e
Adds API support to:
- Disassociate only host from network
- Disassociate only project from network
- Associate network with host (project already supported)
New functionality is added to a new extension networks_associate,
but the original networks extension is modified to allow networks_associate
to extend how it needs to. The original behavior of the networks extension is
preserved (no new functionality, nor change in existing behavior) in
terms of the API presented.
Bumps RPC API version for network RPC server version in order add
the associate function which allows to both associate and disassociate
a network with a host and or tenant. Has overlap with disassociate
and add_network_to_project but these are kept for backwards compatibility
DocImpact
Implmenents: blueprint apis-for-nova-manage
Change-Id: I78fd76e0696d1c872646355ab04d32f051551def
Update the apt-get command to build mysql dependency for ubuntu.
It currenly says apt-get install build-dep python-mysqldb
which should just be apt-get build-dep python-mysqldb
Change-Id: I541f7b80802a6b7191f2fe0338965ef425e7c2fd
Add AggregateInstanceExtraSpecsFilter's replacement text in
doc/source/devref/filter_scheduler.rst
Change-Id: I5b74c5f51eb85f79f79a2d2c556d6522d97f1497
Fixes bug #1062049
There was a typo mapping the security groups resource to floating IPs.
Volumes usage isn't tracked by Nova any more since delete-nova-volume.
Key pairs don't work with the extension because of bug #1089877.
Change-Id: Ifd694b21fef1dc95e67c07dcef0cd6ea3daa8d53
This adds a new extension to nova API. It allows for internal use of
Ned Batchelder's coverage_ module. (what is used for the nosecoverage
plugin)
The api allows for coverage to be enabled and a report to be output to
a file with API calls. The intended use of this is for instrumenting
client based tests like Tempest. Coverage on tempest will not give
information regarding how much of nova is covered.
Implements: blueprint coverage-extension
Change-Id: I47497f5be3fd5956250f2dcd1630c86c72725ce8
Signed-off-by: Matthew Treinish <treinish@linux.vnet.ibm.com>
Added subs wherever applicable.
Added checks for correct return codes after REST ops
Modified sample tests to FlavorManage API to differentiate them
from the ones in FlavorExtraData.
Partially implements blueprint nova-api-samples
Fixes bug 1070162
Change-Id: I57c6611f379bef2ff586551b5501c4f7654e4374
This adds an extension that provides REST API for list/create/delete/
modify agent build. The interface is accessed via
GET /v2/{tenant_id}/os-agents
PUT /v2/{tenant_id}/os-agents/id
POST /v2/{tenant_id}/os-agents
DELETE /v2/{tenant_id}/os-agents
And this patch also create tests to get agent build API Samples.
DocImpact
Implements one workitem of blueprint apis-for-nova-manage
The agent is talking about guest agent.The host can use this for
things like accessing files on the disk, configuring networking,
or running other applications/scripts in the guest while it is
running. Typically this uses some hypervisor-specific transport
to avoid being dependent on a working network configuration.
Xen, VMware, and VirtualBox have guest agents,although the Xen
driver is the only one with an implementation for managing them
in openstack. KVM doesn't really have a concept of a guest agent
(although one could be written).
You can find the design of agent update in this link:
http://wiki.openstack.org/AgentUpdate
and find the code in nova.virt.xenapi.vmops.VMOps._boot_new_instance.
In this design We need update agent in guest from host, so we need
some interfaces to update the agent info in host.
You can find more information about the design of the GuestAgent in
the following link:
http://wiki.openstack.org/GuestAgenthttp://wiki.openstack.org/GuestAgentXenStoreCommunication
DocImpact
Change-Id: I5830388a894efce5b13680fc6916e0cd81a16624
Hooks add the ability to insert custom code around operations that
declare a named hook:
e.g.
@hooks.add_hooks('create_instance')
def create_instance(....):
....
The above hook allows Hook objects to be run 'pre' and 'post' the
execution of create_instance()
Hook objects are discovered via the setuptools entry point group
'nova.hooks'.
Change-Id: I3961df12ef415085de7459438967edacc34500c2
This extends the cloudpipe REST API to allow the setting of the IP and port
for the VPN for each network in the project
/v2/{tenant_id/os-cloudpipe/configure-project # POST ip/port
This forms part of the work to provide APIs for functionality currently
implemented by nova-manage that needs direct db access so nova-manage
can eventually be removed
DocImpact
Implements: blueprint apis-for-nova-manage
Change-Id: I416c0bfbe1c88470638f1c2004d1dcaeb51a6c41
This also includes a bunch of updates to the actual samples that have
become stale as things have changed in the tree and naughty developers
haven't updated the docs. This new bit of logic in the samples test
should help prevent that in the future.
In order to verify the static doc/api_samples files, this adds a new
method to the base test, which allows the subclasses to refine their
subs into pattern matches after the server response is verified, and
before the doc/api_samples file is verified.
Change-Id: Ie46b24a65145c407d46974b63a97a84911223547
Updates the rxtx_factor validations in the instance_types modules so
that rxtx_factor is validated as a float. Given that rxtx_factor is stored
as a float in the database this makes sense... and also adheres
to some of the extension documentation as well (although some of
the extension docs were incorrect as well).
Previously rxtx_factor was being cast into an int which caused it to
be stored and displayed incorrectly via the API.
This patchset adds a test which fails with the old code.
Additionally some of the API docs are corrected so that rxtx_factor is
listed as a float in all examples.
Fixes LP Bug #1081287.
Change-Id: Iae98522a1f2ed63cbd2497b0b0af5ac2d9bb935c
The API samples for Hosts extension missed power operations (shutdown, reboot
and startup) and maintenance/status operations.
Complete fix to bug 1070167
Change-Id: I07fd34e071eae9afc82f9320634df24f48623e0b
This adds an extension that provides a REST API for the bulk creation,
deletion and listing of floating IPs. The interface is accessed via
/v2/{tenant_id}/os-floating-ips-bulk
This forms part of the work to provide APIs for functionality currently
implemented by nova-manage that needs direct db access so nova-manage
can eventually be removed
Implements: blueprint apis-for-nova-manage
DocImpact
Change-Id: I621e2b070a896f7230cdf3f26f78ded85e72cf16
This adds a new service called "nova-conductor" which will provide
services for nova-compute, such as completing database updates and
handling long-running tasks.
Right now, this just adds a fraction of the database-related work
so that we can proceed with incremental changes to nova-compute.
For compatibility/flexibility, both LocalAPI and (RPC)API classes
are provided. Users concerned with performance or compatibility
who wish to maintain compute-node-local database accesses can
set the [conductor] use_local=True, which will mimic the legacy
behavior.
DocImpact
Change-Id: Ib81d879f40b7daceeffad5af0631c7db68168661
api_samples docs for os-server-start-stop apparently got
lost in adding the extension api_samples tests. Adding
in the docs for the extension
DocImpact
Change-Id: Ia9b97c0eb4fc7e8b22fe624ccddab6c7e003952e
part of blueprint:apis-for-nova-manage
os-services is a new module for to support getting
rid of nova-manage. Add this to the all_extensions
api listing.
DocImpact
Change-Id: I3a954de59b16fd86d81204a535f8b152f3073468
now that hypervisor_hostname is getting set in tests, update
api_samples with something better than none
part of blueprint:nova-api-samples
DocImpact
Change-Id: Iaac6a5d2d172eb3c56b64f0dc2a6075a79412712
Host state capabilities include multi-level information, like
cpu features are presented in capabilities:cpu_info:features, cpu
core number in capabilities:cpu_info:topology:cores.
Multi-level capability check maybe helpful in some situation, like
user want to make sure host support SSE3 instructions or AES-NI, or
user want to make sure the host has >4 cores for SMP instance. Current
capability filter does not support these requirements.
To support multi-level check, also add scope to capability filter,
so, now capability filter will handle no-scope extra_specs, or scope-format
as "capabilities:xxx:xxx" etc.
Related to bp hw-feature-to-vm
Change-Id: Id714f99b4babbdb328b8e47f5a270be517b528d2
Signed-off-by: Yunhong, Jiang <yunhong.jiang@intel.com>
* Remove volume calls from nova.db.api
* Remove volume calls from nova.db.sqlalchemy.api
* Remove tables from nova/db/sqlalchemy/models.py
* Remove Xen Storage Manager Volume Driver code
* No migration to preserve data in unused tables
* Remove quota support for volumes
DocImpact
part of bp delete-nova-volume
Change-Id: I2c82c96d67f3746e5de28f917dd8ceb0c8037e27
Continuation of I0b540e54dbabd26901a7530035a38583bb521fda
* delete scheduler.simple
* modify scheduler.multi instead of delete to continue supporting
I753e87fc8979fd0b62529974f00cf11fa55b3d63
* update scheduler.multi docstring
* scheduler.rpcapi bumped to 2.3
* change default scheduler to scheduler.filter_scheduler
DocImpact
part of bp delete-nova-volume
Change-Id: Ie9d9b46742b2d92cd1e9ffe982ef658907a1d411