airship
/
treasuremap
Code Issues Proposed changes
Reference Airship manifests, CICD, and reference architecture.
733 Commits 5 Branches 5 Tags 28 MiB
Shell 96.8%
Makefile 3.2%
Go to file
Sergiy Markin f9a052075a Full site deploy with custom images 
This PS adds 015-make-all-images.sh script that is
building Airship images locally and using it for
Airskiff site deployment. This script it ment to
be used by Airship projects Airskiff integration
tests.

The old Airskiff deployment gate based on minikube
has been disabled.

Change-Id: I7f85af1f4f0f9a8972dfd54cd0128d4e9caafc2b
 		2024-03-12 16:23:13 +00:00
doc Update gates to ubuntu-focal 2023-03-30 15:50:36 +00:00
global Merge "Full-site deploy" into v1.9 2024-02-09 03:37:53 +00:00
site Full site deploy with custom images 2024-03-12 16:23:13 +00:00
tools Full site deploy with custom images 2024-03-12 16:23:13 +00:00
type Switch mariadb to primary service 2024-02-06 16:14:10 +00:00
.gitignore Update gates to ubuntu-focal 2023-03-30 15:50:36 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:19 +00:00
.style.yapf Standardize Treasuremap code with YAPF 2019-07-24 17:58:10 +00:00
.zuul.yaml Full site deploy with custom images 2024-03-12 16:23:13 +00:00
LICENSE Add license - Apache License Version 2.0 2018-08-17 22:49:32 +00:00
Makefile Standardize Treasuremap code with YAPF 2019-07-24 17:58:10 +00:00
README.md Update README with branching changes 2021-03-23 20:37:09 +00:00
bindep.txt Update gates to ubuntu-focal 2023-03-30 15:50:36 +00:00
test-requirements.txt Standardize Treasuremap code with YAPF 2019-07-24 17:58:10 +00:00
tox.ini Update gates to ubuntu-focal 2023-03-30 15:50:36 +00:00

README.md

Treasuremap

This documentation project outlines a reference architecture for automated cloud provisioning and management, leveraging a collection of interoperable open-source tools.

Architecture

To get started, see architecture.

Please Note:

The branching structure of this repository will be changing to the following:

  • The 'v2' branch will become the 'master' branch
  • The current 'master' branch will become a new 'v1.9' branch
  • The current 'v1.8' branch will remain the same

These changes are planned to take effect on Thursday, April 1, 2021, or slightly thereafter.