Re: [gentoo-user] Gentoo deployment scripts?
On Mon, 2005-06-06 at 18:00 +0200, Matthias Bethke wrote: the only remaining problem I can think of right now (I'm sure others will pop up once I try it ;)) is configfile management. A nightly removal of all the ._cfg* files plus some scheme to keep the configs in sync with an SVN server should do it. Yep. That is most certainly a problem. Unless of course you're so sure and you can remove CONFIG_PROTECT and then get use buildpkg's to package in the created tbz2 with the new updated configs. (yeah, you can't use --buildpkg to do it since it will be with the original un-changed config files) -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM 98% Microsoft(tm) Free!! Neuromancer 15:05:22 up 2 days, 23:34, 5 users, load average: 1.29, 0.96, 0.77 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Gentoo deployment scripts?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ow Mun Heng wrote: Yep. That is most certainly a problem. Unless of course you're so sure and you can remove CONFIG_PROTECT and then get use buildpkg's to package in the created tbz2 with the new updated configs. (yeah, you can't use --buildpkg to do it since it will be with the original un-changed config files) If you quickpkg a package, IIRC it packages the *modified* etc files into the tarball. k -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCpUoOhJkrd6A3rSsRAgZJAJ9LKM1UThsXxbvIB/f4b316+RGYOgCgniBc Nki2mf7jLw6OvvCglxINMCI= =+DDv -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Gentoo deployment scripts?
On Tue, 2005-06-07 at 12:47 +0530, Aniruddha Shankar wrote: Ow Mun Heng wrote: Yep. That is most certainly a problem. Unless of course you're so sure and you can remove CONFIG_PROTECT and then get use buildpkg's to package in the created tbz2 with the new updated configs. (yeah, you can't use --buildpkg to do it since it will be with the original un-changed config files) If you quickpkg a package, IIRC it packages the *modified* etc files into the tarball. Yep..Yep.. .I meant quickpkg and not buildpkg. Sorry for the typo -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Gentoo deployment scripts?
On Mon, 06 Jun 2005 09:14:07 +0930, Iain Buchanan wrote: why? Isn't this essentially `emerge --buildpkg` ? Have you looked at buildpkg Matthias? I've used it before on similar machines. Seems to work ok. Granted, you can't just `emerge -upD world` on the copies, but you may get away with minimal effort. You can if you use a shared PKGDIR and add -k to the emerge options. -- Neil Bothwick Do hungry crows have ravenous appetites? pgpxilU7K2FFN.pgp Description: PGP signature
Re: [gentoo-user] Gentoo deployment scripts?
Hi Neil, on Monday, 2005-06-06 at 09:08:53, you wrote: Have you looked at buildpkg Matthias? I've used it before on similar machines. Seems to work ok. Granted, you can't just `emerge -upD world` on the copies, but you may get away with minimal effort. You can if you use a shared PKGDIR and add -k to the emerge options. No, I hadn't lookt at this yet, but it seems easy enough, thanks! So it seems I could have one master where I change the configuration and build binary packages along the way, and all the other machines would just run emerge -uDk in a cron job...sounds easy enough. Then I could also get /usr/portage over NFS and wouldn't even have to emerge --sync on the workstations any more, right? Hm...the only remaining problem I can think of right now (I'm sure others will pop up once I try it ;)) is configfile management. A nightly removal of all the ._cfg* files plus some scheme to keep the configs in sync with an SVN server should do it. cheers! Matthias -- I prefer encrypted and signed messages. KeyID: 90CF8389 Fingerprint: 8E 1F 10 81 A4 66 29 46 B9 8A B9 E2 09 9F 3B 91 pgpus7uRkh8YA.pgp Description: PGP signature
Re: [gentoo-user] Gentoo deployment scripts?
On Fri, 2005-06-03 at 20:55 -0400, Antonino Sabetta wrote: Matthias Bethke wrote: If there were such a script that could copy the binaries and the new files to all the other machines I would probably not trust it! :) why? Isn't this essentially `emerge --buildpkg` ? Have you looked at buildpkg Matthias? I've used it before on similar machines. Seems to work ok. Granted, you can't just `emerge -upD world` on the copies, but you may get away with minimal effort. HTH, -- Iain Buchanan [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
[gentoo-user] Gentoo deployment scripts?
There's some SuSE-based workstations around me here I have to take care of. I guess they won't have to bear SuSE for much longer though. The alternatives I can imagine now are Debian and Gentoo. Personally I'd prefer Gentoo, but I don't feel like reinventing the weel by writing my own deployment scripts. There are not many different hardware setups, so I could do an initial install by installing one machine of each and then cloning its HD---the main problem is getting updates done without having to waste megawatthours on unneccessary compilation. I've seen people mentioning such setups here, so I guess somebody has developed the stuff I'd need already? I'd be thankful for any hint or pointer... cheers! Matthias -- I prefer encrypted and signed messages. KeyID: 90CF8389 Fingerprint: 8E 1F 10 81 A4 66 29 46 B9 8A B9 E2 09 9F 3B 91 pgp8uZcXGJbJj.pgp Description: PGP signature
Re: [gentoo-user] Gentoo deployment scripts?
mentioning such setups here, so I guess somebody has developed the stuff I'd need already? I'd be thankful for any hint or pointer... This does not answer you question, but probably could be a partial solution: have you considered cloning the hd of the 'first' machine and then copying it to the hd of all the others? g4u for instance could be used for this purpose AS -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Gentoo deployment scripts?
Hi Antonino,
on Friday, 2005-06-03 at 20:55:43, you wrote:
So you're actually trying to reuse even the compilation work performed on
the 'first' (let's call it 'master') machine and avoid compiling on all
the others when you do an emerge --update world for instance?
That was my idea, or rather that's how I understood someone whose name I
forgot seems to have done it. Makes sense IMHO.
If there were such a script that could copy the binaries and the new
files to all the other machines I would probably not trust it! :)
Why? The total size of the shell/Python/whatever-scripts a simple
emerge foo triggers is probably over a meg, and it usually runs just
fine. Thinking about it, some simple parsing of emerge's output should
do something useful already:
emerge $package |
sed -n '/^ Merging $package/,/^ \* / {s/^[^ ] //; p}' |
while read f; do scp $f $somewhere ; done
I wouldn't mind adding another 500 bytes of Perl there :)
I'd try to automate as much as possible the update process, possibly
by keeping sincronized the configuration files of all the machines (but
this is to be done on a per-file basis!!) and/or triggering an emerge foo
on the other machines as soon as you do an emerge foo on the master.
I must admit that I see this process difficult to understand and to
debug in case of errors or misbehaviours
Yup. It's unlikely something should fail as long as all machines keep an
identical configuration, but glitches can still happen. So I'd have to
look through all the compilation logs...hm :-S We'll see.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: 90CF8389
Fingerprint: 8E 1F 10 81 A4 66 29 46 B9 8A B9 E2 09 9F 3B 91
pgp15ZC6BiYlp.pgp
Description: PGP signature
