Port hosting module, hostmaster profile and eldir theme to D7

This was planned for the 1.0 release, and we have EclipseGC that expressed interest in the port. This could happen quite soon, depending on contributions.

Univate's work in #517620: Turn hosting features into features features., should greatly simplify the upgrade of hostmaster.profile. The move to Profiler means that lots of the profile's settings now reside in a .info, so upgrading to Profiler-7.x should basically be all that's required. Moving everything else in the profile into a hosting-ui feature, should the allow us focus on upgrading hosting.

Has anyone tried running some of the hosting modules through http://upgrade.boombatower.com/, or the coder tools that power that site?

Also, while of lesser importance, there are probably some upgrades req'd for Eldir too: http://drupal.org/update/themes/6/7.

From hostmaster.profile:

  13     /* aegir contrib */ 'hosting', 'hosting_task', 'hosting_client', 'hosting_db_server', 'hosting_package', 'hosting_platform',
 'hosting_site', 'hosting_web_server', 'hosting_server',
  14     /* other contrib */ 'install_profile_api' /* needs >= 2.1 */, 'jquery_ui', 'modalframe', 'admin_menu',

As far as contrib modules go, install_profile_api is made redundant by moving to profiler (assuming we go that route), and the rest have (more or less) moved into core in D7.

It seems to me that for the Aegir modules, starting by upgrading just the bare essentials to D7 initially would be the way to go; then tackle the rest once that has stabilized somewhat. If that's reasonable, then I think everything listed, save hosting_client, falls into that essential category.

subscribe

So, some further thoughts on migrating hostmaster.profile to D7, especially using the Profiler library:

Vast amounts of code in hostmaster.profile look like this:

<?php
/* Default client */
$node = new stdClass();
$node->uid = 1;
$node->type = 'client';
$node->title = drush_get_option('client_name', 'admin');
$node->status = 1;
node_save($node);
variable_set('hosting_default_client', $node->nid);
variable_set('hosting_admin_client', $node->nid);
?>

Which cannot be done in a declarative .info à la Profiler. However, in D7, just about everything has been stripped out of the default .profiles, and put into .installs. So all this complicated logic could go there too.

On the other hand, variables such as these, can be handled by Profiler:

<?php
variable_set('site_frontpage', 'hosting/sites');

// do not allow user registration: the signup form will do that
variable_set('user_register', 0);
?>

As can setting the theme, profile title and description, and activating modules.

Menus and roles can be moved into Features, which, along with Context, can also handle block placement.

The thing I find most appealing about Profiler though, is it's ability to allow sub-profiles, like sub-themes. This would make custom distributions fairly easy.

I have posted a patch to convert hostmaster install profile to use the profiler & features format: #517620: Turn hosting features into features features.

This should help with upgrading to D7

sub

subb

subscribe

subscribe

Here are some documentation resources on upgrading modules from 6 to 7:

• Converting 6.x modules to 7.x
• Converting 6.x modules to 7.x - Categorical

sub

subscribing

Duplicate of #1261030: [meta] Roadmap: Aegir 3.x (D7 port)