Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document what can be tested in Testing with Vagrant #76

Open
stevepiercy opened this issue Apr 24, 2017 · 6 comments
Open

Document what can be tested in Testing with Vagrant #76

stevepiercy opened this issue Apr 24, 2017 · 6 comments
Assignees

Comments

@stevepiercy
Copy link
Contributor

It's not clear what can be tested under Testing with Vagrant. It would be good to set the user expectation so they don't spend time trying to get something to work that will not, and to improve documentation for things that do work, including links to settings in this repo and Plone docs.

The running of the playbook itself is one test.

It took a while to figure out how to SSH in. I got some settings from vbox_host.cfg. Eventually I figured out that this works: ssh -i /path/to/virtualbox/private_key [email protected] -p2222

I tried all the suggested ports over HTTP:
http://127.0.0.1:1080 (web server/virtual hosting. Links and subrequests to assets (JS, CSS, images) won't work. If there is a known fix or workaround, it would be good to document that.)
http://127.0.0.1:2080 (haproxy stats page?)
http://127.0.0.1:7081 ("Plone is up and running" page)
http://127.0.0.1: 9080 (webdav?)
http://127.0.0.1: 5949 (munin?)

Is there anything that can be tested, and if so through what method?

I volunteer to do any documentation for this.

@stevepiercy stevepiercy self-assigned this Apr 24, 2017
@ramiroluz
Copy link
Member

To ssh you can just run vagrant:
vagrant ssh

Here are some default ports and the location where they are defined:

  • 1080: haproxy - roles/haproxy/defaults/main.yml
  • 4949: munin_node - roles/munin-node/defaults/main.yml
  • 80, 443: nginx - roles/nginx/templates/host.j2
  • 8100: zeo_port - roles/plone.plone_server/defaults/main.yml
  • 8081: client_base_port - roles/plone.plone_server/defaults/main.yml
  • 6081: varnish - roles/varnish/defaults/main.yml

The Vagrantfile, expose this ports:

  • nginx 80 -> host: 1080 (web server/virtual hosting) It don't work because the regex used to configure nginx. Don't know if there is a workaround.
  • haproxy 1080 -> host: 2080 (haproxy stats page)
  • varnish 6081 -> host: 7081
  • load_balancer default front end port 8080 -> host: 9080
  • munin 4949 -> host: 5949

Could not find where the load_balancer default front end is defined as a default, but found this document: http://plone-ansible-playbook.readthedocs.io/en/latest/load_balancer.html

@acsr
Copy link

acsr commented Jun 21, 2018

In the multiserver example first of all the initial provisioning is not tested if it fails at all. See my ticket: #113 Therefore a later failing does not give any hint. If you customize the example everything in the tests needs to be adjusted (right?)

tkimnguyen added a commit that referenced this issue Mar 16, 2019
@tkimnguyen
Copy link
Member

@stevepiercy I think this PR #118 addresses your main point

If you think the vagrant ssh instructions are missing from the docs, please create a new issue

@stevepiercy
Copy link
Contributor Author

There is no main point, but several interrelated points. Reopening.

@stevepiercy stevepiercy reopened this Mar 16, 2019
tkimnguyen added a commit that referenced this issue Mar 17, 2019
@tkimnguyen
Copy link
Member

I added @ramiroluz 's helpful port forwarding info

@stevepiercy
Copy link
Contributor Author

I added some comments to the commit. I could not submit them to request changes in a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants