| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
Seeing a count of more devices than you can find in the UI is confusing, so
only include them in the count if we're doing the advanced UI.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Having it be private was based upon the old assumption that you couldn't add
devices during installation. Of course, that's incorrect for things like
iSCSI and FCOE. So now that we need to update the size label when the
Add Advanced button is clicked, it needs to be renamed.
|
|
|
|
|
| |
Since the basic screen doesn't even have tabs to display the kinds of devices
that can be added with this button, it doesn't make any sense to show it.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Commit 98504bcaad593f3271a76f1591120310c781049d, accidentally
removes a non related line, this patch restores this.
|
|
|
|
|
|
| |
Commit a75aa437f6fcbf988904b8a630cc82ef12c98dd6, leaves the block of
code this patch re-indents wrongly indented, causing to only be executed
in the else: case of the if above it, while it should be always executed.
|
|
|
|
|
|
| |
device.raidSet.name == device.name, so there is no need to specially
add it to ignore disks, this will only lead to the raidset name being
in ignoredDisks twice.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is needed to make room in /boot on previous installs that only have
a 200 MB (or even smaller) /boot so the upgrade can even continue.
|
| |
|
| |
|
|
|
|
| |
This brings the behavior in line with other (dmraid) biosraid members.
|
| |
|
| |
|
|
|
|
|
|
| |
First, a gtk.ComboBoxEntry doesn't have a get_text() method. It has a
child that has a get_text() method. Second, filter-as-you-type works more
like you would expect if the filters use "contains" instead of "is".
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Make iscsi,etc startup use the iscsi,etc Singletons, instead of the not
yet instantiated instData.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bring fcoe/iscsi/zfcp devices online when parsing the kickstart file
(instead of delaying this to the execute phase) so that the disks
can be identified by /dev/disk/by-path/foo, etc. in clearpart, ignoredisks,
etc. commands.
For the iscsi command this also improves error handling by passing
username and password to addTarget as is instead of only passing them if
both are present, using addTarget's error handling for a username without
a password (instead of simply ignoring the username or the password), and
also by catching IOErrors which will be thrown when logging in to the target
fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fcoe, iscsi and zfcp classes are designed to be instantiated only once,
currently this is not enforced. This is causing trouble as their single
instantiation currently is done in storage.__init__, which means they cannot
be used before instData is instantiated, as that instantiates storage.
However we need them to connect to fcoe, iscsi and/or zfcp drives while
parsing kickstart files (so the drivers can be referenced by UUID /
/dev/disk/by-path / whatever), and instData is not yet instantiated at that
time.
So this patch uses a very simple Singleton design pattern, so that we can
instantiate them where ever we need them, and all references returned will
will point to one shared global instance.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Most Fedora users don't need to see the advanced filtering UI with all its
multipath tabs and advanced storage buttons and search interfaces. So,
provide an introductory screen that allows skipping all that stuff.
|
|
|
|
|
|
| |
This UI is the screen that allows the user to select which devices will be
wiped during installation and which should just be mounted. It also allows
selecting which device the bootloader should be installed to.
|
|
|
|
|
|
|
|
|
| |
This brings back the old behavior of having a dialog that can prompt for
unusual storage devices that require manual intervention, like FCOE and iSCSI.
After the dialog is run, we have to put and new devices into the UI. However,
udev isn't going to provide just a list of newly appeared devices so we have to
maintain a list of what was around previously, and compare the current device
list to that. This promises to be slow but there's not a better option.
|
|
|
|
|
|
|
|
|
|
| |
This UI allows the user to select which devices they would like to include
in the rest of the installation process, sorted out by their types. All
devices not checked will never again be referenced by anaconda, though we
may see their udev information in the logs from time to time. This UI
supports two different ways of looking at things: the simple UI for
regular Fedora users with basic devices, and the complex UI with many tabs
and filtering options.
|
|
|
|
|
| |
Add some text at the top, rework the rest of the text to be more descriptive,
and bold/italicize other text to make it stand out more.
|
|
|
|
|
|
|
| |
This revised screen is part of the simple flow for the new storage
filtering UI. It only offers you to pick the kind of install you want
to do, check to review, and check to encrypt. Everything else will go
on another screen later.
|
|
|
|
|
| |
Unfortunately, the udev data for CCISS does not contain MD_* so I can't use
the udev_device_is_md to key off. This will have to do.
|
|
|
|
|
|
|
|
| |
The return type has also changed. It now returns a tuple of a list of regular
devices, a list of multipath sets, and a list of partition devices. This is
necessary so the filtering UI can use the same knowledge that was in the
DeviceTree object to know which devices are part of a multipath set and which
are just standalone disks.
|
| |
|
| |
|
| |
|