C Removing a Site to from an Existing Georedundant Deployment

Prerequisites
  • NEF connected to a cnDBTier is up and running. This is referred as Site-1 (CAPIF-1 and NEF-1).

This section describes the procedure to remove a site (Site-2) from an existing georedundant NEF deployment.

  1. Offboard all the API invokers from CAPIF of the site that needs to be removed.

    This deletes all the subscriptions related to the API invokers onboarded on the CAPIF that needs to be removed.

  2. Upgrade the NEF instance on the surviving site to remove the details of the CAPIF of the site to be removed.
  3. Uninstall the CAPIF instance from the site to be removed.

    Note:

    • The CAPIF instance removed from a georedundant deployment must not be used in any other NEF deployments or as an standalone CAPIF. It is recommended to uninstall the CAPIF and then install again.
    • NEF supports only 2-site.
  4. Uninstall the NEF instance from the site to be removed.
  5. Remove the DB Replication and the NDBCluster on the site to be removed.
Example:
The following steps provide an example to remove Site-2 that consists of NEF-2 and CAPIF-2 whereas, Site-1 with NEF-1 and CAPIF-1 is the surviving site:
  1. Offboard all the invokers from CAPIF-2 on Site-2.
  2. Upgrade NEF-1 to remove details of CAPIF-2 from the ocnef-custom-values.yaml file during upgrade on Site-1.
  3. Uninstall CAPIF-2 instance from Site-2.
  4. Uninstall NEF-2 from Site-2.
  5. Remove the DB Replication and the NDBCluster on Site-2.