[pve-devel] applied-series: [PATCHSET v2] pve-cluster split

[Thomas Lamprecht]

On 11/11/19 11:27 AM, Fabian Grünbichler wrote:
> this patch set attempts to rectify a long-standing issue with our
> pve-cluster packaging:
> - the combination of pmxcfs+ipcc+binding and various other more or less
>   cluster-related perl code in mostly one perl module (PVE::Cluster) and
>   binary package (pve-cluster)
> - a cyclic dependency between pve-access-control and pve-cluster
> 
> to tackle both issues, pve-cluster gets split into two independent
> parts:
> - pve-cluster: pmxcfs+IPCC+cfs_*
> - libpve-cluster(-api)-perl: rest of the perl code
> 
> some notable high-level changes:
> - datacenter.cfg got its own perl module PVE::DataCenterConfig (libpve-cluster-perl)
> - *ssh_info* got its own perl module PVE::SSHInfo (libpve-cluster-perl)
> - the certificate cache got moved (back!) to pve-manager
> - the pvecm call in ExecStartPost of pve-cluster.service got moved to ExecStartPre of pveproxy.service
> 
> for building, the following order should work:
> 
> pve-docs
> pve-cluster
> pve-access-control
> pve-ha-manager
> pve-storage
> pve-guest-common
> pve-container
> qemu-server
> pve-manager
> pve-firewall
> 
> changelog v1->v2:
> - dropped patches already applied
> - dropped addr API endpoint and related patches in pve-cluster[1]
> - dropped no longer needed pve-access-control split
> - added missing versioned breaks pve-cluster -> libpve-access-control
> 
> 1: I'll explore monitoring+broadcasting all configured addresses via
> pmxcfs instead.
> 
> 

applied, updated changelog bumps and the breaks from pve-cluster
to ha-manager and pve-manager, as they got bumped in the meantime.
Thanks for the effort.