QA Team hardware - Revision history

Sergey Bronnikov at 14:43, 9 April 2015

2015-04-09T14:43:06Z

Dowdle: Changed from User: to just name

2015-03-12T15:58:10Z

Changed from User: to just name

Dowdle at 15:57, 12 March 2015

2015-03-12T15:57:16Z

Dowdle: Added my system

2015-03-12T15:56:05Z

Added my system

Sergey Bronnikov: Small correction

2015-03-12T15:42:30Z

Small correction

Sergey Bronnikov: Article is done, removed FIXME

2015-03-12T09:39:23Z

Article is done, removed FIXME

Kir: link to a user (hint: you can just use ~~~~)

2015-03-11T22:32:54Z

link to a user (hint: you can just use ~~~~)

Kir: English, double empty lines

2015-03-11T22:31:11Z

English, double empty lines

Kir: prettify the table

2015-03-11T22:27:43Z

prettify the table

Sergey Bronnikov: Add link to pastee script

2015-03-11T14:56:52Z

Add link to pastee script

← Older revision		Revision as of 14:43, 9 April 2015
Line 2:		Line 2:

	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 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.
		+	Make sure your hardware is healthy before OpenVZ testing, see [[Hardware testing]] for details.

	== How to add new configuration? ==		== How to add new configuration? ==

@@ Line 45: / Line 45: @@
 |Rackmount Server
 |[http://www.montanalinux.org/files/specs-openvz3-cs-montana-edu.txt dmidecode output]
-|[[User:dowdle]]
+|Scott Dowdle
 |}
 [[Category: QA]]

@@ Line 46: / Line 46: @@
 |[http://www.montanalinux.org/files/specs-openvz3-cs-montana-edu.txt dmidecode output]
 |[[User:dowdle]]
+|}
 [[Category: QA]]

@@ Line 40: / Line 40: @@
 |na
 |[[User:Sergey Bronnikov]]
-|}
+|-
 [[Category: QA]]

@@ Line 5: / Line 5: @@
 == How to add new configuration? ==
-* Install these applications (from the trusted standard Ubuntu repositories):
+* Install this application:
    rpm -Uvh http://mirror.symnds.com/distributions/gf/el/6/gf/x86_64/gf-release-6-6.gf.el6.noarch.rpm

← Older revision		Revision as of 09:39, 12 March 2015
Line 4:		Line 4:

	== How to add new configuration? ==		== How to add new configuration? ==
−
−	~~{{FIXME\|describe how to gather hardware information}}~~

	* Install these applications (from the trusted standard Ubuntu repositories):		* Install these applications (from the trusted standard Ubuntu repositories):

@@ Line 29: / Line 29: @@
 |Server
 |[https://gist.github.com/ligurio/7654ce5e3714f604c32e Specification]
-|sergeyb@
+|[[User:Sergey Bronnikov]]
 |-
 |Intel
@@ Line 35: / Line 35: @@
 |Desktop
 |na
-|sergeyb@
+|[[User:Sergey Bronnikov]]
 |-
 |Depo
@@ Line 41: / Line 41: @@
 |Desktop
 |na
-|sergeyb@
+|[[User:Sergey Bronnikov]]
 |}
 [[Category: QA]]

@@ Line 1: / Line 1: @@
 == 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.
+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.
 == How to add new configuration? ==
-FIXME: describe how to gather hardware information
+{{FIXME|describe how to gather hardware information}}
-* Install these three applications (from the trusted standard Ubuntu repositories):
+* Install these 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
@@ Line 17: / Line 16: @@
    hwinfo > openvz_report.txt
-* 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.
+* 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"

@@ Line 20: / Line 20: @@
-{|cellspacing="0" border="1"
+{| class="wikitable sortable"
 !Vendor
 !Model

← Older revision		Revision as of 14:56, 11 March 2015
Line 17:		Line 17:
	hwinfo > openvz_report.txt		hwinfo > openvz_report.txt

−	* 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.	+	* 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.