Hi, Charles. This could be done on an "isolated" network in CloudStack, but you need to manually set up the mapping after the VM is created. You would configure a static NAT rule to essentially map a particular public IP on the CloudStack-managed virtual router to a specific VM on the private "guest" network behind the virtual router.
For "shared" networks in CloudStack, the VMs are not behind a virtual router and are essentially on your network, so you could configure CloudStack to assign public IPs directly to VMs. You would have to make sure your network could route the traffic. You could also configure CloudStack to assign private IPs and set up the NAT translation on your own, outside of CloudStack. Best regards, Kirk On 10/25/2012 11:45 PM, Charles Moulliard wrote: > Hi, > > Is it possible like with OpenStack - Essex to define public and private > pool of IP addresses. So when an new instance is created, it will receive a > public/private IP address. The public IP address could be used to access > this instance from outside of the host/guest. > > Regards, >
