airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jerrin Suresh <jerrinsur...@gmail.com>
Subject Re: Working on Load Balancers
Date Wed, 18 Oct 2017 19:00:59 GMT
Yup, that works too Ameya! In fact, I added the advertise address to
consul and it seems to be working, but there are some issues here and there
which I am trying to troubleshoot.

~Jerrin




On Wed, Oct 18, 2017 at 2:46 PM, Ameya Advankar <aadvanka@umail.iu.edu>
wrote:

>
> Hi Jerrin,
>
> As I suggested on Friday, the command *curl
> http://169.254.169.254/latest/meta-data/public-ipv4
> <http://169.254.169.254/latest/meta-data/public-ipv4> *will give u the
> public IP on the instance.
> This can be used in your consul / ha-proxy startup scripts.
>
> Regards,
>
> Ameya Advankar
>
> aadvanka@indiana.edu
> [image: indiana-university-logo]
>
> On Wed, Oct 18, 2017 at 2:26 PM, Jerrin Suresh <jerrinsuresh@gmail.com>
> wrote:
>
>> Marcus,
>>
>> Yes, that is correct! I don't think we need the public IP. But, then if
>> the portal servers are spread across multiple datacenters, I am not pretty
>> sure if private IP alone would help in that case.
>>
>> I am still looking into this.
>>
>>
>> ~Jerrin
>>
>> On Mon, Oct 16, 2017 at 9:33 AM, Christie, Marcus Aaron <machrist@iu.edu>
>> wrote:
>>
>>> Jerrin,
>>>
>>> I’m not sure I completely understand, but if you are on openstack
>>> couldn’t the load balancer connect over the internal network to the web
>>> server instances and only the load balancer needs to connect out over the
>>> public ip address?  In other words, the load balancer accepts traffic on
>>> the public ip address and forwards it to the web server instances on
>>> private ip addresses.
>>>
>>> On Oct 9, 2017, at 10:05 PM, Jerrin Suresh <jerrinsuresh@gmail.com>
>>> wrote:
>>>
>>> However, now I am facing an issue with binding the ports in consul and
>>> ha-proxy. Within the openstack, there is no provision to access the public
>>> ip of an instance. Hence, ha-proxy, consul-template and consul are
>>> accessing the private IP of the portal server.
>>>
>>> I haven't moved the setup to production. This was the case when I tried
>>> implementing the dummy concept on TACC openstack. So, is there a way in
>>> which I can access the floating IP of instances within an instance?
>>>
>>>
>>>
>>
>>
>> --
>> MS CS Fall-2018
>> Indiana University
>> www.linkedin.com/in/jerrinsuresh
>>
>>
>


-- 
MS CS Fall-2018
Indiana University
www.linkedin.com/in/jerrinsuresh

Mime
View raw message