Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Received-SPF: pass (nike.apache.org: domain of mfojtik@redhat.com designates
 209.132.183.28 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: VMWare vlan choice
From: Michal Fojtik <mfojtik@redhat.com>
In-Reply-To: <50726D18.6060806@ongame.com>
Date: Mon, 8 Oct 2012 10:50:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <06059512-227B-40FA-8CB2-6C4346BD85F8@redhat.com>
References: <506ECEAA.5060602@ongame.com>
 <1349470604.2994.8.camel@avon.watzmann.net> <50726D18.6060806@ongame.com>
To: dev@deltacloud.apache.org

On Oct 8, 2012, at 8:05 AM, Xavier Naveira <xavier.naveira@ongame.com> =
wrote:

Hi,

I'm looking into the VMWare documentation now for the CloneSpec[1]. Can =
you tell me what
argument you want to set specifically?=20

I guess you will need to pass something to CustomizationSpec -> =
CustomizationAdapterMapping ->
CustomizationIPSettings :-)

I think for now we can implement this as a 'feature' for vsphere driver =
and once we figure out
how to manage networks in VSphere properly, we can map it into the =
network models as
David mentioned.

  -- Michal

[1] =
http://www.vmware.com/support/developer/vc-sdk/visdk2xpubs/ReferenceGuide/=
vim.vm.CloneSpec.html


> Hi,
>=20
> In my case I only have one NIC connected to one VLAN per machine, it =
is a pretty simple configuration. The problem comes from the quantity of =
nodes and vlans, the tool I'm building is supposed to rapidly deploy a =
configuration set of 48 machines, every set is connected to its own =
VLAN, this is, those 48 machines are all connected to it, and we are =
planning to have, at least in the beginning, like 20-30 such sets at any =
given time, maybe more in the future. The number of templates I would =
need to create and maintain (if I choose to control the vlan the =
machines are connected to via having templates for them with that =
configuration) grows too much to be viable.
>=20
> For me, a simple extra parameter when cloning an image or an extra =
method that allows me to change the network on an instance should be =
fine.
>=20
> Xavier
>=20
>=20
> On 10/05/2012 10:56 PM, David Lutterkort wrote:
>> On Fri, 2012-10-05 at 14:12 +0200, Xavier Naveira wrote:
>>> I was suggested by marios on the irc channel to post my =
question/feature
>>> request here.
>>>=20
>>> I need to be able to create a number of machines in different vlans =
via
>>> deltacloud-vmware
>>>=20
>>> Until now what I've been doing is to have one VMWare template for =
every
>>> vlan and then creating machines on that vlan by cloning the
>>> corresponding template.
>>>=20
>>> The problem is that if the number of vlans is elevated the update =
and
>>> management of the templates becomes complicated.
>>>=20
>>> I would like to be able to specify the destination vlan of the clone
>>> instead so I would only need to have one template. Both specifying =
the
>>> vlan on instance creation or afterwards would work for me.
>>>=20
>>> Let me know if there is anything I can help you with regarding this
>>> question.
>> We've done something like this for EC2, where we list subnets in =
VPC's
>> as separate realms, and you can launch instance's into these subnets =
by
>> selecting the appropriate realm.
>>=20
>> I am not sure if this would be a good solution for vSphere; depends,
>> e.g. on how many vlans people typically have. We could of course also =
go
>> to managing networks explicitly and making 'network' an add'l =
parameter
>> for the create instance call.
>>=20
>> Do the VM's you launch into a vlan only have one NIC, or is it =
necessary
>> to talk about multiple NIC's and connect those to different vlans ?
>>=20
>> David
>>=20
>>=20
>=20

Michal Fojtik
http://deltacloud.org
mfojtik@redhat.com