April 15, 2020
Workspace update: s3 flavor based workspace instances
Up until today, Workspace in Paris used XEN hypervisor flavors (s1 and c2) to create general desktops. As of this update, Workspace will make use of the KVM hypervisor flavor s3 to create desktops.
In order to preserve consistency, the naming of the flavors shown in the Workspace console will not change. Click on this update to learn more.
With Workspace, users can enjoy virtual Desktops as a Service in order to telework or to better collaborate anywhere, anytime from any device. The virtual desktop can be sized according to a large choice of configurations (CPU, memory, disks and Windows OSs) whether for standard office usage or for graphical design of products or builing plans, images, and video, games.
Users can access to their virtual desktop from any Windows and Mac computers, IPads, Iphones, Smartphones and Android tablets.
The job of the desktop fleet administrator is simplified, with the ability to create multiple batches of instances in minutes and centrally manage their lifecycle via the Workspace console.
Workspace is a completely secure solution where users can access to the organisation’s Information System both in and out of the office.
Compared to a traditional hardware fleet investment, the costs are obviously reduced since the Worskpace service is charged hourly through Pay-as-you-go models or via monthly subscriptions.
As of today, Workspace s1 and c2 instances in Paris are using XEN hypervisors to create general Worskpace desktops. After this change, Workspace service will be using KVM hypervisors. The name and price of the workspace instances remains the same.
This change only affects the Paris region, previously created instances are not impacted. Workspace GPU instances g1 and images are not impacted.
Action to be done by users after the change:
After this change, if you are using private images for Workspace s1 and c2 series flavors, it is necessary to update the private image when you create a new instance and install the UVP VMTools in the image. Otherwise, the network connection of the newly created workspace instance from the private images will be abnormal.
Installation Verification and steps: