New pod creation using public ip

[arpanbht]

Hey guys, I have some questions related to new pod creation.

We already have a zone setup where we don't have any actual public ip, we are using the internal subnet created by the router as the public ip provider inside existing pod.

Here are the sample screenshots

Now we want to create another pod where we will provide actual public ip pool like 14.134.. like ips so when creating the pod with the actual public ip ranges and we will use the public ip gateway, we will create network inside the pod and in that we will get the actual public ip in the ip provider so that we can connect those public ips with the vms. Will this work?

[Ryan-AccuWeb-Cloud]

Hi there,

Yes, this should work. There are just a few important things to keep in mind when setting up the pod and public networking in CloudStack.

Here’s how I’d approach it:

1. Public IPs are configured at the Zone level, not directly on the pod.
   The pod is mainly responsible for the management network, including the management subnet and reserved IPs used by system VMs such as SSVMs and CPVMs.

2. For your setup, you would typically:

   • Create the new pod with its own management gateway and netmask (for example, using the 172.16.x.x range or another dedicated subnet).
   • Add the 14.134.x.x public IP range at the Zone level under Infrastructure → Zones → [Your Zone] → Physical Network → Public → Configure IP Ranges.
   • For an Advanced Zone, guest networks will use the configured guest CIDR, while public IPs can be associated with VMs through NAT/Static NAT.

3. One important point is the public IP gateway.
   The gateway for the 14.134.x.x range needs to be reachable from your CloudStack hosts. If the upstream network isn't already routing this range toward your CloudStack environment, you'll need to configure the upstream router accordingly. CloudStack also expects a single gateway per subnet, so it's worth planning the routing carefully.

4. If you're using VLANs for public traffic, make sure the appropriate VLAN is trunked to the CloudStack hosts and configured correctly in the physical network settings.

So, in short, the pod only needs the correct management network configuration. The 14.134.x.x public IP pool is configured at the Zone level and associated with the Public traffic type. Once the routing and network configuration are in place, your VMs should be able to acquire public IPs and use Static NAT to expose services externally.

If you're looking for a simpler way to get a CloudStack environment up and running, you can also take a look at [AccuWeb Cloud](https://accuweb.cloud).

And if you'd prefer to configure everything yourself, no problem — I’d be happy to assist you.

Best regards,
Ryan
AccuWeb Cloud | Cloud Infrastructure Support