Clone Environment

Objective

This guide explains how to use Clone Environment on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

When developers need to separate running applications For example, Want to add a new work system before actually using it in production? Ruk-Com Cloud has already prepared a method for doing this. Env cloning is creating an Env that is the same as the cloned Env with just a few clicks.

In addition, if we talk about a system that has work from many development teams, the system is complicated. It is recommended to clone the application into several copies. is the operation of making ApplicationlifecycleThe steps are to separate the application into 3 parts as follows.

• development- For developers to create and then improve programs
• testing- For quality auditors to check and analyze various program problems.
• production- For general users, it will be the most complete version of the program.

Below we have prepared a guide forHow to clone an environmentandExamples of general use

Note:Consider and checkFollow the steps below to clone an env to Ruk-Com Cloud:

- Cloned containers will depend onscaling modeThe cloned container is created from the base image (the original program that has not customized the settings of the cloned Env). This format is called "stateless" or it copies the settings from the main container of the clone. This format is called "stateful".

- You may experience a short continer freeze while cloning nodes (see the manual for details on how this works).live migration)

- While cloning the Windows-base Container related env will crash, so get ready for a short downtime.

How to clone an environment

The Env cloning process can be done in the following steps.

1. Select the buttonClone Environmentof the Env to be cloned is shown in the illustration below:

2. After pressing the button, a pop-up will appear. Enter the name of the Env or use an existing default name. Once you have set your name, press the button.Clone.

3. Within a few minutes, the cloned environment will be ready to use.

Tips:In some cases additional modifications are required to be able to clone your Env:

- The IP addresses and hostnames of cloned nodes will be different from the original ones, so if they were configured they will need to be changed after the clone is complete.

- If you are having trouble cloning a large environment (i.e. more than 1TB of data is stored in a container), please contact your hosting provider for assistance.

- Env that is in the formatcollaboration(Envs with shared users) can only be cloned by the owner of the Env. People with shared user rights cannot clone.

After cloning is complete, you can modify the program version, adjust various system structures without affecting the cloned Env.

Examples of general use

Once you can clone it. We have provided an example of usage after cloning an Enviroment in the example below.

• Change the domain name of your Env.
• doingswap domainsTo change the website entry path for your users to access in the new cloned Env.

• Proceedingsblue-green deploymentTo reduce downtime or errors in the deployment process.

• Conduct A/B testing (A/B testing) of the application (e.g. comparing different versions) to determine which offers better user engagement.

• Perform load balancing to reduce errors (failover protection) that will happen to your system.

• Makes it possible to store data from multiple envs inDedicated Storage ContainerSame way to manage storage space more efficiently
• Use the cloned Env to create a "snapshot" with all the settings already set.
• You can determine the value of the production data you have cloned, ensuring that the data is exactly what it is in. testing/staging env without affecting production

These use cases can help you get the most out of env cloning.