6.2
Table Of Contents
- Using Application Services
- Contents
- Using Application Services
- Updated Information
- Introducing Application Services
- Install and Configure Application Services
- Installing Application Services
- Preparing to Install Application Services
- Start the Application Services Appliance
- Troubleshooting Problems Connecting to the Application Services Web Interface
- Unlock Your darwin_user Account
- Restart Application Services
- Configure Application Services to Use a Proxy for External URLs
- Register Application Services to vRealize Automation
- Upgrading Application Services
- Setting Up Users and Groups
- Using Tenants and Business Groups in Application Services
- Import Predefined Content to a Tenant
- Using the Application Services Web Interface
- Setting Up Application Provisioning for the Application Services Environment
- Virtual Machine Requirements for Creating vRealize Automation Custom Templates
- Creating Virtual Machine Templates in vRealize Automation
- Updating Existing Virtual Machine Templates in vRealize Automation
- Register the vRealize Automation Cloud Provider and Template
- Create a vRealize Automation Deployment Environment
- Setting Up Application Provisioning for the vCloud Director Environment
- Virtual Machine Requirements for Creating vCloud Director Custom Templates
- Creating Windows Virtual Machine Templates in vCloud Director
- Create Linux Virtual Machine Templates in vCloud Director
- Verify Cloud Template Configuration from the vCloud Director Catalog
- Updating Existing Virtual Machine Templates in vCloud Director
- Exporting Virtual Machine Templates with OVF Format
- Register the vCloud Director Cloud Provider and Template
- Create a vCloud Director Deployment Environment
- Setting Up Application Provisioning for the Amazon EC2 Environment
- Developing Application Services Components
- Managing the Application Services Library
- Creating Applications
- Working with Artifacts
- Deploying Applications
- Setting Up and Configuring a Deployment Profile
- Deploying with Deployment Profiles
- Publishing Deployment Profiles to the vCloud Automation Center Service Catalog
- Request a vRealize Automation Service Catalog Item
- Using the Deployment Summary Page
- Using the Composite Deployment Summary Page
- Understanding the Deployment and Update Process
- Understanding Deployment Failures
- Updating Application Deployments
- Initiate an Update Process to Scale Out Deployments
- Initiate an Update Process to Scale In Deployments
- Initiate an Update Process to Modify Configurations
- Use an Existing Update Profile
- Promote an Update Profile
- Rollback an Update Process
- Understanding Run Custom Task Update
- Troubleshoot Failed Update Process to Scale Deployments
- Troubleshoot Failed Update Process to Modify Configuration
- Deploying Predefined Library Components
- Managing Deployments
- View Deployment Task and Blueprint Details for an Application
- View Deployed VM Details and Execution Plan of an Application
- Start a Policy Scan
- Tear Down an Application from the Cloud
- Scale In Deployments from vCloud Automation Center
- Scale Out Deployments from vCloud Automation Center
- Tear Down an Application from vCloud Automation Center
- Delete an Application Deployment from Application Services
- Cancel a Deployment or an Update Process
- View Policy Compliance Summary
- Using the Application Services CLI
- Using the CLI Import and Export Functions
Property Description
puppet_version Puppet Enterprise suite version for a Puppet Enterprise and Puppet package
version for a Puppet open source.
For example, the Puppet Enterprise version is 3.2.3 and the Puppet open source
version is 3.6.2.
mc_messaging_server_username User name corresponding to the config setting plugin.activemq.pool.1.user in the
MCollective server config file.
For example, the MCollective server config file in the Puppet Enterprise is located
at /etc/puppetlabs/mcollective/server.cfg .
mc_messaging_server_port Port corresponding to the config setting plugin.activemq.pool.1.port in the
MCollective server config file.
For example, the MCollective server config file in the Puppet Enterprise is located
at /etc/puppetlabs/mcollective/server.cfg .
node_manifest_dir Directory where the node definition manifests are located for virtual machines
deployed using Application Services.
The Puppet Master site.pp must be able to import *.pp files from this directory.
mc_appd_agent_ddl Location of the MCollective Application Services agent DDL file.
You do not need to override this value.
mc_client_setup_script Location of the MCollective Client setup Beanshell script.
You do not need to override this value.
global_conf URL to download the Darwin global configuration for each node.
agent_post_install_wait Time in seconds to wait after installing the agent.
7 In the Agents section, enter the required values.
Option Description
pe_installer_payload_base_path Base URI where the operating system and architecture specific Puppet Enterprise
tar files are hosted. Not for Windows.
The script detects the URI based on the pe_installer_payload_base_path and the
current version of operating system and architecture on the machine. You can
skip this auto detection by specifying a value for the pe_installer_payload
property. Automatic detection assumes that the specific directory structure mirrors
the structure of the Puppet Labs hosted tar files that are located at
https://s3.amazonaws.com/pe-builds/.
installer_payload_base_path Windows version of pe_installer_payload_base_path.
is_enterprise Indicates if the Puppet Master being registered is a Puppet Enterprise with a
value set to true or a Puppet open source with a value set to false.
Using Application Services
VMware, Inc. 71