Add devstack job to .zuul.conf
We know we want to have some level of functional testing to verify enforcement models. This commit uses one approach to add a base devstack job to oslo.limit's .zuul.conf so that we have a minimal-ish installation to configure with limits and write actual integration and functional tests against. Change-Id: I50c41805b8e196fdaf20c95e9aa687b98c369a57
This commit is contained in:
committed by
Stephen Finucane
parent
c02c025a66
commit
2632c8e1a9
32
.zuul.yaml
32
.zuul.yaml
@@ -1,3 +1,29 @@
|
||||
- job:
|
||||
name: oslo-limit-functional-devstack
|
||||
parent: devstack
|
||||
description:
|
||||
This job sets up a minimal devstack deployment, configures various usage
|
||||
and limit scenarios, and verifies usage enforcement based on existing
|
||||
usage.
|
||||
timeout: 9000
|
||||
vars:
|
||||
devstack_localrc:
|
||||
DATABASE_PASSWORD: secretdatabase
|
||||
ADMIN_PASSWORD: secretadmin
|
||||
LOGFILE: /opt/stack/logs/devstacklog.txt
|
||||
LOG_COLOR: false
|
||||
VERBOSE: true
|
||||
VERBOSE_NO_TIMESTAMP: true
|
||||
devstack_services:
|
||||
# Ignore all services by setting "disable_all_service". We do this
|
||||
# because we only really need keystone running to store unified limits.
|
||||
# These functional tests are not testing enforcement between keystone and
|
||||
# other services like nova and cinder. After this, we should only enable
|
||||
# exactly what we need to run keystone.
|
||||
base: false
|
||||
mysql: true
|
||||
key: true
|
||||
|
||||
- project:
|
||||
templates:
|
||||
- check-requirements
|
||||
@@ -9,3 +35,9 @@
|
||||
- periodic-stable-jobs
|
||||
- publish-openstack-docs-pti
|
||||
- release-notes-jobs-python3
|
||||
check:
|
||||
jobs:
|
||||
- oslo-limit-functional-devstack
|
||||
gate:
|
||||
jobs:
|
||||
- oslo-limit-functional-devstack
|
||||
|
||||
Reference in New Issue
Block a user