This Article shows the configuration which needs to be added in the Versa-Headend for Titan 

Prerequisite : The Headend should be deployed (Master and Slave Versa-Director ,Versa-Analytics and Redundant Controllers ) 

Step1 :  Versa-Director should have the following configured

• AMQP (Add the Configuration of AMQP )

• Provider Org with the name VERSA, it is a default provider for versa shop. Please associate supported roles as well, include all tenant level orgs.

• Create a tenant org with the name GUEST org and please note not to enable VPN checkbox.

• Slave Controller will have peer as Master controller.
  1. While onboarding Master Controller, please select both staging and post staging enabled so workflow can build staging config as well on the controller and select sub Org as GUEST.
  2. Name should be controller-1 and controller-2

• Create a Master Template with Name: MASTERTENANT

• Create 4 service template with Name applications_MASTERTENANT, general_MASTERTENANT, nextgen-firewall_MASTERTENANT, class-of-service_MASTERTENANT

PLEASE NOTE : DON’T MAKE CHANGES IN THE NAME OF PROVIDER ORG,TENANTORG, CONTROLLER,AND TEMPLATES