Hi, before proceeding with the schema mount draft, we need to clarify the concept of "inline" mount because it causes a lot of confusion, and the current text (in sec. 3.2) clearly doesn't work for NMDA. I believe there are some hidden assumptions about how it is supposed to work that have to be made explicit.
In particular, the inline mount seems to require that an instance of the mount point plus YANG library data be placed in <operational> as a side effect of creating the corresponding mount point instance in any datastore. Perhaps it would be possible to approach it from the opposite direction and start with creating the necessary data in <operational> as a result of an explicit mount event. For example, when provisioning a new VM instance, the server would "mount" the following data in <operational>: - the mount pount instance - the YLbis data that defines the mounted schema for all datastores - any other state data that are needed. The above step basically creates a new system-controlled resource that can be configured after that in the same way as other system-controlled resources such as physical interfaces. The advantage of this approach is that we needn't speculate about whether and when the embedded YL data magically appears in <operational> - it is the mount event that does exactly this, and only after that the mounted resource can be configured. This concept would also be more alike to the mount operation known from Unix filesystems. Comments? Lada -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
