VOI system architecture and method for instantiating user operating system

Abstract

The invention belongs to the technical field of virtual terminal management systems, and relates to a VOI system architecture and a method for instantiating a user operating system. The VOI system architecture comprises a user side system, a VOI user side connected with the user side system, and a VOI server side, the method comprises the following steps of: accessing a VOI special module of a special system with a three-layer network protocol stack to a VOI terminal; the VOI special module loads a system guider to enter a VOI special system; the VOI special system is provided with a starting manager and a system service agent, a Guest OS system user side system is loaded through the starting manager, a local VOI cloud desktop system is loaded, and the problems that a two-layer network is not reachable and configuration is tedious in a complex network environment are solved. The network architecture is stable, network storms are not easy to occur, and the network security problem is solved; in an old environment, an original network environment is directly reused, and manual adjustment of a network service component and addition of a new access control rule are not needed.

Description

Technical Field

[0001] The present invention belongs to the technical field of virtual terminal management systems, and in particular, relates to a VOI system architecture and a method for instantiating a user operating system. Background Art

[0002] VOI (Virtual OS Infrastructure) cloud desktop system, which stores data on the server, centrally manages all devices, and runs the desktop on the client.

[0003] In the existing VOI cloud desktop system solution, the user-side client usually uses PXE (Preboot Execution Environment) technology to download the boot file and use iSCSI (Internet Small Computer System Interface) and other technologies to achieve system startup (such as CN116069400A A method and terminal for starting the Linux operating system under the VOI architecture), that is, the diskless startup mode. The other is to use PXE technology, where the VOI client directly starts the underlying basic system preset by the VOI server from the network, and downloads the Guest OS (Guest Operating System) system image and boot file in the basic system, that is, the local startup mode, as shown in the attached Figure 1 shown.

[0004] The VOI client startup process is as follows Figure 2 As shown, the deployment of the prior art VOI client requires the deployment of a VOI server device in each corresponding area, such as Figure 3 As shown, the scope of use of the VOI system in projects is greatly limited.

[0005] To improve the above problems, most current technical solutions support an architecture that deploys the DHCP server and VOI server separately: the Proxy DHCP mode. Figure 4 However, the Proxy DHCP mode requires network devices to support related configurations. The VOI server and devices with DHCP functions (including Proxy DHCP) need to be placed in independent computer rooms and configured with independent network segments according to the data center construction plan or security requirements, which results in the user VOI terminal and the DHCP server layer 2 network used for PXE startup being unable to communicate with each other.

[0006] Problems with the traditional VOI cloud desktop system network architecture:

[0007] (1) The VOI client, DHCP server, and VOI server must be in a Layer 2 network. This network architecture is unstable, prone to network storms, and has network security issues.

[0008] (2) When the server needs to be placed in an independent computer room and configured in an independent network segment due to security requirements, the user VOI terminal and the server layer 2 used for PXE boot cannot communicate with each other.

[0009] Problems in the Proxy DHCP architecture:

[0010] In a more complex network environment, the second-layer device needs to support DHCP relay to forward the third-layer DHCP messages; the router and switch hardware need to support the corresponding functions, and there is a problem of environmental support; dedicated network management personnel are required, and this mode cannot be configured and troubleshooted; a large amount of network bandwidth is occupied, which will affect the normal Guest OS system push and other network requirements; if the size of the underlying basic system that IPXE needs to transmit is M, and the number of push nodes is N, the total amount of data that needs to be pushed is M*N, which is a huge amount of data; when the Guest OS system needs to be pushed again, the process of sending the underlying basic system will be repeated, and the push takes a long time. Summary of the invention

[0011] In order to solve the technical problems of unreachable Layer 2 network and complicated configuration in a complex network environment, the present invention provides a VOI system architecture and a method for instantiating a user operating system.

[0012] In a first aspect, the present invention provides a VOI system architecture, including a user-end system, a VOI user-end connected to the user-end system, and a VOI server-end; both the VOI user-end and the VOI server-end are installed with a VOI dedicated system having a three-layer network protocol stack; the user-end system is used to load a local VOI cloud desktop system;

[0013] The VOI user terminal sets a VOI dedicated module; the VOI dedicated module is a ROM memory, including a boot partition, a system partition and a recovery partition; the boot partition is used to store system boot files; the system partition is used to store data layer files of the VOI dedicated system including the Guest OS system image; the recovery partition is used to store backup files of the system boot and the VOI dedicated system, and the backup files are used to rebuild the boot partition and the system partition;

[0014] The VOI dedicated module loads the system bootloader to enter the VOI dedicated system;

[0015] The VOI dedicated system is equipped with a boot manager and a system service agent. The Guest OS system is loaded through the boot manager. The system service agent obtains the system partition information storing the Guest OS system image and accesses the allocated disk space.

[0016] The VOI server is provided with a system management component and a system image library; the system management component reads the data layer file containing the Guest OS system image stored in the system image library to load the Guest OS system.

[0017] In a second aspect, the present invention provides a method for instantiating a user operating system based on a VOI system architecture, comprising:

[0018] The VOI client and VOI server are powered on, and the VOI dedicated module is started;

[0019] Load the system bootloader and enter the VOI dedicated system;

[0020] The VOI client connects to the VOI server to obtain the tasks to be executed;

[0021] The VOI server pushes the Guest OS system image file and boots the repair to the VOI client, and displays the Guest OS system image list;

[0022] The user selects the Guest OS system to be started according to the Guest OS system image list;

[0023] The VOI server configures the restoration strategy of the VOI dedicated system. The VOI dedicated system determines whether to execute the restoration strategy for the Guest OS system selected for startup according to the configuration of the VOI server. If so, the VOI dedicated system executes the restoration strategy for the Guest OS system selected for startup and then configures the system boot device to start from the Guest OS system. Otherwise, the system configures the system boot device to start from the Guest OS system.

[0024] The system reboots and enters the Guest OS system.

[0025] Based on the above technical solution, the present invention can also be improved as follows.

[0026] Furthermore, the VOI dedicated module also includes a Guest OS partition for storing the client system image sent by the VOI server;

[0027] The client system image includes a base layer, a personalized layer, and a data layer;

[0028] The base layer is used to store data layer files containing the Guest OS system image;

[0029] The personalization layer is used to perform personalized settings according to the user attributes of the user terminal, including computer name settings, network configuration and virtual memory configuration;

[0030] The data layer is used to store user data.

[0031] Furthermore, the ROM memory is connected to a PCIE interface or a USB interface.

[0032] Furthermore, the VOI dedicated system executes a restoration strategy according to the configuration of the VOI server, including: deleting the data layer file containing the corresponding Guest OS system in the system partition, creating a new data layer file for the Guest OS system, configuring the system boot loader, and starting the Guest OS system using the new data layer file.

[0033] Furthermore, the VOI service agent reads the system partition information, hides the system partition, and continuously detects and blocks the user's mount request for the system partition and the user's access to the partition of the allocated disk space.

[0034] Furthermore, the storage path of the client system image is hidden inside the client system, and the storage path and the name of the client system image are packaged and encrypted; the vdfuse layer is used to encrypt and decrypt the request parameters used for mounting.

[0035] Furthermore, a RESET button is provided on the VOI dedicated module. When a startup failure occurs in the VOI dedicated system, the RESET button can be used to reset the boot partition and system partition of the VOI dedicated module in one click to rebuild the boot partition and system partition of the VOI dedicated module.

[0036] The beneficial effects of the present invention are as follows: the user-side system loads the local VOI cloud desktop system, and the VOI terminal replaces the underlying basic system by accessing the VOI dedicated module pre-installed with a dedicated system with a three-layer network protocol stack, so that the VOI cloud desktop system in local startup mode no longer relies on PXE technology, and solves the problems of unreachable second-layer network and cumbersome configuration in complex network environments; the network architecture is stable, not prone to network storms and solves network security problems; in an old environment, the original network environment is directly reused, and there is no need for information system managers to manually adjust network service components and add new access control rules. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is the architecture diagram of the local boot mode of the VOI cloud desktop system based on PXE in the prior art;

[0038] Figure 2 A flowchart of starting a VOI client based on PXE in the prior art;

[0039] Figure 3It is a schematic diagram of the network architecture of the VOI cloud desktop system in the conventional mode of the prior art;

[0040] Figure 4 It is the existing ProxyDHCP mode VOI cloud desktop system network architecture;

[0041] Figure 5 is a schematic diagram of the VOI system architecture of the present invention;

[0042] Figure 6 A flowchart of a method for instantiating a user operating system based on a VOI system architecture;

[0043] Figure 7 A flowchart of the restoration strategy for the VOI dedicated system;

[0044] Figure 8 is a structural diagram of a VOI dedicated module of an optional implementation mode;

[0045] Fig. 9 is a structural diagram of a VOI dedicated module of an optional implementation mode;

[0046] Fig.10 is a schematic diagram of the structure of the VOI dedicated module including file A;

[0047] Fig.11 Schematic diagram of the VOI system architecture in the reuse scenario. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0049] Example 1

[0050] As an example, Figure 5 As shown, in order to solve the above technical problems, this embodiment provides a VOI system architecture, including a user-end system, a VOI user-end connected to the user-end system, and a VOI server-end; both the VOI user-end and the VOI server-end are installed with a VOI dedicated system with a three-layer network protocol stack; the user-end system is used to load a local VOI cloud desktop system, such as Windows and Linux systems;

[0051] The VOI user terminal sets up a VOI dedicated module;

[0052] The VOI dedicated module loads the system bootloader to enter the VOI dedicated system;

[0053] The VOI dedicated system is equipped with a boot manager and a system service agent. The Guest OS system is loaded through the boot manager. The system service agent obtains the system partition information storing the Guest OS system image and accesses the allocated disk space.

[0054] The VOI server is provided with a system management component and a system image library; the system management component reads the data layer file containing the Guest OS system image stored in the system image library to load the Guest OS system.

[0055] In actual application, the client system is connected to the VOI client through a network service component. The client system PC hardware environment loads the system image through the user system environment, and the user system environment is provided with a data disk for storing the system image file.

[0056] In actual application, the user-side system loads the local VOI cloud desktop system, and the VOI terminal accesses the VOI dedicated module through the PCIE interface or USB interface. The VOI dedicated module is pre-installed with a dedicated system with a three-layer network protocol stack to replace the underlying basic system, so that the VOI cloud desktop system in local startup mode no longer relies on PXE technology, solving problems such as unreachable second-layer network and cumbersome configuration in complex network environments; at the same time, in the old environment, the original network environment can be directly reused, and there is no need for information system managers to manually adjust network service components and add new access control rules.

[0057] Optionally, the Guest OS system image is such as a VHD (Virtual Hard Disk).

[0058] In actual application, as shown in the attached Figure 6 As shown, the workflow of the VOI user end is:

[0059] The VOI client and VOI server are powered on, and the VOI dedicated module is started;

[0060] Load the system bootloader and enter the VOI dedicated system;

[0061] The VOI client connects to the VOI server to obtain the tasks to be executed;

[0062] The VOI server pushes the Guest OS system image file and boots the repair to the VOI client, and displays the Guest OS system image list;

[0063] The user selects the Guest OS system to be started according to the Guest OS system image list;

[0064] The VOI server configures the restoration strategy of the VOI dedicated system. The VOI dedicated system determines whether to execute the restoration strategy for the Guest OS system selected for startup according to the configuration of the VOI server. If so, the VOI dedicated system executes the restoration strategy for the Guest OS system selected for startup and then configures the system boot device to start from the Guest OS system. Otherwise, the system configures the system boot device to start from the Guest OS system.

[0065] The system reboots and enters the Guest OS system.

[0066] Optionally, the VOI dedicated system executes the restoration strategy according to the configuration of the VOI server, as shown in the attached Figure 7 As shown, it includes: deleting the data layer file corresponding to the Guest OS system in the system partition, creating a new data layer file for the Guest OS system, configuring the system bootloader, and starting the Guest OS system using the new data layer file.

[0067] As an optional implementation, as shown in the attached Figure 8 As shown, the VOI dedicated module is a ROM memory, including a boot partition, a system partition and a recovery partition; the boot partition is used to store system boot files; the system partition is used to store data layer files of the VOI dedicated system including the Guest OS system image; the recovery partition is used to store backup files of the system boot and the VOI dedicated system, and the backup files are used to rebuild the boot partition and the system partition, and the format is ".bak", which are stored as "system boot.bak" and "VOI dedicated system.bak".

[0068] As an optional implementation, as shown in the attached Fig. 9 As shown, the VOI dedicated module is a ROM memory. On the basis of the boot partition, system partition and recovery partition, the VOI dedicated module also includes a Guest OS partition for storing the client system image sent by the VOI server.

[0069] The client system image includes a base layer, a personalized layer, and a data layer;

[0070] The base layer is used to store data layer files containing the Guest OS system image; the data layer files containing the Guest OS system image are from the system image library and are downloaded from the server and external terminal through the network;

[0071] The personalization layer is used to perform personalized settings according to the user attributes of the user terminal, including computer name settings, network configuration and virtual memory configuration;

[0072] The data layer is used to store user data.

[0073] The VOI dedicated module can also store the GuestOS image sent by the VOI server in the Guest OS partition, so that in the reuse mode, the user's original data will not be cleared, and seamless access to the VOI system environment can be achieved.

[0074] Optionally, the ROM memory is connected to a PCIE interface or a USB interface.

[0075] As an optional implementation, the security of the VOI dedicated system is protected by:

[0076] (a) Use Ukey (Unique Key) plus password and other authentication methods to achieve multi-factor authentication;

[0077] (b) Block local key combinations to prohibit ordinary users from obtaining access to the VOI dedicated system;

[0078] (c) Remote access to VOI dedicated systems is prohibited;

[0079] As an optional implementation, the user terminal can only access the allocated virtual disk space, thereby protecting the security of the VOI dedicated system, specifically including:

[0080] (1) As attached Fig.10 As shown, in the VOI dedicated system, the GuestOS partition storing the Guest OS system image is obtained through the system service agent, and the information of the GuestOS partition is stored in the file A under the system partition of the VOI dedicated system;

[0081] (2) In the Guest OS partition, the VOI service agent reads the system partition information in file A, hides the Guest OS partition, and continuously detects and blocks the user's mount request for the Guest OS partition, ensuring that the user can only access the allocated disk space (including virtual disk space and physical disk space).

[0082] As an optional implementation, the storage path of the Guest OS system image is hidden inside the Guest OS system to prevent users from obtaining underlying information in the Guest OS system and protect the security of the VOI dedicated system, including:

[0083] (2) As an optional implementation method for the Linux system, the boot parameters (boot path and Guest OS system image name) are packaged and encrypted, including:

[0084] The vdfuse layer is used to encrypt the request parameters used for mounting to prevent users from finding vdfuse related information in the system.

[0085] The request parameters are decrypted and extracted inside the vdfuse program. In this way, the user layer can only see the encrypted base64 string but cannot know the actual file path of the Guest OS system image.

[0086] (2) As an implementable method for Linux system, the vdfuse process of the Guest OS system mounting tool is hidden, specifically including:

[0087] The dynamic library is loaded at runtime to hijack the Guest OS system call readdir function (directory reading function), and vdfuse related content is filtered out in the readdir function, thereby hiding vdfuse.

[0088] The Readdir function is a system call function. Currently, the mainstream process viewing tools on Linux, such as ps and top, all use the readdir function to read the process information under / proc, so the vdfuse process can be filtered in the readdir function to hide the process.

[0089] LD PRELOAD In the dynamic link library of the Unix operating system, it is a Linux environment variable. When the Linux process is running, it will load the dynamic link library through the environment variable and use the functions in the dynamic link library to overwrite the normal function library. Through the dynamic link library, the readdir function of the vdfuse process is filtered in the dynamic link library, so that processes such as ps and top call the readdir function to achieve the purpose of hiding the process.

[0090] As an optional implementation, in the reuse scenario, when the user terminal cannot support the access of the VOI dedicated module, the same function can be achieved by dividing the specific ROM space in the existing PC hardware environment, only sacrificing part of the user data storage space. Fig.11 shown.

[0091] A VOI dedicated system with a three-layer network protocol stack is installed on the disk of the VOI user-side hardware environment to solve problems such as unreachable second-layer network and cumbersome configuration in complex network environments. At the same time, the original network environment can be directly reused in the old environment, eliminating the need for information system administrators to manually adjust network service components and add new access control rules.

[0092] The present invention proposes a more flexible, secure and easy-to-deploy VOI system architecture, which gets rid of the PXE technology limitation and solves the problem of unreachable Layer 2 network and complicated configuration in complex network environment through the VOI dedicated module in the VOI user-side hardware environment.

[0093] For reuse scenarios that cannot support the access of VOI dedicated modules, the VOI dedicated system supports direct installation in the existing PC hardware environment to divide specific disk space.

[0094] In the old environment, the original network environment can be directly reused, and there is no need for information system administrators to manually adjust network service components and add new access control rules.

[0095] In addition, this embodiment proposes a variety of innovative measures to protect the security of the VOI dedicated system, including protecting the ROM storage structure prefabricated in the VOI dedicated module, protecting the GuestOS system image (vdfuse encryption, process hiding), restricting users from accessing unauthorized disk space, etc. The network architecture is stable, not prone to network storms, and solves network security issues.

[0096] Example 2

[0097] Based on the same principle as the method shown in Example 1 of the present invention, as shown in the attached Figure 6 As shown, the embodiment of the present invention also provides a method for instantiating a user operating system based on the VOI system architecture in embodiment 1, including:

[0098] The VOI client and VOI server are powered on, and the VOI dedicated module is started;

[0099] Load the system bootloader and enter the VOI dedicated system;

[0100] The VOI client connects to the VOI server to obtain the tasks to be executed;

[0101] The VOI server pushes the Guest OS system image file and boots the repair to the VOI client, and displays the Guest OS system image list;

[0102] The user selects the Guest OS system to be started according to the Guest OS system image list;

[0103] The VOI server configures the restoration strategy of the VOI dedicated system. The VOI dedicated system determines whether to execute the restoration strategy for the Guest OS system selected for startup according to the configuration of the VOI server. If so, the VOI dedicated system executes the restoration strategy for the Guest OS system selected for startup and then configures the system boot device to start from the Guest OS system. Otherwise, the system configures the system boot device to start from the Guest OS system.

[0104] The system reboots and enters the Guest OS system.

[0105] Optionally, the VOI dedicated system executes the restoration strategy according to the configuration of the VOI server, as shown in the attached Figure 7 As shown, it includes: deleting the data layer file corresponding to the Guest OS system in the system partition, creating a new data layer file for the Guest OS system, configuring the system bootloader, and starting the Guest OS system using the new data layer file.

[0106] Optionally, the VOI service agent reads the system partition information, hides the system partition, and continuously detects and blocks user mount requests for the system partition and user access to the partition of the allocated disk space.

[0107] Optionally, the storage path of the client system image is hidden inside the client system, and the storage path and the name of the client system image are packaged and encrypted; the vdfuse layer is used to encrypt and decrypt the request parameters used for mounting.

[0108] Optionally, a RESET button is provided on the VOI dedicated module. When a startup failure occurs in the VOI dedicated system, the RESET button can be used to reset the boot partition and system partition of the VOI dedicated module with one click to rebuild the boot partition and system partition of the VOI dedicated module.

[0109] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. VOI system architecture, characterized by: It includes a user-end system, a VOI user-end connected to the user-end system, and a VOI server-end; both the VOI user-end and the VOI server-end are installed with a VOI dedicated system with a three-layer network protocol stack; the user-end system is used to load a local VOI cloud desktop system; The VOI user terminal sets a VOI dedicated module; the VOI dedicated module is a ROM memory, including a boot partition, a system partition and a recovery partition; the boot partition is used to store system boot files; The system partition is used to store the data layer files of the VOI dedicated system including the Guest OS system image; The recovery partition is used to store the backup files of the system boot and VOI dedicated system. The backup files are used to rebuild the boot partition and system partition. The VOI dedicated module loads the system bootloader to enter the VOI dedicated system; The VOI dedicated system is equipped with a boot manager and a system service agent. The Guest OS system is loaded through the boot manager. The system service agent obtains the system partition information storing the Guest OS system image and accesses the allocated disk space. The VOI server is provided with a system management component and a system image library; the system management component reads the data layer file containing the Guest OS system image stored in the system image library to load the Guest OS system.

2. The VOI system architecture according to claim 1, characterized in that: The VOI dedicated module also includes a Guest OS partition, which is used to store the client system image sent by the VOI server; The client system image includes a base layer, a personalized layer, and a data layer; The base layer is used to store data layer files containing the Guest OS system image; The personalization layer is used to perform personalized settings according to the user attributes of the user terminal, including computer name settings, network configuration and virtual memory configuration; The data layer is used to store user data.

3. The VOI system architecture according to claim 1, characterized in that: The ROM memory is connected with a PCIE interface or a USB interface.

4. A method for instantiating a user operating system based on the VOI system architecture of claim 1, characterized in that: include: The VOI client and VOI server are powered on, and the VOI dedicated module is started; Load the system bootloader and enter the VOI dedicated system; The VOI client connects to the VOI server to obtain the tasks to be executed; The VOI server pushes the Guest OS system image file and boots the repair to the VOI client, and displays the Guest OS system image list; The user selects the Guest OS system to be started according to the Guest OS system image list; The VOI server configures the restoration strategy of the VOI dedicated system. The VOI dedicated system determines whether to execute the restoration strategy for the Guest OS system selected for startup according to the configuration of the VOI server. If so, the VOI dedicated system executes the restoration strategy for the Guest OS system selected for startup and then configures the system boot device to start from the Guest OS system. Otherwise, the system configures the system boot device to start from the Guest OS system. The system reboots and enters the Guest OS system.

5. The method for instantiating a user operating system according to claim 4, characterized in that: The VOI dedicated system executes the restoration strategy according to the configuration of the VOI server, including: deleting the data layer file containing the corresponding Guest OS system in the system partition, creating a new data layer file for the Guest OS system, configuring the system bootloader, and starting the Guest OS system using the new data layer file.

6. The method for instantiating a user operating system according to claim 4, characterized in that: The VOI service agent reads the system partition information, hides the system partition, and continuously detects and blocks user mount requests for the system partition and user access to the partition of the allocated disk space.

7. The method for instantiating a user operating system according to claim 4, characterized in that: The storage path of the client system image is hidden inside the client system, and the storage path and the name of the client system image are packaged and encrypted; the vdfuse layer is used to encrypt and decrypt the request parameters used for mounting.

8. The method for instantiating a user operating system according to claim 4, characterized in that: Build a dynamic link library, set the readdir function to filter the vdfuse process in the dynamic link library, and dynamically check whether the process calls the readdir function.

9. The method for instantiating a user operating system according to claim 4, characterized in that: A RESET button is provided on the VOI dedicated module. When a startup failure occurs in the VOI dedicated system, the RESET button can be used to reset the boot partition and system partition of the VOI dedicated module with one click to rebuild the boot partition and system partition of the VOI dedicated module.

Images