Ian, IMO CloudStack VR should not be managing any non CS vm. CloudStack is primarily orchestration layer. The current flow to achieve sharing of vLAN is to: 1) create Guest Network from CS, 2) Reserve a part of IP range in that network for non CS vm /physical device.(UI/updateNetwork API) 3) Manually assign static IPs to these non CloudStack devices. (These IP assignments are not stored in CS db)
VR should be able to route to these IPs. Have a look at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+IP+Range+Reservation+within+a+Network https://cwiki.apache.org/confluence/display/CLOUDSTACK/IP+Range+Reservation+within+a+Network+Test+Cases Thanks, Saksham -----Original Message----- From: Ian Service [mailto:iserv...@ts2.ca] Sent: Tuesday, December 03, 2013 9:35 PM To: users@cloudstack.apache.org Subject: Managing non-CS resources with the Virtual Router I read in the release for 4.2 that there was a way to manage devices that weren't VMs with the CloudStack Virtual router. This is something I've had to do manually so that VMs and real devices could share the same VLAN harmoniously but I'd really like to have it integrated in the VR config so that in the event it gets destroyed, it would rebuild those rules properly. So how can I add a Guest Network Range to an existing network (assuming API) and then how do I assign a device one of those IPs so that it's available form the CloudStack UI so that I can give it port forwards. Thanks, - Ian
