Open Stack

I can speak to the networking bits...

In OpenStack, DHCP doesn't imply inconsistent IP addresses. If you boot a
VM without a specific IP address, it keeps the IP chosen for it until you
destroy the VM. If you boot a VM with a specific (static) IP address, DHCP
serves that IP to the VM. You can disable DHCP, but that tends to break the
IP metadata service and therefore requires implementing config drive. The
provider network scenarios in the networking guide assume use of config
drive.

You don't need to consider DVR unless you intend to use
private/internal/project networks (i.e., virtual networks that reside
completely within OpenStack) in addition to public/external/provider
networks and require higher performance and redundancy for
private-to-public and private-to-private network routing. If you intend to
use private networks, but only for internal communication between two or
more VMs on the same private network, you can easily augment the provider
networks scenario to support conventional private networks. Alternatively,
L3HA provides redundancy for private-to-public and private-to-private
network routing, but exchanges the performance increases of DVR for a
simpler architecture.

Also, if you plan to keep your virtual networking simple, did you consider
the Linux bridge agent?

On Tue, Dec 15, 2015 at 5:15 PM, Tyler Couto <tcouto at certain.com> wrote:

> Hi all,
>
> We are moving from vsphere to openstack. Currently I¹m trying to figure
> out the easiest way to move my vmdk files over. They are already
> integrated directly into our internal network.
>
> Option 1:
> Use provider networks (ie.
> http://docs.openstack.org/networking-guide/scenario_provider_ovs.html) for
> VMs with static ip addressing. This way I think I should be able to move
> the instances directly over, since they already have IP and MAC info.
>
> Option2:
> Use legacy (or DVR) architecture (ie.
> http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html),
> convert vmdks to qcow2s (?), remove ip, mac, uuid, other unique info,
> install acpi, install cloud-init, and boot.
>
> I would also like to avoid using the provider networks scenario with dhcp,
> because I want IPs to be consistent.
>
> Questions:
> Is it possible to use the provider network with static addressing?
> Is there a way to programatically modify images (vmdk or qcow2) with the
> steps described in number 2 above?
>
> Thanks,
> Tyler
>
> The opinions expressed herein are expressly my own and not necessarily the
> opinions of Certain, Inc.
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20151215/48707878/attachment.html>