Open Stack

Hi here!

I think this is of interest to a lot of people, in same scenario like us.
After reading and re-reading a lot (and good) openstack documentation,
wiki, scripts, demos, video, blog and a lot of days and weeks, IMO
openstack has very good resources, but openstack it's a very big and extend
product and those resources can't focus on all.... ... ... I thin next is a
common scenario.

We've need refinement concepts about in openstack infraestructure, if we're
moving from "traditional (KVM) VM infraestructure" to "Clouding Openstack
infraestructure". Please review and comment about this concepts to
refine/correct/tunne and get the right basics:

We're in an typical scenario with KVM traditional virtualization, with
working traditional VM instances. KVM host has two "need" interfaces
(public and private). The VM instances has two "need" interfaces too
(private and public) typical for working with webApps && Database
applications deploys.

Cloud image:
   - Cloud image == dynamic setup inyection to VM instance
   - Not is only VM instance fast SO setup.
   - By scripting let "encapsulate" functionality.
   - When launch it, Openstack injects variable configuration (vcpu, vram,
networking)
   - Instances launched, runs on ephemeral persistence, but you can persist
some setup on previous cloud image encapsulation or attach to nova-volume
resource.

Snapshot image:
   - snapshot image == static setup inside VM instance*(more or less,
because matization need: openstack injects vcpus, vram, continues setup
networking enviroment, continues maintain ephemeral resource, ... [????
some else???] )
   - Is used LIKE TRADITIONAL images to launch traditional VM instances.
   - [???] How to migrate and reflect old working VM traditional instances
Network??
        - [???] We can have old running VM with own networks typically
static public and private ip assigment, disabling DHCP on instance network
start.
          - [???] Private network range can reserved on openstack,
disabling DHCP can maintain setup
          - [???] Public network (it's routed by NAT from OpenStack)  BUT
you have not DHCP mapping to route !!!
        - [???] Alternative solutions && use cases

Please add and complete for refine concepts ...
Thx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121024/01458e38/attachment.html>