Skip to content

Instantly share code, notes, and snippets.

View sw00's full-sized avatar

Sett sw00

View GitHub Profile
---
# ^^^ YAML documents must begin with the document separator "---"
#
#### Example docblock, I like to put a descriptive comment at the top of my
#### playbooks.
#
# Overview: Playbook to bootstrap a new host for configuration management.
# Applies to: production
# Description:
# Ensures that a host is configured for management with Ansible.
@sw00
sw00 / Gerrit Patches and Dependency
Last active April 9, 2017 20:35
Controlling Dependency in new Gerrit Patches
## Checking out unmerged patches
So you've decided to work on a new patch that depends on another that's still under review. There's no need to wait for it to be merged. Gerrit allows you to check out any patch easily
[Imgur](http://i.imgur.com/7xqC5JH.png)
On each patch's page, there's a text-box with the commands to *checkout*, *pull*, *cherry-pick* and *patch* each particular patchset. You want to work on top of an existing patch so go ahead and check it out.
## Housekeeping
@sw00
sw00 / CloudCAFE Instructions
Last active December 24, 2015 09:49
Getting started with CloudCAFE, a testing framework for Openstack
You will first need to clone three repositories from github:
1. OpenCAFE: this is core driver for writing and running tests. It contains a lot of base classes and the `cafe-runner` script used to collect and run cloudcafe tests.
`git clone https://github.com/stackforge/opencafe.git`
2. CloudCAFE: the framework built on top of OpenCAFE. This consists of the API used to write tests and offers easy objects to access Openstack services.
`git clone https://github.com/stackforge/cloudcafe.git`
3. CloudRoast: the repository where the tests for Openstack are implemented. These make use of CloudCAFE as a framework and abstracts enough detail so you can focus on writing tests instead of Openstack internals.
`git clone https://github.com/stackforage/cloudroast.git`