Re: How to create one network per project using as few public addresses as possible?

2024-02-26 Thread Wei ZHOU
Unfortunately vpc source NAT IP cannot be used by any vpc tiers for any purposes (load balance or port FORWARDING, Static NAT). You need to acquire a new public IP. -Wei On Monday, February 26, 2024, Jorge Luiz Correa wrote: > Returning to this topic with the 4.19 release, I can create a

Re: How to create one network per project using as few public addresses as possible?

2024-02-26 Thread Jorge Luiz Correa
Returning to this topic with the 4.19 release, I can create a domain VPC and tiers in each project connected to this domain VPC. Each tier has its ACL rules. This is ok to filter Egress traffic, for example. But, I couldn't find a way to configure port forward in VPC (Ingress). Is there in GUI?

RE: Re: How to create one network per project using as few public addresses as possible?

2023-12-10 Thread Gabriel Ortiga Fernandes
Hello Jorge, I have run some tests on the tiers created for projects, such as acquiring IP addresses, deploying VMs and creating port forward and load balancer rules and it all seems to be working as intended. The only caveat is that, same as when creating the tier, some of these features

RE: How to create one network per project using as few public addresses as possible?

2023-12-10 Thread Gabriel Ortiga Fernandes
Hello Jorge, I have run some tests on the tiers created for projects, such as acquiring IP addresses, deploying VMs and creating port forward and load balancer rules and it all seems to be working as intended. The only caveat is that, same as when creating the tier, some of these features

Re: How to create one network per project using as few public addresses as possible?

2023-11-29 Thread Jorge Luiz Correa
Hi Gabriel! This is exactly what I was looking for. I couldn't find this request in github when looking for something. Thank you for sharing. No problem in creating through the API. So, I'll wait for the test results. If you could share with us, I would appreciate. And thank you so much for these

RE: How to create one network per project using as few public addresses as possible?

2023-11-29 Thread Gabriel Ortiga Fernandes
Hello Jorge, A soon as release 4.19 is launched, the feature of Domain VPCs(https://github.com/apache/cloudstack/pull/7153) will be available, which will allow users and operators to create tiers to VPCs for any account (or in your case project) to which the VPC owner has access, regardless of

Re: How to create one network per project using as few public addresses as possible?

2023-11-28 Thread Wei ZHOU
You can have a look at global setting max.project.public.ips If project has been created, you can update the project resource limitations. -Wei On Tuesday, 28 November 2023, Jorge Luiz Correa wrote: > We have a lot of research centers here. Each one is a domain in CloudStack > with its

How to create one network per project using as few public addresses as possible?

2023-11-28 Thread Jorge Luiz Correa
We have a lot of research centers here. Each one is a domain in CloudStack with its administrators. I would like each domain to use as few public IPs as possible and also use Projects to make management easier. For example, it would be ok if each domain had one virtual router with one public IP