- Uplift the Drydock and MAAS charts
- New charts/HTK require Helm 2.14.1, so uplift tiller
and Armada to support this.
Change-Id: Ie63cff29a979f60f10c97b5b0cb08ed908ed85d4
Sets the apiserver command for use during genesis to refect the service
cidr and service node port range to match Treasuremap conventions (and
fix a failing genesis process)
Change-Id: Id1745d7734901e071e0889fe2a3dc00982156d44
Keystone and Shipyard globally defined host_fqdn_override that utilizes
a DNS server set up for multinode gates. This change moves these to be
overridden/merged in at the site layer instead, allowing the global to
be usable for the single-node Airship-in-a-bottle demo.
Change-Id: I83c9a8f1cdda7017882ca0253ce07d48fb684e16
- The MAAS and Drydock charts are moving to use ingress
rather than node ports. Update versions and chart overrides
to support this.
Change-Id: I9a630f1edad9129719748b848a693e012baf9b37
Ingress requires external DNS or host header
forging. For a better gate test, run a external
DNS resolver for Ingress entries.
Change-Id: I6558230b7fa9f3145c472eb437177d90b7b52835
In response to keystone update and various version updates to airship
components. This change updates across many components ultimately.
Change-Id: I3a794dd37c290f9a272379539f4f56ec80509a6d
The dev-proxy site failed due to a specification of deployment-strategy
in the deployment configuration. Removing this declaration allows
Shipyard to use a default strategy.
Change-Id: I10e6a9e1391f068cc8261a4e6145eeced10df9a8
- Create a site definition to support a full site deployment
workflow using VMs
Multi-Nodes Gate
Enable multi-node gate for Airship using core Airship
components.
Deployment will be driven by Shipyard.
We will re-use and adapt the source codes from the Promenade
g2 Gate [1].
[1] https://github.com/openstack/airship-promenade/tree/master/tools/g2
Change-Id: I41e79f5f26311fa179a2e5c121aa815caa05cfcd
Changes the versions of Deckhand and Shipyard for the
airship-in-a-bottle manifests to newer versions to account for pod
labels. As a result, this also brings along several Shipyard schemas
and yaml files.
Change-Id: I9b8470c45856698725c9aa5a6f63639debfce6eb
Separates and cleans up some documentation around the
airship-in-a-bottle usage for demo vs. development
environment purposes. Dev environments will deploy only the
Airship specific components, while the Demo will show a
more complete installation of OpenStack on top of Airship.
Change-Id: Icca614c4cc4aed426006720b924c105b15d9e510
- Use the NFS storage provisioner instead of Ceph
- Update versions file to include chart and image info for NFS
provisioner
Change-Id: Ieb4360fd941bd1e11e03fe7ee5b9d1bb343c53f8
Using the promenade build, and pegleg-arranged file layout,
provide a single-node/genesis only site deign.
This patchset will focus on the files only, while others
will focus on the scripts and tools using these.
Change-Id: Ie163e4fe2ac45ebfe50b703516bde20765a6b248