systemd is used instead of upstart by default since Ubuntu 15.10
(Wily). This adds systemd init file support for nova services
that are deployed from source.
Change-Id: Ie71aed8c1f28204d5fbd735d51cea6d77977a637
All contributors to this charm have agreed to the switch
from GPL v3 to Apache 2.0; switch to Apache-2.0 license
as agreed so we can move forward with official project status.
Change-Id: I20448e0370138e103a00c7fcf0f49949c82d33a9
openstack-origin-git currently only supports YAML that specifies
the git repositories to deploy from.
This adds support for default openstack-origin-git values. The
default values supported are: icehouse, kilo, liberty, mitaka,
and master. For example: openstack-origin-git=master
Change-Id: I6b737272deed067c2f71dbd36b201aea884265ee
Force upgrades to Liberty to step through Kilo and force Kilo upgrades to
migrate flavor information. The flavor migration needs to be run with a
Kilo tool set as the flavor migration option appears to have been removed
in Liberty . The charm now run the flavor migration if the current
deployment is Kilo and the user is migrating to a higher release.
When an instance is created on Icehouse the flavour ID is stored in a table
called instance_system_metadata. Kilo (or maybe Juno) creates a new table
in the nova database called instance_extra. For new instances created after
upgrading to Kilo the flavour information goes into the instance_extra
table not instance_system_metadata. It is a prerequisite for upgrading to
Liberty that this flavour data has been moved from instance_system_metadata
to instance_extra. At upgrade at this point will fail because the instance
created when the system was on Icehouse has its flavour information in the
wrong place.
Change-Id: If486372b05d165bd17fa9466b435f22088532d89
Closes-Bug: #1580698
This change fixes the obvious race for a status_set() between
check_optional_interfaces() and assess_status() as the later calls the former
which calls status_set(), returns the status, which is then potentially set
again by the assess_status() function. This cleans up the code so that only a
single status_set() is performed when calling assess_status().
Change-Id: Ie37a4d98de9c5e7bd26304e096796ce6287ea52b
Related-Bug:#1588462
A previous commit removed the use of the NeutronAPIContext with
the nova.conf template; restore this context to ensure that
a) the relation is detected when assessing status and b) that
neutron-api relation data is avaliable to the nova.conf template.
Change-Id: Id55800095b9a2d0a5807288ff5f67d71755f9948
Neutron functionality was deprecated last release; remove
direct support for managing the neutron-server process and
associated plugin support from this charm.
All neutron-server support is now provided by the neutron-api
charm.
Change-Id: Iec7bd5ec6d835b573a15f8163fa5f78842bd672b
Openstack mostly defaults to using public endpoints for
internal communication between services. This patch adds
a new option use-internal-endpoints which, if set to True,
will configure services to use internal endpoints where
possible.
Closes-Bug: 1456876
Change-Id: I0f13fa1ab66864859d3adb37e5ec64bd95d7025d
Adds pause and resume unit to the charm such that the
charm stays paused during maintenance operations.
Change-Id: Ia422aa4077fbdd8cdb0353306c14f5633e2affb8
Partial-Bug: 1558642
Rollup all old configuration file templates, remove any related
to Quantum which was renamed in the Havana release.
Drop references in code to Quantum, refactor unit tests to baseline
on Icehouse rather than anything older.
Drop relation and associated references to nova-volume service;
deprecated in Folsom and removed in Havana.
Drop ml2 migration - this was required when migrating to Icehouse
from older releases.
Change-Id: I6f5d641ffef2599d0dfc8e16a2dce3cc7be88bd4
Mitaka requires the use of a separate nova-api database;
ensure that this is setup on the shared-db relation and add
a new [api_database] section to the mitaka nova.conf file.
Add a new NovaAPISharedDBContext wrapper to prefix the key
names for the nova-api database with 'nova_api_' so that we
can present two database connections to the same configuration
file.
Ensure that 'nova-manage api_db sync' is called for database
setup for >= mitaka release.
For upgrades, ensure that the database migration and service
start is deferred until the nova_api database has been
setup by the related mysql service.
Closes-Bug: #1556896
Change-Id: If1c9a037b1e0745a486a57fddf885e26aa7e313d
Advertise Nova API readiness
Adds a new relation 'nova-api' that can be used by services that consume
the nova api in some way or another. We use it to simply pass a flag to
remote services that states whether the API service is ready to be used,
based on the complete context of required interfaces.
Adds a new relation 'nova-api' that can be used by services that consume
the nova api in some way or another. We use it to simply pass a flag to
remote services that states whether the API service is ready to be used,
based on the complete context of required interfaces.
Fix upgrade breakage whereby if upgrading from
version of charm that did not support
dbsync_state peer setting db ops get stuck
waiting infinitely for db to be intialised.
Closes-Bug: 1519035
