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

(BKR-1485) Update documentation #6

Merged
merged 6 commits into from
Jul 16, 2018
Merged

(BKR-1485) Update documentation #6

merged 6 commits into from
Jul 16, 2018

Conversation

Dakta
Copy link
Contributor

@Dakta Dakta commented Jun 22, 2018

Thoroughly document acceptance testing environment configuration.

@Dakta
Copy link
Contributor Author

Dakta commented Jun 22, 2018

This one doesn't actually need unit tests.

Thoroughly document acceptance testing environment configuration.

[skip ci]
Copy link
Contributor

@kevpl kevpl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some small issues to deal with, otherwise it looks fine.

Note that there are a few other spots where the <link> issue came up that I didn't point out, so you'll have to do a pass over it to find them all.

README.md Outdated
We run beaker's base acceptance tests with this library to see if the hypervisor is working with beaker. Please refer to the setting up [vmware fusion](vmware_fusion.md) docs to setup your hosts for testing and modify the [test-nodes hosts](acceptance/config/nodes/test-nodes.yml) file. Once that's setup, there is a simple rake task to invoke acceptance test for the library:
```bash
bundle exec rake test:acceptance
We run beaker's base acceptance tests with this library to see if the hypervisor is working with beaker. You can run the acceptance tests locally; see <acceptance_setup.md>. Once that's setup, there is a simple rake task to invoke acceptance test for the library:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<acceptance_setup.md> doesn't appear to work when I view this page rendered. Does it need to change?


These instructions cover provisioning a Ubuntu 16.04 VM:

1. Download a Ubuntu 16.04 64-bit ISO.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unnecessary, but it would be cool to link out to Ubuntu's downloads page here

These instructions cover provisioning the two testing VMs with a new public key for SSH access. We need two instances of the base VM, `beaker-ubuntu-1604-64` and `beaker-ubuntu-1604-64-2`:

1. You can use the base VM configuration as the first SUT to save space.
2. Configure a static IP for the VM. See <fusion_static_ip.md>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like this has the same problem as above (link broken)


Although originally written for VMWare Fusion 3.x, the Ruby Gem Fission which we use to configure VMWare Fusion VMs appears to work just fine with 10.x. All that is required is changing the local configuration to point to the CLI tools and VM datastore. Create `~/.fissionrc`:

~~~yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this block doesn't render properly. Should these be backticks rather than tilde's?

~~~console
$ ssh root@beaker-ubuntu.local
~~~
5. Create a new snapshot (of the running VM) in VMWare Fusion: with the VM selected, Virtual Machine > Snapshots... > Take Snapshot (Cmd-Shift-S). Name this new snapshot `clear-keys`. This snapshot name is used in [acceptance/config/nodes/hosts.yaml](acceptance/config/nodes/hosts.yaml); when beaker provisions a VMWare host it restores it to a specified snapshot.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dakta it appears hosts.yaml here doesn't exist yet. I'm seeing a test-nodes.yml file, is that what this should be referring to?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorted.

~~~console
$ ssh root@beaker-ubuntu.local
~~~
5. Create a new snapshot (of the running VM) in VMWare Fusion: with the VM selected, Virtual Machine > Snapshots... > Take Snapshot (Cmd-Shift-S). Name this new snapshot `clear-keys`. This snapshot name is used in [acceptance/config/nodes/test-nodes.yml](acceptance/config/nodes/test-nodes.yml); when beaker provisions a VMWare host it restores it to a specified snapshot.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still broken. I suspect that adding a / to the beginning of the link might fix the issue. Looks like the relative link will include the docs folder since it's where this doc lives, which breaks the hosts file URL.

@kevpl kevpl merged commit 761d963 into voxpupuli:master Jul 16, 2018
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

Successfully merging this pull request may close these issues.

2 participants