cd6c366cc6
Adds a new CI job, kayobe-seed-centos, that deploys a single VM as a seed host. The VM provided by Zuul is configured as the seed, rather than a seed hypervisor that provisions a seed VM using nested virt. This approach should be more reliable, faster, and easier to get working, at the expense of not testing the seed hypervisor code paths. Currently the seed services are deployed, but not tested. A future change could test discovery and provisioning of an overcloud host using the seed. Change-Id: Iefe16215af6f1a9fb8ec78094cd6bd76a82a040a Story: 2001655 Task: 6683
26 lines
840 B
Bash
26 lines
840 B
Bash
# Configuration for kayobe development environment.
|
|
|
|
# Path to the kayobe source code repository. Typically this will be the Vagrant
|
|
# shared directory.
|
|
#export KAYOBE_SOURCE_PATH=/vagrant
|
|
|
|
# Path to the kayobe-config repository checkout.
|
|
#export KAYOBE_CONFIG_SOURCE_PATH=${KAYOBE_SOURCE_PATH}/config/src/kayobe-config
|
|
|
|
# Path to the kayobe virtual environment.
|
|
#export KAYOBE_VENV_PATH=~/kayobe-venv
|
|
|
|
# Whether to provision a VM for the seed host.
|
|
#export KAYOBE_SEED_VM_PROVISION=1
|
|
|
|
# Whether to build container images for the seed services. If 0, they will be
|
|
# pulled.
|
|
#export KAYOBE_SEED_CONTAINER_IMAGE_BUILD=0
|
|
|
|
# Whether to build container images for the overcloud services. If 0, they will
|
|
# be pulled.
|
|
#export KAYOBE_OVERCLOUD_CONTAINER_IMAGE_BUILD=0
|
|
|
|
# Additional arguments to pass to kayobe commands.
|
|
#export KAYOBE_EXTRA_ARGS=
|