Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: automatic manager update

...

In this case, perform the following steps:

  1. Use SFTP to copy the RPM packages to your Charon AWS instance (see Data Transfer Options).
  2. Connect to the host system using Charon Manager (see Accessing the Charon-SSP AWS Instance)
  3. Shutdown the guest systems running on the host and stop the emulator.
  4. Use SSH to connect to your Charon AWS instance (see Accessing the Charon-SSP AWS Instance).
  5. Install the new RPM packages as described below.
  6. Install the new Charon-SSP Manager package on your local Linux system as described below.
  7. Connect to the host system using Charon Manager.
  8. Start the emulator and boot the guest systems.

...

Product partPackage names
Charon-SSP emulator software for the different SPARC architectures. 4U+ and 4V+ contain both the 4U and 4U+ and 4V and 4V+ versions respectively.charon-ssp-4v+-<version>.aws-1.x86_64.rpm
charon-ssp-4m-<version>.aws-1.x86_64.rpm
charon-ssp-4u+-<version>.aws-1.x86_64.rpm
Charon-SSP Agent (required for the Charon Manager connection)charon-agent-ssp-<version>.x86_64.rpm

Charon-SSP Manager

(warning) This package must be installed on the local Linux system!

charon-manager-ssp-<version>.rpm

charon-manager-ssp-<version>.deb

Upgrade commands

...

Upgrading Charon Packages on the Charon-SSP AWS Instance

After copying the packages to the Charon-SSP AWS instance, install the packages as described below. For details, please refer to the relevant man-pages on Linux.

Step
Details
1

For packages on the AWS instance: log Log in to the system Charon-SSP AWS via SSH to the sshuser and become the root user (sudo -i).

2

Go to the directory where the packages have been stored:

# cd <package-location>

3Run upgrade command:

For systems with RPM package management (Red Hat, CentOS):
    # yum update <package-name>

Upgrading Charon Manager on the Remote Management System

There are two ways to upgrade the Charon Manager

package

on the

local

remote Linux system

: log

Standard Linux Package Update

Step
Details
1

Log in as the root user. 

32

Go to the directory where the packages have been stored:

# cd <package-location>

4
3

Run upgrade command:

For systems with RPM package management (Red Hat, CentOS):
    # yum update <package-name>

For systems with Debian package management (Debian, Ubuntu):
    # dpkg -i <package-name>(info) This is only applicable for the local Charon Manager installation on Ubuntu

Automatic Update when first Connecting to Updated Charon Host System

(info) New feature in Charon-SSP 4.0.x.

If you connect to a Charon host system with a newer version of Charon-SSP using an older version of the Charon Manager, you will be offered an automatic update to the version of the Charon host system.

The following image shows a sample:

Image Added

Confirm the upgrade by clicking on Yes. This will initiate the download and installation of the new version. If you work as a non-privileged user, you will be prompted for your password.

To decline the automatic update, click on Cancel.

Creating a New Instance with New Charon-SSP AWS AMI Version

...

  • Create new instance with new Charon-SSP version in the same subnet as the old instance. Use the same security group and key pair as in the old instance.
  • Backup emulated SPARC disks and configuration data on the old instance to the separate EBS volume.
  • If applicable, backup important system configuration files to the separate EBS volume.
  • Shut down guest systems and stop running emulator instances on the old host system.
  • Stop the old instance.
  • Copy the Charon Manager kit from the new instance and install it on your local Linux system, or connect to the new instance via Charon Manager to initiate the automatic Charon Manager update.
  • Move the EBS volume(s) and (if applicable) network interfaces with elastic IP addresses to the new instance.
  • Import the virtual SPARC configurations on the new system.
  • Adapt the host system configuration as needed.
  • Start the guest systems.
  • If everything works, terminate the old instance.

...