Anaconda-devel November 2012

anaconda-devel@lists.stg.fedoraproject.org

18 participants
34 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

Ability to install to loopmounted filesystem - mentor wanted
by Tirtha Chatterjee 02 Dec '12

02 Dec '12

Hello. I am trying to implement something like Wubi on Fedora. For this, I first need to make it possible to install to loopmounted filesystems through anaconda. I don't think a lot of modification to the existing source code is required. I tried going through the source code, but it seemed quite big to manage without some guidance. I would be extremely happy if someone guided me on this. Hoping for an affirmative reply :-) -- Regards Tirtha Chatterjee KDE developer http://wyuka.co.cc/

2 3

Re: Crazy custom part UI idea
by Chris Murphy 29 Nov '12

29 Nov '12

On Nov 29, 2012, at 6:26 AM, Steve Allen <allen(a)doobie.itdl.ds.boeing.com> wrote: > Chris Murphy <lists(a)colorremedies.com> wrote: >> >> On Nov 27, 2012, at 12:58 PM, Brian C. Lane <bcl(a)redhat.com> wrote: >> >>> I think that much of this could be fixed by >>> documentation and glossy photographs with circles and arrows and a >>> paragraph for each one. >> >> Because you used the word glossy, I'm going to assume this whole paragraph >> is hyperbole. That this much effort would be necessary to describe UI >> function would by my definition make the UI a hostile user experience. > > I suspect Brian may be a geezer. His reference comes from Arlo Guthrie's > Alice's Restaurant. Yeah fine, and therefore no one is going to read this documentation because all users are effectively blind judges. Chris Murphy

1 0

Crazy custom part UI idea
by Adam Williamson 27 Nov '12

27 Nov '12

So this is probably just the lack of sleep talking, but I notice a pattern in the comments about newUI is that people really aren't confident about which partitions exactly form part of the install, in newUI custom part I was thinking, could we emphasize the difference between 'new Fedora 18 install' and 'existing detected installs' in the left-hand pane more heavily? the specific idea I had may be silly, but it's color coding. give the 'new Fedora 18 install' tree a green background and the old detected installs grey backgrounds, or something. would that help make things clearer? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

6 13

bug cleanup
by Adam Williamson 27 Nov '12

27 Nov '12

hey, folks. Hope no-one minds - yesterday I devised a search to identify F18 anaconda bugs in POST, MODIFIED, ON_QA or VERIFIED status that were fixed in existing anaconda builds but missed being closed, went through, and closed most of them. I checked each bug manually, so for cases which looked like it was possible the bug might not be fixed, I used needinfo instead. That cleaned up 140 bugs or so. If I manage to find time next week I'll go through all open NEW/ASSIGNED F18 anaconda bugs and do some triage on them. if you don't like the sound of that, let me know! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

3 2

iscsi in Anaconda
by "Jóhann B. Guðmundsson" 19 Nov '12

19 Nov '12

Greetings I'm trying to get a move on completing migration from iscsi legacy sysv init to native systemd units since that bug as been open for well over a year now and I'm just wondering if and then how that move might affect Anaconda JBG

2 2

CMD line parm to specify boot loader location in Fedora 18
by Clyde E. Kunkel 16 Nov '12

16 Nov '12

Can't find it now, but I remember seeing that there would be (or is) an Anaconda boot parameter that specifies where we want the boot loader to be installed. Related: during installation, where do we review grub2 device.map entries before boot loader installation? TIA -- Regards, OldFart

2 1

Anaconda/Kickstart updates
by Vratislav Podzimek 15 Nov '12

15 Nov '12

Hi, I have updated our kickstart documentation with changes I've made during F18 development (so far, but I don't expect any additional changes). Could anybody please review the changes? I've updated these sections: https://fedoraproject.org/wiki/Anaconda/Kickstart#keyboard (everything below the "Starting with Fedora 18..." https://fedoraproject.org/wiki/Anaconda/Kickstart#part_or_partition (newly added --hibernation option in the swap section) https://fedoraproject.org/wiki/Anaconda/Kickstart#timezone (again everything below the "Starting with Fedora 18..." Maybe I should also add some info about what timezones we support? Thanks, -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic

4 8

comments on the new custom partitioning UI
by Jeff Moyer 14 Nov '12

14 Nov '12

Hi, I gave the latest install image[1] a try, and I wanted to share my impression of the user interface as it pertains to storage configuration. The very first thing that surprised me was the top-down configuration of storage. What I mean by this is that you specify a file system mount point, and size, without any mention of where it will live. It actually took me several minutes of staring at the UI looking for what I was missing before I actually went ahead and created a file system. After that, I found the obvious drop-downs for choosing whether the file system would be backed by a partition or a logical volume. On my system I have two identical disks, and I decided to create a volume group to host 2 logical volumes, 1 for /boot and one for swap. Then, I created a RAID1 volume to mirror the / partition. This all worked fine, though I was a bit uneasy about not being able to inspect how the partitions were laid out before beginning the installation. I did leave space on both disks. Initially, I had hoped I would be able to create a single volume group that would be larger than I needed, and then just carve out the logical volumes I would use (and leave the rest of the volume group available for expansion). However, due to the way the interface is laid out, there is no way to do this. I can, of course, achieve the same thing after the system is installed by adding another partition to each of the disks, running pvcreate and vgextend. However, I had hoped to set this up in the installer. So, that's my minimal amount of feedback--I hope it's useful. If you have any questions for me, I'd be happy to answer them. Just note that I'm not subscribed to the mailing list, so you'll have to CC me on discussions. Cheers, Jeff [1] https://dl.fedoraproject.org/pub/alt/qa/18/20121101_f18b-smoke14/Fedora-18b…

2 1

Status of firstboot for F19
by Martin Sivak 14 Nov '12

14 Nov '12

Hi, I have a working proof of concept of sharing spokes between anaconda and firstboot targeted at F19. I also have a support for loading 3rd party spokes + their ksdata extensions to have the same data access and export (self.data and install.ks) as everywhere else. Addon has currently the following structure, it is a directory which has the <id> assigned according to it's name: <addon id>/ ks/ (pyanaconda.addons.AddonData) gui/ spokes/ (pyanaconda.ui.Spoke) categories/ (pyanaconda.ui.gui.Category) tui/ spokes/ (pyanaconda.ui.Spoke) The directories contain python files (no __init__.py necessary) and our collect methods look for classes with proper parents (in brackets) in the proper directories when loading stuff. Currently anaconda reads and saves the 3rd party data under self.data.addons.<addon_id> which is an instance of AddonData and is represented by special kickstart section like below. self.data.addons itself is a AddonRegistry class that ensures kickstart export does the right thing and also manages the addon ids. %addon <addon_id> - addon specific data - to be parsed by detected addon - or saved as string so we can export - it back to install.ks %end This should ensure that the code won't fail if the addon is not present (the data will be stored as a string and saved back during export). If the addon is present the parser will pass the lines to the addon's own parser to process and store. I have also modified our UIObject class to look for the sidecar .glade file in the same directory where the instantiated class is defined. I keep the work in progress code (and I rebase quite often) on fedorapeople.org: http://fedorapeople.org/cgit/msivak/public_git/anaconda.git/?h=firstboot-su… http://fedorapeople.org/cgit/msivak/public_git/firstboot2.git/ It is still not review ready, but in case anybody want's to play with it (even from other teams), feel free to report the results. Also if you think about something which needs to be provided by/for 3rd party addons and is not possible using the described model. Ping me. -- Martin Sivák msivak(a)redhat.com Red Hat Czech Anaconda team / Brno, CZ

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel November 2012