RPC is using r11 and 11 for kilo, same for upper branches.
We should be more lenient to the version allowed, whether it's
starting with a r or not, as long as the major version is the
same number.
Change-Id: I42053681fdc5e0b2c16060d8a51b4a620569f38c
If we interrupt the process in unarchive, we'll have a broken
idempotency state: The leapfrog process will run again the venv
prep, the synchronize will be unchanged, and the unarchive
rewire will never run.
Change-Id: I8e91ef39d4ecbc9ff5a6a4a73cd0ce4679d6ecf0
If a user is using a REDEPLOY_EXTRA_SCRIPT to migrate additional
variables before re-deploying, it's maybe best to re-run all the
playbooks that happen in a deploy. All the playbooks are already
there, excepted the openstack-hosts-setup, so we add it here.
Change-Id: I64bade46cb1ece6f21ed42c7622bd6e39f2420fe
This change ensures that all handlers that are triggered are fired which
should assist in cases where a playbook fails and is then rerun.
Change-Id: I6b53611df72cbd0a98bc6d58cff786ae3662e9c5
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This change allows the MNAIO to really be used as a stand alone kick
system which has the potential to be developed into a stand alone
project. At the very least this change improves playbook performance
by scoping variables.
The inventory has been converted into a typical Ansible inventory and
the "servers" used in the MNAIO are now simply host_vars
which will trigger specific VM builds when instructed to do so. This
gives the MNAIO the ability to serve as a stand alone kick system which
could be used for physical hosts as well as MNAIO testing all through
the same basic set of playbooks. Should a deployer want to use this with
physical servers they'd need to do nothing more than define their basic
inventory and where the the required pieces of infrastructure needed to
PXE boot their machines.
Change-Id: I6c47e02ecfbe8ee7533e77b11041785db485a1a9
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Sadly the log node does not have enough ram to run a full ansible run.
Ansible 2.x requires more ram than one would expect, especially when the
inventory gets large. this change moves the deploy node to infra1 as it
will already have the ram needed to run the playbooks. Additionally the
container storage for infra nodes was too small which forces builds into
error. The default storage for VMs has been set to 90GiB each and the
preseed will create a logical volume for VMs mounted at /var/lib/lxc.
While the limited ram works well for the VMs and within a running
deployment of OSA, ansible-playbook is subject to crash like so:
An exception occurred during task execution. To see the full traceback,
use -vvv. The error was: OSError: [Errno 12] Cannot allocate memory
fatal: [infra1_cinder_api_container-b38b47ea]: FAILED! =>
{"failed": true, "msg": "Unexpected failure during module execution.", "stdout": ""}
So infra nodes have had the memory constraint raised to 8GiB
Change-Id: I7175ea92f663dfef5966532cfc0b4beaadb9eb03
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This change ensures that the VMs and host systems cache apt packges
locally which will speed up the boot and deployment process.
Change-Id: I234e338b9f1b9f11ff1e81ede8c5717e033fdad8
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This reduces the resource consumption by removing the deploy node and
using the log node instead. This also ups the ram allocation to the
infra hosts which will improve the deployment experience by ensuring we
don't run out of memory.
Change-Id: Id38ff386669308ac3fd1e539ae37c969f00353b8
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
The original mnaio was built using a lot of bash and was tailored
specifically for ubuntu 14.04. The new mnaio was built using a mix of
bash and ansible and was tailored specifically for ubuntu 16.04. This
patch takes the two code bases and combines the best things from each
method and wraps it up into a single code path all written using ansible
playbooks and basic variables.
While underlying system has changed the bash environment variable syntax
for overrides remains the same. This allows users to continue with what
has become their normal work-flow while leveraging the new structure and
capabilities.
High level overview:
* The general performance of the VMs running within the MNAIO will now
be a lot better. Before the VMs were built within QCOW2 containers,
while this was flexible and portable it was slower. The new
capabilities will use RAW logical volumes and native IO.
* New repo management starts with preseeds and allows the user to pin
to specific repositories without having to worry about flipping them
post build.
* CPU overhead will be a lot less. The old VM system used an
un-reasonable number of processors per VM which directly translated
to sockets. The new system will use cores and a single socket
allowing for generally better VM performance with a lot less
overhead and resource contention on the host.
* Memory consumption has been greatly reduced. Each VM is now
following the memory restrictions we'd find in the gate, as a MAX.
Most of the VMs are using 1 - 2 GiB of RAM which should be more than
enough for our purposes.
Overall the deployment process is simpler and more flexible and will
work on both trusty and xenial out of the box with the hope to bring
centos7 and suse into the fold some time in the future.
Change-Id: Idc8924452c481b08fd3b9362efa32d10d1b8f707
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This change fixes the removal of neutron agent containers so that it no
longer relies on the containers existing on the deploy host.
The file `leapfrog_remove_remaining_old_containers` is only created on
the deploy host, when combined with the fact that the original task
couldn't fail, it resulted in the removal of the containers silently
failing on multi-node builds.
This change gets the list of containers from the file on the deploy host
before trying to delete them on all hosts.
Change-Id: Ic95187fd7e7ff93c796ce01f296cb06a16ba72bd
1, add deploy node into mn-aio-xenial
2, change the nic to eth0 because kvm needs it
3, local cache the ubuntu image for faster installation.
Change-Id: I9be2493fc64481c3e6249cb5e2d36c708545ad3d
In cases where the deployment node is seperated from the infrastructure
node, the openstack-release file discovery logic might calculate the
wrong release since the /etc/openstack-release file does not get generated
on the deployment node.
This commit adds logic to pull down the /etc/openstack-release file from
the infrastucture node to the deployment node. This way, the release discovery
logic will properly assess the openstack release even in situations where the
deployment node is isolated from the infra node.
If the openstack-release file is not found, an attempt to retrieve the
rpc-release file is made.
A conditional is added to check if the rpc-release file exist in the
environment. If it does, and there is no openstack-release file, then
the deployment version is set to Juno.
Co-Authored-By: git-harry <git-harry@live.co.uk>
Change-Id: I6136609ef11be7b98ddcfc7589dd17cf1e98c362
`libmysqlclient-dev` is missing, when performing a Kilo to Newton upgrade
on a multi-node AIO, causing `mysql-python` to fail to install. This
change ensures it is present.
Change-Id: Id418929b1713357bea183c50b64219f175aee9bc
This change is necessary to ensure that all the required PIP packages
are installed. Without this change the code assumes that if the version
of `pip` in okay then all the required packages are already installed.
Change-Id: I16a4eaf24e346411a7f0890d69939f666ecc6be3
Make sure the script is still going if REDEPLOY_EXTRA_SCRIPT is null
or not set, and will run extra script if it is not null.
Change-Id: Ic4b37ccc0ac6c23be892fee7ccd2c82f6f1d7da1
If leapfrogging from Kilo (and above) with a host named rpc.*
all the containers will be wiped during the step
``neutron-remove-old-containers.yml``.
Change-Id: I2e1106bcce12547d6ab9e0384cd96d5e0194001d
Make sure the liberasurecode-dev is installable when needed, in order
to build the venvs for swift.
No distinction is done anymore for backports/anything else like UCA.
Change-Id: I552b77eeb05469b815592da1dd7fab45124ffe89
the auto reboot config should be
d-i finish-install/reboot_in_progress note
not
finish-install finish-install/reboot_in_progress note
Change-Id: Id8e44de5e6376bb576115b0eeca49dc04edf8ed8
