Hi, Martin. CloudStack needs to know about the IP to be able to create a PF rule for it. One potential workaround I think might work would be to acquire a secondary IP for one of the VMs, use that for the virtual IP in your application, and configure the PF rule for it in CloudStack.
Best regards, Kirk On 12/05/2014 08:11 AM, Martin Emrich wrote: > Hi! > > I want to configure a port forwarding rule to a reserved IP (Which is > assigned as a virtual IP across several VMs). Using the Cloudstack load > balancer is not what I want, as it appears as the source of every request in > the application log files. > > I have excluded a range of reserved IPs from the Network as described in > http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/reserved-ip-addresses-non-csvms.html > (I use Cloudstack 4.4.1, but the documentation appears to be still valid). > > This IP is not "known" to Cloudstack, as it is not assigned to any VM. So I > cannot choose "a VM to forward to", but I need to enter the IP directly. Via > GUI this is not possible. > I tried it via Cloud Monkey: > >> create portforwardingrule ipaddressid=589d1160-5618-452f-a78c-dfd6dbec5fb9 >> networkid=1b3893a0-367b-4805-974b-72ae735680fa privateport=8088 >> privateendport=8088 publicport=18088 publicendport=18088 protocol=tcp >> vmguestip=192.168.101.10 > Missing arguments: virtualmachineid > > Faking it by adding some innocent VM's UUID obviously does not work: > >> create portforwardingrule ipaddressid=589d1160-5618-452f-a78c-dfd6dbec5fb9 >> networkid=1b3893a0-367b-4805-974b-72ae735680fa privateport=8088 >> privateendport=8088 publicport=18088 publicendport=18088 protocol=tcp >> vmguestip=192.168.101.10 >> virtualmachineid=b50e75ed-92ea-44cd-b7c2-f5ede5aa4c94 > Error: IP Address is not in the VM nic's network > > So I am stuck here... Any hint on how to make the port forwarding happen? > > Thanks, > > Martin > >
