Hello,
we just released Landscape 1.5.0, which introduces a set of new features that we hope you will enjoy! Read on for details about the main new features.
Package profiles
Package profiles is a very exciting new feature we are delighted to add to Landscape. These profiles allow you to easily install many packages in one go on your servers according to their tags, which means it’s easier than ever to have a machine ready with the software you need.
For example, let’s say we want to prepare a new Ubuntu server machine with the LAMP stack. Traditionally, you would create package activities to install Apache, PHP and MySQL With Package Profiles, all you need to do is define a profile that requires those dependencies:

Note how you can even specify version constraints. In the case above, I just provided the package names and the latest version will be used.
Now what we have to do is apply this profile to the machines we want. This is done via tags:
The moment we select a tag for this profile, it will be automatically applied to the machines in that tag.
The opposite also is true. The moment we apply a tag to a machine, if that tag is also associated with a profile, the profile will be installed on the machine. This is particularly useful when accepting new computers into Landscape. Think about it for a moment: just by accepting a new Ubuntu Server machine and giving it the, say, “lamp” tag, Landscape will take care of installing the LAMP stack on it.
Profile alerts
Once a machine has a profile applied successfully to it, Landscape will monitor this compliance. If for some reason one or more of the packages in that machine no longer match the profile requirements, Landscape will issue an alert:
This means that the package requirement for a profile were broken. For example, someone could have created an activity to remove the mysql-server package from one or more of those machines. In this case, Landscape will not enforce the compliance of the profile, that is, it will not try to reapply it automatically, but that’s an option you have when responding to this alert.
Release upgrades
With Release Upgrades, we give Landscape the ability to upgrade Ubuntu installations to the next available release. This means you can use Landscape to upgrade your Hardy server to Lucid. There are, however, some precautions you should take before attempting this, as well as things you should be aware of:
- these Landscape driven release upgrades are NON-INTERACTIVE! This means that any questions some package may normally ask during the upgrade process will not be answered. Some packages deal with this better than others, so please test your upgrade scenario before. Some tricky cases usually happen with packages that need to speak with a database and want to have it setup during installation, typically asking for a username and a password.
- if there were changes to configuration files, the old version will be left in place after the upgrade, that is, the maintainer version will NOT be installed
- backup your data. This is very important!
The new release upgrade option is available in the Packages page under Advanced Options. If any of the selected computers can be upgraded to a new release, you will see a link that will bring you to a page similar to this one:

This table shows the current release and the release it can be upgraded to. Just select the row you want and the upgrade will start.