Best practices for development of EZ templates - Revision history

Narcisgarcia: OpenVZ 6

2017-08-05T07:54:03Z

OpenVZ 6

Sergey Bronnikov: Marked this version for translation

2015-12-25T22:35:51Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:35:20Z

add 'translate' tags

Kir: add to templates cat

2015-09-11T20:41:58Z

add to templates cat

Sergey Bronnikov: initial version

2015-09-11T16:52:12Z

initial version

New page

{{Virtuozzo}}

This article lists recommendations for those willing to create EZ templates for Virtuozzo. Please consider them to be able to create EZ templates that can be included in the Virtuozzo distribution. Each recommendation has originated in the development and maintenance of Virtuozzo container templates. As the [https://src.openvz.org/projects/OVZT list of supported EZ templates] is evergrowing, before submitting your work make sure the same template has not been already submitted by someone else.

* Make sure your EZ template does not share RPMs with other EZ templates. For example, if you submit a mysql application template, make sure that the mysql package is used only by it and not any other application template, e.g., wordpress.
* Minimize the number of RPMs in packages files. For example, do not list every RPM implied by dependencies.
* Use ''setname'' when you modify an OS EZ template. This will help you avoid code duplication.
* Make sure all your scripts have error-handling routines and return 0.
* Add comments explaining the reasoning behind the code in scripts that is not intuitively clear.
* Make your EZ templates as universal as possible. Avoid specific modifications like localization, time zones, etc.
* Avoid using complex routines in your scripts to make them easier to maintain.

[[Category:Development]]
[[Category:Contributions]]

← Older revision		Revision as of 07:54, 5 August 2017
Line 1:		Line 1:
	{{Virtuozzo}}		{{Virtuozzo}}
		+	{{Note\|For OpenVZ 6 recommended pages are [[Deploying Debian VEs without Templates]] and [[Debian template creation]]}}

	<translate>		<translate>

← Older revision		Revision as of 20:41, 11 September 2015
Line 13:		Line 13:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Contributions]]		[[Category:Contributions]]
		+	[[Category:Templates]]

@@ Line 2: / Line 2: @@
 <translate>
 This article lists recommendations for those willing to create EZ templates for Virtuozzo. Please consider them to be able to create EZ templates that can be included in the Virtuozzo distribution. Each recommendation has originated in the development and maintenance of Virtuozzo container templates. As the [https://src.openvz.org/projects/OVZT list of supported EZ templates] is evergrowing, before submitting your work make sure the same template has not been already submitted by someone else.
 * Make sure your EZ template does not share RPMs with other EZ templates. For example, if you submit a mysql application template, make sure that the mysql package is used only by it and not any other application template, e.g., wordpress.
 * Minimize the number of RPMs in packages files. For example, do not list every RPM implied by dependencies.

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 This article lists recommendations for those willing to create EZ templates for Virtuozzo. Please consider them to be able to create EZ templates that can be included in the Virtuozzo distribution. Each recommendation has originated in the development and maintenance of Virtuozzo container templates. As the [https://src.openvz.org/projects/OVZT list of supported EZ templates] is evergrowing, before submitting your work make sure the same template has not been already submitted by someone else.
@@ Line 10: / Line 11: @@
 * Make your EZ templates as universal as possible. Avoid specific modifications like localization, time zones, etc.
 * Avoid using complex routines in your scripts to make them easier to maintain.
 [[Category:Development]]
 [[Category:Contributions]]
 [[Category:Templates]]