Is anaconda broken roadmap

This page provides a high-level roadmap for implementing the Is_anaconda_broken_proposal project. More detailed tasks can be found in autoqa TRAC roadmap. We follow these steps to define the methods by which we initiate testing

Step 1

Identify all the methods by which we initiate testing :

• URL install source available
• DVD image(s) available
• CD image(s) available
• Live Image

Step 2

Retrieve and check installation media exits

Method	URL	DVD	CD	Live
Media	treeURL	DVD	CD	Live

Step 2

List test scenarios,it will make clear that which suite needs to support.

	Methods to boot vmlinuz+initrd.img
Test	DVD	CD	boot.iso	PXE images	efidisk.img	Live Image
Methods to locate install.img
stage2=cdrom	yes	yes	yes	yes	yes	no
stage2=http://server/path	yes	yes	yes	yes	yes	no
stage2=ftp://[user:passwd@]server/path	yes	yes	yes	yes	yes	no
stage2=nfs:	yes	yes	yes	yes	yes	no
stage2=hd:	yes	yes	yes	yes	yes	no
askmethod	yes	yes	yes	yes	yes	no
Methods to locate packages
autodetect cdrom	yes	yes	yes	yes	yes	no
repo=cdrom	yes	yes	yes	yes	yes	no
repo=http://server/path	yes	yes	yes	yes	yes	no
repo=ftp://[user:passwd@]server/path	yes	yes	yes	yes	yes	no
repo=nfs:	yes	yes	yes	yes	yes	no
repo=nfsiso:	yes	yes	yes	yes	yes	no
repo=hd:	yes	yes	yes	yes	yes	no
repo=hdiso:	yes	yes	yes	yes	yes	no
repo=livecd:	no	no	no	no	no	yes
Methods to locate kickstart file
ks (autodetect from dhcp)	yes	yes	yes	yes	yes	unknown
ks=http://server/path	yes	yes	yes	yes	yes	unknown
ks=ftp://[user:passwd@]server/path	yes	yes	yes	yes	yes	unknown
ks=nfs:	yes	yes	yes	yes	yes	unknown
ks=file:	yes	yes	yes	yes	yes	unknown
ks=hd:	yes	yes	yes	yes	yes	unknown
ks=bd:	yes	yes	yes	yes	yes	unknown
ks=floppy	yes	yes	yes	yes	yes	unknown
ks=cdrom	yes	yes	yes	yes	yes	unknown
Methods to locate updates.img
updates	yes	yes	yes	yes	yes	no
updates=http	yes	yes	yes	yes	yes	no
images/updates.img	no	no	no	yes	yes	no
RHUpdates	no	no	no	yes	yes	no
Methods to determine display device
graphical	yes	yes	yes	yes	yes	yes
text	yes	yes	yes	yes	yes	yes
vnc	yes	yes	yes	yes	yes	no
cmdline	yes	yes	yes	yes	yes	no
serial console=ttyS0	yes	yes	yes	yes	yes	no
telnet	yes	yes	yes	yes	yes	no
Methods to choose kickstart device
ksdevice=link	yes	yes	yes	yes	yes	no
ksdevice=bootif	yes	yes	yes	yes	yes	no
ksdevice=eth0	yes	yes	yes	yes	yes	no
ksdevice=AA:BB:CC:DD:EE:FF	yes	yes	yes	yes	yes	no
Methods to activate network device
ip=dhcp	yes	yes	yes	yes	yes	no
ip=a.b.c.d	yes	yes	yes	yes	yes	no
dns=	yes	yes	yes	yes	yes	no
gateway=	yes	yes	yes	yes	yes	no
netmask=	yes	yes	yes	yes	yes	no

step 3

Set priorities for each test. The test drivers will support the tests with high priority.

Colour	Explanation
yes	supported and default (high priority)
yes	supported (medium priority)
yes	supported (low priority)
no	unsupported configuration
unknown	unknown

step 4

Identify potential test drivers that trigger off of those events.

• URL install source available (typically, http://download.fedoraproject.org/pub/fedora/linux/development/13/i386/os)
  • url_install.py
  • iso_sanity.py (for provided images/boot.iso)
  • bootiso_install.py
  • pxe_install.py (kind of silly, but a possible future test)
• DVD image(s) available (typically, somewhere on http://serverbeach1.fedoraproject.org/pub/alt/stage/)
  • iso_sanity.py
  • dvd_install.py
  • hdiso_install.py
  • nfsiso_install.py
• CD image(s) available (typically, somewhere on http://serverbeach1.fedoraproject.org/pub/alt/stage/)
  • iso_sanity.py
  • cd_install.py
  • hdiso_install.py
  • nfsiso_install.py

Step 5

Write test drivers using requirements gathered in steps #2,#3,#4

Step 6

Write kickstart files to exercise the tests identified in step#2