2.9 KiB
Team and repository tags
ec2api
Table of Contents
- Overview - What is the ec2api module?
- Module Description - What does the module do?
- Setup - The basics of getting started with ec2api
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Beaker-Rspec - Beaker-rspec tests for the project
- Development - Guide for contributing to the module
- Contributors - Those with commits
Overview
The ec2api module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module its self is used to flexibly configure and manage the EC2 API service for OpenStack.
Module Description
The ec2api module is a thorough attempt to make Puppet capable of managing the entirety of ec2api. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the ec2api module to assist in manipulation of configuration files.
Setup
What the ec2api module affects
- Ec2api, the EC2 API service for OpenStack.
Installing ec2api
ec2api is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install ec2api with:
puppet module install openstack/ec2api
Beginning with ec2api
To utilize the ec2api module's functionality you will need to declare multiple resources.
Implementation
ec2api
ec2api is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
- All the ec2api types use the CLI tools and so need to be ran on the ec2api node.
Beaker-Rspec
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install
bundle exec rake acceptance
For more information on writing and running beaker-rspec tests visit the documentation:
Development
Developer documentation for the entire puppet-openstack project.