You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Charles Moulliard <ch...@gmail.com> on 2012/10/26 08:45:19 UTC
Private and Public pool of IP Addresses
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,
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Private and Public pool of IP Addresses
Posted by Murali Reddy <Mu...@citrix.com>.
You could also have a basic zone with Elastic IP (EIP) service, where
CloudStack will allocate both public IP and private IP for the user VM's
and CloudStack orchestrates setting up 1:1 NAT between the public and
private IP of the user VM automatically.
On 26/10/12 1:20 PM, "Charles Moulliard" <ch...@gmail.com> wrote:
>Thanks for the response. Do we have somewhere some explanations on How to
>configure that ?
>
>On Fri, Oct 26, 2012 at 9:48 AM, Kirk Kosinski
><ki...@gmail.com>wrote:
>
>> 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,
>> >
>>
>
>
>
>--
>Charles Moulliard
>Apache Committer / Sr. Enterprise Architect (RedHat)
>Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>
Re: Private and Public pool of IP Addresses
Posted by Charles Moulliard <ch...@gmail.com>.
Thanks for the response. Do we have somewhere some explanations on How to
configure that ?
On Fri, Oct 26, 2012 at 9:48 AM, Kirk Kosinski <ki...@gmail.com>wrote:
> 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,
> >
>
--
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Private and Public pool of IP Addresses
Posted by Kirk Kosinski <ki...@gmail.com>.
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,
>