airship/porthole
Code Issues Proposed changes
Airship utility CLI access
334 Commits 1 Branch 0 Tags 8 MiB
Smarty 63.5%
Python 22.5%
Shell 10.2%
Makefile 2.6%
Jinja 1.2%
master
Go to file
Sergiy Markin e2b4199c4c Security updates 
This PS updates Openstack modules to Caracal
2024.1, updates base ubuntu  image to
quay.io/airshipit, Helm to v3.15.2 and Kubectl to
1.32.0

Change-Id: I0c4f16443ae88e4cfbc54e23222eaf84264580b5
2024-12-24 00:58:28 +00:00
charts Switch to py310 and new kubernetes 1.30.0 2024-09-23 15:18:21 +00:00
doc Update porthole project 2023-06-02 16:01:08 +00:00
images Security updates 2024-12-24 00:58:28 +00:00
jmphost Enforce the use of the correct kubectl client version 2020-01-06 19:31:09 +00:00
kube_utility_container Security updates 2024-12-24 00:58:28 +00:00
tools Security updates 2024-12-24 00:58:28 +00:00
zuul.d Update calicoctl version in jammy image 2024-09-25 21:53:05 +00:00
.gitignore Porthole upgrades 2023-06-23 18:48:26 +00:00
.gitreview Add .gitreview 2019-08-07 14:41:35 +00:00
bindep.txt Update porthole project 2023-06-02 16:01:08 +00:00
LICENSE Initial commit 2018-09-05 14:42:30 -05:00
Makefile Switch to py310 and new kubernetes 1.30.0 2024-09-23 15:18:21 +00:00
README.md Replace Postgresql UC deployment Process 2020-04-08 01:00:25 +00:00
requirements-direct.txt Security updates 2024-12-24 00:58:28 +00:00
requirements-frozen.txt Security updates 2024-12-24 00:58:28 +00:00
requirements.txt Update porthole project 2023-06-02 16:01:08 +00:00
setup.cfg Create an initial Automation Validation Testing framework 2020-06-12 13:43:58 -04:00
setup.py Update porthole project 2023-06-02 16:01:08 +00:00
test-requirements.txt Security updates 2024-12-24 00:58:28 +00:00
tox.ini Switch to py310 and new kubernetes 1.30.0 2024-09-23 15:18:21 +00: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

=======

  1. To run further commands from the CLI manually, execute the following to set up authentication credentials

     export OS_CLOUD=openstack_helm

  2. Clone the Porthole repo to openstack-helm project

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

To deploy utility pods

  1. To Deploy Utility containers, Please run required scripts

     cd porthole

  2. Deploy Calico-utility. ./tools/deployment/utilities/005-calicoctl-utility.sh

  3. Deploy Ceph-utility.

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

  4. Deploy Compute-utility.

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

  5. Deploy Etcdctl-utility.

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

  6. Deploy Mysqlclient-utility.

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

  7. Deploy Openstack-utility.

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

  8. 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).