Hi Jack, Some general comments/questions:
1. The scope of this project is listed as: > The scope of this document encompasses input specifications > (manifests) for the Automated Installer > project (AI). However, later I do not see any mention beyond the 3 manifests that are included in this input specification list. The reason I am asking about this is that we had talked previously about the possibility of defining separate input specs for common functionality among the caiman installers. For example, specification for target devices on which to work. Both AI and DC do this today, although in different ways, but the commonality of the functionality allows for us to possibly define a 'target' input specification that can be used by multiple consumers. Is this no longer in scope? If not has it been decided that this is off the table? Or is it defined in another project? I can't see it related to the other projects you had listed in a previous email but I may be missing something. 2. In this project we are specifically dealing with the AI manifests. Later we will deal with the parser for AI and DC and other potential Caiman consumers. I am wondering... is there anything with regard to DC and AI manifests that can be normalized with regard to the common input we request from users? Maybe not in this project but wondering if this is in scope for any other project. Specific comments/questions on this functional spec: > The XML file format will contain versioning information which is > defined by the XML parsing > functional spec for the third problem statement: ?AI manifests need to > be forward and backward > compatible between builds.? This info isn't really required in this projects functional spec. Section 5.3: > A Sysmap Manifest may contain zero or more sets of criteria. So, can a sysmap manifest contain pointers to other criteria manifests? Or do all criteria in the set have to be specifically be in the same file? Section 6.1: > Derived Profiles makes configuration of each > system unique enough on the network to coexist with the other systems. It isn't clear to me what this statement means with regard to the use case it is associated with. Can you clarify? Section 6.3: > This case installs systems all systems with the same disk > configuration and packages, but I think you mean to say 'This case install all systems with the same disk configuration and packages, but... That's it for now. thanks, sarah > Hi everyone. > > Here is a link to a "functional specification" for solving the XML > parsing problem of "Current AI manifests are not easy to use." It is a > rough draft, and I'm posting it to verify that I am on the right track. > > It deals with XML problem statement 2: > > Current AI manifests are not easy to use. > > Its scope is inter-file organization of the manifests (naming, > high-level structure, inter-relatedness), which is quite a limited > scope for a functional specification. Other redesign tasks (XML and > others) will tackle the fields inside the manifests. > > Please send comments / feedback by lunchtime tomorrow. > > http://www.opensolaris.org/os/project/caiman/XML_Parsing/xml_2_func_spec.pdf > > > Thanks, > Jack > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
