IP Address/Port Group Management in View 4.6

[slaclair]

I'm sure this is going to come off as a stupid question; however, I am new to View and have been reading over the architecture & administration documents so I can get a handle on the product rather than haphazardly rolling it out.  I have been slightly confused on the management of IP addressing in the linked-clones within a pool.

For sake of argument I'll not have anything more available to me than a Class C address space (we'll call it 192.168.1.0/24  VLAN101) for the sake of discussion, so that immediately tells me that I will be limited to 255 machines in the pool at any given time (this is assuming you can release DHCP leases via a script upon refresh/recomposing).

I'm certain that there is something I have to be missing, but I'm going to create the master VM which will belong to the port group containing vlan101 and then all linked clone virtual machines will also be configured to use that same network and pull addresses via DHCP.  So my skewed logic is telling me that if I'm going to have a pool larger than 255 then there will have to be separate virtual machines pointing to different networks to created the linked clones off from?

I know this can't be correct and there is a feature I'm overlooking but I am open to any and all suggestions.

Thanks,

steve

[eeg3]

Here is one solution to the issue I believe you're referring to: http://myvirtualcloud.net/?p=1838

[slaclair]

I had actually stumbled upon that blog post this afternoon, it's a relief to know there wasn't an easy answer.

Currently the approach I'm thinking of is one master that has a cloned VM for each respective port group to be used.  The administrative overhead would be minimal compared to the other approach.  I'm just rather shocked this wasn't addressed in the architecture PDF.