On 08/ 5/10 04:23 PM, Karen Tung wrote:
Hi Jean,

I have further comments on 2 more items below.

On 08/05/10 09:19, jean.mccormack wrote:




- How will all the targets in TI be created? By using the existing libti.so?
Or create all the targets directly using Python?
If we do use libti.so it will be through ctypes but the plan is to create all the targets using Python.
OK. In this case, then, I think it would be useful to discuss how you are planning to go about creating the targets using Python. Are you going to call
commands via Python, or are you going to use some Python APIs
from some components? If I remember correctly, ZFS has some Python interfaces.
Whatever you decide to do, I think it should be documented.

We both think this is an implementation detail and shouldn't be in a design doc.
Personally, I don't think of this as an implementation detail. Whether Python will be calling a command or some other Python API provided by another project are all
imported interfaces, and I think they should be listed in the design doc.

After talking with you on the phone I understand more what you want. We'll put in the doc the info that as to what projects we'll be using (fdisk, zfs etc) and what type of interfaces we
are expecting to use (cli, python).






* Section 8.2:
- It's not clear to me where these destroy data object and create data object
live in the DOC tree?
The live in the checkpoint node for TI.
The checkpoint node for TI... When will the checkpoint node for TI be created, and
who creates that?

The application creates all checkpoint nodes, right?

I guess that depends on the application. I don't see why an application need to create any checkpoint nodes. Are you saying that in order to pass in the the tree of objects for TI to create, an application is required to create the TI checkpoint node?

Yes. I believe we agreed on the phone that the application would be creating a DOC node with the create
object in it to pass to TI.

Thanks,
Jean

Thanks,

--Karen

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to