1 |
Don't sure if this is right place to post, but since I'm experimenting with catalyst |
2 |
maybe someone will share some thoughts and suggests additional reading. |
3 |
|
4 |
What I'm trying to do: |
5 |
|
6 |
1. Create small, task-oriented stage4 for fixed hardware configuration |
7 |
2. Deploy it to several machines (now looking for deployment variants and installers) |
8 |
3. Maintain it (updates) |
9 |
|
10 |
The most interesting and challenging part is (3). There are my thoughts and |
11 |
associated questions: |
12 |
|
13 |
I want special build host, where all binary targets are built. Its setup |
14 |
should be easily repeatable by other developers (i.e. every task should be scripted, |
15 |
without manual tweaks like 'chroot here and patch/emerge this'). Catalyst with |
16 |
specs and overlays seems fine to me. |
17 |
|
18 |
- Which parts of host system affect on resulting target? |
19 |
|
20 |
- I probably do not want update portage tree and world on build host very often, |
21 |
but want newer snapshots and seed stages to build targets. Is it possible? |
22 |
|
23 |
I want incremental selective binary updates to be pushed on nodes. I.e. generate |
24 |
stage4 once, and push only changes for a long period of time. Then repeat. |
25 |
|
26 |
- Is it possible with catalyst to produce icremental binary updates (i.e. feed it with |
27 |
new snapshot and take set of updated packages as a result)? To me seems it is not. |
28 |
|
29 |
- Is portage tree required on nodes in order to install binary packages (never used them)? |
30 |
|
31 |
- My first plan is to unpack stage4, put fresh tree snapshot, clean PKGDIR and update world. |
32 |
Then push everything from PKGDIR to nodes (still don't know how to manage configs). |
33 |
|
34 |
- What about sequential stage4 generation without purging cache? |
35 |
|
36 |
- Get rid of portage on nodes and push binary diffs (or rsync). |
37 |
|
38 |
And small questions about catalyst internals. Is it possible to use some functions manually? |
39 |
For example, I want to mount-bind required parts (/proc, /dev, snapshot, distfiles...), |
40 |
chroot to storedir/tmp/default/stageX, do or test something manually and then exit and unmount. |
41 |
Is there are any handy scripts to do this? Manual catalyst execution step-by-step? |
42 |
Also it will be good to just look on emerge -pv output, or list URLs which catalyst |
43 |
tries to fetch (for manual fetching and offline operations). |
44 |
|
45 |
|
46 |
Any thoughts? How do you guys organize things like this? |
47 |
-- |
48 |
gentoo-catalyst@l.g.o mailing list |