Age | Commit message (Collapse) | Author | Files | Lines |
|
This also improves (again!) the check for parallel packages managers
to print some useful messages for debugging.
Change-Id: I7756db80aa3ed42cd3ef37293f7116b5a9c150c1
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
When running the bifrost jobs for the OPNFV 3rd Party CI, the Ironic
variables are not defined and we get the following error:
./scripts/bifrost-provision.sh: line 112: BIFROST_IRONIC_INSPECTOR_VERSION: unbound variable
As such, we need to provide reasonable defaults when we are running this
script outside of XCI.
Change-Id: I9cc3ae1b70494637a85558b9cae99fc1eeaebc74
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
* Bump up upstream SHAs
* With these upstream SHAs, OSA installs neutron-agent container on
controller node which would require eth12 interface on controller for
establishing vlan provider networks. so adding eth12 interface and
linking it with br-vlan over br-vlan-veth link.
Change-Id: Iaf7cbe6e41dcfd15ec6527c5a50701f2d05eaad8
Signed-off-by: Markos Chandras <mchandras@suse.de>
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
We should pin the SHAs for Ironic components as part of the regular
bifrost bump to ensure maximum long term stability. This also bumps
the bifrost SHA to the latest available one.
Change-Id: Ia66d8ab6566db58e2ddab5134eb8445bd84d2a8f
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The Ironic components are currently being installed from PIP but we
should install them from the git repo instead so we can always try
the latest code from master or the pinned version when such
functionality is implemented.
Change-Id: I0138c54befe52ed9df8bf617b78e063df3cf8750
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
The CI nodes come with a big secondary mechanical disk which can be
attached directly to the clean VM. As such, we split the disk into one
logical volume per distribution and flush the qcow2 image to it before
attaching it to the VM. If the XCI volume group is not available, then
we revert back to using a file-based storage backend. Finally, we hide
stdout/stderr from the package installation process to minimize the
script output.
Change-Id: I11ea82899c411f8a4168e5f23cbbd8187cc891df
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This change brings in the fix for policy.json removal.
https://review.openstack.org/#/c/536349/
Change-Id: Ib18a99502c0ce61278e13f25a01622e073749d14
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
It follows the change "Rename a common credential file for OS and
K8S" which stops forcing OpenStack creds.
[1] https://gerrit.opnfv.org/gerrit/#/c/51283/
Change-Id: Ic83a2e696c9ea8821e29e6b3f4e69db25c528a0d
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
|
|
|
|
Install some additional packages to the clean VM which can be useful
during debugging. Moreover, we move the common distribution packages
into a variable in order to simplify the code a little bit.
Change-Id: I0405820900a15fec730a2bbfc95a1d1f3485bf0f
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
This commit introduces kubespray into XCI.
k8s install currently assumes k8s install
and OpenStack install cannot coexist.
If XCI_INSTALLER is set to "kubespray" and
DEPLOY_SCENARIO is set to "k8-nosdn-nofeature"
the xci-deploy.sh would install kubernetes instead of OpenStack.
The version of kubernetes is beta release v1.9.0 currently
according to the master of kubespray
it only support the ubuntu now.
Opensuse and centos still need to develop and test.
This patch create the directory xci/installer/kubespray,
the related files of kubespray would be placed to it.
The xci/installer/$installer/playbooks/configure-localhost.yml was moved
to xci/playbooks/configure-localhost.yml as a common yaml file.
You can modify some parameters according your need
in xci/installer/kubespray/files/k8s-cluster.yml to deploy cluster.
When deploying kubernetes,
it would download the kubespray to releng-xci/.cache/repos/kubespray.
If your flavor is Ha, it will download haproxy_server and keepalived
to xci/playbook/roles, which setup haproxy service for kubernetes.
Change-Id: I24d521a735d7ee85fbe5af8c4def65f37586b843
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
DeltaRPM allows to install only the difference between an old and new
version of an RPM, as consequence this reduces the network
consumption in CentOS distros.
Change-Id: I317fbac44ae5fb6d5293443e755e2b7ddd08c66e
Signed-off-by: Victor Morales <victor.morales@intel.com>
|
|
Functest requires to read the variable TEST_DB_URL from the env. variables:
https://gerrit.opnfv.org/gerrit/#/c/49757/
Change-Id: Idbfc2df989f5b2a8e6ddd2d9a9a70526dd9bf1f4
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
|
|
Add the DEPLOY_SCENARIO variable to the list of information we
collect when deployment fails.
Change-Id: I7081b80feea1d3d2ff83e54bd5e614b4ea98964d
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The package requirements are the same across distros so
we simply hardcode them in the task. Fixes the following problem:
fatal: [opnfv]: FAILED! => {"changed": true, "cmd":
"/root/run-functest.sh", "delta": "0:00:09.150226", "end": "2018-01-26
14:01:18.758704", "failed": true, "rc": 125, "start": "2018-01-26 1
4:01:09.608478", "stderr": "/root/run-functest.sh: line 14: wget:
command not found
Change-Id: Ib07acac18f8ece1111ee0706766f32005d0ac1da
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Previously xci-deploy.sh looks up the xci_overrides files under
$XCI_SCENARIOS_CACHE/${DEPLOY_SCENARIO} directory, but actually
xci_overrides file resides somewhere in the nested directory level
in both inband/outband scenarios. Hence the fix is done by using
the find command.
Change-Id: Icb507471e368f56290ef91d555673830b598e204
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
This change integrates functest in most easiest and messy way to
get it up and running to bring functest into CI. The reason for
this is that there are strange failures during functest healthcheck
and it is important to look into those rather than beautifying how
functest is integrated at this phase.
Change-Id: I42e993be4aa15da022fa1e0069338447780f177e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
We should look again for active package managers when the timer expires
to avoid locking issues.
Change-Id: I88f0299a87befce17d11ba7581f0330979a25345
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
When the user selects an invalid combination then some facts may not be
set so the deployment may fail in a crypt way like in the following case
fatal: [localhost]: FAILED! => {"failed": true, "msg": "The conditional
check 'deploy_scenario_installer' failed. The error was: error while
evaluating conditional (deploy_scenario_installer):
'deploy_scenario_installer' is undefined\n\nThe error appears to have been in
'/home/opnfv/releng-xci/xci/playbooks/get-opnfv-scenario-requirements.yml':
line 114, column 11, but may\nbe elsewhere in the file depending on the
exact syntax problem.\n\nThe offending line appears to be:\n\n
when: item.installer == XCI_INSTALLER\n - set_fact:\n
^
here\n"}
Change-Id: I931376d99bb178b15c4a9a71d47b48b01b858e4e
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The basic support for CentOS has been merged and it passes the CI
so drop the warning.
Change-Id: I70e6ba0fcd851d2eb9bfcb24d185276ed68c1005
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Changes that make it possible to run XCI on CentOS:
- Remove the check on xci-deploy.sh script that exists on RedHat family
(including CentOS) and making the error into a warning.
- Add centos to a distro in opnfv-scenario-requirements
Change-Id: Ief6f1e50d8c7c9d8787641827e57682a6e0549e4
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
Change-Id: If8c0de44c313fdc22b1c7443b12d42769035c5b0
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
'redhat' as a ansible_os_family covers both the RedHat distros and
CentOS.
Change-Id: I2ab56024d2c0f1f40a014a236cfd94ef38daad04
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
Galera installation in CentOS fails because the mysqld.sock file is in a
different location, despite what the my.cnf configuration tells. This
has been worked around in upstream OSA-galera_server:
https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/
commit/?id=f2bfbd38513ac8d61ba4e02a4d5ef6cbbca259cc
Change-Id: Ied11571189eff8cbab0f1990a7599b51cad9ea2b
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
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>
|
|
A scenario may only support certain NFVIs or distributions so we
need a mapping with all these things so we know what can be tested
and where.
Change-Id: Ibf1b640b762085f58627e05e1d2ca13edfc4d716
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 location where we were putting the scenarios was wrong as it was
placing them in xci/playbooks/roles/$scenario/$scenario so in the end
the Ansible couldn't find the role we were looking for. As a result,
the role was never executed. Moreover, we can use the synchronize
module instead of the shell which should be both faster and safer.
Change-Id: I3d996652bb6a62d23e259da5674d94596dad4d8d
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
|
|
Make sure that any local changes to scenarios are being propagated to
the checkouts. This should only happen when we are testing the 'master'
branch of the scenario since it may be desirable to test a specific SHA
in which case we shouldn't modify the checkout code.
Change-Id: I4197f09a3e4d5a54c86905bc556b06e08948fbc2
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
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>
|
|
1. the "+" and "'" will be part of the string in the path parameter of ansible.
So the directories we create are not right. we need remove these char.
2. it miss the "{{" in ansible variable
Change-Id: I30c9804450588c63f5f18c63c1d90cd869fad90e
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|