CML2 System Maintenance Controls

This page allows to execute maintenance actions on the CML2 controller installation.

 IMPORTANT
All of these tasks require that you're logged in using a privileged account. For this to work as a regular user with sudo privileges, you need to tick "Reuse my password for privileged tasks" on the Login screen!

Maintenance

Download CML2 log files as a .tar.gz archive file.
This will restart the CML2 services. It is recommended to stop all labs before restarting.
This will clean up all VMs and associated runtime elements on the system. This is destructive! This should be only done as a last resort. In particular, running this operation will:
  • Stop all CML2 services
  • Remove all related networking elements
  • Clean the networking fabric
  • Stops all defined virtual machines
  • Deletes all related disks and VM related files
  • Clears log files and the journal
  • Start the services again
    •  All the labs and configurations in the controller configuration itself will be retained.

    This will reset the controller to factory defaults. This is destructive! This will effectively do the same as the Clean Up maintenance action but in addition will also erase the controller configuration. This includes the defined user database.

    After this, the controller will create a default user 'cml2' with the password 'cml2cml2'. Using that user, create a new admin user as needed in the UI and then (logging out and logging in again as the new user) delete the 'cml2' user.

    This will upgrade the controller software to a newer software version. The software will be provided as an RPM file that must be uploaded to the controller first via the or via scp in the same way a node disk image is uploaded. The RPM file must end in .rpm and it should be ensured that only one RPM is uploaded at any given time.

    Ensure that all simulations are stopped prior to upgrading!!

    When the file is found and valid, the controller will be stopped and the software upgrade will be started. The output of the upgrade will be shown below. The controller will be restarted at the end of this process.

    KSM is a memory-saving de-duplication feature. Although memory usage is reduced with this feature, CPU performance and memory latency can be negatively impacted. It is recommended to disable this feature if running large nodes with sufficient memory available.


    Output

    None so far