[PVE-User] unattended PVE server installation

Fabian Gr├╝nbichler f.gruenbichler at proxmox.com
Tue Jan 10 09:45:34 CET 2017


On Mon, Jan 09, 2017 at 07:04:48PM +0100, Vadim Bulst wrote:
> Hi Jeff,
> 
> i totally agree! I also tried to deploy PVE via Puppet:
> 
> class urzpvesrv (
> 
> ) inherits urzpvesrv::params {
> 
>   package { 'systemd-sysv':
>     ensure   => 'installed',
>     provider => 'apt',
>   }
>   package { 'ksm-control-daemon':
>     ensure   => 'installed',
>     provider => 'apt',
>   }
>   package { 'open-iscsi':
>     ensure   => 'installed',
>     provider => 'apt',
>   }
>   package { 'proxmox-ve':
>     ensure          => 'installed',
>     provider        => 'apt',
>     install_options => ['--force-yes','-y'],
>     require         =>
> Package['open-iscsi','ksm-control-daemon','systemd-sysv'],
>     notify          => Reboot['rebootafterpveinst'],
>   }
>   reboot { 'rebootafterpveinst':
>     apply => 'finished',
>   }
> 
> }
> 
> But no luck eighter!
> 
> Proxmox-ve is a virtual package. Shell I try to install them one by one? I
> think there is to much interactive configuration going on in these packages.

proxmox-ve is a METApackage, not a virtual one. although the description
says otherwise ;) those two things are something completely different.

as someone else already mentioned, the problem is most probably a broken
network / hostname configuration, as the PVE installer sets this up as
expected and the packages (or services started as part of the package
installation) don't cope well with non-working configurations. you need
to make sure that all the steps in the crossgrade howto are followed,
not just the package installation/removal ones.

> Is somebody deploying PVE unattended? What do you use? How things go?



More information about the pve-user mailing list