|Deletions are marked like this.||Additions are marked like this.|
|Line 18:||Line 18:|
|* instantaneous alert notification in the UI: no need to reload a page||* ajax-style alert notification in the UI|
Things to write about:
- new license file format available. If you replace your existing license with the new format, you can't go back or all existing computers will lose their registations.
- schema check during startup
- errors to ignore during upgrade:
- patch 119 error
- warnings about transaction import
- non-quickstart upgrade is less troublesome
- installing the new client on an existing vm won't make it report the vm: this only happens at registration time
- automatic activity update (ajax-style refresh)
- VM licensing: optional new license type specific for virtual machines
- database schema check during startup
- better initscripts
- automatic activity status update in the UI using ajax
- new alerts: license overflow and package reporting errors
- ajax-style alert notification in the UI
Please make sure you have backed up the database and all the Landscape config files before proceeding with the upgrade.
In general, the quickstart upgrade works just fine from either LDS 1.6 or LDS 11.03. You may see some warnings about patch errors, but these are accounted for, and if there was a real patch problem, the service start at the end of the upgrade will tell you.
Nonquickstart upgrade from 11.03
The only changes required by this upgrade are schema changes, both to Landscape and to the Clouddeck databases. If you have UPGRADE_SCHEMA set to "yes" in /etc/default/landscape-server, then only the clouddeck schema needs to be updated manually.
- to upgrade the Landscape schema, run this command after the landscape-server package upgrade:
- to upgrade the clouddeck schema, run this command after the clouddeck package upgrade:
sudo clouddeck-schema /etc/clouddeck/stores.cfg
Both commands will only take a few seconds in this upgrade.
Nonquickstart upgrade from 1.6
This upgrade is not trivial. Please follow the steps described in the 1.6 to 11.03 nonquickstart upgrade.
This release of LDS introduces a new license type called "VMFeatures". This license, if purchased, can be used exclusively by virtual machines, including cloud instances. We currently detect vmware, xen and kvm. The use of this feature requires landscape-client 11.07.1.1 or higher.
If you register a virtual machine with Landscape, and you have seats available in the VMFeatures license, the computer will use one of these seats. If VMFeatures is not available, or doesn't have enough seats, then a regular Full seat will be used.
Bare metal machines cannot use VMFeatures seats: they can only use the regular Full license seats. Virtual machines, on the other hand, can use either.
VMFeatures requires new registration
To use a VMFeatures seat, the machine (VM) has to be registered again as this information is only reported at registration time. If it's an existing VM in Landscape, it will need to be removed and registered again, or just registered again. Registering in place of an existing Landscape computer won't work for this feature.
Warnings about transaction module
Some initscripts and the quickstart upgrade will report a warning about the transaction module. This is benign and can be ignored.
Upgrading to new license format
In order to support the VMFeatures license, a new license format was introduced. It is backwards compatible with old installations of LDS.
If you upgrade to the new license format, however, DO NOT DOWNGRADE BACK TO THE OLD ONE. Doing so will remove all existing computers from a license and you will need to license them all again by selecting them and going to the Info page and selecting a suitable license.
Ignoring patch error during LDS upgrades
During the LDS upgrade, you may see one or more messages saying an exception during the application of database schema changes was ignored. These are expected in some cases, and a confirmation that everything is OK can be seen later on when the services are started. We now check for the correct database schema before starting the services, so if they start, then all patches were applied correctly.