airship/treasuremap
Code Issues Proposed changes
Reference Airship manifests, CICD, and reference architecture.
692 Commits 5 Branches 5 Tags 28 MiB
Shell 96.8%
Makefile 3.2%
fd9c28dfdf
Go to file
Matthew Fuller fd9c28dfdf Update README with branching changes 
Updates the main README file with a notice regarding upcoming
changes to the branching structure.

Relates-To: #50
Change-Id: Iedc1cdd7a7ac244385e92253c17b6ddc415117b2
2021-03-23 20:37:09 +00:00
.github Add SECURITY.md 2020-02-20 17:11:04 -06:00
doc Condensed Ceph Troubleshooting Section 2020-06-22 16:30:27 -05:00
global Disable CSI migration enabled in 1.17 by default 2020-12-21 16:24:05 -06:00
site Merge "Regenerate Seaworthy certificates" 2020-05-21 14:33:27 +00:00
tools Merge "Revert "Upgrade k8s from v1.17.3 to v1.18.6"" 2020-09-09 23:20:00 +00:00
type Changed Nova compute endpoint to new version 2019-10-10 22:12:05 +00:00
.gitignore Added FAQ section to documentation 2020-06-09 09:41:26 -05: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 Remove treasuremap from airship docs main page 2020-05-08 15:37:12 +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
test-requirements.txt Standardize Treasuremap code with YAPF 2019-07-24 17:58:10 +00:00
tox.ini Standardize Treasuremap code with YAPF 2019-07-24 17:58:10 +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.