SAS Visual Investigator on the Cloud: Deployment Guide

Transcription

1 SAS Visual Investigator on the Cloud: Deployment Guide SAS Documentation July 14, 2017

2 The correct bibliographic citation for this manual is as follows: SAS Institute Inc SAS Visual Investigator on the Cloud: Deployment Guide. Cary, NC: SAS Institute Inc. SAS Visual Investigator on the Cloud: Deployment Guide Copyright 2017, SAS Institute Inc., Cary, NC, USA All Rights Reserved. Produced in the United States of America. For a hard copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. The scanning, uploading, and distribution of this book via the Internet or any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of others' rights is appreciated. U.S. Government License Rights; Restricted Rights: The Software and its documentation is commercial computer software developed at private expense and is provided with RESTRICTED RIGHTS to the United States Government. Use, duplication, or disclosure of the Software by the United States Government is subject to the license terms of this Agreement pursuant to, as applicable, FAR , DFAR (a), DFAR (a), and DFAR , and, to the extent required under U.S. federal law, the minimum restricted rights as set out in FAR (DEC 2007). If FAR is applicable, this provision serves as notice under clause (c) thereof and no other notice is required to be affixed to the Software or documentation. The Government s rights in Software and documentation shall be only those set forth in this Agreement. SAS Institute Inc., SAS Campus Drive, Cary, NC May 2017 SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are trademarks of their respective companies P1:dplyvi0cld

3 Contents Chapter 1 / Introduction Deployment Architecture How SAS Visual Investigator Is Deployed Chapter 2 / System Requirements for SAS Visual Investigator Cloud Platform Software Requirements Virtual Machine Operating System and Software Requirements Web Browser Requirements Chapter 3 / Pre-installation Tasks Complete Configuration Worksheet Enable Required Ports Chapter 4 / Installing SAS Visual Investigator on SAS Viya Prepare the Installation Tools Prepare the Installation Environment Install SAS Visual Investigator Chapter 5 / Validating the Deployment Overview Chapter 6 / Contact SAS Technical Support Contact SAS Technical Support Chapter 7 / Appendix A: Cloud Foundry Deployment Information Cloud Foundry Deployment Data Using vsphere as the IaaS Cloud Foundry Deployment Data Using OpenStack as the IaaS Chapter 8 / Appendix B: Troubleshooting BOSH Cloud Foundry Run Time

4 iv Contents

5 1 Introduction 1 Deployment Architecture How SAS Visual Investigator Is Deployed Deployment Architecture This document describes the processes to deploy SAS Visual Investigator in a private cloud. Only the Cloud Foundry private cloud environment is currently supported for cloud deployments. Instead of requiring Base SAS, SAS Visual Investigator uses the Cloud Analytic Services (CAS) run-time environment. How SAS Visual Investigator Is Deployed The installation and deployment of SAS Visual Investigator on Cloud Foundry uses a self-extracting installer to deliver the software into a directory on a physical server or a virtual machine (VM). The installer creates a toplevel directory named sas, which contains two subdirectories: the bin directory and the image directory. The bin directory consists of a single Bash script named start. The image directory is a systemd-nspawn namespace container that is invoked by the start Bash script and contains functionality that is used in SAS Visual Investigator deployment-related activities. It can be shut down and restarted whenever these functions are needed. In addition, the entire container, with any changes that are made, can be repackaged, archived, or moved to another server or a VM as needed. You must perform these tasks to deploy SAS Visual Investigator: Prepare the installation tools. Prepare the installation environment. Install SAS Visual Investigator.

6 2

7 3 System Requirements for SAS Visual Investigator 2 Cloud Platform Software Requirements Cloud Foundry Requirements Other Required Software Supported Databases Virtual Machine Operating System and Software Requirements Web Browser Requirements Cloud Platform Software Requirements Cloud Foundry Requirements Cloud Foundry v230 through v246 on either OpenStack or vsphere o OpenStack Mitaka version or later o VMware vsphere ESXi 6.0 U2 BOSH CLI or later cf CLI version d or later Stemcell CentOS 7,x sas_java_buildpack 3.12 Other Required Software The following third-party software is included with your SAS software: HashiCorp Consul Included to enable service discovery and configuration. RabbitMQ Included to provide an open-source, standards-based platform for SAS components and applications to send and receive messages. Elasticsearch Included to provide search capability. Apache Geode Used for session caching.

8 4 Supported Databases SAS Visual Investigator supports the following database: PostgreSQL The following data stores are supported: PostgreSQL 9.4 Oracle 12c Virtual Machine Operating System and Software Requirements The VM instance that is used to install SAS Visual Investigator has the following requirements: Red Hat Enterprise Linux or CentOS 7.2 must be installed. 20 GB free space must be available. The installation user must have sudo privileges. systemd-nspawn must be installed. Web Browser Requirements End users can access the SAS Visual Investigator user interface from a web browser running on a desktop machine. For information about supported web browsers and the corresponding platforms to access SAS Viya user interfaces, see Browsers on tablets and other mobile devices are not supported. SAS Environment Manager and CAS Server Monitor are not supported in this release of SAS Visual Investigator.

9 5 3 Pre-installation Tasks Complete Configuration Worksheet Enable Required Ports Complete Configuration Worksheet To prepare for deployment, you must collect information about deployment via the key value pairs in the CF_Deployment_Questionnaire.xlsx spreadsheet. See index.html. Then, during installation, you must manually enter this information in a configuration file. To complete and customize your deployment, specify the information by associating required and optional keys with the appropriate values. Complete either the vsphere worksheet or the OpenStack worksheet, according to your environment. Specify a value under each Value column that is not already pre-populated. Do not specify any values for passwords. They are entered on-site. Blank lines have been inserted to improve readability and to show a separation between sections of the configuration file. JSON header lines are included to provide information about the section. Enable Required Ports The following ports are used by SAS Visual Investigator and should be available before you begin to deploy your software. The same ports should also be available for any firewalls that are configured on the operating system or the network. Process Required Port Notes HTTPD 80 (internal) 443 (external) default Erlang Port Mapper Daemon (epmd) port 4369

10 6 Process Required Port Notes SAS Infrastructure Data Server For a single server deployment with no failover, ports must be opened. Additional standby nodes each get the next available port number sequentially up to CAS Server Starting Port 5577 Used by clients to make binary connections to CAS. CAS Communicator Port 5580 default SAS Messaging Broker AMQP client access port 5672 SAS Configuration Server 8500 SAS uses HashiCorp Consul as its configuration server. Object Spawner 8591 CAS Server Monitor 8777 Used by clients to make REST HTTP calls to CAS, as with the Python REST interface. Elasticsearch 9200 Default PgPool port 9432 default SAS Messaging Broker management web console port SAS/CONNECT Spawner SAS Cloud Analytic Services Server default SAS Messaging Broker clustering port Apache Geode 40404

11 7 Installing SAS Visual Investigator on SAS Viya 4 Prepare the Installation Tools Overview Download the Binary Installer File Preparation Extract the Files Start the Container Sign On to the Container Overview on Help Prepare the Installation Environment Overview Set the Configuration File Edit the Configuration File Save the Configuration File Authenticate to Cloud Foundry and BOSH Upload the Buildpacks Upload the BOSH Stemcells Upload the BOSH Releases Create the Files for Deployment Preparing to Examine the Files Examine the Files Related to BOSH Examine the Files Related to Cloud Foundry Using Logs Install SAS Visual Investigator Overview Deploy Services to BOSH Deploy Stateless Applications and Microservices Prepare the Installation Tools Overview Installing SAS Visual Investigator begins by downloading the binary installer file to a physical or virtual machine (VM) in the IaaS environment. The VM is used as the secure administration host ("jump server") for the installation and deployment. The installation consists of the following tasks:

12 8 Download the binary installer. Extract the files. Start the container. Sign on to the container. Download the Binary Installer Copy the binary installer file sas.bin to the home directory of the installer ID on the bastion box. For example, if your user ID is test, then the default home directory is /home/test. Copy the binary installer to the bastion box using the wget command. The wget command is used to access a local web server: wget 10_2 xxx lax.zip :53: _2 xxx lax.zip Connecting to :80... connected. HTTP request sent, awaiting response OK Length: (5.1G) [application/octet-stream] Saving to: 'visualinvestigator 10_2 xxx lax.zip' 100%[=================================================>] 5,508,425, MB/s in 1m 43s :54:47 (50.8 MB/s) - 'visualinvestigator 10_2 xxx lax.zip' saved [ / ] File Preparation The file preparation consists of the following tasks: Unzip the file. Unzip the file using the unzip utility. unzip visualinvestigator 10_2 xxx lax.zip. Extract the Files Once the file is on the bastion box, extract the binary file with the following command: bash visualinvestigator 10_2 xxx lax.bin Validating archive... Extracting to /home/test/sas... Note: The binary installer deploys to the installing user s home directory. Start the Container Run the start.sh script in the user s home directory to start the container:./sas/bin/start Here are the displayed results: Starting SAS Visual Investigator Deployment Container...

13 Prepare the Installation Tools 9 Spawning container <instance>.<hostname>.unx.sas.com on /home/test/sas/image. Failed to create directory /home/test/sas/image//sys/fs/selinux: No such file or directory Failed to create directory /home/test/sas/image//sys/fs/selinux: No such file or directory Press ^] three times within 1s to kill container. systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) Detected virtualization systemd-nspawn. Detected architecture x Welcome to CentOS Linux 7 (Core)! Because the container attempts to alter the state of the host operating system, the following error message might be displayed. This message is expected and can be safely ignored: Failed to create directory /home/test/sas/image//sys/fs/selinux: No such file or directory Failed to create directory /home/test/sas/image//sys/fs/selinux: No such file or directory [FAILED] Failed to start LSB: Bring up/down networking. See 'systemctl status network.service' for details. Sign On to the Container Once the container is started, a login prompt is displayed: CentOS Linux 7 (Core) Kernel el7.x86_64 on an x86_64 sfr47066 login: The prompt shows a host name with a randomly generated prefix and then the word login. Enter your user ID and then enter your password to sign on to the container. Last login: Wed Jun 15 12:41:34 on console SAS 15:04:47!1 [~] After you sign on to the container, notice that the prompt now includes the string, SAS, followed by a timestamp. For convenience, the shell is set to the Z shell (zsh), which provides the standard shell for SAS Visual Investigator deployments. Note: Do not change shells. Any other shell might produce unexpected results. The window of your X terminal emulator displays the title Container. The title is a reminder that your work environment is within the container and that you are no longer working within the host file system. Overview on Help Synopsis: help [OPTIONS] [word]... Getting help on packages, components, methods, and functions. Options: -p --package [<package>]... Show package-specific help -c --component <component>... Show component-specific help -s --synopsis Show script synopses for functions, classes, and methods Description: Show help

14 10 For the -p option: Package directories are fully-qualified domain names (FQDNs) that are directly under one of the package root directories: packages:d system:d If the -p option is used, then package-specific help is shown. If the <package> is omitted, then the primary package help is shown. If a <package> is specified, then help is shown for the specified package. For the -c option: Components are those directories directly under a package directory. Those functions and methods that are defined under a component directory are shown when this option is selected. If a component is present in multiple packages, then it is shown for. For more detailed information about deploying SAS Visual Investigator, use the following command: sas help -p SAS Visual Investigator: How to Guide The typical sequence for performing deployments consists of the following commands: sas conf list sas conf install -n <name> -u <url> sas conf use <name> sas conf edit : list the available JSON configuration files : optionally, install a configuration file : set the current configuration to <name> : optionally, edit configuration Now that the configuration has been completed, use it to authenticate. sas cf auth : perform Cloud Foundry login actions Once authenticated, deploy stemcells, buildpacks, releases, and files. sas bosh upload stemcells sas deploy buildpacks sas deploy releases sas deploy files : if not present, upload the stemcells : upload required buildpacks : if not present, upload the releases : use the JSON configuration to generate deployment files After this, it is important to manually inspect the various manifest files to ensure that they are correct. In addition, this is the time at which you can edit those manifest files to make custom changes. sas deploy services : to deploy the stateful services At this point, it is advisable to check the services. sas show details -S : to perform a health check on the services Next, deploy either all apps or individual apps: sas deploy apps sas deploy app <appname> : to deploy the stateless applications : to deploy a single app such as: identities And, you can check the apps now:

15 Prepare the Installation Environment 11 sas show details -A : to perform a health check on the apps You can use following command to summarize the state of your deployment: sas show info sas show status sas show details : to show configuration, urls, and IP addresses : to show the existence or execution state of all components : to perform a health check on both services and apps components The Help system then repeats the same information displayed when using the command sas help sas. To show product information, run the command: sas show info sas show info Product Name : SAS Visual Investigator Version: : Build Date: : Note: Additional information is displayed after doing: sas conf use <configuration>. Prepare the Installation Environment Overview Before you can deploy SAS Visual Investigator, follow these pre-deployment steps: Collect information about the environment. Set, edit, and save the configuration file. Authenticate the sas user to Cloud Foundry and BOSH. Upload BOSH stemcells. Upload buildpacks. Upload releases. Generate files from configuration data for deployment. The information in the Microsoft Excel spreadsheet CF_Deployment_Questionnaire.xlsx needs to be collected. See Then, during installation, you must manually enter this information in a configuration file. Once the information is collected, enter the following command to list the available SAS Visual Investigator configuration files. sas conf list Here are the results: The following configurations are available: template_openstack template_vsphere To use a configuration, use the command:

16 12 sas conf use <configurationname> Current configuration: unset Set the Configuration File 1 Select the template file (vsphere or OpenStack) that corresponds with the underlying IaaS for your Cloud Foundry installation and run the following command: sas conf use template_xxxxx where xxxxx is either vsphere or openstack. Here is an example of the output: Now using configuration: template_xxxxx 2 Save the template configuration file with a new configuration filename that is meaningful in your environment. The configuration file test is used in this example. sas conf save test This produces the following output: Saved configuration file: test 3 Set the new configuration file as the active configuration file for the framework to use. sas conf use test This produces the following output: Now using configuration: test Edit the Configuration File Once the template is ready to use, edit the configuration file and enter the information from the spreadsheet. See Then, during installation, you must manually enter this information in a configuration file. Note: SAS has configured the vim utility to check JSON syntax for this purpose. You cannot exit the utility if the file contains invalid JSON syntax. Here is an example of the configuration file before editing:

17 Prepare the Installation Environment 13 After you enter the information into the table from Appendix A or the spreadsheet, copy your entries into the configuration file. 1 Copy your entries into the configuration file and ensure that your entries do not contain Rich Text markup. It must contain only ASCII 7 data. Every entry in Appendix A or the spreadsheet corresponds to an entry in the configuration file. 2 Save the configuration file. Here is an example of the configuration file after editing:

18 14 Note: The location of this configuration file that is in use is a temporary location and can easily be overwritten by another configuration file. SAS recommends that you save the configuration file that has been edited. Save the Configuration File To save the changes that you have made to a permanent location, run the following command: sas conf save test This produces the following output: Saved configuration file: test This command does not change the active configuration file. Instead, it saves a copy of it to a saved configuration directory. You can see your configuration name now by running the command: sas conf list This produces the following output: The following configurations are available:

19 Prepare the Installation Environment 15 test template_openstack template_vsphere To use a configuration, use the command: sas conf use <configurationname> Current configuration: test Authenticate to Cloud Foundry and BOSH Now that you have entered the information about your Cloud Foundry installation and the servers to be created, you need to connect to Cloud Foundry. This step is required even if the host bastion box is signed on to Cloud Foundry and BOSH. This step is also required whenever you change your configuration to a new configuration that has different authentication details. To authenticate, run the command: sas cf auth This produces the following output: Authentication for user: sas Current target is (ocfdir) API endpoint: (API version: ) User: test Org: test Space: test If authentication is successful, then you know that the data that you entered for the Cloud Foundry and BOSH environments is correct. If authentication is not successful, refer to the data that you entered for the directory and run-time sections of the configuration file. Correct them for your installation and try again. CAUTION! Do not attempt to proceed beyond this point if you do not have a working connection to both BOSH and Cloud Foundry. Upload the Buildpacks Deploying SAS Visual Investigator applications uses Cloud Foundry buildpacks. To ensure that compatible buildpacks are being used, run the following command: sas deploy buildpacks This produces the following output: sas deploy buildpacks Deploying buildpack sas_java_buildpack... OK Deploying buildpack sas_java_buildpack... Done uploading OK This command uploads offline buildpacks into your Cloud Foundry environment.

20 16 Upload the BOSH Stemcells Once connectivity is established to the BOSH environment, you must upload the required stemcells for the creation of virtual machines (VMs). This is done in the IaaS using the BOSH Cloud Provider Interface (CPI). 1 Check to see whether the required stemcells are already installed. Run the following command: bosh stemcells If the output contains the following information, the correct stemcell is already installed. You can skip the remainder of this section. Name="bosh-openstack-kvm-centos-7-go_agent" Version="3309" 2 If the bosh-openstack-kvm-centos-7-go_agent stemcell is not installed, run the following command: sas bosh upload stemcells Two stemcells are delivered: one each for OpenStack and vsphere. 3 To ensure that the correct stemcells are loaded, even if there are existing stemcells, run the following command: sas bosch upload stemcells If the correct stemcells are already installed, you receive a warning message stating that the correct version already exists. You can safely ignore this message and continue with the upload. Upload the BOSH Releases Now you need to upload the included BOSH releases to the BOSH blob storage so that they are available to BOSH when it is time to deploy the services. To upload the BOSH releases, run the following command: sas deploy releases The following release packages are delivered, one for each of the stateful services. Cloud Analytic Server (CAS) Elasticsearch PostgreSQL 9.4 Consul RabbitMQ PGPool Apache Geode Create the Files for Deployment Once the stemcells, buildpacks, and releases are in place, you must create files that are used in deploying SAS Visual Investigator services and apps. This step should be performed each time there is a change in the active configuration file. If these files have already been generated, then remove them from the container first by running the following commands:

21 Prepare the Installation Environment 17 cd rm -rf * The configuration file provides the values to be substituted into the template files that are part of the framework. To create the file system and files, run the following command: sas deploy files As the command runs, it copies the JAR files that are deployed into Cloud Foundry. Then it performs the token substitution on the various files that are required for deploying the solution. When file system creation is complete, token substitution is checked to determine whether there are any unresolved tokens. If tokenization is successful, the message All tokens successfully resolved is displayed. If tokenization is incomplete and an error message is shown, the configuration file is incomplete and needs to be edited again. Note: Be sure to remove the files that were generated before running the command sas deploy files again. Preparing to Examine the Files Examination of the BOSH and Cloud Foundry manifest files is required in order to verify that the information in the files is correct. You must have knowledge about the Cloud Foundry environment and the vim utility. Note: Do not change the information in the manifest files manually because the data comes from the configuration file. Any changes should be made to the configuration file. The contents of the home directory should then be deleted, and the command to deploy files should be rerun to create a new set of manifest files. Examine the Files Related to BOSH The manifest files that deploy stateful services into the BOSH managed environment are located in the /home/sas/services directory in the container. To examine the manifest files: 1 Change to the /home/sas/services directory. 2 Run the following command to display the vim editor: vi */man*.yml. This displays the vim editor in the window, with the first file in the vim buffer. Use the vim :n command to edit the next file match. Use the :rew command to rewind to the beginning if you want to review all files again. Note: It is acceptable to change the configurable entries in the jobs section of the manifest.yml file, which is in the Postgres directory under the services directory. They are intended to be managed outside the framework When examining the manifest files, check the following items: director_uuid make sure this matches what was entered in the configuration file. Make sure that all entries in the networks section of the file are correct. Validate that the IP address is the correct one entered for each server. Look under jobs and then static_ips. Once you have examined the BOSH manifest files, examine the script files in the services directory. To examine the script files: 1 Change to the /home/sas/services directory. 2 Run the following command to display the vim editor: vi */*.sh. This displays the vim editor in the window.

22 18 The most important script in this group is the post_deploy_consul.sh script. In this file, check for empty values ("") and determine whether an empty value is reasonable. Some expected empty values include the archive.storage.local.destination property and in the Folder loop at the bottom of the file. A property with an empty value might indicate that a JSON property in the configuration file was not filled in. If you discover any entries like this, return to the configuration file and make sure that all required entries are filled in. Then delete the contents of the home directory and re-create the files. Note: The following service_tag parameters are blank for all environments: elasticsearch/deploy.sh service_tags, postgres/deploy.sh service_tags, and rabbitmq/deploy.sh service_tags. This is standard and can be ignored. Note: If you are using OpenStack, the static_ips addresses in the cas-worker.yml and manifest-data.yml files are blank. This is standard for OpenStack and can be ignored. Examine the Files Related to Cloud Foundry Manifest files that deploy stateless applications and microservices into the Cloud Foundry run-time environment are located in the /home/sas/apps directory in the container. To examine the manifest files: 1 Change to the /home/sas/apps directory. 2 Run the following command to display the vim editor: vi */man*.yml In these files, check for empty values ("" ) and determine whether an empty value is reasonable. This might indicate that a JSON property in the configuration file was not filled in. If you discover any entries like this, return to the configuration file and make sure that all required entries are filled in. Then delete the directories under the /home/sas directory and re-create the files. Using Logs Log data for applications and microservices is provided through the Cloud Foundry Loggregator system. Using a Cloud Foundry firehose and nozzle to collect log data and redirect it to a logging server is the standard means of providing access to application logs. The rsyslog log has been added to the services deployed in Cloud Foundry BOSH. This information can be routed to any rsyslog server over TCP. This method is compatible with any of the various log store and display applications. Install SAS Visual Investigator Overview Deployment of SAS Visual Investigator consists of the following: deploying services to BOSH deploying stateless applications and microservices

23 Install SAS Visual Investigator 19 Deploy Services to BOSH To deploy the stateful services to BOSH, run the following command: sas deploy services When deployments are complete, test the applications to ensure that the deployment is working as expected. For more information, see Validating the Deployment on page 21. CAUTION! Do not attempt to proceed to the next steps if you see any errors during the deployment of the stateful services. If you see errors, see Appendix B: Troubleshooting on page 61 Deploy Stateless Applications and Microservices To deploy the stateless applications and microservices, run the following command: sas deploy apps This is similar to the command that deploys the stateful services. The sas deploy apps command runs the deploy.sh script in the /home/sas/apps directory. This script executes each of the deploy.sh scripts in the subdirectories under the apps directory. These scripts deploy application JAR files into the Cloud Foundry runtime environment. When the deployments are complete, run the following command to display the status of the full deployment: sas show status Note: The preceding command combines three different commands bosh deployments, cf apps, and cf routes to display information that describes the current environment. Also, use the following command to display information about the applications that are deployed. sas show info It also displays the URLs that enable you to connect to the application interfaces, and it displays information about the environment. All of the information displayed comes from the configuration file and is formatted for readability. Here is typical output: SAS Visual Investigator: Info Product Name : SAS Visual Investigator Version: : 10.1.nnn Build Date: : Day Mon YY HH:MM:ss EDT 2016 Configuration JSON Configuration Org Space Host URLs SAS Visual Investigator Consul RabbitMQ : test : test : test : test : : : IP Addresses

24 20 CAS Controller : CAS Worker : Consul : Elastic Search : Master Nodes : Client Nodes : Data Nodes : PostgreSQL : RabbitMQ : Another way to quickly display the status of a stateful service or application is to use the following command: sas show details Here is typical output: Service Status pass cas-controller (Success) pass cas-worker@ (Success) pass cas-worker@ (Success) pass consul_container (Agent alive and reachable) pass elasticsearch (TCP connect :9200: Success. ElasticSearch cluster green.) pass postgres (Success) pass rabbitmq (Success) App Status pass audit (UP) pass authorization (UP) pass casmanagement (UP) pass datahub (UP) pass entityresolution (UP) pass feature (UP) pass files (UP) pass identities (UP) pass networkanalytics (UP) pass SASLogon (UP) pass SASVisualInvestigator (UP) pass svi-ai (UP) warn svi-alert (DOWN) pass svi-core (UP) pass svi-sand (UP) pass svi-transport (UP)

25 21 Validating the Deployment 5 Overview Elasticsearch Consul RabbitMQ PostgreSQL Overview This section provides instructions for validating the stateful services that are delivered with SAS Visual Investigator. Elasticsearch To validate the installation of the Elasticsearch cluster, run the following command: curl -XGET ' Elasticsearch-IP-address:9200/_cluster/health?pretty=true' Here is typical output: { } "cluster_name" : "testcluster", "status" : "green", "timed_out" : false, "number_of_nodes" : 2, "number_of_data_nodes" : 3, "active_primary_shards" : 5, "active_shards" : 10, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards": 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch": 0, "task_max_waiting_in_queue_millis": 0, "active_shards_percent_as_number": 100 The green status value indicates that the cluster s overall operation is good. For additional information about Elasticsearch cluster health, see For additional Elasticsearch information, see

26 22 Consul To validate the installation of Consul: 1 Open a web browser and go to the URL for Consul. 2 To determine the correct URL for Consul, run the following command: sas show info SAS Visual Investigator: Info Product Name : SAS Visual Investigator Version: : Build Date: : Wed Jun 22 17:48:41 EDT 2016 Configuration JSON Configuration Org Space Host URLs SAS Visual Investigator Consul RabbitMQ : test : test : test : test : : : IP Addresses CAS Controller : CAS Worker : Consul : Elastic Search : Master Nodes : Client Nodes : Data Nodes : PostgreSQL : RabbitMQ : From the preceding output, select the URL for Consul. In this example, the URL is :8500. RabbitMQ To validate the installation of RabbitMQ: 1 Open a web browser and go to the URL for RabbitMQ. 2 To determine the correct URL for RabbitMQ, run the sas show info command. From the previous example, the correct URL would be

27 Overview 23 PostgreSQL The simplest way to validate the installation of the PostgreSQL server is to connect to a remote database. To determine the IP address of the PostgreSQL server, run the sas show info command. From the previous example, the IP address would be Then run the following command to validate the PostgreSQL server: psql -h U dbmsowner postgres Password for user dbmsowner: psql (9.2.15, server 9.4.4) WARNING: psql version 9.2, server version 9.4. Some psql features might not work. Type "help" for help. postgres=# To exit, specify \q and then press the Enter key.

28 24

29 25 Contact SAS Technical Support 6 Contact SAS Technical Support Contact SAS Technical Support Technical support is available to all customers who license SAS software. However, we encourage you to engage your designated on-site SAS support personnel as your first support contact. If your on-site SAS support personnel cannot resolve your issue, have them contact SAS Technical Support to report your problem. Before you call, explore the SAS Support website at support.sas.com/techsup/. This site offers access to the SAS Knowledge Base, as well as SAS communities, Technical Support contact options, and other support materials that might answer your questions. When you contact SAS Technical Support, you are required to provide information, such as your SAS site number, company name, address, and phone number, that identifies you as a licensed SAS software customer.

30 26

31 27 Appendix A: Cloud Foundry Deployment Information 7 Cloud Foundry Deployment Data Using vsphere as the IaaS Cloud Foundry Deployment Data Using OpenStack as the IaaS Cloud Foundry Deployment Data Using vsphere as the IaaS SYNTAX CONVENTIONS #========================================================================== Syntax Description " " A quoted string of the indicated type. [ ] An array of comma-separated values of the indicated type. <name> *<size>* All occurrences of <name> can be replaced with the same replacement value. All occurrences of *<size>* can be replaced with a similar value or a larger value. The exact size depends on how the resource is used. For a size value in the following configuration table, ensure that the value for your instance_type definition is not less than the values that is used for CPU, disk, or RAM as follows: Size Property *<small>* *<medium>* *<large>* *<xlarge>* *<2xlarge>* Specify the Default Size or a Large Size, as Appropriate 2 vcpus, 20 GB disk, 2 GB RAM 4 vcpus, 40 GB disk, 4 GB RAM 4 vcpus, 40 GB disk, 8 GB RAM 8 vcpus, 40 GB disk, 8 GB RAM 8 vcpus, 40 GB disk, 8 GB RAM

32 28 # A 'property' is a simple key-value pair. # A 'section' is either an array or a dictionary that can have many values. # # All properties and sections below must be populated with data unless marked with one of the following indicators: ## Optional - This property or section can remain with no value or can be entirely removed. ## ReadOnly - Do not change any property or section that has this mark. ## ReadOnlyKey - Do not change the property key, but you can change the value. The Value column does not list a default value in some instances. This is intentional so the user can provide customized values. Key Value Description BOSH Director directors <directorname> username username password certificate_path privateip uuid vm_network_name bosh_domain_name dnsserver[ ] gateway The BOSH Director section of the JSON configuration file provides information for accessing the BOSH directors. The director Name that is displayed by the bosh status command and that is listed as Name. The BOSH user name that is used for BOSH director authentication. The BOSH user name that is used for BOSH director authentication. The password for the user that connects to the BOSH director. The certificate for the user that connects to the BOSH director. The IP address of the BOSH Director that is displayed by the bosh status command and that is under the URL. The UUID of the BOSH director that is displayed by the bosh status command and that is listed as uuid. The vsphere network name under which the BOSH instances are created. The domain name of the BOSH director that is displayed by the bosh status command and that is listed as DNS. The array of quoted IP addresses that identify the DNS locations for the BOSH director. Example: [" ", " "]. The IP address of the Gateway server of the BOSH Director.

33 Cloud Foundry Deployment Data Using vsphere as the IaaS 29 Key Value Description cidr_network reserved_network static_network The CIDR range of the network. Example: " /24". The reserved IP address range that is not used for creating the BOSH instances. The format of each array entry is a quoted string that consists of a hyphenseparated IP address range. Example: [" ", " "]. The static IP address range that is used for creating the BOSH instances. The format of each array entry is a quoted string that consists of a hyphen-separated IP address range. Example: [" ", " "]. Cloud Foundry Run-Time Environment runtimes <runtimename> url username password The Cloud Foundry Run-Time Environment section of the JSON configuration file provides information for accessing the Cloud Foundry run-time environment. The name of the run-time environment that is displayed by the bosh deployments command and that is listed as Name. The URL of the Cloud Foundry run-time environment that is displayed by the cf api command. The Cloud Foundry run-time environment admin user name that is used for authentication. This user must have admin privileges in order to create domains and routes. The password for the user connection to the Cloud Foundry run-time environment. options --skip-ssl-validation The command-line options for the Cloud Foundry runtime environment connection. Solution Deployment deployments sas password The Solution Deployment section of the JSON file contains solution deployment details. This section provides information about the user ID that is used for solution deployment. The password for the user of the solution deployment. Do not provide a password in this file. It is entered on-site. iaas vsphere The Infrastructure as a Service (IaaS) name for vsphere. runtime <runtimename> The name of the Cloud Foundry run-time environment that is defined in the Cloud Foundry Run-Time Environment section. director <directorname> The name of the Cloud Foundry BOSH director that is defined in the directors section.

34 30 Key Value Description The following three properties specify the top-level domain (TLD) that is a Cloud Foundry Shared or Private domain. Note: All three of these properties must resolve to the Cloud Foundry HAProxy. cf_nontls_domain front_tls_domain front_nontls_domain label org space This is the internal non-tls domain that resolves directly to the Cloud Foundry HAProxy. If TLS front-end reverse proxying or load balancing is added by the customer, then it is necessary to specify the front-end TLS domain name. If used, this top-level domain can indirectly resolve to the Cloud Foundry HAProxy. If non-tls front-end reverse proxying or load balancing is added by the customer, then it is necessary to specify the front-end non-tls domain name. If used, this top-level domain can indirectly resolve to the Cloud Foundry HAProxy. This property identifies a unique deployment. The use of label in this context refers to a word or set of characters that is placed before the top level domain name (non-tls Domain name). This name immediately precedes the toplevel domain property following in Logging Properties > Domain cell. This name can be used to identify the deployment purpose, the function, or the intended audience of the deployment. It can also be a name that has no obvious meaning. From a deployment perspective, this name is needed to uniquely construct URLs that access a specific deployment. The name of the Cloud Foundry organization that is the target of the deployment. The name of the Cloud Foundry space that is the target of the deployment. LDAP Server ldap type base host password The LDAP Server section of the JSON file provides information about the defined LDAP AD connection. The string must match either ActiveDirectory or OpenLDAP. This section provides base OU information for the LDAP AD (Active Directory) connection. The LDAP server host name. The credentials for the user ID of the solution installation that connects to the LDAP/AD server. The credentials are entered on-site. Do not enter passwords in this file, they will be entered on-site. <Password terminology>.

35 Cloud Foundry Deployment Data Using vsphere as the IaaS 31 Key Value Description port userdn The port that is defined to connect to the LDAP server. If a global port is used to connect to the LDAP server, then port 3268 is required. If a non-global port is used to connect to the LDAP server, then port 389 is required. The LDAP user DN value that is used for the general search account. The DN value can be in the form: "CN=, OU=, OU=, DC=, DC=, DC=". Note that each site is different. LDAP Group Information group basedn searchfilter The LDAP Group Information section of the JSON file specifies group information for the LDAP/AD connection. The LDAP base DN in the form OU=Groups,DC=xxx,DC=yyy,DC=com. The optional LDAP search filter that is used for searches on the LDAP server. Example: samaccountname={0}. LDAP Connection user basedn searchfilter The LDAP Connection section of the JSON file specifies user information for the LDAP/AD connection. The LDAP base DN is in the form DC=xxx,DC=yyy. The optional LDAP search filter that is used for searches on the LDAP server. Example: samaccountname={0}. Internal SAS profile The Internal SAS section of the JSON file is internal to SAS. file ldap/ldap-search-and-bind.xml Use the provided information that is required internal to SAS microservice. Connection Properties property <property name> "config/application/ldap/user/ customfilter": "" The Connection Properties section of the JSON file specifies any special properties that are required for connection to the LDAP/AD server. Define the custom Consul properties for LDAP. At the present time, the only supported property is the customfilter property that is listed. This property can be entirely omitted if no custom Consul properties are needed for LDAP. If this property is used, then the key must match config/application/ldap/user/customfilter: " ". Example: "(&(!(objectclass=computer))(! (useraccountcontrol: :=2)))." Tenancy

36 32 Key Value Description tenancy userrdn The Tenancy section is for information that is required for managing tenancy through the LDAP/AD server. Example "ou=people". Consul Scripts oauth adminsecret The Consul Scripts section of the JSON file is used by scripts that load data into Consul. The password is used to obtain an access token from SASLogon for client registration. Do not provide a password in this file. It is entered on-site. Logging Properties log_server host The Logging Properties section of the JSON file defines logging properties that are used by services that send log data output to a remote rsyslog server via TCP. To enable logging support for apps, a nozzle must be created that logs output to a remote rsyslog server. A nozzle is a component that listens for specified events and metrics and streams this data to external services. Refer to the Cloud Foundry Loggregator documentation for details about nozzles. Cloud Foundry nozzle and the rsyslog server must exist prior to the deployment. This functionality is not included with this deployment code. The fully qualified domain name (FDQN) or the IP address of the rsyslog server in the format: <host>.<toplevel-domain>. Example: rsysloghost.mycompany.com port 5000 The TCP port number of the rsyslog server. Example: Change the value, as appropriate. domain This is the top-level domain name of the rsyslog server. This is only <top-level-domain>, not <host>.<top-leveldomain>. Example: mycompany.com. Fallback Logging