Welcome to CloudBridge’s documentation!¶
CloudBridge aims to provide a simple layer of abstraction over different cloud providers, reducing or eliminating the need to write conditional code for each cloud.
Usage example¶
The simplest possible example for doing something useful with CloudBridge would look like the following.
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
provider = CloudProviderFactory().create_provider(ProviderList.AWS, {})
print(provider.compute.instances.list())
In the example above, the AWS_ACCESS_KEY and AWS_SECRET_KEY environment variables must be set to your cloud credentials.
Quick Reference¶
The following object graph shows how to access various provider services, and the resource that they return. Click on any object to drill down into its details.
Installation¶
The latest release can always be installed form PyPI. For other installation options, see the installation page:
pip install cloudbridge
Documentation¶
Concepts and Organisation¶
Object types¶
Conceptually, CloudBridge consists of the following types of objects.
1. Providers - Represents a connection to a cloud provider, and is the gateway to using its services.
2. Services - Represents a service provided by a cloud provider, such as its compute service, storage service, networking service etc. Services may in turn be divided into smaller services. Smaller services tend to have uniform methods, such as create, find and list. For example, InstanceService.list(), InstanceService.find() etc. which can be used to access cloud resources. Larger services tend to provide organisational structure only. For example, the storage service provides access to the VolumeService, SnapshotService and BucketService.
3. Resources - resources are objects returned by a service, and represent a remote resource. For example, InstanceService.list() will return a list of Instance objects, which can be used to manipulate an instance. Similarly, VolumeService.create() will return a Volume object.
The actual source code structure of CloudBridge also mirrors this organisation.
Object identification and naming¶
In order to function uniformly across across cloud providers, object identity and naming must be conceptually consistent. In CloudBridge, there are three main properties for identifying and naming an object.
1.Id - The id corresponds to a unique identifier that can be reliably used to reference a resource. All CloudBridge resources have an id. Most methods in CloudBridge services, such as get, use the id property to identify and retrieve objects.
2. Name - The name property is a more human-readable identifier for a particular resource, and is often useful to display to the end user instead of the id. While it is often unique, it is not guaranteed to be so, and therefore, the id property must always be used for uniquely identifying objects. All CloudBridge resources have a name property. The name property is often assigned during resource creation, and is often derived from the label property by appending some unique characters to it. Once assigned however, it is unchangeable.
3. Label - Most resources also support a label property, which is a user changeable value that can be used to describe an object. When creating resources, cloudbridge often accepts a label property as a parameter. The name property is derived from the label, by appending some unique characters to it. However, there are some resources which do not support a label property, such as key pairs and buckets. In the latter case, the name can be specified during resource creation, but cannot be changed thereafter.
Detailed class relationships¶
The following diagram shows a typical provider object graph and the relationship between services.
Some services are nested. For example, to access the instance service, you can use provider.compute.instances. Similarly, to get a list of all instances, you can use the following code.
instances = provider.compute.instances.list()
print(instances[0].name)
Getting Started¶
This getting started guide will provide a quick tour of some CloudBridge features. For more details on individual features, see the Using CloudBridge section or the API reference.
Installation¶
CloudBridge is available on PyPI so to install the latest available version, run:
pip install --upgrade cloudbridge
For common issues during setup, check the following section: Common Setup Issues <topics/troubleshooting.html>
Create a provider¶
To start, you will need to create a reference to a provider object. The provider object identifies the cloud you want to work with and supplies your credentials. The following two code snippets setup a necessary provider object, for AWS and OpenStack. For the details on other providers, take a look at the Setup page. The remainder of the code is the same for either provider.
AWS:
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
config = {'aws_access_key': 'AKIAJW2XCYO4AF55XFEQ',
'aws_secret_key': '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'}
provider = CloudProviderFactory().create_provider(ProviderList.AWS, config)
image_id = 'ami-aa2ea6d0' # Ubuntu 16.04 (HVM)
OpenStack (with Keystone authentication v2):
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
config = {'os_username': 'username',
'os_password': 'password',
'os_auth_url': 'authentication URL',
'os_region_name': 'region name',
'os_project_name': 'project name'}
provider = CloudProviderFactory().create_provider(ProviderList.OPENSTACK,
config)
image_id = 'c1f4b7bc-a563-4feb-b439-a2e071d861aa' # Ubuntu 14.04 @ NeCTAR
OpenStack (with Keystone authentication v3):
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
config = {'os_username': 'username',
'os_password': 'password',
'os_auth_url': 'authentication URL',
'os_project_name': 'project name',
'os_project_domain_name': 'project domain name',
'os_user_domain_name': 'domain name'}
provider = CloudProviderFactory().create_provider(ProviderList.OPENSTACK,
config)
image_id = 'acb53109-941f-4593-9bf8-4a53cb9e0739' # Ubuntu 16.04 @ Jetstream
Azure:
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
config = {'azure_subscription_id': 'REPLACE WITH ACTUAL VALUE',
'azure_client_id': 'REPLACE WITH ACTUAL VALUE',
'azure_secret': 'REPLACE WITH ACTUAL VALUE',
'azure_tenant': ' REPLACE WITH ACTUAL VALUE'}
provider = CloudProviderFactory().create_provider(ProviderList.AZURE, config)
image_id = 'Canonical:UbuntuServer:16.04.0-LTS:latest' # Ubuntu 16.04
List some resources¶
Once you have a reference to a provider, explore the cloud platform:
provider.security.firewalls.list()
provider.compute.vm_types.list()
provider.storage.snapshots.list()
provider.storage.buckets.list()
This will demonstrate the fact that the library was properly installed and your provider object is setup correctly but it is not very interesting. Therefore, let’s create a new instance we can ssh into using a key pair.
Create a key pair¶
We’ll create a new key pair and save the private portion of the key to a file on disk as a read-only file.
import os
kp = provider.security.key_pairs.create('cloudbridge_intro')
with open('cloudbridge_intro.pem', 'w') as f:
f.write(kp.material)
os.chmod('cloudbridge_intro.pem', 0o400)
Create a network¶
A cloudbridge instance should be launched into a private subnet. We’ll create a private network and subnet, and make sure it has internet connectivity, by attaching an internet gateway to the subnet via a router.
net = provider.networking.networks.create(cidr_block='10.0.0.0/16',
label='my-network')
sn = net.create_subnet(cidr_block='10.0.0.0/28', label='my-subnet')
router = provider.networking.routers.create(network=net, label='my-router')
router.attach_subnet(sn)
gateway = net.gateways.get_or_create_inet_gateway()
router.attach_gateway(gateway)
Create a VM firewall¶
Next, we need to create a VM firewall (also commonly known as a security group) and add a rule to allow ssh access. A VM firewall needs to be associated with a private network.
from cloudbridge.cloud.interfaces.resources import TrafficDirection
fw = provider.security.vm_firewalls.create(
label='cloudbridge-intro', description='A VM firewall used by
CloudBridge', network=net.id)
fw.rules.create(TrafficDirection.INBOUND, 'tcp', 22, 22, '0.0.0.0/0')
Launch an instance¶
We can now launch an instance using the created key pair and security group. We will launch an instance type that has at least 2 CPUs and 4GB RAM. We will also add the network interface as a launch argument.
img = provider.compute.images.get(image_id)
vm_type = sorted([t for t in provider.compute.vm_types
if t.vcpus >= 2 and t.ram >= 4],
key=lambda x: x.vcpus*x.ram)[0]
inst = provider.compute.instances.create(
image=img, vm_type=vm_type, label='cloudbridge-intro',
subnet=sn, key_pair=kp, vm_firewalls=[fw])
# Wait until ready
inst.wait_till_ready() # This is a blocking call
# Show instance state
inst.state
# 'running'
Note
Note that we iterated through provider.compute.vm_types directly instead of calling provider.compute.vm_types.list(). This is because we need to iterate through all records in this case. The list() method may not always return all records, depending on the global limit for records, necessitating that additional records be paged in. See Paging and iteration.
Assign a public IP address¶
To access the instance, let’s assign a public IP address to the instance. For this step, we’ll first need to allocate a floating IP address for our account and then associate it with the instance. Note that floating IPs are associated with an Internet Gateway so we allocate the IP under the gateway we dealt with earlier.
fip = gateway.floating_ips.create()
inst.add_floating_ip(fip)
inst.refresh()
inst.public_ips
# [u'54.166.125.219']
From the command prompt, you can now ssh into the instance
ssh -i cloudbridge_intro.pem ubuntu@54.166.125.219
.
Get a resource¶
When a resource already exists, a reference to it can be retrieved using either its ID, name, or label. It is important to note that while IDs and names are unique, multiple resources of the same type could use the same label, thus the find method always returns a list, while the get method returns a single object. While the methods are similar across resources, they are explicitly listed in order to help map each resource with the service that handles it.
# Key Pair
kp = provider.security.key_pairs.get('keypair ID')
kp_list = provider.security.key_pairs.find(name='cloudbridge_intro')
kp = kp_list[0]
# Network
net = provider.networking.networks.get('network ID')
net_list = provider.networking.networks.find(name='my-network')
net_list = provider.networking.networks.find(label='my-network')
net = net_list[0]
# Subnet
sn = provider.networking.subnets.get('subnet ID')
# Unknown network
sn_list = provider.networking.subnets.find(name='my-subnet')
sn_list = provider.networking.subnets.find(label='my-subnet')
# Known network
sn_list = provider.networking.subnets.find(network=net.id, name='my-subnet')
sn_list = provider.networking.subnets.find(network=net.id,
label='my-subnet')
sn = sn_list(0)
# Router
router = provider.networking.routers.get('router ID')
router_list = provider.networking.routers.find(name='my-router')
router_list = provider.networking.routers.find(label='my-router')
router = router_list[0]
# Gateway
gateway = net.gateways.get_or_create_inet_gateway()
# Floating IPs
fip = gateway.floating_ips.get('FloatingIP ID')
# Find using public IP address
fip_list = gateway.floating_ips.find(public_ip='IP address')
# Find using name or tag
fip_list = net.gateways.floating_ips.find(name='my-fip')
fip_list = net.gateways.floating_ips.find(label='my-fip')
fip = fip_list[0]
# Firewall
fw = provider.security.vm_firewalls.get('firewall ID')
fw_list = provider.security.vm_firewalls.find(name='cloudbridge-intro')
fw_list = provider.security.vm_firewalls.find(label='cloudbridge-intro')
fw = fw_list[0]
# Instance
inst = provider.compute.instances.get('instance ID')
inst_list = provider.compute.instances.list(name='cloudbridge-intro')
inst_list = provider.compute.instances.list(label='cloudbridge-intro')
inst = inst_list[0]
Cleanup¶
To wrap things up, let’s clean up all the resources we have created
from cloudbridge.cloud.interfaces import InstanceState
inst.delete()
inst.wait_for([InstanceState.DELETED, InstanceState.UNKNOWN],
terminal_states=[InstanceState.ERROR]) # Blocking call
fip.delete()
fw.delete()
kp.delete()
os.remove('cloudbridge_intro.pem')
router.detach_gateway(gateway)
router.detach_subnet(sn)
gateway.delete()
router.delete()
sn.delete()
net.delete()
And that’s it - a full circle in a few lines of code. You can now try the same with a different provider. All you will need to change is the cloud-specific data, namely the provider setup and the image ID.
Using CloudBridge¶
Introductions to all the key parts of CloudBridge you’ll need to know:
Installation¶
Prerequisites: CloudBridge runs on Python 2.7 and higher. Python 3 is recommended.
We highly recommend installing CloudBridge in a virtualenv. Creating a new virtualenv is simple:
pip install virtualenv
virtualenv .venv
source .venv/bin/activate
Latest stable release¶
The latest release of CloudBridge can be installed from PyPI:
pip install cloudbridge
Latest unreleased dev version¶
The development version of the library can be installed directly from the GitHub repo:
$ pip install --upgrade git+https://github.com/CloudVE/cloudbridge.git
Developer installation¶
To install additional libraries required by CloudBridge contributors, such as tox, clone the source code repository and run the following command from the repository root directory:
$ git clone https://github.com/CloudVE/cloudbridge.git
$ cd cloudbridge
$ pip install --upgrade --editable .[dev]
Checking installation¶
To check what version of the library you have installed, do the following:
import cloudbridge
cloudbridge.get_version()
Setup¶
To initialize a connection to a cloud and get a provider object, you will need to provide the cloud’s access credentials to CloudBridge. These may be provided in one of following ways:
- Environment variables
- A dictionary
- Configuration file
Procuring access credentials¶
For Azure, Create service principle credentials from the following link : https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal#check-azure-subscription-permissions
Providing access credentials through environment variables¶
The following environment variables must be set, depending on the provider in use.
Amazon
Mandatory variables | Optional Variables |
---|---|
AWS_ACCESS_KEY | |
AWS_SECRET_KEY |
Openstack
Mandatory variables | Optional Variables |
---|---|
OS_AUTH_URL | NOVA_SERVICE_NAME |
OS_USERNAME | OS_COMPUTE_API_VERSION |
OS_PASSWORD | OS_VOLUME_API_VERSION |
OS_PROJECT_NAME | OS_STORAGE_URL |
OS_REGION_NAME | OS_AUTH_TOKEN |
Azure
Note that managing resources in Azure requires a Resource Group. If a Resource Group is not provided as part of the configuration, cloudbridge will attempt to create a Resource Group using the given credentials. This operation will happen with the client initialization, and requires a “contributor” or “owner” role. Similarly, a Storage Account is required when managing some resources, such as KeyPairs and Buckets. If a Storage Account name is not provided as part of the configuration, cloudbridge will attempt to create the Storage Account when initializing the relevant services. This operation similarly requires a “contributor” or “owner” role. For more information on roles, see: https://docs.microsoft.com/en-us/azure/role-based-access-control/overview
Mandatory variables | Optional Variables |
---|---|
AZURE_SUBSCRIPTION_ID | AZURE_REGION_NAME |
AZURE_CLIENT_ID | AZURE_RESOURCE_GROUP |
AZURE_SECRET | AZURE_STORAGE_ACCOUNT |
AZURE_TENANT | AZURE_VM_DEFAULT_USER_NAME AZURE_PUBLIC_KEY_STORAGE_TABLE_NAME |
Once the environment variables are set, you can create a connection as follows:
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
provider = CloudProviderFactory().create_provider(ProviderList.OPENSTACK, {})
Providing access credentials through a dictionary¶
You can initialize a simple config as follows. The key names are the same as the environment variables, in lower case. Note that the config dictionary will override environment values.
from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
config = {'aws_access_key' : '<your_access_key>',
'aws_secret_key' : '<your_secret_key>'}
provider = CloudProviderFactory().create_provider(ProviderList.AWS, config)
## For Azure
config = {'azure_subscription_id': '<your_subscription_id>',
'azure_client_id': '<your_client_id>',
'azure_secret': '<your_secret>',
'azure_tenant': '<your_tenant>',
'azure_resource_group': '<your resource group>'}
provider = CloudProviderFactory().create_provider(ProviderList.AZURE, config)
Some optional configuration values can only be provided through the config dictionary. These are listed below for each provider.
CloudBridge
Variable | Description |
---|---|
default_result_limit | Number of results that a .list() method should return.
Defaults to 50. |
Amazon
Variable | Description |
---|---|
aws_session_token | Session key for your AWS account (if using temporary credentials). |
ec2_is_secure | True to use an SSL connection. Default is True . |
ec2_region_name | Default region name. Defaults to us-east-1 . |
ec2_region_endpoint | Endpoint to use. Default is ec2.us-east-1.amazonaws.com . |
ec2_port | EC2 connection port. Does not need to be specified unless EC2 service is running on an alternative port. |
ec2_conn_path | Connection path. Defaults to / . |
ec2_validate_certs | Whether to use SSL certificate verification. Default is
False . |
s3_is_secure | True to use an SSL connection. Default is True . |
s3_host | Host connection endpoint. Default is s3.amazonaws.com . |
s3_port | Host connection port. Does not need to be specified unless S3 service is running on an alternative port. |
s3_conn_path | Connection path. Defaults to / . |
s3_validate_certs | Whether to use SSL certificate verification. Default is
False . |
Providing access credentials in a file¶
CloudBridge can also read credentials from a file on your local file system.
The file should be placed in one of two locations: /etc/cloudbridge.ini
or
~/.cloudbridge
. Each set of credentials should be delineated with the
provider ID (e.g., openstack
, aws
, azure
) with the necessary credentials
being supplied in YAML format. Note that only one set of credentials per
cloud provider type can be supplied (i.e., via this method, it is not possible
to provide credentials for two different OpenStack clouds).
[openstack]
os_username: username
os_password: password
os_auth_url: auth url
os_user_domain_name: user domain name
os_project_domain_name: project domain name
os_project_name: project name
[aws]
aws_access_key: access key
aws_secret_key: secret key
Other configuration variables¶
In addition to the provider specific configuration variables above, there are some general configuration environment variables that apply to CloudBridge as a whole
Variable | Description |
---|---|
CB_DEBUG | Setting CB_DEBUG=True will cause detailed debug
output to be printed for each provider (including HTTP
traces). |
CB_USE_MOCK_PROVIDERS | Setting this to True will cause the CloudBridge
test suite to use mock drivers when available. |
CB_TEST_PROVIDER | Set this value to a valid ProviderList value
such as aws , to limit tests to that provider only. |
CB_DEFAULT_SUBNET_LABEL | Name to be used for a subnet that will be considered the ‘default’ by the library. This default will be used only in cases there is no subnet marked as the default by the provider. |
CB_DEFAULT_NETWORK_LABEL | Name to be used for a network that will be considered the ‘default’ by the library. This default will be used only in cases there is no network marked as the default by the provider. |
Launching instances¶
Before being able to run below commands, you will need a provider
object
(see this page).
Common launch data¶
Before launching an instance, you need to decide what image to launch as well as what type of instance. We will create those objects here. The specified image ID is a base Ubuntu image on AWS so feel free to change it as desired. For instance type, we’re going to let CloudBridge figure out what’s the appropriate name on a given provider for an instance with at least 2 CPUs and 4 GB RAM.
img = provider.compute.images.get('ami-759bc50a') # Ubuntu 16.04 on AWS
vm_type = sorted([t for t in provider.compute.vm_types
if t.vcpus >= 2 and t.ram >= 4],
key=lambda x: x.vcpus*x.ram)[0]
In addition, CloudBridge instances must be launched into a private subnet. While it is possible to create complex network configurations as shown in the Private networking section, if you don’t particularly care in which subnet the instance is launched, CloudBridge provides a convenience function to quickly obtain a default subnet for use. We just need to supply a zone to use.
zone = provider.compute.regions.get(provider.region_name).zones[0]
subnet = provider.networking.subnets.get_or_create_default(zone)
When launching an instance, you can also specify several optional arguments such as the firewall (aka security group), a key pair, or instance user data. To allow you to connect to the launched instances, we will also supply those parameters (note that we’re making an assumption here these resources exist; if you don’t have those resources under your account, take a look at the Getting Started guide).
kp = provider.security.key_pairs.find(name='cloudbridge_intro')[0]
fw = provider.security.vm_firewalls.list()[0]
Launch an instance¶
Once we have all the desired pieces, we’ll use them to launch an instance:
inst = provider.compute.instances.create(
name='cloudbridge-vpc', image=img, vm_type=vm_type,
subnet=subnet, key_pair=kp, vm_firewalls=[fw])
Private networking¶
Private networking gives you control over the networking setup for your instance(s) and is considered the preferred method for launching instances. To launch an instance with an explicit private network, you can create a custom network and make sure it has internet connectivity. You can then launch into that subnet.
net = self.provider.networking.networks.create(
name='my-network', cidr_block='10.0.0.0/16')
sn = net.create_subnet(name='my-subnet', cidr_block='10.0.0.0/28')
# make sure subnet has internet access
router = self.provider.networking.routers.create(network=net, name='my-router')
router.attach_subnet(sn)
gateway = net.gateways.get_or_create_inet_gateway()
router.attach_gateway(gateway)
inst = provider.compute.instances.create(
name='cloudbridge-vpc', image=img, vm_type=vm_type,
subnet=sn, key_pair=kp, vm_firewalls=[fw])
For more information on how to create and setup a private network, take a look at Networking.
Block device mapping¶
Optionally, you may want to provide a block device mapping at launch, specifying volume or ephemeral storage mappings for the instance. While volumes can also be attached and mapped after instance boot using the volume service, specifying block device mappings at launch time is especially useful when it is necessary to resize the root volume.
The code below demonstrates how to resize the root volume. For more information,
refer to LaunchConfig
.
lc = provider.compute.instances.create_launch_config()
lc.add_volume_device(source=img, size=11, is_root=True)
inst = provider.compute.instances.create(
name='cloudbridge-bdm', image=img, vm_type=vm_type,
launch_config=lc, key_pair=kp, vm_firewalls=[fw])
where img
is the Image
object to use for the root volume.
After launch¶
After an instance has launched, you can access its properties:
# Wait until ready
inst.wait_till_ready() # This is a blocking call
inst.state
# 'running'
Depending on the provider’s networking setup, it may be necessary to explicitly assign a floating IP address to your instance. This can be done as follows:
# Create a new floating IP address
fip = provider.networking.floating_ips.create()
# Assign the desired IP to the instance
inst.add_floating_ip(fip)
inst.refresh()
inst.public_ips
# [u'149.165.168.143']
Private networking¶
Private networking gives you control over the networking setup for your instance(s) and is considered the preferred method for launching instances. Also, providers these days are increasingly requiring use of private networks. All CloudBridge deployed VMs must be deployed into a particular subnet.
If you do not explicitly specify a private network to use when launching an
instance, CloudBridge will attempt to use a default one. A ‘default’ network is
one tagged as such by the native API. If such tag or functionality does not
exist, CloudBridge will look for one with a predefined name (by default, called
‘CloudBridgeNet’, which can be overridden with environment variable
CB_DEFAULT_NETWORK_NAME
).
Once a VM is deployed, cloudbridge’s networking capabilities must address several common scenarios.
Allowing internet access from a launched VM
In the simplest scenario, a user may simply want to launch an instance and allow the instance to access the internet.
Allowing internet access to a launched VM
Alternatively, the user may want to allow the instance to be contactable from the internet. In a more complex scenario, a user may want to deploy VMS into several subnets, and deploy a gateway, jump host or bastion host to access other VMs which are not directly connected to the internet. In the latter scenario, the gateway/jump host/bastion host will need to be contactable over the internet.
Secure access between subnets for n-tier applications
In this third scenario, a multi-tier app may be deployed into several subnets depending on their tier. For example, consider the following scenario:
- Tier 1/Subnet 1 - Web Server Needs to be externally accessible over the internet. However, in this particular scenario, the web server itself does not need access to the internet.
- Tier 2/Subnet 2 - Application Server The Application server must only be able to communicate with the database server in Subnet 3, and receive communication from the Web Server in Subnet 1. However, we assume a special case here where the application server needs to access the internet.
- Tier 3/Subnet 3 - Database Server The database server must only be able to receive incoming traffic from Tier 2, but must not be able to make outgoing traffic outside of its subnet.
At present, CloudBridge does not provide support for this scenario, primarily because OpenStack’s FwaaS (Firewall-as-a-Service) is not widely available.
1. Allowing internet access from a launched VM¶
Creating a private network is a simple, one-line command but appropriately connecting it so that it has uniform Internet access across all providers is a multi-step process: (1) create a network; (2) create a subnet within this network; (3) create a router; (4) attach the router to the subnet and (5) attach the router to the internet gateway.
When creating a network, we need to set an address pool. Any subsequent
subnets you create must have a CIDR block that falls within the parent
network’s CIDR block. Below, we’ll create a subnet starting from the beginning
of the block and allow up to 16 IP addresses within a subnet (/28
).
net = provider.networking.networks.create(
name='my-network', cidr_block='10.0.0.0/16')
sn = net.create_subnet(name='my-subnet', cidr_block='10.0.0.0/28', zone=zone)
router = provider.networking.routers.create(network=net, name='my-router')
router.attach_subnet(sn)
gateway = net.gateways.get_or_create_inet_gateway()
router.attach_gateway(gateway)
2. Allowing internet access to a launched VM¶
The additional step that’s required here is to assign a floating IP to the VM:
net = provider.networking.networks.create(
name='my-network', cidr_block='10.0.0.0/16')
sn = net.create_subnet(name='my-subnet', cidr_block='10.0.0.0/28', zone=zone)
vm = provider.compute.instances.create('my-inst', subnet=sn, ...)
router = provider.networking.routers.create(network=net, name='my-router')
router.attach_subnet(sn)
gateway = net.gateways.get_or_create_inet_gateway()
router.attach_gateway(gateway)
fip = provider.networking.floating_ips.create()
vm.add_floating_ip(fip)
Retrieve an existing private network¶
If you already have existing networks, we can query for it:
provider.networking.networks.list() # Find a desired network ID
net = provider.networking.networks.get('desired network ID')
Object states and lifecycles¶
Overview¶
Some objects, namely, Instances, Volumes, Snapshots and Images, have a specific life-cycle and a set of states they can be in. For example, an Instance may be in state RUNNING and a volume maybe in state AVAILABLE. These provider specific states are mapped to a common vocabulary of states in CloudBridge.
In addition, it is common to want to wait for objects to reach a particular
state. For example, wait for an instance to transition from PENDING->RUNNING.
To facilitate this, all such objects in CloudBridge implement the
ObjectLifeCycleMixin
. Each object with a lifecycle has a state
property, a refresh method and a wait_for method.
The state property will return the object’s current state, and the refresh() method can be used to requery the server and update the object’s state. The wait_for method can be used to wait for the object to transition to a desired state or set of states.
There is also a convenience method named wait_till_ready(), which will wait for the object to reach a ready-to-use state. A ready-to-use state would mean that the object has been successfully created and can be interacted with, and is not in an error state. Since this can be tedious to get right, the wait_till_ready() method encapsulates this behaviour. For example - in the case of an Instance, wait_till_ready() will internally call the wait_for method as follows:
self.wait_for(
[InstanceState.RUNNING],
terminal_states=[InstanceState.DELETED, InstanceState.ERROR],
timeout=timeout,
interval=interval)
This would cause the wait_for method to repeatedly call refresh() till the
object’s state reaches RUNNING. It will raise a WaitStateException
if the timeout expires, or the object reaches a terminal state, such as
DELETED or ERROR, in which case it is no longer reasonable to wait for the
object to reach a running state.
Informational states and actionable states¶
As in the wait_for example above, some states are purely informational, and some states are actionable. Informational states are meant to provide information to the end-user, and should generally not be used by program logic to take actions. For example, it would be incorrect to write a wait_for function as follows:
wait_for([InstanceState.PENDING], ...)
This is because the PENDING state is fleeting and may occur too fast to be reliably detected by the client. In contrast, a state such as RUNNING is more stable and program logic can reasonably take actions based on such states. In the discussion that follows, we will specifically differentiate between informational and actionable states.
Instance states and lifecycle¶
The following states are defined for a CloudBridge Instance.
State | Category | Description |
---|---|---|
UNKNOWN | actionable | Instance state is unknown. This means that the instance does not exist or CloudBridge does not know how to map this state. |
PENDING | informational | Instance is pending |
CONFIGURING | informational | Instance is being reconfigured in some way and may not be usable. |
RUNNING | actionable | Instance is running. |
REBOOTING | informational | Instance is rebooting. |
DELETED | actionable | Instance is deleted. No further operations possible. |
STOPPED | actionable | Instance is stopped. Instance can be resumed. |
ERROR | actionable | Instance is in an error state. No further operations possible. |
The lifecycle diagram is as follows:
Actionable states are shown in blue and informational states in cyan. Note that any state could potentially transition into an ERROR state. An Instance may initially be in an UNKNOWN state and transition into a PENDING state on launch. Similarly, it may transition into an UNKNOWN state after TERMINATION and the object no longer exists. More rarely, an instance may transition into an UNKNOWN state if CloudBridge does not know how to map the state reported by the cloud provider. Therefore, when writing a wait_for method, these potential transitions should be taken into account.
Volume states and lifecycle¶
The following states are defined for a CloudBridge Volume.
State | Category | Description |
---|---|---|
UNKNOWN | actionable | Volume state is unknown. This means that the volume does not exist or CloudBridge does not know how to map this state. |
CREATING | informational | Volume is pending |
CONFIGURING | informational | Volume is being reconfigured in some way and may not be usable. |
AVAILABLE | actionable | Volume is unattached and available for use. |
IN_USE | informational | Volume is attached to an instance and in-use. |
DELETED | actionable | Volume has been deleted. No further operations possible. |
ERROR | actionable | Volume is in an error state. No further operations possible. |
The lifecycle diagram is as follows:
Actionable states are shown in blue and informational states in cyan. Note that any state could potentially transition into an ERROR state. A Volume may initially be in an UNKNOWN state and transition into a CREATING state when created anew. Similarly, it may transition into an UNKNOWN state after DELETED and the object no longer exists. More rarely, a volume may transition into an UNKNOWN state if CloudBridge does not know how to map the state reported by the cloud provider. A Volume will typically transition through a CONFIGURING stage before going to an IN_USE stage and vice versa.
Snapshot states and lifecycle¶
The following states are defined for a CloudBridge Snapshot.
State | Category | Description |
---|---|---|
UNKNOWN | actionable | Snapshot state is unknown. This means that the snapshot does not exist or CloudBridge does not know how to map this state. |
PENDING | informational | Snapshot is pending |
CONFIGURING | informational | Snapshot is being reconfigured in some way and may not be usable. |
AVAILABLE | actionable | Snapshot is ready. |
ERROR | actionable | Snapshot is in an error state. No further operations possible. |
The lifecycle diagram is as follows:
Actionable states are shown in blue and informational states in cyan. Note that any state could potentially transition into an ERROR state. A Snapshot may initially be in an UNKNOWN state and transition into a PENDING state when created anew. Similarly, it may transition into an UNKNOWN state after deleted and the object no longer exists. More rarely, a snapshot may transition into an UNKNOWN state if CloudBridge does not know how to map the state reported by the cloud provider.
Image states and lifecycle¶
The following states are defined for a CloudBridge Image.
State | Category | Description |
---|---|---|
UNKNOWN | actionable | Image state is unknown. This means that the Image does not exist or CloudBridge does not know how to map this state. |
PENDING | informational | Image is pending |
AVAILABLE | actionable | Image is ready. |
ERROR | actionable | Image is in an error state. No further operations possible. |
The lifecycle diagram is as follows:
Actionable states are shown in blue and informational states in cyan. Note that any state could potentially transition into an ERROR state. An Image may initially be in an UNKNOWN state and transition into a PENDING state when created anew. Similarly, it may transition into an UNKNOWN state after deleted and the image no longer exists. More rarely, an Image may transition into an UNKNOWN state if CloudBridge does not know how to map the state reported by the cloud provider.
Paging and iteration¶
Overview¶
Most provider services have list() methods, and all list methods accept a limit parameter which specifies the maximum number of results to return. If a limit is not specified, CloudBridge will default to the global configuration variable default_result_limit, which can be modified through the provider config.
Since the returned result list may have more records available, CloudBridge
will always return a ResultList
object to assist with paging through
additional results. A ResultList extends the standard list
and
the following example illustrates how to fetch additional records.
Example:
# get first page of results
rl = provider.compute.instances.list(limit=50)
for result in rl:
print("Instance Data: {0}", result)
if rl.supports_total:
print("Total results: {0}".format(rl.total_results))
else:
print("Total records unknown,"
"but has more data?: {0}."format(rl.is_truncated))
# Page to next set of results
if (rl.is_truncated)
rl = provider.compute.instances.list(limit=100,
marker=rl.marker)
To ease development, CloudBridge also provides standard Python iterators that will page the results in for you automatically. Therefore, when you need to iterate through all available objects, the following shorthand is recommended:
Example:
# Iterate through all results
for instance in provider.compute.instances:
print("Instance Data: {0}", instance)
Working with block storage¶
To add persistent storage to your cloud environments, you would use block storage devices, namely volumes and volume snapshots. A volume is attached to an instance and mounted as a file system for use by an application. A volume snapshot is a point-in-time snapshot of a volume that can be shared with other cloud users. Before a snapshot can be used, it is necessary to create a volume from it.
Volume storage¶
Operations, such as creating a new volume and listing the existing ones, are
performed via the VolumeService
. To start, let’s create a 1GB volume.
vol = provider.storage.volumes.create('cloudbridge-vol', 1, 'us-east-1e')
vol.wait_till_ready()
provider.storage.volumes.list()
Next, let’s attach the volume to a running instance as device /dev/sdh
:
vol.attach(‘i-dbf37022’, ‘/dev/sdh’) vol.refresh() vol.state # ‘in-use’
Once attached, from within the instance, it is necessary to create a file system on the new volume and mount it.
Once you wish to detach a volume from an instance, it is necessary to unmount the file system from within the instance and detach it. The volume can then be attached to a different instance with all the data on it preserved.
vol.detach()
vol.refresh()
vol.state
# 'available'
Snapshot storage¶
A volume snapshot it created from an existing volume. Note that it may take a long time for a snapshot to become ready, particularly on AWS.
snap = vol.create_snapshot('cloudbridge-snap',
'A demo snapshot created via CloudBridge.')
snap.wait_till_ready()
snap.state
# 'available'
In order to make use of a snapshot, it is necessary to create a volume from it:
vol = provider.storage.volumes.create(
'cloudbridge-snap-vol', 1, 'us-east-1e', snapshot=snap)
The newly created volume behaves just like any other volume and can be attached to an instance for use.
Working with object storage¶
Object storage provides a simple way to store and retrieve large amounts of unstructured data over HTTP. Object Storage is also referred to as Blob (Binary Large OBject) Storage by Azure, and Simple Storage Service (S3) by Amazon.
Typically, you would store your objects within a Bucket, as it is known in AWS and GCE. A Bucket is also called a Container in OpenStack and Azure. In CloudBridge, we use the term Bucket.
Storing objects in a bucket¶
To store an object within a bucket, we need to first create a bucket or retrieve an existing bucket.
bucket = provider.storage.buckets.create('my-bucket')
bucket.objects.list()
Next, let’s upload some data to this bucket. To efficiently upload a file, simple use the upload_from_file method.
obj = bucket.objects.create('my-data.txt')
obj.upload_from_file('/path/to/myfile.txt')
You can also use the upload() function to upload from an in memory stream. Note that, an object you create with objects.create() doesn’t actually get persisted until you upload some content.
To locate and download this uploaded file again, you can do the following:
bucket = provider.storage.buckets.find(name='my-bucket')[0]
obj = bucket.objects.find(name='my-data.txt')[0]
print("Size: {0}, Modified: {1}".format(obj.size, obj.last_modified))
with open('/tmp/myfile.txt', 'wb') as f:
obj.save_content(f)
Using tokens for authentication¶
Some providers may support using temporary credentials with a session token, in which case you will be able to access a particular bucket by using that session token.
provider = CloudProviderFactory().create_provider(
ProviderList.AWS,
{'aws_access_key': 'ACCESS_KEY',
'aws_secret_key': 'SECRET_KEY',
'aws_session_token': 'MY_SESSION_TOKEN'})
provider = CloudProviderFactory().create_provider(
ProviderList.OPENSTACK,
{'os_storage_url': 'SWIFT_STORAGE_URL',
'os_auth_token': 'MY_SESSION_TOKEN'})
Once a provider is obtained, you can access the container as usual:
bucket = provider.storage.buckets.get(container)
obj = bucket.create_object('my_object.txt')
obj.upload_from_file(source)
Common Setup Issues¶
macOS Issues¶
If you are getting an error message like so:
Authentication with cloud provider failed: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
then this indicates that you are probably using a newer version of Python on macOS. Starting with Python 3.6, the Python installer includes its own version of OpenSSL and it no longer uses the system trusted certificate keychains.Python 3.6 includes a script that can install a bundle of root certificates from
certifi
. To install this bundle execute the following:cd /Applications/Python\ 3.6/ sudo ./Install\ Certificates.command
For more information see this StackOverflow answer and the Python 3.6 Release Notes.
Contributor Guide¶
This section has information on how to contribute to CloudBridge development, and a walkthrough of the process of getting started on developing a new CloudBridge Provider.
Design Goals¶
- Create a cloud abstraction layer which minimises or eliminates the need for
cloud specific special casing (i.e., Not require clients to write
if EC2 do x else if OPENSTACK do y
.) - Have a suite of conformance tests which are comprehensive enough that goal 1 can be achieved. This would also mean that clients need not manually test against each provider to make sure their application is compatible.
- Opt for a minimum set of features that a cloud provider will support, instead of a lowest common denominator approach. This means that reasonably mature clouds like Amazon and OpenStack are used as the benchmark against which functionality & features are determined. Therefore, there is a definite expectation that the cloud infrastructure will support a compute service with support for images and snapshots and various machine sizes. The cloud infrastructure will very likely support block storage, although this is currently optional. It may optionally support object storage.
- Make the CloudBridge layer as thin as possible without compromising goal 1. By wrapping the cloud provider’s native SDK and doing the minimal work necessary to adapt the interface, we can achieve greater development speed and reliability since the native provider SDK is most likely to have both properties.
Design decisions¶
This document captures outcomes and, in some cases, the through process behind some of the design decisions that took place while architecting CloudBridge. It is intended as a reference.
Require zone parameter when creating a default subnet.
Placement zone is required because it is an explicit application decision, even though ideally default would not require input. Before requiring it, the implementations would create a subnet in each availability zone and return the first one in the list. This could potentially return different values over time. Another factor influencing the decision was the example of creating a volume followed by creating an instance with presumably the two needing to be in the same zone. By requiring the zone across the board, it is less likely to lead to a miss match. (Related to 63.)
Resource identification, naming and labeling
While it would be reasonable to expect that complex constructs like networking would be the most difficult to abstract away uniformly across providers, in retrospect, simple naming of objects has arguably been the most complex and convoluted to map consistently. CloudBridge has been through several iterations of naming and labeling, before finally settling on the current design. This section captures that history and design rationale.
*First iteration* In the early days, when CloudBridge supported only AWS and OpenStack, there were only two concepts, id and name. The id was straightforward enough, as it usually mapped to a unique identifier, auto-generated by the provider. The name generally mapped to a tag in the case of AWS, and a name field in the case of OpenStack. However, even then, there were inconsistencies within individual providers. For example, while AWS generally supported tags, it had a dedicated name field for machine images called ami-name. Furthermore, this name field could only be set at image creation time, and could not be changed thereafter. Similarly, AWS does not allow VM firewall (i.e., security group) names to be changed. Nevertheless, CloudBridge continued to use id and name, with the name being changeable for some resources, and read-only in others.
As CloudBridge evolved and support was added for Azure and GCE, things only became more complex. Some providers (e.g. Azure and GCE) used a user-provided value instead of an auto-generated value as an id, which would also be displayed in their respective dashboards as Name. This meant that they were treating their servers as individually named pets, instead of adopting the cattle model, should one be tempted to use that macabre pets vs cattle analogy. These user provided names could not be changed after a resource had been created. Instead, these providers seemed to be gravitating toward the use of tags (or labels) to support arbitrary naming and name changes. Yet, not all resources support tags so CloudBridge could not rely solely on tags. Further, tags do not need to be unique across multiple resources, while names do (at least for some resources, such as vmfirewalls within a private network). Overall, consistency was challenging to achieve with resource naming. Therefore, it was decided that CloudBridge would continue to support resource renaming to the best extent possible and balance between the use of the resource name property and resource tags. However, because of the inconsistency in rename functionality across providers, using the rename capabilities within CloudBridge would lead to cloud-dependent code (Related to 131.) and therefore, the only option was to continue to stick a caveat emptor to resource renaming.
*Second iteration* However, it soon became apparent that this overloaded terminology was continuing to cause confusion. The id property in cloudbridge mapped to the unchangeable name property in Azure and GCE, and the name property in cloudbridge sometimes mapped to a tag in certain providers, and a name in other providers and they were sometimes read-only, sometimes writable. In an attempt to disambiguate these concepts, it was then decided that perhaps three concepts were needed - id, display_id and label. The id would continue to refer to a unique identifier for a resource and be mapped accordingly to the underlying provider. The display_id would be a more user-friendly version of an id, suitable for display to an end-user and be unchangeable, but on rare occasions, not unique. For example, ami-name was a display_id while the ami-id was an id. Similarly, an Azure resource name mapped to the display_id, since it was an unchangeable, user-friendly identifier. Finally, label was a changeable, user-assignable value that would be mapped often to a tag on the resource, or the name of the resource, should the name be changeable. This clearly disambiguated between unique identifiers, user-assignable values and read-only, user-friendly values. At object creation, all services would accept a label as an optional parameter. If provided, the display_id would sometimes be derived from the label by appending a uuid to the label, depending on the provider. At other times, it would simply map to an id.
*Third iteration* It soon became apparent that some resources like keypairs could not have a label at all, yet needed to be named during object creation. However, we could not use display_id for this purpose became the display_id, by definition, is unchangeable. It could not be called label because the label, in contrast, was changeable. Therefore, it seemed like we were back to calling it name instead, introducing yet a fourth term. To simplify this, it was then decided that display_id and name would be collapsed together into one term and be called name instead. All resources would have an id and a name, and resources that support it would have a label. To make things even simpler and consistent, it was also decided that label would be made mandatory for all resources during object creation, and follow the same restrictions as name, which is to have a 3 character minimum. (this was to deal with an exception in OpenStack, where the label mapped to instance name, but could not be empty. Therefore, by making all labels mandatory and adhere to minimum length restrictions, we could make the overall conventions uniform across all resources and therefore easier to remember and enforce)
*TL;DR* CloudBridge has three concepts when it comes to naming and identifying objects. The id is a unique identifier for an object, always auto-generated. The name is a read-only, user-friendly value which is suitable for display to the end-user. The label is a user-assignable value that can be changed. The name is often derived from the label but not always. Not all resources support labels. Some only accept names which can be specified at object creation time (e.g. keypairs). Both names and labels adhere to the same restrictions - a minimum length of 3 which should be alphanumeric characters or dashes only. Names or labels should not begin or end with a dash, or have consecutive dashes.
Running tests¶
In the spirit of the library’s Design Goals, the aim is to have thorough tests for the entire library. This page explains the testing philosophy and shows how to run the tests locally.
Testing philosophy¶
Our testing goals are to:
- Write one set of tests that all provider implementations must pass.
- Make that set of tests a ‘conformance’ test suite, which validates that each implementation correctly implements the CloudBridge specification.
- Make the test suite comprehensive enough that a provider which passes all the tests can be used safely by an application with no additional testing. In other words, the CloudBridge specification and accompanying test suite must be comprehensive enough that no provider specific workarounds, code or testing is required.
- For development, mock providers may be used to speed up the feedback cycle, but providers must also pass the full suite of tests when run against actual cloud infrastructure to ensure that we are not testing against an idealised or imagined environment.
- Aim for 100% code coverage.
Running tests¶
- To run the test suite locally:
- Install tox with
pip install tox
- Export all environment variables listed in
tox.ini
(underpassenv
) - Run
tox
command
- Install tox with
This will run all the tests for all the environments defined in file
tox.ini
.
Specific environment and infrastructure¶
If you’d like to run the tests on a specific environment only, say Python 2.7,
against a specific infrastructure, say aws, use a command like this:
tox -e py27-aws
. The available provider names are listed in the
ProviderList class (e.g., aws
or openstack
).
Specific test cases¶
You can run a specific test case, as follows:
tox -- test/test_image_service.py:CloudImageServiceTestCase.test_create_and_list_imag
It can also be restricted to a particular environment as follows:
tox -e "py27-aws" -- test/test_cloud_factory.py:CloudFactoryTestCase
See nosetest documentation for other parameters that can be passed in.
Using unittest directly¶
You can also run the tests against your active virtual environment directly
with python setup.py test
. You will need to set the CB_TEST_PROVIDER
and CB_USE_MOCK_PROVIDERS
environment variables prior to running the tests,
or they will default to CB_TEST_PROVIDER=aws
and
CB_USE_MOCK_PROVIDERS=True
.
You can also run a specific test case, as follows:
python setup.py test -s test.test_cloud_factory.CloudFactoryTestCase
Using a mock provider¶
Note that running the tests may create various cloud resources, for which you
may incur costs. For the AWS cloud, there is also a mock provider (moto) that
will simulate AWS resources. It is used by default when running the test suite.
You can toggle the use of mock providers by setting an environment variable:
CB_USE_MOCK_PROVIDERS
to Yes
or No
.
Provider Development Walkthrough¶
This guide will walk you through the basic process of developing a new provider for CloudBridge.
1. We start off by creating a new folder for the provider within the
cloudbridge/cloud/providers
folder. In this case: gce
. Further, install
the native cloud provider Python library, here
pip install google-api-python-client==1.4.2
and a couple of its requirements
oauth2client==1.5.2
and pycrypto==2.6.1
.
2. Add a provider.py
file. This file will contain the main implementation
of the cloud provider and will be the entry point that CloudBridge uses for all
provider related services. You will need to subclass BaseCloudProvider
and
add a class variable named PROVIDER_ID
.
from cloudbridge.cloud.base import BaseCloudProvider
class GCECloudProvider(BaseCloudProvider):
PROVIDER_ID = 'gce'
def __init__(self, config):
super(GCECloudProvider, self).__init__(config)
3. Add an __init__.py
to the cloudbridge/cloud/providers/gce
folder
and export the provider.
from .provider import GCECloudProvider # noqa
Tip
You can view the code so far here: commit 1
4. Next, we need to register the provider with the factory.
This only requires that you register the provider’s ID in the ProviderList
.
Add GCE to the ProviderList
class in cloudbridge/cloud/factory.py
.
- Run the test suite. We will get the tests passing on py27 first.
export CB_TEST_PROVIDER=gce
tox -e py27
You should see the tests fail with the following message:
TypeError: Can't instantiate abstract class GCECloudProvider with abstract
methods storage, compute, security, network
6. Therefore, our next step is to implement these methods. We can start off by
implementing these methods in provider.py
and raising a
NotImplementedError
.
@property
def compute(self):
raise NotImplementedError(
"GCECloudProvider does not implement this service")
@property
def network(self):
raise NotImplementedError(
"GCECloudProvider does not implement this service")
@property
def security(self):
raise NotImplementedError(
"GCECloudProvider does not implement this service")
@property
def storage(self):
raise NotImplementedError(
"GCECloudProvider does not implement this service")
Running the tests now will complain as much. We will next implement each Service in turn.
- We will start with the compute service. Add a
services.py
file.
from cloudbridge.cloud.base.services import BaseSecurityService
class GCESecurityService(BaseSecurityService):
def __init__(self, provider):
super(GCESecurityService, self).__init__(provider)
8. We can now return this new service from the security property in
provider.py
as follows:
def __init__(self, config):
super(GCECloudProvider, self).__init__(config)
self._security = GCESecurityService(self)
@property
def security(self):
return self._security
Tip
You can view the code so far here: commit 2
9. Run the tests, and the following message will cause all security service tests to fail:
TypeError: Can't instantiate abstract class GCESecurityService with abstract
methods key_pairs, security_groups
The Abstract Base Classes are doing their job and flagging all methods that need to be implemented.
10. Since the security service simply provides organisational structure, and is
a container for the key_pairs
and security_groups
services, we must
next implement these services.
from cloudbridge.cloud.base.services import BaseKeyPairService
from cloudbridge.cloud.base.services import BaseSecurityGroupService
from cloudbridge.cloud.base.services import BaseSecurityService
class GCESecurityService(BaseSecurityService):
def __init__(self, provider):
super(GCESecurityService, self).__init__(provider)
# Initialize provider services
self._key_pairs = GCEKeyPairService(provider)
self._security_groups = GCESecurityGroupService(provider)
@property
def key_pairs(self):
return self._key_pairs
@property
def security_groups(self):
return self._security_groups
class GCEKeyPairService(BaseKeyPairService):
def __init__(self, provider):
super(GCEKeyPairService, self).__init__(provider)
class GCESecurityGroupService(BaseSecurityGroupService):
def __init__(self, provider):
super(GCESecurityGroupService, self).__init__(provider)
Tip
You can view the code so far here: commit 3
Once again, running the tests will complain of missing methods:
TypeError: Can't instantiate abstract class GCEKeyPairService with abstract
methods create, find, get, list
11. Keep implementing the methods till the security service works, and the tests pass.
Note
We start off by implementing the list keypairs method. Therefore, to obtain the keypair, we need to have a connection to the cloud provider. For this, we need to install the Google sdk, and thereafter, to obtain the desired connection via the sdk. While the design and structure of that connection is up to the implementor, a general design we have followed is to have the cloud connection globally available within the provider.
To add the sdk, we edit CloudBridge’s main setup.py
and list the
dependencies.
gce_reqs = ['google-api-python-client==1.4.2']
full_reqs = base_reqs + aws_reqs + openstack_reqs + gce_reqs
We will also register the provider in cloudbridge/cloud/factory.py
’s
provider list.
class ProviderList(object):
AWS = 'aws'
OPENSTACK = 'openstack'
...
GCE = 'gce'
Tip
You can view the code so far here: commit 4
12. Thereafter, we create the actual connection through the sdk. In the case of
GCE, we need a Compute API client object. We will make this connection
available as a public property named gce_compute
in the provider. We will
then lazily initialize this connection.
A full implementation of the KeyPair service can now be made in a provider specific manner.
Tip
You can view the code so far here: commit 5
Release Process¶
- Increment version number in
cloudbridge/__init__.py
as per `semver rules <https://semver.org/>_. - Freeze all library dependencies in
setup.py
. The version numbers can be a range with the upper limit being the latest known working version, and the lowest being the last known working version. - Run all
tox
tests. - Add release notes to
CHANGELOG.rst
. Also add last commit hash to changelog. List of commits can be obtained usinggit shortlog <last release hash>..HEAD
- Release to PyPi
python setup.py sdist upload
python setup.py bdist_wheel upload
- Tag release and make GitHub release.
API reference¶
This section includes the API documentation for the reference interface.
Providers¶
CloudProvider¶
-
class
cloudbridge.cloud.interfaces.provider.
CloudProvider
(config)[source]¶ Base interface for a cloud provider
-
__init__
(config)[source]¶ Create a new provider instance given a dictionary of configuration attributes.
Parameters: config ( dict
) – A dictionary object containing provider initialization values. Alternatively, this can be a Bunch or any other object whose fields can be accessed as members. See specific provider implementation for the required fields.Return type: CloudProvider
Returns: a concrete provider instance
-
authenticate
()[source]¶ Checks whether a provider can be successfully authenticated with the configured settings. Clients are not required to call this method prior to accessing provider services, as most cloud connections are initialized lazily. The authenticate() method will return True if cloudbridge can establish a successful connection to the provider. It will raise an exception with the appropriate error details otherwise.
Example:
try: if provider.authenticate(): print("Provider connection successful") except ProviderConnectionException as e: print("Could not authenticate with provider: %s" % (e, ))
Return type: bool
Returns: True
if authentication is successful.
-
compute
¶ Provides access to all compute related services in this provider.
Example:
regions = provider.compute.regions.list() vm_types = provider.compute.vm_types.list() instances = provider.compute.instances.list() images = provider.compute.images.list() # Alternatively for instance in provider.compute.instances: print(instance.name)
Return type: ComputeService
Returns: a ComputeService object
-
config
¶ Returns the config object associated with this provider. This object is a subclass of
dict
and will contain the properties provided at initialization time, grouped under cloud_properties and credentials keys. In addition, it also contains extra provider-wide properties such as the default result limit for list() queries.Example:
config = { 'aws_access_key' : '<my_key>' } provider = factory.create_provider(ProviderList.AWS, config) print(provider.config['credentials'].get('aws_access_key')) print(provider.config.default_result_limit)) # change provider result limit provider.config.default_result_limit = 100
Return type: Configuration
Returns: An object of class Configuration, which contains the values used to initialize the provider, as well as other global configuration properties.
-
has_service
(service_type)[source]¶ Checks whether this provider supports a given service.
Example:
if provider.has_service(CloudServiceType.BUCKET): print("Provider supports object store services") provider.storage.buckets.list()
Parameters: service_type ( CloudServiceType
) – Type of service to check support for.Return type: bool
Returns: True
if the service type is supported.
-
networking
¶ Provide access to all network related services in this provider.
Example:
networks = provider.networking.networks.list() subnets = provider.networking.subnets.list() routers = provider.networking.routers.list()
Return type: NetworkingService
Returns: a NetworkingService object
-
security
¶ Provides access to key pair management and firewall control
Example:
keypairs = provider.security.keypairs.list() vm_firewalls = provider.security.vm_firewalls.list()
Return type: object
ofSecurityService
Returns: a SecurityService object
-
storage
¶ Provides access to storage related services in this provider. This includes the volume, snapshot and bucket services,
Example:
volumes = provider.storage.volumes.list() snapshots = provider.storage.snapshots.list() if provider.has_service(CloudServiceType.BUCKET): print("Provider supports object store services") print(provider.storage.buckets.list())
Return type: StorageService
Returns: a StorageService object
-
Services¶
CloudService¶
-
class
cloudbridge.cloud.interfaces.services.
CloudService
[source]¶ Base interface for any service supported by a provider. This interface has a provider property that can be used to access the provider associated with this service.
-
provider
¶ Returns the provider instance associated with this service.
Return type: CloudProvider
Returns: a CloudProvider object
-
ComputeService¶
-
class
cloudbridge.cloud.interfaces.services.
ComputeService
[source]¶ The compute service interface is a collection of services that provides access to the underlying compute related services in a provider. For example, the compute.instances service can be used to launch a new instance, and the compute.images service can be used to list available machine images.
-
images
¶ Provides access to all Image related services in this provider. (e.g. Glance in OpenStack)
Example:
# print all images for image in provider.compute.images: print(image.id, image.name, image.label) # print only first 50 images for image in provider.compute.images.list(limit=50): print(image.id, image.name, image.label) # find image by name image = provider.compute.images.find(name='Ubuntu 16.04')[0] print(image.id, image.name, image.label)
Return type: ImageService
Returns: an ImageService object
-
instances
¶ Provides access to all Instance related services in this provider.
Example:
# launch a new instance image = provider.compute.images.find(name='Ubuntu 16.04')[0] size = provider.compute.vm_types.find(name='m1.small') instance = provider.compute.instances.create('Hello', image, size) print(instance.id, instance.label)
Return type: InstanceService
Returns: an InstanceService object
-
regions
¶ Provides access to all Region related services in this provider.
Example:
for region in provider.compute.regions: print("Region: ", region.name) for zone in region.zones: print("\tZone: ", zone.name)
Return type: RegionService
Returns: a RegionService object
-
vm_types
¶ Provides access to all VM type related services in this provider.
Example:
# list all VM sizes for vm_type in provider.compute.vm_types: print(vm_type.id, vm_type.name) # find a specific size by name vm_type = provider.compute.vm_types.find(name='m1.small')[0] print(vm_type.vcpus)
Return type: VMTypeService
Returns: an VMTypeService object
-
InstanceService¶
-
class
cloudbridge.cloud.interfaces.services.
InstanceService
[source]¶ Provides access to instances in a provider, including creating, listing and deleting instances.
-
create
(label, image, vm_type, subnet, zone=None, key_pair=None, vm_firewalls=None, user_data=None, launch_config=None, **kwargs)[source]¶ Creates a new virtual machine instance.
Parameters: - label (
str
) – The label of the virtual machine instance. The instance name will be derived from this label. - image (
MachineImage
orstr
) – The MachineImage object or id to boot the virtual machine with - vm_type (
VMType
orstr
) – The VMType or name, specifying the size of the instance to boot into - subnet (
Subnet
orstr
) –The subnet object or a subnet string ID with which the instance should be associated. The subnet is a mandatory parameter, and must be provided when launching an instance.
Note: Older clouds (with classic networking), may not have proper subnet support and are not guaranteed to work. Some providers (e.g. OpenStack) support a null value but the behaviour is implementation specific.
- zone (
Zone
orstr
) –The Zone or its id, where the instance should be placed. This parameter is provided for legacy compatibility (with classic networks).
The subnet’s placement zone will take precedence over this parameter, but in its absence, this value will be used.
- key_pair (
KeyPair
orstr
) – The KeyPair object or its id, to set for the instance. - vm_firewalls (A
list
ofVMFirewall
objects or a list ofstr
object IDs) –A list of
VMFirewall
objects or a list ofVMFirewall
IDs, which should be assigned to this instance.The VM firewalls must be associated with the same network as the supplied subnet. Use
network.vm_firewalls
to retrieve a list of firewalls belonging to a network. - user_data (
str
) – An extra userdata object which is compatible with the provider. - launch_config (
LaunchConfig
object) – ALaunchConfig
object which describes advanced launch configuration options for an instance. Currently, this includes only block_device_mappings. To construct a launch configuration object, call provider.compute.instances.create_launch_config()
Return type: object
ofInstance
Returns: an instance of Instance class
- label (
-
create_launch_config
()[source]¶ Creates a
LaunchConfig
object which can be used to set additional options when launching an instance, such as block device mappings and network interfaces.Return type: object
ofLaunchConfig
Returns: an instance of a LaunchConfig class
-
find
(**kwargs)[source]¶ Searches for an instance by a given list of attributes.
Supported attributes: name, label
Parameters: - name (
str
) – The name to search for - label (
str
) – The label to search for
Return type: List of
object
ofInstance
Returns: A list of Instance objects matching the supplied attributes.
- name (
-
get
(instance_id)[source]¶ Returns an instance given its id. Returns None if the object does not exist.
Return type: object
ofInstance
Returns: an Instance object
-
list
(limit=None, marker=None)[source]¶ List available instances.
The returned results can be limited with limit and marker. If not specified, the limit defaults to a global default. See
list()
for more information on how to page through returned results.example:
# List instances instlist = provider.compute.instances.list() for instance in instlist: print("Instance Data: {0}", instance)
Parameters: - limit (
int
) – The maximum number of objects to return. Note that the maximum is not guaranteed to be honoured, and a lower maximum may be enforced depending on the provider. In such a case, the returned ResultList’s is_truncated property can be used to determine whether more records are available. - marker (
str
) – The marker is an opaque identifier used to assist in paging through very long lists of objects. It is returned on each invocation of the list method.
Return type: ResultList
ofInstance
Returns: A ResultList object containing a list of Instances
- limit (
-
VolumeService¶
-
class
cloudbridge.cloud.interfaces.services.
VolumeService
[source]¶ Base interface for a Volume Service.
-
create
(label, size, zone, snapshot=None, description=None)[source]¶ Creates a new volume.
Parameters: - label (
str
) – The label for the volume. - size (
int
) – The size of the volume (in GB). - zone (
str
orPlacementZone
object) – The availability zone in which the Volume will be created. - snapshot (
str
orSnapshot
object) – An optional reference to a snapshot from which this volume should be created. - description (
str
) – An optional description that may be supported by some providers. Providers that do not support this property will returnNone
.
Return type: object
ofVolume
Returns: a newly created Volume object.
- label (
-
find
(**kwargs)[source]¶ Searches for a volume by a given list of attributes.
Supported attributes: label
Return type: object
ofVolume
Returns: a Volume object or None
if not found.
-
SnapshotService¶
-
class
cloudbridge.cloud.interfaces.services.
SnapshotService
[source]¶ Base interface for a Snapshot Service.
-
create
(label, volume, description=None)[source]¶ Creates a new snapshot off a volume.
Parameters: - label (
str
) – The label for the snapshot. - volume (
str
orVolume
) – The volume to create a snapshot of. - description (
str
) – An optional description that may be supported by some providers. Providers that do not support this property will return None.
Return type: object
ofSnapshot
Returns: a newly created Snapshot object.
- label (
-
find
(**kwargs)[source]¶ Searches for a snapshot by a given list of attributes.
Supported attributes: label
Return type: list of Snapshot
Returns: a Snapshot object or an empty list if none found.
-
StorageService¶
-
class
cloudbridge.cloud.interfaces.services.
StorageService
[source]¶ The Storage Service interface provides access to block device services, such as volume and snapshot services, as well as object store services, such as buckets, in the provider.
-
buckets
¶ Provides access to object storage services in this provider.
Example:
# print all buckets for bucket in provider.storage.buckets: print(bucket.id, bucket.name) # find bucket by name bucket = provider.storage.buckets.find(name='my_bucket')[0] print(bucket.id, bucket.name)
Return type: BucketService
Returns: a BucketService object
-
snapshots
¶ Provides access to volume snapshots for this provider.
Example:
# print all snapshots for snap in provider.storage.snapshots: print(snap.id, snap.name, snap.label) # find snapshot by label snap = provider.storage.snapshots.find(label='my_snap')[0] print(snap.id, snap.name, snap.label)
Return type: SnapshotService
Returns: a SnapshotService object
-
volumes
¶ Provides access to volumes (i.e., block storage) for this provider.
Example:
# print all volumes for vol in provider.storage.volumes: print(vol.id, vol.name, vol.label) # find volume by label vol = provider.storage.volumes.find(label='my_vol')[0] print(vol.id, vol.name, vol.label)
Return type: VolumeService
Returns: a VolumeService object
-
ImageService¶
-
class
cloudbridge.cloud.interfaces.services.
ImageService
[source]¶ Base interface for an Image Service
-
find
(**kwargs)[source]¶ Searches for an image by a given list of attributes
Supported attributes: name, label
Return type: object
ofImage
Returns: an Image instance
-
get
(image_id)[source]¶ Returns an Image given its id. Returns None if the Image does not exist.
Return type: object
ofImage
Returns: an Image instance
-
list
(filter_by_owner=True, limit=None, marker=None)[source]¶ List all images.
Parameters: filter_by_owner ( bool
) – IfTrue
, return only images owned by the current user. Else, return all public images available from the provider. Note that fetching all images may take a long time.Return type: list
ofImage
Returns: list of image objects
-
NetworkingService¶
-
class
cloudbridge.cloud.interfaces.services.
NetworkingService
[source]¶ Base service interface for networking.
This service offers a collection of networking services that in turn provide access to networking resources.
-
networks
¶ Provides access to all Network related services.
Return type: NetworkService
Returns: a Network service object
-
routers
¶ Provides access to all Router related services.
Return type: RouterService
Returns: a Router service object
-
subnets
¶ Provides access to all Subnet related services.
Return type: SubnetService
Returns: a Subnet service object
-
NetworkService¶
-
class
cloudbridge.cloud.interfaces.services.
NetworkService
[source]¶ Base interface for a Network Service.
-
create
(label, cidr_block)[source]¶ Create a new network.
Parameters: - label (
str
) – A label for the network. - cidr_block (
str
) – The cidr block for this network. Some providers will respect this at the network level, while others will only respect it at subnet level. However, to write portable code, you should make sure that any subnets you create fall within this initially specified range. Note that the block size should be between a /16 netmask (65,536 IP addresses) and /28 netmask (16 IP addresses). e.g. 10.0.0.0/16
Return type: object
ofNetwork
Returns: A Network object
- label (
-
delete
(network_id)[source]¶ Delete an existing Network.
Parameters: network_id ( str
) – The ID of the network to be deleted.
-
find
(**kwargs)[source]¶ Searches for a network by a given list of attributes.
Supported attributes: name, label
Return type: List of object
ofNetwork
Returns: A list of Network objects matching the supplied attributes.
-
get
(network_id)[source]¶ Returns a Network given its ID or
None
if not found.Parameters: network_id ( str
) – The ID of the network to retrieve.Return type: object
ofNetwork
Returns: a Network object
-
list
(limit=None, marker=None)[source]¶ List all networks.
Return type: list
ofNetwork
Returns: list of Network objects
-
subnets
¶ Provides access to subnets.
Example:
# Print all subnets for s in provider.networking.subnets: print(s.id, s.name, s.label) # Get subnet by ID s = provider.networking.subnets.get('subnet-id') print(s.id, s.name, s.label)
Return type: SubnetService
Returns: a SubnetService object
-
SubnetService¶
-
class
cloudbridge.cloud.interfaces.services.
SubnetService
[source]¶ Base interface for a Subnet Service.
-
create
(label, network_id, cidr_block, zone)[source]¶ Create a new subnet within the supplied network.
Parameters: - label (
str
) – The subnet label. - network (
Network
object orstr
) – Network object or ID under which to create the subnet. - cidr_block (
str
) – CIDR block within the Network to assign to the subnet. - zone (
str
) – A placement zone for the subnet. Some providers may not support this, in which case the value is ignored.
Return type: object
ofSubnet
Returns: A Subnet object
- label (
-
delete
(subnet)[source]¶ Delete an existing Subnet.
Parameters: subnet ( Subnet
object orstr
) – Subnet object or ID of the subnet to delete.
-
find
(**kwargs)[source]¶ Searches for a subnet by a given list of attributes.
Supported attributes: name, label
Return type: List of object
ofSubnet
Returns: A list of Subnet objects matching the supplied attributes.
-
get
(subnet_id)[source]¶ Returns a Subnet given its ID or
None
if not found.Parameters: subnet_id ( Network
object orstr
) – The ID of the subnet to retrieve.Return type: object
ofSubnet
return: a Subnet object
-
get_or_create_default
(zone)[source]¶ Return a default subnet for the account or create one if not found. This provides a convenience method for obtaining a network if you are not particularly concerned with how the network is structured.
A default network is one marked as such by the provider or matches the default label used by this library (e.g., cloudbridge-net).
Parameters: zone ( PlacementZone
objectstr
) – Placement zone where to look for the subnet.Return type: object
ofSubnet
Returns: A Subnet object
-
RouterService¶
-
class
cloudbridge.cloud.interfaces.services.
RouterService
[source]¶ Manage networking router actions and resources.
-
create
(label, network)[source]¶ Create a new router.
Parameters: - label (
str
) – A router label. - network (
Network
object orstr
) – Network object or ID under which to create the router.
Return type: object
ofRouter
Returns: A Router object
- label (
-
delete
(router)[source]¶ Delete an existing Router.
Parameters: router ( Router
object orstr
) – Router object or ID of the router to delete.
-
find
(**kwargs)[source]¶ Searches for a router by a given list of attributes.
Supported attributes: name, label
Return type: List of object
ofRouter
Returns: A list of Router objects matching the supplied attributes.
-
BucketService¶
-
class
cloudbridge.cloud.interfaces.services.
BucketService
[source]¶ The Bucket Service interface provides access to the underlying object storage capabilities of this provider. This service is optional and the
CloudProvider.has_service()
method should be used to verify its availability before using the service.-
create
(name, location=None)[source]¶ Create a new bucket.
If a bucket with the specified name already exists, return a reference to that bucket.
Example:
bucket = provider.storage.buckets.create('my_bucket_name') print(bucket.name)
Parameters: - name (str) – The name of this bucket.
- location (
object
ofRegion
) – The region in which to place this bucket.
Returns: a Bucket object
Return type: object
ofBucket
-
find
(**kwargs)[source]¶ Searches for a bucket by a given list of attributes.
Supported attributes: name
Example:
buckets = provider.storage.buckets.find(name='my_bucket_name') for bucket in buckets: print(bucket.id, bucket.name)
Return type: Bucket
Returns: a Bucket instance
-
get
(bucket_id)[source]¶ Returns a bucket given its ID. Returns
None
if the bucket does not exist. On some providers, such as AWS and OpenStack, the bucket id is the same as its name.Example:
bucket = provider.storage.buckets.get('my_bucket_id') print(bucket.id, bucket.name)
Return type: Bucket
Returns: a Bucket instance
-
SecurityService¶
-
class
cloudbridge.cloud.interfaces.services.
SecurityService
[source]¶ The security service interface can be used to access security related functions in the provider, such as firewall control and keypairs.
-
key_pairs
¶ Provides access to key pairs for this provider.
Example:
# print all keypairs for kp in provider.security.keypairs: print(kp.id, kp.name) # find keypair by name kp = provider.security.keypairs.find(name='my_key_pair')[0] print(kp.id, kp.name)
Return type: KeyPairService
Returns: a KeyPairService object
-
vm_firewalls
¶ Provides access to firewalls (security groups) for this provider.
Example:
# print all VM firewalls for fw in provider.security.vm_firewalls: print(fw.id, fw.name) # find firewall by name fw = provider.security.vm_firewalls.find(name='my_vm_fw')[0] print(fw.id, fw.name)
Return type: VMFirewallService
Returns: a VMFirewallService object
-
KeyPairService¶
-
class
cloudbridge.cloud.interfaces.services.
KeyPairService
[source]¶ Base interface for key pairs.
-
create
(name, public_key_material=None)[source]¶ Create a new key pair or raise an exception if one already exists. If the public_key_material is provided, the material will be imported to create the new keypair. Otherwise, a new public and private key pair will be generated.
Parameters: - name (str) – The name of the key pair to be created.
- public_key_material (str) – The key-pair material to import in OpenSSH format.
Return type: object
ofKeyPair
Returns: A keypair instance or
None
.
-
delete
(key_pair_id)[source]¶ Delete an existing VMFirewall.
Parameters: key_pair_id (str) – The id of the key pair to be deleted. Return type: bool
Returns: True
if the key does not exist,False
otherwise. Note that this implies that the key may not have been deleted by this method but instead has not existed at all.
-
find
(**kwargs)[source]¶ Searches for a key pair by a given list of attributes.
Supported attributes: name
Return type: object
ofKeyPair
Returns: a KeyPair object
-
get
(key_pair_id)[source]¶ Return a KeyPair given its ID or
None
if not found.On some providers, such as AWS and OpenStack, the KeyPair ID is the same as its name.
Example:
key_pair = provider.security.keypairs.get('my_key_pair_id') print(key_pair.id, key_pair.name)
Return type: KeyPair
Returns: a KeyPair instance
-
VMFirewallService¶
-
class
cloudbridge.cloud.interfaces.services.
VMFirewallService
[source]¶ Base interface for VM firewalls.
-
create
(label, network_id, description=None)[source]¶ Create a new VMFirewall.
Parameters: - label (str) – The label for the new VM firewall.
- network_id (
str
) – Network ID under which to create the VM firewall. - description (str) – The description of the new VM firewall.
Return type: object
ofVMFirewall
Returns: A VMFirewall instance or
None
if one was not created.
-
delete
(group_id)[source]¶ Delete an existing VMFirewall.
Parameters: group_id (str) – The VM firewall ID to be deleted.
-
find
(**kwargs)[source]¶ Get VM firewalls associated with your account filtered by name.
Supported attributes: name
Parameters: name (str) – The name of the VM firewall to retrieve. Return type: list of VMFirewall
Returns: A list of VMFirewall objects or an empty list if none found.
-
get
(vm_firewall_id)[source]¶ Returns a VMFirewall given its ID. Returns
None
if the VMFirewall does not exist.Example:
fw = provider.security.vm_firewalls.get('my_fw_id') print(fw.id, fw.name)
Return type: VMFirewall
Returns: a VMFirewall instance
-
list
(limit=None, marker=None)[source]¶ List all VM firewalls associated with this account.
Return type: list
ofVMFirewall
Returns: list of VMFirewall objects
-
VMTypeService¶
-
class
cloudbridge.cloud.interfaces.services.
VMTypeService
[source]¶ -
find
(**kwargs)[source]¶ Searches for an instance by a given list of attributes.
Supported attributes: name
Return type: object
ofVMType
Returns: an Instance object
-
RegionService¶
-
class
cloudbridge.cloud.interfaces.services.
RegionService
[source]¶ Base interface for a Region service
-
current
¶ Returns the current region that this provider is connected to.
If the current region cannot be discovered, return
None
.Return type: object
ofRegion
Returns: a Region instance or None
-
find
(**kwargs)[source]¶ Searches for a region by a given list of attributes.
Supported attributes: name
Return type: object
ofRegion
Returns: a Region object
-
Resources¶
- CloudServiceType
- CloudResource
- Configuration
- ObjectLifeCycleMixin
- PageableObjectMixin
- ResultList
- InstanceState
- Instance
- MachineImageState
- LaunchConfig
- MachineImage
- NetworkState
- Network
- SubnetState
- Subnet
- FloatingIP
- RouterState
- Router
- Gateway
- InternetGateway
- VolumeState
- Volume
- SnapshotState
- Snapshot
- KeyPair
- Region
- PlacementZone
- VMType
- VMFirewall
- VMFirewallRule
- TrafficDirection
- BucketObject
- Bucket
CloudResource¶
-
class
cloudbridge.cloud.interfaces.resources.
CloudResource
[source]¶ Base interface for any Resource supported by a provider.
This interface has a _provider property that can be used to access the provider associated with the resource, which is only intended for use by subclasses. Every cloudbridge resource also has an id, a name and a label property. The id property is a unique identifier for the resource. The name is a more user-friendly version of an id, suitable for display to an end-user. However, it cannot be used in place of id. See @name documentation. The label property is a user-assignable identifier for the resource.
-
id
¶ Get the resource identifier.
The id property is used to uniquely identify the resource, and is an opaque value which should not be interpreted by cloudbridge clients, and is a value meaningful to the underlying cloud provider.
Return type: str
:return: ID for this resource as returned by the cloudmiddleware.
-
name
¶ Get the name id for the resource.
The name property is typically a user-friendly id value for the resource. The name is different from the id property in the following ways: 1. The name property is often a more user-friendly value to
display to the user than the id property.- The name may sometimes be the same as the id, but should never be used in place of the id.
- The id is what will uniquely identify a resource, and will be used internally by cloudbridge for all get operations etc.
- All resources have a name.
- The name is read-only.
- However, the name may not necessarily be unique, which is the reason why it should not be used for uniquely identifying a resource.
Example: The AWS machine image name maps to a cloudbridge name. It is not editable and is a user friendly name such as ‘Ubuntu 14.04’ and corresponds to the ami-name. It is distinct from the ami-id, which maps to cloudbridge’s id property. The ami-name cannot be edited, and is set at creation time. It is not necessarily unique. In Azure, the machine image’s name corresponds to cloudbridge’s name property. In Azure, it also happens to be the same as the id property.
The name property and the label property share the same character restrictions. see
label
-
Configuration¶
-
class
cloudbridge.cloud.interfaces.resources.
Configuration
[source]¶ Represents a cloudbridge configuration object
-
debug_mode
¶ A flag indicating whether CloudBridge is in debug mode.
Setting this to
True
will cause the underlying provider’s debug output to be turned on. The flag can be toggled by sending in thecb_debug
value via the config dictionary, or setting theCB_DEBUG
environment variable.Return type: bool
Returns: Whether debug mode is on.
-
default_result_limit
¶ Get the default maximum number of results to return for a list method.
The default limit will be applied to most
list()
andfind()
methods whenever an explicit limit is not specified.Return type: int
Returns: The maximum number of results to return
-
default_wait_interval
¶ Get the default wait interval for
LifeCycleObjects
.The default wait interval is applied in
wait_for()
andwait_till_ready()
methods if no explicit interval is specified.Return type: int
Returns: How frequently to poll the object’s state.
-
default_wait_timeout
¶ Get the default wait timeout for
LifeCycleObjects
.The default wait timeout is applied in
wait_for()
andwait_till_ready()
methods if no explicit timeout is specified.Return type: int
Returns: The maximum length of time (in seconds) to wait for the object to change to desired state.
-
ObjectLifeCycleMixin¶
-
class
cloudbridge.cloud.interfaces.resources.
ObjectLifeCycleMixin
[source]¶ A mixin for an object with a defined life-cycle.
Object examples include an Instance, Volume, Image, or Snapshot. An object that supports ObjectLifeCycleMixin will always have a state, defining which point in its life cycle it is currently at.
It also defines a
wait_till_ready
operation, which indicates that the object is in a state in its life cycle where it is ready to be used by an end-user.A
refresh
operation allows the object to synchronize its state with the service provider.-
state
¶ Get the current state of this object.
Return type: str
Returns: The current state as a string.
-
wait_for
(target_states, terminal_states=None, timeout=None, interval=None)[source]¶ Wait for for an object to reach a one of desired target states.
If the object does not reach the desired state within the specified timeout, a
WaitStateException
will be raised. The optionalterminal_states
property can be used to specify an additional set of states which, should the object reach one, the object thereafter will not transition into the desired target state. Should this happen, aWaitStateException
will be raised.Example:
instance.wait_for( [InstanceState.DELETED, InstanceState.UNKNOWN], terminal_states=[InstanceState.ERROR])
Parameters: - target_states (
list
of states) – The list of target states to wait for. - terminal_states (
list
of states) – A list of terminal states after which the object will not transition into a target state. A WaitStateException will be raised if the object transition into a terminal state. - timeout (
int
) – The maximum length of time (in seconds) to wait for the object to changed to desired state. If no timeout is specified, the global default_wait_timeout defined in the provider config will apply. - interval (
int
) – How frequently to poll the object’s state (in seconds). If no interval is specified, the global default_wait_interval defined in the provider config will apply.
Return type: True
Returns: Returns
True
if successful. AWaitStateException
exception may be thrown by the underlying service if the object cannot get into a ready state (e.g. if the object is in an error state).- target_states (
-
wait_till_ready
(timeout, interval)[source]¶ Wait till the current object reaches its ready state.
An object’s ready state is any state where the end-user can successfully interact with the object. Will throw a
WaitStateException
if the object is not ready within the specified timeout.Parameters: - timeout (
int
) – The maximum length of time (in seconds) to wait for the object to become ready. - interval (
int
) – How frequently to poll the object’s ready state (in seconds).
Return type: True
Returns: Returns
True
if successful. AWaitStateException
exception may be thrown by the underlying service if the object cannot get into a ready state (e.g. if the object is in an error state).- timeout (
-
PageableObjectMixin¶
-
class
cloudbridge.cloud.interfaces.resources.
PageableObjectMixin
[source]¶ A marker interface for objects which support paged iteration.
The list of objects can be iterated over using the
list(limit, marker)
method.-
list
(limit=None, marker=None)[source]¶ Returns a list of objects up to a maximum limit.
If a limit and marker are specified, the records will be fetched up to the limit starting from the marker onwards. The returned list is a list of class ResultList, which has extra properties like is_truncated, supports_total and total_records to provide extra information about record availability.
If limit is not specified, the limit will default to the underlying provider’s default limit. Therefore, you need to check the is_truncated property to determine whether more records are available.
The total number of results can be determined through the total_results property. Not all provides will support returning the total_results property, so the supports_total property can be used to determine whether a total is supported.
To iterate through all the records, it will be easier to iterate directly through the instances using __iter__ instead of calling the list method. The __iter__ method will automatically call the list method to fetch a batch of records at a time.
Example:
# get first page of results instlist = provider.compute.instances.list(limit=50) for instance in instlist: print("Instance Data: {0}", instance) if instlist.supports_total: print("Total results: {0}".format(instlist.total_results)) else: print("Total records unknown," "but has more data?: {0}".format(instlist.is_truncated)) # Page to next set of results if (instlist.is_truncated) instlist = provider.compute.instances.list(limit=100, marker=instlist.marker) # Alternative: iterate through every available record for instance in provider.compute.instances: print(instance)
-
ResultList¶
-
class
cloudbridge.cloud.interfaces.resources.
ResultList
[source]¶ Provide extra properties to aid with paging through a many results.
This is a wrapper class around a standard Python
list
class.Example:
# get first page of results rl = provider.compute.instances.list(limit=50) for result in rl: print("Instance Data: {0}", result) if rl.supports_total: print("Total results: {0}".format(rl.total_results)) else: print("Total records unknown," "but has more data?: {0}."format(rl.is_truncated)) # Page to next set of results if (rl.is_truncated) rl = provider.compute.instances.list(limit=100, marker=rl.marker)
-
is_truncated
¶ Indicate whether this result list has more results that can be paged.
-
marker
¶ An opaque identifier used in paging through very long lists of objects.
This marker can be provided to the list method to get the next set of results.
-
supports_server_paging
¶ Indicate whether this
ResultList
supports server side paging.If server side paging is not supported, the result will useclient side paging and the data property provides direct access to all available data.
-
supports_total
¶ Indicate whether can obtain the total number of available results.
The
supports_total
property should be checked before accessing thetotal_results
property. This is a provider-specific property.
-
total_results
¶ Indicate the total number of results for a particular query.
The
supports_total
property should be used to check whether the provider supports returning the total number of results, before accessing this property, or the behavior is indeterminate.
-
InstanceState¶
-
class
cloudbridge.cloud.interfaces.resources.
InstanceState
[source]¶ Standard states for an instance.
Variables: - UNKNOWN – Instance state unknown.
- PENDING – Instance is pending
- CONFIGURING – Instance is being reconfigured in some way.
- RUNNING – Instance is running.
- REBOOTING – Instance is rebooting.
- DELETED – Instance is deleted. No further operations possible.
- STOPPED – Instance is stopped. Instance can be resumed.
- ERROR – Instance is in an error state. No further operations possible.
Instance¶
-
class
cloudbridge.cloud.interfaces.resources.
Instance
[source]¶ -
add_floating_ip
(floating_ip)[source]¶ Add a public IP address to this instance.
Parameters: floating_ip (:class: .FloatingIP
or floating IP ID) – The FloatingIP object to associate with the instance. Note that is not the actual public IP address but the CloudBridge object encapsulating the IP or the respective provider ID that identifies the address.
-
add_vm_firewall
(firewall)[source]¶ Add a VM firewall to this instance
Parameters: firewall (:class: .VMFirewall
) – The VMFirewall to associate with the instance.
-
create_image
(label)[source]¶ Create a new image based on this instance.
Return type: :class: .Image
Returns: an Image object
-
image_id
¶ Get the image ID for this instance.
Return type: str
Returns: Image ID (i.e., AMI) this instance is using.
-
key_pair_id
¶ Get the id of the key pair associated with this instance.
Return type: str
Returns: Id of the ssh key pair associated with this instance.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
private_ips
¶ Get all the private IP addresses for this instance.
Return type: list
Returns: A list of private IP addresses associated with this instance.
-
public_ips
¶ Get all the public IP addresses for this instance.
Return type: list
Returns: A list of public IP addresses associated with this instance.
-
reboot
()[source]¶ Reboot this instance (using the cloud middleware API).
Return type: bool
Returns: True
if the reboot was successful;False
otherwise.
-
remove_floating_ip
(floating_ip)[source]¶ Remove a public IP address from this instance.
Parameters: floating_ip (:class: .FloatingIP
or floating IP ID) – The FloatingIP object to remove from the instance. Note that is not the actual public IP address but the CloudBridge object encapsulating the IP or the respective provider ID that identifies the address.
-
remove_vm_firewall
(firewall)[source]¶ Remove a VM firewall from this instance
Parameters: firewall ( VMFirewall
) – The VMFirewall to associate with the instance.
-
subnet_id
¶ Get the subnet ID where this instance is placed.
Return type: str
Returns: Subnet ID to which this instance is connected.
-
vm_firewall_ids
¶ Get the IDs of the VM firewalls associated with this instance.
Return type: list or :class: str
Returns: A list of the VMFirewall IDs associated with this instance.
-
vm_firewalls
¶ Get the firewalls (security groups) associated with this instance.
Return type: list or VMFirewall
objectsReturns: A list of VMFirewall objects associated with this instance.
-
vm_type
¶ Retrieve full VM type information for this instance.
Return type: VMType
Returns: VM type for this instance
-
vm_type_id
¶ Get the VM type id for this instance.
This will typically be a string value like ‘m1.large’. On OpenStack, this may be a number or UUID. To get the full :class:
.VMType
object, you can use theinstance.vm_type
property instead.Return type: str
Returns: VM type id for this instance (e.g., m1.large
)
-
zone_id
¶ Get the placement zone ID where this instance is running.
Return type: str
Returns: Region/zone/placement where this instance is running.
-
LaunchConfig¶
-
class
cloudbridge.cloud.interfaces.resources.
LaunchConfig
[source]¶ Represents an advanced launch configuration object.
This object can contain information such as
BlockDeviceMappings
configurations and other advanced options, which may be useful when launching an instance.Example:
lc = provider.compute.instances.create_launch_config() lc.add_block_device(...) inst = provider.compute.instances.create( 'MyVM', image, vm_type, subnet, launch_config=lc)
-
add_ephemeral_device
()[source]¶ Add a new ephemeral block device mapping to the boot configuration.
This can be used to add existing ephemeral devices to the instance (the total number of ephemeral devices available for a particular
VMType
can be determined by querying theVMType
service). Note that on some providers, such as AWS, ephemeral devices must be added in as a device mapping at instance creation time and cannot be added afterwards.Note that the device name, such as /dev/sda1, cannot be selected at present, since this tends to be provider and VM type specific. However, the order of device addition coupled with device type will generally determine naming order, with devices added first getting lower letters than instances added later.
Example:
lc = provider.compute.instances.create_launch_config() # 1. Add all available ephemeral devices vm_type = provider.compute.vm_types.find(name='m1.tiny')[0] for i in range(vm_type.num_ephemeral_disks): lc.add_ephemeral_device()
-
add_volume_device
(source=None, is_root=None, size=None, delete_on_terminate=None)[source]¶ Add a new volume based block device mapping to the boot configuration.
The volume can be based on a snapshot, image, existing volume or be a blank new volume, and is specified by the source parameter.
The property
is_root
can be set toTrue
to override any existing root device mappings. Otherwise, the default behavior is to add new block devices to the instance.Note that the device name, such as /dev/sda1, cannot be selected at present since this tends to be provider and VM type specific. However, the order of device addition coupled with device type will generally determine naming order, with devices added first getting lower letters than instances added later (except when
is_root
is set).Example:
lc = provider.compute.instances.create_launch_config() # 1. Create and attach an empty volume of size 100GB lc.add_volume_device(size=100, delete_on_terminate=True) # 2. Create and attach a volume based on a snapshot snap = provider.storage.snapshots.get('<my_snapshot_id>') lc.add_volume_device(source=snap) # 3. Create+attach a volume based on an image and set it as root img = provider.compute.images.get('<my_image_id>') lc.add_volume_device(source=img, size=100, is_root=True)
Parameters: - source (
Volume
,Snapshot
,Image
or None.) – The sourceblock_device
to add. IfVolume
, the volume will be attached directly to the instance. IfSnapshot
, a volume will be created based on the Snapshot and attached to the instance. IfImage
, a volume based on the Image will be attached to the instance. IfNone
, the source is assumed to be a blank volume. - is_root (
bool
) – Determines which device will serve as the root device. If more than one device is defined as root, anInvalidConfigurationException
will be thrown. - size (
int
) – The size of the volume to create. An implementation may ignore this parameter for certain sources like ‘Volume’. - delete_on_terminate (
bool
) – Determines whether to delete or keep the volume on instance termination.
- source (
-
MachineImage¶
-
class
cloudbridge.cloud.interfaces.resources.
MachineImage
[source]¶ -
-
description
¶ Get the image description.
Return type: str
Returns: Description for this image as returned by the cloud middleware.
-
min_disk
¶ Return the minimum size of the disk that’s required to boot this image.
Value returned is in gigabytes.
Return type: int
Returns: The minimum disk size needed by this image.
-
Network¶
-
class
cloudbridge.cloud.interfaces.resources.
Network
[source]¶ Represents a software-defined network, like the Virtual Private Cloud.
-
cidr_block
¶ A CIDR block for this network.
Note
OpenStack does not define a CIDR block for networks.
Return type: str
Returns: A CIDR block string.
-
create_subnet
(label, cidr_block, zone=None)[source]¶ Create a new network subnet and associate it with this Network.
Parameters: - label (
str
) – The subnet label. The subnet name will be derived from this label. - cidr_block (
str
) – CIDR block within this Network to assign to the subnet. - zone (
str
) – Placement zone where to create the subnet. Some providers may not support subnet zones, in which case the value is ignored.
Return type: object
ofSubnet
Returns: A Subnet object
- label (
-
external
¶ A flag to indicate if this network is capable of Internet-connectivity.
Return type: bool
Returns: True
if the network can be connected to the Internet.
-
gateways
¶ Provides access to the internet gateways attached to this network.
Return type: GatewayContainer
Returns: A GatewayContainer object
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
state
¶ The state of the network.
Return type: str
Returns: One of unknown
,pending
,available
,down
orerror
.
-
Subnet¶
-
class
cloudbridge.cloud.interfaces.resources.
Subnet
[source]¶ Represents a subnet, as part of a Network.
-
cidr_block
¶ A CIDR block for this subnet.
Return type: str
Returns: A CIDR block string.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
network
¶ The parent network object associated with this this subnet.
Return type: Network
Returns: Network object
-
network_id
¶ ID of the network associated with this this subnet.
Return type: str
Returns: Network ID.
-
zone
¶ Placement zone of the subnet.
If the provider does not support subnet placement, return
None
.Return type: PlacementZone
objectReturns: Placement zone of the subnet, or None
if not defined.
-
FloatingIP¶
-
class
cloudbridge.cloud.interfaces.resources.
FloatingIP
[source]¶ Represents a floating (i.e., static) IP address.
-
in_use
¶ Whether the address is in use or not.
Return type: bool
Returns: True
if the address is attached to an instance.
-
private_ip
¶ Private IP address this address is attached to.
Return type: str
Returns: IP address or None
.
-
public_ip
¶ Public IP address.
Return type: str
Returns: IP address.
-
Router¶
-
class
cloudbridge.cloud.interfaces.resources.
Router
[source]¶ Represents a private network router.
This logical router is meant to roughly mimic the properties of a physical router. Therefore, attaching a subnet can be thought of as plugging in a network cable to enable routing to/from that subnet. Attaching a gateway can be thought of as plugging in an upstream link.
-
attach_gateway
(gateway)[source]¶ Attach a gateway to this router.
Parameters: gateway ( Gateway
) – The Gateway to attach to this router.Return type: bool
Returns: True
if successful.
-
attach_subnet
(subnet)[source]¶ Attach this router to a subnet.
Parameters: subnet ( Subnet
orstr
) – The subnet to which to attach this router.Return type: bool
Returns: True
if successful.
-
detach_gateway
(gateway)[source]¶ Detach this router from a gateway.
Return type: bool
Returns: True
if successful.
-
detach_subnet
(subnet)[source]¶ Detach this subnet from a network.
Parameters: subnet ( Subnet
orstr
) – The subnet to detach from this router.Return type: bool
Returns: True
if successful.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
network_id
¶ ID of the network to which the router is attached.
Return type: str
Returns: ID for the attached network or None
.
-
state
¶ Router state: attached or detached to a network.
Return type: str
Returns: attached
ordetached
.
-
Gateway¶
-
class
cloudbridge.cloud.interfaces.resources.
Gateway
[source]¶ Represents a gateway resource.
-
delete
()[source]¶ Delete this gateway. On some providers, if the gateway is public/a singleton, this operation will do nothing.
-
floating_ips
¶ Provides access to floating IPs connected to this internet gateway.
Return type: FloatingIPContainer
Returns: A FloatingIPContainer object
-
network_id
¶ ID of the network to which the gateway is attached.
Return type: str
Returns: ID for the attached network or None
.
-
VolumeState¶
-
class
cloudbridge.cloud.interfaces.resources.
VolumeState
[source]¶ Standard states for a volume
Variables: - UNKNOWN – Volume state unknown.
- CREATING – Volume is being created.
- CONFIGURING – Volume is being configured in some way.
- AVAILABLE – Volume is available and can be attached to an instance.
- IN_USE – Volume is attached and in-use.
- DELETED – Volume has been deleted. No further operations possible.
- ERROR – Volume is in an error state. No further operations possible.
Volume¶
-
class
cloudbridge.cloud.interfaces.resources.
Volume
[source]¶ Represents a block storage device (aka volume).
-
attach
(instance, device)[source]¶ Attach this volume to an instance.
Parameters: - instance (
str
orInstance
object) – The ID of an instance or anInstance
object to which this volume will be attached. - device (
str
) – The device on the instance through which the volume will be exposed (e.g. /dev/sdh).
Return type: bool
Returns: True
if successful.- instance (
-
attachments
¶ Get attachment information for this volume.
Return type: AttachmentInfo
Returns: Returns an AttachmentInfo object.
-
create_snapshot
(label, description=None)[source]¶ Create a snapshot of this Volume.
Parameters: - label (
str
) – The label for this snapshot. - description (
str
) – A description of the snapshot. Limited to 256 characters.
Return type: Returns: The created Snapshot object.
- label (
-
create_time
¶ Get the creation data and time for this volume.
Return type: DateTime
Returns: Creation time for this volume as returned by the cloud middleware.
-
description
¶ Get the volume description.
Some cloud providers may not support this property, and will return the volume label instead.
Return type: str
Returns: Description for this volume as returned by the cloud middleware.
-
detach
(force=False)[source]¶ Detach this volume from an instance.
Parameters: force ( bool
) – Forces detachment if the previous detachment attempt did not occur cleanly. This option is supported on select clouds only. This option can lead to data loss or a corrupted file system. Use this option only as a last resort to detach a volume from a failed instance. The instance will not have an opportunity to flush file system caches nor file system meta data. If you use this option, you must perform file system check and repair procedures.Return type: bool
Returns: True
if successful.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
size
¶ Get the volume size (in GB).
Return type: int
Returns: Size for this volume as returned by the cloud middleware.
-
source
¶ If available, get the source that this volume is based on.
This can be a
Snapshot
, anImage
, orNone
if no source.Return type: Snapshot
,Image
, orNone
Returns: Snapshot or Image source for this volume as returned by the cloud middleware.
-
zone_id
¶ Get the placement zone id that this volume belongs to.
Return type: str
Returns: PlacementZone for this volume as returned by the cloud middleware.
-
SnapshotState¶
-
class
cloudbridge.cloud.interfaces.resources.
SnapshotState
[source]¶ Standard states for a snapshot
Variables: - UNKNOWN – Snapshot state unknown.
- PENDING – Snapshot is pending.
- CONFIGURING – Snapshot is being configured in some way.
- AVAILABLE – Snapshot has been completed and is ready for use.
- ERROR – Snapshot is in an error state. No further operations possible.
Snapshot¶
-
class
cloudbridge.cloud.interfaces.resources.
Snapshot
[source]¶ Represents a snapshot of a block storage device.
-
create_time
¶ Get the creation data and time for this snapshot.
Return type: DateTime
Returns: Creation time for this snapshot as returned by the cloud middleware.
-
create_volume
(placement, size=None, volume_type=None, iops=None)[source]¶ Create a new Volume from this Snapshot.
Parameters: - placement (
str
) – The availability zone where to create the Volume. - size (
int
) – The size of the new volume, in GiB (optional). Defaults to the size of the snapshot. - volume_type (
str
) – The type of the volume (optional). Availability and valid values depend on the provider. - iops (
int
) – The provisioned IOPs you want to associate with this volume (optional). Availability depends on the provider.
Return type: Returns: An instance of the created Volume.
- placement (
-
description
¶ Get the snapshot description.
Some cloud providers may not support this property, and will return the snapshot label instead.
Return type: str
Returns: Description for this snapshot as returned by the cloud middleware.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
size
¶ Get the snapshot size (in GB).
Return type: int
Returns: Size for this snapshot as returned by the cloud middleware.
-
volume_id
¶ Get the id of the volume that this snapshot is based on.
This method may return
None
if the source volume no longer exists.Return type: int
Returns: Id of the volume that this snapshot is based on
-
Region¶
-
class
cloudbridge.cloud.interfaces.resources.
Region
[source]¶ Represents a cloud region.
A cloud region is typically a separate geographic area and will contain at least one placement zone.
-
zones
¶ Access information about placement zones within this region.
Return type: Iterable Returns: Iterable of available placement zones in this region.
-
VMType¶
-
class
cloudbridge.cloud.interfaces.resources.
VMType
[source]¶ A VM type object.
-
extra_data
¶ A dictionary of extra data about this instance. May contain nested dictionaries, but all key value pairs are strings or integers.
Return type: dict
Returns: Extra attributes for this VM type.
-
family
¶ The family/group that this VM type belongs to.
For example, General Purpose Instances or High-Memory Instances. If the provider does not support such a grouping, it may return
None
.Return type: str
Returns: Name of the instance family or None
.
-
num_ephemeral_disks
¶ The total number of ephemeral disks on this VM type.
Return type: int
Returns: Number of ephemeral disks available.
-
ram
¶ The amount of RAM (in GB) supported by this VM type.
Return type: float
Returns: Total RAM (in GB).
-
size_ephemeral_disks
¶ The size of this VM types’s total ephemeral storage (in GB).
Return type: int
Returns: Size of ephemeral disks (in GB).
-
size_root_disk
¶ The size of this VM types’s root disk (in GB).
Return type: int
Returns: Size of root disk (in GB).
-
size_total_disk
¶ The total disk space available on this VM type (root_disk + ephemeral).
Return type: int
Returns: Size of total disk space (in GB).
-
vcpus
¶ The number of VCPUs supported by this VM type.
Return type: int
Returns: Number of VCPUs.
-
VMFirewall¶
-
class
cloudbridge.cloud.interfaces.resources.
VMFirewall
[source]¶ Represents a firewall resource applied to virtual machines.
This is in contrast to a firewall for a network, for example.
-
description
¶ Return the description of this VM firewall.
Return type: str
Returns: A description of this VM firewall.
-
label
¶ Get the resource label.
The label property is a user-defined, editable identifier for a resource. It will often correspond to a user editable resource label in the underlying cloud provider, or be simulated through tags/labels.
The label property adheres to the following restrictions: * Must be at least 3 characters in length. * Cannot be longer than 63 characters. * May only contain ASCII characters comprising of lowercase letters,
numeric characters, and dashes.- Must begin with an alphanumeric character and end with one (i.e. cannot begin or end with a dash)
Some resources may not support labels, in which case, a NotImplementedError will be thrown.
Return type: str
Returns: Label for this resource as returned by the cloud middleware. :throws NotImplementedError if this resource does not support labels
-
network_id
¶ Network ID with which this VM firewall is associated.
Return type: str
Returns: Provider-supplied network ID or None
is not available.
-
rules
¶ Get a container for the rules belonging to this VM firewall.
This object can be used for further operations on rules, such as get, list, create, etc.
Return type: An object of VMFirewallRuleContainer
Returns: A VMFirewallRuleContainer for further operations
-
VMFirewallRule¶
-
class
cloudbridge.cloud.interfaces.resources.
VMFirewallRule
[source]¶ Represents a VM firewall rule.
-
cidr
¶ CIDR block this VM firewall is providing access to.
Return type: str
Returns: CIDR block.
-
direction
¶ Direction of traffic to which this rule applies.
Either
TrafficDirection.INBOUND
orTrafficDirection.OUTBOUND
.Return type: str
Returns: Direction of traffic to which this rule applies.
-
from_port
¶ Lowest port number opened as part of this rule.
Return type: int
Returns: Lowest port number or 0 if not set.
-
protocol
¶ IP protocol used. Either
tcp
|udp
|icmp
.Return type: str
Returns: Active protocol.
-
src_dest_fw
¶ VM firewall given access permissions by this rule.
Return type: :class: .VMFirewall
Returns: The VM firewall granted access.
-
src_dest_fw_id
¶ VM firewall id given access permissions by this rule.
Return type: str
Returns: The VM firewall granted access.
-
to_port
¶ Highest port number opened as part of this rule.
Return type: int
Returns: Highest port number or 0 if not set.
-
BucketObject¶
-
class
cloudbridge.cloud.interfaces.resources.
BucketObject
[source]¶ Represents an object stored within a bucket.
-
generate_url
(expires_in)[source]¶ Generate a URL to this object.
If the object is public, expires_in argument is not necessary, but if the object is private, the lifetime of URL is set using expires_in argument.
Parameters: expires_in ( int
) – Time to live of the generated URL in seconds.Return type: str
Returns: A URL to access the object.
-
iter_content
()[source]¶ Returns this object’s content as an iterable.
Return type: Iterable Returns: An iterable of the file contents
-
last_modified
¶ Get the date and time this object was last modified.
Return type: str
Returns: Date and time formatted string %Y-%m-%dT%H:%M:%S.%f
-
name
¶ Retrieve the name of the current object.
The bucket object name adheres to a naming requirement that is more relaxed than the naming requirement enforced across CloudBridge. More details are available here: http://docs.aws.amazon.com/AmazonS3/latest/ dev/UsingMetadata.html#object-key-guidelines
Return type: str
Returns: Name for this object as returned by the cloud middleware.
-
refresh
()[source]¶ Refresh this object’s state and synchronize it with the underlying service provider.
-
size
¶ Get this object’s size.
Return type: int
Returns: Size of this object in bytes.
-
Bucket¶
-
class
cloudbridge.cloud.interfaces.resources.
Bucket
[source]¶ Represents a namespace for objects (eg, object store bucket or container).
-
delete
(delete_contents=False)[source]¶ Delete this bucket.
Parameters: delete_contents ( bool
) – IfTrue
, all objects within the bucket will be deleted.Return type: bool
Returns: True
if successful.
-
name
¶ Retrieve the name of the current bucket.
Return type: str
Returns: Name for this instance as returned by the cloud middleware.
-
objects
¶ Get a container for the objects belonging to this Bucket.
This object can be used to iterate through bucket objects, as well as perform further operations on buckets, such as
get
,list
,create
, etc.# Show all objects in bucket print(list(bucket.objects)) # Find an object by name print(bucket.objects.find(name='my_obj.txt')) # Get first page of bucket list print(bucket.objects.list()) # Create a new object within this bucket obj = bucket.objects.create('my_obj.txt')
Return type: BucketContainer
Returns: A BucketContainer for further operations.
-
Exceptions¶
InvalidLabelException¶
-
class
cloudbridge.cloud.interfaces.exceptions.
InvalidLabelException
(msg)[source]¶ Marker interface for any attempt to set an invalid label on a CloudBridge resource. An example would be setting uppercase letters, which are not allowed in a resource label. InvalidLabelExceptions inherit from, and are a special case of InvalidNameExceptions. At present, these restrictions are identical.
InvalidValueException¶
-
class
cloudbridge.cloud.interfaces.exceptions.
InvalidValueException
(param, value)[source]¶ Marker interface for any attempt to set an invalid value on a CloudBridge resource.An example would be setting an unrecognised value for the direction of a firewall rule other than TrafficDirection.INBOUND or TrafficDirection.OUTBOUND.