Operating Systems in a Layerd Virtual Workspace

• US 20110061045A1
• Filed: 11/11/2010
• Published: 03/10/2011
• Est. Priority Date: 12/20/2007
• Status: Abandoned Application

• Current Assignee: Virtual Computer Incorporated (Cloud Software Group)
• Original Assignee: Virtual Computer Incorporated (Cloud Software Group)
• Inventors: Phillips, Robert
• Application Number:
  US12/944,300
• Publication Number:
  US 20110061045A1
• Time in Patent Office: Days
• US Class Current: 717/173
• CPC Class Codes: G06F 9/45541 Bare-metal, i.e. hypervisor runs directly on hardware

Abstract

A virtual workspace can include an active instance of a layered virtual file system namespace. A layered virtual file system namespace is referred to by the virtual workspace and includes a collection of system data (e.g. layered virtual file system base layer), user data (e.g. layered virtual file system user layer), and virtualized applications (e.g. virtual app layer), metadata and policies (e.g. layered virtual file system layer scope). Because a virtual workspace can include software such as an operating system and one or more applications in addition to user data, a virtual workspace can be aligned with a namespace so that an operating system of the virtual workspace may be located at a “base layer”, one or more applications executing on the operating system may be located at an upper “virtual app” layer, and user data in a virtual workspace may be found at any layer at or above the user layer.

Claims

1. A method for updating an operating system of a client computer, the method comprising:

installing a computer operating system into a new base layer that is suitable for use as a base layer in a layered virtual file system and storing the new base layer in a memory accessible to a data management server;

transmitting the new base layer from the data management server to a client computer to be stored in a memory accessible to the client computer; and

directing an instance of the layered virtual file system that is resident on the client computer to use the new base layer.

2. The method of claim 1, wherein directing includes logically positioning the new base layer above an existing base layer of the instance of the layered virtual file system.

3. The method of claim 1, wherein directing includes replacing references to an existing base layer in the layered virtual file system with references to the new base layer.

4. The method of claim 1, wherein transmitting includes transmitting an instance of the layered virtual file system from the server to the client.

5. The method of claim 1, further including creating a check point associated with the instance of the layered virtual file system that facilitates restoring an existing base layer.

6. A method for deploying a virtualized operating system for use by a plurality of users, the method comprising:

providing a base layer of a layered virtual file system that facilitates access to an operating system;

storing the base layer in a memory accessible to a central data management server;

receiving a request to provide a virtualized workspace on any one of a plurality of client computing facilities;

deploying the base layer from the server to the one of the plurality of client computing facilities for use as a bottom most layer in a layered virtual file system that comprises a plurality of virtual layers in the virtualized workspace; and

providing a merged view of the plurality of layers in the virtualized workspace for accessing the operating system in the deployed base layer.

7. A method of managing changes to operating system data in an instance of a virtual workspace, the method comprising:

providing a layered virtual file system comprising a plurality of virtual layers that include at least one of a base layer and a user layer, wherein the base layer is configured as the bottom most layer of the plurality of virtual layers;

providing each of the plurality of virtual layers with its own file system hierarchy, wherein the file system hierarchy of the plurality of virtual layers are transparently overlaid such that a file system hierarchy in the user layer is configured above the base layer and has priority;

configuring the operating system and associated data in the file system hierarchy of the base layer; and

recording changes to operating system data in the file system hierarchy of the user layer, wherein the changed operating system data is visible in a merged view of the user layer and base layer file system hierarchies even though the base layer file system hierarchy data is unchanged.