[opensuse-autoinstall] autoyast with multiple LVM Volume Groups
Hello,
I'm trying to have autoyast setup some LVM volume groups. I can get
things setup with a single volume group, but if try to add 2 volume
groups I seem to be running into some issue.
I'm using the following xml inside the partitioning section to setup
the PVs and add to the volume groups.
.
.
.
<drive>
<device>/dev/sdb</device>
<partitions config:type="list">
<partition>
big beer schrieb:
Hello,
I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups.
[...]
The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist.
[...]
Hello bigbeer,
using SLES10 SP3 the creation of 2 VGs on 2 PVs works for me. There has been
a related issue in the past - I don't remember when it was and what exactly
the behaviour has been - since then I have been using "partition_id" and
"partiton_nr" instead of "partition_type":
<drive>
<device>/dev/cciss/c0d1</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
big beer schrieb:
Hello,
I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups.
[...]
The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist.
[...]
Hello bigbeer,
using SLES10 SP3 the creation of 2 VGs on 2 PVs works for me. There has been a related issue in the past - I don't remember when it was and what exactly the behaviour has been - since then I have been using "partition_id" and "partiton_nr" instead of "partition_type":
<drive> <device>/dev/cciss/c0d1</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition>
database <mount></mount>--> *)
142 -->
1 <size>max</size> </partition> </partitions> <use>all</use> </drive>
*) partition_id: ,,Linux LVM'' = 0x8e = 142 (as reported by fdisk) partion_nr: 1..4 =>primary partitions, 5.. => extended partitions (IIRC)
Regards, Oliver
-- Oliver Schweikert Software Development
HORIBA Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen (Germany) Tel: +49 7158-933-413 Fax: +49 7158-933-613 Email: oliver.schweikert@horiba.com
Geschäftsführer: Thomas E. Ehmann, Yuichi Muroga, Takashi Nagano Amtsgericht Stuttgart, HRB 213200
--
Using the xml you provided worked like a charm! I should note that this is on opensuse 11.3. Thanks! -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Given : SLES 11 SP1
Task:
Create a LVM partition on /dev/sdb. In case the partition already exist just mount/import the LV.
Problem:
I am able to create the LVM partition but i do not know how "import" a already existing partition nor how to prevent autoyast to overwrite the existing one.
Ny current thoughts are using a pre-script or rule to check if there is a already configured /dev/sdb with lvm .
In case none exist the following config will be applied , in case a LVM partiton already exist a post script will import these partition from /dev/sdb
Still i would like to let autoyast do this but i do not know how ?
Any tips or already working config ?
Tia
Hajo
The current config looks like:
<partitioning config:type="list">
....
<drive>
<device>/dev/sdb</device>
<initialize config:type="boolean">false</initialize>
<partitions config:type="list">
<partition>
<create config:type="boolean">true</create>
<format config:type="boolean">false</format>
On Tue, Sep 04, Hans-Joachim Ehlers wrote:
Given : SLES 11 SP1
Task: Create a LVM partition on /dev/sdb. In case the partition already exist just mount/import the LV.
Problem: I am able to create the LVM partition but i do not know how "import" a already existing partition nor how to prevent autoyast to overwrite the existing one.
Ny current thoughts are using a pre-script or rule to check if there is a already configured /dev/sdb with lvm . In case none exist the following config will be applied , in case a LVM partiton already exist a post script will import these partition from /dev/sdb
Still i would like to let autoyast do this but i do not know how ?
Any tips or already working config ?
It works with a pre-script and some sed trickery. I have a non-destructive default
in partitioning section and change it when no lvm vg is detected in pre-script.
I expect volume group rootvg on disk /dev/sdb
I have the following partitioning section:
<partitioning config:type="list">
<drive>
<device>/dev/rootvg</device>
<lvm2 config:type="boolean">true</lvm2>
<partitions config:type="list">
<partition>
<create config:type="boolean">false</create>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
Given : SLES 11 SP1
Task: Create a LVM partition on /dev/sdb. In case the partition already exist just mount/import the LV.
Problem: I am able to create the LVM partition but i do not know how "import" a already existing partition nor how to prevent autoyast to overwrite the existing one.
Ny current thoughts are using a pre-script or rule to check if there is a already configured /dev/sdb with lvm . In case none exist the following config will be applied , in case a LVM partiton already exist a post script will import these partition from /dev/sdb
Still i would like to let autoyast do this but i do not know how ?
Any tips or already working config ?
It works with a pre-script and some sed trickery. I have a non-destructive default in partitioning section and change it when no lvm vg is detected in pre-script. I expect volume group rootvg on disk /dev/sdb
I will take your approach and i will add a importvg (logic) to a post script in case a datavg (lvm) exist already on /dev/sdb Thx Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hi,
Given : SLES 11 SP1
LDAP Server
- auth via SSL is not working SSL & and start_TSL command is not working.
The funny thing. If created via yast / network services / LDAP server - everything works fine.
In case somebody could share a working XML file for a ldap server .....
Tia
Hajo
P.S
My LDAP Server XML file looks like. ( Created via yast autoinstallation , schema entries have been changed )
$ cat ldap_server.xml
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
Am 06.09.2012 11:02, schrieb Hans-Joachim Ehlers:
Hi,
Given : SLES 11 SP1
LDAP Server - auth via SSL is not working SSL & and start_TSL command is not working.
The funny thing. If created via yast / network services / LDAP server - everything works fine.
In case somebody could share a working XML file for a ldap server .....
Tia Hajo
P.S My LDAP Server XML file looks like. ( Created via yast autoinstallation , schema entries have been changed )
Hello Hajo, does your ssl-certificate contain the correct hostname? I experienced a lot of problems with ldap, when the hostname in the certificate and the hostname itself are not identical. Regards from Darmstadt :-) Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (5)
-
big beer
-
Hans-Joachim Ehlers
-
Ivan De Masi
-
Oliver Schweikert
-
Thomas Fehr