aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rogier Dikkes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1958) Improve Vagrant setup with vagrant-hostmanager
Date Tue, 13 Feb 2018 08:06:00 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361961#comment-16361961
] 

Rogier Dikkes commented on AURORA-1958:
---------------------------------------

Added these for review:

https://reviews.apache.org/r/63871/

> 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)

Mime
View raw message