2.0 alphas, betas & release candidates

Tagged:

This section documents all the release candidates towards the 2.0 release.

2.0-rc5 release notes

The Aegir team is is pleased to announce the fifth release candidate for the upcoming Aegir 2.0 release!

This release ships a ton of bugfixes we have found in RC4. We also finalised subdirectory support which, while it still has some issues, is now actually working correctly, even on multiple servers. The IP allocation code for SSL on multiple servers was also fixed, making this probably the most solid multi-server Aegir release ever. We also did some API cleanups that seemed necessary before the final 2.0 release.

Finally, we should also mentionned that the install process was significantly sped up thanks to the use of Drupal.org distributions to ship a single tarball for the hostmaster platform instead of using a makefile to build it from its parts all the times. During out tests, the platform make step went from 60 seconds to 1.5 seconds, an amazing improvement!

Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes, with 2.x-specific instructions outlined in bold.

It is still imperative that you read the the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. You should be able to upgrade to 2.x releases from any release in the 1.x series, but it's better to upgrade to the latest 1.x release first.

Known issues

Those are the critical bugs that were found in this release that you may encounter and should watch out for.

There was a problem in the Debian package, the original uploads were missing some critical files (subdir support and some makefiles). This was fixed in an intermediate package named 2.0~rc5.1.
If /var/aegir is a symlink, it will be destroyed, see issue #2118857 for a workaround.
hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
Some upgrades fail with mysterious redirection failures, see #2118061 for details.
Some upgrades may loop over one of the update_N() functions, see #2118917 for details and workaround.
Upgrading through Debian packages removes the aegir.conf Apache configuration file, dropping all sites, during the upgrade, see #2121263.
Ubuntu sausy has some changes in apache config wich breaks Aegir #2155705

Detailed list of changes

API CHANGES

remove version pinning in hostmaster, our release process now again needs to modify only one makefile (#2002114)
#1986928: Provide 2.x upgrade guidance for services
#2099889: More hosting_features checks in _drush_load hooks?
#1882708: Unused 'release_id' field in 'hosting_platform'
#2012508: hosting_context_name returns '@' if node not found
#1283738: Add new hook provision_drupal_create_directories in _provision_drupal_create_directories
the package name changed (for example) from aegir-hostmaster2 to aegir2-hostmaster, compatibility shims are available for people having installed aegir2 before, but they will be dropped in 2.0, so make sure you upgrade to this release before upgrading to aegir 2.0

NEW FEATURES

aegir install time reduced by about 60 seconds (on a cable uplink) by using Drupal.org distributions (#2002114)
#2001964: Upgrade Views Bulk Operations 6.x-1.16
#2099057: Allow _provision_drupal_create_directories to skip chmod
#2100251: Implement post-enable hook for 'hosting_*' modules
#2020075: Refactor subdirs to use proper Config class(es)
#2020079: Multi-server subdirectory support
#2096629: hook_provision_drupal_create_directories_alter by ref
#2086009: Logo Cannot be changed / disabled
#2069387: Support nonstandard ports on hostmaster-install command
#2074681: Ports are hardcoded in hostmaster.profile
#2103173: Provide an example of saving data to a site context

BUG FIXES

Login or register to post comments

2.0-rc4 release notes

An error in the manual portion of our release process resulted in the incorrect version of the code-base being built. See the release notes for 2.0-rc3 for relevant changes since 2.0-rc2.

Known bugs

In addition to those listed in the release notes for 2.0-rc3, note that some people have experienced problems with downloading a patch in the main Aegir makefile. This is most likely due to problems with drupal.org's SSL certificate. If you are experiencing such an issue, there is a simple work-around: edit the aegir.make file in the provision/ directory to make the path use http:// instead of https://.

For a Debian-based system (including Ubuntu), this would look something like:

$ sudo vi /usr/bin/drush/commands/provision/aegir.make

For 'manual' installs on other OS's, it would probably be:

$ sudo vi /var/aegir/provision/aegir.make

Change the line:

projects[drupal][patch][] = "https://drupal.org/files/common.inc_6.28.patch"

to read:

projects[drupal][patch][] = "http://drupal.org/files/common.inc_6.28.patch"

Then re-run the install. On Debian/Ubuntu machines:

$ sudo apt-get install aegir2

On manually installed systems (CentOS, etc.) as the aegir user:

$ drush hostmaster-install

Detailed list of changes

API CHANGES

None.

NEW FEATURES

None.

BUG FIXES

Fixed makefiles to point to proper versions of projects.

Login or register to post comments

2.0-rc3 release notes

Tagged:

The Aegir team is pleased to announce the third release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes a couple critical bugs in 2.0-rc2 that were causing problems when sites were being cloned or renamed. We've added a couple small features, such as additional options during hostmaster-install, and allowing the redirect to the Welcome page to be turned off. Also, we've made a small addition to the API, in that there is now a hook available (hook_provision_drupal_create_directories_alter()) to allow altering the directories created when a site installed.

In order to better support PHP 5.4, we have added a patch to Drupal core to suppress E_STRICT warnings. These were harmless, but annoying. They were caused by a changed in PHP error-reporting in PHP 5.4, and the Views module's maintainers' desire to remain backward compatible with PHP 4. For more details, see: #2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.

A number of pending issues require a new stable release of Drush (5.10), so we will work with the maintainers to help get a new release out.

Known issues

Our release process is still done by hand instead of being more automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs a number of issues to be fixed before completion, see #2046167 for details. Note that this will not block a stable release, since this feature is 'experimental', and additional re-factoring can occur during the stable release cycle.

Detailed list of changes

API CHANGES

#1283738 by halcyonCorsair, cweagans: Allow other commands to add or alter the directories to be created.

NEW FEATURES

#2069387 by cweagans, mstenta: Support nonstandard ports on hostmaster-install command.
#2067617: Allow hostmaster-install to accept '--working-copy' option.
Allow the redirect to the welcome page to be turned off.

BUG FIXES

Add E_STRICT patch to test openatrium makefile so tests will pass on PHP 5.4.
#2067603: Fix original and cloned site pointing to the same database.
#2048653: Ensure mysql is secure before proceeding with hostmaster install.
#2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.
#2038279: Warn of invalid account email on site install.
#2055949: Fix migrate drops wrong database when domain name changes.
#2074681 by cweagans, mstenta: Fixed ports are hardcoded in hostmaster.profile.
Use custom functions for block visibility.
#1940378: Fix PHP 5.4 warning by initializing an object variable prior to assigning properties.
#2050881: Call drush.php via php, since it isn't executable when installed via PEAR.
Enable platform site-list block, since it had to be renamed.

Login or register to post comments

2.0-rc2 release notes

Tagged:

The Aegir team is pleased to announce the second release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes our project makefile that, due to an error in our build process, did not pull in the latest code. As a result, installing 2.0-rc1 actually installed a 2.0-beta2 codebase. While changes between 2.0-rc1 and 2.0-rc2 have otherwise been minimal, we invite you to explore all the new features and bugfixes in 2.0-rc1.

Note that we have taken this opportunity to update our external dependencies, as well.

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

~~Issue #2046783: Task dialogs won't open after clearing the cache was the result of updating our dependencies. Refreshing the page is usually sufficient to make modal dialogs work again.~~ It looks like this was probably specific to the development environment, as we can no longer reproduce it.

A critical bug was discovered: Issue #2055949: Migrate drops wrong database when domain name changes. It has been fixed in 6.x-2.x, and a patch for 2.0-rc2 is available.

Detailed list of changes

API CHANGES

Update external dependencies.

NEW FEATURES

none

BUG FIXES

Add dependency on jquery_update, so we can use the more recent version of modal_dialog.
Enable login and nav blocks explicitly.
treat symlinks as existing, fixes #2046249

Login or register to post comments

2.0-rc1 release notes

Tagged:

The Aegir team is pleased to announce the first release candidate for the upcoming Aegir 2.0 release.

This release mainly targets a few critical bugs that were found in the second beta, mostly related to ongoing Views, Drush integration and access control. We also introduce a number of new features and finally drop support for provisioning Drupal 5 sites completely (for real this time!). Along the way, we did quite a bit of API cleanup.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems, as well as overhauling our access control. Significant improvements to the package-management system have also been introduced.

Our only remaining critical bugs are basically waiting on a new release of Drush, upgrade testing on Nginx and some contrib upgrade guidance documentation. If no other critical bugs are discovered during the time it takes us to fix these, we should move on to a full release of Aegir 2.0!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

Detailed list of changes

API CHANGES

#1034520: Cleanup package instances when deleting sites and platforms.
#1830220: Drop support for Drupal 5.
#1975086: Move log parsing and status updates to seperate functions and call them from a shutdown function.
Pass the entity type when we're sync'ing package instances.
Save the platform field when creating a package instance record.
Move to individual operation callbacks for VBO tasks.
#2022849: Record disable and delete backups in the database.
#2031491: Rename SSL permission to be more descriptive.
Clean up hosting_node_grants().
Add 'administer' permissions for platforms and servers, and allow platforms to be viewed.

NEW FEATURES

#905326 by ergonlogic, crea: Improve file path changes.
#1201174: Make UID1 username configurable.
#1345118: Make platform access control an autocomplete form.
#1515416 by ergonlogic, helmo, Deciphered: Replace listing of sites and platforms using a package with a view.
#1975086: Add 'update status' button to tasks.
#2005310: Add VBO operations to platforms view.
#2006074 by Deciphered: Enable backups via VBO.
#2025787 by omega8cc, ergonlogic, anarcat: Open site goto link in a new window/tab.
#2022813 by Deciphered: Expose backups to Views.
#2027269: Update a task's status after all Drush operations are complete.
#2031491: Review and update permissions for all roles.
#2031765: Clean up VBO operations with Action Permissions.
#2035873: Show package 'popularity' on platform package view
#2036283: Make Aegir aware of site-specific packages.
#2036793 Ignore hidden modules and profiles.
#2037045 by helmo, ergonlogic: Change some log statuses to better match Drush's log styling.
#2037965: Clean up hosting-pause.
#2038279 by ergonlogic, Jon Pugh: Validate email during site install.
Display all validation errors when adding a client, and limit to 20 suggestions.
Flag rollbacks as warnings in our task logs.
Handle package page views separately for sites and platforms.
Update default hosting_site views to use new access plugin for blocks, and add a couple more displays for non admin listings.
Add Views access plugin for hosting_site and hosting_package.
Add views handler to filter packages by status.

BUG FIXES

#1238618: Fix client form validation.
#1263264 by ergonlogic, recidive, anarcat: Specify a type when getting a package, to avoid collisions.
#1647830 by sambonner: Fix Incorrect ownership of directories under sites/example.com/private/files/.
#1861898 by ergonlogic, Jon Pugh: Don't hardcode the types of entities to which we can attach tasks.
#1975086 by helmo | anarcat: Fixed updating a task when there is none.
#2025355: view platform' permission broken
#2026417: Disambiguate site operations.
#2031491: Fix roles.
#2031747: Fix Views block placement and visibility.
#2038891: Add 'client_email' option to 'provision-install-backend'.
#2038891: Switch from '--invoke' to '--strict=0' for backend calls.
#2040285 debian: properly detect webserver, again
#2044251 drush command '@none provision-save' could not be found
#2045907: Remove extra tabs from deleted platforms.
Fix php 5.4 issue
Add missing unicode include for UID1 name validation.
Fix update hook name.
Only register shutdown function to update task status in the context of a front-end task.
Don't display package block on profiles.
Only show link to add clients on site form to those with proper permissions.
Override hook_access functions for node_grants when hosting_client is enabled.
Register node type in hosting_task's Hosting feature.
Clean up Views exposed forms.
Fix Views block placement and visibility.
Only display client sites block on the 'view' tab.

Login or register to post comments

2.0-beta2 release notes

Tagged:

The Aegir team is pleased to announce the second stabilization (beta) release of the Aegir 2.x branch.

This release mainly targets a few critical bugs that were found in the first beta, namely IP allocation on non-SSL and non-cluster sites which was completely broken and bugs the Debian package. We also introduce a few new features and finally drop support for provisionning Drupal 5 sites completely.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems.

We are down to only one active critical bug. If no other critical bugs are discovered during the time it takes us to fix it, we should move on to our first release candidate!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

Nginx support missing (issue #2020091)
If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
Multi-server support is untested (issue #2020079)
Code needs to be refactored to the new 2.x API (issue #2020075)

The move to Views has highlighted some additional issues:

Fixing #2027269: warnings and errors in front-end pre- and post- hooks are ignored for task status required a new Drush commandfile, and thus a 'drush cc drush' if upgrade between an alpha/beta release and HEAD.

The debian package still doesn't properly configure the webserver, a patch has been committed and a workaround is available in issue #2040285.

New features

Bug fixes

Login or register to post comments

2.0-beta1 release notes

Tagged:

The Aegir team is pleased to announce the first stabilization (beta) release of the Aegir 2.x branch, after nearly 3 weeks of development since our second alpha release. While we had expected an additional alpha release prior to the beta cycle, development on outstanding features went smoother than foreseen. We've added some significant features, and fixed a couple bugs and (again) made some important improvements to our API.

This release marks our feature freeze. The intention is to limit any further changes to only critical and major bug fixes. However, exceptions may be granted on a case by case basis. Our development efforts will now move to tackling all release critical bugs. Once all of these are fixed, we'll move on to our release candidate (RC) phase. That said, we expect this release to be sufficiently stable that we intend to run it in production at Koumbit soon.

Release overview

This release introduces a major new feature into Aegir core: support for installing sites in subdirectories (example.com/foo, example.com/bar, etc.). This has been our number one feature request from higher education institutions, and so we hope that this will enable greater adoption within that sector. While categorized as an "experimental" feature, we feel our approach is sufficiently strong that we're considering merging this into our core site functionality.

Additional new features include a nice homepage, fixes to SSL support and IP allocation on clusters, and we've added a couple new roles.

We've also tackled a number of bugs, especially in the Debian package, which now supports installing Aegir on Nginx servers. We've also fixed some issues introduced with the new views code, and improved nginx support.

The project's Debian repo now includes Drush 5.9, and we have migrated the 'aegir2' packages to the Testing repository.

Known issues

the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in issue #2002076
SSL support was severely broken for single servers and could lead to loss of the SSL certificate copies when a non-SSL site is installed. See commits f0980e0..9b86038 in Provision for fixes. (fixed in issue #2023621)
the Debian package is severely broken - in most configuration (e.g. clean installs but not upgrade) the install will just fail with a permission denied. See commits d4efa37 and 56d1718 for fixes.

These are related to drush:

some warnings and errors may not show up in Aegir's task logs, making it believe tasks succeeded when the actually failed. this affects only hosting-queued. (issue #1931000 / issue #1982502)
our release process is now done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

Nginx support missing (issue #2020091)
If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
Multi-server support is untested (issue #2020079)
Code needs to be refactored to the new 2.x API (issue #2020075)

API changes

Multiple files can be managed in a single context now (see issue #2000038, issue #1784108)

New features

Support for installing in subdirectories (issue #705026)
Proper homepage on startup so non-logged-in users don't see an error page, and new users have basic instructions (issue #1793740)
SSL support for clusters should now work properly (issue #2000964)
New roles added: 'aegir platform manager', 'aegir administrator' (issue #1403208)
Convert list of platforms to use views (Issue #1876350)

Bugfixes

Debian package support for nginx was severely broken issue #2001142
the views bulk operations version shipped with alpha2 had security issues, see issue #2001964
an update hook was incorrectly named, and has since been fixed. The updates should not be destructive, but may output errors.
Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.
fix warning "Invalid argument supplied for foreach()" (issue #2005698)
fix "Unknown options for provision-save" error (issue #1972286)
removed hardcoded checks for IP addresses in settings.php that belong to core (issue #2013683)
Views filter for status does not tell what to filter for (issue #1997088)
nginx cloaks database credentials properly now
configure nginx to properly talk to the default php-fpm configuration in Debian (issue #1635622)
lots of fixes for the Debian package, including
- Silence garbage in the install output (issue #2002076)
- nginx support in sudoers file (issue #2001142)
- nginx autodetection in Debian package (issue #2003712)

Login or register to post comments

2.0-alpha2 release notes

The Aegir team is pleased to announce the second preview (alpha) release of the Aegir 2.x branch, after nearly 3 months of development since our first alpha release. We've squashed a number of tenacious bugs, added some nifty features, and made some important improvements to our API. We expect at least one more alpha release before we call a feature-freeze, and begin out stabilizing and cleanup (beta) release cycle.

During this release cycle, we also began work on Aegir 3, a more-or-less straight port of Aegir 2 to Drupal 7. We continue to sync changes in 2.x to our 3.x branch, and look forward to continuing the port (and beginning to add new features) as soon as we've released our first stable 2.x release.

Our next alpha release will target getting sub-site support (example.com/site1, example.com/site2, etc.) into Aegir core as an experimental feature. This has been our number one feature request from higher education institutions, and so we intend to incorporate it into Aegir 2, in order to enable greater adoption within that sector. We have a fairly detailed implementation plan, and so feel confident that we can incorporate this major feature, in fairly short order.

Release overview

This release features improvements to the IP management mechanisms that were broken in the last alpha1 release. We now manage IP addresses individually, and check if an IP is in use before allowing it to be deleted.

We also finally leave the files alone on spokes in the multi-server model, a long-standing bug in the 1.x series that led to data loss. A lot of work was done to standardize the Nginx configuration to allow for simpler, yet optional, configurations that leave the admin in charge of choosing the optimisation methods.

Also, we've moved Hosting and Eldir back to their own projects, and are now included via our makefiles. This simplifies building custom install profiles, though it complicates our release process somewhat. We've also added a drupal-org.make that will eventually allow proper distribution bundling of Aegir.

Finally, we've moved to using Views and View Bulk Operations for our lists of sites, platforms and packages. While there remain some rough edges, this will allow much easier customization of our principal UIs. It has also significantly reduced the custom code we have to maintain, in favour of exported Views, which simplifies maintenance.

Known issues

the Debian package support for nginx is severely broken #2001142
the views bulk operations version shipped with alpha2 has security issues, see #2001964
the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in #2002076
an update hook was incorrectly named, and has since been fixed. This may cause the hook to be run again, if the site is upgraded to a newer version. The updates should not be destructive, but may output errors.
Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.

API changes

deprecate hosting_ip_delete_revision(), dupe of hosting_ip_delete() now that revisions are gone (8 weeks ago)
allow running tasks that appear to be running with --force
remove deprecated DEBUG flag in debian package
#1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
#1945950: Rename provision_drupal_sync_site_back()
#1083366: Make the spokes authoritative for files/ and private/ directories
#1812338: Refactor sync back
a new control file has been introduced in /etc/nginx/basic_nginx.conf to force the nginx configuration to be the "simpler" one (see #1635596: nginx: do not decide the policy for users)
#1987026: Move generated platform drushrc.php to sites/all/drush

New features

#1929372: Flag tasks with logged warnings
#1515416: On a package page, show table listing sites and platforms using the package
#1853620: Add db_name to site summary
#1681904: Ability to configure a url to redirect to in site configuration.
#1968226: manage each IP individually on the server level - manage IPs individually
add uninstall command
Nginx Security: BEAST attack protection and fix for PCI compliance.
#1980136: Allow setting default profile from the front-end.
#588728: Replace custom lists with Views and VBO for sites, platforms and packages.

Bugfixes

#1930670: Duplicate entry 0 for key PRIMARY in hosting_ip_addresses when installing / upgrading
#1907028: user warning: Table 'XXX.hosting_ip_addresses' doesn't exist
#1961920: nginx: [emerg] invalid number of arguments in "limit_conn_zone" directive in /etc/nginx/conf.d/aegir.conf
#1923490: Incorrect error message in aegir-provision2.preinst
#1901508: "gzip --rsyncable" is invalid on OS X
#1678528: Database deleted on edge cases
#1930740: provision-delete leaves a drushrc.php lying around
Nginx: Do not override Nginx name with fake Apache name.
#1990370: Enable Hosting feature dependencies.

Other

#1923552: Rename 'Queue runner settings' tab to 'Queue daemon'
#1834036: Add 'hosting platform pathauto' to the .gitignore
#1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
#1979496: Update upgrade.sh.txt for Drush 5
#1974752: Document old_uri option for provision-deploy

Login or register to post comments

2.0-alpha1 release notes

The Aegir team is pleased to announce the first preview release (alpha) of the Aegir 2.x branch, after almost 2 years of development. We have been pretty busy with the maintenance of the 1.x branch, so development has been sometimes intermittent, but it is not over yet!

This release is only a first of a series of alpha releases that are tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published on a more regular basis in the weeks to come as more features from the new provisional roadmap are implemented. We are still considering the following:

We have set the following priorities:

subsite support (#705026) - now that mig5 did most of the work ;)
nginx cleanup (#1635596, #1635622, #1622846, #1635586, #1608910) and Nginx Debian package (#1348560)
files/ sync settled (#1083366)
~~SSL code cleanup (#941870, see also this report)~~ - done! Now onto testing and fixing the actual bugs linked from #941870

We would like to get those in 2.x, but since no one has really started significant work on those, we are more likely to simply postpone those to 3.x at this point.

standard archive support (#1138882, original roadmap description)
intersite security (the infamous #762138)
more intelligence in spokes (original roadmap description)

Also, since every single attempt at providing a proper timeline for the final 2.0 release has failed miserably, we'll just stop trying our luck and just give up on a formal timeline. Instead, we'll just do the freaking work. :) Also remember that the port to Drupal 7 has been postponed to Aegir 3. Aegir 1 and 2 both support provisionning Drupal 7 sites, but the frontend is running Drupal 6. We are aiming for a "straight port" (no rewrite) of the frontend for Aegir 3.

Table of Contents

1. Major changes
2. Major API changes
3. Installing and upgrading
4. Need help?
5. Features and improvements
6. Bugfixes
7. Known issues

1. Major changes

This first alpha already packs a lot of changes. Those release notes detail the changes since the 2.x branch was first created, all the way back two years ago, when 1.0 was released. Of course, we are not detailing all the changes made in the 1.x series that are all part of the 2.x, but only the changes specific to the 2.x release.

SSL improvements:
- IP allocation was moved to the backend to the frontend
- SSL certificate generation now has saner defaults (e.g. 2048bits)
- better error handling
Drush 5 support
- includes better support for archive-dump command
- means we also drop the dependency on drush make 2.3, now included in Drush 5
- support for Drush 4 has been dropped, the minimum version is now 5.5
Debian package improvements and changes
- Nginx support in the Debian package
- now a "native" debian package
- package name changed: it is now aegir2, aegir-provision2, etc, to avoid overwriting the previous package - note that aegir 1 and 2 can not be installed in parallel
Nginx improvements:
- fixed support for nginx 1.3 and newer
- better defaults for caching
- SSL and Nginx are now officially supported (not marked as "experimental")
New modules:
- the hosting-queue-runner module is now merged into core as hosting-queued
- "pack" module, designed as a lightweight replacement to the "cluster" module, now available as an experimental extension
Hosting-queued improvements
- run with a lower priority ("niced")
- improved portability and reliability of startup script
- enabled by default in the Debian package
Code refactoring and improvements:
- now using the Symphony autoloading code
- fix coding style in a lot of source files
- improved builtin test suite
- eldir is split in its own module again, allowing for porting it more easily to Drupal 7

A more detailed log of bugfixes and improvements is available below.

Back to top

2. Major API changes

Those changes are, as usual, more explicitly documented in the upgrade path documentation.

hosting-task now needs a --force argument to run a non-queued task
functions that were deprecated in 1.x are now removed
the email and client_email database fields are now removed from client and site node types
numerous changes to the IP allocation and SSL management code

Please note that the 2.x API is still not considered stable and may change without warning until 2.x is fully stabilized, see our release process for more information.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes.

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

Back to top