hiya
Thomas asked me to talk to the devel list about this. On linux-fai we
talked a bit about yaml support, Thomas hinted at an implementation by
Ingo some time ago
http://faiwiki.informatik.uni-koeln.de/index.php/FaiTemplates and that
someone on this list is working on this too.
I've taken
hiya
Just an update on the template engine modification. So far I'm very happy
with my modification to Thomas' and Kai's original work. I like to give an
appetizer what is possible by now. (Does anybody care? The feedback from
my previous posts was kinda non existent.)
This is a template
hiya
Hello, may a client belong simultaneously to GRUB and GRUB_PC classes?
If not, if a client belongs to GRUB_PC class,
the /files/boot/grub/menu.lst/GRUB
will not be copied to the new system installed.
Nope...GRUB and GRUB_PC are seperate bootloaders.
A server or install client should
Hello
This posting is one half rant to let some steam off and one half
documentation/request.
Okay, I'm not a newbie admin. I think I know my way around quite a lot of
linux distributions. That somehow only adds insult to injury, because I'm
struggling for about several hours to get a working
Hello everyone
Management summary:
- grave bug regarding preserving volumes in last version
- http://www.fluffbunny.de/setup-storage_1.4+ami.tar.gz
- http://www.fluffbunny.de/testwrapper_setup-storage_2012-09-02.tar.gz
As a convenience I attached the testwrapper's readme file which
is also part
Hello
convert_unit 42,75TiB
Please report this error to the Debian Bug Tracking System.
at /usr/share/fai/setup-storage//Parser.pm line 382
Which locale are you using? 42,75TiB looks very much like a german locale
has crept in there somewhere. The setup-storage parser complains it can not
Hello
tl;dr: reasons for the fork, document current state, asking for
feedback/help
I have started to fork setup-storage. Actually forking isn't the proper
term, it's more like a rewrite.
= Why change the code? =
I'm extremely dissatisfied with the current code since I'm using LVM-volumes
Hello
The bug: sameas:disk1 works, sameas:sda does not
Proposed patches and sample config attached to mail.
Output for sameas:disk1
# cat /var/lib/fai/config/disk_config/SAMEAS_DISK1
disk_config disk1 disklabel:msdos align-at:4k
primary - 1G-50% - -
On Tuesday 24 June 2014 16:48:06 Thomas Lange wrote:
It would be nice it you could separate the whitespace
diffs from all other patches.
???
I already did that. patch1_indentation is just the re-indentation to match the
file's general style. It looks a bit intimidating, but it's really just
On Wednesday 25 June 2014 12:12:15 Thomas Lange wrote:
However there's an underlying problem by treating 'disk#' and
hda/sda/xvda differently. patch3 addresses that issue.
Mmm, I did a diff on the code block after sameas:(\S+) and
sameas:disk(\d+). Except for the clone vs. dclone call, it's
Hello
On Wednesday 25 June 2014 14:59:53 Andreas Heinlein wrote:
Moving this to FAI devel as Thomas Lange requested. I tested your
solution and I am happy to say it works for me - both with and without
preserving LV's.
Thank you for the confirmation!
bye
thomas
Hello Thomas, Kerim and who else is listening
PullRequest https://github.com/faiproject/fai/pull/17
Please review this patchset to get rid of the global variable %FAI::disk_var
and the implicit usage of %FAI::configs in find_boot_mnt_point().
Patches can be applied one after another, alls
Hello
I have compiled a patch that can be applied on top of my recent pull request.
https://github.com/ThomasNeumann/setup-storage/commit/407516476a747809553bb4220b1e8fc711e4
---
generate actual disk_var output in
Hello
2 more pull requests which seem very trivial on their on, but follow the
general desire to get rid of as many global variables as possible. While
making these variables local does not have an immediate impact it should
change the reader's mindset from 'this one is global - someone else
Hello
setup-storage 1.5: LVM delete+create works
setup-storage 1.6: LVM delete+create broken
Can someone confirm this regression? I am pretty sure I haven't done some
stupid mistake
(like using the wrong libraries) but an independent confirmation would be nice.
how to reproduce:
==
Hello Kerim
Can you please explain the following line from Commands.pm?
my $tmp_vg = `pvdisplay $raid | grep VG Name | grep -o vg[0-9]`;
Does this really mean you only consider volume groups with a name of
'vgdigit' as valid values for $tmp_vg?
This is how I would do it. Maybe there is
Hello Luke
On Friday 21 November 2014 14:24:27 Luke Alexander wrote:
1) be able to create an lv using extents from a specific physical device in
the vg
2) be able to allocate 100% of the extents from that specific device
What's the deeper meaning behind this? From just this description
17 matches
Mail list logo
