On 02/14/11 04:39 PM, Ethan Quach wrote:
All,
I have uploaded the design document for AI Zones support into the
caiman-docs gate.
http://src.opensolaris.org/source/xref/caiman/caiman-docs/AI/AI_Zones_Design.odt
Ethan, comments below.
5.1.2: Several questions here:
- The configuration source must contain exactly these files and no
others? Is it permissible to tar/zip/<other archive format> them
together for convenience of the user managing them?
- Shouldn't we suggest/configure an area in the AI Apache instance to
hold these by default?
- I would think that the definition of the default AI manifest for zones
would be part of this document?
- I'm confused as to why we provide sysidcfg support for S10 branded
zones. How would a branded zone possibly appear in a situation where
AI's transport of the configuration would be useful?
5.1.3.1.1: The examples provided here could stand to be more complete;
i.e. tying an input file to a corresponding output file so the reader
can grok what AI can expect a bit better.
5.2: Does this mean that the system/install/auto-install package will
become a dependency of system/zones?
5.2.1: I would think the relaxed form would be more useful in allowing
reuse of AI manifests across global and non-global zones. What's the
advantage of making this tight initially?
5.2.2.1: re: com.oracle.libbe:nbe_handle - I thought I had asked that
the BE properties remain in the org.opensolaris namespace rather than
have this mixed set.
5.2.4: s.var/run.system/volatile.
6.2: Why is -Z Private (which isn't specific enough, anyway; it would
have to be qualified, proably as Oracle Private were we to go this route).
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
