- date
2014-09-08 15:46
- tags
rackspace, openstack
- category
*nix
This VirtualBox Appliance will get you up and running with OpenStack Icehouse quickly!
Cinder maintains an iSCSI connection between the cinder-volume and compute node when utilizing the LVM driver (cinder.volume.drivers.lvm.LVMISCSIDriver).
If one uses the NFS driver for a backend (cinder.volume.drivers.nfs.NfsDriver), the volume is served to the compute node via NFS share.
Multiple-storage back-end capability in Cinder was introduced in Grizzly.
This allows one to run multiple cinder volume back-ends and create groups of these back-ends based off unique volume drivers. Cinder volume backends are spawned as children to cinder-volume. The filter scheduler determines where to send the volume based on the volume type thats passed in.
One can resize a running instance in OpenStack by running the following nova command:
nova resize --poll <server> <flavor>
The default behavior of this command is to invoke the nova scheduler to determine the best compute node for the resized instance. If there is only one compute node in the environment, the resize will fail.
A few months ago, we did a write up on the new PKI Token default introduced in Grizzly Keystone.
This described the new workflow for authentication and the fact that services no longer need to constantly validate tokens against Keystone - this can be done on the service endpoint with the help of security certificates.
How this really works has been bugging me for awhile since I was confused about the concepts of encoding/decoding/encrypting/decrypting. Let's walk through it.
Note: