Setting Up Environment

Objective

This guide explains how to use Setting Up 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.

The first step of a hosting application is to create an environment with the required container isolation.
Ruk-Com Cloud PaaS provides a powerful and easy-to-use UI. To create and configure the environment according to your needs. This article will walk you through all the necessary steps along with additional specifications and explanations about the features.

1. Start by logging into the Ruk-Com Cloud Dashboard and clicking the New Environment button in the top left corner.

2. Within the topology wizard you can set all necessary customizations. We recommend making adjustments in the following order:

• Choose a programming languageor a dedicated deployment solution (Docker Engine or Kubernetes Cluster)
• Set topologyBy adding the required software stacks
• Configurenodes resources and specifications
• Check the valuation, environment name, andConfirm environment creation

Below we will talk about each of them in detail, giving a description of all the possibilities of their work. Once you're familiar with the process, you'll be able to define a new environment (or modify an existing one) in less than a minute.

Choosing a specific programming language or deployment option

The first step in creating an environment is to choose the deployment solution required for your project. Ruk-Com Cloud PaaS is a highly scalable platform. It supports a wide range of options for application development and hosting. Therefore, it is most suitable for the needs of customers.

1. Recommended and most common options. Any container (unless specifically executing the application/architecture) is a certified container. These stacks are configured and managed specifically from Ruk-Com Cloud (such as version updates, etc.). Security Installation) By default, the platform supports all features. (scaling, auto-deploy, redeploy, SSL, etc.) for the smoothest and most convenient hosting and development.

Click the tab to select the desired programming language (Java, PHP, Ruby,.NET, Node.js, or Python) to proceed with.Ruk-Com Cloud Containerthat has been certified

2. Other deployment options are available on the Docker tab. The options listed below are based on the Ruk-Com Cloud container system (also called an OS container), which allows for the majority of interoperability. (but not all) platform features such as vertical and horizontal scaling

• Custom Docker Containers- Docker image according to operating systemSupported OSand deploy into the container system Compared to managed containers This option provides access to a wider range of solutions, such as searching the entire Docker Hub registry or private storage.
  However, software functionality and platform compatibility cannot be guaranteed because the content is managed by the respective image administrators. We therefore recommend creating a custom Docker image based on the image.certifiedand then using the commandFROM
  
• Docker Engine-Docker Engine CEdeploying containers provides access to traditional Docker functionality, including installation, scaling, and internal management.Container application
  
• Kubernetes Cluster- Kubernetes clusterAvailable with pre-configured master and container-based worker nodes, the installation, scaling, and internal control/management of the microservice is handled by Kubernetes, while Ruk-Com Cloud scales and manages the master and worker nodes.
  
  

3. We also recommend selectingRegionas you wish (if any) before proceeding further.

Topology settings

You can configure your environment topology through the wizard on the left. Refer to your environment wizard as the following blocks:

• Load Balancers- The working stack is the starting point for the environment to distribute incoming requests and create load on other nodes.
  
• Application Servers(calculation nodes) - The web server that runs on your application.
  
• Databases(SQL & NoSQL) - Database solutions for data storage and management.
  
• Cache Node- Memcached object caching system to speed up applications and reduce database load
  
• Shared Storage- Dedicated storage with NFSv4 support, disk expansion and optimized performance
  
• Elastic VPS- Virtual private server on CentOS, Ubuntu, Debian and Windows OS.
  
• Build Node- Automation tools for Java projects
  
• Extra(custom layer) - any of the above stacks

1. Ruk-Com PaaS has several popular options for each of these segments. You can enable the blocks you want for the environment and select the functionally appropriate stack.

Tips:If you can't find the software solution you're looking for, you can add a custom Docker container from Docker Hub or a personal repository.

2. SSL protection can be configured for your environment through the section of the same name. Two options are available:

• Built-In SSL- Activate a trusted SSL certificate, avoid additional verification and save your time in certificate verification. However, it can only be used with the domain name of the default environment (such as the domain of the end host) and will not work if there is a public IP attached to your server.
  
• Custom SSL- Displays the prerequisites for using a custom SSL certificate for the environment by clicking the button.Enableto automatically comply with requirements (such as activating a public IP), and you can click on the link for further instructions.

Tips:Also you can useLet’s Encrypt SSLAdded after creating the environment to automatically issue free SSL certificates.

Configuring node resources and specific information

Once the topology is defined, you can modify each layer in the middle of the wizard. This section describes the different options available.

1. You can switch layers.ON/OFFYou can also change the alias name yourself.

2. Configure the scaling settings.automatic vertical scalingBy setting the number of dynamic cloudlets (1 cloudlet = 128 MiB of RAM and 400 MHz of CPU) for nodes within a layer.

Minimum and maximum CPU & RAM capacity per server That is, no matter how high the scaling limit is, only the resources actually used will be charged. This will solve the problem of load lags, while at the same time you will not overpay for unused memory or processor.

3. In the sectionhorizontal scalingIt helps to define the number of nodes within a layer and choose your preferred scaling mode (stateful or stateless).

To make additional modifications, you can click the dropdown to change the required stack and version in the case of modifying an existing environment. These items will redirect to the redeploy container to deploy the changes.

Tips:Click the gear icon for additional options regarding management during resizing.

4. Configure additional settings.

Each item may vary. It depends on the particular stack and account permissions.

• Auto-Clustering- Automatic grouping of approved templates Additional information can appear after activation. such as selecting items (master-slave, master-master or Galera) for database cluster
  
• Disk Limit- Number of disks reserved per node, and most shared storage containers have larger capacity.
  
• Sequential restart-delay- Delaying the completion of a restart operation on one node and starting another node to avoid downtime and ensure that at least one server is still running. You can set the value to "-1" to restart all nodes within a layer simultaneously.
  
• High-Availability- Automatic session simulation for Tomcat and TomEE server applications.
  
• Access via SLB- Block access to layer nodes through the Shared Load Balancer platform
  
• Public IPv4/IPv6- Attach a specified external IP address to each node within the layer.
  

5. Below you will see buttons for configuring the container:

• Variables- Check and manage your listenvironment variablesfor the current layer
  
• Links- Connect layers within the environment
  
• Volumes- Manage lists of volumes to ensure file integrity throughout the container lifecycle
  
• Ports- View information about a container's port.
  
• CMD/Entry Point- Configure the Entry Point and Run Command of the container.
  

Verify and confirm Environment creation

After completing all the configuration, you can check the amount of allocated resources and the approximate cost of the environment.

1. The unit of measurement for Ruk-Com Cloud PaaS resources is cloudlets. You can view the number of reserved items.reservedand dynamic scaling limits for the entire environment.

for better analysis Values are divided into groups by color as follows:

• Green - Load Balancer
• Blue - Application Server
• Orange - Databases and Cache Nodes
• Gray - All other stacks

2. Next you can see the estimated cost of your environment. The widget will display the price in the same color as above and you can change the time period. Be it hourly, daily or monthly.

TabFROMShows the amount that will be charged as the reserved resource is covered. Tab sectionTOIt shows the maximum possible price if all nodes in the environment are going to use all their resources up to their scaling limit in the entire duration.

Tips:Hover over the price to see more details on calculating the estimated cost.



You can click the link under the widget to learn more about how Ruk-Com Cloud PaaS prices and charges are calculated.

3. Finally, specify a name for your environment and click the button.Createto continue

And here are all the steps: After pressing create and waiting a few seconds, your new environment will appear on the dashboard.

You are now ready to deploy the application and continue using your cloud environment.