Improve the pattern-1 bosh-release and tile to work with PCF sandbox

[msmshariq]

Purpose

The previous resources related to pattern-1 bosh-release and pcf tile was developed and tested in pcf-dev environment. When testing these artifacts in an actual pcf environment, we noticed that there were many improvements required to get it to work. This PR improves the bosh-release and tile to work with an actual PCF deployment.

Goals

• Setup a two node API-M deployment configured with an Analytics node.
• Provide capability to point to an external MySQL db.
• Synchronize artifacts between API-M nodes via an NFS share.

Approach

• Provide the ability to point to an external database. Previously a mysql docker container was used as the database. This PR provided the capability to point to an external database by providing a custom form that allows users to enter database connection details that are then passed to the server. For testing purposes, p-mysql (Pivotal MySQL v1) was used.
• Configured the Cloud Foundry route_registrar component to expose the API-M Jaggery apps and the gateway externally. Two different hosts are used to expose the Jaggery apps and gateway. The route registrar component handles sticky sessions and route requests to the backend nodes in a round-robin manner.
• Used bosh links to link the API-M and Analytics nodes. By using links, we can identify the ip address of the linked bosh VM's, this IP's are used to configure the API-M analytics section.
• Create a bosh release to start up a NFS server. A NFS share is used to synchronize deployment artifacts between the two nodes. Since PCF doesn't provide an OOTB NFS server, an NFS server is created by installing the nfs-kernel-server package via apt-get. Also, nfs-common package is installed in the API-M vm's to mount the NFS share.