| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* iw/datacombo.py (set_active_text): Make sure we return False when we
don't find 't'.
* iw/partition_gui.py (createCB): Activate the 'create lv' radio button
only when there is free space in a Volume Group. Create a Combo box
with a list of the Volume Group(s) that have free space. Pre-select the
Volume group that the user has selected in the tree view.
(editCB): Call the editLVMLogicalVolume with its new parameters.
(editLVMLogicalVolume): Change the parameters for this function.
(device, isNew = False) -> (lv = None, vg = None). In this way if lv is
none and vg is a Volume Group we are creating a new LV in the vg Volume
Group. If lv is not None, we are editing lv.
* ui/create-storage.glade: Put the 'create lv' radio button in a
Horizontal box so we can fit the Volume Group Combo Box.
|
|
|
|
|
| |
* ui/create-storage.glade: Give the 'vertical' orientation to the
gtk.VBox elements.
|
|
|
|
|
|
|
| |
For all the elements that are not showable in the bar view, we should
show the information graph. The "Please select a device" message
instead of a device. The 'edit' and 'delete' buttons should be
non-sensitive as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When users click on stuff that is not editable or deletable we should
not let them click on the edit and/or the delete buttons. It is still
possible to click edit or delete for a partition that is part of a
Volume Group or a RAID device. In this case the user will be presented
with a message that describes the reason for not editing or deleting.
This behavior is on purpose so the user is not confused when the
"delete" or the "edit" button are not active on something that could be
thought as editable or deletable. Also, I want to avoid going down to
the storage class every time the user clicks on the GUI.
Now we are sure that we receive a device in these functions and
therefore don't need checks in deleteCB and editCB.
* iw/partition_gui.py (treeSelectCB): set_sensitive(True) when user
clicks on something that is editable or deletable.
(getScreen): make the edit button and the delete button part of the
class variables so we can access them in treeSelectCB.
* iw/partition_gui.py (deleteCB, editCB): Stop checking to see if what
is selected is a device.
|
|
|
|
|
|
|
|
|
|
| |
Previously these were no-op actions. Now that editCB can handle LV, VG
and RAID, we should activate this in the custom screen.
* iw/partition_gui.py (treeActivateCB): Add
storage.LVMLogicalVolumeDevice, storage.LVMVolumeGroupDevice and
storage.MDRaidArrayDevice to the types of devices that we react to when
double clicking the tree view.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the tree view has much more space than before, there is no need
to hide the RAID or LVM. In the worst case scenario the user can
manually hide the RAID, LVM or Device lists by using the horizontal
arrow beside the device type title.
* iw/partition_gui.py (populate, getScreen, appendToHiddenPartitionsList
(clearHiddenPartitionsList, resetSelection, viewButtonCB): Removed
clearHiddenPartitionList and appendToHiddenPartitionList. Also removed
self.show_uneditable.
|
|
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (MessageGraph): New class that handles the
message.
(treeSelectCB): Every time a device is selected in the tree, destroy the
message object and replace it with the device stripe graph.
(getScreen): Initialize the new Message object and put it in
self.messageGraph.
|
|
|
|
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (l_d_g, r_d_g, p_d_g): Use aliases for modules
with long names: l_d_g -> lvm_dialog_gui, r_d_g -> raid_dialog_gui,
p_d_g -> partition_dialog_gui. This allows for better line formating
when using these modules.
(createCB, editRaidArray, editPartition, editLVMVolumeGroup)
(editLVMLogicalVolume, lvm_dialog_gui, parteditor, partition_dialog_gui)
(raid_dialog_gui, raideditor): Use boolean when passing the isNew value.
while 1: -> while True:
|
|
|
|
|
| |
* iw/partition_gui.py (__init__, _createStripe): Handle the
initialization of self.tree and self.editCB in the child clases.
|
|
|
|
|
| |
* iw/partition_gui.py (_createStripe): Uset "%.0f" to output the size
values.
|
|
|
|
|
|
| |
* iw/partition_gui.py (_createStripe): We add a "free space" sliece to
the extended partition when the last offset of the last logical
parition is less then the end of the extended partition.
|
|
|
|
|
|
|
|
|
| |
The message was being munged and it was overly long, grabbing attention
from the drive lists.
* iw/raid_dialog_gui.py (__init__): Reduce message length. Introduce
some padding for the drive lists. The gtk reference suggests to use
set_default_size instead of set_size_request
http://www.pygtk.org/docs/pygtk/class-gtkwindow.html#method-gtkwindow--set-default-size
|
| |
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (_createStripe): Add the new call back function.
(selectRowFromObj): New call back function. More general than the
previous one
(selectPartition): Remove old callback function.
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (StripeGraph, method, getCanvas, setDisplayed)
(_createStripe, __init__): The canvas used to paint the graphs will be
the same for all the classes. Access the canvas through getCanvas,
which is a classmethod now.
|
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (treeSelectCB): Make sure that the graph is being
painted by the right StripeGraph class. We decide which graph to use
based on the device we receive.
(resetCB, refresh, viewButtonCB, getScreen, populate): Change the custom
screen graph name from diskStripeGraph to stripeGraph.
|
|
|
|
|
|
| |
* iw/partition_gui.py (LVMStripeGraph) : New class to handle the LVM
graphs.
(MDRaidArrayStripeGraph) : New class to handle the md RAID graphs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason behind this change is to make the code ready for LVM and
RAID.
* iw/partition_gui.py (Slice, Stripe, StripeGraph): New classes that
replace the old ones. These new clases do not depend on partition
objects. The only accept offsets and lengths.
(Slice.eventHandler): Introduce a oneClick and doubleClick call back
funcitons. The one click call back will be used for selecting the tree
device when the bar device is clicked.
(DiskStripeGraph): Make the new DiskStripeGraph use the generic bar view
clases.
(Stripe.putOnCanvas, Slice.putOnCanvas): New function. It separates
the creation of the class from the drawing of whatever the class
represents. When this function is called, the drawing occurs.
(Slice.select, Slice.deselect): Change color on the bar view when
(de)selecting slices.
(addSlice): New function that handle the addition of slices to stripes.
(DiskStripeGraph.setDisplayed, DiskStripeGraph.getDisplayed): New
functions to handle the shown "device".
(DiskStripeGraph.display): Expects a storage.DiskDevice. Creates Stripe
and draws immediately. Will remove whatever was previously on bar view.
(shutDown): Mark the currentDisplayed as None.
|
|
|
|
|
|
| |
* iw/partition_gui.py (display): Pass the device instead of just the
name.
(add): Use the device to display the path, instead of "/dev/" + name.
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (__init__): For the "Device" cell renderer, use
'markup' instead of just text.
(populate): Use pango markup to chaqnge the size and color of the
device paths for 'normal' devices and raid devices.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (__init__): Add variable to track the displayed
storage element.
(getDisplayed, setDisplayed): New functions that manage the
varialbe holding the current displayed storage element.
(display): New function that handles the display of a disk.
(populate): Show only one disk in the bar view.
(treeSelectCB): When the user clicks on one of the disks or the
partitions, modify the bar view if needed.
(getScreen): A vertical Pane is not needed anymore.
|
|
|
|
|
| |
* iw/partition_gui.py (editCB): Fix indentation on the "Unable to edit"
message.
|
|
|
|
|
|
|
|
| |
Increase readability in getScreen.
* iw/partition_gui.py (getScreen): Remove the unneeded spaces. Replace
the \t where needed. Put the "Hide" checkbox in the same level as the
buttons.
|
|
|
|
|
|
| |
* iw/partition_gui.py (getScreen): Point the checkmark loading line to
the new checkMark.png image.
* pixmaps/checkMark.png : New check mark image.
|
|
|
|
| |
* iw/partition_gui.py (DiskTreeModel): Modified the "titles" variable.
|
| |
|
|
|
|
|
|
|
|
| |
Put the action buttons at the bottom of the screen (on top of the "Ok"
and "Cancel") buttons so they similar to what gnome standard uses.
* iw/partition_gui.py (getScreen): Change the order of the main
customization screen.
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (makeLvmCB, makepartCB, makeraidCB): Remove
functions.
(createCB): Add the messages.
* ui/create-storage.glade: Make the buttons visible and sensitive.
|
|
|
|
|
|
|
| |
* iw/partition_gui.py (createCB): New function. All the create requests
will pass through this function. It pops up a dialog that presents the
different creat options to the user. Use the new storage/partitioning.py
function (hasFreeDiskSpace).
|
|
|
|
|
| |
* ui/create-storage.glade: New file. Glade file that describes the new
screen.
|
|
|
|
|
|
| |
It is not implemented for now. Going to wait for the new doPartitioning
code.
* storage/partitioning.py (hasFreeDiskSpace): New function.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* iw/lvm_dialog_gui.py (run, convertToActions): New function. Need to
have a separate function so we can run it from the editLVMLogicalVolume
function in iw/partition_gui.py. We call new function from run.
* iw/partition_gui.py (editCB): Call the new editLVMLogicalVolume
function.
(editLVMLogicalVolume): New function. Serves the same purpose as
editLVMVolumeGroup but for Logical Volumes.
(deleteCB): All actions are created when we delete a selected LV. We do
need to make sure that we delete the deleted LV from the VG that
|
|
|
|
|
|
|
|
| |
If we get a failure to commit a partitioning change to disk, the first
thing to do is try shutting down all devices: In the case of lvm-on-md
we implicitly activate the md device in order to wipe an lv that we're
about to destroy. Subsequent attempts to commit to a disk containing any
of the md device's members will fail because the md is still active.
|
| |
|
| |
|
|
|
|
|
|
| |
The path attribute may have changed due to parted renumbering things,
so we need to grab the partition by its original path instead. Otherwise
we may be grabbing the wrong partition.
|
| |
|
|
|
|
|
|
| |
Since the parted ebusy errors due to unnecessary udev event generation on the
partition nodes bug has been nailed, we no longer need the retry loop around
committing to disk.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Touch /dev/.in_sysinit, as that stops /lib/udev/rules.d/65-md-incremental.rules
from messing with mdraid sets.
This patch adds the touching twice, once to our own init, for when running
as standalone installer, and once in python for when running from a livecd,
to stop the udev trigger "block" we do will cause
/lib/udev/rules.d/65-md-incremental.rules to trigger in the livecd case.
|
| |
|
|
|
|
|
|
|
| |
With the new external metadata mdraid support we need to wait for raid
sets to become clean (iow for mdmon to have finished updating the metadata)
before rebooting. Otherwise we get a full array sync on the first boot after
installation.
|
|
|
|
|
|
| |
This parameter has the same format that url --proxy= does in loader. In
fact, we use the same regular expression in both places. Be sure to change
both if you change one.
|
|
|
|
|
|
|
| |
We pass the URL and port as the --proxy= argument, and any authentication
information through /tmp/proxy. This file will be removed by stage2. The
reason for this song-and-dance is so passwords aren't on the anaconda
command line.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The proxy parameter to be used on the cmdline and in kickstart is
of the form:
proxy=[protocol://][user[:password]@]host[:port]
This is also used as url --proxy= and repo --proxy=.
|
| |
|
|
|
|
|
| |
Also, rip out all the username/password stuff too. That's not needed for
nfs.
|
| |
|