I believe you're the first person that's tried to run this in a completely
private VPC so I don't have experience with it but can suggest a change
that might get over this initial hump at least.
My guess is that get_galaxy_dns method is why you're seeing this log
so perhaps changing that method to return an address you've configured as
an accessible one would fix it? After changing the code, it'll also be
necessary to update CloudMan source code in the corresponding bucket; see
this page for more on that topic:
Hope this helps. Let us know how things progress and we can update the code
if a solution is generic.
On Fri, Jan 29, 2016 at 10:51 AM, Chris Dagdigian <d...@bioteam.net> wrote:
> Apologies if this is asked often, I did a bit of searching and google-foo
> but could not find very new news...
> I've long been a fan/user of cloudman-managed Galaxy clusters but for the
> first time I need galaxy in an AWS environment where we absolutely cannot
> stand up any sort of public facing service or any sort of host with a
> visible EIC IP address. The hosts can access the internet through NAT etc.
> but we can't run them in a public VPC or otherwise expose them to the
> Internet at large.
> My experiment last night with cloudman launching inside a private VPC
> (with NAT'ed internet access and working forward/reverse DNS resolution for
> all hosts in the subnet) seemed to have failed - the key error in the
> cloudman logs was an endless iteration of "attempting to learn public
> hostname" log entries.
> I blew away the install when I saw that error message endlessly repeating
> because there is zero chance our hosts in this VPC subnet will ever have a
> public FDQN hostname. They all have private IPs and private (but DNS
> resolvable) hostnames.
> Can anyone give a current state update on cloudman inside private VPCs? Is
> this something I should have debugged further or am I better off just
> rolling my own AMI and installing galaxy and perhaps the cloudman elements
> by hand?
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: