No Description

Sebastien Badia 25ee79309e spec: Update travis configuration 2 years ago
examples 0e7a2e6c46 Initial commit (puppet module generate ganeti) 2 years ago
manifests a96b51ee1b init: Install basic packages (libs, tools, core) 2 years ago
spec a96b51ee1b init: Install basic packages (libs, tools, core) 2 years ago
.fixtures.yml 64dbe5066f spec: Configure the repository (spec, travis, fixtures) 2 years ago
.travis.yml 25ee79309e spec: Update travis configuration 2 years ago
CONTRIBUTING.md 64dbe5066f spec: Configure the repository (spec, travis, fixtures) 2 years ago
Gemfile 33e7c05266 spec: Update for rubocop 2 years ago
LICENSE 64dbe5066f spec: Configure the repository (spec, travis, fixtures) 2 years ago
README.md 0e7a2e6c46 Initial commit (puppet module generate ganeti) 2 years ago
Rakefile 33e7c05266 spec: Update for rubocop 2 years ago
metadata.json 64dbe5066f spec: Configure the repository (spec, travis, fixtures) 2 years ago

README.md

ganeti

Table of Contents

  1. Description
  2. Setup - The basics of getting started with ganeti
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Description

Start with a one- or two-sentence summary of what the module does and/or what problem it solves. This is your 30-second elevator pitch for your module. Consider including OS/Puppet version it works with.

You can give more descriptive information in a second paragraph. This paragraph should answer the questions: "What does this module do?" and "Why would I use it?" If your module has a range of functionality (installation, configuration, management, etc.), this is the time to mention it.

Setup

What ganeti affects OPTIONAL

If it's obvious what your module touches, you can skip this section. For example, folks can probably figure out that your mysql_instance module affects their MySQL instances.

If there's more that they should know about, though, this is the place to mention:

  • A list of files, packages, services, or operations that the module will alter, impact, or execute.
  • Dependencies that your module automatically installs.
  • Warnings or other important notices.

Setup Requirements OPTIONAL

If your module requires anything extra before setting up (pluginsync enabled, etc.), mention it here.

If your most recent release breaks compatibility or requires particular steps for upgrading, you might want to include an additional "Upgrading" section here.

Beginning with ganeti

The very basic steps needed for a user to get the module up and running. This can include setup steps, if necessary, or it can be an example of the most basic use of the module.

Usage

This section is where you describe how to customize, configure, and do the fancy stuff with your module here. It's especially helpful if you include usage examples and code samples for doing things with your module.

Reference

Here, include a complete list of your module's classes, types, providers, facts, along with the parameters for each. Users refer to this section (thus the name "Reference") to find specific details; most users don't read it per se.

Limitations

This is where you list OS compatibility, version compatibility, etc. If there are Known Issues, you might want to include them under their own heading here.

Development

Since your module is awesome, other users will want to play with it. Let them know what the ground rules for contributing are.

Release Notes/Contributors/Etc. Optional

If you aren't using changelog, put your release notes here (though you should consider using changelog). You can also add any additional sections you feel are necessary or important to include here. Please use the ## header.