Deploying Debian VEs without Templates - Revision history

Narcisgarcia: ctcreate to ctctl

2020-01-28T09:24:52Z

ctcreate to ctctl

Narcisgarcia: ctcreate

2017-10-17T07:21:58Z

ctcreate

Narcisgarcia: ctcreate and deploy.sh

2017-08-05T08:04:50Z

ctcreate and deploy.sh

Kir: SEO spam removed

2011-06-01T21:01:57Z

SEO spam removed

82.227.48.154: url changed. Old one not working any more

2011-05-30T23:54:48Z

url changed. Old one not working any more

2.94.77.130 at 08:54, 29 March 2011

2011-03-29T08:54:50Z

Robe: /* A working solution */

2008-11-29T22:19:13Z

‎A working solution

Robe: /* It's not needed after all */

2008-11-29T21:07:14Z

‎It's not needed after all

Robe: /* Tarballs are of questionable security */

2008-11-29T20:57:32Z

‎Tarballs are of questionable security

Robe: /* Management of tarballs can be tedious */

2008-11-29T20:57:03Z

‎Management of tarballs can be tedious

@@ 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.
-{{Note|'''[https://downloads.actiu.net/ctcreate/ ctcreate]''' is an alternative way to create a container and convert it to a template.}}
+{{Note|'''[https://downloads.actiu.net/ctctl/ ctctl]''' is an alternative wizard to create a container and convert it to a template.}}
 == Templates ==

← Older revision		Revision as of 07:21, 17 October 2017
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.
		+
		+	{{Note\|'''[https://downloads.actiu.net/ctcreate/ ctcreate]''' is an alternative way to create a container and convert it to a template.}}

	== Templates ==		== Templates ==

@@ 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.
 == 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.
 == Reasons for pre-built templates ==
@@ Line 45: / Line 43: @@
 The basic steps needed to deploy Debian VEs are outlined in [[Debian template creation]].
-== A working solution ==
+== Creation helpers ==
 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://github.com/terrorobe/vzstuff. To get a local copy you will need to install [http://git-scm.com/ git] and then run the following command:
+=== ctcreate by Narcis Garcia ===
+version included in the [https://git.actiu.net/libre/amoreos/ Amoreos repository]. Deploys APT/Debian containers for OpenVZ 6 in APT/Debian host, by building its corresponding template first.
 Following the instructions in the README file should get you started nicely.

@@ Line 31: / Line 31: @@
 === Templates are of questionable security ===
-Pre-built templates, especially those which can be downloaded from the internet, are of doubtful trustworthiness.[http://www.videoradio.ru] [http://www.shop.videoradio.ru] It's trivial to open backdoors, install keyloggers or run DDoS clients if you have full control of the binaries which are going to be run in a VE.
+Pre-built templates, especially those which can be downloaded from the internet, are of doubtful trustworthiness. It's trivial to open backdoors, install keyloggers or run DDoS clients if you have full control of the binaries which are going to be run in a VE.
 === It's not needed after all ===

@@ Line 49: / Line 49: @@
 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:
+A work-in-progress version of such a tool can be found at https://github.com/terrorobe/vzstuff. To get a local copy you will need to install [http://git-scm.com/ git] and then run the following command:
-  hg clone https://workbench.amd.co.at/hg/vzstuff/
+git clone git://github.com/terrorobe/vzstuff.git

← Older revision		Revision as of 22:19, 29 November 2008
Line 51:		Line 51:
	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:		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/	+	hg clone https://workbench.amd.co.at/hg/vzstuff/

@@ Line 35: / Line 35: @@
 === It's not needed after all ===
-With Debian, there is no reason to actually use pre-built templates if you're not time-constrained in the deployment process and have other means of managing your configuration, since <tt>debootstrap</tt> is the tool at the core of every Debian installation and it doesn't matter if it's run by the [http://wiki.debian.org/DebianInstaller|Debian Installer], by hand or a completely different distribution.
+With Debian, there is no reason to actually use pre-built templates if you're not time-constrained in the deployment process and have other means of managing your configuration.
 == Basic Steps ==

@@ Line 29: / Line 29: @@
 Experience has shown, that quality is one of the first things being cut in operations/production environments when being time constrained, so preventing one source of constant work improves quality and security instantly and irrevocably.
-=== Tarballs are of questionable security ===
+=== Templates are of questionable security ===
 Pre-built templates, especially those which can be downloaded from the internet, are of doubtful trustworthiness. It's trivial to open backdoors, install keyloggers or run DDoS clients if you have full control of the binaries which are going to be run in a VE.

@@ Line 25: / Line 25: @@
 === Management of tarballs can be tedious ===
-Managing templates in a non-trivial environment can become it's own demanding task, if taken seriously. The templates have to be updated constantly to reflect new security updates or point releases. And with every updated template, said templates have to be distributed to all Hardware Nodes where they are used.
+Managing templates in a non-trivial environment can become it's own demanding task, if taken seriously. The templates have to be updated constantly to reflect new security updates or operating system point releases. And with every updated template, said templates have to be distributed to all Hardware Nodes where they are used.
-Experience has shown, that quality is one of the first things being cut in operations/production environments when being time constrained, so preventing one source of constant work improves quality and security instantly.
+Experience has shown, that quality is one of the first things being cut in operations/production environments when being time constrained, so preventing one source of constant work improves quality and security instantly and irrevocably.
 === Tarballs are of questionable security ===