Precreated templates

[smeat]

To have a template file automatically show up in the VM Create Template drop down you have to name your file like this:
os-osversion-name_nameversion_arch.tar.gz
ubuntu-8.04-RailsServer_2.2.3-1_amd64.tar.gz

 

[DaveQB]

To have a template file automatically show up in the VM Create Template drop down you have to name your file like this:
os-osversion-name_nameversion_arch.tar.gz
ubuntu-8.04-RailsServer_2.2.3-1_amd64.tar.gz

Wow that works awesome!

Exactly what I was after

Thanks.

 

[apmuthu]

The latest apm-available to include the Joomla v1.5.15 template is attached in this post.

 

[apmuthu]

Latest apm-available file attached in this post.

 

[dt_]

I tried to create a template for cPanel and I have similar problems:

centos-5-cpanel_5.2-11.24_i386.tar.gz

Package: centos-5-cpanel
Version: 5.2-11.24
Type: openvz
OS: centos-5
Section: system
Maintainer: me
Location: http://##/centos-5-cpanel_5.2-11.24_i386.tar.gz
Infopage: http://pve.proxmox.com/wiki
md5sum: dc3a001747e0141fc06d74ee81ce207f
Description: cPanel 11.24 R + CentOS 5

logs

unable to parse appliance record: version = '5.2-11.24'
found incomplete appliance records

 

[apmuthu]

It appears that there should not be any "." in the build number after the base version. Try this:

Rename file as: centos-5-cpanel_5.2-1124_i386.tar.gz
 
Place in the apl-available file:
======================
Package: centos-5-cpanel
Version: 5.2-1124
Type: openvz
OS: centos-5
Section: system
Maintainer: me
Location: [URL]http://##/centos-5-cpanel_5.2-1124_i386.tar.gz[/URL]
Infopage: [URL]http://pve.proxmox.com/wiki[/URL]
md5sum: dc3a001747e0141fc06d74ee81ce207f
Description: cPanel 11.24 R + CentOS 5
 The second line of the description onwards must begin with a space

 

[dt_]

Indeed, the dot was the problem. It works fine now. Thank you, apmuthu!

 

[apmuthu]

Latest apm-available file for appending to /var/lib/pve-manager/apl-available is attached here. This includes the latest FrontAccounting v2.2.1-1 template details.

 

[SuSt]

I've noticed, that PVE manager accepts only i386 architecture in the names of templates. Such behaviour is explained by the next lines in the code:

ProxMox PVE v.1.4, "/usr/share/perl5/PVE/APLInfo.pm", Line 193:

    $template =~ s/\.tar\.gz$//;
    $template =~ s/_i386$//;

So, any different text rather "_i386.tar.gz" in the file name leads to ignoring this file as "known application" by the PVE web interface.

I think that it is either a bug or a nonsense. I would be very glad to find this issue fixed in following versions of ProxMox.

 

[dietmar]

I think that it is either a bug or a nonsense. I would be very glad to find this issue fixed in following versions of ProxMox.

It is neither a bug nor nonses - support for other architectures is simply not implemented - but it is on our todo list.

 

[SuSt]

support for other architectures is simply not implemented

OK, but therefore, how can I successfully run several OpenVZ-Containers based on Debian 5.0.3 (Lenny), amd64? I have created templates for them manually, according to this manual: http://wiki.openvz.org/Debian_template_creation
Furthermore, I generate theese templates "by hands", not using DAB. And all this does work fine.

 

[martin]

I've noticed, that PVE manager accepts only i386 architecture in the names of templates. Such behaviour is explained by the next lines in the code:

ProxMox PVE v.1.4, "/usr/share/perl5/PVE/APLInfo.pm", Line 193:

    $template =~ s/\.tar\.gz$//;
    $template =~ s/_i386$//;

So, any different text rather "_i386.tar.gz" in the file name leads to ignoring this file as "known application" by the PVE web interface.

I think that it is either a bug or a nonsense. I would be very glad to find this issue fixed in following versions of ProxMox.

if you upload a template e.g. via web interface, i386 and amd64 is supported.