Introduction to Cloud Technology
What Cloud products does Citrix have?
Why deploy XenApp/XenDesktop in a Cloud?
Deep dive: XA/XD on Citrix CloudPlatform (with live demo)
Deep dive: XA/XD on Amazon EC2 (with live demo)
Where does the future Citrix Workspace Services technology fit in?
%+27788225528 love spells in Colorado Springs Psychic Readings, Attraction sp...
Citrix xa xd cloud provisioning webinar
1. XA/XD Cloud
Provisioning
Lee Bushen & Mikael Lindholm
Tech Readiness EMEA
Important – Webinar Audio
The audio for this
webinar is available over
VoIP. Just select the ‘Use
Mic & Speakers’ option to
listen to the webinar
through your computers
speakers.
To listen using your
telephone select the
‘Use Telephone’
option. For local
numbers click the
‘additional numbers’
link.
You will need to use
the Access Code
and Audio PIN.
Start Time
14:00 BST 15:00 CET 9:00 EDT
2. Lee Bushen, EMEA Tech Readiness
Provisioning XenApp / XenDesktop in the Cloud
Mikael Lindholm, EMEA Tech Readiness
June 10th 2014
NIST (National Institute of Standards & Technology) Definition of Cloud Computing:
• On-demand self-service: Individuals can set themselves up without needing anyone’s help
• Ubiquitous network access: Available through standard Internet-enabled devices.
• Location independent resource pooling: Compute, Storage and Network needs are balanced across a common infrastructure, with no particular resource assigned to any individual user.
• Rapid elasticity: Consumers can increase or decrease capacity at will.
• Measured Service (Pay per use): Consumers pay for what they use: Compute, storage, Network.
There are five characteristics that define Cloud Computing:
On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider.
Broad network access. Capabilities are available over the network and accessed through standard
mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations).
Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, and network bandwidth.
Rapid elasticity. Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time.
Measured service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
Private cloud
The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.
Public cloud
The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud
The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).
Secondary Storage is used to store virtual machine Templates, ISO images and Snapshots. The storage is available to all PODs in a Zone, and can also be replicated automatically between Availability Zones thereby providing a common storage platform throughout the whole Cloud. Secondary Storage uses the Network File System (NFS) as this ensures it can be accessed by any Host in the Zone.
Dedicating pod, cluster or host to a specific domain/account means that the domain/account will have sole access to the dedicated pod, cluster or hosts such that scalability, security and manageability within a domain/account can be improved. The resources which belong to that tenant, will be placed into that dedicated pod, cluster or host.
Explicitly Dedicated Resources: Resources dedicated to an account/domain during configuration time
Shared Resources: All the non-dedicated resources.
Explicit Dedication - Explicit dedication, a new type will be added in Affinity Groups which will indicate deployment on explicitly dedicated resources.
Security groups keep VMs from different accounts separate as well as VMs within the same account separate
Even VMs within the same security group can’t see each other without rules
The virtual router connects to the public network for external communication. In many scenarios this is a routed VLAN as well but could also be untagged like shown in the example.
Disk offerings control the Data Volume Size when deploying an Instance from a Template.
Disk Offerings control the Root Volume Size when deploying an instance from an ISO.
- preparation Windows VM based on the Windows image selected is being deployed in an isolated network
- preparation data disk is created
- instance of worker VM is deployed and started up
- preparation data disk is attached to worker VM
- preparation data disk is detached from worker VM
- preparation data disk is attached to Windows preparation VM
- prep VM is started up and shut down, response files on data volume are generated
- data disk is detached from Windows prep VM
- data disk is attached to worker VM
- data disk is deleted
- new template is generated from preparation VM
- perparation Windows VM is deleted
- „real“ desktop VM is created from previously created template
- identity disk is created
- identity disk is attached to worker VM
- identity disk is detached from worker VM
- worker VM is destroyed
- identity disk is attached to „real“ desktop VM
Storefront could be in both sites as well, same as db
Storefront and controller could be in both sites as well, same as db