PDA

View Full Version : autoyast scripting sles11sp2 install boot-from-SAN



kat888
14-Feb-2013, 03:44
I need to build 3 new clusters each of 8 nodes with diskless HP bl460c blades booting from a SAN.

The problem I anticipate is scripting the partitioning of the boot LUNs. On our existing cluster servers with local RAID disks they are addressed as /dev/sda (or /dev/cciss), and this is consistent on all servers in the cluster. Obviously this won't work when the LUNs have a unique id and are addressed at /dev/<wwn>.

Does anyone have experience of scripting boot-from-SAN installation?

cheers


Kat

Automatic reply
21-Feb-2013, 14:30
kat888,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

olveld
28-Feb-2013, 09:55
hey,

that is a little bit tricky. we actually have the same problems. trying to install on multipathed devices while during installation proces device naming sda,sdb,sdc is changing.
You needn't to script a way , you can use the multipath DUD ( http://www.novell.com/support/kb/doc.php?id=7009981 )

that give's you the ability to use /dev/mapper Device or /dev/dm Device inside your autoyast.xml File!

we are dealing with this problem by giving every Server the same luns ( 3 x 17GB ) while it's initial install . so we always have the same device mapping

(...)
<device_map config:type="list">
<device_map_entry>
<firmware>fd0</firmware>
<linux>/dev/fd0</linux>
</device_map_entry>
<!-- HD0 = VG_SYSTEM -->
<device_map_entry>
<firmware>hd0</firmware>
<linux>/dev/sda</linux>
</device_map_entry>
<!-- HD1 = VG_SYSTEM -->
<device_map_entry>
<firmware>hd1</firmware>
<linux>/dev/sdb</linux>
</device_map_entry>
<!-- HD2 = VG_ORAHOME -->
<device_map_entry>
<firmware>hd2</firmware>
<linux>/dev/sdc</linux>
</device_map_entry>
</device_map>
(...)


but be careful, that is only a valid setup when you have an active/active Storage Array. Active/Passive is way more complicated.

hope that helps ...

--
olli

kat888
05-Mar-2013, 23:11
Thanks for the info Olli, that looks very useful. I should be able to test it later on today.

Kat