[ensembl-dev] Are the IP address(es) for useastdb.ensembl.org fixed/static?

[Steve Trevanion]

Hi Kevin,

ensembldb.ensembl.org is hosted at EMBL-EBI and the IP is stable.

So you need to use port 5306 for all applications.  I guess you could 
set it as an environment variable and then use that in your scripts 
(http://www.ensembl.org/info/docs/api/registry.html) but that's not very 
elegant. Can anyone from Ensembl @core or @variation comment ?

Cheers,

Steve



On 08/02/2018 03:48, Ernst, Kevin wrote:
> Hi Steve, thanks for your reply. I'll share that information with our 
> research IT people and see what they say.
>
> What about ensembldb.ensembl.org (ensembldb.ebi.ac.uk)? That does not 
> appear to be hosted with AWS. Is that IP (or that of the load 
> balancer, if there is one) likely to change on a whim, or have they 
> been fairly stable? Perhaps that's our only option.
>
> I have an additional question about the MySQL port number as well. I 
> was unable to convince our organizational network security team to 
> make exceptions for the "standard" port 3306 (which is, sadly, 
> opposite the motivation described in this Ensembl blog post 
> <http://www.ensembl.info/2013/05/02/database-port-changes/>).
>
> So... will Ensembl tools like VEP generally try one port and then the 
> other, or is there a way we could globally configure anything using 
> the Perl API to prefer the non-standard port number—for all users of 
> our cluster? Perhaps with a Makefile.PL flag, or an environment variable?
>
> (I see that creating an /etc/skel/.vep/vep.ini for new users is one 
> potential option for VEP, for example, but there are hundreds of 
> existing users, so setting an environment variable in our Environment 
> Modules modulefile for VEP would work much better.)
>
> Thanks very much.
>
> Cheers,
> Kevin Ernst
>
>
> On 07.02.18 19:07, Steve Trevanion wrote:
>> Can you speak again with your IT colleagues ? I am not a specialist 
>> in this area so I will talk next week with members of the EMBL-EBI 
>> network team to see if they can suggest any ways around this.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20180208/2fa9cb48/attachment.html>