Continuing our blog series on Citrix Lifecycle Management, in this post we would like to answer some of the frequently asked questions about Citrix Lifecycle Management.
For an introduction to Citrix Lifecycle Management please read our blog: Radically Simplify Management of Citrix Workloads and Enterprise Application Lifecycles.
Now, lets take a look at the frequently asked questions for Citrix Lifecycle Management.
What is Citrix Lifecycle Management?
Citrix Lifecycle Management is a comprehensive cloud-based service lifecycle management solution to accelerate and simplify the design, deployment and ongoing management of Citrix workloads and enterprise applications.
In simple terms, Citrix Lifecycle Management is software hosted by Citrix in the cloud that you can access from anywhere on any device. You use it to automate several tasks including: deployment of Citrix software like Citrix XenApp, or other enterprise applications to public or private clouds, virtualized infrastructure or behind your firewall in your datacenter. Once deployed, you can easily perform monitoring, management and upgrading.
For Citrix workloads such as XenDesktop, XenApp, XenMobile and NetScaler, Citrix Lifecycle Management provides the following benefits:
- Automated deployment and configuration of Citrix and enterprise applications using pre-validated blueprints
- Simplified management of workloads across virtual or private and public cloud infrastructures
- Easy-to-use tools for monitoring and managing workload performance and availability
- Automated upgrades from older to new versions
How is Citrix Lifecycle Management delivered?
Citrix Lifecycle Management will be delivered as a service through the Citrix Workspace Cloud, at http://workspace.cloud.com. You can sign up for a free Workspace Cloud account or sign in to request a trial for the Lifecycle Management service.
Virtualization and Cloud Management
Which virtualization and cloud platforms does Lifecycle Management support?
Lifecycle Management supports the following virtualization and cloud platforms out of the box:
- Amazon EC2 (Amazon Web Services)
- Citrix CloudPlatform 4.3
- Citrix XenServer 6.2 and 6.5
- VMware vSphere 5.1, 5.5, and 6.0
- Microsoft Hyper-V Server 2012 R2
- Microsoft Azure
My virtualization or cloud environment is behind a firewall. How does Citrix Lifecycle Management communicate with it?
If your virtualization or cloud environment is behind firewall, a machine that acts as a connector is required for Citrix Lifecycle Management to connect to it. This machine must have Internet access and be able to communicate with your environment. To configure a machine to be a connector, you first install the Lifecycle Management Agent on the machine and then select and promote the machine to be a connector when you add your virtualization or cloud environment to Lifecycle Management.
What ports do I need to provide for the Lifecycle Management agent to connect?
Lifecycle Management understands that the security of your technical environment is paramount. We take very seriously your concerns regarding exposure over public networks. For this reason, the Lifecycle Management Agent has been carefully designed to communicate securely over outbound HTTPS only. The only time that inbound access through the firewall may be necessary is to auto-install the agent over SSH port 22 on Linux and over RDP port 3389 on Windows. After the agent is installed, the port can be shut down and Lifecycle Management communicates exclusively over outbound HTTPS.
Note: The agent needs direct communication to Lifecycle Management after installation. The agent does not communicate with Lifecycle Management through the connector even if one is configured for your environment.
Do I have to install agent as root or administrator?
For manual installation on Linux, the agent must be installed under the root account. For manual installation on Windows, the agent must be installed using a local Administrator account. If the default local Administrator account has been disabled, you must modify the agent to run as the administrator-enabled user.
Note: The agent can run as any sub-user once installed as root on Linux or Administrator on Windows to avoid executing operations as the superuser (if desired) for the operating system.
Catalog and Blueprint Deployment
How do I deploy a blueprint from the Citrix catalog?
First, you need to add blueprints from the Blueprint Catalog to your personal library. Then you can deploy blueprints from your personal library. Make sure you have at least one virtualization or cloud environment added prior to deploying blueprints.
How do I know that my blueprint has deployed successfully?
When you deploy a blueprint from the Library, you receive an email notification. You will receive another email notice when the deployment finishes. To view the status of your deployment in progress, go to the Manage area to view the deployment details, including current status.
Which virtualization or cloud environment can I use to deploy a blueprint?
You can deploy blueprints into any virtualization or cloud environment you have added to Lifecycle Management as long as the blueprint supports these environments. For details of which virtualization or cloud environment a specific blueprint supports, select the blueprint from the Blueprint Catalog and click View Info.
How can I collaborate with others on my deployments?
To collaborate with another user, you first need to add him or her to your account by clicking Resources & Settings -> Users > Add User.
After you add the user to your account, you can select a blueprint from your Library and share it with that user. Users sharing a blueprint are working on the same object. So, any changes and any subsequent deployments of the blueprint will be visible to all users who are sharing the blueprint.
Stay tuned for additional blogs where we will cover some more Lifecycle Management Questions.
Haven’t tried Citrix Lifecycle Management yet? Start your free trial today and let us know what you think of Citrix Lifecycle Management. We may include any additional questions in a follow-up blog as well.