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

doc/dev: add "Deploy a cluster for manual testing" section #8228

Merged
1 commit merged into from Mar 29, 2016

Conversation

smithfarm
Copy link
Contributor

http://tracker.ceph.com/issues/15218 Fixes: #15218

Signed-off-by: Nathan Cutler ncutler@suse.com

At this point, the engineer (user) can ssh into the cluster and do whatever
manual testing is required. This is done by first sshing into the
teuthology node, as described above, and then sshing to one of the cluster
nodes. The IP addresses of the cluster nodes can be found in the OpenStack
Copy link

Choose a reason for hiding this comment

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

I would suggest a simpler approach: "The IP addresses of the cluster nodes can be displayed by running 'openstack server list' on the teuthology machine". The OpenStack credentials and the OpenStack cli are installed there which is convenient.

@smithfarm
Copy link
Contributor Author

@dachary: Revised and repushed.

@ghost
Copy link

ghost commented Mar 20, 2016

Indeed that's what I meant and it does not show in the yaml section of the log, my bad.


``packages-repository`` - VM where packages are stored

``ceph-*`` - VM where packages are built
Copy link
Contributor Author

Choose a reason for hiding this comment

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

EDIT: s/rpm-//

However, there are times when the automated tests do not cover a particular
scenario and manual testing is desired. It turns out that it is simple to
adapt a test to stop and wait after the Ceph installation phase, and the
engineer can then ssh into the running cluster.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

[EDIT] revised the last sentence

Once the target machines are up and running and the test enters its wait
loop, the engineer can ssh into the target machines and do whatever manual
testing is required. Use the teuthology machine as jump host.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

omitted beginning of next chapter - will put it in a new PR

@ghost ghost merged commit 43d63ee into ceph:master Mar 29, 2016
@smithfarm smithfarm deleted the wip-15218 branch March 29, 2016 11:20
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant