CSS Corp Open Source Services

Archive for the ‘Nova API’ Category

[OpenStack Beginner’s Guide for Ubuntu 11.04] Storage Management

with 2 comments

Nova-volume

Nova-volume provides persistent block storage compatible with Amazon’s Elastic Block Store. The storage on the instances is non persistent in nature and hence any data that you generate and store on the file system on the first disk of the instance gets lost when the instance is terminated. You will need to use persistent volumes provided by nova-volume if you want any data generated during the life of the instance to persist after the instance is terminated.

Commands from euca2ools package can be used to manage these volumes.

Here are a few examples:

Read the rest of this entry »

[OpenStack Beginner’s Guide for Ubuntu 11.04] OpenStack Commands

with 4 comments

Nova Manage commands

OpenStack provides commands for administrative tasks such as user/role management,  network management etc. In all the examples we will use username as “novadmin” and project name as “proj”. All the nova-manage commands will need to be run as “root”. Either run them as root or run them under sudo.

Read the rest of this entry »

[OpenStack Beginner’s Guide for Ubuntu 11.04] Role Based Access Control

with 3 comments

Every nova user has a role associated with him. This role can be assigned at the time of creation of the account using “nova-manage add user…” or by editing the profile later using the Openstack Dashboard by the project manager. The role can be either global or project specific in scope. All access in Openstack is governed by roles. Each role has a predefined set of operations permitted within the relevant scope(global or local)

Read the rest of this entry »

[OpenStack Beginner’s Guide for Ubuntu 11.04] Security

leave a comment »

Openstack provides ingress filtering for the instances based on the concept of security groups. OpenStack accomplishes ingress filtering by creating suitable IP Tables rules. A Security Group is a named set of rules that get applied to the incoming packets for the instances. You can specify a security group while launching an instance. Each security group can have multiple rules associated with it. Each rule specifies the source IP/network, protocol type, destination ports etc. Any packet matching these parameters specified in a rule is allowed in. Rest of the packets are blocked.

Read the rest of this entry »