WHOA... lots of nice ideas here...

On Tue, May 24, 2011 at 09:44, Fabiano - deStilaDo
<fabianoeng...@gmail.com> wrote:
> Some more ideas:
>
> - Local copy dist files, two very easy ways to do without mirroring a
> huge official gentoo server:
>  - Networked DISTDIR
>  - First server on GENTOO_MIRRORS, like "http://10.0.0.2/gentoo";
>

Yup, that's what I did on my in-company Gentoo servers. For the
cloud-based ones, I just use the Gentoo mirrors (they have *huge*
bandwidth and I'm not capped/throttled).

> - Use you own binary packages: This saves some nice compile time, but
> the binary optimization has to be a common denominator for all the
> architectures in use, or have different binary repositories for
> different arches if they are "really" different (i.e. incompatible).
> For example, if you have intel and amd server you can optimize to
> i686. I like better this approach on more homogeneous setups, like
> everything optimized for say core 2.

Core 2 optimizations work for AMD Opterons?

>  - Here goes my favourite approach:
>   - First backup every affected package with:quickpkg --include-config=y
>     - This makes it very easy to revert a unsuccessfully upgrade and
> usually is sufficient to revert, but special attention must me given
> to programs/services that uses files not save as config files (like
> databases for examples).
>     - emerge with  --buildpkgonly, this way a bin package is built
> but not installed, while the services are running.
>     - now, the upgrade is much faster: service stop, emerge bin
> package = very fast tar unpack, service start. If service does not
> start, emerge very fast unpack time of previous binary backup version,
> service start.
>     - this can be easy automated with shell scripts (or say,
> semi-automated, as the should ask for confirmation on critical
> operations)
>

Very nice tip, thanks!

Will certainly do that for my next updates :-)

> - Versioned configs: you can put config dirs (like /etc) under version
> control, like subversion or git. This makes it easy to track changes
> and do reverts if needed. In case of polytheistic environments (you
> are not the only god, there are other sysadmins) this is also a good
> way to track who changed what, why and when.
>

Interesting... how do I put /etc under svn/git?


Rgds,
-- 
Pandu E Poluan
~ IT Optimizer ~
Visit my Blog: http://pepoluan.posterous.com
Google Talk:    pepoluan
Y! messenger: pepoluan
MSN / Live:      pepol...@hotmail.com (do not send email here)
Skype:            pepoluan
More on me:  My LinkedIn Account  My Facebook Account

Reply via email to