]> git.proxmox.com Git - pve-cluster.git/commit - data/PVE/API2/ClusterConfig.pm
projects / pve-cluster.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 74e09a9) | patch
api/cluster: create cluster in forked worker
authorThomas Lamprecht <t.lamprecht@proxmox.com>
Tue, 12 Dec 2017 16:15:56 +0000 (17:15 +0100)
committerFabian Grünbichler <f.gruenbichler@proxmox.com>
Fri, 16 Feb 2018 12:50:46 +0000 (13:50 +0100)
commit333a9bc8c0c3b752c8b0515f934a7875350362fa
tree01512ce0a6c61892963823a736f2961e8949188btree
parent74e09a9397f26e4782fbd7fa788a6daa2c25a0e1commit | diff
api/cluster: create cluster in forked worker

Creating a cluster may need a bit longer, we need to gather random
data for the corosync authkey, restart services and such.
As we're now exposed in the API the 30 second response limit from
pveproxy is a big reason to do this. But we also get a nice task log
entry with this, which is nice.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
data/PVE/API2/ClusterConfig.pm diff | blob | blame | history
Cluster FS and Tools