You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Andrija Panic <an...@gmail.com> on 2020/10/08 10:39:26 UTC
Re: Using Multiple Public Networks
Rafael,
re your last email - this is only saying that CLoudStack Public network can
have either "a real public / publicly routable" IP address range, or some
other private Ip range - but both of those are, so to speak, external to
CloudStack - and whatever the IP (range) defined fort the cloudstack
"Public" network - those IP (be it really public or private) will be
attached to VR only.
Using Isolated network offering - has NOTHING to do with the "public"
network. The Isolated network is a network on VR's internal interfaces,
between the VR and VMs in that Isolated, while the CloudStack "public"
network is the network/IP of the external NIC (publicly facing NIC) of the
VR.
Let me know if you need more clarification
Best,
Re: Using Multiple Public Networks
Posted by Andrija Panic <an...@gmail.com>.
I believe that is true, Rafael.
There is a notion of TAGs that can be attached to various resources, but
I'm not sure that can be consumed in way you need it.
Best,
On Fri, 9 Oct 2020 at 09:12, Rafael del Valle <rv...@privaz.io.invalid>
wrote:
> Andrija,
>
> Thanks for the clarification. I found it confusing at first that "public"
> refers in reality to external to cloudstack, be it corporate intranet or
> public internet.
>
> I understand that know.
>
> What I am still trying to achieve is a way to differentiate/manage
> external IPs of the different types ACS can manage.
>
> I.e. My couldstack has now 3 different of external/public IPs.
> * Local fiber provider range which supports IPV4 only
>
> * IPs from an SDWan that also support IPV6
> * A local network that we call GuestAdmin, that administrators of ACS
> Projects can access via externally provided VPN fir the purpose. SSVMs are
> here.
> Each of them sets on a different VLAN.
>
> Now I have added all as Public, using different VLAN-IP-RANGE. And it is
> working just fine.
>
> The only drawback is that we need know what type of IP is each, as I
> cannot find a way to label, group or differentiate this IPs within ACS.
>
> I think ACS does not have any functionality yet to help with this use
> case, does it?
>
> Regarsds,
> Rafael
>
> On Thu, 2020-10-08 12:39 PM, Andrija Panic <an...@gmail.com>
> wrote:
> > Rafael,
> >
> > re your last email - this is only saying that CLoudStack Public network
> can
> > have either "a real public / publicly routable" IP address range, or some
> > other private Ip range - but both of those are, so to speak, external to
> > CloudStack - and whatever the IP (range) defined fort the cloudstack
> > "Public" network - those IP (be it really public or private) will be
> > attached to VR only.
> >
> > Using Isolated network offering - has NOTHING to do with the "public"
> > network. The Isolated network is a network on VR's internal interfaces,
> > between the VR and VMs in that Isolated, while the CloudStack "public"
> > network is the network/IP of the external NIC (publicly facing NIC) of
> the
> > VR.
> >
> > Let me know if you need more clarification
> >
> > Best,
> >
--
Andrija Panić
Re: Using Multiple Public Networks
Posted by Rafael del Valle <rv...@privaz.io.INVALID>.
Andrija,
Thanks for the clarification. I found it confusing at first that "public" refers in reality to external to cloudstack, be it corporate intranet or public internet.
I understand that know.
What I am still trying to achieve is a way to differentiate/manage external IPs of the different types ACS can manage.
I.e. My couldstack has now 3 different of external/public IPs.
* Local fiber provider range which supports IPV4 only
* IPs from an SDWan that also support IPV6
* A local network that we call GuestAdmin, that administrators of ACS Projects can access via externally provided VPN fir the purpose. SSVMs are here.
Each of them sets on a different VLAN.
Now I have added all as Public, using different VLAN-IP-RANGE. And it is working just fine.
The only drawback is that we need know what type of IP is each, as I cannot find a way to label, group or differentiate this IPs within ACS.
I think ACS does not have any functionality yet to help with this use case, does it?
Regarsds,
Rafael
On Thu, 2020-10-08 12:39 PM, Andrija Panic <an...@gmail.com> wrote:
> Rafael,
>
> re your last email - this is only saying that CLoudStack Public network can
> have either "a real public / publicly routable" IP address range, or some
> other private Ip range - but both of those are, so to speak, external to
> CloudStack - and whatever the IP (range) defined fort the cloudstack
> "Public" network - those IP (be it really public or private) will be
> attached to VR only.
>
> Using Isolated network offering - has NOTHING to do with the "public"
> network. The Isolated network is a network on VR's internal interfaces,
> between the VR and VMs in that Isolated, while the CloudStack "public"
> network is the network/IP of the external NIC (publicly facing NIC) of the
> VR.
>
> Let me know if you need more clarification
>
> Best,
>