Go to file

Arun Nagarajan c5a71ce811 Upgrade stestr version for inclusive jargon

The older versions of stestr (like 2.1.1), had options which made use
of some derogatory/non-inclusive terms. These are now in the process of
being deprecated, in favour of more succint yet non-discriminative
words! The new options are available starting from v3.1.0, which is
being added here.

Ref: https://github.com/mtreinish/stestr/issues/296

Change-Id: I373de9fd6cc0d95ab5416535e65460917cd1f624

2020-12-16 20:07:10 +00:00

charts

Correct small issue trying to get the ON_DEMAND pod name

2020-11-05 15:17:07 -06:00

docs

Create an initial Automation Validation Testing framework

2020-06-12 13:43:58 -04:00

images

Fix issue reading backup/restore secrets

2020-10-05 22:56:54 +00:00

jmphost

Enforce the use of the correct kubectl client version

2020-01-06 19:31:09 +00:00

kube_utility_container

Merge "Add Below test Cases to Postgres Utility Container"

2020-08-19 17:38:17 +00:00

tools

Switch to ensure-docker role

2020-09-21 20:05:43 +00:00

zuul.d

Rename Zuul Test Job

2020-08-19 17:45:28 +00:00

.gitignore

Chart/Dockerfile for Ceph Utility Container

2019-01-10 10:08:55 -06:00

.gitreview

Add .gitreview

2019-08-07 14:41:35 +00:00

LICENSE

Initial commit

2018-09-05 14:42:30 -05:00

Makefile

Create an initial Automation Validation Testing framework

2020-06-12 13:43:58 -04:00

README.md

Replace Postgresql UC deployment Process

2020-04-08 01:00:25 +00:00

requirements-frozen.txt

Upgrade stestr version for inclusive jargon

2020-12-16 20:07:10 +00:00

requirements.txt

Upgrade stestr version for inclusive jargon

2020-12-16 20:07:10 +00:00

setup.cfg

Create an initial Automation Validation Testing framework

2020-06-12 13:43:58 -04:00

setup.py

Create an initial Automation Validation Testing framework

2020-06-12 13:43:58 -04:00

test-requirements.txt

Upgrade stestr version for inclusive jargon

2020-12-16 20:07:10 +00:00

tox.ini

Create an initial Automation Validation Testing framework

2020-06-12 13:43:58 -04:00

README.md

Utility Containers

Utility containers give Operations staff an interface to an Airship environment that enables them to perform routine operations and troubleshooting activities. Utility containers support Airship environments without exposing secrets and credentials while at the same time restricting access to the actual containers.

Prerequisites

=======

Deploy OSH-AIO.

Deploy the Openstack-Helm All-in-One environment starting from here up through the section Deploy Compute Kit

The recommended minimum system requirements for a full deployment are:

16 GB RAM
8 Cores
48 GB HDD

=======

To run further commands from the CLI manually, execute the following to set up authentication credentials
```
 export OS_CLOUD=openstack_helm
```

Clone the Porthole repo to openstack-helm project

 git clone https://opendev.org/airship/porthole.git

To deploy utility pods

To Deploy Utility containers, Please run required scripts
```
 cd porthole
```
Deploy Calico-utility. ./tools/deployment/utilities/005-calicoctl-utility.sh

Deploy Ceph-utility.

 ./tools/deployment/utilities/010-ceph-utility.sh

Deploy Compute-utility.

 ./tools/deployment/utilities/020-compute-utility.sh

Deploy Etcdctl-utility.

 ./tools/deployment/utilities/030-etcdctl-utility.sh

Deploy Mysqlclient-utility.

 ./tools/deployment/utilities/040-Mysqlclient-utility.sh

Deploy Openstack-utility.

 ./tools/deployment/utilities/050-openstack-utility.sh

Deploy `Postgresql-utility'. ./tools/deployment/utilities/060-postgresql-utility.sh

NOTE

The PostgreSQL utility container needed Postgresql DB Pods for Testing. Please follow below Link. [PostgreSQL README](https://opendev.org/airship/porthole/src/branch/master/images/postgresql-utility/README.md).