opendev
/
infra-specs
Code Issues Proposed changes

Zuul v3: remove references to swift 

We have found that in the Zuul v3 architecture, as long as we have
the "secrets" functionality, we should be able to move the swift
functionality into Ansible roles, making for a simpler Zuul
application.

Change-Id: Ic1c37602ffb5a8e67cabb7afeac4127dd3a1b16c
This commit is contained in:
James E. Blair 2017-03-09 14:07:22 -08:00
parent e6e357f0f1
commit 40e26f1455
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
specs/zuulv3.rst
View File

@ -353,20 +353,20 @@ handled by the Jenkins (or other worker) definition::
nodes: precise
auth:
inherit: true # Child jobs may inherit these credentials
swift: # Swift usage may only be defined in config repo
- container: logs
secrets:
- logserver-credentials
workspace: /opt/workspace # Where to place git repositories
post-run:
- archive-logs
Jobs have inheritance, and the above definition provides a base level
of functionality for all jobs. It sets a default timeout, requests a
single node (of type precise), and requests swift credentials to
upload logs. For security, job credentials are not available to be
inherited unless the 'inherit' flag is set to true. For example, a
job to publish a release may need credentials to upload to a
distribution site -- users should not be able to subclass that job and
use its credentials for another purpose.
single node (of type precise), and requests credentials to upload
logs. For security, job credentials are not available to be inherited
unless the 'inherit' flag is set to true. For example, a job to
publish a release may need credentials to upload to a distribution
site -- users should not be able to subclass that job and use its
credentials for another purpose.
Further jobs may extend and override the remaining parameters::
@ -456,8 +456,8 @@ Secrets
~~~~~~~
The `auth` attribute of a job provides way to add authentication or
authorization requirements to a job. Examples above include `swift`
and `secrets`, though other systems may be added.
authorization requirements to a job. The example above includes only
`secrets`, though other systems may be added in the future.
A `secret` is a collection of key/value pairs and is defined as a
top-level configuration object::