Editing Deploying Debian VEs without Templates
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
Installing Debian Virtual Environments without relying on a precreated template has many advantages and a few drawbacks. This article tries to outline those factors and provide a possible solution to reduce the amount of work needed for template-less Debian deployments. | Installing Debian Virtual Environments without relying on a precreated template has many advantages and a few drawbacks. This article tries to outline those factors and provide a possible solution to reduce the amount of work needed for template-less Debian deployments. | ||
− | |||
== Templates == | == Templates == | ||
[[Template|Templates]] are at the heart of the OpenVZ VE creation process. A "template cache" is basically a tarball consisting of a minimum operating system installation of a given Linux flavor. | [[Template|Templates]] are at the heart of the OpenVZ VE creation process. A "template cache" is basically a tarball consisting of a minimum operating system installation of a given Linux flavor. | ||
+ | |||
== Reasons for pre-built templates == | == Reasons for pre-built templates == | ||
Line 45: | Line 45: | ||
The basic steps needed to deploy Debian VEs are outlined in [[Debian template creation]]. | The basic steps needed to deploy Debian VEs are outlined in [[Debian template creation]]. | ||
− | == | + | == A working solution == |
To automate the process of deploying VEs with <tt>debootstrap</tt> a bit of shell-scripting glue is needed. | To automate the process of deploying VEs with <tt>debootstrap</tt> a bit of shell-scripting glue is needed. | ||
− | + | A work-in-progress version of such a tool can be found at https://workbench.amd.co.at/hg/vzstuff/. To get a local copy you need a [http://www.selenic.com/mercurial/wiki/ mercurial] client installed and then run the following command: | |
− | + | ||
+ | hg clone -r stable https://workbench.amd.co.at/hg/vzstuff/ | ||
− | |||
− | |||
− | |||
Following the instructions in the README file should get you started nicely. | Following the instructions in the README file should get you started nicely. | ||