Anaconda-devel December 2012

anaconda-devel@lists.stg.fedoraproject.org

30 participants
21 discussions

post-f18 newui TODO
by Chris Lumens 07 Feb '13

07 Feb '13

I guess we might as well start assembling a list of things we need to do after F18 goes out. Here's what I've got: * Put advanced storage (filtering, multipath/iscsi/zfcp dialogs) back in. * Make system-config-kickstart work again. It's been broken since I got rid of iw/GroupSelector.py (#859928). * Add keyboard accelerators to pretty much everything, breaking all kinds of strings in the process (#864964). * Move us to using mutter (or something like it) so we don't get all the redraw ugliness (#858684). * Review Allan Day's suggestions, see what we can and cannot do, do it. * Review the Wall of Anaconda, see what we can and cannot do, do it. * Work on making our threading a little less awkward. In particular, it can be very hard to tell what thread a method is executing in, and whether or not you can do GTK calls directly. We also could use thread name constants (wasn't someone else already working on that?). * Allow selecting multiple disks (#864707). * Allow a faster way of deleting everything on a disk (#880686). - Chris

5 6

RAID levels not intuitive in anaconda GUI
by Marian Ganisin 02 Jan '13

02 Jan '13

Based on recommendation moving discussion from bug https://bugzilla.redhat.com/show_bug.cgi?id=874068 to anaconda-devel-list. Initial posts can be found in that bug. If you are willing to discuss my notes, please keep me on cc list as I am not subscribed in anaconda-devel list. Thank you. >To address the concerns you specifically wanted explicit addressing: > >> * multiple usage of term redundancy/redundant for few checkboxes. > >The term 'Redundancy' is used once on the RAID configuration screen, I'm looking at the screen now. It is used once, not multiple times. If that isn't what you meant, please clarify. On this screenshot (attached to original bug): https://bugzilla.redhat.com/attachment.cgi?id=640017 First checkbox has label 'Redundancy', last checkbox has label 'Redundant'. In my understanding same terms. Additonally they aren't different by any means, just two equivalent checkboxes for 'redundancy' in same group. Btw that 'RAID6' label visible on the screenshot does not bring any light to selected configuration. >> * error detection is feature of all RAIDs but RAID0, levels can't be >> differentiated > >This is incorrect, Marian. Neither RAID0 or RAID1 have error detection. > >https://en.wikipedia.org/wiki/RAID#Standard_levels Linked section does not seem to mention error detection for any RAID level at all (maybe following table, however that clearly states RAID1 is able to detect/tolerate failure of n-1 drives which is far away best error detection/correction from all other levels). Contrary last sentence of top-level initial paragraph of same wiki page clearly states: RAID levels > 0 provide protection against unrecoverable (sector) read errors, as well as whole disk failure. Additionally md manual page (try man md or read http://linux.die.net/man/4/md ) states exactly same in section RECOVERY: If the md driver detects a write error on a device in a RAID1, RAID4, RAID5, RAID6, or RAID10 array, it immediately disables that device (marking it as faulty) and continues operation on the remaining devices. Marian is right, wiki as well as man md agree with him, all RAID levels except of RAID0 do error detection. Therefore I say that usage of term 'error detection' is highly confusing as it actually counts wide range of RAID levels, RAID is error detecting redundant composition of disks by definition (once more, many professionals do not count RAID0 to RAID family). >> * concern that 'common terminology' used in anaconda is not used anywhere else. > >If you read comment #10 again, you will see I wrote the following: > >in the RAID # format ("common terminology"). > >I was referring to the RAID # format (RAID ), RAID 5, RAID10, etc) as the "common terminology" as that was what Martin called it in comment #0. This confusion is caused by insufficient description of my intention, that's my fault sorry for that. I'll try to correct it. I absolutely agree with initial reporter of reffered bug, Martin Banas, that common terminology is crucial for easy adoption of new RAID handling. In my opinion it is absolutely necessary to bring similar naming as other products providing RAID capability such as BIOS RAID, full featured RAID controllers or other operating systems. I am afraid that terminology introduced in new anaconda isn't used by any similar product and as such it tends to be highly confusing (it is highly confusing to me for all expressed reasons). Therefore I asked to show usage of approach also in other products. I hope it is much clearer now. Well, this is it. Last but not least initial message of bug https://bugzilla.redhat.com/show_bug.cgi?id=874068 describes issue with current implemetation of RAID definition in really specific comments as is and it does not deserve to be closed/rejected without further discussion/research. As the anaconda implements creation of MD devices it would be really nice to have it aligned with MD terminology as expressed in relevant man pages. Thank you very much for audience. Regards, Marian

3 6

Hostnames and Active Directory
by Stef Walter 19 Dec '12

19 Dec '12

Hey all (sorry for starting a new thread about this, just subscribed)... I'd just like to pitch in and say that having a valid hostname is also needed for joining an Active Directory or FreeIPA domain from within Anaconda. A kerberos computer account principal is created based on the hostname (as in gethostname()) of the machine. The keytab of the machine will contain the hostname too. So in order to join a domain from the Anaconda UI, we have to have setup a host name before the post install configuration. This means that (for the AD/FreeIPA use case) it's sufficient to have the hostname in the progress 'spoke', as Chris pointed out: https://www.redhat.com/archives/anaconda-devel-list/2012-December/msg00071.… We would theoretically block on prompting for a the hostname if joining a domain. Somewhat related: In the case of kickstart, we currently assume that the admin has setup some sort of way to distribute unique host names (either via DHCP or munging the kickstart files as they're served). Perhaps this can be fine tuned in the future. Cheers, Stef

2 2

[lorax 1/3] Automatic commit of package [lorax] release [18.24-1].
by Martin Gracik 18 Dec '12

18 Dec '12

From: "Brian C. Lane" <bcl(a)redhat.com> --- lorax.spec | 12 +++++++++++- rel-eng/packages/lorax | 2 +- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/lorax.spec b/lorax.spec index 1191863..ea76217 100644 --- a/lorax.spec +++ b/lorax.spec @@ -1,7 +1,7 @@ %define debug_package %{nil} Name: lorax -Version: 18.23 +Version: 18.24 Release: 1%{?dist} Summary: Tool for creating the anaconda install images @@ -84,6 +84,16 @@ make DESTDIR=$RPM_BUILD_ROOT install %changelog +* Fri Dec 14 2012 Brian C. Lane <bcl(a)redhat.com> 18.24-1 +- imgutils: use -s for kpartx, wait for device creation (bcl(a)redhat.com) +- livemedia-creator: Use SELinux Permissive mode (bcl(a)redhat.com) +- livemedia-creator: use cmdline mode (bcl(a)redhat.com) +- use correct variable for upgrade image on s390 (dan(a)danny.cz) +- only ix86/x86_64 and ppc/ppc64 need grub2 (dan(a)danny.cz) +- no mount (sub-)package since RHEL-2 (dan(a)danny.cz) +- Correct argument to installupgradeinitrd. (dmarlin(a)redhat.com) +- Added fedup requires to spec (bcl(a)redhat.com) + * Wed Dec 05 2012 Brian C. Lane <bcl(a)redhat.com> 18.23-1 - remove multipath rules (#880263) (bcl(a)redhat.com) - add installupgradeinitrd function and use it to install the upgrade initrds diff --git a/rel-eng/packages/lorax b/rel-eng/packages/lorax index 52a8298..5beaf90 100644 --- a/rel-eng/packages/lorax +++ b/rel-eng/packages/lorax @@ -1 +1 @@ -18.23-1 / +18.24-1 / -- 1.7.9.5

1 2

NTH Bugs for F18 Final
by Tim Flink 17 Dec '12

17 Dec '12

Since the list of NTH bugs is so huge right now, we're trying to prioritize the order in which we review the currently proposed NTH bugs. Instead of adding a comment to all of the proposed NTH for anaconda, I figured I would send an email to anaconda-devel-list. If you think that any of the following bugs would be fixed in time for F18 final (currently scheduled for 2013-01-08), please add a comment to the bug or reply to this email. I'll be collecting the "most likely to be fixed in time" NTH bugs to review on Monday. Thanks, Tim (875944) shrinking Windows partition creates an unusable dual-boot setup - https://bugzilla.redhat.com/show_bug.cgi?id=875944 (885807) firewalld accidentally made mandatory; needs to be optional for f18 and f19 - https://bugzilla.redhat.com/show_bug.cgi?id=885807 (864470) anaconda can be closed during installation - https://bugzilla.redhat.com/show_bug.cgi?id=864470 (872826) f18 beta tc7 anaconda - no option to install bootloader to a partition - https://bugzilla.redhat.com/show_bug.cgi?id=872826 (870570) Anaconda needs to retry downloading the repo medata on a network config change - https://bugzilla.redhat.com/show_bug.cgi?id=870570 (878985) MATE entry on RC1 i386 DVD install results in an incomplete mate-desktop (openbox login only) please remove mate from DVD left list - https://bugzilla.redhat.com/show_bug.cgi?id=878985 (876916) anaconda claims I don't have enough free space when I have - https://bugzilla.redhat.com/show_bug.cgi?id=876916 (873605) corrupt NFS installation source doesn't present clear warning text - https://bugzilla.redhat.com/show_bug.cgi?id=873605 (875418) Anaconda fails if not enough memory ie (512MB) - https://bugzilla.redhat.com/show_bug.cgi?id=875418 (875430) After installing unable to boot Fedora 18 with virtio-scsi after successfully installing using virtio-scsi driver (have to use virtio-blk to boot) - https://bugzilla.redhat.com/show_bug.cgi?id=875430

5 8

Re: Adding disaster recovery to Anaconda
by Moray Henderson 17 Dec '12

17 Dec '12

On Mon, 17 Dec 2012 12:58:10 +0100 Vratislav Podzimek wrote: >On Mon, 2012-12-17 at 11:26 +0000, Moray Henderson wrote: >> In anaconda-11.1.2.224.1.el5 (CentOS 5.6) I was able to add a disaster >> recovery utility to Anaconda's rescue mode by adding "junglediskserver" to >> PACKAGESRESCUE and "etc/jungledisk/junglediskserver-license-EXAMPLE.xml" and >> "usr/local/bin/junglediskserver" to KEEPFILERESCUE in scripts/upd-instroot. >> >> I have made exactly the same changes in anaconda-13.21.176 (CentOS 6.3) but >> only the usr/local/bin/junglediskserver file appears in the rescue image; >> the etc/jungledisk/junglediskserver-license-EXAMPLE.xml file is missing. >> >> Does anyone know why the license file is missing in the newer version, or >> how to get it included in rescue mode now? >> >> Thanks, > See KEEPFILE and KEEPFILERESCUE variables defined below PACKAGESRESCUE > in scripts/upd-instroot. I did that: KEEPFILERESCUE now contains etc/junglediskserver/junglediskserver-license-EXAMPLE.xml usr/local/bin/junglediskserver it worked in anaconda-11.1.2.224.1.el5 but not in anaconda-13.21.176. Wait a minute - in the junglediskserver rpm the license files have the 'd' flag. Is that 'documentation'? Are documentation files now excluded even if I've specifically asked for them to be kept? Moray. "To err is human; to purr, feline."

1 0

Re: Adding disaster recovery to Anaconda
by Vratislav Podzimek 17 Dec '12

17 Dec '12

On Mon, 2012-12-17 at 11:26 +0000, Moray Henderson wrote: > In anaconda-11.1.2.224.1.el5 (CentOS 5.6) I was able to add a disaster > recovery utility to Anaconda's rescue mode by adding "junglediskserver" to > PACKAGESRESCUE and "etc/jungledisk/junglediskserver-license-EXAMPLE.xml" and > "usr/local/bin/junglediskserver" to KEEPFILERESCUE in scripts/upd-instroot. > > I have made exactly the same changes in anaconda-13.21.176 (CentOS 6.3) but > only the usr/local/bin/junglediskserver file appears in the rescue image; > the etc/jungledisk/junglediskserver-license-EXAMPLE.xml file is missing. > > Does anyone know why the license file is missing in the newer version, or > how to get it included in rescue mode now? > > Thanks, See KEEPFILE and KEEPFILERESCUE variables defined below PACKAGESRESCUE in scripts/upd-instroot. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

1 0

Adding disaster recovery to Anaconda
by Moray Henderson 17 Dec '12

17 Dec '12

In anaconda-11.1.2.224.1.el5 (CentOS 5.6) I was able to add a disaster recovery utility to Anaconda's rescue mode by adding "junglediskserver" to PACKAGESRESCUE and "etc/jungledisk/junglediskserver-license-EXAMPLE.xml" and "usr/local/bin/junglediskserver" to KEEPFILERESCUE in scripts/upd-instroot. I have made exactly the same changes in anaconda-13.21.176 (CentOS 6.3) but only the usr/local/bin/junglediskserver file appears in the rescue image; the etc/jungledisk/junglediskserver-license-EXAMPLE.xml file is missing. Does anyone know why the license file is missing in the newer version, or how to get it included in rescue mode now? Thanks, Moray. "To err is human; to purr, feline."

1 0

usability lab on DevConf in Brno
by Kamil Paral 14 Dec '12

14 Dec '12

Some of you might be visiting DevConf [1] in February 2013 in Brno. I heard there would be some Anaconda talks. I was contacted by Ben Levenson who's trying to make sure we have enough of interesting QA-related talks and labs. One of his ideas is to set up a usability lab for Anaconda NewUI and he asked me to contact you. The idea is that we would have a set of goals we would ask people to achieve, and we would watch them how they handle the task. There might be interesting outcomes related to different program dialogs/screens and how different people cope with them. Of course if you have other ideas how the lab should work, in can be done another way. The audience on that conference is mainly technical, lots of Red Hatters, but there is a high chance of involvement also from university students and other not-as-technical people. Probably most of the attendees have installed some OS in the past, but I think we might get some people who installed only Windows or Ubuntu, nothing else (some of them might be even Red Hatters, hah, we're not all Linux developers). It might be interesting to see them tackle with Anaconda. The main question is whether you would like to implement this idea. Our local Fedora QA team is willing to help you in any ways with preparation and execution of this lab. It would be great to have some answers by the end of the next week. Thanks. [1] http://devconf.cz/

5 8

Anaconda auto-reboots on unknown error
by Reartes Guillermo 14 Dec '12

14 Dec '12

Hi, I having some issue with anaconda (18.37.2) ,it does reboot by itself in storage, i am not able to even see the 'unknown' error to even perform a proper bug report. I tried to ssh into smoke5 but i got no luck with it. I even tried to scp sshd and sshd_config and launching it manually. I managed to launch the sshd server, but: Also there is firewald, i am unfamiliar with it. I could not perform an 'iptables -F' (no iptables) What is the equivalent command to 'iptables -F' using 'firewall-cmd' ? And also there is no 'passwd' command to set the root password for ssh access. Is there other way to disable anaconda's capability to perform a reboot? Thanks in advance.

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel December 2012