Migrating from Rundeck Team to Rundeck Enterprise (RPM Installs)

Nathan Fluegel
Customer Success Manager

Migrating from Rundeck Team to Rundeck Enterprise (with RPM installations)

When carrying out a migration like this, there are at heart two main approaches you can take. The “safest” choice is typically to install the new version on a fresh server and migrate your Rundeck projects from the old instance to the new one. The “faster” choice would be install your new version on the same server as the old one. Below are the general steps to follow for both alternatives. These steps assume, generally, that you are running Team and therefore Enterprise on a single server. There are some additional steps you might carry out if you are moving to . a cluster with two or more servers.

The “safe” migration method

This method ensures that you will have all of the current default settings in your new install, such as project config in the database, automatic configuration of keys and other settings, etc.

  1. Install/setup Rundeck Enterprise on a new server
    1. Connect to a clean new Rundeck database
    2. Connect to your Enterprise authentication server
    3. Get a new license key for the new server, based on the new server(s)’ Rundeck UUIDs
    4. Import any custom ACL policies through ACL GUI
  2. Export any active projects from your Rundeck Team server
  3. Import active projects into Rundeck Enterprise server
  4. Point your team and any load balancer to the new server

The “faster” migration method (rpm-installed platforms)

If you are following this migration path, it is advised that you are on the same Rundeck major version both before and after the migration. If your current environment is on Rundeck Team 2.×, please upgrade to Rundeck Team 3.x first before you migrate to Rundeck Enterprise 3.×.

Steps for “faster” migration

  1. stop rundeck:
# service rundeckd stop
  1. install rundeckpro enterprise:
# yum install rundeckpro-enterprise
  1. remove rundeckpro team:
# yum remove rundeckpro-team
  1. start rundeck:
# service rundeckd start
  1. install enterprise (cluster) license.
  2. set execution mode to “active”.
  3. takeover scheduled jobs if any via api or rd-cli tool(recommended):

Takeover schedules using the api:
Docs page for taking over schedules on a Rundeck cluster

For example:

$ curl -X PUT -H "X-RunDeck-Auth-Token: TOKEN.HERE" -H "Content-Type: application/xml" -d "<takeoverSchedule><server all=\"true\"/></takeoverSchedule>" http://RUNDECKENTERPRISE.SERVER:4440/api/31/scheduler/takeover

Take over scheduled jobs using the rd-cli tool:
Github site for Rundeck CLI tool

For example:

$ cat ~/.rd/rd.conf
export RD_URL=http://RUNDECKENTERPRISE.SERVER:4440
export RD_TOKEN=TOKEN.HERE
$ rd scheduler takeover -a