openstack/barbican
Code Issues Proposed changes

Removed README.rst in favor of README.md

Browse Source 
Change-Id: Ib56956bcc4fda54dd7b3a418b70b8d2ac3e4fc09
Closes-Bug: 1251739
This commit is contained in:
Dolph Mathews 2013-11-15 13:30:58 -06:00
parent 0905323ccd
commit a287807c8e
2 changed files with 1 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
MANIFEST.in
View File

@ -1,5 +1,5 @@
include ChangeLog
include README.rst
include README.md
include MANIFEST.in pylintrc
include Authors
include HACKING.rst

48
README.rst
View File

@ -1,48 +0,0 @@
====
Barbican
====
TBD: Make this Barbican specific....test change for Jenkins
Glance is a project that defines services for discovering, registering,
retrieving and storing virtual machine images. The discovery and registration
responsibilities are handled by the `glance-registry` component while the
retrieval and storage responsiblities are handled by the `glance-api`
component.
Quick Start
-----------
If you'd like to run trunk, you can clone the git repo:
git clone git@github.com:openstack/glance.git
Install Glance by running::
python setup.py build
sudo python setup.py install
By default, `glance-registry` will use a SQLite database. If you'd like to use
MySQL, or make other adjustments, you can modify the glance.cnf file (see
documentation for more details).
Now that Glance is installed, you can start the service. The easiest way to
do that is by using the `glance-control` utility which runs both the
`glance-api` and `glance-registry` services::
glance-control all start
Once both services are running, you can now use the `glance` tool to
register new images in Glance.
glance add name="My Image" < /path/to/my/image
With an image registered, you can now configure your IAAS provider to use
Glance as its image service and begin spinning up instances from your
newly registered images.