Install Worker on a Windows Image
This procedure may differ based on your cloud and your Windows version. This procedure provides a point of reference to install the WINDOWS_WORKER_OS_VERSION image.
The Management Agent is now a Go-based agent and introduces the following differences:
Earlier CloudCenter releases, the agent used a Java-based installer and installing Java on Application VMs was a requirement. CloudCenter 4.10.0 uses a Golang-based agent and removes the requirement to have Java on Application VMs, unless the applications themselves need Java.
Approximately 95% of the space needed by the agent is reduced (down to ~7Mb from ~200Mb) with this strategy and the delay when the node is booting (in the Deployment Details page) is considerably reduced. You will also see a substantial reduction in CPU/Memory usage on Application VMs.
Logs are now verbose and you will see additional status messages in the Deployment Details page.
The CloudCenter platform no longer uses the node metadata service, JVM, and Jetty on Worker VMs by default. See the 4.10.0 release notes for the change announcement.
Be aware that the screenshots may differ depending on your version of Windows.
A lightweight agent, called AgentLite (agentlite or agent-lite), can be installed on VMs that have been imported into CloudCenter. This agent is an alternate option for VMs that do not require the capability to launch applications but do require some basic CloudCenter functionality like performing platform actions. If installed, the Virtual Machines page and the VM Details page display the icon and version. See VM Management > AgentLite for additional details.
- vCD Installation Nuances
Install CliQr Tools on the application VM.
Stop the VM.
Edit the settings for this VM and be sure to remove the NIC(s).
Save the VM as a template into the vCD catalog of your choice.
- VMware Installation Nuances
To use VMware VMs, you should have already installed VMware tools on the Windows machine.
To install CloudCenter Tools on a Windows image, follow this procedure:
Contact CloudCenter Support to obtain the installer package (cliqr_installer.exe).
You can only install the installer.exe package once – you must use a clean image and perform a fresh install.
Launch a base Windows image from the Cloud Provider Console. The following image is an example for OpenStack.
CloudCenter requires PowerShell 4.0 or above on W2k12R2 or W2k16. Verify that you are running the correct version of PowerShell:
Verify that the
C:\PROGRA~1path is resolvable to
Otherwise, you must create the corresponding link:
Download CloudCenter Tools as directed by CloudCenter Support.
- Go to the command prompt window and run the downloaded file:
C:\<path to the file>\cliqr_installer.exe /CLOUDTYPE=openstack (or other cloud) /CLOUDREGION=default
(The other cloud options are: amazon, azurerm, azurestack, azurepack, google, openstack, opsource, softlayer, vcd, vmware, cisco)
Run the Installer. You may add the IIS installation (depends on your deployment).Additional steps if using Windows 2016 Image on AWS
Additional steps if using a Windows Azure Image
Recently, AWS has changed its metadata script execution behavior, and custom images will not work out-of-box
To execute the scripts while launching the image, the following extra step is required if configuring a Windows 2016 application VM image on AWS.
Before creating this image run the following scripts PowerShell.
The following extra steps are required if configuring W2k12R2 or W2k16 application VM image in Azure.Windows 2012 R2 worker image in Azure
Open Server Manager and start/open the Add Roles and Features Wizard.
Click Next at the Before you begin pane.
Select Role-based or feature-based installation on the Installation type pane and click Next .
Select the Select a server from the server pool option in the Server Selection pane.
In the Server Roles pane, select Web Server (IIS), and add all roles under Application Development.
Click Next to proceed to the Features pane.
In the Internet Information Services pane, expand Web Management Tools, and select IIS Management Console.
- Select Add Features and select:
.NET Framework 3.5 Features, add .NET Framework 3.5
.NET Framework 4.5 Features, add ASP.NET 4.5
Remove the installer.exe file.
- Go to Control Panel > System and Security > System > Allow Remote Access. Uncheck the check box to Allow connections only from computers running Remote Desktop with Network Level Authentication. This action allows you to RDP into the VM from the CloudCenter UI.
In the file explorer go to C:\Windows\System32\Sysprep. Double click on sysprep. Make sure you choose the options displayed in the image below. Once sysprep is done, your RDP session will terminate
Go to the Azure Management UI and shutdown the application VM image.
After installing the agent, verify the post-installation information.
If this information remains unverified, be aware that the agent may not be successfully installed.
Ensure that the Golang-based agent Service is up and running. Set set both the CliQr Startup Service and the Golang-based Agent Service start up to Automatic(Delayed Start).
Capture an image of the Worker VM.
After creating the image, include the Image ID in the CloudCenter logical image (CCM UI > Admin > Images > Manage Cloud Mapping > Add/Edit Mapping). See Cloud Mapping for Images for additional context).
You have now mapped your Windows image to the cloud.
Back to: Worker (Conditional)
- No labels