airship
/
treasuremap
Code Issues Proposed changes
Reference Airship manifests, CICD, and reference architecture.
708 Commits 5 Branches 5 Tags 28 MiB
Shell 96.8%
Makefile 3.2%
Go to file
Sergiy Markin 430f817644 Update airskiff to focal 
The following Airship images were uplifted to latest-ubuntu_focal:
- promenade
- drydock
- deckhand
- airflow
- shipyard
- pegleg

Also latest charts were uplifted for the projects above.

Also openstack-helm-infra commit ip has been updated to
97ce6d7d8e9a090c748800d69a57bbd9af698b60

Change-Id: I18b1e8fb86d275ac937508caa1923dfb79c901a0
 		2023-05-04 05:45:02 +00:00
doc Update gates to ubuntu-focal 2023-03-30 15:50:36 +00:00
global Update airskiff to focal 2023-05-04 05:45:02 +00:00
site Update airskiff to focal 2023-05-04 05:45:02 +00:00
tools Update airskiff to focal 2023-05-04 05:45:02 +00:00
type Changed Nova compute endpoint to new version 2019-10-10 22:12:05 +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 Update airskiff to focal 2023-05-04 05:45:02 +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.