deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Fojtik <mfoj...@redhat.com>
Subject Re: VMWare vlan choice
Date Fri, 19 Oct 2012 09:08:26 GMT
On 10/18/2012 08:57 AM, Xavier Naveira wrote:
> Hi,
>
> Is there a JIRA ticket or something regarding this one so I can follow
> the status?

I just created one: https://issues.apache.org/jira/browse/DTACLOUD-348

I will start working on this next week, will update the status of this 
JIRA once I will have something for testing :-)

   -- Michal

>
> Thanks
>
> Xavier
>
> On 10/08/2012 11:08 AM, Michal Fojtik wrote:
>> On Oct 8, 2012, at 11:06 AM, Xavier Naveira
>> <xavier.naveira@ongame.com> wrote:
>>
>> Hi,
>>
>> Yes, this is exactly what I want :-) Thanks!
>>
>>    -- Michal
>>
>>> Hi,
>>>
>>> I think that what you want to do is to change something called the
>>> "Portgroup". Sorry I don't have a lot of info regarding this but one
>>> of the reasons I'm using deltacloud is avoiding digging in obscure
>>> perl scripts :)
>>>
>>> Anyway, here an example of what I would like to achieve:
>>>
>>> http://communities.vmware.com/message/840944#840944
>>>
>>> I hope it helps!
>>>
>>> Xavier
>>>
>>>
>>>
>>> On 10/08/2012 10:50 AM, Michal Fojtik wrote:
>>>> 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?
>>>>
>>>> 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,
>>>>>
>>>>> 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.
>>>>>
>>>>> 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.
>>>>>
>>>>> Xavier
>>>>>
>>>>>
>>>>> 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.
>>>>>>>
>>>>>>> I need to be able to create a number of machines in different
>>>>>>> vlans via
>>>>>>> deltacloud-vmware
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> The problem is that if the number of vlans is elevated the update
>>>>>>> and
>>>>>>> management of the templates becomes complicated.
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> 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.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> 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
?
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>> Michal Fojtik
>>>> http://deltacloud.org
>>>> mfojtik@redhat.com
>>>>
>>>>
>>>>
>>>
>>


-- 

Michal Fojtik <mfojtik@redhat.com>
Deltacloud API, CloudForms

Mime
View raw message