Management Agent (Worker)
About the Worker
To deploy VMs and run applications on VMs that use the CloudCenter platform (called worker VMs), you need a Management Agent (software installed on the worker to communicate with the Workload Manager) to be installed on each worker VM.
When the VM first boots up, the worker communicates with the bundle store to download the latest version of the agent and then start the agent. Once the Management Agent is started, it needs access to the Cisco hosted bundle store () or to your locally-installed custom bundle store to download and start the service.
The Worker image provided or shared by Cisco contains the agent pre-installed using the CentOS 6 operating systems for some supported clouds. A Worker image becomes fully functional after you deploy the Worker VM to the cloud.
See Options to Install the Worker for details on how you can install the worker.
Management Agent Tasks
The Management Agent communicates with the CloudCenter Suite cluster, either directly or through Cloud Remote, and receives instructions to perform the following tasks:
Complete application deployment tasks
Perform provisioning tasks (for example running configuration scripts)
Run custom cleanup scripts (for example to de-provision or shutdown applications)
Enforce policies (for example, to reconfigure middle ware service during auto-scaling)
Collect system metrics based on policy requirements
Monitor data, provide status updates, and keep alive system heartbeats.
The Management agent (also called the agent) can be used in two modes.
Deployed by Workload Manager
Question: Is the Management Agent required?
Answer: You do not need to install either the Management Agent in the following cases:
If a service is defined as agentless (without an agent, see Custom Service Definition for additional details), then the applications running these services do not require an agent to be installed.
If you don't run custom scripts on imported VMs, you can continue use these VMs without installing the Management Agent.
Question: How is the Management Agent different from the AgentLite?
Answer: The legacy management agent used in CloudCenter Platform 4.x is no longer available. AgentLite was the interim lightweight agent that was used in CloudCenter Suite 5.0. Effective CloudCenter Suite 5.0, the term Management Agent refers to the agent that works in either Brownfield or Greenfield modes. The term AgentLite is no longer used in documentation. If you have a legacy agent installed, you can always update it to the CloudCenter Suite 5.x Management Agent.
Question: Why is the Agent installed on Worker VM as part of Application deployment?
Answer: An agent is required to support on-demand actions and lifecycle actions defined in the Actions Library, service definition and application profile.
Question: How does the worker get installed on a Workload Manager deployed VM?
Answer: Two ways:
Create a pre-bootsrapped image: Use the worker installer for Linux or Windows, depending on your base OS, to manually create an image with the worker fully installed. Cisco also provides a Centos 6 pre-bootstrapped image as an appliance.
Dynamic Bootstrapping Injection: When your VM-based application is launched in clouds that support an init string, Workload Manager passes an init string to the cloud provider that contains the first script needed in the worker install process. The cloud provider injects the script into the VM at deploy time. The script then executes when the VM is started and installs the worker.
Question: How does the agent communicate with the CloudCenter Suite cluster?
Answer: Once the agent is installed, it needs to connect with the AMQP service in the CloudCenter Suite cluster. If the worker VM cannot initiate this connection due to firewall restrictions, you must install Cloud Remote (Conditional).
Question: Which files are created as part of the agent installation process?
Answer: The list of file created as part of the agent installation process differs for Linux and Windows installations. See the Deployment Lifecycle Scripts > Lifecycle Action Script Definition for additional context.
Question: Why is cliqruser permission required to run some scripts?
Answer: By default, key-based authentication is configured using cliqruser permission – this user refers to the OS user in the Application VM (Worker). See the Deployment Lifecycle Scripts > Lifecycle Action Script Definition for script-specific details on when cliqruser permission is required.
Question: Why does the agent program retain files in the C:\temp and C:\ directories?
Answer: Some deployment scripts like resumeScript or reboot or restore take effect based on information retained in these directories. These scripts require information from those files to function as designed. Each script, the level at which it is defined, the script download location, the user running the script, and the location from which the script is run in provided in detail in the Deployment Lifecycle Scripts > Lifecycle Action Script Definition section for both Linux and Windows environments.
Question: Does the worker installer for Windows install any open source tools on Windows workers?
Answer: No, the Window worker installer does not install any open source tools on Windows. It does, however, install ccc_unarchiver, a proprietary tool to open TAR files.
Question: How are application services different from the services created by the agent installation process?
Answer: The agent services and application services are independent of each other.
Agent Services: Specific to the agent installer. When you install the agent, the Agent installer installs some services to help with the installation and maintenance of the management agent. These files include the CliQr Installer Service, Agent Service, and other services mentioned in Question 4 in this section.
- No labels