RETIRED, Ansible based project for setting up TripleO virtual environments
Go to file
Sandeep Yadav 4ef0f8f99a Pin os_tempest in tripleo jobs
We are using master branch of os_tempest from
always in all branches - train/wallaby

Recently, os-tempest dropped support for EL8
and this broke our Centos8 - train/wallaby job
and rhel8 downstream jobs.

With this patch, we are pinning os_tempest to
a hash before [1] merged.

Alternative is to use correct branch, but we
don't know how much work would that be. And
considering train will be eol soon - we are
going ahead with pinning for now.

[1] 2441b55aac

Closes-Bug: #2020618
Change-Id: I1568e177e6d47409ae09337d5b8775c244090513
2023-05-24 20:59:46 +05:30
ci-scripts Correctly pass environment file to quickstart.sh in full-deploy.sh 2022-03-22 20:44:57 -07:00
config Merge "Revert "Exclude latest gnupg2 & Pin to last good version"" 2023-04-17 18:59:55 +00:00
doc Fix tox4 issues 2022-12-27 14:32:43 -03:00
library Run all linters via pre-commit 2019-01-15 11:14:31 +00:00
molecule/install-deps Move tox-molecule job to centos stream 8 2022-01-31 13:11:55 -07:00
playbooks Bump linters and remove dead code 2021-07-13 16:04:08 +03:00
releasenotes Switch to newer openstackdocstheme and reno versions 2020-06-03 20:39:39 +02:00
roles Adds mixed os vars to be used with per role container image prep 2023-02-03 12:05:45 +02:00
test_plugins Fix H102 Apache 2.0 license header not found 2016-07-29 14:08:00 -04:00
tests Remove explicit set for whole_disk_image: true 2021-11-16 16:56:53 +00:00
zuul.d Tripleo-CI master CI teardown check and gate only branchful jobs 2023-04-24 14:05:44 +00:00
.ansible-lint Bump linters and remove dead code 2021-07-13 16:04:08 +03:00
.gitignore Remove developer tools from tripleo .gitignore 2018-11-06 14:38:51 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:42:42 +00:00
.pre-commit-config.yaml Fixes ansible-lint in tox linter job 2023-05-18 04:12:26 +02:00
.yamllint Run all linters via pre-commit 2019-01-15 11:14:31 +00:00
Dockerfile Docker file for running quickstart in container 2018-01-15 18:29:55 +00:00
LICENSE Run all linters via pre-commit 2019-01-15 11:14:31 +00:00
README.rst Fix --install-deps bindep for quickstart.sh 2019-05-15 16:40:58 -03:00
ansible-collection-requirements.yml Choose version of Ansible OpenStack collection based on RDO release 2022-10-17 20:05:32 +02:00
ansible-role-requirements.yml Pin os_tempest in tripleo jobs 2023-05-24 20:59:46 +05:30
ansible.cfg Add the default collection path to ansible.cfg 2021-12-02 12:43:44 +02:00
ansible_ssh_env.sh Use export in ansible_ssh_env file 2016-10-20 17:11:08 +00:00
bindep.txt Revert sudo and six workarounds for virtualenv 20.0.1 issues 2020-02-28 16:48:40 +00:00
devmode.sh OpenDev Migration Patch 2 2019-04-22 10:51:54 +05:30
fs-matrix.py Added fs067 for standalone ffu 2022-11-07 09:07:50 +01:00
install-deps.sh Increase verbosity of ansible-galaxy commands 2022-07-26 13:31:40 +02:00
molecule-requirements.txt Move tox-molecule job to centos stream 8 2022-01-31 13:11:55 -07:00
quickstart-extras-requirements.txt Install roles with ansible-galaxy 2022-04-08 08:37:43 -07:00
quickstart-role-requirements.txt Removing locking hash on undercloud post role 2016-09-14 03:33:22 -04:00
quickstart.sh Use Ansible OpenStack collection <2.0.0 for RHOS releases 2022-10-24 13:25:41 +02:00
requirements.txt Run CI with Ansible 2.11 2021-11-16 17:10:17 +00:00
setup.cfg Update docs building 2020-05-08 12:50:20 +00:00
setup.py Disable auto discovery as a workaround 2022-03-25 19:40:13 +05:30
test-requirements.txt Switch to newer openstackdocstheme and reno versions 2020-06-03 20:39:39 +02:00
tox.ini Fix tox4 issues 2022-12-27 14:32:43 -03:00

README.rst

Team and repository tags

image

tripleo-quickstart

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

Note

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

The 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 AllowUsers includes stack.

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 quickstart.sh script.

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.