Following dprince's change to use
FLAGS, rather than cfg.CONF,
zmq_opts needs to be registered explicitly.
Change-Id: I66bc71563435088ee9224fdd603602e35f3e3bff
Python ignores SIGPIPE on startup, because it prefers to check every
write and raise an IOError exception rather than taking the signal. Most
Unix subprocesses don't expect to work this way. This patch (adapted
from Colin Watson's post at http://tinyurl.com/2a7mzh5) sets SIGPIPE
back to the default action for nova.utils.execute and nova-rootwrap
created subprocesses.
Fixes bug 1053364
Change-Id: I17e1629bb4ef4268515c6734ddb6e12746739c52
Updates quota value to -1 in db rather than None
if the user specify the quota limit as "unlimited".
Fixes bug 979087
Change-Id: I0ec412189ad9630c4a875655294c1e77886108f5
The nova-manage volume commands weren't updated when the switch
from int volume-id's to uuid's was made. This updates the
param2id method to call the appropriate conversion, and doesn't
attempt to cast the value to an int.
There is an additional issue with the nova-manage commands with the
introduction of Cinder. The calls in nova-manage are direct to the
nova database which when using Cinder is not valid. Add an error message
when trying to use delete or re-attach commands as they don't work.
This change deprecates the nova-manage delete function as it's now
implemented as an admin extension (nova commit id: If795599d and
cinder commit id: I29f4b892).
The reattach command is only valid for nova-volumes, a similar extension
will need to be added to cover cinder at which time the nova-manage volume
reattach can be deprecated as well.
Partial fix for bug #1051603
Change-Id: I666d4e627dee4a2025f7135560ee36c40f4bf17a
When creating a new flavor, it's now possible to omit flavorid. In this
case it will be automatically generated using utils.gen_uuid().
nova-manage and OS API updated accordingly.
Fixes: bug #1043410
Change-Id: Ibf9229599dac953177fbf1ffac5242ed716142db
Current websockify constructor in nova-novncproxy requires
target_path to be explicitely set. This commit adds the missing
parameter. Fixes bug 1031998.
Change-Id: I05e346b5df5bc1501b55ff606fc4cefdda889d60
Updates the bin/nova-rpc-zmq-receiver so that it makes use of FLAGS,
calls parse_args, and loads the nova.conf config file like all
other nova- binaries.
Fixes LP Bug #1044153
Change-Id: I904e5d2ae491cd805be78038493d437dd1f7f3cc
blueprint project-specific-flavors
This change implements API extension to manage project specific flavor
types, so that non-public flavor type can only see by projects with
access rights.
Change-Id: Ie2d2c605065b0c76897f843a4548a0c984a05f1a
The NetworkManager code will not raise webob exceptions, so there's no
point in explicitly catching those.
Also, the contrib.networks module is unused in nova-manage.
Change-Id: I5f9fe7fa7f4365f44e7a70b3d9536da8f10b8fa7
Implements blueprint os-api-network-create
The ability to create new networks is currently only exposed by the
nova-manage CLI. Here we add support for network creation in the
os-networks API extension.
With the exception of num_networks and network_size, all the parameters
supported by 'nova-manage network create' are supported. Only a single
network may be created by each API call.
To avoid code duplication, the nova-manage code is refactored and moved
into NetworkManager so that it can be re-used by the API.
DocImpact
Change-Id: I682d498ab35ea43b553b64e13e677fe9eeb8e08b
See bug 1034384, bug 1037590.
This reverts commit https://github.com/openstack/nova/commit/391f345d,
but leaves the DB migration in place while adding a further
migration to reverse it.
The motivation for reversion is that the per-user quota logic would
totally undermine the per-project quotas set for a pre-existing
openstack install.
The per-user quota logic could be re-introduced in a fixed state
after Folsom-3.
Change-Id: Idd4b55a2404a25f43f6737b661f828c28501066f
bug 1034692
Quantum team is removing all v1 support in Folsom, so this code
will not be used or supported with Quantum Folsom release.
Change-Id: I4c397d5238fcc3a15320e052bdc4735dfec1f176
Implements blueprint per-user-quotas.
Based on the original quotas structure.
NOTE:
quota_instances, quota_cores, quota_ram, quota_volumes,
quota_gigabytes, quota_key_pairs and quota_security_groups
are supported per user.
Allow 'projectadmin' role to access the user quota setting
methods.
Add commands 'nova-manage quota project/user' for quotas
management.
Change-Id: I07a39499432571fedd819c53ae414240cefc3354
bug 1031263
The nova database API use instance_type id as parameter to access flavor
extra spec. However, the flavor extra_specs API extension use flavor_id as
parameter wrongly.
As the instance_type ID is a purely nova internal ID, the database should
not expose it and instead use flavor_id as the parameter
Change-Id: I5f509cb7c4457d8c399df32f559a874d498be762
Signed-off-by: Yunhong, Jiang <yunhong.jiang@intel.com>
Fixes bug #1032177
If a floating IP is not associated with an instance, nova-manage fails
with:
local variable 'instance_uuid' referenced before assignment
This is a regression introduced by commit fc82c6d. Simply rename
the local variable to instance_uuid.
Change-Id: Ia6df23c945f0815c65bcfd2f49e8ba3225d03d7f
Mark the root_helper option deprecated and introduce usage of
the rootwrap_config option instead. The root_helper option will
still fully be supported in Folsom, but will be removed in Grizzly.
Transition notes: you should replace:
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
by:
rootwrap_config=/etc/nova/rootwrap.conf
Implements bp deprecate-root-helper
Change-Id: I8dfc94e9b91f7ffc82d393b345f09409da347e78
blueprint update-flavor-key-value
Enhance nova-manage so that it can add, delete and list key/value pairs for
flavors extra specs.
Change-Id: I0665bec6aecd7f7a1d8e845fd930f4bd5a841522
Signed-off-by: Yunhong, Jiang <yunhong.jiang@intel.com>
This fix correct the problem reported in bug 930193
nova-manage does not return a full list of fixed IPs. The reason
is that the call to fixed_ip['instance_id'] can throw exception
when fixed_ip does not have instance_id as its member. The changes
in this fix corrects the problem.
rebase to resolve the automatic merge issue.
Change-Id: Ic15a0a0f43f53b82f9d88a03803c96b44a8ddcb9
The fix addresses the bug reported in bug 1025827
currently command 'nova-manage fixed list' will return
'Command failed.' message when there is no network defined or
all networks have been deleted or even when a network gets
deleted, then a new network gets created. In all these cases,
the command produces the 'Command failed.' error message which
does not really tell what went wrong. This fix will produce
'No fixed IP found' in these conditions.
changes made for globalization.
changes made for based on the comments for patchset 7.
Change-Id: I3c2e9bf3fa3c748e680c1df27d243a648ed47cf5
this fix addresses the bug #1021810
Currently command 'nova-manage network list' or
'nova-manage fixed list' will return 'Command failed.' message when
there is no network defined or networks get deleted. This fix combined
with fixes to bug 1025827 will fix both command problem.
also change the print out message so that it can be translated.
code structure changes according to the suggestion from comments.
Change-Id: Id9a1a10217aac971cbbba9db5829c8478892db1a
Fixes bug 1017682 the netaddr.IPNetwork.iter_hosts
method doesn't return any IPs when /32 or /31 and
should throw an exception instead of silent error
Change-Id: Id8875b6016a4dbb40b29d2f7687e6c35491e0129
Fix bug 1021222.
This patch tweaks nova-manage to always attempt to delete all addresses
in the specified IP range, even if an error is encountered. This is an
easy way to handle a case where a range was created, but then a subset
of that range was deleted. Otherwise, deleting the rest of the range is
a pain.
An example of this would be:
# nova-manage floating create --ip_range=1.1.1.0/24
# nova-manage floating delete 1.1.1.1
# nova-manage floating delete 1.1.1.0/24
Previously this would fail. Now it works.
Change-Id: Ia01c04dee5383f597976c6a79d9a0d9e19985898
The instance usage audit cronjob that generates periodic
compute.instance.exists notifications is not particularly scalable.
It is run on one server and takes longer as the number of instances grows.
This change moves the generation of those events to a periodic task in
the compute manager. It also adds an api extension that can be used
by administrators to check for errors generating these events.
Change-Id: I856d3d0c73c34e570112f1345d306308ef20a9ae
Drop support for management of deprecated auth by deleting
the following nova-manage commands:
* role *
* export *
* project/account * (except scrub and quota)
* shell export
* user *
Additionally, delete relevant documentation and tests.
Related to bp remove-deprecated-auth.
Change-Id: Iad9787f696cb55d4673d68fc60851c7f5bd25805
This appears to have slipped through the cracks in the recent move
from nova.log to nova.openstack.common.log
Change-Id: I4935c6e1ba0681a31c081b580f1afecc676c5697
Logging broke with change to stdlib logging,
changed to openstack.common log.
Use of 'python -d' seems not to work with 'env', and unnecessary.
Change-Id: I428c56c612c7d9d043dab2d36b80beb6ca184d27
Implements blueprint multi-process-api-service
This is based on Huang Zhiteng's patch.
This patch adds support for running services as multiple processes. This
is primarily intended to be used with the API service as a way to provide
more concurrency than eventlet can sometimes provide.
A SIGTERM or SIGINT signal will cause the parent process to gracefully
terminate the child processes, allowing them to finish processing the
requests currently being processed. The parent will wait for the
children to finish before exiting.
Change-Id: Ie6d6802626eb42d5e64c4167be363fbf6cea2a1b
Fix a typo in nova-all where logging.exception was used instead of
LOG.exception like the rest of the code uses
Change-Id: I6f88014e1c5d87a9b84bb2ac833931a93aaf96c0
Move rootwrap filters definition from being defined within Nova
code to being defined in configuration files to facilitate pluging-in
new rootwrap commands.
Transition notes:
* nova-rootwrap now requires an additional (first) parameter pointing
to the root-owned rootwrap.conf file, sudoers needs to be updated
to specify that ("nova-rootwrap /etc/nova/rootwrap.conf *")
* Packagers should ship {compute,network,volume}.filters inside a
directory listed in rootwrap.conf rather than shipping
nova/rootwrap/{compute,network,volume}.py
* Filter definitions now only support strings. The KillFilter (which was
using arrays as parameters) was modified and the tests updated.
Implements bp nova-rootwrap-pluggable-filters
Corresponding devstack change needs to land first, so that tests pass:
https://review.openstack.org/8842
Change-Id: I2350154cd8057bd57926ed542de035626f7de37d
Jenkins