If the compute node is deployed in a cell it will get service
credentials via a direct relationship with keystone and not
from a nova-cloud-controller relation. This change adds support
for having a complete CloudComputeContext without having
service credentials.
Change-Id: Ie2160a08e431a2c681bda84dfe32a4fa11f2aaae
In a cells deployment the credentials for the nova-compute
application will no longer be available via the
nova-cloud-controller in the local cell. This change adds the
scaffolding for a cell to utilise a new cloud-credentials relation
to allow it to retrieve credentials directly from keystone.
Change-Id: I9d1a7353d730f7cb8e93cc9eea5b788f7c956c3d
Return current hugepage usage and kernel cmdline
for static hugepage allocation
Change-Id: Ib34b2d7c3da5aacd117b19249be41bb95b91dfcd
Closes-Bug: #1734360
The [pci] header is necessary since pike [0]. This change updates the
pike template to add the [pci] header, rename pci_passthrough_whitelist
to passthrough_whitelist and add the config option pci-alias.
[0] https://docs.openstack.org/nova/pike/admin/pci-passthrough.html
Change-Id: I7a8c76f5989edb5b4a0b30036ce722ffb0ecb7ab
Add support for encryption of the underlying block device providing
storage for local instances.
This commit introduces a new juju storage binding and configuration
option to provide a single block device for use for local instance
storage; this block device is formatted and mounted at
/var/lib/nova/instances. In a MAAS deployment, this could be a
bcache fronted device.
The configuration option is preferred over the Juju storage binding
if both are supplied.
This block device can optionally be encrypted using dm-crypt/LUKS
with encryption keys stored in Hashicorp Vault using vaultlocker.
vaultlocker ensures that keys are never persisted to local storage,
providing assurance around security of data at rest in the event
that disks/server are stolen.
Charm support is implemented using a new configuration option 'encrypt'
which when set enforces a mandatory relationship to an instance
of the vault application.
Copy the 'ephemeral-unmount' config option and assocaited code from
the ceph-osd and swift-storage charms to enable testing in cloudy
environments.
Change-Id: I772baa61f45ff430f706ec4864f3018488026148
Deprecated at 18.02, removal for 18.05 release; superceeded by
Neutron Designate Extension driver.
Change-Id: I5bd824027a7bca80176d08f310c4e43a983e6c45
lvm has never actually been supported in this charm; update config
docs to drop lvm - rbd or qcow2 are the only two supported types.
Related-Bug: 1610392
Change-Id: I94ac64a4a4a3a56e1e1793b5b7c618a55dbf6f22
This patchset add 'nova-designate-relation-broken' hook definition
which is required to update nova-compute configuration files when
removing the legacy relation with designate.
Change-Id: I65f5b4ea4f3a6d3bf56a4df2f11da2d750e68e7a
Closes-Bug: 1763614
As of pip 10.0, --allow-unverified is not permitted.
Use of the flag in this repo was previously used to force
installation of python-apt to accommodate certain unit tests.
The unverified package, python-apt, is no longer necessary
for test execution.
Related-Bug: #1760720
Change-Id: I42387c238e74415ccaf5adb5182ae252bcbf10bf
Switch to use Keystone v3 clients for Queens and setup
domains etc for new demo user.
Change-Id: I4a90a28212ec6e1a8e9f348b1318722141f35d2c
Requires: https://github.com/juju/charm-helpers/pull/119
Adds new charm config option to enable multipath
connections to iscsi volumes. This is configured
in the [libvirt] section of the nova config.
Since newton, the option has been renamed to
'volume_use_multipath'. To accomodate this,
a newton template has been created.
Change-Id: Ibbf91547c5fc41215873c63219cd83303b1d37cd
Partial-Bug: #1518001
Sync in the charm-helpers to use the new VolumeAPIContext object
in order to determine the volume catalog info to use in the
configuration file.
This is simply an alternative implementation for commit 5d92bc9f.
This will separate concerns for determining internal endpoints
and determining volume api versions.
Change-Id: I91009e1f9643f818b6f97898aa5d7c43e84684ed
Related-Bug: #1733566
Change I804a34fb044090010ecfd2560594cc1f55e9bd21, commit hash
b89de21d47 dropped notifications_designate
completely to solve a problem described in pad.lv/1738100, however, to
make this change backwards compatible notifications_designate should be
used in addition to "notifications" topic used by default.
This way designate will continue to receive notifications on
notifications_designate from nova, and ceilometer will get notifications
using the "notifications" topic.
Change-Id: I245f5b263994c204a5e521dad542ed83952f54b8
Related-Bug: #1710831
Related-Bug: #1738100
Adding check code if there is libvirt group or libvirtd group after
pike release.
Currently getting error when setting hugepage option in pike
Change-Id: I324b7d95c659ea047b0fe8e25c8e2faad1077f1a
Closes-Bug: #1747805
Drop support for deployment from Git repositories, as deprecated
in the 17.02 charm release. This feature is unmaintained and has
no known users.
Change-Id: I44a7a92d5d4ae493bab4d5b81e9757cb12149a66
Remove postgresql DB support; This feature is untested as part
of the charms, is not in use and was deprecated as part of
the 1708 charms release.
Change-Id: I327a686a35edf9b6ff5c1c3cbc4165f8faeef688
A similar change will land in designate to drop this extra topic as
well.
Also, driver and topic overrides in a service-specific context are not a
good idea.
Change-Id: I804a34fb044090010ecfd2560594cc1f55e9bd21
Closes-Bug: #1710831
Closes-Bug: #1738100
volumev2 api is deprecated for >= Pike so switch
internal endpoint to v3 for Pike onwards.
Change-Id: I23dffc61a5bfdb4990c744975f13b0e55ef40cbc
Partial-Bug: 1733566
Support for the ZeroMQ messaging driver has bit-rotted over the
last few years across the OpenStack charms; drop support for ZMQ
inline with deprecation notices issues in 17.02 charm release.
Change-Id: I66330dd29972e39e45e9bf81cb0570d5749b8312
Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.
Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.
Change-Id: Ie4189fab0c8ce04f60ada98ec94de98f2a79e302
In the change from py2 -> py3, some expectations around
file modes have changed,and this update changes the tests
to match those expectations.
Change-Id: I6c1348e02024368b70c10d91137f1ed6d9d5a483
During the recent py3 conversion of the charm a couple of places
where the charm writes text in binary mode were missed. This
fixes that problem. Without this fix the charm errors with:
"TypeError: a bytes-like object is required, not 'str'"
Change-Id: I5c2af1dce12092c1ba1be4b4ad9a50261000e886
The current profile does not include ceph paths
which breaks nova-compute if
libvirt-image-backend=rbd when in enforce mode.
Also fix access to /tmp and /var/tmp.
Change-Id: Ie03a43ef73ca5f97f4f9e5edcefd261a0e36abf9
Closes-Bug: 1732492
OpenDev Sysadmins