cas-mirror
and anaconda-enterprise-cli
configurations (see Step 4 below), as $HOME/cas-mirror
will be overwritten during the upgrade process. To avoid any compatibility issues, we recommend you upgrade your mirror tools as part of the upgrade process. Afterwards, simply copy over the configuration files you backed up to restore your custom configuration.
anaconda-enterprise-anaconda-platform.yml
ConfigMap by running the following command:
ae5-tools
by running the following command in a terminal that has access your Workbench cluster over the network:
backup.sh
script that runs as part of the upgrade process will restart all pods, so if they don’t, they will lose any unsaved work.
<location_of_installer>
with the location of the installer, and <version>
with your installer version:
sudo ./gravity plan
. You can then roll back any step in the upgrade process by running the rollback
command against the name of the phase, as it’s listed in the Phase
column:
backup.sh
script that runs as part of the upgrade process will restart all pods, so if they don’t, they will lose any unsaved work.
<location_of_installer>
with the location of the installer, and <version>
with your installer version:
sudo ./gravity plan
. You can then roll back any step in the upgrade process by running the rollback
command against the name of the phase, as it’s listed in the Phase
column:backup.sh
script that runs as part of the upgrade process will restart all pods, so if they don’t, they will lose any unsaved work.
<location_of_installer>
with the location of the installer, and <version>
with your installer version:
sudo ./gravity status
.
sudo ./gravity plan
. You can then roll back any step in the upgrade process by running the rollback
command against the name of the phase, as it’s listed in the Phase
column:
backup.sh
script that runs as part of the upgrade process will restart all pods, so if they don’t, they will lose any unsaved work.
<location_of_installer>
with the location of the installer, and <version>
with your installer version:
sudo ./gravity status
.
sudo ./gravity plan
. You can then roll back any step in the upgrade process by running the rollback
command against the name of the phase, as it’s listed in the Phase
column:
https://example.anaconda.com/
—replacing example.anaconda.com
with the FQDN of your server—and logging in using the same credential you used in your previous installation.git
section of the anaconda-enterprise-anaconda-platform.yml
file used to configure Anaconda Enterprise 5.3.1 includes parameter changes. If you backed up your Anaconda Enterprise config map before upgrading, and copied it onto the newly-updated master node, you’ll need to update your config map with the new information as described here.kinit <username>
.sc
command to connect to Sparkmagic and start Spark.