Convert Isolated Install to Production Mode
The quickstart documentation suggests setting up an
installation for quick PoC and Trial testing. Should you want to convert
to a system managed
Production install mode, RackN recommends you
re-install from scratch. However, the below article may help you convert
or migrate should you choose to not do a fresh install.
There currently is no officually supported migration tool to move from
Production install mode. However, any existing
customizations, Machines, Leases, Reservations, Contents, etc. can be
moved over from the Isolated install directory structure to a Production
install directory, and you should be able to retain your Isolated mode
All customized content is stored in the following default subdirectories as:
- Isolated: in
drp-data/in the Current Working Directory the installation was performed in
- Production: in
The contents and structure of these locations is the same. Follow the below procedure to safely move from Isolated to Production mode.
- backup your current
tar -czvf /root/drp-isolated-backup.tgz drp-data/)
- perform fresh install on same host, without the
- follow the start up scripts setup - BUT do NOT start the
dr-provisionservice at this point
- copy the
drp-data/*directories recursively to
unalias cp; cp -ra drp-data/* /var/lib/dr-provision/)
- make sure your startup scripts are in place for your production mode
- start the new production version with
systemctl start dr-provision.service
- verify everything is running fine
- delete the
drp-datadirectory (suggest retaining the backup copy for later just in case)
As of DRP Version v4.3.0, content writable objects are no longer stored in raw JSON files in these directories. They have been moved to new WAL (write-ahead-log) journalled database objects.
If you install a new version of the Digital Rebar Provision service, you
must verify that there are no Content differences between the two
versions. Should the
dr-provision service fail to start up; it's
entirely likely that there may be some content changes that need to be
addressed in the JSON/YAML files prior to the new version being started.
See the rs_upgrade notes for any
version-to-version specific documentation.
Additional resources and information related to this Knowledge Base article.
v3.x to v4.3.0, but not including v4.3.0
dr-provision, isolated, production, migration, conversion