0% found this document useful (0 votes)
33 views6 pages

FINAL Round Robin 3

This document describes a proposed round robin load balancer for hosting a service on a 3-node Docker swarm cluster in the cloud. The system uses Docker swarm technology to create a private network between nodes to allow communication. It will handle executing multiple processes concurrently using Docker containers. One container will act as a load balancer to distribute requests across the nodes based on available resources like CPU cores. The system aims to efficiently balance loads and prevent bottlenecks while hosting services elastically in the cloud.

Uploaded by

Aaradhya Shukla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views6 pages

FINAL Round Robin 3

This document describes a proposed round robin load balancer for hosting a service on a 3-node Docker swarm cluster in the cloud. The system uses Docker swarm technology to create a private network between nodes to allow communication. It will handle executing multiple processes concurrently using Docker containers. One container will act as a load balancer to distribute requests across the nodes based on available resources like CPU cores. The system aims to efficiently balance loads and prevent bottlenecks while hosting services elastically in the cloud.

Uploaded by

Aaradhya Shukla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

ROUND ROBIN LOAD BALANCER FOR

THE THREE NODE SWARM CLUSTER FOR


HOSTING A SERVICE ON THE CLOUD
Aaradhya Shukla Ayush Singh Chauhan Dr.J.Kalaivani
Dept of computer science and engineering Dept of computer science and engineering Dept of Computer Science

SRM IST, INDIA,603203 SRM IST, INDIA,603203 SRM IST, INDIA,603203


[email protected] [email protected] kalaivaj.srmist.edu.in

I. ABSTRACT accomplish vitality effectiveness. Facilitate for the


client the appropriation of the compartment's
In this project we will be creating an application which
innovation to build up a commercial Centre. With
uses socket programming for communication and all of
the data/metadata are saved in mongo DB. We will be regards to ongoing venture, we propose, in this paper,
taking this application and hosting it on a 3 node swarm our underlying thoughts for another booking
cluster. methodology executed in Docker Swarm, the
principle innovation utilized in the venture.
This cluster will be using Docker swarm technology to
create a private network through which each of the nodes This paper is for the most part committed to usage
can talk to each other along a specified RPC port. subtleties and general thoughts. More work has been
So, based on this concept we will be making a Docker
done for the current year to broaden this work, see for
container which will handle the execution of multiple example and a general union of our system is at
processes which lead to working of different projects present under looking into. The Discussion area will
concurrently. clarify, last on, some situating actualities of this work
contrasted with progressing works.
Docker is a PC program that performs working
framework level virtualization otherwise called Docker Swarm is a bunching and booking apparatus
containerization. for Docker holders. It chooses the principal demand
II. INTODUCTION that must be executed by utilizing the traditional
FIFO system. At that point, Docker Swarm picks the
These days, distributed computing is becoming the suitable machine for example fulfilling the need of
business membership to outer administrations in in so the client as far as CPU centers, by utilizing one
many sectors. Its guideline depends on the procedure among the accompanying methodologies:
compensation for-use display that can influence
diverse components, for example, the mentioned Our proposed financial model relies upon three SLA
application, information stockpiling limit, memory classes to answer to the customers' needs. The
handling and number of clients. The fundamental showing with three classes is motivated by the
targets of this task are to manage and to setup: mechanical endeavors and relies upon the
discernment that encouraging courses of action don't
Receipt, in light of asset utilization so as to allow makers or cloud providers to offer to their
accomplish the business effectiveness of the customers a sensible or exact receipt, for instance a
organization; precise receipt with reverence to the use of benefits
by the referenced organization. Seen that the errand
Avoid wastage of asset utilization and devour as it
were what is vital and productive to applications to
must respond to the going with use cases concerning
the sent organizations, every organization addresses
one SLA class Long administration it is a determined
administration encountering pinnacles of burden
(CPU, smash, plate, organize) like times of
dormancy.

III. RELATED WORK

Previously similar kind of work has been done. This Figure 1:Basic Swarm
container flow
includes hosting services on the cloud. The basic
each over a system (administration arranged
cloud architecture in the older days used to use the
engineering)) can be associated with one another
Round Robin Load Balancer, which is nothing but an
Proposed improved planning calculation which
algorithm that is used to manage the client server
depended on standard Max-Min calculation for
request.
burden balance in the flexible cloud. In this work
So all of the previous work using this Round Robin they kept up an assignment status table to store the
techniques were not so fast and were neither that assessed continuous heap of VMs proposed in this
efficient on providing the proper results. paper and rough fulfilment time of
undertakingsrequires timely re-service like laundry
Later On Click Load Balancer was introduced in the service.
cloud system .This system is really effective and it
helps in reaching parallel computing and IV.PROPOSED METHODOLOGY
simultaneous request handling .The bad aspect to this
A. A backend network model of the proposed
technology is that it is very costly method to
implement.

So in order to facilitate this method and make it more


refine and less expensive to the the majority of
people we decided to use the Docker Swarm
technology .]. Docker is stage for structure,
dispatching and running applications. It doesn't
contain the entire working framework, however
simply the important parallels and libraries. It
fundamentally encapsulates a run time condition. It is
kept running on client space over the OS. There is no
understanding of hypervisor. Namespaces encourage
the compartment to have its very own system, IP and system
so forth. Control bunches deal with the utilization of
memory and CPU. It is a stage for creating, network architecture
delivering and running applications. It is somewhat
similar to the virtual machine. However, the entire Creation of an application which will be hosted on
OS isn't made. Docker utilizes the host machine's the cloud.We will be using Docker swarm and
piece. It is lightweight and decreases the size. The Routing mesh Technology to create a private network
host machine is of no worry. Pictures can be pulled all of this together will act as a load balancer. We
from the stores or can be made by clients (for will be using 4 containers and in which two of them
example by utilizing Dockerfiles). Dockerfiles can be will act as a swarm container which in turn can create
utilized to assemble pictures. Docker libraries are and delete requests.
used to store the pictures. Docker compartments get
Proposed framework will give you the opportunity to
made when pictures are run. Information volumes
pick the information of any subject.Here, it gives you
can likewise be shared between compartments. The
compartments/microservices (benefits that speak with
the effect the outcomes and measurements will have module is working properly because if it isn’t it could
on the separate field.Proposed system. create large security breaches which will make it
difficult for the system administrator to manage the
virtual network.
B. Cloud connectivity and computing: F. Load Balancer:
All the requests of clients will be in cloud and all the Its job will be to avoid deadlock after the resources
database used for storing the other meta data are have been allocated. It will help decrease the
stored and computed in MongoDb The Cloud service starvation through context switching which will help
is encapsulated with layers of security protecting it in the prevention of deadlock as it will not allow a
from potential attack. The personal details are private virtual node-n to access the Critical section for a long
and order details are only shown to the client it is period of time.
assigned to. All the data is resided in distributed
servers and retrieved only when queried.

V. RESULT ANALYSIS

We used Digital Ocean a Cloud Service hosting


platform for creating linux virtual servers .These
servers are referred to as droplets.We used for
Droplets among which one was made as the swarm
manager .With the help of visual studio we loaded
the Docker Script into each of the nodes thereby
making 3 nodes as workers and 1 as the manager.All
of these containers communicated together using
routing mesh technique frequently establishing RPC
Figure 2: application's cloud ports for inner and outer communication.Using this
architecture we played our voting application over it. The security
was through the linux ‘ssh’ command.The resultant
C. VM Engine:
was a full proof and secured voting system.
Its job is to maintain a sub-level between the
system/server, so as to provide seamless dataflow in
the given model. It maintains all the virtual nodes and
keeps them at a separate level-1. It provides the start
for the virtual machine and also maintains the cloud
architecture in-order ton ensure security protocols
between server and n-node user.

D. Resource Allocator:

with This part manages resource allocation in the


system, as many virtual servers try to access the Figure 3:overall system architecture
system it will create different allocation times based
on priority. It is a very important component of the VI. CONCLUSION:
model as it will help manage the resources that might
Using technologies like Docker and Docker swarm
try to enter the critical section at once.
we were able to deploy a standard voting application
E. System Manager: to a 3 node swarm cluster where each node can be
either a swarm manager or a swarm worker and
It will overlook the complete model. It can be communicating among each other via an open RPC
considered as the master component of the model port. Thus we created a load balancer for our chat
because everything has to pass through the system application. The implementation part included two
manger. It will keep in check if each and every sets of our project backend and frontend.
VII. REFERENCES: (5) S. S. Hegde and D. P. Jayarekha,
"Basic Analysis of Docker
(1) G. Rastogi and D. R. Sushil, "Analytical
Literature Survey on Existing Load Networking," International Journal
Balancing Schemes in Cloud of Advanced Research in Computer
Computing," International Conference Science, vol. 8, no. 5, pp. 740-743,
on Green Computing and Internet of 2017.
Things, 2015 (6) P. J. Dilip and P. K. Nangana, "Docker,
(2) B. B. Rad, H. J. Bhatti and M. Ahmadi, An Optimized Virtualization Using
"An Introduction to Docker and Analysis Container," International Journal for
of its Performance," International Research in Applied Science &
Journal of Computer Science and Engineering Technology.
Network Security, vol. 17, no. 3, pp. 228- (7) P. Dziurzanski and L. S. Indrusiak,
235, 2017. Value-Based Allocation of Docker
(3) C. Cerin, "A New Docker Swarm Containers.
Scheduling Strategy," Universite de
Paris.
(4) K. S. Akshay, K. J. Anish, K. Amit, K.
(8) The Docker Book | John Martin and
T. Vivek and H. Praveen, "RESOURCE
Jmaes Turbull ,2016 publications
MONITORING OF DOCKER
CONTAINERS," International Journal
of Advance Engineering and Research
Development.

VII. AUTHORS PROFILE:


Dr.J.Kalaivani (Jeyaraj Kalaivani)
Aaradhya Shukla is presently doing is Computer obtained her Bachelor’s Degree in
Science and Engineering from SRM IST Chennai. ComputerScience and Engineering,
His Hometown is in Lucknow and he did his National Engineering College, Anna
Class 10th and 12th from ST.Francis College, University, Tamil Nadu, India in2005.
Lucknow,Uttar Pradesh. Aaradhya shukla has Master’s Degree in Computer Science
earlier worked as an intern in E,soft.Connect and Engineering, Mepco Schlenk
EngineeringCollege, Anna University,
He has previously worked on Android Projects. Tamil Nadu, India in 2008. Ph.D. in the
Aaradhya Shukla always had a great interest in Department of InformationTechnology,
Cloud Computing .This is the first time that he has Madras Institute of Technology, Anna
Worked on a research paper. University, Chennai, Tamil Nadu, India
Aaradhya Shukla will be joining TCS, as a Software in2017. She is working as
Engineer in July . Assistant Professor in the
Aaradhya Shukla has worked on several other projects Department of Computer Science
That were based on android application development . andEngineering, SRM Institute of
Science and Technology,
Kattankulathur, Kanchipuram
Second Author of this paper is Ayush Singh Chauhan. District,Tamil Nadu, India. Her research
Ayush Singh Chauhan is presently doing Computer interest is Computer Networks
Science and Engineering from SRM IST Chennai.
Ayush Singh Chauhan hails from Lucknow
And he has done his class 10th and 12th from CMS
Aliganj Lucknow. Ayush Singh Chauhan has
Done couple of internships based on web dev-
-velopment .Ayush always had a keen interest
In Networking and Big Data.
He is applying for Foreign Universities for
His masters in Big Data .Ayush and Aaradhya started working on this pro-
-ject when they were in third year.
Ayush has previously worked on several Cloud projects.

You might also like