This commit enables overriding the default storage options of
cinder/swift to a Ceph backed storage for the multinode all in one
deployments.
We also correct the README and build.sh script to show/use the
current defaults correctly for VM_DISK_SIZE and INFRA_VM_SERVER_RAM.
Change-Id: I9e1f1b09d1bcf224f4afa765c585baf28e6cafa8
This commit enables the openstack Octavia load balancing service
if the option is enabled. The Octavia service replaced the legacy
Neutron LBAAS service.
Change-Id: Ib820ec3c4a7f6c9116608140b59332d03cf4c451
The loadbalancer vm is configured to utilize br-dhcp for the external
vip and br-mgmt for the internal vip. Users end up accessing these
from various networks depending on the dev/testing going on. For
example if you utilize the flat network for vms that need to hit the
external api, the calls fail. This is due to traffic coming in on
br-dhcp then going back out on br-flat. This change is to remove the
unused interfaces to cut down on routing issues in the load balancer.
Change-Id: Ic3c3bd18e63943ff288692da20d449852a316b5e
Closes-Bug: #1795710
This is essentially a noop that establishes a healthy DRY pattern of
group var definitions in the pxe_server subgroups.
Change-Id: Ie458f0684f720879c21ca639320814ef12d5dc4e
loadbalancer_vm_server_vcpus is used instead of logging_vm_server_vcpus
for the vcpu override host_vars/logging1.yml file. This review is to
correct the naming error.
Change-Id: I7f335eb8c8baf84ecc122abcba4c315512794b4a
Closes-Bug: 1775211
This change allows someone to modify the vcpu count settings
similar to how the ram is currently done. It also allows for
custom ansible parameters via an MNAIO_ANSIBLE_PARAMETERS var
to add custom ansible parameters for the vpcu overrides as well
as other settings.
Change-Id: I3c1fa7b55a87931eff586c0e983bb9b8c6f34fc3
Closes-Bug: 1750402
This change makes it possible to deploy ACNG within a physical
host NOT automatically tied to an MNAIO installation. This also
adds an infra preseed file which can be used to provision physical
hosts.
By default the domain name is now passed into the server boot params
which is useful when setting up an environment in support of
RFC-1034/5.
Ubuntu 16.04 has an issue with the options "quiet splash" being passed
in which cause it to have no usable console. See [Related-Issue] for
more.
Related-Issue: #1656605
Change-Id: I731dfb70e4b5d676d8c22082da77c0d22d5afb58
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
The VMs deployed are using a very conservative setting for RAM. If a
user has the memory to spare they should have the option to set this
based on their needs.
Change-Id: Ib0fcdada64f009ad5924db171831840120a3eaee
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Currently, instances will not boot as nova.conf is configured with
`reserved_host_memory_mb: 2048` while the compute VMs themselves only
have 2048MB of RAM assigned.
This commit bumps the compute VMs to have 8192MB of RAM so that
instances can be successfully booted.
NOTE: Prior to all the recent refactors that have taken place, we were
giving the compute VMs 9216MB of RAM. I'm not entirely sure why
this number was chosen but can happily change 8192MB to 9216MB to
match what was being used before.
Change-Id: Ie36fcb4fb3f3b5bce27f2851fba0afc6e0d1966a
* 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 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>