Re: Regarding the VPC offering

[Harikrishna Patnala]

Hi Vivek,

For the default VPC offering, in the database I see both "InternalLbVM" and 
"VpcVirtualRouter" as the providers for the LB service. Though the list 
response in UI only shows "IntenalLbVM".  That is the reason you could create 
both internal and public LB tiers.

While creating a new VPC offering from UI we are providing only one option to 
select the provider. This could be a UI improvement to provide option to select 
multiple providers.

You can try API or Cloudmonkey to create a VPC offering with multiple 
providers. I gave it a quick try something like below.

(localcloud) 🐱 > create vpcoffering displaytext="test" name="test" 
supportedservices=Lb serviceProviderList[0].service=Lb 
serviceProviderList[0].provider=VpcVirtualRouter 
serviceProviderList[1].service=Lb serviceProviderList[1].provider=InternalLbVm


Hope this helps.

Thanks,
Harikrishna



From: Vivek Kumar 
Sent: Wednesday, June 29, 2022 5:28 PM
To: users@cloudstack.apache.org 
Subject: Regarding the VPC offering

Hello Folks,

ACS comes with a default VPC offering which has following service enabled -

Supported Services
Dhcp : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Vpn : VpcVirtualRouter
Dns : VpcVirtualRouter
SourceNat : VpcVirtualRouter
StaticNat : VpcVirtualRouter
UserData : VpcVirtualRouter


— So using the default offering I can create all three type of tiers - i.e 1) 
Public LB tier, 2) Internal LB Tier and 3) NoLB Tier.  Recently I have created 
a custom VPC offering with specific systemoffering_id, below are the services - 
which is identical to the default vpc offering -

Supported Services
Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

— But from this offering I am not able to create public LB tier - it says - 
Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC 
[75-Indiqus-4].  So I created a another vpc offering with Lb:VpcVirtualRouter , 
below are the services -

Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : VpcVirtualRouter
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

But in this VPC offering I am not able to create internal LB tiers - it says - 
Lb/InternalLbVm is not supported by VPC [VPC [54-Indiqus-test3]   So How come I 
am able to create all kind of Tiers with default vpc offering.





Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

+ 91 7503460090 
vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

 

Regarding the VPC offering

[Vivek Kumar]

Hello Folks, 

ACS comes with a default VPC offering which has following service enabled - 

Supported Services
Dhcp : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Vpn : VpcVirtualRouter
Dns : VpcVirtualRouter
SourceNat : VpcVirtualRouter
StaticNat : VpcVirtualRouter
UserData : VpcVirtualRouter


— So using the default offering I can create all three type of tiers - i.e 1) 
Public LB tier, 2) Internal LB Tier and 3) NoLB Tier.  Recently I have created 
a custom VPC offering with specific systemoffering_id, below are the services - 
which is identical to the default vpc offering - 

Supported Services
Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

— But from this offering I am not able to create public LB tier - it says - 
Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC 
[75-Indiqus-4].  So I created a another vpc offering with Lb:VpcVirtualRouter , 
below are the services - 

Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : VpcVirtualRouter
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

But in this VPC offering I am not able to create internal LB tiers - it says - 
Lb/InternalLbVm is not supported by VPC [VPC [54-Indiqus-test3]   So How come I 
am able to create all kind of Tiers with default vpc offering.  





Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

+ 91 7503460090 
vivek.ku...@indiqus.com 
www.indiqus.com 




-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.