Re: [pve-devel] [PATCH docs] Stress the recommandation use CD-ROM for installation and put information abou on-top-of-Debian information into special paragraph

[Dietmar Maurer]

applied, comments inline:

> On October 5, 2016 at 12:10 PM "friedrich.ramberger" 
> wrote:
> 
> 
> From: fritz 

Please use your full name instead of 'fritz'

> 
> Signed-off-by: fritz 

same here

> ---
>  pve-installation.adoc | 47 ++-
>  1 file changed, 26 insertions(+), 21 deletions(-)
> 
> diff --git a/pve-installation.adoc b/pve-installation.adoc
> index 27f2d72..486f916 100644
> --- a/pve-installation.adoc
> +++ b/pve-installation.adoc
> @@ -2,27 +2,17 @@ Installing Proxmox VE
>  =
>  include::attributes.txt[]
>  
> -{pve} ships as a set of Debian packages, so you can simply install it
> -on top of a normal Debian installation, or download the installation
> -CD-ROM and use that to install {pve} on your hardware.
> -
> -Installing on top of an existing Debian installation looks easy, but
> -it presumes that you have correctly installed the base system, and you
> -know how you want to configure and use the local storage. Network
> -configuration is also completely up to you.
> -
> -In general, this is not trivial, especially when you use LVM or
> -ZFS. This is why we provide an installation CD-ROM for {pve}. That
> -installer just ask you a few questions, then partitions the local
> -disk(s), installs all required packages and configures the system
> +{pve} is based on Debian and comes with an installation CD-ROM 
> +which includes a complete Debian ("jessie" for Proxmox VE 4.x) system as 
> +well as all necessary Proxmox VE packages. The
> +installer just asks you a few questions, then partitions the local
> +disk(s), installs all required packages, and configures the system
>  including a basic network setup. You can get a fully functional system
> -within a few minutes, including the following:
> +within a few minutes. This is the preferred and recommended installation
> method.
>  
> -* Complete operating system (Debian Linux, 64-bit)
> -* Partition the hard drive with ext4 (alternative ext3 or xfs) or ZFS
> -* {pve} Kernel with LXC and KVM support
> -* Complete toolset
> -* Web based management interface
> +Alternatively, Proxmox VE can be installed on top of an existing Debian
> system. 
> +This option is only recommended for advanced users since detail knowledge
> about 
> +Proxmox VE is necessary.
>  
>  ifndef::wiki[]
>  
> @@ -34,7 +24,14 @@ endif::wiki[]
>  Using the {pve} Installation CD-ROM
>  ---
>  
> -This is the preferred and recommended installation method.
> +Includes the following:

Please can we have a more elaborate start of this section?

> +
> +* Complete operating system (Debian Linux, 64-bit)
> +* Partition the hard drive with ext4 (alternative ext3 or xfs) or ZFS
> +* {pve} Kernel with LXC and KVM support
> +* Complete toolset
> +* Web based management interface
> +
>  
>  NOTE: By default, the complete server is used and all existing data is
>  removed.
> @@ -167,7 +164,7 @@ ifndef::wiki[]
>  Install {pve} on Debian
>  ---
>  
> -{pve} ships as a set of Debian packages, so you can simply install it
> +{pve} ships as a set of Debian packages, so you can install it
>  on top of a normal Debian installation. After configuring the
>  repositories, you need to run:
>  
> @@ -177,6 +174,14 @@ apt-get update
>  apt-get install proxmox-ve
>  
>  
> +Installing on top of an existing Debian installation looks easy, but
> +it presumes that you have correctly installed the base system, and you
> +know how you want to configure and use the local storage. Network
> +configuration is also completely up to you.
> +
> +In general, this is not trivial, especially when you use LVM or
> +ZFS.
> +
>  You can find a detailed step by step howto on the
>  {webwiki-url}Install_Proxmox_VE_on_Debian_Jessie[wiki].
>  
> -- 
> 2.1.4

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] Include name of template in LXC conf file?

[Dietmar Maurer]

> Is there any reason why the LXC conf file should not retain the name of the
> original template file?  I am prepared to submit a patch for this, if that
> would be acceptable.

We only store the OS type, for example:

ostype: debian
arch: amd64

Storing the original template seems misleading to me, because users
often update the container, so the template does not contain the 
same content as the container.

I guess it would be better to use the latest available 
template instead?

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] Include name of template in LXC conf file?

[Brendan Jurd]

Hello,

With Proxmox 3 / OpenVZ, it was possible to see the name of the template
file that was originally used to create the container, from
/etc/pve/openz/.conf.

It seems that the LXC conf file lacks this feature.  I haven't found
anywhere in Proxmox 4 which retains the name of the original template for
LXC nodes.  If such a thing exists, I'd be glad to know where to find it.

This is of interest because we want to be able to re-create an LXC
container based on its configuration file, and then bring the container up
to spec by running Ansible against it.  We are planning for disaster
recovery scenarios where it is not feasible to restore whole containers
from vzdumps.

We could keep track of the template used separately, but it would be
simpler all around if that information were stored in the LXC conf file.

Is there any reason why the LXC conf file should not retain the name of the
original template file?  I am prepared to submit a patch for this, if that
would be acceptable.

Thanks for your time,
Brendan Jurd
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel