From Fedora Project Wiki

No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 22: Line 22:
** rsyslog listening on specific port on host
** rsyslog listening on specific port on host


== Watcher ==
== Watcher and Download Images ==


Identify potential test drivers that trigger off of events.
Identify potential test drivers that trigger off of events.


* URL install source (typically, http://download.fedoraproject.org/pub/fedora/linux/development/15/i386/os)
* Source to watcher
* DVD images (typically, http://dl.fedoraproject.org/pub/alt/stage/)
** URL install source (typically, http://download.fedoraproject.org/pub/fedora/linux/development/15/i386/os)
* Live images (typically, http://dl.fedoraproject.org/pub/alt/stage/)
** DVD images (typically, http://dl.fedoraproject.org/pub/alt/stage/)
* netinst.iso images (typically, http://serverbeach1.fedoraproject.org/pub/alt/stage/)
** Live images (typically, http://dl.fedoraproject.org/pub/alt/stage/)
== Download Images==
** netinst.iso images (typically, http://dl.fedoraproject.org/pub/alt/stage/)
* Tree compose: http://download.fedoraproject.org/pub/fedora/linux/development/[$VERSION]/[$ARCH]/os/
 
* DVD, Live, boot.iso, netinst.iso: http://dl.fedoraproject.org/pub/alt/stage/
* Download Methods
** Download by mirror
To avoid multiple download for saving bandwidth and time, the following methods can be adopted:
** Download by proxy (squid)
** mirror
** proxy, such as squid


== Image Sanity ==
== Image Sanity ==
Line 42: Line 43:
* repoclosure for DVD
* repoclosure for DVD
* file conflict for DVD
* file conflict for DVD
== Logging ==
* serial console
* [[Anaconda/Logging]]


== Create Guest ==
== Create Guest ==
Line 58: Line 55:
* libguestfs
* libguestfs


==Step 5 : Logging and watching the steps of installation==
== Logging ==
Get the installation output and logs at every step:
* serial console
{|
* [[Anaconda/Logging]]
! Stage !! Log file !! End label
|-
|width =100|Boot
|width=300|boot.log
|width=300|Greetings
|-
|Stage1
|stage1.log
|Running anaconda [version], system installer - please wait
|-
|Stage2
|stage2.log
|
|}
 
== Key ==
Set priorities for each test. The test drivers will support the tests with high priority.


{| class="wikitable sortable" border="0"
== Watch Installation Steps ==
! Colour !! Explanation
The installation steps can be watched by monitor the terminal output
|-
| style="background-color:green;"|yes
| supported and default (high priority)
|-
| style="background-color:#66FF00;"|yes
| supported (medium priority)
|-
| style="background-color:lightgreen;"|yes
| supported (low priority)
|-
| style="background-color:red; color:white;"|no
| unsupported configuration
|-
| style="background-color:yellow;"|unknown
| unknown
|-
|}


==References==
==References==
<references/>
<references/>

Latest revision as of 05:47, 21 November 2011

Test Environment

  • Virtualization
    • python-fedora installed
    • libvirt installed
    • qemu-kvm installed
    • python-virtinst installed
    • pax installed
    • service libvirtd started
  • Virtual disk (required for hd installation and ks hosted on hd)
    • libguestfs installed
    • python-libguestfs installed
  • Interaction with Desktop
    • Linux Desktop Test Project (LDTP)[[1]]
      • ldtp installed
      • python-ldtp installed
    • dogtail
  • Logging
    • service rsyslog started on host
    • rsyslog listening on specific port on host

Watcher and Download Images

Identify potential test drivers that trigger off of events.

  • Download Methods

To avoid multiple download for saving bandwidth and time, the following methods can be adopted:

    • mirror
    • proxy, such as squid

Image Sanity

  • size
  • sha256sum
  • md5sum
  • repoclosure for DVD
  • file conflict for DVD

Create Guest

  • virt-install

Boot Arguments

  • Linux Desktop Test Project [[2]]

The mapping of test cases with kick start files can be found at Testcase_Kickstart_Mapping

Virtue Disk

  • libguestfs

Logging

Watch Installation Steps

The installation steps can be watched by monitor the terminal output

References

Retrieved from "https://fedoraproject.org/w/index.php?title=Is_anaconda_broken_solution&oldid=261679"