Skip to main content

Chapter VI Deka Flexi : Network

This menu is used to create VPC Network, assign floating IP, and create load balancer.

List of Content

Content

6.1 VPC Network

VPC (Virtual Private Cloud) Network is an architecture virtual version of physical network that implemented in Cloudeka cloud environment. A VPC Network ensures secure traffic between any resource like Instance, Kubernetes clusters, database clusters, and load balancers. Any resource you create within a VPC can communicate securely over their private IP Address.

6.1.1 Create VPC Network

This menu explains how to create a VPC Network. VPC Network is also the basis for creating a Virtual Machine, you must create a VPC Network before creating a Virtual Machine.

  • Go to Network page


Image 6.1 Network Page



  • Click Create VPC button.


Image 6.2 Network Page - Create VPC



  • Fill in the form Create VPC Network.

Table 6.1 Create VPC Network Form


Column Description
Name Name of VPC Network
Description Description of VPC Network
Region To determine the location of the data center at the TKP Data Center (Taman Tekno Park)
Billing Type - Fixed
- Trial
IP Address Enter Private IP Address also the subnetmask, The Internet Assigned Number Authority (IANA) has assigned several address ranges to be used by private networks. Address ranges to be use by private network are:

- Class A: 10.0.0.0 to 10.255.255.255
- Class B: 172.16.0.0 to 172.31.255.255
- Class C: 192.168.0.0 to 192.168.255.255

An IP address within these ranges is therefore considered non-routable, as it is not unique. Any private network that needs to use IP addresses internally can use any address within these ranges without any coordination with IANA or an Internet registry. Addresses within this private address space are only unique within a given private network.

  • Then, click Create VPC Network


Image 6.3 Create VPC Network Form




Image 6.4 Form Create VPC Network



  • There will be a notification if the VPC Network is successfully created “VPC network has been successfully created”


Image 6.5 Notification



6.1.2 Edit VPC Network

You can only edit VPC Network for the Name and Description only, you cannot change the IP Address Configuration.

  • On the Network page, click the Edit button.


Image 6.6 Network Page - Edit



  • You can only change the Name and Description. For Region, Billing Type, and IP Configuration can not be changed. Then, click Save button.


Image 6.7 Edit VPC Network Form




Image 6.8 Edit VPC Network Form



  • There will be a notification if the VPC Network is successfully created “VPC network has been successfully updated”


Image 6.9 Notification



6.1.3 Delete VPC Network

Before you delete a VPC Network, you need to make sure there are no other instances or services connected to the VPC Network.

  • On the Network page, click the Delete button.


Image 6.10 Network Page - Delete



  • Click the Confirm button to start the process of deleting VPC Network data or Cancel if you don’t want to continue the process.


Image 6.11 Confirm Delete VPC



  • There will be a notification if the VPC Network is successfully deleted “VPC network has been successfully deleted”.


Image 6.12 Notification



6.2 Floating IP

Floating IP is a public, static IP Address for instances that provide access from an external network to the instance without public network interface.

6.2.1 Assign Floating IP

If your instance require external IP address for external access, you can assign Floating IP by following these steps:

  • On the Network page select the Floating IP tab.


Image 6.13 Network Page - Floating IP



  • In Floating IP Type, there are two Floating IP Types, namely Reserved and Non Reserved. In the Non-Reserved type when you Reassign Instance then the IP used will be deleted from the list in the Floating IP, while in the Reserved type if you Reassign Instance then the IP used will remain on the list in Floating IP so you can use the IP for other instances of your project.


Image 6.14 Network Page - Floating IP - Floating IP Type



  • On the Billing Type, there are two types of Billing Type, i.e Fixed and Trial.


Image 6.15 Network Page - Floating IP - Billing Type



  • On the Resource Type, there are two types of Resource Type, i.e Instance and Load Balancer.


Image 6.16 Network Page - Floating IP - Resource Type



  • If you choose Instance on Resource Type, then select the instance that you want to assign Floating IP. After that, click Assign Floating IP.


Image 6.17 Network Page - Floating IP - Resource




Image 6.18 Network Page - Assign Floating IP



  • If the Floating IP is succesfully assigned, the Floating IP will be display in Floating IP list


Image 6.19 Network Page - Floating IP List



6.2.2 Unassign Floating IP

If you want to unassign or remove Floating IP of your instance, please follow these steps. Note: if you unassign Floating IP from your instance, so your instance doesn’t have external access anymore. However, you can reassign the Floating IP whenever you want.

  • If you are already on the Network page and on the Floating IP tab, select the Floating IP in Action column that you want to unassign from your instance. Click More, then select Unassign.


Image 6.20 Action - Unassign Floating IP



  • If the Floating IP has been successfully unassigned, a pop up will appear “Floating IP has been successfully unassigned!”


Image 6.21 Unassigned Successfully



6.2.3 Delete Floating IP

Before you delete floating IP, you need to unassign the Floating IP first. You cannot delete it if the Floating IP still in use.

  • In the Action column, choose Floating IP that you want to delete. click More, then select Delete.


Image 6.22 Floating IP - Action - Delete



  • Click the Confirm button to start the process of deleting data Floating IP or Cancel if you don’t want to continue the process.


Image 6.23 Delete Confirmation



  • If the Floating IP has been successfully deleted, a pop up will appear “Floating IP has been successfully deleted”


Image 6.24 Notification



6.3 Cloudeka Load Balancer

Cloudeka Load Balancer distributes network traffic to across multiple instance to improve service capability and application availability. Cloudeka Load Balancer provides several features, including:

  • Multiple protokol Cloudeka load balancer supports multiple protocols to meet your needs. Currently, several protocols are available:
    • TCP
    • HTTP
  • Health Check, to periodically check the state of the backend instance. This will automatically stop sending traffic to the non-responsive instances.


In load balance, there are 3 algorithm methods used, including the following:

Table 6.2 Load Balancer Method


Column Description
Roundbin It is a load method that is given sequentially from one server to another so that it forms a round.
Least Connection Is a load method that is given based on the server that has the fewest connections in the lists of servers available.
Source Is a method of selecting the server to use based on the hash of the source IP address where the user made the request, so in this method ensures that the same user will connect to the same server.


Before creating a Load Balancer, you must first have an Instance. If you don’t have an Instance yet, you can deploy an Instance in Create VM Instance

6.3.1 Create Load Balancer

  • On the Cloudeka portal, open the Network menu and select Load Balancer.


Image 6.25 Network - Load Balancer



  • Click Create Load Balancer


Image 6.26 Create Load Balancer



  • Fill in the Name, Flavor, VPC Network, dan centang High Avaibility, then click Create Load Balancer.


Image 6.27 Form Create Load Balancer



Table 6.3 Create Load Balancer Form


Column Description
Name The name of your load balancer.
Flavor Flavor for your instance size.
VPC Network The VPC network must be on the same segment as the instances to be load balanced.
High Avaibility If you check High Availability then the service will create 2 instances so that if one instance dies, there will still be another instance that will run the load balancer.

  • The Creating the Load Balancer notification will appear and the Column Status will show ON-PROGRESS.


Image 6.28 Form Create Load Balancer



  • If the load balancer is created successfully, a notification will appear Load balancer [name of load balancer] has successfully created.


6.29 Notification - Load Balancer has successfully created



  • Load Balancer is active and ready to use. The table that will appear on the Load Balancer page is:


Image 6.30 Halaman Load Balancer



Tabel 6.4 Create Load Balancer Form


Columns Description
Name The name of the Load Balancer created.
Floating IP The public static IP address your instance is using.
Flavor The type of instance size used.
High Availability The description column uses High Availability Yes or No.
Status Load Balancer status, CREATED status means the Load Balancer is ready for use, while ON-PROGRESS status means the Load Balancer is being prepared by the system so it cannot be used yet.
Action Option to edit or delete Load Balancer.

  • After the Load Balancer has been created, note the IP address used by the Load Balancer.


Image 6.31 Halaman Load Balancer



6.3.2 HTTP Configuration in Load Balancer

For HTTP configuration on Load Balancer you have to configure backend and frontend. Follow the explanation for the configuration.

6.3.2.1 Configuration Backend

After you have successfully created a Load Balancer, then you need to configure the Backend on the Load Balancer that you have created. Follow these steps:

  • On the Network page, click the Load Balancer tab. Click the Configuration button in the Column Action.


Image 6.32 Halaman Load Balancer



  • On the Load Balancer Configuration page, click the Backend tab, then click Create Backend.


Image 6.33 Load Balancer - Create Backend HTTP



  • The Create Backend page appears, fill in the form provided.


Image 6.34 Load Balancer - Form Create Backend (a)



Table 6.5 Create Backend Form


Columns Description
Name Backend configuration name and for backend naming characters can only use A-Z,a-z, and _ underscore.
Load Balancer In this Column there are 3 options including Roundrobin, Least Connection, and Source. This section select Roundrobin.
Mod There are 2 modes including the following:
a.HTTP
b.TCP
Because this section is the backend configuration for HTTP so select HTTP.
Advanced Check Because in Column Mode, you select HTTP, then click httpchk. Httpchk is HTTP Check.
HTTP Check Method There are 2 options:
a.GET, used to request data to retrieve data.
b.POST, used to request to create new data.
Http Check URI This column is used to determine whether the server status is active or inactive. In this section type /_health.php

  • In Column Servers, fill in the available Columns. Click the Add Servers button, if you want to add server data that will be used.


Image 6.35 Load Balancer - Create Backend Form - Servers Form



Tabel 6.6 Form Servers


Columns Description
Server Name Select a previously created VPC.
Server Port Port that will be used by the server.
Max Connection Maximum number of accepted connections.
Weight The load that will be received by the server.

  • After filling out all the forms on the Create Backend page, click the Create Backend button.


Image 6.36 Load Balancer - Create Backend Form



  • A notification appears Backend Configuration has successfully created!.


Image 6.37 Halaman Load Balancer



6.3.2.2 Edit Configuration Backend HTTP

If you want to change the backend configuration that you have created, then follow these steps:

  • On the Configuration Load Balancer page, click the Backend tab. On the backend_one in the Backend Name column, click the Edit button.


Image 6.38 Load Balancer - Edit Configuration Backend HTTP



  • The Edit Backend page appears, which can be changed only Column Load Balance Method, Advanced Check, Http Check Method, Http Check URI, and you can add Servers by clicking Add Servers. Then click Update Backend.


Image 6.39 Load Balancer - Edit Configuration Backend HTTP (a)




Image 6.40 Load Balancer - Edit Configuration Backend HTTP (b)



  • A notification appears Backend Configuration has successfully updated!.


Image 6.41 Load Balancer - Edit Configuration Backend HTTP success



6.3.2.3 Configuration Frontend HTTP

After you have configured the Backend for HTTP mode, the next step is to configure the HTTP Load Balancer frontend. Follow these steps:

  • On the Configuration Load Balancer page, click the Frontend tab, then click Create Frontend.


Image 6.42 Load Balancer - Create Frontend HTTP



  • The Create Frontend page appears, fill in the form provided.


Image 6.43 Load Balancer - Form Create Frontend (a)




Image 6.44 Load Balancer - Form Create Frontend (b)



Table 6.7 Create Frontend Form


Columns Description
Name Backend configuration name and for backend naming characters can only use A-Z,a-z, and _ underscore.
Default Backend Choose a backend that was previously created.
Bind Address There are 2 options including the following:
a.Internal uses the IP address that has been registered on the Cloudeka Portal Service.
b.Internet uses an IP address so that it can be accessed from outside networks.
Bind Port Because we use HTTP so the port used is port 80.
Mode There are 2 options including HTTP and TCP.
Because in this section is the backend configuration for HTTP so choose HTTP.

  • If you want to add a Backend, in the Additional Backend section you can click the Add Backend button. Then fill in Backend Name, ACL Name, Criteria, Value and Condition.


Image 6.45 Load Balancer - Create Frontend Form (c)



  • After filling out all the forms on the Create Backend page, click the Create Backend button.


Image 6.46 Load Balancer - Form Create Frontend (d)



  • A notification appears Frontend Configuration has successfully created! that Frontend Configuration Load Balancer has been added.


Image 6.47 Halaman Load Balancer



6.3.2.4 Edit Configuration Frontend HTTP

If you want to change the Frontend configuration that you have made, then follow these steps:

  • On the Load Balancer Configuration page, click the Frontend tab. On frontend_one in the Backend Name column, click the Edit button.


Image 6.48 Load Balancer - Edit Configuration



  • The Edit Frontend page appears, which can be changed only Column Default Backend, Additional Backend if you want to add another Backend by clicking the Add Backend, Bind Address, and Bind Port buttons. Then click Update Frontend.


Image 6.49 Load Balancer - Edit Configuration Frontend TCP (a)




Image 6.50 Load Balancer - Edit Configuration Frontend TCP (b)



  • Appears notification Frontend Configuration has successfully updated!.


Image 6.51 Load Balancer - Edit Configuration Frontend TCP Success



6.3.3 Configuration TCP in Load Balancer

For TCP configuration on Load Balancer you have to configure backend and frontend. Follow the explanation for the configuration.

6.3.3.1 Configuration Backend TCP

After you have successfully created a Load Balancer and have configured HTTP, then you need to configure Backend and Frontend for TCP on the Load Balancer that you have created. Follow these steps:

  • On the Network page, click the Load Balancer tab. Click the Configuration button in the Action Column.


Image 6.52 Halaman Load Balancer



  • On the Load Balancer Configuration page, click the Backend tab, then click Create Backend.


Image 6.53 Load Balancer - Create Backend



  • On the Create Backend page, fill in the form provided. After completing the form, click the Create Backend button.


Image 6.54 Load Balancer - Form Create Backend TCP (a)




Image 6.55 Load Balancer - Form Create Backend TCP (b)



Table 6.8 Create Backend Form


Columns Description
Name Backend configuration name and for backend naming characters can only use A-Z,a-z, and _ underscore.
Load Balance Method In this Column there are 3 options including Roundrobin, Least Connection, and Source. This section select Roundrobin.
Mod There are 2 modes including HTTP and TCP. Because in this section is the backend configuration for TCP so select TCP.
Advanced Check There are 2 options including the following:
a. SSL HelloCheck
b. TCPCheck.
In this section select SSL Hello Check.
Servers Click the Add Servers button if you need more than 1 server. You only need to fill in Server Name, Server Port, Max Connection, and Weight.

  • Notification appears Backend Configuration has successfully created!


Image 6.56 Load Balancer - Create Backend Success



6.3.3.2 Edit Configuration Backend TCP

If you want to change the backend configuration that you have created, then follow these steps:

  • On the Configuration Load Balancer page, click the Backend tab. On the backend_tcp in the Backend Name Column, click the Edit button.


Image 6.57 Load Balancer - Edit Configuration



  • The Edit Backend page appears, which can be changed only Column Load Balance Method, Advanced Check and you can add Servers by clicking Add Servers. Then click Update Backend.


Image 6.58 Load Balancer - Edit Configuration Backend TCP (a)




Image 6.59 Load Balancer - Edit Configuration Backend TCP (b)



  • Notification appears Backend Configuration has successfully updates!


Image 6.60 Load Balancer - Edit Configuration Backend Success



6.3.3.3 Configuration Frontend TCP

  • After you have configured the Backend, the next step is to click the Frontend tab, then click the Create Frontend button.


Image 6.61 Load Balancer - Create Frontend



  • On the Create Backend page, fill in the available form. After completing the form, click the Create Frontend button.


Image 6.62 Load Balancer - Create Frontend TCP (a)




Image 6.63 Load Balancer - Create Frontend TCP (b)



Table 6.9 Form Create Frontend


Column Description
Name Backend configuration name and for backend naming characters can only use A-Z,a-z, and _ underscore.
Default Backend Select the TCP Backend that was previously created.
Addtional Backend You can add additional Backends by clicking Add Backend and filling in the Backend Name, ACL Name, Criteria, Value, and Conditions.
Bind Address There are 2 options Internal and Internet, select Internet.
Bind Port In this section Fill the port with port 80.
Mode Select TCP.

  • Notification appears Frontend Configuration has successfully created!


Image 6.64 Halaman Load Balancer



6.3.3.4 Edit Configuration Frontend TCP

If you want to change the Frontend configuration that you have made, then follow these steps:

  • On the Load Balancer Configuration page, click the Frontend tab. On the frontend_tcp in the Backend Name Column, click the Edit button.


Image 6.65 Load Balancer - Edit Configuration



-The Edit Frontend page appears, which can be changed only Column Default Backend, Additional Backend if you want to add another Backend by clicking the Add Backend, Bind Address, and Bind Port buttons. Then click Update Frontend.


Image 6.66 Load Balancer - Edit Configuration Frontend TCP (a)




Image 6.67 Load Balancer - Edit Configuration Frontend TCP (b)



  • A notification appears Frontend Configuration has successfully updated!


Image 6.68 Load Balancer - Edit Configuration Frontend TCP Success



6.3.4 Delete Load Balancer

If you want to delete a load balancer, follow the instruction bellow:

  • On the Load Balancer page, choose the load balancer that you want to delete, in Action column, then click Delete.


Image 6.69 Load Balancer Page



  • Select Confirm button to continue process.


Image 6.70 Delete Confirmation



  • There will be a pop up notification “Load balancer has been successfully deleted”.


Image 6.71 Notification



×