Yes this might make sense. Currently you can use the project field in the image profile to add in an additional VLAN for vm's(only if it exists on the vmhost). The name should match the name of the vlan. This provides a 3rd network connection instead of either private/(protected or public).
Aaron On Fri, May 17, 2013 at 2:49 PM, Dmitri Chebotarov <[email protected]> wrote: > Hi > > Currently VM host profile defines two networks - Private (VM Network 0, > management) and Public (VM Network 1, user access). Both networks are > mandatory and each VM will always have these two networks. > > Would it make sense to move Public Network (VM Network 1) definition from VM > Host profile to Image profile? > Each VM would still have VM Network 0 (management), but in would be possible > to place an Image into a different access network (private/protected). > > > -- > Thank you, > > Dmitri Chebotarov > VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & > Messaging > 223 Aquia Building, Ffx, MSN: 1B5 > Phone: (703) 993-6175 | Fax: (703) 993-3404 > > > -- 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.
