use host only networking for brooklyn node #31
Conversation
- brooklyn accessible via mapped 8081 port at http://127.0.0.1:8081 which matches the manual install url (simplifies docs) - can still access the byon nodes and avoids having to worry about subnet clashes for brooklyn itself
|
fyi @neykov this is related to your comment about the web console url not being correct for Vagrant. |
| ip: 10.10.10.100 | ||
| forwarded_ports: | ||
| - guest: 8081 | ||
| host: 8081 |
There was a problem hiding this comment.
If someone has another process listening on port 8081, then presumably vagrant up brooklyn will fail with a nice message? Is that ok to assume they won't have anything else running there? I think yes.
There was a problem hiding this comment.
If it's a process running in userspace then it will override the mapped port which will become accessible if the overriding process is halted.
Give me a second and I'll check the output from :auto_correct
- defaults to true in servers.yaml - doesn't appear to be too reliable, currently fails for me and throws the following warning before attempting to install, rather than fail silently with the locally bound port overriding the forwarded brooklyn port: ``` ==> brooklyn: Clearing any previously set forwarded ports... Vagrant cannot forward the specified ports on this VM, since they would collide with some other application that is already listening on these ports. The forwarded port to 8081 is already in use on the host machine. To fix this, modify your current project's Vagrantfile to use another port. Example, where '1234' would be replaced by a unique host port: config.vm.network :forwarded_port, guest: 80, host: 1234 Sometimes, Vagrant will attempt to auto-correct this for you. In this case, Vagrant was unable to. This is usually because the guest machine is in a state which doesn't allow modifying port forwarding. ``` - Updated the Vagrantfile to point the user at `servers.yaml` when they search for the suggested line in the warning above.
|
LGTM. Works for me when nothing else is using port 8081. Merging, and will cherry-pick into 0.9.0 branch. |
3 participants
vagrant up) via mapped8081port athttp://127.0.0.1:8081which matches the manual install url (simplifies docs)10.10.10.xand avoids having to worry about subnet clashes for brooklyn itself