Update links in the docs to refer to opendev

Sync of Airship project to Github has been stopped [0],
refer to opendev.org mirror instead of Github to
make sure the user is always referred to updated
repos.

[0] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005011.html

Change-Id: I31303af9176e90f13ef63bfea68ad3796710bae5
This commit is contained in:
Evgeny L 2019-04-22 18:29:47 +00:00 committed by Kaspars Skels
parent d0dc46ed0f
commit ffde6bcbd5
6 changed files with 25 additions and 25 deletions

View File

@ -289,14 +289,14 @@ client is configured for authentication:
.. _OpenStack-Helm project: https://docs.openstack.org/openstack-helm/latest/
install/developer/requirements-and-host-config.html
.. _Armada: https://github.com/openstack/airship-armada
.. _Deckhand: https://github.com/openstack/airship-deckhand
.. _Pegleg: https://github.com/openstack/airship-pegleg
.. _Shipyard: https://github.com/openstack/airship-shipyard
.. _Armada: https://opendev.org/airship/armada
.. _Deckhand: https://opendev.org/airship/deckhand
.. _Pegleg: https://opendev.org/airship/pegleg
.. _Shipyard: https://opendev.org/airship/shipyard
.. _Armada image: https://quay.io/repository/airshipit/armada?tab=tags
.. _airship-treasuremap: https://github.com/openstack/airship-treasuremap
.. _airship-treasuremap: https://opendev.org/airship/treasuremap
.. _Shipyard actions: https://airship-shipyard.readthedocs.io/en/latest/
action-commands.html

View File

@ -455,7 +455,7 @@ Clone the Promenade repo, if not already cloned:
::
git clone https://github.com/openstack/airship-promenade
git clone https://opendev.org/airship/promenade
Refer to the ``data/charts/ucp/promenade/reference`` field in
``airship-treasuremap/global/software/config/versions.yaml``. If
@ -694,7 +694,7 @@ Start by cloning the shipyard repository to the Genesis node:
::
git clone https://github.com/openstack/airship-shipyard
git clone https://opendev.org/airship/shipyard
Refer to the ``data/charts/ucp/shipyard/reference`` field in
``airship-treasuremap/global/software/config/versions.yaml``. If
@ -736,7 +736,7 @@ Ex:
export OS_PASSWORD=46a75e4...
(Note: Default auth variables are defined
`here <https://github.com/openstack/airship-shipyard/blob/master/tools/shipyard_docker_base_command.sh>`__,
`here <https://opendev.org/airship/shipyard/src/branch/master/tools/shipyard_docker_base_command.sh>`__,
and should otherwise be correct, barring any customizations of these
site parameters).

View File

@ -18,13 +18,13 @@ Component Projects
Pegleg
------
`Pegleg <https://github.com/openstack/airship-pegleg>`_ is a document aggregator
`Pegleg <https://opendev.org/airship/pegleg>`_ is a document aggregator
that provides early linting and validations via Deckhand, a document management
micro-service within Airship.
Shipyard
--------
`Shipyard <https://github.com/openstack/airship-shipyard>`_ is the directed acyclic
`Shipyard <https://opendev.org/airship/shipyard>`_ is the directed acyclic
graph controller for Kubernetes and OpenStack control plane life cycle
management.
@ -49,7 +49,7 @@ monitor and control the execution of the workflow.
Drydock
-------
`Drydock <https://github.com/openstack/airship-drydock>`_ is a provisioning orchestrator
`Drydock <https://opendev.org/airship/drydock>`_ is a provisioning orchestrator
for baremetal servers that translates a YAML-based declaritive site topology into a
physical undercloud that can be used for building out a enterprise Kubernetes cluster.
It uses plugins to leverage existing provisioning systems to build the servers allowing
@ -69,7 +69,7 @@ Capabilities
Deckhand
--------
`Deckhand <https://github.com/openstack/airship-deckhand>`_ is a document-based
`Deckhand <https://opendev.org/airship/deckhand>`_ is a document-based
configuration storage service built with auditability and validation in mind.
Core Responsibilities
@ -90,7 +90,7 @@ Core Responsibilities
Armada
------
`Armada <https://github.com/openstack/airship-armada>`_ is a tool for managing multiple
`Armada <https://opendev.org/airship/armada>`_ is a tool for managing multiple
Helm charts with dependencies by centralizing all configurations in a single
Armada YAML and providing life-cycle hooks for all Helm releases.
@ -110,7 +110,7 @@ basic mechanisms for deployment, maintenance, and scaling of applications.
Promenade
---------
`Promenade <https://github.com/openstack/airship-promenade>`_ is a tool for
`Promenade <https://opendev.org/airship/promenade>`_ is a tool for
bootstrapping a resilient, self-hosted Kubernetes cluster and managing its
life-cycle.
@ -161,7 +161,7 @@ OpenStack applications into a cloud-native model.
Divingbell
----------
`Divingbell <https://github.com/openstack/airship-divingbell>`_ is a lightweight
`Divingbell <https://opendev.org/airship/divingbell>`_ is a lightweight
solution for:
1. Bare metal configuration management for a few very targeted use cases
@ -177,7 +177,7 @@ The needs identified for Divingbell were:
Berth
-----
`Berth <https://github.com/openstack/airship-berth>`_ is a deliberately minimalist VM
`Berth <https://opendev.org/airship/berth>`_ is a deliberately minimalist VM
runner for Kubernetes.
@ -201,6 +201,6 @@ Process Flows
.. _Kubernetes Homepage: https://kubernetes.io/
.. _Openstack: https://www.openstack.org/
.. _Openstack Helm: https://github.com/openstack/openstack-helm
.. _Treasuremap: https://github.com/openstack/airship-treasuremap
.. _Treasuremap: https://opendev.org/airship/treasuremap
.. _yaml: http://yaml.org/

View File

@ -5,7 +5,7 @@ Airship Seaworthy is a multi-node site deployment reference
and continuous integration pipeline.
The site manifests are available at
`site/airship-seaworthy <https://github.com/openstack/airship-treasuremap/tree/master/site/airship-seaworthy>`__.
`site/airship-seaworthy <https://opendev.org/airship/treasuremap/src/branch/master/site/airship-seaworthy>`__.
Pipeline
@ -15,15 +15,15 @@ Airship Seaworthy pipeline automates deployment flow documented in
`Site Authoring and Deployment Guide <https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html>`__.
The pipeline is implemented as Jenkins Pipeline (Groovy), see code for the pipeline at
`Jenkinsfile <https://github.com/openstack/airship-treasuremap/blob/master/tools/gate/Jenkinsfile>`__.
`Jenkinsfile <https://opendev.org/airship/treasuremap/src/branch/master/tools/gate/Jenkinsfile>`__.
Versions
--------
The manifest overrides (`versions.yaml <https://github.com/openstack/airship-treasuremap/blob/master/global/software/config/versions.yaml>`__)
The manifest overrides (`versions.yaml <https://opendev.org/airship/treasuremap/src/branch/master/global/software/config/versions.yaml>`__)
are setup to deploy OpenStack Ocata.
The versions are kept up to date via `updater.py <https://github.com/openstack/airship-treasuremap/blob/master/tools/updater.py>`__,
The versions are kept up to date via `updater.py <https://opendev.org/airship/treasuremap/src/branch/master/tools/updater.py>`__,
a utility that updates versions.yaml latest charts and (selected) images.
The pipeline attempts to uplift and deploy latest versions on daily bases.
@ -40,7 +40,7 @@ to align parts of the system such as Ceph replication, etcd, etc.
Airship Seaworthy site has 6 DELL R720xd bare-metal servers:
3 control, and 3 compute nodes.
See host profiles for the servers `here <https://github.com/openstack/airship-treasuremap/tree/master/site/airship-seaworthy/profiles/host>`__.
See host profiles for the servers `here <https://opendev.org/airship/treasuremap/src/branch/master/site/airship-seaworthy/profiles/host>`__.
Control (masters)
- cab23-r720-11
@ -57,7 +57,7 @@ Network
-------
Physical (underlay) networks are described in Drydock site configuration
`here <https://github.com/openstack/airship-treasuremap/blob/master/site/airship-seaworthy/networks/physical/networks.yaml>`__.
`here <https://opendev.org/airship/treasuremap/src/branch/master/site/airship-seaworthy/networks/physical/networks.yaml>`__.
It defines OOB (iLO/IPMI), untagged PXE, and multiple tagged general use networks.
Calico overlay for k8s POD networking uses IPIP mesh.

View File

@ -3,7 +3,7 @@
# parameters. This should not require modification for a new site. However,
# shipyard deployment strategies can be very useful in getting around certain
# failures, like misbehaving nodes that hold up the deployment. See more at
# https://github.com/openstack/airship-shipyard/blob/master/docs/source/site-definition-documents.rst#using-a-deployment-strategy
# https://opendev.org/airship/shipyard/src/branch/master/doc/source/site-definition-documents.rst#using-a-deployment-strategy
schema: shipyard/DeploymentConfiguration/v1
metadata:
schema: metadata/Document/v1

View File

@ -3,7 +3,7 @@
# parameters. This should not require modification for a new site. However,
# shipyard deployment strategies can be very useful in getting around certain
# failures, like misbehaving nodes that hold up the deployment. See more at
# https://github.com/openstack/airship-shipyard/blob/master/docs/source/site-definition-documents.rst#using-a-deployment-strategy
# https://opendev.org/airship/shipyard/src/branch/master/doc/source/site-definition-documents.rst#using-a-deployment-strategy
schema: shipyard/DeploymentConfiguration/v1
metadata:
schema: metadata/Document/v1