Fwd: [suse-autoinstall] auto updating install tree
I am still not clear about the process of getting the updates from SuSe.
1. The command line (online_update) does not have any parameters for
passing my portal username and password.
2. I don't want to use the GUI because I want to script this.
3. man online_update does not exist. -h is very little help either.
4. If I use the gui via YaST2 then the patches get downloaded in
/var/lib/Yast2/you/blah.. This happens for the i386 architecture by
default. How do I also do this for the x86_64 architecture ? (SLES9).
5. There do not seem to be too many rpms doenloaded after step 4. But
a lot of patch-xxx files. What do I do with these ?
6. What do I do with .patch.rpm packages ?
I am so confused that I would rather go back to freebsd and its
awesome cvsup system.
Any help would be appreciated esp with the command lines to get the
updates and info on what parts of the downloaded tree to move into the
updates folder created by Anas's script.
Thanks!
On 4/27/05, Ashe Canvar
Perfect. I got the script after some digging. Will let you know if this works.
http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh
On 4/24/05, Anas Nashif
wrote: Hi,
If you dont know it by now, there is a command line utility for YOU
/usr/bin/online_update
What you can do is download all updates (download only) to the server, create an update source with the script I have posted some weeks ago and copy the rpms to this new source and recreate the package database everytime something changes. All those steps can be automated using a smart script run by cron.
Then you can install new machines with the new packages and without the need to run YOU afterwards...
Anas
Ashe Canvar wrote:
Hi all,
I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive.
The issue I am not clear about is as follows:
- I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126
- if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server.
- What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required.
Is there any way to accomplish this ?
How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual.
I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization.
Thanks!
I am resending because I got no reply. Hopefully this will catch someone's eye this time : I am still not clear about the process of getting the updates from SuSe. 1. The command line (online_update) does not have any parameters for passing my portal username and password. 2. I don't want to use the GUI because I want to script this. 3. man online_update does not exist. -h is very little help either. 4. If I use the gui via YaST2 then the patches get downloaded in /var/lib/Yast2/you/blah.. This happens for the i386 architecture by default. How do I also do this for the x86_64 architecture ? (SLES9). 5. There do not seem to be too many rpms doenloaded after step 4. But a lot of patch-xxx files. What do I do with these ? 6. What do I do with .patch.rpm packages ? I am so confused that I would rather go back to freebsd and its awesome cvsup system. Any help would be appreciated esp with the command lines to get the updates and info on what parts of the downloaded tree to move into the updates folder created by Anas's script. Thanks!
On 4/27/05, Ashe Canvar
wrote: Perfect. I got the script after some digging. Will let you know if this works.
http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh
On 4/24/05, Anas Nashif
wrote: Hi,
If you dont know it by now, there is a command line utility for YOU
/usr/bin/online_update
What you can do is download all updates (download only) to the server, create an update source with the script I have posted some weeks ago and copy the rpms to this new source and recreate the package database everytime something changes. All those steps can be automated using a smart script run by cron.
Then you can install new machines with the new packages and without the need to run YOU afterwards...
Anas
Ashe Canvar wrote:
Hi all,
I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive.
The issue I am not clear about is as follows:
- I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126
- if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server.
- What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required.
Is there any way to accomplish this ?
How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual.
I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization.
Thanks!
On Fri, 6 May 2005, Ashe Canvar wrote:
I am resending because I got no reply. Hopefully this will catch someone's eye this time :
I am still not clear about the process of getting the updates from SuSe.
1. The command line (online_update) does not have any parameters for passing my portal username and password.
you can find information for online_update from SuSe administrator guide
2. I don't want to use the GUI because I want to script this.
use wget to download the patches.
3. man online_update does not exist. -h is very little help either.
4. If I use the gui via YaST2 then the patches get downloaded in /var/lib/Yast2/you/blah.. This happens for the i386 architecture by default. How do I also do this for the x86_64 architecture ? (SLES9).
5. There do not seem to be too many rpms doenloaded after step 4. But a lot of patch-xxx files. What do I do with these ?
6. What do I do with .patch.rpm packages ?
I am so confused that I would rather go back to freebsd and its awesome cvsup system.
Any help would be appreciated esp with the command lines to get the updates and info on what parts of the downloaded tree to move into the updates folder created by Anas's script.
Thanks!
On 4/27/05, Ashe Canvar
wrote: Perfect. I got the script after some digging. Will let you know if this works.
http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh
On 4/24/05, Anas Nashif
wrote: Hi,
If you dont know it by now, there is a command line utility for YOU
/usr/bin/online_update
What you can do is download all updates (download only) to the server, create an update source with the script I have posted some weeks ago and copy the rpms to this new source and recreate the package database everytime something changes. All those steps can be automated using a smart script run by cron.
Then you can install new machines with the new packages and without the need to run YOU afterwards...
Anas
Ashe Canvar wrote:
Hi all,
I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive.
The issue I am not clear about is as follows:
- I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126
- if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server.
- What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required.
Is there any way to accomplish this ?
How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual.
I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization.
Thanks!
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (2)
-
Ashe Canvar
-
Lisa Dong