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
agent_run_interval How frequently the puppet agent applies the library. The default run interval is
every 30 minutes (30m). You can specify the run interval in the following units.
n
Seconds. For example, 30 or 30s.
n
Minutes. For example, 30m.
n
Hours. For example, 6h.
n
Days. For example, 5d.
n
Years. For example, 2y.
A run interval of 0 tells the puppet agent to run continuously.
identity_private_key Private key of the certificate issued to the Application Services server by the
Puppet Master.
Application Services uses this certificate for authentication with Puppet Master
and MCollective. The format of the certificate is PEM encoded including the
header and trailer. The header for example is formatted as, '-----BEGIN RSA
PRIVATE KEY--'
Copy contents of the file TempCredsDir/private_keys/Name.pem you created to
prepare the Puppet Master, as the value for this property.
identity_public_cert The X509 certificate corresponding to the identity_private_key property.
The format of the certificate is PEM encoded including the header and trailer. The
header for example is formatted as, '-----BEGIN CERTIFICATE--'
Copy contents of the file TempCredsDir/certs/Name.pem you created to prepare
the Puppet Master, as the value for this property.
ca_cert The X509 certificate of the certificate authority that issues digital certificates used
to authenticate with Puppet Master and MCollective.
The format of the certificate is PEM encoded including the header and trailer. The
header for example is formatted as, '-----BEGIN CERTIFICATE--'
Copy contents of the file TempCredsDir/certs/ca.pem you created to prepare the
Puppet Master, as the value for this property.
mc_servers_shared_cert Shared server certificate or public key for the MCollective cluster.
The format of the certificate is PEM encoded including the header and trailer. The
header for example is formatted as, '-----BEGIN CERTIFICATE-----' or '-----BEGIN
PUBLIC KEY--'
Copy contents of the file TempCredsDir/certs/pe-internal-mcollective-servers.pem
for Puppet Enterprise or TempCredsDir/certs/mcollective-servers.pem for Puppet
Open Source you created to prepare the Puppet Master, as the value for this
property.
The trailer for example is formatted as,' -----END CERTIFICATE-----' or '-----END
RSA PUBLIC KEY--'
mc_messaging_server_password Password corresponding to the config setting plugin.activemq.pool.1.password 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 .
identity_cert_name Name of the identity certificate.
This name is the string which you set when you generated the Application
Services certificate to correspond to the Puppet Master during the preparation of
the Puppet Master.
Using Application Services
VMware, Inc. 70