setup a cloudsatck on aws vpc (LEVEL 2 network issue and Primary Storage issue) #10056

bullblock · 2024-12-07T05:33:56Z

bullblock
Dec 7, 2024

Recently, I built a CloudStack env on AWS VPC. We all know that AWS VPC could be more friendly to Level 2 networks since it filters all Level 2 traffic. This means that if your IP or MAC address is not in the AWS VPC list, you cannot make it work.

My environment is for testing only, not production. I don't need to worry about the scale of the environment, so I created CloudStack using a BareMetal server. All CloudStack networks will be virtual networks inside BareMetal only, and the VPC will be the external network of CloudStack. The following is my solution:

Public network: The Internet
External network (AWS VPC): 10.0.0.224/27
AWS VPN Endpoint: 172.27.224.0/22 (for remote access into the VPC)
CloudStack Management: 192.168.2.0/24 (virtual)
CloudStack Public: 192.168.1.0/24 (virtual)
CloudStack Guest: 192.168.3.0/24 (virtual)
CloudStack Storage: 192.168.4.0/24 (virtual)
BareMetal physical eth0: enable SNAT and FORWARDING (iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE and net.ipv4.ip_forward=1 in /etc/sysctl.conf)
AWS VPC routing table: add a routing table 192.168.0.0/16 --> the BareMetal ENI to the VPC routing table.

Question 1:
The above solution works fine but cannot be extended to other BareMetal servers. Would you happen to have any better ideas?

Question 2:
In the above environment, I tried to create the Primary Storage using the AWS EFS (an AWS NFS service), but I had no luck!!! But I'm able to develop the Secondary Storage using the AWS EFS!!! How come? Is there anything special about the Primary Storage? Does it limit the IP range?