Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cc-node
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Mirror
cc-node
Commits
d5c96055
Commit
d5c96055
authored
12 years ago
by
Anael Beutot
Browse files
Options
Downloads
Patches
Plain Diff
Added test scenario to documentation.
parent
55493d52
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/dev/source/index.rst
+1
-0
1 addition, 0 deletions
docs/dev/source/index.rst
docs/dev/source/test.rst
+60
-0
60 additions, 0 deletions
docs/dev/source/test.rst
with
61 additions
and
0 deletions
docs/dev/source/index.rst
+
1
−
0
View file @
d5c96055
...
...
@@ -14,6 +14,7 @@ Contents:
architecture
host
hypervisor
test
Indices and tables
==================
...
...
This diff is collapsed.
Click to expand it.
docs/dev/source/test.rst
0 → 100644
+
60
−
0
View file @
d5c96055
Test scenario for cc-node
=========================
Host
----
* Check all tags
* Check handlers: shutdown, execute_command
Hypervisor
----------
* Check all tags
* Check handlers: vm_start, vm_stop (+destroy), vm_suspend, vm_resume, vm_undefine,
vm_export, vm_define
* Check statuses of VMs change
* Check objects are registered/unregistered to the cc-server when VMs
disapear/appear.
Error handling
..............
Behaviour when libvirt connection is lost:
* libvirtstatus tag is updated to disconnected
* domains are unregistered
* some tags (relative to storage pools are unregistered)
* handlers relative to VMs are removed
Behaviour when libvirt connection is retrieved:
* libvirtstatus tag is updated to connected
* domains are registered
* tags (relative to storage pools) are registered
* handlers relative to VMs are added
CC-server
---------
Error handling
..............
Behaviour when connection is lost:
* Nothing changes
Behaviour when connection is retrieved:
* Authentify
* Check role returned and load another main plugin is role changed, else
keeps current runnning plugin
* Register tags and objects
Error handling
--------------
* Test with libvirt/cc-server failures multiple configuration
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment