[
https://issues.apache.org/jira/browse/AURORA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376054#comment-16376054
]
Stephan Erb commented on AURORA-1958:
-
Hi Rogier,
sorry for the super late response. The problem with this plugin is that it
requires root privileges on the host. I am not a great fan of this.
The aurora client config allows to set a [proxy
URL|https://github.com/apache/aurora/blob/master/docs/reference/client-cluster-configuration.md#proxy_url].
In the vagrant environment one could change the config to:
{code:java}
[{
"name": "devcluster",
"zk": "192.168.33.7",
"scheduler_zk_path": "/aurora/scheduler",
"auth_mechanism": "UNAUTHENTICATED",
"slave_run_directory": "latest",
"slave_root": "/var/lib/mesos",
"proxy_url": "http://192.168.33.7:8081/";
}]
{code}
This would then lead to the generation of URLs working outside and inside of
the VM:
{code:java}
vagrant@aurora:~/aurora$ aurora job create devcluster/www-data/prod/hello
examples/jobs/hello_world.aurora
INFO] Creating job hello
INFO] Checking status of devcluster/www-data/prod/hello
Job create succeeded: job
url=http://192.168.33.7:8081/scheduler/www-data/prod/hello
{code}
This would at least solve the immediate issue with the URLs generated by the
Aurora client.
A completely different alternative, that should also solve the Mesos case,
would be to change the hostname of the VM to localhost and ensure via
portmapping that "localhost:8081" means the same thing inside and outside of
the VM. This is how we currently do it for the packaging tests (see [this
vagrant ssh
command|https://github.com/apache/aurora-packaging/blob/master/test/test-artifact.sh#L28]).
I have not tested this, but I [guess the config could also be moved to the
Vagrantfile|https://www.vagrantup.com/docs/networking/forwarded_ports.html] so
that it works out of the box.
Would any of those ideas work for you?
> Improve Vagrant setup with vagrant-hostmanager
> --
>
> Key: AURORA-1958
> URL: https://issues.apache.org/jira/browse/AURORA-1958
> Project: Aurora
> Issue Type: Task
> Components: Usability
>Affects Versions: 0.19.0
> Environment: Vagrant setup
>Reporter: Rogier Dikkes
>Priority: Trivial
> Labels: newbie, vagrant
> Fix For: 0.20.0
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Currently the vagrant devcluster is setup with aurora.local in the /etc/hosts
> file of the guest virtual machine, however the /etc/hosts file on the host
> machine where Vagrant is running on does not get changed. Result is that
> clients outside of the Vagrant environment have issues connecting to the
> devcluster, also the url within the devcluster environment do not work when
> you use it from your browser. An example of this is the url of the aurora
> framework in the Mesos master page.
> Found vagrant-hostmanager which is easy to implement, it generates the
> /etc/hosts and removes entries upon destroying the Vagrant setup. It also has
> the ability to add entries within the Vagrant environment, for now i left
> that out of the scope of this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
