Migrating the Privacy Proxy

The PrivacyProxy service provides the outgoing traffic to the Internet.

The privacy proxy service migration is a step of the service nodes migration to Azure.

Migration is performed within one maintenance (migration) window.

Migration Procedure

To migrate the PrivacyProxy service to Azure:

• Step 1. Prepare a new VM with a new IP address in Azure for Privacy Proxy (Azure).
• Step 2. Configure the target PrivacyProxy with the new IP (Azure).
• Step 3. Update the APS Connection proxy settings (PCP).
• Step 4. Remove the source PrivacyProxy (On-Premise).

Step 1. Prepare a new VM with a new IP address in Azure for PrivacyProxy (Azure)

1. Create a VM in Azure with a private IP address.
2. Check the outbound access to the Internet.

3. To prepare the VM for registration in CloudBlue Commerce, set up sudores for the user that will be used for registering the VM in CloudBlue Commerce:

   # vim /etc/sudoers.d/waagent
   <USER>        ALL=(ALL)       NOPASSWD: ALL

   where <USER> is the user that will be used for registering the VM in CloudBlue Commerce.

Step 2. Configure the target PrivacyProxy service with the new IP address (Azure)

1. Register the VM prepared above in CloudBlue Commerce.

   1. Go to Infrastructure > Service Nodes. Click Add New Node and complete the fields.

      Note: Use the private IP of the VM both as Exclusive and as Shared during the registration because for the deployment of a Privacy Proxy to Azure, a private IP  is sufficient, a public IP  is not necessary.

   2. Make sure that the "node_registration_..." task from the queue is completed.
2. Deploy the PrivacyProxy PPM package to the Azure VM:
   1. Go to Infrastructure > PPM Group Operations > click Create new PPM group operation > select Installation > select the linpps01 host > set PrivacyProxy to other > click Finish.
   2. Wait to make sure that the "Install PrivacyProxy to..." task is completed.

3. Check the outbound access to the Internet through the proxy on the proxy and MN nodes:

   wget -e use_proxy=yes -e http_proxy=<PROXY_IP>:<PROXY_PORT> http://download.platform.cloudblue.com/cb/20.5/updates/updates.xml

   where:

   • <PROXY_IP> is the IP address of the target PrivacyProxy service;
   • <PROXY_PORT> is the proxy port of the target PrivacyProxy service.

   For example:

   wget -e use_proxy=yes -e http_proxy=10.94.45.201:8008 http://download.platform.cloudblue.com/cb/20.5/updates/updates.xml

4. Update the Repository proxy URL field at PCP > Package Repository > YUM Configuration.

Step 3. Update the APS Connection Outbound Proxy Settings

Update the outbound proxy configuration in CloudBlue Commerce:

1. Go to System > Settings > APS Connection > Proxy settings > the Outbound Proxy section.

2. Update the mandatory Hostname and port field in the following format:

   <PROXY_IP>:<PROXY_PORT>

   where:

   • <PROXY_IP> is the IP address of the target PrivacyProxy service.
   • <PROXY_PORT> is the proxy port of the target PrivacyProxy service.

   For example:

   10.94.45.201:8008

Step 4. Remove the source PrivacyProxy service (On-Premise)

1. Remove the source PrivacyProxy service from the proxy node:
   1. Go to Infrastructure > PPM Group Operations > click Create new PPM group operation > select Deinstallation > select the necessary host > set PrivacyProxy to other > click Finish.
   2. Wait to make sure that the "Deinstall PrivacyProxy..." task is completed.

2. Remove the On-Premise privacy proxy node from CloudBlue Commerce:

   Go to Infrastructure > Service Nodes > select the necessary host > click Delete.