[pve-devel] [PATCH cluster v3 00/14] Allow adding/deleting nodes and cluster creation over API
Thomas Lamprecht
t.lamprecht at proxmox.com
Tue Dec 19 12:52:25 CET 2017
Third iteration of this series, see [1] for the cover letter of the last on.
This series depends on the apiclient exception series and the common v2
run_command: add 'quiet' parameter series.
changes v2 -> v3:
* put join and cluster creation in a fork_worker
* use exceptions to catch a not implemented (i.e. outdated packages on peer
side)
* tell cluster log when we add or delete a node (new patch 2/14)
* use run_command instead of system (new patch 4/14)
* simplify error handling in assert_joinable (new patch 5/14)
* use resolved IP address for ring0_addr as default (new patch 14/14)
changes v1 -> 2:
* 7/10, 8/10, 9/10, 10/10 are new - mostly moving also the create
cluster to the API and preparing for the UI component
* prev. 1/6 - 5/6 stayed the same
* prev. 6/6 (now 6/10): use PVE::PTY directly, not the CLIHandler
wrapper
[1]: https://pve.proxmox.com/pipermail/pve-devel/2017-December/029696.html
Thomas Lamprecht (14):
move addnode/delnode from CLI to cluster config API
tell cluster log when adding/deleting a node
node add: factor out code
use run_command instead of system
assert_joinable: simplify error and warning handling
return cluster config and authkey in addnode API call
api/cluster: add join endpoint
pvecm add: use API by default to join cluster
cluster create: factor out initial corosync config assembly
cluster create: restart corosync & pmxfs in one go and say so
move cluster create to API
api/cluster: create cluster in worker
api/cluster: add endpoint to GET cluster join information
use resolved IP address for ring0_addr as default
data/PVE/API2/ClusterConfig.pm | 490 +++++++++++++++++++++++++++++++++++-
data/PVE/CLI/pvecm.pm | 556 +++--------------------------------------
data/PVE/Cluster.pm | 137 +++++++++-
data/PVE/Corosync.pm | 73 ++++++
debian/control.in | 2 +
5 files changed, 740 insertions(+), 518 deletions(-)
--
2.11.0
More information about the pve-devel
mailing list