Re: Installing Arusha on a new site (long, but dull)

[Will P. <pa...@dc...>]

Here are detailed comments on Joel S's notes:

> Following the Sidai team notes on booting ARK stuff, I copied and
> modified the sidai/sysadmin-utils/add-perhost-ark-dirs.sample script.

Note that I've tidied up the "blessed names" for things
(optional, of course); e.g.

   reveal area   deploy area

   /our          /our/.-ark-deploy
   /usr/local    /usr/local/.-ark-deploy
   /             /.-ark-deploy

(I won't change glasli1, because that isn't what it uses :-()

Also, I now am inclined to keep ARK/system-y chunks in /sys,
rather than /d; so I changed things to refer to e.g.

   /sys/.-ark-install-ALL
   /sys/ark-builds
   /sys/ark-state

Note that where I keep tarballs and vendor things are still

   /d/open-src
   /d/vendor-stuff

Again, these are all entirely up to the site owner.

> cd $ARK_SRC/ARK/arkbase
> ./arkcmd package reveal --verbose --use-deps=max arkbase < /dev/null

Given current chat on ark-dev, this may need to change to

  ./arkcmd package reveal --verbose ark-bootstrap

but let's wait and see...

> In the sample1 team, revealing arkbase requires ALL.xml and three
> packages (ark-prereq-utils.xml, ark-site-gen.xml, and arkbase.xml).
> I copied newer versions of these package files from the verilab2 team
> to the package directory of my own team.

I sync'd all of these except ALL.xml, where sample1 and
any-real-team (e.g. verilab2) are trying to do quite
different things (play vs work :-).

> On the next run, I learned that my primary group must match the group
> specified by ark-sysadmin-group-must-be.  ...

Note: if you don't want all ARK work to be forced to be done
as a particular group (e.g. when multiple cooperating
sysadmins), then just don't set that field.

> Arusha complained that a "CVS entry is badly formed." I had checked
> in the Arusha distributions with the -ko option to retain the
> original CVS keyword expansions.  This displeased event.py.

Fixed in the next release :-)

> My next challenge was understanding why Arusha complained about
> directories like /our/.-ark-deploy, which were not mentioned in
> add-perhost-ark-dirs.sample or the HTML documentation.  The explanation
> was that verilabs2 lists different directories than glasli1 or the
> documentation.  ...

Fixed; as per notes above.

> As Arusha installed itself, it created three new directories in /d:
> ark-builds, ark-gen-pkg, and ark-state.  It had some trouble creating
> /d/ark-gen-pkg/arkbase because /d/ark-gen-pkg had not yet been
> created.  Following the approach used elsewhere, I added -p to the
> mkdir options.

Fixed.

> I was installing Arusha on a virgin machine, but Arusha was configured
> to look for tar, gcc, and other programs in the places where it would
> later install them.  Some packages specified a boot version of these
> utilities, but, perversely, these three basic Arusha packages did not.

As you know (from ark-dev), we're taking another run at this
bootstrapping thing; I think it's going to be simpler.

Keep up the good work,

Will