Editing QA Team hardware

== Why? ==

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.

Developers ask such things as: "please include the output of lsusb, lspci, cpuproc, etc."


== How to add new configuration? ==

FIXME: describe how to gather hardware information


{|cellspacing="0" border="1"
!Vendor
!Model
!Type
!Full specification
!Person
|-
|Depo
|na
|Desktop
|na
|sergeyb@
|-
|Intel
|na
|Desktop
|na
|sergeyb@
|-
|Depo
|na
|Desktop
|na
|sergeyb@
|}


[[Category: QA]]
@@ Line 1: / Line 1: @@
 == 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? ==
+Developers ask such things as: "please include the output of lsusb, lspci, cpuproc, etc."
-* Install this application:
-  rpm -Uvh http://mirror.symnds.com/distributions/gf/el/6/gf/x86_64/gf-release-6-6.gf.el6.noarch.rpm
+== How to add new configuration? ==
-  yum install -y hwinfo.x86_64
-* Run the command:
-  hwinfo > openvz_report.txt
+FIXME: describe how to gather hardware information
-* 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.
-{| class="wikitable sortable"
+{|cellspacing="0" border="1"
 !Vendor
 !Model
@@ Line 24: / Line 18: @@
 !Person
 |-
-|Supermicro
+|Depo
 |na
-|Server
+|Desktop
-|[https://gist.github.com/ligurio/7654ce5e3714f604c32e Specification]
+|na
-|[[User:Sergey Bronnikov]]
+|sergeyb@
 |-
 |Intel
@@ Line 34: / Line 28: @@
 |Desktop
 |na
-|[[User:Sergey Bronnikov]]
+|sergeyb@
 |-
 |Depo
@@ Line 40: / Line 34: @@
 |Desktop
 |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]]