summaryrefslogtreecommitdiffstats
path: root/kickstart.py
Commit message (Collapse)AuthorAgeFilesLines
* Add escrow supportMiloslav Trmač2009-09-141-7/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for storing an X.509 certificate used to encrypt the escrow data, and a "create backup passphrase" flag, to storage.formats.LUKS, and support for storing the same options of "autopart" globally to storage.Storage. While parsing kickstart directives, download the X.509 certificates specified in thekickstart file (if any), enabling network access if necessary, then store the data in the above-described storage objects. While autopartitioning, copy the "autopart" escrow options into each created LUKS volume. Finally, as a part of doPostInstall, find all LUKS volumes with escrow configured, create the escrow files and store them in /mnt/sysimage/root. Changes since the previous version: - Drop unused .encryptedDevice assignments - Move writeEscrowPackets inside doPostInstall - Fix bugs introduced while moving code to storage.formats.LUKS Further changes: - Don't pass escrow args to lvmpv format constructor. - Move backup passphrase generation into storage.devicelibs.crypto. - Use newer, clearer except syntax in storage.writeEscrowPackets.
* Update for pykickstart with escrow supportMiloslav Trmač2009-09-141-8/+8
| | | | | | A related pykickstart patch (#508963) adds support for key-escrow related options. Use the "F12" versions of kickstart commands to use these options.
* Fix --encrypted when creating volumes in kickstartMiloslav Trmač2009-09-141-3/+3
| | | | | | | | | | | | This fixes handling of e.g. the following kickstart commands: part / --size=1024 --grow --encrypted raid /mnt/raid --level 0 --device=md0 raid.0 raid.1 --encrypted logvol /mnt/lv --vgname=myvg --name=mylv --size=32 --grow --encrypted Anaconda was crashing without this patch, so it is definitely an improvement. More changes might be necessary, I didn't test all cases (e.g. --onpart/--useexisting).
* The zonetab module has moved (#521986).Chris Lumens2009-09-091-1/+1
|
* Expose common fsset methods and properties in class Storage.David Cantrell2009-09-031-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Add the following methods and properties to class Storage which map through to FSSet methods, modify existing calls to use the method on class Storage: turnOnSwap() mountFilesystems() umountFilesystems() parseFSTab() mkDevRoot() createSwapFile() fsFreeSpace() mtab mountpoints migratableDevices rootDevice Callers no longer need to pass the Anaconda object to the FSSet methods directly. The method on Storage takes care of that. The mtab() method on FSSet is exposed as a property on Storage. The same is true for fsFreeSpace().
* Simplify language.py to two basic settings, and a lot of support (#517569).Chris Lumens2009-09-021-1/+2
| | | | | | | | | There's now just two important settings in the Language module: instLang, which is the language used while anaconda is running; and systemLang, which is the language the installed system itself will use. These two can be different mainly due to anaconda's text mode interface. The rest of anaconda should only set and get these two. All the other support functions still exist for grabbing timezone, font, etc.
* Fix a typo in a kickstart error string (#517760).Chris Lumens2009-08-171-1/+1
|
* Do not go interactive if timezone in ks is not valid (#473647)Radek Vykydal2009-08-071-2/+1
| | | | | | | | | | | | Handle invalid timezones in ks the same way as in RHEL 5.4: in case that the timezone is invalid, the system time of install environment will be set correctly if it is in tzdata package, and even if it is not there the ks install will proceed. This will prevent possible breaking of installs with kickstarts working in older versions of RHEL. The question may be if we can/want to broaden valid timezones to all those present in tzdata package officialy (document it). Complete tzdata package is part of stage2 in Fedora and will be in RHEL 5.4.
* Lots of small grammar and wording changes.Peter Jones2009-07-131-8/+9
| | | | Just auditing the world for clarity, don't mind me.
* Edit user-visible dialogs for style.Peter Jones2009-07-131-4/+4
| | | | | We have lots of strings that we display to users which are unclear or contain poor usage and grammar. That's bad.
* error messages of zFCP on s390: log or pass to the UISteffen Maier2009-07-101-1/+4
|
* Add kickstart fcoe commandHans de Goede2009-07-081-0/+10
| | | | Add an command to activate FCoE attached SAN's from kickstart
* Allow creating new groups through kickstart.Chris Lumens2009-07-021-0/+1
| | | | | This is executed before users are created, so new users may be added to the new groups immediately.
* Fix an obvious traceback when doing part --ondisk= (#504687).Chris Lumens2009-06-081-1/+1
|
* Fix discovery of existing raid/lvm for ks install without clearpart ↵Radek Vykydal2009-06-051-1/+1
| | | | | | | | | | | | | | | | | (#503310) (#503681) Default clearPartType to None so that all devices are discovered during storage initialization step, and UI parttype can be set to its default "Replace existing linux system". Also set clearPartType appropriately when going back from partition dialog so that all devices are discovered during storage reset. There is one case that can't be resolved this way: clearpart --all or --linux is set in ks and "Create custom layout" is selected in parttype UI step. Because of ks setting, storage initialization doesn't discover devices (RAID, LVM) on partitions that are to be cleared and therefore they are not present in custom partition dialog. This can be workarounded by going back and than again to custom partitioning dialog. I think we should grey-out type of partitioning combo set to value from ks clearpart command.
* Use the F12 version of the bootloader command.Chris Lumens2009-06-041-2/+2
|
* Remove the bootloader --lba32 option.Chris Lumens2009-06-041-2/+0
|
* Use the F12 version of the driverdisk command.Chris Lumens2009-06-021-1/+1
|
* format.mountpoint -> lvd.mountpoint (#500913).Chris Lumens2009-05-141-2/+2
|
* Use a newer version of the kickstart Partition command.Chris Lumens2009-05-121-2/+2
|
* Only set clearpart data if the command was provided in the kickstart file.Chris Lumens2009-05-111-4/+5
| | | | | This prevents clearPartType from getting set to None, which causes problems in shouldClear.
* Override previously defined mountpoints in kickstart (#499746).Chris Lumens2009-05-111-0/+27
|
* Handle clearpart in the early kickstart pass too.Chris Lumens2009-05-011-2/+14
|
* Fix kickstart PV references handling for lvm on raid (#497352).Radek Vykydal2009-04-271-0/+1
|
* Use slightly better checks when testing for 0 size (#493656, #497186, #497389).Chris Lumens2009-04-241-3/+3
|
* Support --encrypted --useexisting on kickstart installs (#497147).Chris Lumens2009-04-231-17/+37
|
* Enforce the fstype that holds /boot on kickstart installs (#497238).Chris Lumens2009-04-231-0/+4
| | | | | | | This is useful if there's no --fstype= parameter specified since otherwise the default is (for now) ext4. This does not help if the user has a part line for / and none for /boot, since doing a check for that would require knowing what part lines come later.
* Fix editing of raid device (persistence of level choice) (#496159)Radek Vykydal2009-04-171-1/+1
| | | | | | I didn't want to add another 0/'0'/'RAID0' tweaking so I made mdraid.raid_levels and mdraid deviceclass level attribute to contain constants for levels defined in mdraid.py.
* Fix ks --useexisting and --noformat options of logvol and volgroupRadek Vykydal2009-04-171-19/+7
| | | | | | | Combinations of --useexisting and --noformat options of ks commands logvol and volgroup should work (I did basic tests). For volume group, --noformat and --useexisting do the same thing as volume group is not formattable (--noformat is redundant and should be removed from docs)
* Fix ks raid --useexisting and --noformatRadek Vykydal2009-04-081-4/+4
|
* Fix processing of --level and --device options of ks raid commands.Radek Vykydal2009-04-081-5/+6
| | | | | | | | | | * We get RAID1 from ks parser, mdadm accepts only lowercase level specifiers of this form. * We get int device number (e.g. 0) from ks option --device (e.g. md0). Though this might require rather changes in pykickstart, especially when mdadm 3.0 allows creating of arbitrary device names in /dev/md. * mdadm --create --level option is changed to comply strictly to documentation (e.g. "--level=raid0", though "--level raid0" works too)
* Use existing partitions when --onpart is used for PVs or raid members (#493065)Radek Vykydal2009-04-071-5/+16
| | | | | | | Store mapping from pv names used in ks (e.g. pv.1, raid.1) to existing partitions in ks handler and use it when processing ks commands referring to the names. Also fix some attribute references.
* Stop lying about our support for dmraid and multipath in kickstart.Chris Lumens2009-04-061-51/+2
|
* If no partitioning commands are given, apply the UI selections (#490880).Chris Lumens2009-04-031-0/+8
| | | | | | | First, always apply the default partitioning scheme in kickstart installs. Then, always run clearPartitions since it knows best. Finally, if any of the various kickstart partitioning commands are given, unset doAutoPart so the user-provided partitioning scheme takes effect.
* Move %pre processing to much earlier in the install process.Chris Lumens2009-03-311-25/+31
| | | | Also, rename the kickstart processing functions to make more sense.
* Add an early kickstart processing pass.Chris Lumens2009-03-311-13/+55
| | | | | | | | | This gets rid of the old several early passes for VNC and rescue, instead replacing them with a single one that also looks for ignoredisks. We need to look for ignoredisks early on so that we have that list ready before enabling storage. Otherwise, ignoredisks won't really do what it's supposed to. The problem here is what to do about if the ignoredisks directive is located in an include generated by a %pre script.
* Assign weights to partition requests when doing manual or kickstart installs.Chris Lumens2009-03-301-7/+10
|
* Add a missing import (#491605).Chris Lumens2009-03-231-0/+1
|
* storage.disks never includes disks without media present.Chris Lumens2009-03-171-1/+1
|
* Use correct parse method for the upgrade command (#471232)Will Woods2009-03-161-1/+1
|
* Add mediaPresent and eject to the OpticalDevice class.Chris Lumens2009-03-131-1/+1
| | | | | | | These no longer belong in isys.py as putting them in the classes is much more correct. I also put a mediaPresent method on Device in general. This will come in handy when we start dealing with USB CF readers and similar devices that can be present without having media.
* Get rid of the mappings and ksID as well.Chris Lumens2009-03-121-7/+0
|
* Update the volgroup command to work with the new storage code.Chris Lumens2009-03-121-16/+37
|
* Update the raid command to work with the new storage code.Chris Lumens2009-03-121-50/+79
|
* Update the part command to work with the new storage code.Chris Lumens2009-03-121-84/+97
|
* Update the logvol command to work with the new storage code.Chris Lumens2009-03-121-52/+85
|
* addPartRequest is no longer needed.Chris Lumens2009-03-121-14/+3
| | | | | The new storage code schedules actions, so we don't need to batch all the requests up to be added later.
* Clear partitions before scheduling requests.Chris Lumens2009-03-121-0/+4
| | | | | Otherwise, our scheduling requests will get purged by the action loop detector.
* We are searching a list, not a dict nowRadek Vykydal2009-03-101-2/+2
| | | | Related commit: 4503335c6f5d33bcb236da1757123dde73a842bc.
* Start storage before parsing the kickstart file.Chris Lumens2009-03-061-3/+4
| | | | | | This is needed to perform sanity checks on the values given to things like clearpart --drives, as well as to add requests later on. Waiting until we're into the dispatcher steps is too late.
generated by cgit (git 2.34.1) at 2024-09-21 08:32:00 +0000