c908b9625d
The kube-upgrade strategy invokes a synchronous POST operation to start and cleanup a kubernetes upgrade. kube-upgrade-start takes about 3 seconds. kube-upgrade-complete takes about one second. The old code would ignore the results of those REST API calls, and enter a polling mode to check the host state. This could take up to two minutes to complete. Polling is un-neccessary (for these steps), and by using the results from the NFV plugin being invoked, the step can quickly be completed. This reduces the time of a kube-upgrade strategy by over three minutes. Test Plan: PASS: AIO-SX kube upgrade Story: 2010565 Task: 48152 Signed-off-by: Al Bailey <al.bailey@windriver.com> Change-Id: Icb511e70eea445b0d07a139d437e018fb3c505f3 |
||
---|---|---|
api-ref/source | ||
devstack | ||
doc | ||
mtce-guest | ||
nfv | ||
nova-api-proxy | ||
releasenotes | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_build_layer.cfg | ||
centos_dev_docker_images.inc | ||
centos_dev_wheels.inc | ||
centos_guest_image.inc | ||
centos_guest_image_rt.inc | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_stable_docker_images.inc | ||
centos_stable_wheels.inc | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
debian_stable_docker_images.inc | ||
debian_stable_wheels.inc | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
README.rst
nfv
StarlingX NFVI Orchestration