airship
/
airship-in-a-bottle
Code Issues Proposed changes
airship-in-a-bottle/manifests/basic_ucp
History
Anthony Lin 50d9bcd527 Update Overrides for armada.yaml.sub - Ingress 
There has been recent updates in OSH [0] that requires
updates to be made to 'armada.yaml.sub'

[0] b311f86193 (diff-b81b605c0ada77e93a9f62b6a1205190)

Change-Id: Ia3c4e06c0f954cd8a8fea25750e0f4fcd2dacf02
 		2018-02-22 10:36:08 +00:00
..
ArmadaManifest.yaml Removed rbac from ucp-integration 2018-01-22 09:23:54 -06:00
Docker.yaml Fixes for UCP deployment 2018-01-12 01:00:25 -05:00
Genesis.yaml.sub Update ucp-integration Repo 2018-01-17 14:54:54 +00:00
HostSystem.yaml.sub Fixes for CoreDNS update 2018-02-15 16:29:34 -06:00
Kubelet.yaml.sub Add Promenade Kubelet.yaml configuration 2017-11-27 13:32:08 -06:00
KubernetesNetwork.yaml.sub Update promenade config for PKICatalog + proxy 2018-02-13 15:08:41 -06:00
PKICatalog.yaml.sub Update promenade config for PKICatalog + proxy 2018-02-13 15:08:41 -06:00
armada-resources.yaml.sub Update selector on kube-system ingress 2018-02-20 09:21:08 -06:00
armada.yaml.sub Update Overrides for armada.yaml.sub - Ingress 2018-02-22 10:36:08 +00:00
deploy_ucp.sh Fix bug in Promenade chart 2018-02-20 09:21:08 -06:00
drydock.yaml.example Migrate to Promenade v2 2017-11-20 09:57:45 -06:00
drydock_deckhand.yaml fix small errors in prom bootaction location 2018-02-14 09:27:34 -06:00
get_token.sh Update Armada template for job cleanup 2017-12-15 10:59:11 -06:00
readme.md Deployment of base UCP control plane 2017-09-25 12:40:45 -05:00
set-env.sh Update ucp-integration Repo 2018-01-17 14:54:54 +00:00

readme.md

Artifacts to deploy a basic UCP control plane

The scripts and artifacts in this directory can be used to deploy a basic UCP control plane on a single node.

  1. Generate Promenade configuration and certificates
  2. Run Promenade genesis process to bootstrap Kubernetes
  3. Deploy Ceph using Armada
  4. Deploy UCP backend services (MariaDB, Postgres) using Armada
  5. Deploy Drydock and MaaS using Armada

Setup environment for your environment

This deployment process utilizes several environment variables to customize the deployment to your environment. The set-env.sh file has an example environment known to work.

  • CEPH_CLUSTER_NET

    The CIDR of the network(s) that Ceph will utilize for storage replication and other intra-cluster communication. Can be a comma-separated list of CIDRs.

  • CEPH_PUBLIC_NET

    The CIDR of the network(s) that Ceph will utilize for accepting requests for storage provisioning. Can be a comma-separated list of CIDRs.

  • CEPH_OSD_DIR

    The directory Ceph will use for OSD storage

  • GENESIS_NODE_IP

    The IP address of the genesis node or VM.

  • MASTER_NODE_IP

    The IP address of the second node to be added to the cluster. Scripting does not yet support deployment of this node, but it is REQUIRED to be included in the bootstrap configuration

  • DRYDOCK_NODE_IP

    The IP address of the node that will host the Drydock container. Defaults to the genesis node which is normally correct.

  • MAAS_NODE_IP

    The IP address of the node that will hsot the MaaS container. Defaults to the genesis node which is normally correct.

  • NODE_NET_IFACE

    The NIC interface on each node that Calico should use to access the underlay network. Defaults to 'eth0'

  • PROXY_ADDRESS

    If a HTTP/HTTPS proxy is needed for public access, specify the address here in URL format.

  • PROXY_ENABLED

    Whether to enable proxy use. Should be 'true' or 'false', defaults to 'false'.

  • GENESIS_NODE_NAME

    The hostname of the genesis node. REQUIRED to be accurate. Defaults to 'node1'

  • MASTER_NODE_NAME

    The hostname of the master (or second) node. REQUIRED to be accurate. Defaults to 'node2'

  • *_CHART_REPO

    The Git repository used for pulling charts. * can be any of 'CEPH', 'DRYDOCK' or 'MAAS'

  • *_CHART_BRANCH

    The Git branch used for pulling charts. * can be any of 'CEPH', 'DRYDOCK' or 'MAAS'

  • *_IMAGE

    The Docker image file used for deployments and running commands. * can be any of 'DRYDOCK', 'ARMADA', 'PROMENADE'.

Run the deployment

Once all of the above environmental variables are correct, run deploy_ucp.sh as root.