Document compatibility with Amazon EC2 and how to use boto library
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Document the compatibility of the nova-api endpoint with Amazon EC2. This includes:
- Which API calls are supported (partially documented right now at http://
- how compatible the metadata service is
- Any differences in the content of the data structures returned. (For example, I ran into the "architecture" field not being set and the name set to "None" when querying images using the EPI).
Should also document how to use boto to connect to the endpoint. For example (and I'm not even 100% sure this is correct:
import boto.ec2
region_name = "My internal cloud"
endpoint = "192.168.2.10" # Example endpoint IP
access_key = ... # Describe how to determine the access key
secret_key = ... # Describe how to determine the secret key
# These are the defaults, at least for Diablo
port = 8773
path = "/services/Cloud"
is_secure = False # endpoint does not use SSL by default
region = boto.ec2.
connection = boto.ec2.
Changed in openstack-manuals: | |
importance: | Undecided → Low |
status: | New → Confirmed |
tags: | added: ec2 nova |
Changed in openstack-manuals: | |
status: | Confirmed → Triaged |
Changed in openstack-manuals: | |
importance: | Low → Wishlist |
NeCTAR maintains some basic boto commands at:
http:// support. rc.nectar. org.au/ technical_ guides/ interfaces/ boto.html
http:// support. rc.nectar. org.au/ technical_ guides/ object_ storage. html
which can be copied and pasted for this.