Manual Chapter :
AS3 tenant name details
Applies To:
Show Versions
BIG-IQ Centralized Management
- 8.3.0, 8.2.0, 8.1.0, 8.0.0, 7.1.0, 7.0.0
AS3 tenant name details
When AS3 deploys an application service to a managed device, it deploys to the tenant partition specified in the AS3 template on which the application service is based. As part of the deployment process AS3 removes any objects previously existing in that target partition on the managed device.
For example, if you had manually deployed a number of virtual servers to a partition named
my-app-servers
on a BIG-IP named my.server.com
and then use AS3 to deploy an application service to that same partition and device, AS3 would remove the existing virtual servers and then deploy the application service. If you have deployed configuration objects to the devices that you plan to deploy AS3 application services, make sure the tenant names you specify are unique; that is, they don't match the names of any BIG-IP partitions to which you have deployed configuration objects. Best practice is to you select
Editable
for the tenant name, so you have the flexibility to revise the name when you use the template to deploy an application service.Another factor to consider when you specify the
Tenant
for a template is that BIG-IQ uses the both the application name and the tenant name as identifiers to organize the application services it deploys to your managed devices. You cannot deploy two application services with the same name to the same device if those services use the same tenant name. For example, consider the following work flow. - Create a template namedAs3Service1and name the tenantTenant1.
- Leave theEditablecheck box cleared.
- Use the template to deploy an application service namedAppservice1to a managed device nameddevice1.mynet.com
With these settings, you could not use
As3Service1
to deploy another application service named Appservice1
to device1.mynet.com
. If for some reason you did want to deploy two application services with the same name to the same device, you have two choices:
- Use a second template that uses a different tenant name.
- Use the same template, but make the tenant name editable. Then when you create the second application, specify a different tenant name.
