Upgrading Anaconda Enterprise 5 on Gravity

​

Prerequisites

• You must have jq installed.
• You must have a service account with sudo access on your Kubernetes (K8s) master node.
• Your K8s master node must be configured with a DNS A record. The A record sets the domain name you use for your Anaconda Enterprise instance.
• If you are upgrading Anaconda Enterprise on a system with multiple nodes, you must verify the clock on each node is in sync with the others. Anaconda recommends using Network Time Protocol (NTP) to synchronize computer system clocks automatically over your network. For more information on installing and using Chrony to manage the NTP, see the instructions provided here.
• You must have the ae-preflight package installed. For more information, see Anaconda Enterprise pre-flight check.
• Create a backup of your anaconda-enterprise-anaconda-platform.yml ConfigMap by running the following command:
  kubectl get cm anaconda-enterprise-anaconda-platform.yml -o json | jq -r '.data["anaconda-platform.yml"]' > configmap-backup.yml
  

​

Upgrading

​

In-place upgrade

1. Log in to a service account with sudo access on the master node running your Anaconda Enterprise software.
2. Download the installer file by running the following command:
   # Replace <INSTALLER_LOCATION> with the provided location of the installer file
   curl -O <INSTALLER_LOCATION>
   
3. Decompress the installer file by running the following command:
   # Replace <INSTALLER> with the installer file you just downloaded
   tar xvzf <INSTALLER>
   
4. Enter the installer directory by running the following command:
   # Replace <INSTALLER> with the version of your installer
   cd <INSTALLER>
   
5. Run the following command to verify your environment is properly prepared:
   ae-preflight
   
   If the check returns an overall result of WARN, you can view the results of the check by running the following command:
   cat results.txt
   
   If necessary, make applicable corrections to properly prepare your environment to meet the Installation requirements. Once you’ve verified that your environment is properly configured, you can begin the upgrade process.
6. To start the upload and upgrade process, run the following commands:
   sudo ./upload
   sudo ./gravity upgrade
   
   The upgrade process can take up to an hour or more to complete, primarily due to the upload step. You can view the status of the upgrade process at any time by running the following command:
   sudo watch ./gravity plan
   
   Once the upgrade process is complete, the pods will start to come up on their own, but this process also takes some time to finish. Monitor the pods status by running the following command:
   sudo watch kubectl get pods
   
   If you encounter errors while doing your in-place upgrade, you can view which phase of the upgrade failed by running the following command:
   sudo ./gravity plan
   
   You can return to any phase of the upgrade process by running the rollback command against the name of the phase as it’s listed in the Phase column of the ./gravity plan commands’ return:
   # Replace <NAME_OF_PHASE> with the name listed in the Phase column
   sudo ./gravity plan rollback --phase=/<NAME_OF_PHASE>
   
   After addressing any errors, resume the upgrade by running the following command:
   sudo ./gravity upgrade --resume --force
   

​

Fresh reinstallation upgrade

• Back up your configuration
• Uninstall
• Reinstall and apply your saved settings

​

Back up your configurations

1. Log in to a service account with sudo access on the master node running your Anaconda Enterprise software.
2. Download the installer file by running the following command:
   # Replace <INSTALLER_LOCATION> with the provided location of the installer file
   curl -O <INSTALLER_LOCATION>
   
3. Decompress the installer file by running the following command:
   # Replace <INSTALLER> with the installer file you just downloaded
   tar xvzf <INSTALLER>
   
   
4. Enter the installer directory by running the following command:
   # Replace <INSTALLER> with the installer file you just decompressed
   cd <INSTALLER>
   
   
   The installer bundle contains the extract_config.sh script, which retains the following files when run: * anaconda-enterprise-certs.yaml * anaconda-enterprise-keycloak.yaml * helm_values.yaml * gravity_values.yaml
5. Create a directory to contain the configuration data extracted by the script and name it “reinstall”:
   mkdir reinstall 
   
6. Enter the directory you just created:
   cd reinstall 
   
7. Run the extract_config.sh script by running the following command:
   sudo bash extract_config.sh
   
   Once the script has completed, you will need to manually save some additional configurations and secrets to your reinstall directory.
8. Export your configmap to a .yaml file by running the following command:
   sudo kubectl get cm -o yaml --export > configmap.yaml 
   

​

Uninstall

​

Reinstall and apply your saved settings

1. Run the following command to verify your environment is properly prepared:
   ae-preflight
   
   If the check returns an overall result of WARN, you can view the results of the check by running the following command:
   cat results.txt
   
   If necessary, make applicable corrections to properly prepare your environment to meet the Installation requirements. Once you’ve verified that your environment is properly configured, you can begin the upgrade process.
2. Run the Gravity installation command using the gravity_values.yaml file stored in the reinstall directory you created earlier instead of creating a new file during installation:
   # Replace <ADVERTISE-ADDR> with the IP address you want to be visible to the other nodes. If you have a private network and all nodes can communicate on it, use the private IP address for the advertise address
   # Replace <CLUSTERNAME> with the name you're giving to your cluster. Alphanumeric characters and periods only
   # Replace <VALUES_PATH> with the filepath to the gravity_values.yaml file created from running the extract_config.sh script
   sudo ./gravity install --advertise-addr=<ADVERTISE-ADDR> --cluster=<CLUSTERNAME> --config <VALUES_PATH> --service-uid=$(id -u) --cloud-provider=generic
   
   Here is an example of what the installation command looks like for a single-node cluster:
   sudo ./gravity install --advertise-addr=192.168.1.1 --cluster=MyCluster --config ./gravity_values.yaml --service-uid=$(id -u) --cloud-provider=generic
   
3. Complete the rest of the installation process.
4. Replace your SSL certificate by running the following commands:
   sudo kubectl create -f anaconda-enterprise-certs.json
   sudo kubectl replace -n kube-system -f cluster-tls.json
   
5. Replace your user secrets by running the following command:
   sudo kubectl create -f user-secrets.json
   
   The configmap.yaml file that you created earlier contains settings that need to be restored to the anaconda-enterprise-anaconda-platform.yml file manually.
6. Open a web browser and log in to Anaconda Enterprise as an Administrator.
7. Open the User dropdown menu and select Admin Console.
   
8. Select Manage Resources to open your Gravity Ops Center.
9. Log in to your Gravity Ops Center. Contact your Gravity systems administrator if you need access.
10. Select Kubernetes from the left-hand navigation menu.
11. Select Edit config map under anaconda-enterprise-anaconda-platform.yml to open the file. Leave this browser open for now.
    
12. Return to your terminal and view the contents of your configmap.yaml file by running the following command:
    cat configmap.yaml
    
13. Review the contents of the anaconda-enterprise-anaconda-platform.yml file and verify that your configuration values have been properly restored. If necessary, replace the applicable sections of the anaconda-enterprise-anaconda-platform.yml file with the configurations saved in your configmap.yaml file.
14. Restart the Anaconda platform pods by running the following command:
    kubectl get pods | grep ap- | cut -d ' ' -f 1 | xargs kubectl delete pods
    
15. Add the worker nodes to the cluster.

​

Verifying your installation

1. Verify all pods are running by running the following command:
   sudo kubectl get pods
   
2. Open a web browser and navigate to your Authentication Center.
   # Replace <FQDN> with the fully qualified domain name of your Anaconda Enterprise server
   https://<FQDN>/auth/admin
   
3. Select Users from the Manage menu, then click View all users and verify your users’ data is present.
4. Open a web browser and navigate to your Anaconda Enterprise URL. Log in using the same credentials you used for your previous installation.
5. Review the Projects list to verify that all project data has been restored.

​

Additional configurations

​

TLS/SSL certificates

​

External git repository

​

Spark/Hadoop

# Replace <PATH_TO_SECRETS.yaml> with the path to your anaconda secrets .yaml file
sudo kubectl replace -f <PATH_TO_SECRETS.yaml>

1. Log in to Anaconda Enterprise.
2. If your configuration uses Kerberos authentication, open a Hadoop terminal and authenticate yourself through Kerberos using the same credentials you used previously. For example, kinit <USERNAME>.
3. Open a Jupyter Notebook that uses Sparkmagic and verify that it behaves as expected by running the sc command to connect to Sparkmagic and start Spark.

​

Cleaning up