[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-autoinstall
Subject:    Fwd: [opensuse-autoinstall] autoyast and vlan
From:       686f6c6d <686f6c6d () googlemail ! com>
Date:       2010-11-16 17:32:24
Message-ID: AANLkTi=hncvoV92f17FvUo2x4yd3T=7RZuwMJtuNrSQP () mail ! gmail ! com
[Download RAW message or body]

Sorry again, I only bcc'ed this mail to the list, which apparently
caused it to disappear.

tty,
    686f6c6d


---------- Forwarded message ----------
From: 686f6c6d <686f6c6d@googlemail.com>
Date: Tue, Nov 16, 2010 at 13:32
Subject: Re: [opensuse-autoinstall] autoyast and vlan
To: Dirk.Lohmann@bertelsmann.de


On Mon, Nov 15, 2010 at 10:40,  <Dirk.Lohmann@bertelsmann.de> wrote:
> Hello,
> we are using the SELS11 minicd with costum-made initrd.
> If we boot with minicd, we boot into a graphical menu because we must configure the \
> vlan there.

Ok, first of all, please take your time to read my email from
2010-11-14 and answer the questions, one by one, if that is possible.
Otherwise we're running in circles here.


> After we configured the vlan manuely the installation is going on. But after the \
> first reboot we have to configure the vlan again.

Yes, I tried to answer that before, but I left out some important
details it seems. (;
The thing is, if you configure your network manually, (to my
knowledge) autoyast has no way of knowing that, and hence you have to
configure it manually *again* in stage 2 in this case.
It is certainly debatable if this autoyast behaviour makes sense. I
myself would like it very much if autoyast would, for example, extend
<keep_install_network> to also remember a manually set-up network.
(Uwe: Are there reasons why this wouldn't work or is a stupid idea?)

However, the best option I found in your case was the one I was
referring to in my long mail from before:
- Put the commands you did manually in a shell script (because they
look like they can be automated to a very high degree)
- Put a small autoyast profile (autoinst.xml in my setup) on the boot
CD with scripts to:
 - bring up the network as you would do manually (you can also use
ask-scripts to fetch user input)
 - fetch the second profile (net.xml in my setup) from a webserver
(if you use one) and fetch it to, like, /tmp/stage2.xml
 - patch your already-manually-set network settings into that new
autoyast profile and then move the file to /tmp/profile/modified.xml
(This way, autoyast will use your user-input network settings in stage
2!)

As a - lesser - alternative to the last point, you could instead use a
script that "rescues" your file to stage2 and bring the network up by
script from these values again. But then you still have to set it up
manually *again* because you never told autoyast the machine should
have a network configuration.

How the exact VLAN section of the autoyast profile must look like you
can best find out if you clone an existing server's settings.


HTH,
    686f6c6d
-- 
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org


[prev in list] [next in list] [prev in thread] [next in thread]