Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2011-03-30 21:20:14
Size: 768
Editor: ahasenack
Comment:
Revision 5 as of 2011-04-06 21:09:42
Size: 3169
Editor: ahasenack
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:

=== Computer registration ===
 * register a computer using the command line provided by the LDS how-to-register page

=== Mailing ===
 * send out an invitation for another administrator. There should be no significant waiting period (i.e., the admin should get the email quickly as it's not dependent on a cron job)
 * subscribe to the pending computer alert: register a new computer and see if you get the alert in the next 10min
 * subscribe to the offline computer alert: stop landscape-client on an existing computer and wait 10min

=== hash-id-databases ===
Right after a computer registered, keep tailing its package-reporter.log log file. Pretty soon you should see a line similar to this one:
{{{
2011-04-06 17:52:02,971 INFO [MainThread] Downloaded hash=>id database from https://landscape.canonical.com/hash-id-databases/af6f2dcf-1967-11de-8dd0-001a4b4d8d10_lucid_i386
}}}
That means it worked. The important thing is that it downloaded a file for the right distribution and architecture.

=== Cron jobs ===
LDS has several cron jobs that access the network. The purpose of this test is to make sure the current installation allows that.
 * maintenance: run `sudo -u landscape /opt/canonical/landscape/scripts/maintenance_wrapper.sh`. At the end, you should see it downloading several AMI codes.
 * security db: run `sudo -u landscape bash -x /opt/canonical/landscape/scripts/update_security_db.sh`. Make sure it succeeds in downloading the security db.
 * hash-id-databases: run `sudo -u landscape bash -x /opt/canonical/landscape/scripts/hash_id_databases.sh`. It will take several minutes to complete. There can't be any network errors.
 * meta-release: run `sudo -u landscape bash -x /opt/canonical/landscape/scripts/meta_releases.sh`. Same deal, no network errors. It will also take a while to complete

=== Ajax server and cloud ===
 1. Create a public cloud, using Amazon
 1. List the security groups. You should see at least one called "Default"
 1. Create a security group called "ssh", description "ssh". Click on it, allow ports 22 to everyone.
The above steps test:
 * ajax server
 * clouddeck infrastructure
 * that the maintenance script that was run earlier successfully populated the AMI database. If you only see "Other" in the Ubuntu release dropbox, then it failed.
If you want, you can create an ssh key, start an instance and login.

WORK IN PROGRESS

This guide should be followed after an installation of LDS. It's purpose is to verify that all aspects of the installation are working.

Items that need verification:

  • mailing: alerts, invitations
  • computer registration: tests https, message server, ping server, app server
  • access hash-id-database via web
  • run maintenance script one: tests that LDS can reach the AMI database on uec-images.ubuntu.com
  • run update-security-db once: tests that the USN database can be downloaded
  • run hash-id-databases once: it tests the necessary network connections. Note: it will take a while
  • run meta-releases once: it tests the network connection. Note: it also takes a while

TODO: write a single script that makes these tests.

Computer registration

  • register a computer using the command line provided by the LDS how-to-register page

Mailing

  • send out an invitation for another administrator. There should be no significant waiting period (i.e., the admin should get the email quickly as it's not dependent on a cron job)
  • subscribe to the pending computer alert: register a new computer and see if you get the alert in the next 10min
  • subscribe to the offline computer alert: stop landscape-client on an existing computer and wait 10min

hash-id-databases

Right after a computer registered, keep tailing its package-reporter.log log file. Pretty soon you should see a line similar to this one:

2011-04-06 17:52:02,971 INFO     [MainThread] Downloaded hash=>id database from https://landscape.canonical.com/hash-id-databases/af6f2dcf-1967-11de-8dd0-001a4b4d8d10_lucid_i386

That means it worked. The important thing is that it downloaded a file for the right distribution and architecture.

Cron jobs

LDS has several cron jobs that access the network. The purpose of this test is to make sure the current installation allows that.

  • maintenance: run sudo -u landscape /opt/canonical/landscape/scripts/maintenance_wrapper.sh. At the end, you should see it downloading several AMI codes.

  • security db: run sudo -u landscape bash -x /opt/canonical/landscape/scripts/update_security_db.sh. Make sure it succeeds in downloading the security db.

  • hash-id-databases: run sudo -u landscape bash -x /opt/canonical/landscape/scripts/hash_id_databases.sh. It will take several minutes to complete. There can't be any network errors.

  • meta-release: run sudo -u landscape bash -x /opt/canonical/landscape/scripts/meta_releases.sh. Same deal, no network errors. It will also take a while to complete

Ajax server and cloud

  1. Create a public cloud, using Amazon
  2. List the security groups. You should see at least one called "Default"
  3. Create a security group called "ssh", description "ssh". Click on it, allow ports 22 to everyone.

The above steps test:

  • ajax server
  • clouddeck infrastructure
  • that the maintenance script that was run earlier successfully populated the AMI database. If you only see "Other" in the Ubuntu release dropbox, then it failed.

If you want, you can create an ssh key, start an instance and login.

LDS/ValidationGuide (last edited 2011-04-07 17:52:39 by ahasenack)