kubemark cluster starts partition servers in parallel#1113
Conversation
| # | ||
| MASTER_METADATA="" | ||
|
|
||
| ### to upload etcd image / binary tar once |
There was a problem hiding this comment.
the test_resource_upload() can be added to the very beginning of the test setup and ensure it is done. so that this check can be removed
There was a problem hiding this comment.
admin cluster also needs this uploading, and it is directly set up by kube-up.sh script; starting partition clusters also eventually call into kube-up.sh; if we don't want to change this structure, we have to have some sort of condition check in place.
yb01
left a comment
There was a problem hiding this comment.
/lgtm
with a few minor comments
|
/lgtm |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yb01, zmn223 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* design doc: DaemonSet support in scale-out Arktos (#1109) * doc: DaemonSet support in scale-out Arktos * minor: rephrased daemonset managability of failed TP * added notes of scale-up arktos supporting system tenanted DS * put daemonset design doc in separate file * trivial: resource manager reworded as resource partition * added design alternatives based on peer feedback * emphasized on DS and supporting resources in unit of TP; put more detail of kubelet secret/configmap local store changes * added clarifications based on peer feedback * minor: revised based on peer review * kubemark cluster starts partition servers in parallel (#1113) * multiple partitions of same kind (tp/rp) able to start in parallel * eliminates /tmp/saved_tenant_ips.txt and TP_IP_CONCAT var from kubemark setup scripts * minor: todo comments for dedicated log stream of parallel calls * Bump Arktos to v0.8.0 (#1116) * Fix a bug that event client was created with wrong user agent (#1120) Co-authored-by: hwchen <hong.chen@futurewei.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adopts parallel starting of arktos scale-out partitions when starting the kubemark cluster.
Current start-kunemark scripts starts the scale-out partitions (TP or RP) in sequence, which is quite time consuming if the number of TP servers and that of RP servers are not minimum. There are various ways to optimize the cluster setup time and reduce the overhead; one obvious way is making these partition servers started in parallel can significantly reduced the cluster setup time. This PR starts multiple TPs in parallel, after all TPs are started, then starts multiple RPs in parallel.
This PR does not try to start TPs and RPs at the same time.
Does this PR introduce a user-facing change?:
NONE