Kevin Carter 975c232084 Updated the repo-build process

This commit changes the repo build play such that it no longer
requires "yaprt". The intention here is to make the build process
less of a blackbox, simpler, and faster. With recent improvements
in OpenStack and PIP we're now able to do a lot more without the
use of the "yaprt" tool. Repo building is now its own standalone
role.

This PR now reintroduces the repo-clone ability which is now made
smarter. The repo-build process creates a manifest file which is
used to provide the ability to sync exactly the contents of the
tagged release. This will make repeatable deployments faster for
downstream consumers.

The repo-store-source.yml play was removed because it hasn't been
used as the repo clone process is part of the main repo build
process.

DocImpact
UpgradeImpact
Change-Id: Icb0a4e3443491eb0242125ea59f8d5b50f89410b
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

2015-10-22 20:04:27 +00:00

3.0 KiB

Raw Blame History

OpenStack repo build

tags: openstack, repo, build, cloud, ansible
category: *nix

contributor guidelines

Filing Bugs

Bugs should be filed on Launchpad, not GitHub: "https://bugs.launchpad.net/openstack-ansible"

When submitting a bug, or working on a bug, please ensure the following criteria are met:

The description clearly states or describes the original problem or root cause of the problem.
Include historical information on how the problem was identified.
Any relevant logs are included.
The provided information should be totally self-contained. External access to web services/sites should not be needed.
Steps to reproduce the problem if possible.

Submitting Code

Changes to the project should be submitted for review via the Gerrit tool, following the workflow documented at: "http://docs.openstack.org/infra/manual/developers.html#development-workflow"

Pull requests submitted through GitHub will be ignored and closed without regard.

Extra

Tags:: If it's a bug that needs fixing in a branch in addition to Master, add a '<release>-backport-potential' tag (eg juno-backport-potential). There are predefined tags that will autocomplete.
Status:: Please leave this alone, it should be New till someone triages the issue.
Importance:: Should only be touched if it is a Blocker/Gating issue. If it is, please set to High, and only use Critical if you have found a bug that can take down whole infrastructures.

Style guide

When creating tasks and other roles for use in Ansible please create then using the YAML dictionary format.

Example YAML dictionary format:

- name: The name of the tasks
  module_name:
    thing1: "some-stuff"
    thing2: "some-other-stuff"
  tags:
    - some-tag
    - some-other-tag

Example NOT in YAML dictionary format:

- name: The name of the tasks
  module_name: thing1="some-stuff" thing2="some-other-stuff"
  tags:
    - some-tag
    - some-other-tag

Usage of the ">" and "|" operators should be limited to Ansible conditionals and command modules such as the ansible shell module.

Issues

When submitting an issue, or working on an issue please ensure the following criteria are met:

The description clearly states or describes the original problem or root cause of the problem.
Include historical information on how the problem was identified.
Any relevant logs are included.
If the issue is a bug that needs fixing in a branch other than Master, add the ‘backport potential’ tag TO THE ISSUE (not the PR).
The provided information should be totally self-contained. External access to web services/sites should not be needed.
If the issue is needed for a hotfix release, add the 'expedite' label.
Steps to reproduce the problem if possible.

3.0 KiB Raw Blame History Unescape Escape