Following changes are done with this patch:- - Ussuri+ releases are CentOS8 only, switch the standalone environment settings to reflect the same. - Add some os tempest options in standalone environment file to get tempest run with it. - Enable repo setup on virthost it will be needed to get repos needed by DLRN run. - Add settings to not prepare overcloud nodes as standalone deploy doesn't need those. - Also add some vars required for standalone deployment. - Do not use egg_info for tripleo-quickstart-extras path to avoid quickstart-extras installation from pip cache and instead install it from specified path. This environment file will be used to test standalone deployments on ci.centos.org. Closes-Bug: #1889219 Depends-On: I87a0214a344a9b23dd267e412a37b2abe0eb0571 Change-Id: Ic17bf6e69b1620bdcca339f436e1399b29c0437e
|1 week ago|
|ci-scripts||17 hours ago|
|config||17 hours ago|
|doc||2 months ago|
|library||1 year ago|
|molecule/install-deps||4 months ago|
|playbooks||1 month ago|
|releasenotes||2 months ago|
|roles||3 weeks ago|
|test_plugins||4 years ago|
|tests||1 year ago|
|zuul.d||2 months ago|
|.ansible-lint||7 months ago|
|.gitignore||1 year ago|
|.gitreview||1 year ago|
|.pre-commit-config.yaml||7 months ago|
|.yamllint||1 year ago|
|Dockerfile||2 years ago|
|LICENSE||1 year ago|
|README.rst||1 year ago|
|ansible-role-requirements.yml||1 year ago|
|ansible.cfg||2 months ago|
|ansible_ssh_env.sh||3 years ago|
|bindep.txt||5 months ago|
|devmode.sh||1 year ago|
|fs-matrix.py||2 months ago|
|install-deps.sh||1 week ago|
|molecule-requirements.txt||4 months ago|
|quickstart-extras-requirements.txt||2 months ago|
|quickstart-role-requirements.txt||3 years ago|
|quickstart.sh||1 month ago|
|requirements.txt||4 months ago|
|setup.cfg||3 months ago|
|setup.py||4 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||3 months ago|
An up-to-date HTML version is available on docs.openstack.org.
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/tripleo-quickstart/
One of the barriers to entry for trying out TripleO and its derivatives has been the relative difficulty in getting an environment up quickly.
This set of ansible roles is meant to help.
Quickstart's default deployment method uses a physical machine, which is referred to as
$VIRTHOST throughout this documentation. On this physical machine Quickstart sets up multiple virtual machines (VMs) and virtual networks using libvirt.
One of the VMs is set up as undercloud, an all-in-one OpenStack cloud used by system administrators to deploy the overcloud, the end-user facing OpenStack installation, usually consisting of multiple VMs.
You will need a
$VIRTHOST with at least 16 GB of RAM, preferably 32 GB, and you must be able to
ssh to the virthost machine as root without a password from the machine running ansible. Currently the virthost machine must be running a recent Red Hat-based Linux distribution (CentOS 7.x, RHEL 7.x). Other distributions could work but will not be supported with out CI validation.
Quickstart tool runs commands with superuser privileges as installing packages to the deployer system. The script should be run by a sudo user, e.g.
deployer, which should be added to the sudoers configuration, as shown below:
deployer ALL=(ALL) NOPASSWD: ALL
Running quickstart.sh commands as root is not suggested or supported.
The SSH server on your
$VIRTHOST must be accessible via public keys for both the root and stack users.
A quick way to test that root to your virthost machine is ready to rock is:
ssh root@$VIRTHOST uname -a
stack user is not added until the quickstart deploy runs, so this cannot be tested in advance. However, if you lock down on a per-user basis, ensure
Timeouts can be an issue if the SSH server is configured to disconnect users after periods of inactivity. This can be addressed for example by:
ClientAliveInterval 120 ClientAliveCountMax 720
The quickstart defaults are meant to "just work", so it is as easy as downloading and running the
Copyright 2015-2016 Red Hat, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.