c1dd9435ee
Packstack has traditionally allowed multinode deployments with 1 controller, one or more network nodes and several compute nodes, but this has never been properly tested in our CI. This job enables an option to use a 2-node architecture, with one controller and one compute node. It adds a job running scenario002, but enables scenario001 and scenario003, so they can be used on demand if needed. Change-Id: Ide96a232c902370f3ec25ed54f2b272cc1757dad
96 lines
2.5 KiB
YAML
96 lines
2.5 KiB
YAML
- job:
|
|
name: packstack-base
|
|
parent: base
|
|
timeout: 7200
|
|
pre-run: playbooks/packstack-pre.yaml
|
|
post-run: playbooks/upload-logs.yaml
|
|
irrelevant-files:
|
|
- ^docs/.*$
|
|
- ^releasenotes/.*$
|
|
required-projects:
|
|
- openstack/packstack
|
|
- openstack/puppet-aodh
|
|
- openstack/puppet-ceilometer
|
|
- openstack/puppet-cinder
|
|
- openstack/puppet-glance
|
|
- openstack/puppet-gnocchi
|
|
- openstack/puppet-heat
|
|
- openstack/puppet-magnum
|
|
- openstack/puppet-horizon
|
|
- openstack/puppet-ironic
|
|
- openstack/puppet-keystone
|
|
- openstack/puppet-manila
|
|
- openstack/puppet-neutron
|
|
- openstack/puppet-nova
|
|
- openstack/puppet-openstack_extras
|
|
- openstack/puppet-openstacklib
|
|
- openstack/puppet-oslo
|
|
- openstack/puppet-ovn
|
|
- openstack/puppet-panko
|
|
- openstack/puppet-sahara
|
|
- openstack/puppet-swift
|
|
- openstack/puppet-tempest
|
|
- openstack/puppet-trove
|
|
- openstack/puppet-vswitch
|
|
|
|
- job:
|
|
name: packstack-allinone
|
|
parent: packstack-base
|
|
nodeset:
|
|
nodes:
|
|
- name: allinone
|
|
label: centos-7
|
|
run: playbooks/packstack-integration-tempest.yaml
|
|
|
|
- job:
|
|
name: packstack-multinode
|
|
parent: packstack-base
|
|
nodeset:
|
|
nodes:
|
|
- name: controller
|
|
label: centos-7
|
|
- name: compute
|
|
label: centos-7
|
|
run: playbooks/packstack-multinode.yaml
|
|
|
|
- job:
|
|
name: packstack-integration-scenario001-tempest
|
|
parent: packstack-allinone
|
|
vars:
|
|
scenario: scenario001
|
|
|
|
- job:
|
|
name: packstack-integration-scenario002-tempest
|
|
parent: packstack-allinone
|
|
vars:
|
|
scenario: scenario002
|
|
|
|
- job:
|
|
name: packstack-integration-scenario003-tempest
|
|
parent: packstack-allinone
|
|
vars:
|
|
scenario: scenario003
|
|
|
|
# We should have nested post-run jobs, according to
|
|
# https://docs.openstack.org/infra/zuul/user/config.html#job
|
|
- job:
|
|
name: packstack-multinode-scenario002-tempest
|
|
parent: packstack-multinode
|
|
post-run: playbooks/packstack-post-compute.yaml
|
|
vars:
|
|
scenario: scenario002
|
|
|
|
- project:
|
|
check:
|
|
jobs:
|
|
- packstack-integration-scenario001-tempest
|
|
- packstack-integration-scenario002-tempest
|
|
- packstack-integration-scenario003-tempest
|
|
- packstack-multinode-scenario002-tempest
|
|
gate:
|
|
jobs:
|
|
- packstack-integration-scenario001-tempest
|
|
- packstack-integration-scenario002-tempest
|
|
- packstack-integration-scenario003-tempest
|
|
- packstack-multinode-scenario002-tempest
|