Browse Source

Fix: various documentation and URL fixes

1) UCP -> Airship
2) -> (there is redirect)
3) http -> https
4) attcomdev -> airshipit (repo on
5) att-comdev -> openstack/airship-* (repo on github/openstack git)
6) many URLs have been verified and adjusted to be current
7) no need for 'en/latest/' path in URL of the RTD
8) added more info to some setup.cfg and files
9) ucp-integration docs are now in airship-in-a-bottle
10) various other minor fixes

Change-Id: I64fb508a3ff72258d82c795193e918f2945deb29
Roman Gorshunov 3 years ago
7 changed files with 23 additions and 21 deletions
  1. +7
  2. +3
  3. +2
  4. +4
  5. +1
  6. +1
  7. +5

+ 7
- 7 View File

@ -3,7 +3,7 @@
A python REST orchestrator to translate a YAML host topology to a provisioned
set of hosts and provide a set of post-provisioning instructions.
See full documentation at [](
See full documentation at [](
## Required
@ -15,7 +15,7 @@ See full documentation at [](http://att
## Recommended
* A running Kubernetes cluster with Helm initialized
* Familiarity with the AT&T Community Undercloud Platform (UCP) suite of services
* Familiarity with the Airship platform suite of services
## Building
@ -44,14 +44,14 @@ and policy file templates to be customized
The preferred deployment pattern of Drydock is via a Helm chart
to deploy Drydock into a Kubernetes cluster. Additionally use of
the rest of the UCP services provides additional functionality
the rest of the Airship services provides additional functionality
for deploying (Armada) and using (Promenade, Deckhand) Drydock.
You can see an example of a full UCP deployment in the [UCP Integration]( repository.
You can see an example of a full Airship deployment in the [Airship in a Bottle]( repository.
### Stand up Kubernetes
Use the UCP [Promenade](
Use the Airship [Promenade](
tool for starting a self-hosted Kubernetes cluster with Kubernetes
Helm deployed.
@ -62,11 +62,11 @@ Use them for preparing your Kuberentes cluster to host Drydock.
* [Postgres](
* [Keystone](
* [MAAS](
* [MAAS](
### Deploy Drydock
Ideally you will use the UCP [Armada](
Ideally you will use the Airship [Armada](
tool for deploying the Drydock chart with proper overrides, but if not you can
use the `helm` CLI tool. The below are overrides needed during deployment

+ 3
- 3
charts/drydock/Chart.yaml View File

@ -18,8 +18,8 @@ name: drydock
version: 0.1.0
- drydock
- name: att-comdev
- name: airship

+ 2
- 2
docs/source/development.rst View File

@ -48,7 +48,7 @@ Control
The ``control`` module is simply the RESTful API. It is based on the
`Falcon Framework <>`_ and utilizes oslo_policy
for RBAC enforcement of the API endpoints. The normal deployment of Drydock
uses `uWSGI <>`_ and PasteDeploy
uses `uWSGI <>`_ and PasteDeploy
to build a pipeline that includes Keystone Middleware for authentication
and role decoration of the request.
@ -96,7 +96,7 @@ for testing and publishing. It also requires Drydock to produce multiple artifac
but separate: the Python package, the Docker image and the Helm chart. The code is published via the
Docker image artifact.
Drydock strives to conform to the `Airship coding conventions <>`_.
Drydock strives to conform to the `Airship coding conventions <>`_.

+ 4
- 4
docs/source/getting_started.rst View File

@ -23,7 +23,7 @@ Bootstrap Kubernetes
You can bootstrap your Helm-enabled Kubernetes cluster via the Openstack-Helm
`AIO <>`_
or the `Promenade <>`_ tools.
or the `Promenade <>`_ tools.
Deploy Drydock and Dependencies
@ -35,9 +35,9 @@ the deployments of the `MaaS <
chart and the `Keystone <>`_ chart.
A integrated deployment of these charts can be accomplished using the
`Armada <>`_ tool. An example integration
`Armada <>`_ tool. An example integration
chart can be found in the
`Airship in a Bottle <>`_ repo in the
`Airship in a Bottle <>`_ repo in the
``./manifests/dev_single_node`` directory.
Load Site
@ -49,7 +49,7 @@ YAML. An example of this is in ``./test/yaml_samples/deckhand_fullsite.yaml``.
Documentation on building your topology document is at :ref:`topology_label`.
Drydock requires that the YAML topology be hosted somewhere, either the preferred
method of using `Deckhand <>`_
method of using `Deckhand <>`_
or through a simple HTTP server like Nginx or Apache.
Use the CLI to create tasks to deploy your site

+ 1
- 1
docs/source/task.rst View File

@ -116,7 +116,7 @@ When querying the state of an existing task, the below document will be returned
"result": Status object
The Status object is based on the UCP standardized response format::
The Status object is based on the Airship standardized response format::
"Kind": "Status",

+ 1
- 1
python/drydock_provisioner/statemgmt/design/ View File

@ -109,7 +109,7 @@ class ReferenceResolver(object):
def resolve_reference_ucp(cls, design_uri):
"""Retrieve artifacts from a UCP service endpoint.
"""Retrieve artifacts from a Airship service endpoint.
Return a byte array of the response content. Assumes Keystone
authentication required.

+ 5
- 3
python/ View File

@ -21,9 +21,11 @@ from setuptools import setup, find_packages
description='Bootstrapper for Kubernetes infrastructure',
author='AT&T - AIC UCP Developers',
description=('A python REST orchestrator to translate a YAML host '
'topology to a provisioned set of hosts and provide a set of '
'post-provisioning instructions.'),
author='The Airship Authors',
license='Apache 2.0',