HowTo test cmserver
From ComputeMode
(Difference between revisions)
| Line 1: | Line 1: | ||
[[Category:User doc]] |
[[Category:User doc]] |
||
[[Category:Status Draft]] |
[[Category:Status Draft]] |
||
| − | [[Category:Version 1.0.0]] |
+ | [[Category:Version 1.0.1]] |
| − | In progress |
+ | === Node autodetection, boot of the CM image and OAR node's creation === |
| + | |||
| + | For node atodetection: |
||
| + | |||
| + | * Actions to perform: |
||
| + | Be sure that the CMserver is running and available |
||
| + | Be sure that nodes are configured to boot from LAN |
||
| + | Launch several nodes at same time |
||
| + | |||
| + | * Checks to perform: |
||
| + | Check that into the CMwebadmin interface, nodes are recorded with the "unconfigured" tag |
||
| + | Check that after IPXE discovery the operating system on the disk is booting |
||
| + | Check the /var/log/apache2/error.log file to detect some web errors |
||
| + | Check the /var/log/error.log file to detect some DHCP/IPXE/TFTP errors |
||
| + | |||
| + | |||
| + | |||
| + | For the CM boot image and OAR node creation: |
||
| + | |||
| + | * Actions to perform: |
||
| + | Log-in into the CMwebadmin interface and configure node scheduler by editing node settings. You can choose the "Always CM" scheduler. By default, this scheduler is using the Debian Squeeze operating system. |
||
| + | Launch several nodes at same time |
||
| + | |||
| + | * Checks to be perform: |
||
| + | Check that the CM image is correctly booting |
||
| + | Check that nodes are also creating into the OAR database (you can use Monika to check that CPU/CORE feature is available) |
||
| + | |||
| + | |||
| + | |||
| + | === OAR access and POV ray demos === |
||
Revision as of 12:02, 19 December 2011
Node autodetection, boot of the CM image and OAR node's creation
For node atodetection:
- Actions to perform:
Be sure that the CMserver is running and available Be sure that nodes are configured to boot from LAN Launch several nodes at same time
- Checks to perform:
Check that into the CMwebadmin interface, nodes are recorded with the "unconfigured" tag Check that after IPXE discovery the operating system on the disk is booting Check the /var/log/apache2/error.log file to detect some web errors Check the /var/log/error.log file to detect some DHCP/IPXE/TFTP errors
For the CM boot image and OAR node creation:
- Actions to perform:
Log-in into the CMwebadmin interface and configure node scheduler by editing node settings. You can choose the "Always CM" scheduler. By default, this scheduler is using the Debian Squeeze operating system. Launch several nodes at same time
- Checks to be perform:
Check that the CM image is correctly booting Check that nodes are also creating into the OAR database (you can use Monika to check that CPU/CORE feature is available)
