Hi Jerrin, Avoiding a single point of failure for the load balancer is tricky. But typically, a good approach is to have multiple load balancers (for HA) and a floating IP which maps to an “active” load balancer – this is assuming we have an Active-Passive type HA cluster for the load balancer. Container orchestration engines such as Kubernetes/DCOS provide such features out-of-the-box; same goes with public clouds such as AWS or GCE. Privately managed cloud like OpenStack will need some complex configuring to enable such DNS mapping.
Hope this helps! Thanks and Regards, Gourav Shenoy From: Jerrin Suresh <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, October 3, 2017 at 3:31 PM To: "[email protected]" <[email protected]> Subject: Re: Working on Load Balancers The main idea of implementing a load balancer is to balance the load to the portal and remove any single point of failure. However, after implementing the load balancer, the load balancer itself becomes a single point of failure. Any thoughts regarding the same? Should we have multiple load balancers involved, i.e a master and a slave or a dual master setup? On Mon, Oct 2, 2017 at 10:51 AM, Christie, Marcus Aaron <[email protected]<mailto:[email protected]>> wrote: No plans. But if it makes sense to do so we could. On Oct 2, 2017, at 10:03 AM, Jerrin Suresh <[email protected]<mailto:[email protected]>> wrote: Just a quick question, do you have plans of dockerizing the Django portal? ~jerrin On Fri, Sep 29, 2017 at 10:58 PM, Jerrin Suresh <[email protected]<mailto:[email protected]>> wrote: Hi Marcus, Thanks for the update. I shall set the load balancer up for a sample application, and am planning to use haproxy for the project. Regards, Jerrin On Fri, Sep 29, 2017 at 9:11 AM, Christie, Marcus Aaron <[email protected]<mailto:[email protected]>> wrote: Jerrin, What specifically do you want to work on regarding load balancing? Depending on what you want to work on, load balancing a web application is fairly independent of the web application framework. So I would say for now you could just try load balancing any web application, even a simple little one written in either Laravel or Django (or another framework). We run the PHP PGA and Django PGA in Apache HTTPD server. So it would be good if the load balancing work you do works with Apache HTTPD. However, I’m open to using something else like nginx or whatever if you can make a good case for it. Thanks, Marcus On Sep 28, 2017, at 11:25 AM, Jerrin Suresh <[email protected]<mailto:[email protected]>> wrote: Hi, I am working on setting up Load Balancers for Apache Airavata. However, as the PGA is being moved to the Django framework is it better to work on the PGA branch or should I work on the Django branch? ~jerrin -- MS CS Fall-2018 Indiana University www.linkedin.com/in/<http://www.linkedin.com/in/>jerrinsuresh -- MS CS Fall-2018 Indiana University www.linkedin.com/in/<http://www.linkedin.com/in/>jerrinsuresh -- MS CS Fall-2018 Indiana University www.linkedin.com/in/<http://www.linkedin.com/in/>jerrinsuresh -- MS CS Fall-2018 Indiana University www.linkedin.com/in/<http://www.linkedin.com/in/>jerrinsuresh
