Hi Oliver, seems to be exactly what I'm looking for! Nice and detailed description. Thanks a lot! Bye, Peer Am 15.04.2016 um 17:56 schrieb Oliver Schweikert:

Hi Peer,

1. Copy the SLES-11-SP3 repository from DVD to $REPO and replace/add your packages below $REPO/suse/*/ as you need.

2. Update the package metadata:

#> create_package_descr -d $REPO/suse -o $REPO/suse/setup/descr

(create_package_descr is part of the inst-source-utils package)

3. Remove all "META SHA1 .... packages*" lines from $DIR/content and

4. add the new hashs to the same file:

#> (cd $REPO/suse/setup/descr && sha1sum packages* | \ while read LINE; \ do echo META SHA1 $LINE;done ) >> $REPO/content

At this point you can install manually, but you will get disturbed by signature and security warnings, which you have to commit.

5. Configure the signature handling in your AutoYaST profile:

<general>

...

<signature-handling> true true true true true </signature-handling> </general>

6. Install with "autoyast=<theprofile> insecure=1".

Regards, Oliver

Am 15.04.2016 um 13:32 schrieb Dr.Peer-Joachim Koch:

...

Hi,

we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome!

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org

Hi, did you try to add the update repositories to the initial installation instead of changing the SLES repository? (My autoYaST xml files look like this: <add-on> <!-- you got the first also via the “pxe install=” line --> <listentry> <![CDATA[ftp://reposerver/repos/sle11sp3/sles11sp3-x86_64/CD1]]> <product>SLES 11 SP3 (x86_64)</product> / <name>sles-x86_64</name> </listentry> <listentry> <![CDATA[http://USER:PASS@EXTERNAL_REPOSERVER/Y....]]> <product>SLES 11 SP3 (x86_64) Updates</product> / <name>sles-x86_64-updates</name> </listentry> ... Best regards Robert On Fri, 24 Jun 2016 09:57:47 +0200 "Dr.Peer-Joachim Koch" wrote:

Hi,

the installation is working very well now using this kind of repository. However when I'm trying to use the YAST tool for auto installation to work on the package list, I get an error. Whenever I select "modify" the system is working for some time, but I never get into the subsection to select packages. I will stay in the top level menu again. Any idea ?

Bye, Peer

On 15.04.2016 20:15, Peer-Joachim Koch wrote:

...

Hi Oliver,

seems to be exactly what I'm looking for! Nice and detailed description.

Thanks a lot!

Bye, Peer Am 15.04.2016 um 17:56 schrieb Oliver Schweikert:

...

Hi Peer,

1. Copy the SLES-11-SP3 repository from DVD to $REPO and replace/add your packages below $REPO/suse/*/ as you need.

2. Update the package metadata:

#> create_package_descr -d $REPO/suse -o $REPO/suse/setup/descr

(create_package_descr is part of the inst-source-utils package)

3. Remove all "META SHA1 .... packages*" lines from $DIR/content and

4. add the new hashs to the same file:

#> (cd $REPO/suse/setup/descr && sha1sum packages* | \ while read LINE; \ do echo META SHA1 $LINE;done ) >> $REPO/content

At this point you can install manually, but you will get disturbed by signature and security warnings, which you have to commit.

5. Configure the signature handling in your AutoYaST profile:

<general>

...

<signature-handling> true true true true true </signature-handling> </general>

6. Install with "autoyast=<theprofile> insecure=1".

Regards, Oliver

Am 15.04.2016 um 13:32 schrieb Dr.Peer-Joachim Koch:

...

Hi,

we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome!

-- Robert Klein UNIX Operations Max Planck-Institut für Polymerforschung Anschrift: Ackermannweg 10, 55128 Mainz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org

Hi, I just notice some unexpected behavior: Using this kind of repository as nfs installations source everything is working perfect. Using the same as http source does not work. Ciao, Peer On 15.04.2016 20:15, Peer-Joachim Koch wrote:

Hi Oliver,

seems to be exactly what I'm looking for! Nice and detailed description.

Thanks a lot!

Bye, Peer Am 15.04.2016 um 17:56 schrieb Oliver Schweikert:

...

Hi Peer,

1. Copy the SLES-11-SP3 repository from DVD to $REPO and replace/add your packages below $REPO/suse/*/ as you need.

2. Update the package metadata:

#> create_package_descr -d $REPO/suse -o $REPO/suse/setup/descr

(create_package_descr is part of the inst-source-utils package)

3. Remove all "META SHA1 .... packages*" lines from $DIR/content and

4. add the new hashs to the same file:

#> (cd $REPO/suse/setup/descr && sha1sum packages* | \ while read LINE; \ do echo META SHA1 $LINE;done ) >> $REPO/content

At this point you can install manually, but you will get disturbed by signature and security warnings, which you have to commit.

5. Configure the signature handling in your AutoYaST profile:

<general>

...

<signature-handling> true true true true true </signature-handling> </general>

6. Install with "autoyast=<theprofile> insecure=1".

Regards, Oliver

Am 15.04.2016 um 13:32 schrieb Dr.Peer-Joachim Koch:

...

Hi,

we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome!

-- Mit freundlichem Grüßen, Peer-Joachim Koch ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

Hi Oliver, the system is starting up, finds network etc. , but is telling me "the following packages could not be found..." I'm using the same folder for NFS and HTTP installation source. At the top level a ISO file for SLES 11 SP3 seems to get found. The system installs everything from the ISO. All the rest is ok. In the log from apache2 I saw the installation looking for some files: [Mon Jun 27 09:49:41 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/ALL [Mon Jun 27 09:49:41 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/ALL [Mon Jun 27 09:49:41 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/ALL [Mon Jun 27 09:49:41 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/ALL [Mon Jun 27 09:54:59 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/media.1/info.txt [Mon Jun 27 09:54:59 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/part.info [Mon Jun 27 09:54:59 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/driverupdate [Mon Jun 27 09:55:23 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/repodata [Mon Jun 27 09:55:26 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/add_on_products.xml [Mon Jun 27 09:55:26 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/add_on_products [Mon Jun 27 09:55:26 2016] [error] [client 192.168.1.100] File does not exist: /scratch/media/SLES11SP3/SP3/product.profile /scratch/media/SLES11SP3/SP3/ALL contains a folder SUSE with all files from DVD and all patches (as you have described before). For NFS it's working this way, when I change it to HTTP I get the error message. Sorry, I'm a little bit busy right now, because one server does not boot correctly and I've to check this. General problem is, that we have 3 different kind of hardware setups and all SAN things have to be done individual. But I want to get all the basics to be the same .... Thanks a lot! Bye, Peer On 27.06.2016 13:11, Oliver Schweikert wrote:

Hi Peer,

never used NFS for this kind of repositories, but HTTP, so it works, principally. At which point do you get an error? Take a look at the linuxrc options, may be its an network setup issue (proxy, dns,..). Use netsetup=1 in the kernel append line and you will get to a networking setup wizard.

http://users.suse.com/~ug/autoyast_doc/appendix.linuxrc.html#id332794

Regards, Oliver

Am 27.06.2016 um 10:39 schrieb Dr.Peer-Joachim Koch:

...

Hi,

I just notice some unexpected behavior: Using this kind of repository as nfs installations source everything is working perfect. Using the same as http source does not work.

Ciao, Peer

On 15.04.2016 20:15, Peer-Joachim Koch wrote:

...

Hi Oliver,

seems to be exactly what I'm looking for! Nice and detailed description.

Thanks a lot!

Bye, Peer Am 15.04.2016 um 17:56 schrieb Oliver Schweikert:

...

Hi Peer,

1. Copy the SLES-11-SP3 repository from DVD to $REPO and replace/add your packages below $REPO/suse/*/ as you need.

2. Update the package metadata:

#> create_package_descr -d $REPO/suse -o $REPO/suse/setup/descr

(create_package_descr is part of the inst-source-utils package)

3. Remove all "META SHA1 .... packages*" lines from $DIR/content and

4. add the new hashs to the same file:

#> (cd $REPO/suse/setup/descr && sha1sum packages* | \ while read LINE; \ do echo META SHA1 $LINE;done ) >> $REPO/content

At this point you can install manually, but you will get disturbed by signature and security warnings, which you have to commit.

5. Configure the signature handling in your AutoYaST profile:

<general>

...

<signature-handling> true true true true true </signature-handling> </general>

6. Install with "autoyast=<theprofile> insecure=1".

Regards, Oliver

Am 15.04.2016 um 13:32 schrieb Dr.Peer-Joachim Koch:

...

Hi,

we are using autoinstall for our HPC cluster. However we have to use old releases, because we are using a global file system on the cluster. So we could now migrate to SLES11SP3 and I'm wondering, if there is a way to setup a repository containing all updates for the system (current status), but with the original kernel from the DVD. Is there an easy way to create this kind of repository ? Or just add the update repository while we install the nodes (but what about the kernel ??) .... Any help will be welcome!

-- Mit freundlichem Grüßen, Peer-Joachim Koch ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705