Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of kirkkosinski@gmail.com
 designates 209.85.210.47 as permitted sender)
Message-ID: <508A405F.3070701@gmail.com>
Date: Fri, 26 Oct 2012 00:48:47 -0700
From: Kirk Kosinski <kirkkosinski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.7) Gecko/20120920 Thunderbird/10.0.7
MIME-Version: 1.0
To: cloudstack-users@incubator.apache.org
Subject: Re: Private and Public pool of IP Addresses
References: 
 <CAAxZHdcTCrY9tRW=X0ZJ6=zGkmyCg9TrA+iVAo3xWGz0s9Pqew@mail.gmail.com>
In-Reply-To: 
 <CAAxZHdcTCrY9tRW=X0ZJ6=zGkmyCg9TrA+iVAo3xWGz0s9Pqew@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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,
>