| 1 |
Thierry Carrez wrote: |
| 2 |
|
| 3 |
>Hi folks, |
| 4 |
> |
| 5 |
>I would like to get your opinion on Enterprise-oriented desktop |
| 6 |
>deployment tools for Gentoo Linux (or the lack of). |
| 7 |
> |
| 8 |
>As a small company CIO, I deployed Gentoo on a small scale here but |
| 9 |
>quickly ran into scaling problems and the lack of tools to help. |
| 10 |
> |
| 11 |
>There is no obvious way to freeze a Portage tree (or to design a |
| 12 |
>specific profile) for testing on a golden workstation, |
| 13 |
> |
| 14 |
Why not? Just don't update the portage tree |
| 15 |
|
| 16 |
> to build a set of |
| 17 |
>update packages (ServicePack) and push it to the workstations, or to |
| 18 |
>have centralized accountability of what's installed where. |
| 19 |
> |
| 20 |
set make.conf to point to a static tree stored somewhere which you |
| 21 |
update as time permits. You could even create an /etc/init.d script that |
| 22 |
would check for updates (emerge --sync) against your QA'ed frozen tree |
| 23 |
at each boot. |
| 24 |
|
| 25 |
>There is no |
| 26 |
>easy way to avoid having to keep a synchronized copy of the portage tree |
| 27 |
>on all systems, even when using yourown-binaries. |
| 28 |
> |
| 29 |
> |
| 30 |
see above |
| 31 |
|
| 32 |
>With automatic deployments, would we run into difficult-to-solve |
| 33 |
>etc-update problems ? Should/could the ServicePack system take care of |
| 34 |
>that ? |
| 35 |
> |
| 36 |
> |
| 37 |
etc-update would continue to be a problem |
| 38 |
|
| 39 |
>Even in a simpler setup (preprod > production) we don't have the tools |
| 40 |
>to push a software configuration change from a test machine to a |
| 41 |
>production one. |
| 42 |
> |
| 43 |
>What tools are missing ? Is it our job to provide them ? Can it |
| 44 |
>reasonably be done ? Am I just wrong to want to use Gentoo in that |
| 45 |
>direction ? |
| 46 |
> |
| 47 |
>Next week: Gentoo-as-a-metadistribution tools :) |
| 48 |
> |
| 49 |
> |
| 50 |
> |
| 51 |
I think most of the assumptions that you're making involve giving your |
| 52 |
user population root access. |
| 53 |
Don't |
| 54 |
Lock down your make.conf and only roll up update when you deem is |
| 55 |
neccassary using your internal tree. etc-update may still be an issue.... |
| 56 |
|
| 57 |
-- |
| 58 |
|
| 59 |
Omkhar Arasaratnam - Gentoo PPC64 Developer |
| 60 |
omkhar@g.o - http://dev.gentoo.org/~omkhar |
| 61 |
Gentoo Linux / PPC64 Linux: http://ppc64.gentoo.org |
| 62 |
|
| 63 |
-- |
| 64 |
gentoo-dev@g.o mailing list |
Archives