Migrating your Developer Portal OVAs from Debian V7 to Ubuntu V16.04

It is strongly recommended that you migrate your Developer Portal to the Ubuntu V16.04 base now because support for Debian V7 upgrades was withdrawn in May 2018. To migrate your Developer Portal OVAs from Debian V7 to Ubuntu V16.04, you need to upgrade your existing Debian OVAs, if not already on the latest version, deploy and configure the new Ubuntu OVAs to replace them, and then shutdown all the Debian OVAs.

• Migrating by clustering new Ubuntu nodes with the existing Debian nodes.
  1. Ensure that you complete the pre-migration checks described previously, and that the Distribution version of your Debian nodes matches that of the Ubuntu nodes that you are migrating to.
  2. If your Developer Portal is a stand-alone Debian machine, you must set that machine to be in a cluster of one member. Run the following command:

     [[ $(dbstatus) == "Standalone" ]] && set_cluster_members -c

  3. Deploy the Ubuntu V16.04 OVAs. You must deploy as many Ubuntu OVAs as there are Debian OVAs in your Developer Portal cluster. Deploy the portal OVAs as described in Deploying the Developer Portal OVA file, and then configure them as described in Installing the Developer Portal; you must complete all the steps described, ensuring that the Management cluster that you specify is the same as that used by the Debian nodes.
  4. Ensure that the Ubuntu nodes report the same time and NTP server as the Debian nodes. All nodes must also have their operating system timezone set to UTC; this is the default setting so you need to change this only if it has been changed previously.
  5. On the first configured Ubuntu portal node, run the following command:

     touch /var/aegir/config/nginx.conf

     and then add this node to the cluster by running the following command:

     set_cluster_members IP_address_of_an_existing_Debian_7_ova

     Repeat the set_cluster_members command for every Ubuntu OVA that you are adding to the cluster.
  6. Run the status command.
     Check that every server is marked as SUCCESS. It might take several hours for large deployments to fully replicate across all servers.
  7. If the sites on the Debian nodes are still being used, you need to restart nginx on the sites so that they can use the updated nginx config file that was replicated from the Ubuntu node. To do this, run sudo service nginx restart on all of the Debian nodes.
  8. Add the new Ubuntu OVAs into the existing load balancing configuration for the Developer Portal user interfaces, and for the SSH communication from the Cloud Manager. For more information, see Load balancing in IBM API Connect and Load balancing the requests the Cloud Manager sends to the Developer Portal.

     If the configuration does not use a load balancer, edit the IP address for the Cloud Manager SSH communication to match one of the new Ubuntu OVAs (modify the Portal Management Address field in the Cloud Manager UI, see Installing the Developer Portal).

  9. Shut down all of the existing Debian V7 OVAs, by logging in to the CLI for each Debian machine and running the following command:

     queue_run -qp && sudo halt -p

  10. Log in to one of the Ubuntu V16.04 machines, and run the following commands depending on whether you are configuring a cluster of machines, or a stand-alone machine.
      To recluster with the currently visible Ubuntu machines, run the following command:

      set_cluster_members -v

      For a stand-alone Ubuntu machine, run the following command to de-cluster the single machine and convert it to stand-alone mode:

      
      set_cluster_members -v1

      Your cluster of Ubuntu machines, or stand-alone machine, is set up.
  11. Apply the latest 5.0.8.x fix pack/interim fix that is available on IBM Support Fix Central.
• Migrating by using a backup file. If you can have only one virtual machine at a time in your environment, you must complete the following instructions to migrate your Developer Portal OVA from Debian V7 to Ubuntu V16.04. The backup file method should be done on a stand-alone Debian node to a stand-alone Ubuntu node only.
  1. Complete the pre-migration checks described previously.
  2. If the Debian deployment is part of a cluster, reduce it down to a single node by using the set_cluster_members -d command.
  3. Back up your Debian Developer Portal by using the backup_devportal command, and then save the backup to a separate FTP/SFTP server.
     For more information, see backup_devportal.

     Important: You must save your backup to a separate server. Otherwise the backup is lost when you delete your Debian Developer Portal in the next step.
  4. Delete your Debian Developer Portal virtual machine.
  5. Deploy the Ubuntu Developer Portal OVA in place of the deleted Debian one, and set the same IP address and host name as the deleted Debian OVA.
     For detailed instructions, see Deploying the Developer Portal OVA file.
  6. Configure the Ubuntu Developer Portal to connect to the management server. For detailed steps, see Installing the Developer Portal.
  7. Copy the Debian Developer Portal backup that you created in Step 3 to the newly deployed Ubuntu server by using FTP, SFTP, or SCP. Then, restore the site by using the restore_devportal -scn command.
     For example:

     restore_devportal -scn backup_file_absolute_path

     where backup_file_absolute_path is the location of your backup file. For more information, see restore_devportal.
  8. Run the status command.
     Check that the server is marked as SUCCESS.
  9. Apply the latest 5.0.8.x fix pack/interim fix that is available on IBM Support Fix Central.