[Openstack-operators] vmware to openstack

Fox, Kevin M Kevin.Fox at pnnl.gov
Fri May 6 16:21:20 UTC 2016

There are a couple of reasons I think this may cause you problems even if it was technically feasible:

 * VMs deployed on vmware are built as pets and really need/benifit from the features of vmware. if migrating to anything but a vmware openstack cloud then those underlying expectations built into the vms no longer hold true and badness can ensue.
 * Users without experience in the cloud expect it to work the same way as regular vm's. Its very different. if you can "just move" a vm in, then it incorrectly strengthens the expectation. If users have to work a little bit to get it into the cloud, then there's opportunity for re-education on the differences and a chance to do the migration correctly, de-pet'ing the vm at migration time. If you don't do it at migration time, it tends not to happen at all, and as an operator, you then have  a sea of pets you end up having to deal with and not very many tools at your disposal to deal with them. :/

Yes, it seems like a good idea to help your users by transitioning automagically, but in the long run, it causes more pain then it saves.

From: Jonathan Proulx [jon at csail.mit.edu]
Sent: Friday, May 06, 2016 8:50 AM
To: Silence Dogood
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] vmware to openstack

On Fri, May 06, 2016 at 11:39:03AM -0400, Silence Dogood wrote:
:this strikes me as a really bad idea from a security standpoint... in fact
:it would violently violate like every audit / policy requirement I am aware

I come from a research environment with admittedly low thresholds for
this sort of thing (we don't do classified or medical stuff so no hard
regulations), but...

If the same entity controls the source cloud, translation layer, and
destination cloud where's the harm?

I can (maybe) see an issue if you're piping all you images through a
third part not involved in the source or target clouds. That's similar
to running on a public cloud trust wise so if you can trust a public
provider even that should be surmountable, but I don't think that's
the model suggested here.


:On Fri, May 6, 2016 at 11:32 AM, suresh kumar <boilingbabu at gmail.com> wrote:
:> Thanks Mariano, that really helps.
:> On Fri, May 6, 2016 at 11:16 AM, Mariano Cunietti <mcunietti at enter.it>
:> wrote:
:>> From: suresh kumar <boilingbabu at gmail.com>
:>> Date: Friday 6 May 2016 at 17:07
:>> To: "openstack-operators at lists.openstack.org" <
:>> openstack-operators at lists.openstack.org>
:>> Subject: [Openstack-operators] vmware to openstack
:>> I am working on a project to migrate vm's from vmware to openstack where
:>> am using tools to convert disk and later upload them to glance and spin
:>> instances are there any tools/scripts where I can migrate multiple vm's at
:>> a time.
:>> https://cloudbase.it/cloud-migration-as-a-service/
:> _______________________________________________
:> OpenStack-operators mailing list
:> OpenStack-operators at lists.openstack.org
:> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

:OpenStack-operators mailing list
:OpenStack-operators at lists.openstack.org


OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org

More information about the OpenStack-operators mailing list