Hi everyone.
I am calling a meeting tomorrow regarding AI manifest organization. We
need to discuss the structure of the files again in a context of
scalability and a compelling user experience.
I request that those people explicitly addressed attend, others are most
welcome as well.
Meeting logistics:
14:00 - 16:00 PST (2 hours, just in case)
Toll Free Dial In Number: (866)545-5227
Int'l Access/Caller Paid Dial In Number: (215)446-3648
ACCESS CODE: 7385082
The main issue is that the functional spec defines two or three files,
in two different formats, and that the user will probably have to edit
them to set up an installation. How to simplify this from the user
point of view and make this a more compelling experience? How to set
the files up to make it as easy for a first-time one-system user as for
an admin of a large lab with many different groups of systems?
We have many factors to consider.
- One hard constraint: The System Configuration (SC) manifest must be a
DTD to fit as an enhanced SMF profile.
- We can't rely on existence of GUI tools to set up the files.
- We don't want to have the contents of the SC manifest specified in
another schema format because we don't want to make users learn two
different formats for specifying the same data.
- RelaxNG schema is much easier to read and work with than DTDs.
Agenda:
Let's start with a few minutes (really) to discuss broadening the
problem statement and set the tone. I'll suggest the following to start
things:
"AI manifest structure and organization should be easy to use and
understand, and scale to a wide variety of installation environments."
Then we'll move into discussing what our options are to solving this
problem.
Thanks,
Jack
P.S. I'd like to leverage what we already have, at:
http://www.opensolaris.org/os/project/caiman/XML_Parsing/xml_2_func_spec.6.pdf
