autotest/autotest — pull request #394 by nacc (2012-06-13 00:03:34+00:00)
Title: Tighten install server integration4

Hi,

So one gap in the current implementation of the install server
functionality I noticed is that the end-user still has to fiddle with
the backend cobbler server when they want to install a different than
the currently selected profile. It seems like the end user should be
able to select the profile to use on a host-by-host basis.

Some implementation notes:

The link between autotest and cobbler is established by the platform of the autotest host being found in the comment field for the profile in cobbler. This is because the architectures in Cobbler are not necessarily the same as the platforms in Autotest and I can't think of a good way to manage them together.

Profiles are always strings.

Changed since v2 (pull request #319):

Fixed various bugs
Fixed unittests with lmr and cleber's help
More testing

Changed since v1 (pull request #254):

Fixed bugs in clone
Fixed bugs in reinstall
More testing

1/12: install_server: default profile to an empty-string
2/12: hosts/remote: add install_server_is_configured
3/12: database: add profile column to afe_host_queue_entries table
4/12: frontend: add XMLRPC lookup of profile information from install server to get_hosts
5/12: frontend: add profiles parameter to job creation interfaces
6/12: hosts: add profile to the remote class
7/12: autoserv: append profile selection to hostname parameter
8/12: frontend/afe: add current profile to host view
9/12: frontend/afe: add profile used to job view
10/12: frontend/afe: add listbox widget support
11/12: frontend/afe: add profile to host tables
12/12: fronted/afe: add support for do_not_install profile