Setting up and enabling multi-tier provisioning (LAMP large stack)

BMC Cloud Lifecycle Management lets you provision a large multi-tier LAMP stack (2xWeb servers, 1xPHP server, 1 mySQL server) with configurable load balancer and firewall (network path) entities. For example, you can use the single VM Compact Deployment but it requires additional configuration to enable the large LAMP stack deployment service to function. This topic describes the steps that enable multi-tier provisioning with configurable load balancer and firewall (network path) entities.

This topic contains the following information:

Requesting the CLM 4.0 Compact Deployment instance

Note

This section is visible to BMC employees only.

Open BDC.
Request the CLM 4.0 Compact Deployment session.
After it is provisioned, locate and remotely connect to the CLM4-mini-VC-d instance.
Before you can onboard the required network blueprint, add the load balancer and firewall nodes to the active HOU pod within BNA.
From within the CD-d instance, launch the Chrome (or IE/Firefox) browser and navigate to the BNA sign on screen.
Sign in sysadmin/clmAdm1n.

Adding load balancer and firewall nodes

Before you can onboard the required network blueprint, you must add the load balancer and firewall nodes to the active pod within BMC Network Automation.

Log on to BMC Network Automation.
Click the Network tab and select Pods from the navigation tree.
Select the magnifying glass icon to open the Pod configuration.
The configuration window appears.
Next to the Pod Node section, click Add Node.
Add a load balancer node.
You must add the following values:
Scroll down to the bottom of the window and click Save.
Return to the Pod Node section and add a firewall node.
You must add the following values:

You are now ready to onboard resources.

Onboarding resources

Log on to the BMC Cloud Lifecycle Management - Administration Console.
Click Workspaces and then click Resources.
In Resource Management, click Pods and then select the Import Network blueprint toolbar icon.
Select a container blueprint and then click Import.
Wait for the container blueprint to successfully complete the import cycle.

Now use the imported blueprint to create a new network container.
In Resource Management, navigate to the Network Containers section and click the Add Container toolbar icon.
Create a new container using the values provided exactly as they appear within the following screenshot.
You must add the following values. Specify the Tags and NAT Address Pool values correctly.
Click Next.
In the Create Network Container wizard, switch to Table View by selecting the top right icon.
Set Enabled to True to enable both the External and WEB2 networks.
Click the Load Balancers tab and enable both the DBVIP and WAVIP objects.
Click the Firewalls tab and enable both the DBVFW and WAVFW objects.
Click Next.
Click Submit.
Wait for the network container to successfully complete the creation process.
Depending on your environment, this could take some time.
Select the network container you just created and then select the Map Tenants toolbar icon.
Map the tenant (for example, Network Engineering) to this container and then click Save.
Wait for the Map Tenants to Network Container activity to successfully complete.
When you finish mapping the tenant, select the network container, and then select the Map Compute Pools icon.
Map the virtual clusters (for example, Silver and Gold), and then click Save.

You now can request the multi-tier large LAMP stack.

Requesting a multi-tier large LAMP stack from the Cloud User Portal

Log on to the Cloud Tenant Admin Console.
Request the service offering (for example, LAMP Large Web Application Platform) from the Service Catalog.
Provision the LAMP stack.
In this example, you are provisioning a multi-tier (2xWeb, 1xPHP, 1 mySQL) SOI.
Navigate the SOI to view and manipulate the Load Balancer and Firewall controls.
Any changes you make here are also reflected within BMC Network Automation.