Currently, deploying a multi-node AIO results in
internal_lb_vip_address and external_lb_vip_address being set to the
same IP (10.0.236.150), which results in services having issues
communicating with the lb.
This commit simply sets external_lb_vip_address to use the
load balancer's dhcp address, which is fixed to 10.0.2.150.
Change-Id: I6faabd641c0559a0381e559f364cc76c49293014
Currently, we use lineinfile against /root/.tmux.conf, however if the
file does not first exist the deploy-osa.yml playbook will fail. This
commit simply updates the `Config Tmux` task by adding the create option
to lineinfile so that the config will get created if it doesn't first
exist.
Change-Id: I366c4a875c6e7c2482f28a46bb29a2882b773f30
When using environment variables to setup a proxy, it checks whether
global_environment_variables (for permanent proxy) or
deployment_environment_variables (for playbooks only) is in use and
sets up matching user_variables for OSA. Previously, it only setup
global environment variables.
Added | bool filters as suggested in review.
Change-Id: I6554cd28f817ab0d128a1a469a6007b043851c07
add tmux configuration on infra1 to raise up the history-limit to
20000, which helps troubleshooting the deployment.
Change-Id: I075364868c0b74a297ad6b8ca7dbfec71ca91c27
Adding even more dynamic user config options and a compute preseed.
Change-Id: Ieccbd61a45a77b7dff9e228fc6fdaf92df852abb
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
* added ip alias for interfaces
* Update settings and improve vm performance
* Change the VG name in VMs. The VG name was changed so that the volume
which is being used by VMs can be mounted on a physical host, and not
conflict, with standard volume group naming. This is usful when a VM
is DOA and a deployer wants to disect the instance.
Change-Id: If4d10165fe08f82400772ca88f8490b01bad5cf8
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
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>
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
The current range can cause tempest tests to
allocate floating IPs to the created test servers
that conflict with the IPs of the host VMs.
Change-Id: Ib885122f0ee291f10ecfe9ef4735adc9ae5f5cbf
Add deploy node into the multinode-aio env, move the deployment
and HAproxy into it, and NAT the port 22, 80, 443 into the deploy
node.
Change-Id: I7c886f213e6b3398cb4ecbc36a4ee55fb7f7fd10
Base on the http://packages.ubuntu.com/trusty/kernel/, the
linux-image-generic will install the 3.13.0.112.120 [amd64, i386]
kernel. leave it empty will do nothing to the kernel. this is
important when you deploy ubuntu 14.04.5 on VMs which use 4.4 rather
then 3.13.
Change-Id: I7984edaef5a65320ec3b10085646e8ad5c93f65d
More values have been added to the variables.sh file. None of these have
been adjusted from the default values but this now provides a standard
goto place to have all these values and be able to change with ease.
An include for varibles.sh is now also at the top of each of the script
files.
Change-Id: I2354c87e985115ce0b7f168ab1d056d5032e5cff
By default AIO deploy overrides apt-sources, if things like a local
mirror are already set up then this script will override these. This
option allows for the override to be disabled.
Change-Id: Id84c2c5d12153125d7ac6698493c41a840993c5b
This commit allows for a proxy to be pushed to each of the deployed
containers based on the standard environment variable "$http_proxy".
Change-Id: I94dc3a8afda9472f032fbd94991f8b676131cbfb
Some networks may not allow 8.8.8.8 Google DNS servers. This patch
allows this to be specified in the variables file or to pull the value
from the systems resolv.conf file.
Change-Id: I494ab82c41bcd59ea85404d49cb2696029353a0e
