Move genesis from pod17-jump to pod17-node1 45/68445/2
authorKaspars Skels <kaspars.skels@att.com>
Wed, 4 Sep 2019 17:12:49 +0000 (12:12 -0500)
committerKaspars Skels <kaspars.skels@att.com>
Wed, 4 Sep 2019 18:45:29 +0000 (13:45 -0500)
commit18ca21eac0c569868250fdc9e652e41f76ae2fbd
tree09af5b178c07eba62ec4526a7389e43759017bca
parent8aee7b343082db8f65319e3358deb48528294bda
Move genesis from pod17-jump to pod17-node1

Adjust installation to comply with Pharos specification
http://artifacts.opnfv.org/pharos/colorado/docs/specification/index.html

The jump host is intended to serve as a node where installer runs.
This then is used as a worker node for Jenkins.

This patchset re-configures genesis to move to pod17-node1, and
reduces compute nodes from 3 to 2.

Change-Id: Ie5f65ad7cc0e6f688c913705babab6dc25925b4e
Signed-off-by: Kaspars Skels <kaspars.skels@att.com>
site/intel-pod17/baremetal/nodes.yaml
site/intel-pod17/networks/common-addresses.yaml
site/intel-pod17/pki/pki-catalog.yaml
site/intel-pod17/secrets/certificates/certificates.yaml
site/intel-pod17/software/charts/kubernetes/container-networking/etcd.yaml
site/intel-pod17/software/charts/kubernetes/etcd/etcd.yaml
tools/deploy.sh
type/cntt/software/charts/osh/openstack-tenant-ceph/ceph-client.yaml