Age | Commit message (Collapse) | Author | Files | Lines |
|
Using 'installer' to describe the tool that will deploy the foundations
of a particular XCI scenario is more appropriate than NFVI which
normally describes both the physical and virtual resources needed by
an NFV deployment.
Change-Id: Ib8b1aac58673bf705ce2ff053574fd10cb390d71
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The upstream patchset has been merged, so drop the SUSE
specific workaround when obtaining the status of the galera
cluster.
Link: https://review.openstack.org/#/c/508154/
Change-Id: Ic990e6939fb794a532caf8af2759969198fa5d3a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Introduce a new XCI_DISTRO variable to select the distribution to deploy
on the VMs in order to make deployments more flexible and decouple the
VM OS selection from the host one. The default value for this new
variable is to match the host OS but users can always set it to one
of the supported distributions. We can now simply execute the
install-ansible.sh script instead of sourcing it in order to keep
the environment as clean as possible.
Change-Id: Ia74eb0422f983848cde0fb7b220ea1035dfa78bc
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
It was committed by accident in c74cfd33fc3c ("xci: OSA: Move all the
OSA specific playbooks to the NFVI directory") so drop it.
Change-Id: I5de91f0aad750a9cb723a46baa63e75beb3180de
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
we maybe introduce other NFVI in the future in XCI.
it is necessary to put the nfvi files to corresponding directory xci/nfvi/$NFVI/files,
otherwise the files directory will be confused.
Change-Id: Iea98167ff0bc8d338a94fe1c064ac0ab396c53d3
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
The commit 6b529de0315fe6cd12f6e78c00a5f2f2d3a01e28 in
openstack-ansible-lxc_hosts reverts an earlier change that introduced
systemd-networkd to lxc containers that run OpenStack services. This
prevents the containers from being stopped (ie, lxc-stop fails until it
times out), since systemd-networkd restarts. lxc-stop sends the SIGRT+3
message to the container which the container interprets as "halt".
systemd-networkd conflicts with shutdown, so when the system tries to
enter halt, systemd-networkd gets started again. As a result, the
container does not shut down cleanly.
This patch uses a version of openstack-ansible-lxc_hosts that does not
use systemd-networkd in the containers.
Change-Id: Ie85d2117ce2e6e8afa87810d690eab78e3b3be3d
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
We need to set the 'pipefail' option so if an SSH command fails we stop
the deployment instead of silently ignoring it just because the right
leg of the pipe succeeded.
Change-Id: Iebc720fbd3e6e96fc7135a6cf15e3c0941974d2c
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Move all the playbooks that only make sense for OpenStack-Ansible
deployments to the NFVI/OSA directory where they belong. This further
disassociates XCI from OSA.
Change-Id: Iab8b6dc81d9025a1d85608a98fb1eee0f1c6a69f
Signed-off-by: Markos Chandras <mchandras@suse.de>
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
This is needed in order to update the files before we attempt to
run osa-periodic job.
Change-Id: Ied5a53c294fd753039a6f79fa0ebce24b515cdba
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
In preparation for supporting more NFVIs in XCI, we need to make the
main script NFVI agnostic. Right now, our NFVI is being deployed using
bifrost+OSA so we keep bifrost in the main script since the hardware
provisioning is NFVI agnostic (at least for now) but we move OSA to
its own directory. This should allow more NFVI to plug into XCI by
simply providing a nfvi-deploy.sh script. The user can select the
preferred NFVI using the XCI_NFVI variable.
Change-Id: Ieeacd3b22a64d363feff5d43ff23a80c39038837
Signed-off-by: Markos Chandras <mchandras@suse.de>
|