Editing QA Team hardware

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
== Why? ==
 
== Why? ==
  
When developers receive testing results, look at bug reports, or discuss technical issues, they may ask you to submit the detailed information about configuration of your computer. This report includes things such as the type of CPU, the kind of memory, and other important hardware specifications. Adding your 'quick link' from here reduces the time which would be wasted if they need ask you to post up additional information, then you getting it and posting it up. It is much faster if you include your link in the bug report/discussion at the beginning. If they do not need it, they need not click on the link.
+
When developers receive testing results, look at bug reports, or discuss technical issues, they may need you to submit detailed information about configuration of your computer. This report includes such things as: the type of CPU, the kind of memory, and other important hardware specifications. Adding your 'quick link' from here reduces the time which would be wasted if they need ask you to post up additional information, then you getting it and posting it up. It is much faster if you include your link in the bug report/discussion at the beginning. If they do not need it, they need not click on the link.
Make sure your hardware is healthy before OpenVZ testing, see [[Hardware testing]] for details.
+
 
  
 
== How to add new configuration? ==
 
== How to add new configuration? ==
  
* Install this application:
+
FIXME: describe how to gather hardware information
 +
 
 +
* Install these three applications (from the trusted standard Ubuntu repositories):
  
 
   rpm -Uvh http://mirror.symnds.com/distributions/gf/el/6/gf/x86_64/gf-release-6-6.gf.el6.noarch.rpm
 
   rpm -Uvh http://mirror.symnds.com/distributions/gf/el/6/gf/x86_64/gf-release-6-6.gf.el6.noarch.rpm
Line 15: Line 17:
 
   hwinfo > openvz_report.txt
 
   hwinfo > openvz_report.txt
  
* Add the output to http://pastebin.org service or create a [https://gist.github.com gist] and add a link to it at the '''top''' of the below table. This [https://raw.githubusercontent.com/chilicuil/learn/master/python/pastebin Python script] may be helpful.
+
* Add output to [http://pastebin.org pastebin] service or create a [https://gist.github.com gist] and link to it to the TOP of table below. This [https://raw.githubusercontent.com/chilicuil/learn/master/python/pastebin Python script] may be helpful.
 +
 
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
Line 28: Line 31:
 
|Server
 
|Server
 
|[https://gist.github.com/ligurio/7654ce5e3714f604c32e Specification]
 
|[https://gist.github.com/ligurio/7654ce5e3714f604c32e Specification]
|[[User:Sergey Bronnikov]]
+
|sergeyb@
 
|-
 
|-
 
|Intel
 
|Intel
Line 34: Line 37:
 
|Desktop
 
|Desktop
 
|na
 
|na
|[[User:Sergey Bronnikov]]
+
|sergeyb@
 
|-
 
|-
 
|Depo
 
|Depo
Line 40: Line 43:
 
|Desktop
 
|Desktop
 
|na
 
|na
|[[User:Sergey Bronnikov]]
+
|sergeyb@
|-
 
|Dell
 
|PowerEdge R510
 
|Rackmount Server
 
|[http://www.montanalinux.org/files/specs-openvz3-cs-montana-edu.txt dmidecode output]
 
|Scott Dowdle
 
 
|}
 
|}
  
  
 
[[Category: QA]]
 
[[Category: QA]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)