CLI Tutorial: Server Scaling

Objective

This guide explains how to use CLI Tutorial: Server Scaling 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.

Once an environment is created, in some cases the topology may need to be changed - for example Scaling a particular server or modifying the entire environment layer (using scalingVerticalandHorizontalrespectively) due to the changing incoming load. The topology can be modified usingchangetopologyCLI:

~/jelastic/environment/control/changetopology --envName {env_name} --env '{"engine" : "{engine_type}"}' --nodes ['{"nodeType" : "{node_type}","count" : {nodes_amount}, "fixedCloudlets" : {cloudlets_amount}, "flexibleCloudlets" : {cloudlets_amount}}, {"nodeType" : "{node_type}", "count" : {nodes_amount}, "fixedCloudlets" : {cloudlets_amount}, "flexibleCloudlets" :  {cloudlets_amount}}']

Set parametersAll possible methods are the same.Creating the environmentexcept–envName{env_name}- points to an existing environment that should be modified

The remaining options in this example We use the following options:

• {engine_type}- The selected environment instance type is driven by (mandatory string)
• {node_type}- Stack type specified according toItem
• {nodes_amount}- Number of nodes configured (usedHorizontal scaling)
• {cloudlets_amount}- number of cloudlets defined (fixedCloudlets) or flexible (flexibleCloudlets) to be allocated for the specified node type. (use scalingVertical)

More:Optimal functionality for horizontally scaling server applications. Nodes should be added.load balaningfor your topology in advance. (if it doesn't exist)

Reconfiguration of the environment topology can take several minutes to complete.