Age | Commit message (Collapse) | Author | Files | Lines |
|
It switches between parts of the code which are specific for baremetal
or non-baremetal. Those parts come with this patch:
https://gerrit.opnfv.org/gerrit/#/c/60797
It also selects different variables when calling the opnfv-virtual.yml
playbook:
https://gerrit.opnfv.org/gerrit/#/c/60795
It decides the value of BAREMETAL based on the vendor value of the pdf
Change-Id: I8e6171f4f21db7f814a472e6ed1bacb30220b4ec
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
We now support multiple PDF files so instead of introducing another
env variable, we can simply pass this information as command line
arguments to xci-deploy.sh. We can extend the script to allow more
options line verbosity, scenario name, functest details etc so we
can get rid of multiple env variables.
Change-Id: I6c4a8d6e8b70e91746a659de923fee19019ed5e0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The old role has disappeared so we have to use another one.
Change-Id: I8533912a19680e93a9cf061109019a0801485936
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: If87afa892a0c39d082cb1563e1c019f46b742169
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Bifrost no longer installs on the deployment host so we don't need
to look into the bifrost venv for a vbmc installation. Moreover, XCI
uses virtualenv by default, so we should only look there for vbmc.
Finally, we should clear vbmc config files from previous deployments
since that could leave artifacts behind.
Change-Id: I4cd35636a65e1823c9e4ca9a7c5b17d4b103c6a2
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Leap 15 is using ID=opensuse-leap and Tumbleweed is using
ID=opensuse-tumbleweed so we should extend the regexp to match
these distributions as well. This allows XCI to support more
openSUSE variants as deployment hosts.
Change-Id: I8bf8e7b15fc00c45807ff92fbc14d7ec79ec4bcb
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This patch is doing the first work item of the spec:
https://github.com/opnfv/releng-xci/blob/master/docs/specs/infra_manager.rst
It creates the required VMs by XCI to afterwards deploy the VIM. It does that
by reading the pdf provided by the user.
- It is currently assumed that the OS for the VM will be installed in the first
disk of the node described by the pdf
- It is assumed that the opnfv VM characteristics are not described in the pdf
but in a similar document called opnfv_vm.yml
- All references to csv from bifrost-create-vm-nodes were removed
Change-Id: I46a85284e4ce7df21cbf66f66619b35f74251e68
Signed-off-by: Manuel Buil <mbuil@suse.com>
Co-Authored-by: Markos Chandras <mchandras@suse.de>
|
|
In preparation for using PDF/IDF to deploy nodes in XCI, we need to have
shade and python-pyyaml on the host since these are requirements for the
OpenStack Ansible modules (eg os_ironic) and the dynamic inventories.
Change-Id: Ie26af0dc58599af6e29a47d91707976dcf16ac6d
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
OpenStack-Ansible maintains a requirements file which ensure that a
working combination of pip/setuptools/wheels/virtualenv can be mixed up
with distro packages so it's beneficial to take that into consideration
when building our environment.
Change-Id: Ic5398de3e464e1526f8d9fb6b6460907ac30084a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
* changes:
xci: Move the rest of functions to xci-lib.sh
xci: file: xci-lib.sh: Avoid sourcing xci-lib.sh twice
xci: Move sourcing of configuration files to the install-lib.sh
|
|
The xci-deploy.sh contains several functions used throughout in the
XCI deployment so we should move thse to xci-lib.sh file.
Change-Id: Iae6751619beea85b894900e5cd2f91a433410f66
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The file can be sourced from multiple places so we need to avoid
sourcing it twice.
Change-Id: I7d47f3d7e461d90d5456c95a1f7a791b4e3a2bde
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The install-lib.sh assumes that certain configuration files have been
loaded before it's sourced. However, this doesn't work well when other
scripts are using install-lib.sh directly since they also need to load
the same configuration files. As such, lets source all these
configuration files from the install-lib.sh file directly. We also
rename this file to 'xci-lib.sh' since it's not just about installation
helpers anymore.
Change-Id: I35e1e804db06b2bb512e4991e5fdf21a72ffaadb
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We should not wipe the repositories in the localhost playbooks since
it makes it somewhat hard to debug problems. We should do that at the
beginning of the deployment to ensure that we start without any stale
git data.
Change-Id: I70b2ac77284a9ca304d6aa68dbf1654f59260dc4
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
XCI_ANSIBLE_PIP_VERSION is determined dynamically using curl.
This package is not present on every system, hence fails
since it can not install a null version of Ansible
Change-Id: I96a2237e6bdb28e09f0eebee4aae91742973d770
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
|
|
We need to make sure that pip is the first thing we upgrade in the
virtual environment because old pip releases do not support the '-c'
option which we use to install the rest of the required components.
Change-Id: I8b3ec080617324bfefbec2a6cdfa6ef58afb7c20
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
If we don't clear the cache, the script errors out with the following:
fatal: destination path '/root/releng-xci/.cache/repos/openstack-ansible-tests'
already exists and is not an empty directory
Change-Id: I22111ed655a4c6790f808155968deb2fd3828e41
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
|
|
|
|
The hash value for the OpenStack requirements project is consumed
for other projects which can be out of the openstack-ansible scope.
This change creates the OPENSTACK_REQUIREMENTS_VERSION variable using
the openstack_services.yml value as default one.
Change-Id: I4544bcc3f14c107aab8ebba1dced1ba203f07f68
Signed-off-by: Victor Morales <victor.morales@intel.com>
|
|
deploy-scenario:k8-nosdn-nofeature
installer-type:kubespray
Change-Id: I540eb8bad2f35d7029ae8a2148c431f7664fbad0
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
opnfv@linux-r4ap:~$ export LANG="C"
opnfv@linux-r4ap:~$ perl -E exit
opnfv@linux-r4ap:~$ export LANG="c"
opnfv@linux-r4ap:~$ perl -E exit
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US.UTF-8",
LC_ALL = "",
LANG = "c"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
paste of deploy failing: https://hastebin.com/fufananewa.sql
Change-Id: Id1ef2430887251044700e03fc1f294ad18adf90a
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
The ansible-lint tool can help with maintaining consistency across all
the XCI playbooks, so lets introduce it early in the process to capture
common mistakes before the actual XCI deployment is executed. This
however needs to run after all the scenarios repositories have been
cloned and configured.
Change-Id: I28104429e3ac0cdbc48a003b163f4fb8c3acd8a7
Link: https://github.com/willthames/ansible-lint
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Now that all pip installations are managed in the same way we can
move them inside a global virtual environment to further isolate the
XCI artifacts from the rest of the system. Moreover, we further simplify
the initial package installation to install everything at once instead
of calling the package manager for every single package that we need.
Change-Id: I6a170d2439fae8b0653f3141e0e8bb8ead67657e
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
rsync may fail because the OPNFV VM doesn't exist if we failed quite
early in the process so hide any errors from the remote rsync operation
to avoid confusion.
Change-Id: I43dfb0a527165a186674178d12e6d00ffc61f580
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
The OSA deployment is driven by the OPNFV host so we need to install
and configure the ARA plugin there as well.
Change-Id: Ib583f5771a8c2da7531f0a42612d7c0b34fb4898
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
If we switch from one flavor to another then some VMs may left behind
so we need to cleanup the VMs from all flavors.
Change-Id: I8b5d400b6d543b32b9cdaff73c3d173984357012
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
The ARA Ansible plugin can be used to visualize the entire XCI run so
lets install it by default and generate a report at the end of the
execution.
Change-Id: I66c3230b371001c110e81755c5f0dad4b1756606
Link: https://github.com/openstack/ara
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We can avoid "polluting" the system with all the pip packages we install
so we could just install them in the user's home directory.
Change-Id: I5b3369175535e8ab74c2591d1284c743391fd718
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Installing Ansible is just one of the functions we need during XCI
deployment, as such move it to a library file which can contain more
functions in the future.
Change-Id: I708a4e51b2b1d624d6827a8c99f3719b59227ec0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
In some cases the XCI development environment can be located behind a
corporate proxy resulting in a additional layer to consider to
configure. These changes pretend to include proxy support for all
linux distros in all the posible flavors.
Change-Id: Iab469268809ac471d09e244bb3ccd83de1a41b88
Signed-off-by: Victor Morales <victor.morales@intel.com>
|
|
The cleanup script has grown quite a bit over time and it now does more
things than cleaning up old 'bifrost' artifacts to move it to the global
files directory so it can be used by all installers.
Change-Id: Ibf70ff255f14e798216cedc71fb7c5f5476b964a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
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>
|
|
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>
|