rBuilder:Update Path to 4.1.0

From rPath Wiki

Migrations to rBuilder 4.1.0 require that your current rBuilder version is of 4.0.0 or higher. If you are currently using rBuilder 3.1.4 or earlier, you must first update to 4.0.x before moving to 4.1.0. Because of major changes in the partition structure and job handling, updating to 4.1.x from pre-4.0.x releases requires a backup, new installation, and restore process as described here. Additionally, rBuilder 4.0.0 runs on 64-bit processor architectures only. Because of these changes, rPath is assisting each customer with the 3.x to 4.0.x update process.

Customers with rBuilder 3.1.4 or earlier should contact an rPath representative to schedule an update to rBuilder 4.0.1.

Why is this update different?

Starting with version 4.1.0, the conary repositories for products in rBuilder should use PostgreSQL databases instead of SQLite databases. PostgreSQL provides better performance, improved concurrency, and higher reliability. After updating rBuilder to 4.1.0, schedule a maintenance window as appropriate prior to migrating to PostgreSQL.

rPath strongly recommends you convert to PostreSQL using the provided link in the menu; until your rBuilder appliance has done this, you are in an unsupported configuration.

Unlike appliance updates performed in the rAPA interface, this migration is irreversible. However, the migration creates new databases and allows users to test the PostgreSQL conversion before selecting to finalize the change and remove the old databases.

This update also moves the rBuilder Appliance to Conary version 2. During regular system updates, Conary will update to version 2 and convert the internal package repository (including rollbacks) to be version compliant. Depending on how large your Conary repository is, this may lengthen system update time considerably.

Prepare for the Update

To prepare for this update, rPath recommends that you make a backup of your current configuration and repository.

Schedule an Update Window

This update will require rBuilder to be in maintenance mode for a window of time that may impact its users. Schedule this window and announce it to users so they can plan appropriately. During the maintenance window for PostgreSQL migration, a site administrator must put the appliance in maintenance mode. Then, as noted previously, an appliance administrator should ensure there is a current backup of the appliance to preserve the product repository contents prior to migration.

Update to rBA 4.1.0

• Log in to the rBuilder interface as an administrator.
• Place rBuilder into Maintenance mode.
• Log in to the rAPA interface as an administrator.
• Make a backup of your current configuration and repository.
• Click the System Updates task on the left navigation panel.
• Click the Check Now button to start checking for available updates.
• Click the Apply Updates button to apply the updates shown.
  • As noted previously, the first series of updates will be moving the system from Conary 1 to Conary 2. There may be an extended wait while Conary moves to version 2.
  • The updates plugin will apply updates to your rBA...if a restart of rAPA is required, do so.

Convert to PostgreSQL

1. Access and log in to the rPath Appliance Platform Agent web interface. The PostgreSQL Conversion task will appear immediately following login.
2. Click the Convert button to begin the conversion process.
3. Close all other applications that may interrupt the conversion process (browser tabs, updates, etc).
4. Read the warning dialog and click Convert Now to proceed.
5. Follow the PostreSQL Conversion prompts to continue the process.
6. Click OK when the conversion process reports "Completed Successfully".
7. Remove rBuilder from Maintenance Mode.

After the conversion, administrators should exit maintenance mode and allow developers to verify that their day-to-day interactions can resume using the converted product repositories.

If developers are confident they can continue their work without any issues, administrators should

1. Access and log in to the rPath Appliance Platform Agent web interface. Note the PostgreSQL Conversion task is still present immediately following login.
2. Click the PostgreSQL Conversion task on the left navigation panel.
3. Click Finalize to finish the conversion process (this will remove the Repository Conversion task from your view). This also removes the old databases to free up disk space.

If developers experience issues interacting with product repositories and are not able to continue their work, the Designated customer representative should contact rPath immediately for assistance in repairing the migration.