No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Backup and Restoration Guide 03

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
How to StartServices That Have etcd Cache?

How to StartServices That Have etcd Cache?

Restarting the Tenant O&M Domain

Procedure
NOTE:

The node managed in the data zone does not need to perform Step 4, Step 5, and Step 11.

  1. Stop kube-apiserver and kube-canal-apiserver.

    1. Use PuTTY to log in to the manage_lb1_ip node.

      The default username is paas, and the default password is QAZ2wsx@123!.

    2. Move the following files to the upper-level directory:

      cd /var/paas/kubernetes/manifests

    1. Stop kube-apiserver.

      mv kube-apiserver.manifest ../

    2. Stop kube-canal-apiserver.

      mv kube-canal-apiserver.manifest ../

  2. Restart kube-apiserver and kube-canal-apiserver.

    1. Start kube-apiserver.

      mv ../kube-apiserver.manifest .

      Run the following command to check whether kube-apiserver docker process has been started:

      sudo docker ps|grep kube-apiserver

      If information similar to the following is displayed, the starting is successful:

      fd8165c9796a        10.75.186.81:8081/root/paas-cfe-kube-apiserver-bootstrap            "/bin/sh -c '/usr/loc"   29 hours ago        Up 29 hours                             k8s_kube-apiserver.1a69bbe_kube-apiserver-10.75.186.81_kube-system_d9808bb799f98a786abd83edf5de2745_ff010c03
      4ab1370aa735        10.75.186.81:8081/root/paas-cfe-pause-bootstrap                     "/pause"                 29 hours ago        Up 29 hours                             k8s_POD.4bffe1ea_kube-apiserver-10.75.186.81_kube-system_d9808bb799f98a786abd83edf5de2745_9274ddd8
    2. Start kube-canal-apiserver.

      mv ../kube-canal-apiserver.manifest .

      Run the following command to check whether kube-canal-apiserver docker process has been started:

      sudo docker ps |grep kube-canal-apiserver

      If information similar to the following is displayed, the starting is successful:

      2e25e6539f4b        cfe-canal-apiserver:2.9.28                                 "/bin/sh -c 'canal-ap"   3 weeks ago         Up 3 weeks                              k8s_kube-canal-apiserver.3363789e_kube-canal-apiserver-paas-10-184-42-132_om_631a35eb611b4519fd0ce10ab7fcc867_5454b36f
      bc2ace10399        paas-cfe-pause-bootstrap                                   "/pause"                 3 weeks ago         Up 3 weeks                              k8s_POD.6d5cdc5e_kube-canal-apiserver-paas-10-184-42-132_om_631a35eb611b4519fd0ce10ab7fcc867_82fd89ee

  3. Log in to the manage_lb2_ip node as the paas user and execute Step 1~Step 2.
  4. Restart kubelet and kube-proxy.

    NOTE:

    Perform the operations on each node in the tenant management zone.

    1. Run the following commands to restart kubelet and kube-proxy:

      monit restart kubelet

      monit restart kube-proxy

    2. Run the following command to check the statuses of kubelet and kube-proxy (Running or Status ok indicates that the component is running properly):

      monit summary

  5. Restart ingressproxy.

    1. Log in to the manage_lb1_ip node as the paas user.
    2. Run the following command and enter the password of the root user to switch to the root user:

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to query all pods of ingressproxy:

      kubectl -n fst-manage get pods | grep ingressproxy

      ingressproxy-ber-6tjh4                        1/1       Running   0          4d 
       ingressproxy-ber-kzvz9                        1/1       Running   0          2d 
       ingressproxy-er-9nv83                         1/1       Running   0          4d 
       ingressproxy-er-cdsc9                         1/1       Running   0          4d 
       ingressproxy-ir-dh11q                         1/1       Running   0          4d 
       ingressproxy-ir-ncfvv                         1/1       Running   0          4d 
       ingressproxy-ir-ndngh                         1/1       Running   0          4d 
       ingressproxy-ir-nwbms                         1/1       Running   0          4d
    4. Run the following command to restart the pods of ingressproxy in sequence (Pod names are in the first column in the command output above):

      kubectl -n fst-manage delete pods pod name

    5. Run the following command to check the status of each pod of ingressproxy (Running indicates that the component is running properly):

      kubectl -n fst-manage get pods | grep ingressproxy

  1. Stop swr-api-server, aos-apiserver and aos-cmdbserver.

    1. Stop swr-api-server.

      kubectl -n fst-manage edit deployment swr-api-server

      Press the Enter key to open the editing window.

      Change 3 (the queried value of replicas) in the spec area from 3 (the actual value prevails) to 0. Then, run the wq! command to save the change and exit.

      NOTE:

      If no swr-api-server is found, skip this step.

    2. Stop aos-apiserver.

      kubectl -n fst-manage edit deployment aos-apiserver

      Press the Enter key to open the editing window.

      Change 2 (the queried value of replicas) in the spec area from 3 (the actual value prevails) to 0. Then, run the wq! command to save the change and exit.

      NOTE:

      If no aos-apiserver is found, skip this step.

    3. Run the following command to stop aos-cmdbserver:

      kubectl -n fst-manage edit deployment aos-cmdbserver

      Press the Enter key to open the editing window.

      Change the value of replicas in the spec area from 3 (the actual value prevails) to 0. Then, run the wq! command to save the change and exit.

      NOTE:

      If no aos-cmdbserver is queried, skip this step.

  2. Restart swr-api-server, aos-apiserver and aos-cmdbserver.

    1. Start swr-api-server.

      kubectl -n fst-manage edit deployment swr-api-server

      Press the Enter key to open the editing window.

      Change the value of replicas in the spec area from 0 to 3. Then, run the wq! command to save the change and exit.

      NOTE:

      If swr-api-server is not stopped, skip this step.

    2. Start aos-apiserver:

      kubectl -n fst-manage edit deployment aos-apiserver

      Press the Enter key to open the editing window.

      Change the value of replicas in the spec area from 0 to 3. Then, run the wq! command to save the change and exit.

      NOTE:

      If aos-apiserver is not stopped, skip this step.

    3. Run the following command to start aos-cmdbserver:

      kubectl -n fst-manage edit deployment aos-cmdbserver

      Press the Enter key to open the editing window.

      Change the value of replicas in the spec area from 0 to 3. Then, run the wq! command to save the change and exit.

      NOTE:

      If no aos-cmdbserver is queried during the stop operation, skip this step.

  3. Stop kube-scheduler.

    1. Move the following files to the upper-level directory:

      cd /var/paas/kubernetes/manifests

    2. Stop kube-scheduler.

      mv kube-scheduler.manifest ../

  4. Start kube-scheduler.

    mv ../kube-scheduler.manifest .

  5. Log in to the manage_lb2_ip node as the paas user, and run Step 8 and Step 9.
  6. Restart canal-agent.

    NOTE:

    Perform the operations on each node in the tenant management zone.

    1. Run the following command to restart canal-agent.

      monit restart canal

    2. Run the following command to check the statuses of each component of canal-agent (Running or Status ok indicates that the component is running properly):

      monit summary

  7. Query statuses of all components.

    NOTE:

    Repeat the query operation until all components run properly.

    1. Log in to the manage_lb1_ip node as the paas user, and run the following command to check the statuses of all components.
    2. Run the following command and enter the password of the root user to switch to the root user:

      su - root

      Default password: QAZ2wsx@123!

    3. kubectl -n fst-manage get pods | grep -e swr-api-server -e aos-apiserver -e aos-cmdbserver

      If the status of all components are Running, as shown in the following output, all components are running properly.

      aos-apiserver-59979b9d7c-fltbf                1/1       Running   1          2h
      aos-apiserver-59979b9d7c-hjgg5                1/1       Running   1          2h
      aos-cmdbserver-66db949957-blzr6               1/1       Running   1          2h
      aos-cmdbserver-66db949957-z2h28               1/1       Running   1          2h
      swr-api-server-7c87f4b486-pbddj               1/1       Running   1          2h
      swr-api-server-7c87f4b486-prl8q               1/1       Running   1          2h
      swr-api-server-7c87f4b486-xc8lm               1/1       Running   1          2h
      swr-api-server-7c87f4b486-zfcvn               1/1       Running   1          2h

Translation
Download
Updated: 2019-06-14

Document ID: EDOC1100062366

Views: 797

Downloads: 9

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next