To complete this tutorial, you will need a machine with an Ubuntu Pro subscription. The prerequisites for adding Ubuntu Pro to an Ubuntu machine are:
- An Ubuntu One account
- An Ubuntu Pro subscription
- An Ubuntu Pro token attached to your Ubuntu machine
- Landscape Client installed and registered with either Landscape on-prem or Landscape SaaS
- Landscape Client that is allowed to remotely execute scripts
Obtain an Ubuntu Pro subscription
Anyone can use Ubuntu Pro for free for personal use, or evaluation purposes, on up to 5 machines. Ubuntu Pro subscriptions come with Livepatch and Landscape on-premises.
Visit ubuntu.com/pro to create or sign in to your Ubuntu One account, and obtain an Ubuntu Pro subscription that matches your needs.
Attach an Ubuntu Pro token to your machine
A token is used to associate your machine to your Ubuntu Pro subscription.
Let’s first check whether we have already attached the token using Pro Client, by running:
SERVICE AVAILABLE DESCRIPTION
cc-eal no Common Criteria EAL2 Provisioning Packages
esm-infra yes UA Infra: Extended Security Maintenance (ESM)
fips yes NIST-certified core packages
fips-updates yes NIST-certified core packages with priority security updates
livepatch yes Canonical Livepatch service
usg yes Security compliance and audit tools
This machine is not attached to an Ubuntu Pro subscription.
We can see that this is not yet attached to an Ubuntu Pro subscription. Let’s fix that now.
Your UA token can be found on your Ubuntu Advantage dashboard. To access your dashboard, you need an Ubuntu One account. If you still need to create one, ensure that you use the email address used to purchase your subscription.
The Ubuntu One account functions as a Single Sign On, so once logged in we can type the address for the Ubuntu Advantage dashboard into the browser’s address bar: ubuntu.com/pro. Then click on a subscription in the left hand column, and the Documentation tab on the right hand side column. Now we’re ready to attach our UA token to the Pro Client. Look for the copy and paste ready command to attach a machine, it will look similar to this:
sudo pro attach <your_pro_token>
The Landscape quickstart deployment guide offers the shortest path to a functional Landscape Server instance, and enrolling a machine to be managed by Landscape with Landscape Client. Signing up for Landscape SaaS eliminates the server installation step, and relieves you of any maintenance activities to keep Landscape up to date.
The Landscape Client steps from the quickstart deployment guide are accurate for both Landscape SaaS and Landscape on-premises users. During installation, Landscape Client will request permission for executing scripts remotely for all users.
Landscape has a feature which enables administrators to run
arbitrary scripts on machines under their control. By default this
feature is disabled in the client, disallowing any arbitrary script
execution. If enabled, the set of users that scripts may run as is
Enable script execution? [y/N]:
Answering yes to this “Enable script execution” question is required for this tutorial to work successfully.
By default, scripts are restricted to the 'landscape' and
'nobody' users. Please enter a comma-delimited list of users
that scripts will be restricted to. To allow scripts to be run
by any user, enter "ALL".
Script users: ALL
ALL to the
Script users prompt is not necessary to complete this tutorial. To be maximally useful, Landscape Client should be able to execute scripts with elevated privileges (such as
root) on an as-needed basis. This tutorial is limited to monitoring, which does not require
root privileges. If you intend to also complete the tutorial to change Livepatch configurations at scale with Landscape, you will need to answer this prompt with