Knowledge base
How to create containers and how to manage them?
Posted by on 05.09.2012 09:56

In the Containers tab you can functionally group instances supporting e.g. the same application. With this service, you can enable load balancing (spreading movement) in many instances placed in a container.

A container also includes an autoscaler function that when you turn on will ensure that the container always has a sufficient number of instances to handle the traffic on your site. You can also plan a calendar of activities of the container in such a way that at certain times the configuration of an instance and its class will be changed.

 

 

To create and manage containers select the Containers tab in the subpage Services.

 

 

You will see a list of already created containers with information about the number of virtual machines they include and existing schedulers.

To add a new container, click the Add Container button above the list.

Of course, the removal of container does not remove the constituent instances, and only eliminates the connection between them.

 

 

Now you have to name the new container and select the instances that it includes. You can do this by simply dragging the selected instances into the labelled box. Right away you can also choose to activate Load balancer. You will find out more about these functions, in the following sections.

Shortly after creating a new container, it should appear in the list.

 

 

When you click the container‘s name in the list, its panel will be displayed with a list of instances it includes. You may perform identical operations to the ones in the OCI tab, which include e.g. editing the configuration, turning on and off, and creating snapshots.

 

 

To change the configuration of the container established at its creation, click the Edit link under his name.

 

 

The panel looks almost the same as when you created a container. You can change the name, add or delete OCI instances, and change the settings of Load balancer.

 

 

Load balancer is used for the optimal spreading of the load between the instances, to ensure maximum efficiency of services and applications. After enabling the function you will see additional fields with detailed settings. First you choose which service is to be covered by the Load Balancer (including HTTP, HTTPS, SMTP and Port) and specify whether to enable SSL.

You then choose one of the three algorithms:

  • Least connection - directs traffic to the instance with the least number of connections,
  • Least response time - directs traffic to the instance with the shortest response time,
  • Source IP Hash - directs traffic from an IP address permanently to the same instance.

Next you choose how to handle the session:

  • the source IP persistence,
  • persistence in cookies,
  • Lack of persistence.

Finally, you specify the protocol version - IPv4 or IPv6 and decide whether to perform Availability of services check.

 

 

Description of the autoscaling and schedulers is available in “What is an autoscaler and what are the consequences of its enabling (also in the context of a container)?”

(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.