| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I55a690e621af9c37613cb29ab3cf53d9e1f73435
|
|
ceilometer api and client are dead in queens. lets drop this
client.
Change-Id: I1d2b31977f05c3a912d8704caa019c02c784556e
|
|
|
|
|
|
Change-Id: I5846b48d336583ae82743f61bfbdadc99c755e8d
Partially-implements: blueprint vitrage-roles
|
|
Option "wsrep_on" behaves differently between 10.0 and 10.1 [1]:
"Before MariaDB 10.1, even though this variable is ON by default,
its value get automatically adjusted based on whether mandatory
configurations to turn on Galera replication have been specified.
Since MariaDB 10.1, it is set to OFF by default and must be turned
on to enable Galera replication."
So on MariaDB 10.0 although wsrep_on set to OFF, its value will
automatically adjusted to ON because wsrep mandatory configurations
are set. Whereas on MariaDB 10.1, it will failed at galera provider
'wsrep_ready' checking because wsrep_on is set to OFF.
We can set wsrep_on to ON to handle both 10.0 and 10.1.
But, the point is that the cluster bits, which are creating a cluster
and wsrep_ready checking, are no need at bootstrap stage.
At bootstrap stage it mainly do two things:
Creating required system DBs (by mysql_install_db)
and securing the mariadb (by bootstrap_db).
After the bootstrap stage, it will create a cluster when starting the
first node.
[1] https://mariadb.com/kb/en/library/galera-cluster-status-variables/#wsrep_ready
Partial-Bug: 1740060
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: Ia2acb09e877a586243fc1acb49d8d140cf27d7b5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ceilometer collector is remove from ceilometer code base[1]
[1] https://review.openstack.org/504244
Change-Id: Id15d4d881b0fddcbc5e3f6afd6221a49e15ae704
|
|
Change-Id: I939a495b12fbca545a1b43dce7bc147e6e6bae23
|
|
|
|
Change-Id: I7ffb991adbd05275e331401cd73fc84362084ebd
Closes-Bug: #1738748
|
|
There should be no pip install in binary builds, move the installation
of the downloaded bits where it belongs into the 'source' install_type
section.
Change-Id: I6d8609d072d18e635250df1c1e9aa687ce1f769d
|
|
Change-Id: Id2f0441f65f87fc4a7fdecd1504797d6ca7d9ffc
|
|
|
|
Change-Id: I3a32334b77407a3ab7d3a844573c0161b981b555
|
|
|
|
|
|
We no longer use ceph from upstream as it does not support Debian
'stretch'.`
This reverts commit d4017985a574b6e4eab90213e6f383ef7912b0a3.
Change-Id: Ia363bf93429ea917f242c4a24d78853cf43c95ff
|
|
|
|
|
|
|
|
Since we have bump to ceph luminous. So no need to pin the ceph version
any more.
This reverts commit a0b60bff4386a98a7e2c3e4d549738d34134f4dd.
Change-Id: I7701b768d1189db750c8d0818ced90c4ec508d22
|
|
1. Ceilometer API has been deprecated since Ocata release,
this patch to remove it for kolla
2. move the extend_start.sh into eilometer-notification
Change-Id: Iea0a46aead14e238fe102d4127b7774dbc2be0e4
|
|
When we install 'mongodb-server' package in Debian/stable it errors out
because 'mongodb' user already exists.
It was reported [1] and got resolved in Debian/testing.
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858903
Change-Id: Iabfcbf68a3aea9d7b09b72eb3e8325f09c2f9d31
|
|
Add sensu yum repository to base image
Create images for sensu-server, sensu-api and sensu-client processes
Install a basic set of handler plugins into server image
Install a basic set of sensu plugins into client image
Change-Id: I0b88133080c58070c24ed90059315366b64034c6
|
|
|
|
|
|
Debian 'stretch' has rabbitmq-server 3.6.10 in backports repository so
we will use it instead of external version.
Also take care of 'erlang-base-hipe' (or rather lack of it) on AArch64
architecture.
Depends-on: I72d1d1c10cbc4c5fe0907e395b6d7c969353dff8
Change-Id: Id332215b1e05e6edf18efd85c4463993bb7b321f
|
|
For some images (like rabbitmq) we may need packages from
stretch-backports repository.
Enabling backports does not mean that we use those packages - they have
to be specified by hand.
Change-Id: I72d1d1c10cbc4c5fe0907e395b6d7c969353dff8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
build-swift-ring.py is an ancient artifact from early Kolla days when
Swift was first implemented. It's not documented nor recommended to be
used.
Change-Id: I98f567067e455344ed68774cb35c3f3db26be74d
|
|
* Added python-sushy for CentOS/RHEL for the redfish driver
(introduced in the Pike release).
* Added ansible and systemd-python for ansible driver
(introduced in the Queens cycle).
* Added python-scciclient as it was packaged for CentOS/RHEL.
* Removed seamicroclient, pyghmi and pyremotevbox as the
corresponding drivers were removed.
* Removed wsman as no drivers use it any more: the AMT driver
was removed, the iDrac driver switched to python-dracclient.
Most of removals happened as part of the Ocata driver cleanup:
https://docs.openstack.org/releasenotes/ironic/ocata.html#id9
Change-Id: I8774a45bb1cfcdf5c3b675e235fb074af4a9646c
|
|
in order to be able to use gnocchi as data store for collectd metrics.
Change-Id: Iad404c2c888d2b3b8aed6497224e59f5049ba427
|
|
|
|
This is not needed. If we make sure qemu use nova user.
Because nova user in group qemu.
See comment #7 of bug #1715356:
The root cause for this issue is that qemu not run with nova user on
debian.
If we set qemu running with nova user with this patch:
https://review.openstack.org/#/c/525891/
Then we need to revert commit f1b98a4925826333cf22dafe15ef755066c51d48.
This reverts commit f1b98a4925826333cf22dafe15ef755066c51d48.
Closes-bug: #1715356
Depends-on: I36720af0c7d3dd7c69d2404843f54c0991aea1bb
Change-Id: I62fbcf9e4ee5c3170c96576698f4ae8b66db1b74
|
|
to be able to display statistics from ovs
ovs_events can be used to get notified by events generated by
ovs.
Change-Id: Ifb2e4dd30c88e85d368f359be23e30814d26515f
|
|
"
|
|
heat dashboard is split from horizon code base in Queens cycle.[0][1]
[0] https://review.openstack.org/#/c/523402/
[1] https://github.com/openstack/heat-dashboard
Closes-Bug: #1737475
Change-Id: I920394b8cb6eb7027df9110fe88de6842d2bd8b3
|
|
|
|
|