We are working in this as well and have something functioning. I'll leave it
to Matt to give you the details as he's the one whose got it up and running.
Please excuse any typos -- Sent from my iPhone
On Jan 29, 2016, at 1:27 PM, Enis Afgan
> wrote:
Hi Chris,
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 message
(https://github.com/galaxyproject/cloudman/blob/master/cm/controllers/root.py#L863)
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:
https://wiki.galaxyproject.org/CloudMan/CustomizeGalaxyCloud#Using_custom_CloudMan_application
Hope this helps. Let us know how things progress and we can update the code if
a solution is generic.
Cheers,
Enis
On Fri, Jan 29, 2016 at 10:51 AM, Chris Dagdigian
> 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?
Thanks!
-Chris
___
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:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
___
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:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
This message (including any attachments) may contain confidential, proprietary,
privileged and/or private information. The information is intended to be for
the use of the individual or entity designated above. If you are not the
intended recipient of this message, please notify the sender immediately, and
delete the message and any attachments. Any disclosure, reproduction,
distribution or other use of this message or any attachments by an individual
or entity other than the intended recipient is prohibited.
___
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:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/