Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment Guide

Transcription

1 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment Guide Dell EMC Engineering August 2018 A Dell EMC Deployment Guide

2 Revisions Date August 2017 August 2018 Description Initial release Updates for XC Core. The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright 2018 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. [8/27/2018] Dell EMC believes the information in this document is accurate as of its publication date. The information is subject to change without notice. 2 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

3 Table of contents Revisions... 2 Executive summary Introduction Audience Terms Infrastructure Prerequisites Assumptions Configuring VMware NSX for Pivotal Cloud Foundry Deploying logical switches in NSX Deploying NSX Edge devices Configuring NSX Edge appliances Configuring an NSX Edge firewall Configuring NSX Edge load balancer Configuring NSX Edge NAT/SNAT Deploying and configuring Operations Manager Deploying Operations Manager to vsphere Configuring Operations Manager Director for vsphere Deploying and configuring Elastic Runtime for vsphere Adding Elastic Runtime to Ops Manager Viewing all the VMs for Ops Manager Director or Elastic Runtime Creating new orgs, spaces, and user accounts Obtaining credentials cf CLI for orgs, spaces, and user accounts Obtaining and pushing apps to PCF Hello World Pushing Hello World Confirming Hello World is working Spring Music Assembling Spring Music Confirming Spring Music is working Intro to Apps Manager Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

4 7 Deploying and configuring Articulate app with Attendee-Service code connecting to MySQL 2.0 for PCF Deploying MySQL to PCF Attendee-Service Assembling and pushing Attendee-Service Articulate app Packaging and pushing Articulate app Confirming Articulate is working A Appendix A.1 Adding proxy to Git for Windows A.2 Adding proxy to manifest.yml A.3 Adding proxy to gradle.properties file A.4 Adding proxy to mvnw.cmd file B Technical support and resources C Related resources D Deployment Checklist Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

5 Executive summary Note: The information in this document applies to both Dell EMC XC Series Appliances, as well as the Dell EMC XC Core System offering. Sections or information that apply to only one of the offerings (XC Series or XC Core) will be called out explicitly. The Dell EMC XC Series Hyper-converged Appliance powered by Nutanix delivers a highly resilient, converged compute and storage platform that brings benefits of scalable architecture to business-critical enterprise applications. The XC Series platform is hypervisor agnostic and software installs quickly for deployment of multiple virtualized workloads. The XC Series platform uses the Nutanix Distributed Storage Fabric (DSF) which delivers a unified pool of storage from all appliances across the cluster, using techniques including striping, replication, auto-tiering, error detection, failover, and automatic recovery. The XC Series platform delivers storage through multiple protocols such as NFS, SMB, and iscsi. Pivotal Cloud Foundry (PCF) is a platform agnostic cloud computing platform that provides an on-demand and scalable solution that enables rapid application development and deployment. It is hosted on virtualized services on on-premises private infrastructure as well as in the cloud. The combined solution allows developers and dev-ops professionals to quickly deploy a modern application development platform on their on-premises infrastructure. The easy to use scaling functionality of the XC Series and PCF allows the developer to focus on the application as a unit of scale rather than the infrastructure or supporting services. This document provides the reference architecture for deploying a PCF production configuration onto Dell EMC XC Series hyper-converged appliances in a VMware vsphere environment. 5 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

6 1 Introduction This guide details the necessary steps to deploy and configure production level Pivotal Cloud Foundry (PCF) in a VMware vsphere environment on Dell EMC XC Series hyper-converged appliances. For more information, refer to the latest Pivotal guide located at Audience This document is intended for decision makers, managers, architects, cloud administrators, developers, and technical administrators of IT environments who want a solution guide that demonstrates how to deploy Pivotal Cloud Foundry (PCF) on Dell EMC XC Series Hyper-converged appliances in a VMware vsphere environment. This guide also goes into some details for creating orgs/spaces/users and pushing apps for multiple frameworks. You must be familiar with XC Series, Pivotal Cloud Foundry technologies, VMware vsphere technologies, VMware NSX and have a basic familiarity with storage, compute, and network technologies. Business and end-user readers of this document must be familiar with general IT, cloud technologies, and understand the relationship between their business, IT, and the application development requirements that are part of multiple business units. 1.2 Terms Useful terminology Term Nutanix Distributed Storage Fabric (DSF) Distributed VMware NSX Software-defined XC Series cluster PCF NAT/SNAT/DNAT Description DSF delivers a unified pool of storage from all appliances across the cluster, using techniques including striping, replication, auto-tiering, error detection, failover, and automatic recovery. Distributed means all data, metadata, and operations are distributed across the entire cluster. VMware NSX is a network virtualization and security platform. NSX enables the creation of entire networks in software and embeds them in the hypervisor layer. It s an abstraction from the underlying physical hardware. Software-defined delivers all services through software using proven Dell EMC hardware. XC Series cluster are a hyper-converged infrastructure solution that consolidates compute and storage into a single integrated appliance and creates a distributed virtual computing platform. Each appliance in the cluster runs an industry standard hypervisor and all the appliances work together to form a cluster which is scalable. Pivotal Cloud Foundry Network Address Translation occurs when one IP address in an IP header is changed. Source NAT is when the source IP is changed but 6 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

7 Term Description the destination IP stays the same. This allows multiple hosts on the inside to get any host on the outside. Destination NAT is when the destination IP is changed but the source IP stays the same. This allows any host on the outside to get to a single host on the inside. 1.3 Infrastructure The infrastructure for Pivotal Cloud Foundry (PCF) on VMware vsphere in a production level configuration using XC Series Hyper-converged appliances is defined in the Production Pivotal Cloud Foundry on Dell EMC XC Series Hyper-converged Appliances - Reference Architecture document. This guide assumes you have read that document prior to doing this deployment. 1.4 Prerequisites There are several prerequisites that must be in place before starting the PCF install. Review the prerequisites for installing PCF on vsphere under vsphere Requirements. In addition, we have included a Deployment Checklist for information you will need throughout this deployment. Before you begin, fill out what you can of the Checklist at the end of document and complete the following list of prerequisites. Note: This deployment assumes you have read and understood the Dell EMC XC Series Pivotal Cloud Foundry Reference Architecture document and that you have successfully deployed three XC Series clusters, NSX Manager, and three NSX controllers with vsphere. Prerequisites for setting up PCF Prerequisite Routable IPs Load balancer considerations Definition Pivotal recommends 10 consecutive routable IPs be applied to the NSX Edge. One reserved for NSX use (Controller to Edge). Deployment Checklist item #1. One for NSX Load Balancer to GoRouters. Deployment Checklist item #2. One for NSX Load Balancer to Diego Brains for SSH to apps. Deployment Checklist item #3. One routable IP used to access the Ops Manager frontend. Deployment Checklist item #4. One routable IP for use with SNAT egress. Deployment Checklist item #5. Five for future use. Deployment Checklist item #6. We used a VMware NSX for load balancer. Pivotal recommends that NSX Edge Appliances are deployed as high availability pairs and sized large or greater. 7 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

8 Prerequisite Trusted certificate matching fully qualified hostname of NSX Manager. Definition Ops Manager Director deployment requires that the certificate applied to NSX Manager matches the fully qualified hostname of NSX Manager. Network Time Protocol (NTP) Necessary for timesync. Deployment Checklist item #15. Create two (2) wildcard DNS entries DNS A record for Ops Manager hostname Set up an SMTP server (recommended) Pivotal Network Account These should be in the format of: *.apps.yourdomain.yourtopleveldomain *.system.yourdomain.yourtopleveldomain Both should point to the routable IP for your load balancer/gorouter. Deployment Checklist item #2. Host (A) record should be registered for Ops Manager before beginning the Ops Manager deployment in section 3. Deployment Checklist item #7. Use an SMTP server for notifications. Deployment Checklist item #16. Account to log in and download products from Pivotal Network. Deployment Checklist item #23. Use your corporate security recommendations to manage your credentials. In addition to being a common practice, Dell EMC recommends creating a VM for all of the tools required in this environment. You must join this VM to the same domain and it is where you will do most of your management of the XC clusters and Pivotal Cloud Foundry. We created a Windows VM with the apps below. There may also be versions of these or similar apps for other platforms, such as Linux. Table 3 shows a list of suggested apps to install and links to where you can download them. List of suggested apps to install Tool VMware vsphere Web Client and/or regular vsphere Client cf CLI Notepad++ Git for Windows Putty WinSCP Definition Web-based client that connects to vcenter to manage an ESXi environment. Comes with VMware vcenter. Cloud Foundry command line interface. Text editor that supports tabbed editing. Lightweight set of GIT tools for use inside Windows. Versatile tool for connecting to other machines or services. SFTP/FTP Windows Secure Copy tool. 8 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

9 1.5 Assumptions The reader has read and understood the Dell EMC XC Series Pivotal Cloud Foundry Reference Architecture document. See Dell EMC Tech Center at The reader has working knowledge to deploy, manage, and update Dell EMC XC Series clusters. For additional documentation, see the Dell.com/XCseriesmanuals page. The Dell EMC XC Series clusters have been deployed and updated to the latest firmware and drivers. For the latest drivers and firmware visit the Dell EMC XC Series product support page. VMware NSX Manager and Controllers are deployed. Requires VMware vsphere 5.5 or greater. NSX 6.1.x or greater for PCF. And will be installing PCF 1.6 or greater. 9 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

10 2 Configuring VMware NSX for Pivotal Cloud Foundry VMware NSX enables the creation of networks in software and embeds them in the hypervisor layer. In this implementation, it provides firewall, load balancing, and NAT/SNAT services for Pivotal Cloud Foundry on vsphere. These are not all encompassing settings, but rather a working base to start from. Additional configuration may be necessary in other environments. NSX is installed in our production environment. More information about the NSX below is found in the NSX Edge Cookbook for Pivotal Cloud Foundry on vsphere. All of these steps were performed using the VMware vsphere Web Client and following the NSX Cookbook as closely as possible. We wanted to show how to successfully configure NSX for Pivotal Cloud Foundry, using our example environment. We show you where to write the data using your own information in the provided Deployment Checklist found in this document. 2.1 Deploying logical switches in NSX First, we created four logical switches. These were assigned on the internal interface of the NSX Edge as follows: /26 = PCF Deployment Network, also called the PCF Infrastructure Network /22 = Deployment Network for Elastic Runtime Tile /22 = CF Tiles Network for all Tiles besides ERT /22 = Dynamic Services Network for BOSH Director-managed service tiles Note: Pivotal Cloud Foundry on vsphere Reference Architecture shows an additional network called IsoZone##. The NSX Cookbook does not reference this network, so this document does not deploy the IsoZone network. If you would like to, that would require some additional configuration including another Logical Switch in VMware NSX. The internal gateway for each network should be set to the.1 IP address in each of the above networks. In our example, the PCF deployment network internal gateway would be Add these IPs to the Deployment Checklist item #s 12A-12D. You need to pre-assign one IP in the PCF Deployment Network for Ops Manager. Write this IP in Deployment Checklist item #8. You need to pre-assign eight IPs in the Deployment Network for Elastic Runtime Tile because, by default, PCF deploys: Three GoRouters Three Diego Brains Two ERT-MySQL-Proxies Write three IPs in Deployment Checklist item #9A-9C for the GoRouters. Write three IPs in Deployment Checklist item #10A-10C for the Diego Brains. Write two IPs in the Deployment Checklist item #11A-11B for the ERT-MySQL-Proxies. 10 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

11 1. In VMware vsphere Web Client, click Networking & Security. 2. Click Logical Switches and then click the green Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

12 3. On the Edit screen, do the following: a. In the Name box, type the first switch name. In our example, we used Infrastructure_ /26. b. In our example, the description is PCF Deployment Network. c. Unicast and Enable IP Discovery are already selected by default. 4. Click OK. 12 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

13 5. Click the green + again to create the next logical switch. 6. In the Name box, type the next switch name. In our example, we used Deployment_ /22 with description of Deployment Network for Elastic Runtime Tile. Again, Unicast and Enable IP Discovery are selected by default. 7. Click OK. 13 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

14 8. Click the green + again to create the next logical switch. In our example, we used CF_Tiles_ /22 with description of CF Tiles Network for all Tiles besides ERT. 9. Click OK. 14 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

15 10. Click the green + one more time to create the last logical switch. In our example, we used Services_ /22 with description of Dynamic Services network for BOSH Directormanaged service tiles. 11. Click OK. View the logical switches on the Logical Switches screen. After these Logical Switches were deployed, we obtained the VirtualWire names. 15 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

16 12. In VMware vsphere Web Client, click Home > Networking. 13. The name of each virtual wire is available in the left pane, or for the one that is highlighted the names are also in the right pane. Write down all four of these beside the correct network in the Deployment Checklist. (Item #s 13A-13D). Our examples are displayed in the image here. 16 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

17 2.2 Deploying NSX Edge devices 1. In the left pane, click NSX Edges and then click on the green Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

18 2. On the New NSX Edge screen, do the following: a. Next to Install Type, select Edge Services Gateway. b. In the Name box, give it a name. In our example, we used PCF_Edge. c. Select the boxes to Deploy NSX Edge and Enable High Availability. d. Click Next. 18 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

19 3. On the Settings screen, do the following: a. Add a username and password. Write down your username and password in the Deployment Checklist item #26. b. Enable auto rule generation is selected by default. c. Click Next. 19 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

20 4. On the Configure deployment screen, do the following: a. In the Datacenter drop-down list, select your datacenter b. Next to Appliance Size, select Large or greater. c. To add an Edge appliance, click the green Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

21 5. In the Add NSX Edge Appliance dialog, select your Cluster Resource Pool and Datastore. 6. Click OK. 7. Click Next. 21 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

22 8. To add the first interface, on the Configure interfaces screen, click the green Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

23 9. On the Add NSX Edge Interface screen, do the following: a. The first interface is for the External Uplink. In the Name box, give it a name. In our example, we used External Uplink. b. For Type, click Uplink c. Click the green + to add the reserved external IP for the Edge (Deployment Checklist item #1) under Primary IP Address and then add the Subnet Prefix Length. d. Click Select. 23 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

24 10. On the Connect NSX Edge to a Network dialog box, click Distributed Portgroup, select your port group, and then click OK. 24 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

25 11. Under Secondary IP Addresses, add the nine other external IPs that were reserved for the NSX Edge (Deployment Checklist items #2-6). 12. Click OK. 25 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

26 14. Back on the Configure Interfaces screen (seen in step 8 above), click the green + to add another interface. This one will be named Infrastructure. Select Internal for Type. Click Select and on the Logical Switch tab, select the Infrastructure_ /26 switch. Click OK. 26 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

27 15. Click the green + and add the first IP of the network range in the Connected To field as the Primary IP Address ( or Deployment Checklist item #12A). Then add the Subnet Prefix Length (26). This adds that IP to the inside port of the Edge. Click OK. 16. Back on the Configure Interfaces page (seen in step 8 above), click the green + to add another interface. This one will be named Deployment. Select Internal for Type. Click Select and on the Logical Switch tab, select the Deployment_ /22 switch. Click OK. 27 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

28 17. Click the green + and add the first IP of the network range in the Connected To field as the Primary IP Address ( or Deployment Checklist item #12B). Then add the Subnet Prefix Length (22). This adds that IP to the inside port of the Edge. Click OK. 28 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

29 18. Back on the Configure Interfaces page (seen in step 8 above), click the green + to add another interface. This one will be named CF_Tiles. Select Internal for Type. Click Select and on the Logical Switch tab, select the CF_Tiles_ /22 switch. Click OK. 29 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

30 19. Click the green + and add the first IP of the network range in the Connected To field as the Primary IP Address ( or Deployment Checklist item #12C). Then add the Subnet Prefix Length (22). This adds that IP to the inside port of the Edge. Click OK. 30 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

31 20. Back on the Configure Interfaces page (seen in step 8 above), click the green + to add another interface. This one will be named Services. Select Internal for Type. Click Select and on the Logical Switch tab, select the Services_Tiles_ /22 switch. Click OK. 21. Click the green + and add the first IP of the network range in the Connected To field as the Primary IP Address ( or Deployment Checklist item #12D). Then add the Subnet Prefix Length 31 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

32 (22). This adds that IP to the inside port of the Edge. Click OK. 22. Back on the Configure interfaces screen, you will see all 5 interfaces configured. The first is the External Uplink and the other four are the internal networks that will be used by various components of PCF. Click Next. 32 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

33 23. On the Default gateway setting screen, do the following: a. Select Configure Default Gateway. b. In the vnic drop-down list, select External Uplink c. In the Gateway IP box, set your external Gateway IP. d. Click Next. 24. On the Firewall and HA screen, do the following: a. You can either Configure the Firewall default policy now or later. b. Under Configure HA parameters, in the vnic drop-down list, select any. c. Click Next. 25. On the Ready to complete page, review the summary and click Finish. This deploys two NSX Edge appliances to the cluster you chose. After the Edge appliances are deployed, if you choose, you can live migrate one of them to another XC cluster in the same vsphere Datacenter. 33 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

34 2.3 Configuring NSX Edge appliances Next, we need to configure the Edge Appliances for firewall, load balancing, and NAT/SNAT Configuring an NSX Edge firewall 1. If not already there, click on NSX Edge in the left column and then double click on the new Edge appliance in the middle pane. In our example, it is called edge Select the Manage tab and then click Firewall. You should see the default rules that were already built. 34 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

35 3. Click the green + to add a new rule. 4. The rules that need to be added come from the NSX Cookbook under Step 1: Configure Firewall. The first rule to add will be Allow Ingress -> Ops Manager. Type that in the Name field. Under the Destination column, click the small IP button to bring up the next window. 5. In Destination IP Address dialog box, type in the reserved external IP for Ops Manager (Deployment Checklist item #4). 6. Click OK. 35 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

36 7. Back on the Firewall configuration, on the same rule under the Service column, click the small pencil icon. 8. On the Specify Service dialog box, do the following: a. In the Object Type drop-down list, select Service. b. In the Available Objects list, find the three services for this rule (SSH, HTTPS, HTTP) and use the right arrow to add them to the Selected Objects box. c. Click OK. 36 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

37 9. After you have followed the same pattern for all the rest of the rules listed in the NSX Cookbook, your Firewall rules page will look similar to the image above. Click the Publish Changes button to make the rules active Configuring NSX Edge load balancer Next, we will setup the load balancer. We have chosen to pass SSL termination through the load balancer directly to the GoRouters. Note: For details about the different SSL/TLS termination point options, how they correspond to different points-of-entry for Elastic Runtime, and related certificate requirements, see Providing a Certificate for Your SSL/TLS Termination Point. If you do not want to pass SSL termination to the GoRouters, follow Step 2.1 through Step 2.3 in the NSX Cookbook and then skip to step 11 below. 37 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

38 1. In the VMware vsphere Web Client, click Load Balancer > Global Configuration. 2. Click Edit. 3. On the Edit Load balancer global configuration screen, select Enable the Load Balancer, Acceleration, and Logging. Set Log Level to the desired level. In our example, we selected Warning. 4. Click OK. 38 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

39 5. On the Manage > Application Profiles screen click the green + to add a new profile. We will be adding three application profiles. 6. On the New Profile screen, the first profile will be named PCF-HTTP. Set the Type to HTTP and select Insert X-Forwarded-For HTTP header. 7. Click OK. 39 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

40 8. Click the green + again to add another Application Profile. This one will be named PCF-HTTPS. Set the Type to HTTPS. We enabled SSL Passthrough for our environment because we are passing SSL termination to the GoRouters. 40 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

41 9. Click the green + again to add another Application Profile. This one will be named PCF-TCP. Set the Type to TCP and then click OK. 41 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

42 10. You should have three application profiles similar to the above image. 11. Select Manage tab >Application Rules. We will add three rules. Click the green + to add the first rule. 42 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

43 12. On the Add Application Rule dialog box, the first rule is named Option httplog and the script is option httplog. Click OK. 13. Create two more rules using these names and scripts: Rule names and scripts Name Reqadd X-Forwarded-Proto:\ https Reqadd X-Forwarded-Proto:\ http Script Reqadd X-Forwarded-Proto:\ https Reqadd X-Forwarded-Proto:\ http Completed application rules displayed. 43 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

44 14. Next step is to create monitors for pools. In the left pane, click Service Monitoring. Click the green + to add a monitor. The three monitors seen in the image above are created by default. 15. The first monitor will be named http-routers. Set the Type to HTTP, Method to GET, and set the URL to /health. 16. Click OK. 44 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

45 17. Back on the Service Monitoring screen, click the green + again to create the second monitor. This one will be named diego-brains. Set the Type to TCP. 18. Click OK. 19. Back on the Service Monitoring screen, click the green + again to create the third monitor. This one will be named ert-mysql-proxy. Set the Type to TCP. 20. Click OK. 45 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

46 Service Monitoring screen with the three new monitors added. Now we need to create pools for multiple-element PCF targets. These are the pools of resources to which the NSX Edge will be load balancing, which are the GoRouters, Diego Brain, and ERT MySQL Proxy jobs deployed by BOSH Director. 21. In the left pane, click Pools, and then click the green + to add a pool. We will add three pools. 46 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

47 22. The first pool will be named http-routers. Set the Description to GoRouters. Algorithm should be Round-Robin and Monitors should be set to http-routers. Click the green + to add a new member. On the New Member dialog box, set the following: a. Name GoRouter#. b. IP Address: Reserved internal IP for GoRouter# (Deployment Checklist item #9A). c. State: Enable. d. Port: 443, because we will be passing all traffic to https websites. e. Monitor Port: f. Click OK. 47 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

48 23. Click the green + again and add GoRouter2 with its assigned internal IP (Deployment Checklist item #9B). Continue this process until you have all of your GoRouters added. We have three, which you can see in the above image. 24. Click OK. 25. Back on the Edit Pool screen, click the green + again to add the second pool. This one will be named diego-brains. Algorithm should be ROUND-ROBIN. Monitors should be diego-brains. Click the green 48 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

49 + to add new members. For example, we have three diego brains to add as seen in the above image. Each one will be set as follows: a. Name: diego-brain#. b. IP Address: Reserved internal IP for diego-brain# (Deployment Checklist item #10A). c. Port: d. Monitor Port: e. Click OK. f. Repeat this process until you add all of your diego-brains. g. Click OK on the Pool screen after all three members have been added. 26. Back on the Edit Pool screen, click the green + again to add the last pool. This one will be named ertmysql-proxy. Algorithm should be Round-Robin. Monitors should be ert-mysql-proxy. Click the green + to add new members. We have two ert-mysql-proxies to add as seen in the above image. Each one will be set as follows: a. Name: ert-mysql-proxy#. b. IP Address: internal IP for ert-mysql-proxy# (Deployment Checklist item #11A). c. Port: d. Monitor Port: e. Click OK. f. Repeat this process until you add all of your ert-mysql-proxies. g. Click OK on the Edit Pool screen after all three members have been added. 49 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

50 The Pools screen with three pools added. See the members for the highlighted pool at the bottom of the screen. 27. Next we add virtual servers. In the left pane, click Virtual Servers and then click the green + to add the first virtual server. 50 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

51 28. The first Virtual Server will need the following settings: a. Enable the Virtual Server. b. Application Profile: PCF-TCP. c. Name: mysql-lbr. d. IP Address: inside router IP for Elastic Runtime Tile (Checklist item #12B). e. Protocol: TCP. f. Port: g. Default Pool: ert-mysql-proxy. h. Click OK. 51 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

52 29. In the New Virtual Server dialog box, add another virtual server with the following settings: a. Select Enable Virtual Server. b. Application Profile: PCF-HTTPS. c. Name: GoRtr-HTTPS. d. IP Address: external reserved IP for the GoRouter (Deployment Checklist item #2). e. Protocol: HTTPS. f. Port: 443. g. Default Pool: http-routers. h. Click the Advanced tab. 52 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

53 30. On the Advanced tab, click the green + to add Rules. Select both the option httplog rule and the reqadd X-Forwarded-Proto:\ https rule. 31. Click OK twice to get out of the New Virtual Server window. 32. In the New Virtual Server dialog box, add the last virtual server with the following settings: a. Enable the Virtual Server. 53 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

54 b. Application Profile: PCF-HTTPS. c. Name: SSH-DiegoBrains. d. IP Address: external reserved IP for the Diego Brain (Deployment Checklist item #3). e. Protocol: TCP. f. Port: g. Default Pool: diego-brains. h. Click OK. Screen view after adding all three virtual servers. 54 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

55 2.3.3 Configuring NSX Edge NAT/SNAT Last in the configuration of the NSX Edge is configuring NAT/SNAT. 1. At the top of the screen, click NAT. The three rules seen in the above image are created by default. We will add two rules. When you click on the green + to add each one, you will also have to choose whether the rule will be DNAT or SNAT. 55 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

56 2. The first rule will be a DNAT rule with the following settings: a. Applied On: External Uplink. b. Protocol: tcp. c. Original Destination IP: external reserved IP for Ops Manager (Deployment Checklist item #4). d. Original Destination Port: any. e. Translated IP: internal reserved IP for Ops Manager (Deployment Checklist item #8). f. Translated Port: any. g. Description: Ops Manager. h. Ensure the rule is Enabled. i. Click OK. 56 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

57 3. The second rule will be an SNAT rule with the following settings: a. Applied On: External Uplink. b. Protocol: any. c. Original Source IP: the entire inside CIDR range /16. d. Translated Source IP: external reserved IP for the GoRouter (Deployment Checklist item #2). e. Description: SNAT for /16. f. Ensure the rule is Enabled. g. Click OK. NAT rules page after adding two additional rules. 57 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

58 4. Click Publish Changes to make all rules active. This concludes our configuration of VMware NSX Edge Appliances in preparation for deploying Pivotal Cloud Foundry. 58 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

59 3 Deploying and configuring Operations Manager This section describes how to deploy and configure Operations Manager and Operations Manager Director. Operations Manager for Pivotal Cloud Foundry (PCF) provides a graphical interface to manage the deployment and upgrade of PCF components like Elastic Runtime, additional services and partner products. 3.1 Deploying Operations Manager to vsphere For more information, go to the Pivotal page for Deploying Operations Manager to vsphere. 1. Navigate to the Pivotal Cloud Foundry Ops Manager for vsphere page to download the latest version or use the drop-down list to select a previous version. You must have a Pivotal account and must log in before you can download (Deployment Checklist item #23). 2. Select the latest Ops Manager release. Version was used for this guide. We will be using the regular vsphere Client to deploy the OVF template due to a current issue with browsers using the 59 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

60 vsphere Web Client. 3. In vsphere Client, select VMs and Templates. 4. Write down the name of your DataCenter in the Deployment Checklist, item # Right click your datacenter, and then select New Folder. 6. Name the folder pivotal_cf, and then press OK. 7. Select the new pivotal_cf folder to highlight it, and then click File > Deploy OVF Template. 60 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

61 8. In the Source screen, browse to and select the Pivotal Cloud Foundry Ops Manager for vsphere.ova file that you downloaded and click Next. 9. In the Details page, review the details page and click Next. 61 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

62 10. In the Name and Location page, name the VM and select the pivotal_cf folder you created earlier and then click Next. 11. In the Host / Cluster page, select your XC cluster where you want the Ops Manager VM to initially live. Write down all of the cluster names in the Deployment Checklist, item #19. Then click Next. 62 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

63 12. On the Storage page, select the storage container where the Ops Manager VM will live, which should have a minimum of 2 TB available. Be careful to not select any of the CVM storage containers (start with NTNX by default). We chose the Default-Container for this deployment. 63 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

64 13. In the Disk Format page, select a virtual disk format. Click Next. Note: For more information about formats, go to Provisioning a Virtual Disk. 64 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

65 14. In the Network Mapping page, select a destination network. This should be the PCF Deployment Network Logical Switch created in NSX. Deployment Checklist item #13A. Click Next. 65 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

66 15. In the Properties page, do the following: a. Type in the network info for Ops Manager. This should be in the PCF Deployment network range. i. IP Address: Deployment Checklist item #8. ii. Netmask: If following the NSX cookbook and instructions in this guide, this will be because of the /26 network. iii. Gateway: Deployment Checklist item #12A. iv. DNS: Deployment Checklist item #14. v. NTP: Deployment Checklist item #15. vi. Admin Password: Used for SSH. The username is always Ubuntu and is entered for you on the Deployment Checklist item #27. vii. Custom Hostname for Ops Manager. 16. Click Next. 66 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

67 17. In the Ready to complete screen, review information. Select the Power on after deployment check box. 18. Click Finish. This deploys the Ops Manager VM to the pivotal_cf folder you created under your cluster. 3.2 Configuring Operations Manager Director for vsphere For more information, go to Configuring Operations Manager Director for vsphere. Any field with a red asterisk (*) is mandatory. For more information about configuration options, see the online Pivotal Documentation. The following steps cover the mandatory options and what Dell EMC set for a successful deployment. 67 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

68 1. In a browser, navigate to the fully qualified domain name (registered in DNS) or external IP of your new Ops Manager. For the IP address see Deployment Checklist item #4. 2. The first time you start Ops Manager, you must select one of the following. You can find more information from the provided Pivotal links. Use an Identity Provider, such as an external server that maintains your user database. Internal Authentication, PCF maintains your user database. We use this option for this guide. Important: The internal security module used by Ops Manager remembers the IP or hostname of this visit and always redirects to it. If you select this option, you must maintain this current IP or hostname to avoid authentication issues in the future. Pivotal recommends an FQDN. 68 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

69 3. In the Internal Authentication dialog box, complete the following steps: a. Enter a Username, Password, and Password Confirmation. Write this into the Deployment Checklist item #28. Use your corporate security recommendations for handling credentials. b. Enter a Decryption passphrase and the Decryption passphrase confirmation. Write this into the Deployment Checklist item #31. Use your corporate security recommendations for handling credentials. c. If you are using an Http or Https proxy, follow the PCF Director Proxy Settings instructions. We left them blank. d. Read the terms and conditions and select the select box to accept. e. Click Setup Authentication. Note: This passphrase encrypts the Ops Manager datastore and is not recoverable. 69 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

70 4. In the Pivotal log in dialog box, log in to Ops Manager with the admin credentials you created in the previous step (Deployment Checklist item #28). Use the same format you entered previously. It does not have to be in format. 5. In the Installation Dashboard screen, click the Ops Manager Director tile. 70 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

71 71 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

72 6. On the Settings tab, in the left pane, click vcenter Config and configure the following: a. vcenter Host: The hostname, or IP, of the vcenter that manages vsphere. Deployment Checklist item #17 b. vcenter Username: A vcenter username with create and delete privileges for virtual machines (VMs) and folders. Deployment Checklist item #24. c. vcenter Password: The password for the vcenter used, which was specified above. Deployment Checklist item #23. d. Datacenter Name: The name of the datacenter as it appears in vcenter. Deployment Checklist item #20. e. Virtual Disk Type: The Virtual Disk Type to provision for all VMs. For guidance on the virtual disk type to select, see Provisioning a Virtual Disk in vsphere. f. Ephemeral Datastore Names (comma delimited): The names of the datastores that store ephemeral VM disks deployed by Ops Manager. These are the datastores across each cluster where VMs could live or migrate to. Deployment Checklist item #21A-21C. 72 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

73 g. Persistent Datastore Names (comma delimited): The names of the datastores that store persistent VM disks deployed by Ops Manager. These are the datastores across each cluster where VMs could live or migrate to. Deployment Checklist item #21A-21C. h. Select NSX Networking. i. NSX Address, enter the FQDN that matches the fully trusted certificate applied to NSX Manager. Deployment Checklist item #18. ii. NSX Manager Username, which should be admin. Deployment Checklist item #25. iii. NSX Manager Password. Deployment Checklist item #25. iv. NSX CA Cert: Paste the PEM format of the fully trusted certificate applied to NSX Manager. This must include -----BEGIN CERTIFICATE---- all the way through -----END CERTIFICATE-- ---, just as the image shows above. i. VM Folder: What you would like the vsphere datacenter folder to be named (default: pcf_vms). This is where Ops Manager places VMs. j. Template Folder: What you would like the vsphere datacenter folder to be named (default: pcf_templates). This is where Ops Manager places VM Templates. k. Disk path Folder: What you would like the vsphere datastore folder to be named (default: pcf_disk). This is where Ops Manager creates attached disk images. You must not nest this folder. l. Click Save. Note: The NSX Address must match the name on the trusted certificate applied NSX Manager. Without a matching certificate, deployment will fail. 73 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

74 74 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

75 75 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

76 7. Click Director Config and do the following: a. In the NTP Servers (comma delimited) field, type your NTP server addresses. We set up our Domain Controller as an NTP server and typed that IP here. Deployment Checklist item #15. b. Enable the VM Ressurector Plugin. c. Both Blobstore Location and Database Location were left set to Internal. d. Leave all other options cleared and set to defaults. e. Click Save. 76 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

77 8. In the left pane, click Create Availability Zones. a. Click Add. 9. In the Create Availability Zones form do the following: a. Type a unique Name for the Availability Zone. b. Type the name of your first vcenter Cluster to use as an Availability Zone. Deployment Checklist item #19A. 10. Repeat steps 8 and 9 for each Cluster using Deployment Checklist item #s 19B and 19C. We have 3 clusters so we created 3 Availability Zones. a. Click Save. 77 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

78 78 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

79 11. In the left pane, click Create Networks. 12. In the Create Networks form, do the following: a. To enable ICMP on your networks, select Enable ICMP checks. Ops Manager uses ICMP checks to confirm that components within your network are reachable. 79 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

80 b. Use the following steps to networks: i. Click Add Network. ii. Type a unique Name for the network. We used the network names that match up with the logical switches created in NSX. c. To create one or more subnets for the network, click Add Subnet. i. Type the full path and vsphere Network Name as it displays in vcenter. Deployment Checklist item #13A. ii. For CIDR, type the valid CIDR notation for the block of IPs that matches this network. For example, /26. iii. For Reserved IP Ranges, type any IP addresses from the CIDR that you want to blacklist from the deployment. Ops Manager will not deploy VMs to any address in this range. In our example, this will include because.1 is already assigned to the NSX inside port and.2 is already assigned to Ops Manager. Deployment Checklist item #8. iv. Type your DNS and Gateway IP addresses. Deployment Checklist items #14 & 12A. v. Select which Availability Zones to use with the network. This may be all Clusters. a. Repeat steps b and c above for each internal network created following the NSX Cookbook. User Deployment Checklist items 12A-D and 13A-D for the appropriate fields. The last network will have the Service Network box checked because that will be the Dynamic Services network for BOSH Director-managed service tiles. b. Click Save. 13. When you Save the Create Networks form, you may see a ping related verification error. This message can be ignored because ICMP is disabled. 14. On the left, click Assign AZs and Networks. a. Use the drop-down menu to select a Singleton Availability Zone. The Ops Manager Director installs in this Availability Zone. b. Use the drop-down menu to select a Network for your Ops Manager Director. c. Click Save. 80 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

81 15. In the left pane, click Security. a. Leave this at Default settings and click Save. 16. In the left pane, click Syslog. a. We are not using a Syslog server so we chose No. b. Click Save. 81 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

82 17. In the left pane, click Resource Config. a. We chose large disk and large cpu. b. Click Save. 18. In the upper left area of the page, click Installation Dashboard to go back to the Dashboard. 82 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

83 19. On the right side of the page, click Apply Changes. This applies the changes made and deploy Ops Manager Director. 20. You should see the same errors from Create Networks page. Click Ignore errors and start the install. When the deployment is complete, you should see the following screen telling you that changes were applied. 83 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

84 21. Click Return to the Installation Dashboard. Green bar displays across the bottom of Ops Manager Director. On the Installation Dashboard you can see the green bar across the bottom of Ops Manager Director tile indicating that it is fully deployed. If the deployment fails, you will continue to see the red bar across the bottom of the tile and you would be taken to the Change Log. There you can click on the Logs link at the end of the row for more information to begin troubleshooting. Troubleshooting deployment is beyond the scope of this guide. 84 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

85 Get the log file if you want more information to help with troubleshooting. 85 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

86 4 Deploying and configuring Elastic Runtime for vsphere This section covers importing, configuring, and deploying Elastic Runtime for vsphere. For more information, go to the Pivotal page for Configuring Elastic Runtime for vsphere. 4.1 Adding Elastic Runtime to Ops Manager Pivotal Cloud Foundry Elastic Runtime is a complete, scalable runtime environment, extensible to most modern frameworks or languages running on Linux. Deployed applications enjoy built-in services and can automatically bind to new data services through a service broker or to an existing user-provided service. 1. Navigate to the Pivotal Cloud Foundry Elastic Runtime download page. Download the latest version or use the drop-down menu to download a previous release. Version Build 2 was used for this guide. 2. In Ops Manager, click Import a Product and select the Elastic Runtime file you downloaded. This may take a minute or two and then it should show up in the left column. 86 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

87 3. Then click the green + to add the Elastic Runtime tile. 4. Click the Pivotal Elastic Runtime tile to open the configuration. 87 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

88 5. The first section should already be selected but if not, on the Settings tab, click Assign AZs and Networks. a. Under Place singleton jobs, select the cluster where you want single instance VMs to live. b. Under Balance other jobs in, select all clusters to distribute other VMs. c. For Network, select the Deployment Network for ERT. d. Click Save. 6. Click Domains. 88 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

89 a. The System Domain defines your target when you push apps to Elastic Runtime. Dell EMC and Pivotal recommend the domain format: system.yourdomain.yourtopleveldomain. Replace the placeholders for your domain and top level domain. b. The Apps Domain defines where Elastic Runtime should serve your apps. Dell EMC and Pivotal recommend the domain format: apps.yourdomain.yourtopleveldomain. Replace the placeholders for your domain and top level domain. c. These are the domains you set a DNS wildcard entry for mentioned in the Prerequisites. d. Click Save. 7. In the Generate RSA Certificate dialog box, type the same domain names here and click Generate. 89 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

90 90 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

91 8. Click Networking. a. Because we are using VMware NSX, we added the three IPs that we reserved for the GoRouters (Deployment Checklist item #9) in the Router IPs box. The three IPs we reserved for Diego Brains (Deployment Checklist item #10) in the SSH Proxy IPs box, and left the HAProxy and TCP Router boxes empty. b. Because we are using NSX, under point-of-entry, we selected Forward SSL to Elastic Runtime Router. i. Click Generate RSA Certificate. 91 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

92 ii. Here you will want to add a comma delimited list of the domain names to put on the certificate. iii. Click Generate. More information can be found at the link Providing a Certificate for Your SSL/TLS Termination Point. The following are the recommended list for a split domain. *.yourdomain.com *.apps.yourdomain.com *.system.yourdomain.com *.login.system.yourdomain.com *.uaa.system.yourdomain.com iv. We chose to Enable route services. v. We selected the option to enable TCP Routing at a later time. vi. Leave the rest of the fields blank or set to defaults. vii. Click Save. 92 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

93 9. Click Application Containers. a. We made sure the first three options are selected and left the rest of the defaults set. b. Click Save. 93 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

94 10. Click Application Developer Controls. a. Leave the defaults set. b. Click Save. 11. Click Application Security Groups. a. Read and understand the message and then follow the directions at the prompt. b. Click Save. 94 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

95 12. Click Authentication and Enterprise SSO. a. Set the password policy to match your corporate password policy. b. Click Save. 95 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

96 13. Click UAA. a. We chose Internal MySQL for high availability. 96 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

97 b. Generate new SAML Service Provider Credentials. The following domains must be associated with the certificate: i. Login.your-system-domain ii. *.login.your-system-domain Note: The Pivotal Single Sign-On Service and Pivotal Spring Cloud Services tiles require the *.login.your-system-domain. c. The last thing changed on this page was the Customize Username Label. This was changed to read as Username instead of because usernames do not always have to be in the format. 14. Click Databases. a. We selected Internal Databases MySQL (preferred for complete high-availability). b. Click Save. 97 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

98 15. Click Internal MySQL. a. Enter the reserved MySQL Proxy IPs (Deployment Checklist item #11). b. The MySQL Service Hostname is entered as the load balancer inside IP on the same subnet as the MySQL Proxy IPs. Deployment Checklist Item #12B. c. Add an address to which alerts can be sent. d. Select Disabled automated backups of MySQL, because this guide is based on a proof of concept install, so we are not doing backups. e. Leave all other defaults. f. Click Save. 98 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

99 16. Click File Storage. a. Select Internal WebDAV. b. Click Save. 17. Click System Logging. 99 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

100 a. This section is optional. We will leave the defaults. b. Click Save. 18. Click Custom Branding (Optional). a. Here you can add a Company Name, Accent Color, and other style options. b. Leave everything else empty. c. Click Save. 100 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

101 19. Click Apps Manager. a. Leave all the defaults. b. Click Save. 20. Click Notifications. 101 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

102 a. Leave all of these blank or defaults. Leaving this section empty requires an Admin user to create all users accounts. Having an SMTP server available and completing this section facilitates user self-registration. SMTP server is Deployment Checklist item #16 if you have one. b. Click Save. 21. Click Cloud Controller. a. Leave this blank. This is only necessary on subsequent deployments. b. Click Save. 102 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

103 22. Click Smoke Tests. a. Select Temporary org and space. b. Click Save. 103 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

104 23. Click Advanced Features. a. Leave all defaults. b. Click Save. 104 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

105 24. Click Errands. a. Set the Notifications Errand and Notifications UI Errand to Off since we did not configure an SMTP server. If you configured an SMTP server, you can leave these enabled. b. Leave all other Errands set to Default so that they will run when they are changed. c. Click Save. 105 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

106 25. Click Resource Config. a. Leave all defaults. b. Make sure HAProxy Instances is set to 0 since we are using NSX. c. Click Save. 26. Click Stemcell. a. Leave this page alone since it was already showing the latest stemcell version that came with Ops Manager. 106 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

107 b. In the upper left area of the page, click Installation Dashboard. 27. On the right side of the page, click Apply Changes. This applies the changes and deploys Elastic Runtime. 28. When the deployment completes, you should see the following screen showing that changes have been applied. Click Return to the Installation Dashboard. 107 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

108 On the Installation Dashboard, you can now see the green bar across both the Ops Manager Director tile and Elastic Runtime tile indicating that they are both deployed correctly. If the deployment fails, you may continue to see the red bar across the bottom of the tile and you would be taken to the Change Log. There you can click on the Logs link at the end of the row for more information to begin troubleshooting. Troubleshooting deployment is beyond the scope of this guide. Check the log file if you need to troubleshoot Ops Manager Director. 108 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

109 4.1.1 Viewing all the VMs for Ops Manager Director or Elastic Runtime 1. From the Installation Dashboard, click either Ops Manager Director tile or Pivotal Elastic Runtime tile. Then click on the Status tab. This displays all of the VMs for Ops Manager Director or Elastic Runtime, depending on which tile you selected. 2. In the Elastic Runtime Status images below, you can also see the AZ column, which shows on which Cluster that instance is running. 109 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

110 Page that displays when you select Pivotal Elastic Runtime Status. Page that displays when you select Pivotal Elastic Runtime Status. 110 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

111 5 Creating new orgs, spaces, and user accounts Next, we create new Orgs, Spaces, user accounts, and associate them together before you can push apps. Do this using your management VM. In addition, you can use the Apps Manager UI to create Orgs and Spaces, but not to create user accounts in Elastic Runtime v You can use the cf CLI to do both and we illustrate those steps in the following sections. 5.1 Obtaining credentials Before you can log in to the cf CLI, credentials are required. Many of the possibly needed sets of credentials are kept in Pivotal and are obtained from the Credentials tab in Ops Manager for each component. 1. Log in to Ops Manager with the credentials you created and used earlier in Section 3.2, Step 3 (Deployment Checklist item #28). 2. Click on the Elastic Runtime tile. 111 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

112 3. Click Credentials. 4. On the Credentials tab, find UAA in the left column and Admin Credentials in the right column. Click Link to Credential. This takes you to a page showing you the generated username and password. Write these credentials in the Deployment Checklist item #29. Note: This page will not update if you log in to that user profile and change the password. 5. Use those credentials to log in to the cf CLI in the next section. 5.2 cf CLI for orgs, spaces, and user accounts This is where we will create a new org, a space within that org, a user account, and associate them together. 1. Open an elevated command prompt on your tools machine where you have the cf CLI installed. 2. At the command prompt, type: cf login a api.system.yourdomain.yourtopleveldomain --skip-ssl-validation 3. You are prompted for and password. These are the credentials you obtained above in section 5.1 and do not need to be in format. Deployment Checklist item # Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

113 4. Next, you are asked for an org. Because we want to create a new org, press Enter to skip. This takes you back to a command prompt but you are now logged into the API system. 5. To create a new org, at the command prompt type the following and then press Enter: cf create-org NewOrgName 6. To create a new space inside that org, at the command prompt type the following and press Enter: cf create-space NewSpaceName o NewOrgName 113 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

114 7. You must target that org and space to work inside of it. At the command prompt, type the following and press Enter: cf target NewOrgName s NewSpaceName 8. Time to create a new user in that org and space. Add these new credentials to the Deployment Checklist item #30. At the command prompt type the following and then press Enter: cf create-user UserName Password Note: Password must adhere to the password policy configured during Elastic Runtime configuration. 9. After a user is created, that user must be given a role in this org and space. At the command prompt type the following and press Enter: cf set-space-role --help to see the available roles. For more information, go to Orgs, Spaces, Roles, and Permissions. 114 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

115 10. At the command prompt, type the following and press Enter: cf set-space-role UserName OrgName SpaceName RoleName You have created a new org, space, and user account. That user alone has access to that org and space. Next, we can push an app to this space as this user. 115 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

116 6 Obtaining and pushing apps to PCF In our example app deployments, we have forked the code for the Dotnet Core Hello World app and the Spring Music app from the Cloud Foundry samples at Github so that the code will remain unchanged. You can obtain them from the links in each section or from the list of links at the bottom of this paper. We will verify each app works by visiting the created webpages from another machine. Because we are using a private network behind a company proxy, there were a couple of additional configurations to get these to work. You may or may not need these same additional configurations. We are not able to publish public DNS records. This means that to check that our apps are published and working, we have to use another machine in our environment that can resolve the web addresses created when the apps are pushed. Because we are behind a corporate proxy, there are some changes we had to make so that our management machine could access the internet and our intranet at the same time in the various tools. Git for Windows uses its own proxy list instead of Windows Internet Options proxies or environment variables. We had to set proxies directly in the Git for Windows tool. While pushing an app, PCF tries to reach out to the internet to make sure it has the correct dependencies for that app. In our specific situation, this required us to set proxies in the manifest.yml file for each app we tried to push. The Spring Music app has to be assembled first. This operation connects to the internet to download dependencies and assembles the app using the Gradlew command. We had to set our proxies in the gradle.properties file. There are other possible ways to get around these, but this was a quick solution for this solution guide. Note: See Appendix for more information on these additional configurations. Create a folder where you can put your apps. 1. First, use your favorite File Explorer and create a new folder where you can put your apps from the web. We created a folder called TestApps. 2. Cloud Foundry samples at Github is where you find several example applications. There are many more example applications up a level from that page as well. 116 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

117 6.1 Hello World Let s use Git for Windows to obtain the Hello World app. 1. Here is the direct link to the dotnet-core-hello-world app that we will be using. 2. On this page, click the green Clone or download button and then click on the Copy to Clipboard icon at the end of the address. 3. Open an elevated Git for Windows CMD. Change directory to the folder you created in step At the command prompt, type git clone and then CTRL + V to paste the URL that you copied to the clipboard. The result will be: git clone Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

118 5. Press Enter. The Hello World app will be unpacked into its own folder inside your TestApps folder. After the app is unpacked, you can make any changes to the manifest.yml file as needed such as how we had to add our proxies. That is discussed in more detail in the Appendix Pushing Hello World 1. Go back to the elevated CMD where we were typing cf commands if it is still open and you are still logged into the api.system.yourdomain.yourtopleveldomain. If it is not still open, you must open a new elevated CMD and login with the following command again, using the new user we created. Use credentials in Deployment Checklist item #30. cf login a api.system.yourdomain.yourtopleveldomain --skip-ssl-validation 118 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

119 2. Because this user only has access to this Org and Space, that is what is targeted. Change to the directory where your app has been unpacked. 3. Buildpacks are updated frequently. At the command prompt, type cf buildpacks and press Enter to see the buildpacks currently installed and their versions. 4. The app we are going to push is a dotnet app and we can see that the version we have installed is an older version than what is currently available. Even when your deployment is with a newer version of Elastic Runtime, and you get newer buildpacks, this is a good exercise so that you get the latest buildpack. We want to reach out to Github and use the latest dotnet buildpack when we push this app. To do this, at the command prompt, type the following and press Enter: cf push b 5. You should see the app begin deployment. 119 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

120 6. After the app is pushed and started, you will see an OK for health and get a URL to access it. This will be the URL you use to access your newly published app. Write this URL in the Deployment Checklist item # Confirming Hello World is working Pivotal Cloud Foundry is installed and the first app has been pushed. Now to confirm that it is working, we will browse to the Hello World URL (Deployment Checklist item #32) given in the output of the cf push function. Do this from any other machine in the same environment. We have to use a machine that can resolve the URL. Browsing to the Hello World URL. 6.2 Spring Music Let s use Git for Windows to obtain the Spring Music app. 1. Here is the direct link to the Spring Music app that we will be using. 120 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

121 2. On this page, click the green Clone or download button and then click the Copy to Clipboard icon at the end of the address. 3. Open an elevated Git for Windows CMD. Change directory to the folder you created in Section 6, step At the command prompt, type git clone and then ctrl+v to paste the URL that you copied to the clipboard. The result displays here: git clone Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

122 5. Press Enter. The Spring Music app will be unpacked into its own folder inside your TestApps folder. After the app is unpacked, you can make any changes to the manifest.yml file as needed, such as how we had to add our proxies. That is discussed in more detail in the Appendix Assembling Spring Music Spring Music is a little different from Hello World in that it has to be assembled before it can be pushed. As mentioned above, this is where we had to set our proxies in the gradlew.properties file. More information about that can be found in the Appendix. 1. To assemble Spring Music, go back to the elevated CMD where we were typing cf commands if it is still open and you are still logged into the api.system.yourdomain.yourtopleveldomain. If it is not still open, you must open a new elevated CMD. Change directory to your Spring Music folder. 2. At the command prompt, type the following command and press Enter. This starts assembling the app and you will see it downloading and unzipping packages. 122 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

123 Gradlew clean assemble 3. At the end of the assembly you will see BUILD SUCESSFUL. 4. Now, we need to make sure we are logged in with the cf CLI tools again using the new user we created. Use credentials in Deployment Checklist item #30 again. At the command prompt, type the following command and then press Enter. cf login a api.system.yourdomain.yourtopleveldomain --skip-ssl-validation 5. Since this user only has access to this Org and Space, that is what is targeted. Change to the directory where your app has been unpacked. 123 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

124 6. Since this app was assembled already, we should only have to push it. At the command prompt, type the following command: cf push and press Enter to see the deployment begin. 7. After the app is pushed and started, you will see an OK for health and get a URL to access it. This will be the URL you use to access your newly published app. Write this URL in the Deployment Checklist item # Confirming Spring Music is working Pivotal Cloud Foundry is installed and the second app has been pushed. Now to confirm that it is working, we will browse to the Spring Music URL (Deployment Checklist item #33) given in the output of the cf push function. Do this from any other machine in the same environment. We have to use a machine that can resolve the URL. 124 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

125 6.3 Intro to Apps Manager We can also look in Apps Manager to see our running apps in their Org and Space. 1. Open a webpage on your tools VM and browse to the following URL. On this page, you will log in with the credentials that you created in Section 5.2, Step 8 (Deployment Checklist item #30) and then click Sign In Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

126 2. After you are logged in, you see your new Org and the smaller box is your Space. Click on your Space where it shows two Apps. 3. On the Space Test page, we can see both of our apps (Hello World and Spring Music), that they are both running, and some additional information about them. You can click on one of them to drill down further. This concludes our deployment of Pivotal Cloud Foundry on a Dell XC cluster including pushing two apps to confirm our deployment is working. 126 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

127 7 Deploying and configuring Articulate app with Attendee- Service code connecting to MySQL 2.0 for PCF Articulate is a web application that exposes friendly, browsable user interface. However, it does not work with data directly. It depends on the Attendee-service application to manage data. The Attendee-service persists data to a MySQL database. 7.1 Deploying MySQL to PCF This section covers importing, configuring, and deploying MySQL v2.0 for Pivotal Cloud Foundry. For more information, go to the Pivotal page for MySQL for PCF. MySQL for PCF enables PCF app developers to provision and use a MySQL database with a single command. MySQL for PCF 2.0 introduces a new type of service, an on-demand service that replaces the pre-provisioned service that was in the v1.x series. 127 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

128 1. Navigate to the MySQL for PCF v2 download page. Download the latest version or use the dropdown menu to download a previous release. Version was used for this guide. 2. Before we can import, configure, and deploy MySQL, we need to create an Application Security Group specifically for MySQL. 3. With Notepad++, create a file called mysql-asg.json with the following configuration. Replace CIDR with your Dynamic Services Network. If you are following this guide exactly, that will be /22 as listed in Section 2.1. [ ] { } "protocol": "tcp", "destination": "CIDR", "ports": "3306" 4. Use cf login again to log in as your admin user with the same credentials obtained in section 5.1 (Deployment Checklist item #29). Hit Enter leaving Org blank. 128 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

129 5. Make sure your prompt is in the same folder where the mysql-asg.json file is. Create an Application Security Group called p.mysql by typing cf create-security-group p.mysql./mysql-asg.json and press Enter. 6. To bind the Application Security Group to the platform-wide running Application Security Group type cf bind-running-security-group p.mysql and press Enter. 7. In PCF Ops Manager, click Import a Product and select the MySQL file you downloaded. This may take a minute or two and then it should show up in the left column. 8. Then click the green + to add the MySQL for Pivotal Cloud Foundry v2 tile. 129 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

130 9. Click the MySQL for Pivotal Cloud Foundry v2 tile to open the configuration. 10. The first section should already be selected but if not, on the Settings tab, click Assign AZs and Networks. a. Under Place singleton jobs, select the cluster where you want the MySQL Broker to run in. The broker runs as a single instance VM. 130 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

131 b. Under Balance other jobs in, select one but it doesn t matter which one because this field is currently not used. c. For Network, select the Deployment Network for ERT. d. For Service Network, select the Dynamic Services Network. e. Click Save. 11. The next 5 pages are MySQL plans that will be offered. For example, Page 1 will be a small plan with 1 CPU, 2GB RAM, and 8GB of disk storage. Page 2 will be a medium plan with 2 CPUs, 4GB RAM, and 8GB of disk storage. Page 3 will be a large plan with 2 CPUs, 8GB RAM, and 16GB disk storage. On the Plan 1 page (our small plan): a. Select Enable if it is not already enabled. b. Change the Plan Name if desired. c. Select a MySQL VM Type. d. Select a MySQL Persistent Disk size. e. Select a MySQL Availability Zone. The plan creates al service instance VMs with this plan in this AZ. Chose a different AZ than the one that the broker is in. f. Click Save. Note: If you intend to enable backups, choose a persistent disk type that is three times as large as you intend to provide to developers. For more information, see Backing up and Restoring On-Demand MySQL. 131 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

132 12. On the Plan 2 page (our medium plan): a. Select Enable if it is not already enabled. b. Change the Plan Name if desired. c. Select a MySQL VM Type. d. Select a MySQL Persistent Disk size. e. Select a MySQL Availability Zone. The plan creates al service instance VMs with this plan in this AZ. Chose a different AZ than the one that the broker is in. f. Click Save. Note: If you intend to enable backups, choose a persistent disk type that is three times as large as you intend to provide to developers. For more information, see Backing up and Restoring On-Demand MySQL. 132 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

133 13. On the Plan 3 page (our large plan): a. Select Enable if it is not already enabled. b. Change the Plan Name if desired. c. Select a MySQL VM Type. d. Select a MySQL Persistent Disk size. e. Select a MySQL Availability Zone. The plan creates al service instance VMs with this plan in this AZ. Chose a different AZ than the one that the broker is in. f. Click Save. Note: If you intend to enable backups, choose a persistent disk type that is three times as large as you intend to provide to developers. For more information, see Backing up and Restoring On-Demand MySQL. 133 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

134 14. Page Plan 4 will not be used so it will be set to Inactive. Click Save. 15. Page Plan 5 will not be used so it will be set to Inactive. Click Save. 134 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

135 16. On the Settings screen, decide whether to provide public IP addresses to the Service VMs and enter the Maximum number of service instances. We left the defaults. Click Save. 17. On the Backups screen, select if and how backups will be done. We left this disabled. Click Save. 135 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

136 18. On the Monitoring page, configure logging if desired. We left both unchecked. Click Save. 19. On the Syslog page, we chose to not configure syslog. Click Save. 136 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

137 20. On the Errands page, turn off Smoke Test because it is currently dependent on port 80. Following this guide sets all apps curling over port 443. This Smoke Test is not necessary for MySQL to function correctly and the code will be updated in the next release so that it will not be dependent on port 80. Click Save. 137 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

138 21. On the Resource Config page, click Save. 22. In a web browser, go to Stemcells for PCF to download the latest release. The latest at the time of this guide is Select Ubuntu Trusty Stemcell for vsphere Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

139 23. On the Stemcell page, click Import Stemcell and select the file you downloaded in the previous step. Then click Installation Dashboard. 24. Back on the Installation Dashboard, click Apply Changes to deploy MySQL. 139 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

140 25. When the deployment is finished successfully, you will see the Change Log showing MySQL with a result of Succeeded. If the deployment fails, you may continue to see the red bar across the bottom of the tile and on the Change Log you can click on the Logs link at the end of the row for more information to begin troubleshooting. Troubleshooting deployment is beyond the scope of this guide. 7.2 Attendee-Service Before we can push the Articulate app, we need the Attendee-service to sit between Articulate and MySQL. 1. Here is the direct link to the Attendee-service-code that we will be using. 2. On this page, click Clone or download and then click the Copy to Clipboard icon at the end of the address. 140 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

141 3. Open an elevated Git for Windows CMD. Change directory to the folder you created in Section 6, step At the command prompt, type git clone and then CTRL + V to paste the URL that you copied to the clipboard. The result will be: git clone 5. Press Enter. The Attendee-service code will be unpacked into its own folder inside your TestApps folder. After the app is unpacked, you can make any changes to the manifest.yml file as needed such as how we had to add our proxies. That is discussed in more detail in the Appendix. 141 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

142 7.2.1 Assembling and pushing Attendee-Service Attendee-service is similar to Spring Music in that it has to be assembled before it can be pushed. Here we had to set our proxies in the mvnw.cmd file. More information about that can be found in the Appendix. 1. To assemble Attendee-service code, go back to the elevated CMD where we were typing cf commands if it is still open and you are still logged into the api.system.yourdomain.yourtopleveldomain. If it is not still open, you must open a new elevated CMD. Change directory to your pcf-attendee-service-code folder. 2. At the command prompt, type the following command and press Enter. This starts assembling the app and you will see it downloading and unzipping packages. mvnw clean install 3. At the end of the assembly you will see BUILD SUCCESS. 142 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

143 4. Now, we need to make sure we are logged in with the cf CLI tools again using the new user we created. Use credentials in Deployment Checklist item #30 again. At the command prompt, type the following command and then press Enter. cf login a api.system.yourdomain.yourtopleveldomain --skip-ssl-validation 5. Since this user only has access to this Org and Space, that is what is targeted. 6. Now we need to create a MySQL service for the Attendee-service. Type the following command: cf marketplace and press Enter to see the list of available services. We will be using the p.mysql service with one of the plans lists. 7. To create the new p.mysql service called attendee-service using the db-small plan type cf create-service p.mysql db-small attendee-mysql and press Enter. 143 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

144 8. This can take several minutes to create the new service. Type cf services and hit Enter to see the status. This step can be repeated until the service has been created. 9. Alternatively, you can look at the Services screen in App Manager to see when the service is finished being created. 10. After the service has finished being created, we need to push the Attendee-service. Type cf push and press Enter. 11. After the Attendee-service is pushed and started, you will see an OK for health and get a URL to access it. We will need this URL in a couple minutes. Write it down in the Deployment Checklist item # Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

145 7.3 Articulate app Now that MySQL and the Attendee-service-code are in place, we need to package, push, and bind the Articulate app. 1. Here is the direct link to the Articulate app that we will be using. Note: This is a forked version of this code that allows https. The original version was bound to http, which we have terminated at the GoRouter. 2. On this page, click Clone or download and then click Copy to Clipboard at the end of the address. 3. Open an elevated Git for Windows CMD. Change directory to the folder you created in Section 6, step At the command prompt, type git clone and then CTRL + V to paste the URL that you copied to the clipboard. The result will be: 145 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

146 git clone 5. Press Enter. The Articulate app will be unpacked into its own folder inside your TestApps folder. 6. This version of Articulate unpacks with a manifest.yml file that needs modification. This is what it looks like after our modifications including adding our proxy, which is discussed in more detail in the Appendix. --- applications: - name: articulate path: target/articulate snapshot.jar memory: 1024M disk_quota: 1024M random-route: true stack: cflinuxfs2 env: https_proxy: Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

147 7. Save this manifest.yml file in the same folder where Articulate is unpacked Packaging and pushing Articulate app Articulate app is similar to Attendee-service in that it has to be assembled before it can be pushed. Here we had to set our proxies in the mvnw.cmd file. More information about that is found in the Appendix. 1. To assemble Articulate app code, go back to the elevated CMD where we were typing cf commands if it is still open and you are still logged into the api.system.yourdomain.yourtopleveldomain. If it is not still open, you must open a new elevated CMD. Change directory to your articulate folder. 2. At the command prompt, type the following command and press Enter. This starts assembling the app. mvnw package 3. At the end of the assembly you will see BUILD SUCCESS. 147 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

148 4. Now, we need to make sure we are logged in with the cf CLI tools again using the new user we created. Use credentials in Deployment Checklist item #30 again. At the command prompt, type the following command and then press Enter. cf login a api.system.yourdomain.yourtopleveldomain --skip-ssl-validation 5. Since this user only has access to this Org and Space, that is what is targeted. 6. After the Articulate app has been assembled with mvnw package, we need to push the app. Type cf push and hit Enter. 7. After the Articulate app is pushed and started, you will see an OK for health and get a URL to access it. But we are not ready to run the app yet. Write down that URL in the Deployment Checklist item # Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

149 8. Before we can bind Articulate to the Attendee-service, we have to create a new user provided service called attendee-service. Do that with cf create-user-provided-service attendeeservice p uri. And when prompted for the uri, type in the URL you received after pushing Attendee-service code and wrote in the Deployment Checklist item #34. Then press Enter. 9. Now we can bind Articulate to the Attendee-service with cf bind-service articulate attendee-service and press Enter. 10. Before using Articulate, we need to restage it after binding it to the new service. Type cf restage articulate and press Enter. 11. You should receive an OK for health and the same URL that Articulate was using previously (Deployment Checklist item #35). 149 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

150 7.3.2 Confirming Articulate is working 1. Browse to the Articulate URL (Deployment Checklist item #35) given in the output of the cf restage articulate function at the end of Section Do this from any other machine in the same environment that can resolve the URL. Click on the Services menu. 2. Enter information into the Attendees Database Tool on the left and then click Add. 150 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

151 3. Here you can see that the new record was added to the MySQL database. This concludes our deployment of the Articulate app using the Attendee-service-code to work with a MySQL database. 151 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

152 A Appendix A.1 Adding proxy to Git for Windows If you use a proxy to access the Internet, Git for Windows uses its own list. It does not use the list under LAN Settings on the Connections tab in Internet Options. In addition, it does not use Windows environment variables. Proxies must be set in the Git for Windows CMD tool. Here are the commands and what they do. Used to remove any previously set proxies: git config --global --unset http.proxy git config --global --unset https.proxy Used to set your http and https proxies. Replace FQDN:port with the address and port of your proxies: git config --global http.proxy FQDN:port git config --global https.proxy FQDN:port Example: git config --global http.proxy Example: git config --global https.proxy Used to verify the proxies are set. This should output the address and port you set above. git config --global get http.proxy git config --global get https.proxy A.2 Adding proxy to manifest.yml If you use a proxy to access the internet, you may need to add your proxy to the environment (env) section in the Manifest.yml file in each app before pushing the app. If the env section is not there, add it. In this example, the env section was already there and had the CACHE_NUGET_PACKAGE line. We added the http_proxy and https_proxy lines. Format should be similar to this. Adding the http_proxy. 152 Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment

153 A.3 Adding proxy to gradle.properties file If you use a proxy to access the internet, and you have to assemble an app using the gradlew command, you may have to add your proxies to the gradle.properties file. This file should be located in the root of your app where the gradlew command is. Format should be similar to the following and you can remove any of these lines that you do not need. This shows both http and https settings for the proxy, port, and credentials if necessary. Notepad++ is used in the example to edit the gradle.properties file. Example format A.4 Adding proxy to mvnw.cmd file If you use a proxy to access the internet, and you have to assemble an app using the mvnw command, you may have to add your proxies to the mvnw.cmd file. This file should be located in the root of your app where the mvnw command is. Format should be similar to the following and can be added into the file between some of blocks. set MAVEN_OPTS=-Dhttps.proxyHost=proxy.company.com -Dhttp.proxyPort=80 -Dhttps.proxyHost=proxy.company.com -Dhttps.proxyPort= Production Pivotal Cloud Foundry on VMware vsphere using Dell EMC XC Series Appliances or XC Core System Deployment