Auto Provisioning Multi-Domain Setup

[Juan_Concepcion]

I am attempting to get auto scaling in an MDS environment working but on second CMA the tag does not get appended correctly to the Azure members.

Environment:

R80.10 MDS

Auto Scale set is setup for 2 members

Have this going to 1 CMA without issues. Defined a new controller for the second CMA, created new templates, added the templates to the new controllers, specified the domain for the controller and then kicked off the Azure Deployment - the new instances get associated to the correct domain but the tag is not correct.

In the working one I get:

{tags=managed-virtual-gateway|__once__|__generation__|__template__<name>-template}

In current I'm only getting:

{tags=managed-virtual-gateway}

Have tried to read documentation but where it's split across 2 sk's it's not very clear.

[PhoneBoy]

More of a CloudGuard (Formerly vSEC)‌ question, so it's moving there

This sounds like buggy behavior and may be worth a TAC case to investigate.

[Juan_Concepcion]

So what this turned out to be is that when you extract the autoprovision.tgz the absolute path was not used for the .tgz so instead of populating the proper locations it creates the directories in your local dir:

usr/bin/python

opt/CPsuite-R80/fw1/scripts/autoprovision/

opt/CPsuite-R80/fw1/scripts/autoprovision/version

opt/CPsuite-R80/fw1/scripts/autoprovision/aws.py

opt/CPsuite-R80/fw1/scripts/autoprovision/conf-cli.py

opt/CPsuite-R80/fw1/scripts/autoprovision/monitor.py

opt/CPsuite-R80/fw1/scripts/autoprovision/azure.py

opt/CPsuite-R80/fw1/scripts/autoprovision/merge-bundle.sh

opt/CPsuite-R80/fw1/scripts/autoprovision/gcp.py

opt/CPsuite-R80/fw1/bin/autoprov-cfg

opt/CPsuite-R80/fw1/scripts/protect.sh

var/opt/CPshrd-R80/conf/public-cloud/297.crt

etc/rc.d/init.d/autoprovision

--Juan

[PhoneBoy]

I think I made that mistake the first time I installed autoprovision.tgz too

[Juan_Concepcion]

Would be nice if the sk told you this ☺ (hint hint sk rewrite)

-Juan

[Juan_Concepcion]

So turns out i missed the / in the 'tar -xzvf <filename>.tgz /' -- user error

[PhoneBoy]

Yup, I made that same mistake

[Dori_Nachman]

On the Azure Autoscale SK it says:

Unpack the add-on package to the root partition ("/"):

[Expert@HostName:0]# cd /some_path_to_addon/
[Expert@HostName:0]# tar zxfC autoprovision-addon.tgz /

Note the trailing '/' at the end of the "tar" command.

If you have any better way to phrase this I'm open to hear suggestions.

[Juan_Concepcion]

I would say 1 of two solutions since in the instructions the user is automatically overwriting the files without backing them up first:

1. Create the tar file with the absolute pathname preserved, this removes the need for user to put in the “/” when extracting

2. Modify the instructions as such that users will not miss the note about the trailing “/”

Unpack the add-on package to the root partition ("/"):

# cd /some_path_to_addon/

# tar zxfC autoprovision-addon.tgz / <--Note the trailing '/' at the end of the "tar" command.

Regards,

Juan

[ramakrishnan]

Is this auto provision, where  we could see template and controllers, and which we using for Tag in internal load-balancer?