We did not have a easy way to ensure all the openstack clients are
installed on a given system. In the old instack-undercloud installation,
we were installing some additional clients outside of the ones required
via python-tripleoclient. To allow a user to quickly install all the
clients on a given system, this change adds an OpenStack clients
"service" which can be added to a role to ensure the clients are
available. In the future if we provide a client container, this service
can be converted into a container deployment mechanism.
Change-Id: If878c2ab7679eea2fff42b410bec9c8c9b92ed6f
Closes-Bug: #1800001
In some cases we may need to disable selinux (like in CI). The role
needs the SELinux service so that the management can be done during the
deployment.
Change-Id: Ife3c4600f5bd70490a68059eb27c5100743a5298
Closes-Bug: #1797910
Similarly to undercloud, Swift is using only a single replica on AIO
(all-in-one standalone). Therefore recovering from a corrupted or lost object
is not possible, and running replicators and auditors only wastes resources.
And may create some trouble. For example, the DB replicators and auditors will
lock the DB, and new objects won't be stored during that time.
Related-Bug: #1797167
Change-Id: I839393bf6cbb2303a0359f8aed32b2fc67d46f6a
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
The standalone role can be used either with the tripleo deploy command
to deploy locally, or it can be used with an undercloud to deploy an
all-in-one node. This change provides a sample set of environment files
for both deployment mechanisms.
Change-Id: Ibc735ac4326a9217469e368c074de8b0df7689bd
Related-Blueprint: all-in-one
With the standalone deployment mechanism, the default list of enabled
OpenStack services is Keystone, Nova (and related), Neutron (and
related), Glance, Cinder, Swift and Horizon. The default list of
disabled of OpenStack services is Aodh, Barbican, Ceilomter,
Congress, Designate, Gnocchi, Heat, Ironic, Manila, Mistral, Panko,
Sahara, Tacker and Zaqar. Disabled services can be enabled by
passing the appropriate environment files to re-enable them during
the deployment.
Change-Id: Ibf49ac61f4a50b429e72ebeb5b35f6524ae8f24d
Related-Blueprint: all-in-one
Implement a post script for the standalone to generate a basic
clouds.yaml for use with various tools. This one does not reuse the
undercloud post because the undercloud script performs a bunch of
undercloud specific functions.
Change-Id: I0496f4dd2026ab6c705683126c8f50302a0861b9
For a standalone all-in-one, we need to create a basic role that has
some of the services, a network config for a single node and an
environment file that has all the services defined but disabled so
that we can enable just the services we will need. In the future, we
will likely make the service list more dynamic but for now it contains a
minimal set of services for a keystone/openshift/kubernetes deployment.
Change-Id: Ieb7c94563bd0132393b5fa268d743981f6e0b6f2
Related-Blueprint: all-in-one