Since this thread is moved from a "how to" to a design I'm changing it
to the vcl-dev list.
These are some of the initial key questions which would need to be
My first pass would be to break this down into two problems to solve.
1) better handling of multiple networks already trunked to the vcl
infrastructure either through the hyerpvisor or a locally managed
2) dynamically creating/destroying vlans at provisioning time.
1 - is there, but is within the provisioning modules. Should it stay
in the prov modules or be generalized and called as a lower-level
function which can be accessed by all the prov. modules.? Here we
should define a direction we want to go in.
2- The harder one. Maybe not with a single hypervisor. But in the data
center and even across the public internet. Are there any projects out
there which are working on this? The issue comes down to how much
access would be granted to the upstream switches to create a vlan.
Some scope needs to be defined for this problem.
Those are just a couple of my thoughts. But I'm definitely not a networking guy.
Thoughts from others who might have strong network background?
On Mon, Aug 8, 2011 at 11:15 AM, Xianqing Yu <yu267155...@hotmail.com> wrote:
> I think it can be an interesting project. I start to think that I probably
> can add the vlan support to my kvm provisioning module (which we discussed
> in other emails in vcl-dev mail list.) From the designer prospective, could
> you talk about how this dynamical vlan should work? For example, what kinds
> of machines should be under the same vlan or different vlans? The machines
> under different vlans, should they still be able to connect to each other
> through public network? Should we create different vlans for both public
> network and private network? Where we should put the "create vlan function"?
> In provisioning module, or in higher level of VCL code?
> Xianqing Yu
> Graduate Research Assistant, Cyber Defense Lab
> Department of Computer Science
> North Carolina State University, Raleigh, NC
> E-mail: x...@ncsu.edu
> -----Original Message----- From: Aaron Peeler
> Sent: Monday, August 08, 2011 10:55 AM
> To: vcl-u...@incubator.apache.org
> Subject: Re: Reserve a cluster in VCL
> Yes, but with limitations. Also this is more related to your local
> networking setup and the individual provisioning modules.
> Today VCL does not dynamically create/destroy vlans when needed. I
> think this is needed in the long-term - at some solution at a
> localized level - i.e. within a DataCenter.
> To make it work in the current code - You would need to have the
> required vlans setup and preconfigured in your hypervisor, if using
> xcat in your ethernet switch modules(ESM).
> In the image table there is a column called project. At NCSU we use
> this project variable to define special vlans that have been trunked
> to the hypervisor or the ESM that the desired vcl image should be in.
> Within a provisioning module, one can use the project variable to
> define which network the vm should be a part of.
> Note - there is not a globally defined VCL method for handling the
> project variable. For example in the xcat module there is a routine
> called _assign2project. This routine simply calls out the a custom
> script (local to NCSU) to change the vlan assignments on the blade
> port within the related ESM.
> In the VMware/VMware.pm module it checks for and adds an existing
> network by the project name to the vm. But the network name has to be
> listed within the hypervisor. Look for $image_project in the
> It would be great for the community to start researching this and
> designing the code to handle dynamic vlans.
> On Mon, Aug 8, 2011 at 10:28 AM, Xianqing Yu <yu267155...@hotmail.com>
>> Hi Aaron,
>> It is great.
>> Could you say more about the network environment for the cluster? For
>> example, is that possible make the cluster have an isolated network
>> environment? That means, only machines in the cluster can communicate to
>> each other.
>> Xianqing Yu
>> Graduate Research Assistant, Cyber Defense Lab
>> Department of Computer Science
>> North Carolina State University, Raleigh, NC
>> E-mail: x...@ncsu.edu
>> -----Original Message----- From: Aaron Peeler
>> Sent: Friday, August 05, 2011 11:21 AM
>> To: vcl-u...@incubator.apache.org
>> Subject: Re: Reserve a cluster in VCL
>> Just created this page.
>> Let me know if you see any typos or if it doesn't make sense.
>> 2011/8/4 Xianqing Yu <yu267155...@hotmail.com>:
>>> Hi guys,
>>> Do you know how to reserve a cluster in VCL? What is the configuration of
>>> the cluster?
>>> Xianqing Yu
>>> Graduate Research Assistant, Cyber Defense Lab
>>> Department of Computer Science
>>> North Carolina State University, Raleigh, NC
>>> E-mail: x...@ncsu.edu
>> Aaron Peeler
>> Program Manager
>> Virtual Computing Lab
>> NC State University
>> All electronic mail messages in connection with State business which
>> are sent to or received by this account are subject to the NC Public
>> Records Law and may be disclosed to third parties.
> Aaron Peeler
> Program Manager
> Virtual Computing Lab
> NC State University
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.