System and method for pre-installing of virtual private server files

1. A method for managing Virtual Private Servers, the method comprising:

launching a plurality of active Virtual Private Servers (VPSs) in a computing system, wherein the VPSs share services of the same host operating system, and wherein each VPS virtualizes the host operating system;

as a background process, generating a plurality of inactive VPSs, wherein data related to the inactive VPS comprises a set of files and links to a common template area that contains files shared by multiple VPSs, that are required for the VPS to function and each of which is stored in its own dedicated container, and wherein the generating includes setting up a disk partition and a mount point required for activating functioning VPS, including any blank areas, implemented by a system administrator during activation of the VPS, for each inactive VPS on a storage device of the computing system, and copying files associated with each inactive VPS to the disk partition,

wherein the inactive VPSs are not associated with any owner, and wherein the inactive VPSs virtualize the same host OS as the plurality of VPSs;

upon request from a user for a VPS, activating one of the inactive VPSs using the dedicated container by associating the activated VPS with an owner; and

configuring the activated VPS based on user parameters, including configuring any of URL names, IP addresses, passwords, resource allocations, DNS names, hostnames, VPS administrative functions, and VPS user password,

wherein a process of one VPS only runs in that VPS, and no other VPS.

2. The method of claim 1 , wherein the dedicated container is a part of one or more files which represent a block level image of the partition and related data with file system on the top of block level image.

3. The method of claim 2 , wherein the partition includes system files of an operating system.

4. The method of claim 1 , wherein the dedicated container includes a private area of a copy-on-write file system.

5. The method of claim 1 , wherein the generating step comprises generating a plurality of inactive VPSs of any of mail server, web server, database server, FTP server, and game server.

6. The method of claim 1 , further comprising generating inactive VPSs of a specified configuration, if number of inactive VPSs of the specified configuration falls below a predefined value.

7. The method of claim 1 , further comprising generating inactive VPSs that have shared components with other VPSs.

8. A system for managing Virtual Private Servers, the system comprising:

a plurality of active Virtual Private Servers (VPSs) in user space of a computing system, wherein the VPSs share services of the same host operating system and wherein each VPS virtualizes the host operating system;

a plurality of inactive VPSs, and wherein each inactive VPSs includes a disk partition, and files associated with each inactive VPS copied to the disk partition;

as a background process, means for activating one of the inactive VPSs using data related to the inactive VPS that comprises a set of files and links to a common template area that contains files shared by multiple VPSs, stored in a dedicated container, that are required for the VPS to function and each of which is stored in its own dedicated container, and wherein the activating includes setting up a disk partition for each inactive VPS on a storage device of the computing system and including setting up a mount point required for activating functioning VPS, including any blank areas, implemented by a system administrator during activation of the VPS, and copying files associated with each inactive VPS to the disk partition,

wherein the inactive VPSs are not associated with any owner, and wherein the inactive VPSs virtualize the same host OS as the plurality of VPSs;

upon request from a user for a VPS, means for activating one of the inactive VPSs using the dedicated container by associating the activated VPS with an owner; and

means for configuring the activated VPS based on user parameters, including configuring any of URL names, IP addresses, passwords, resource allocations, DNS names, hostnames, VPS administrative functions, and VPS user password,

wherein a process of one VPS only runs in that VPS, and no other VPS.

9. The system of claim 8 , wherein the generating step comprises generating a plurality of inactive VPSs of any of mail server, web server, database server, FTP server, and game server.

10. The system of claim 8 , wherein, when a number of inactive VPSs of a specified configuration falls below a predefined value, additional inactive VPSs of the specified continuation are generated.

11. The system of claim 8 , wherein the inactive VPSs have shared components with other VPSs.

12. The method of claim 8 , wherein the inactive VPSs have fully isolated components.

13. A computer program product for managing Virtual Private Servers, the computer program product comprising a non-transitory computer useable recording medium having computer program logic recorded thereon for performing the steps of claim 1 .