New: [rhinstaller/anaconda/pulls/164 master] Generate random hostnames
by dashea
Instead of defaulting to localhost.localdomain (which makes joining
an enterprise domain difficult), we will instead generate a random
hostname of the form <famous_person>.<adjective>.lan.
Note that if DHCP provides a hostname for this machine, the DHCP-
assigned hostname will be selected, rather than using this
randomly-assigned one.
Testing performed:
Booted two VMs, one bridged to a network which has DHCP-assigned
naming, one NATed with libvirt having no DHCP-assigned names. On
the bridged VM, anaconda selected new-host-4.home as directed by
DHCP. On the NATed VM, it selected newton.elegant.lan as directed
by this random name generation.
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/164
8 years, 2 months
New: [rhinstaller/blivet/pulls/163 master] LUKS resize
by dashea
This is a request for comment, because it is incomplete. I am trying to figure out better ways to test the higher-level functionality but am having problems obtaining a cooperating virtual machine.
There are a few points:
* What makes this a bit tricky is that LUKS is handled as both a device and a format. There is a sense
in which it is both.
* I decided to start from the bottom up this time, working on resizing the format first, rather than worrying about the Actions.
* If the resize of a LUKSDevice is handled as just a resize of its slave's LUKS format then blivet.resizeDevice() does not need to change at all to handle LUKS devices AFAICT.
* However, it does not make much sense to resize a LUKS format outside the LUKS device...since the format knows nothing about the size of the, e.g., filesystem that it encrypts. And yet, it is still possible. Not sure whether it is necessary or desirable to do anything about that.
* I have not handled the dependencies between the actions.
--
To view this pull request on github, visit https://github.com/rhinstaller/blivet/pull/163
8 years, 2 months
[PATCH rhel6-branch] Increment MD container child counter even if its volumes are ignored (#1120640)
by Artur Paszkiewicz
Volumes which are not selected in Specialized Storage Devices are
ignored in addUdevDevice. This causes that their parent container
won't have its child counter incremented, which can later cause an
incorrect unusedRaidMembersWarning.
Resolves: rhbz#1120640
Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz(a)intel.com>
---
storage/devicetree.py | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/storage/devicetree.py b/storage/devicetree.py
index 4045cdf..b9ea399 100644
--- a/storage/devicetree.py
+++ b/storage/devicetree.py
@@ -1328,6 +1328,13 @@ class DeviceTree(object):
# slice off the "/dev/" part, lvm filter cares only about the rest
partitions_paths = [p[5:] for p in partitions_paths]
map(lvm.lvm_cc_addFilterRejectRegexp, partitions_paths)
+
+ if udev_device_get_md_container(info):
+ parentName = devicePathToName(udev_device_get_md_container(info))
+ container = self.getDeviceByName(parentName)
+ if container:
+ container.addChild()
+
return
log.debug("scanning %s (%s)..." % (name, sysfs_path))
--
1.8.4.5
8 years, 3 months