You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Jorge Luiz Correa <jo...@embrapa.br.INVALID> on 2024/02/26 18:32:23 UTC
Re: How to create one network per project using as few public addresses as possible?
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?
For example, in Networks > Public IP addresses -> choose any isolated
network. I can see options like "Details, Firewall, Port forwarding, Load
balancing, VPN, Events, Comments".
When a tier is created its public IP is also listed in Networks > Public IP
addresses. But, when I click on the public IP address from the VPC the
options are only "Details, VPN".
How can I configure ingress options, as port forwarding? For example, I
need to forward ports 80 and 443 to a specific VM in some tier.
Thank you!
Em qua., 29 de nov. de 2023 às 14:50, Jorge Luiz Correa <
jorge.l.correa@embrapa.br> escreveu:
> 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 tests!
>
> :)
>
> Em qua., 29 de nov. de 2023 às 10:01, Gabriel Ortiga Fernandes <
> gabriel.ortiga@hotmail.com> escreveu:
>
>> 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
>> domain, thus, allowing all the projects to share a single VR.
>>
>> For now, this feature is not available in the GUI; however, you can
>> create a tier through the API 'createNetwork', informing both the projectId
>> and vpcId.
>>
>> This feature has been tested using accounts, but not projects, so I will
>> run some tests in the next few days and give you an answer regarding its
>> viability.
>>
>> Kind regards,
>>
>> GaOrtiga
>>
>> PS: This email will probably be a duplicate since I tried sending it
>> through a different provider, but it took too long, so I am sending this
>> again to save time.
>>
>
--
__________________________
Aviso de confidencialidade
Esta mensagem da
Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), empresa publica
federal regida pelo disposto na Lei Federal no. 5.851, de 7 de dezembro
de 1972, e enviada exclusivamente a seu destinatario e pode conter
informacoes confidenciais, protegidas por sigilo profissional. Sua
utilizacao desautorizada e ilegal e sujeita o infrator as penas da lei.
Se voce a recebeu indevidamente, queira, por gentileza, reenvia-la ao
emitente, esclarecendo o equivoco.
Confidentiality note
This message from
Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), a government
company established under Brazilian law (5.851/72), is directed
exclusively to its addressee and may contain confidential data,
protected under professional secrecy rules. Its unauthorized use is
illegal and may subject the transgressor to the law's penalties. If you
are not the addressee, please send it back, elucidating the failure.
Re: How to create one network per project using as few public addresses as possible?
Posted by Wei ZHOU <us...@gmail.com>.
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
<jo...@embrapa.br.invalid> wrote:
> 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?
>
> For example, in Networks > Public IP addresses -> choose any isolated
> network. I can see options like "Details, Firewall, Port forwarding, Load
> balancing, VPN, Events, Comments".
>
> When a tier is created its public IP is also listed in Networks > Public IP
> addresses. But, when I click on the public IP address from the VPC the
> options are only "Details, VPN".
>
> How can I configure ingress options, as port forwarding? For example, I
> need to forward ports 80 and 443 to a specific VM in some tier.
>
> Thank you!
>
>
> Em qua., 29 de nov. de 2023 às 14:50, Jorge Luiz Correa <
> jorge.l.correa@embrapa.br> escreveu:
>
> > 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 tests!
> >
> > :)
> >
> > Em qua., 29 de nov. de 2023 às 10:01, Gabriel Ortiga Fernandes <
> > gabriel.ortiga@hotmail.com> escreveu:
> >
> >> 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
> >> domain, thus, allowing all the projects to share a single VR.
> >>
> >> For now, this feature is not available in the GUI; however, you can
> >> create a tier through the API 'createNetwork', informing both the
> projectId
> >> and vpcId.
> >>
> >> This feature has been tested using accounts, but not projects, so I will
> >> run some tests in the next few days and give you an answer regarding its
> >> viability.
> >>
> >> Kind regards,
> >>
> >> GaOrtiga
> >>
> >> PS: This email will probably be a duplicate since I tried sending it
> >> through a different provider, but it took too long, so I am sending this
> >> again to save time.
> >>
> >
>
> --
> __________________________
> Aviso de confidencialidade
>
> Esta mensagem da
> Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), empresa publica
> federal regida pelo disposto na Lei Federal no. 5.851, de 7 de dezembro
> de 1972, e enviada exclusivamente a seu destinatario e pode conter
> informacoes confidenciais, protegidas por sigilo profissional. Sua
> utilizacao desautorizada e ilegal e sujeita o infrator as penas da lei.
> Se voce a recebeu indevidamente, queira, por gentileza, reenvia-la ao
> emitente, esclarecendo o equivoco.
>
> Confidentiality note
>
> This message from
> Empresa Brasileira de Pesquisa Agropecuaria (Embrapa), a government
> company established under Brazilian law (5.851/72), is directed
> exclusively to its addressee and may contain confidential data,
> protected under professional secrecy rules. Its unauthorized use is
> illegal and may subject the transgressor to the law's penalties. If you
> are not the addressee, please send it back, elucidating the failure.
>