- charm-helpers sync for new charm-helpers changes
- update tox/pip.sh to ensure setuptools<50.0.0
Change-Id: If2397cf401d1bcec3ff7c622fa9e3477291fc7eb
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: Ia190032a975de9bd242c724e54407918be817bc5
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I520e34a35b250954c0691250c779eee6e804c749
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
* Include NoNetworkBinding late fix.
func-test-pr: https://github.com/openstack-charmers/zaza/pull/409
Change-Id: I1a97004410c5cf4ef98164281137bce46756b12c
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I99b9f3570549921b40c937a983c2624e254bc677
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I1bf6a834b3678f631f6335af9f0e8b779f863c66
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: Id9e0319806471fa4d074c77bff105e2083313e19
When the percona cluster is undergoing a series upgrade, clients
should suspend db activity in their hooks (like db migrations).
This change sents a notification of upgrade down the shared-db
relation which clients can then react to.
Change-Id: I5d8ed7d3935db5568c50f8d585e37a4d0cc6914f
Using the new version of the sync tool which removes the charmhelpers
directory before syncing, run charm helpers sync to find any unexpected
missing dependencies.
Change-Id: Iff046c2fbcf35cc44845a432b8ca2dfcfe257dde
Use helpers from charmhelpers to generate the data to send down the
relation to the hacluster charm.
This results in a few changes in behaviour:
1) The charm will no longer specify a nic name to bind the vip. This
is because Pacemaker VIP resources are able to automatically
detect and configure correct iface and netmask parameters based
on local configuration of the unit.
2) The original iface named VIP resource will be stopped and deleted
prior to the creation of the new short hash named VIP resource.
Change-Id: Id3804fb7913662b8c573f59d84e663561a687b1f
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: I182314eee702cf4bf842b26cb2f2a5c0ee03dcc7
In order to fix bug#1756928 the whole cluster buildup process needed to
be redesigned. The assumptions about what is_bootstrapped and clustered
meant and when to restart on configuration changed needed to be
re-evaluated.
The timing of restarts needed to be protected to avoid collisions.
Only bootstrapped hosts should go in to the
wsrep_cluster_address=gcomm:// setting. Adding or removing units should
be handled gracefully. Starting with a single unit and expanding to a
cluster must work.
This change guarantees mysqld is restarted when the configuration file
changes and meets all the above requirements. As a consequence of the redesign,
the workload status now more accurately reflects the state of the unit.
Charm-helpers sync to bring in distributed_wait fix.
Closes-Bug: #1756308
Closes-Bug: #1756928
Change-Id: I0742e6889b32201806cec6a0b5835e11a8027567
Bionic will ship with Percona XtraDB Cluster 5.7 and a newer
version of Percona XtraBackup; the majority of charm changes
are associated with the use of native mysql{@} units for
bootstrap and startup of mysqld.
Co-Authored-By: James Page <james.page@ubuntu.com>
Change-Id: I50c5642e11393da3bc03de0ef0b9af4c32e9a0c9
Resync charm-helpers to ensure that MySQL syntax is correctly
quoted with single quotes, supporting use of the db-{admin} relation
with services containing a dash.
Change-Id: I859133263a8200e82e73d74837bcb91a18b3e0ff
Closes-Bug: 1675220
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: I22d7f8f37bf53635cb689803eb6e9b5170181bb1
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
Change-Id: I61a6831f381664f9378a1b6a7a119cf3a2c026c2
Related-Bug: #1659575
- Add Zesty as a supported series to metadata.yaml.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: I8f8ccdaf283ba1fa3d3a0efc0014ce49199ddb2a
Refactor to support direct use of BasicDeployment test class
in all gate tests. As hacluster now defaults to using unicast
transport, the configuration for multicast device address is
no longer required and can be dropped, removing the need to
specialize tests on a per series basis.
Use min-cluster-size in tests to ensure that pxc clusters
build out correctly.
Refactor specific test cases into BasicDeployment test
class so they get executed against all series, including
kill mysqld test
pause/resume tests
Closes-Bug: 1546577
Change-Id: I239946808f68a0225b49c0327da2b4d35715b837
Inline with the mysql charm, add a tuning-level configuration option
that allows end users to change the configuration profile for PXC.
This option supports three values
safest (default): use configuration options with best data
integrity guarantees.
fast: compromise some data integrity guarantees
to improve performance.
unsafe: pretty much throw away all data integrity
guarantees to maximise performance.
In clustered deployments, 'fast' and 'unsafe' may be appropriate to
use but should be considered carefully before reconfiguration away
from the default 'safest' option.
Right now, this option tweaks the innodb_flush_log_at_trx_commit
value for PXC:
safest (default): 1
fast: 2
unsafe: 0
but should be used for other tuning optimizations that come along
in the future.
Also add direct configuration options for:
innodb-change-buffering
innodb-io-capacity
to allow end users to tweak other performance optimizations that
we can't yet do automatically using charm options.
This commit also includes a resync of charm-helpers, which includes
the fix to flush priviledges after adding grants to resolve bug
1513239.
Change-Id: I7c31e3bfbb825ae7091913e678dd1b7893892d1d
Closes-Bug: 1599222
Closes-Bug: 1513239
Cap default memory consumption at 512MB or 50% of system memory -
whichever is the lowest - to ensure that deployments in containers
on large server infrastructure don't end up consuming silly
amounts of memory by default.
Update tests to not explicity configure dataset-size, and to
remove the constraint for a larger VM for testing - with the
performance schema disabled by default things should fit into
a default instance size in the gate.
Change-Id: Ifb9bd7e28e160190913f6bd03b84073a2857e4d7