Hi All, Attached is a list of notes, and questions, that I came up with for Slim with regard to the changes required in the Orchestrator to support the new TI and Transfer modules. Plus some additional stuff we need to handle somehow. Hopefully they are not too cryptic. If they are, ask questions. I tried to think of all the changes required for the orchestrator to support slim but certainly may have missed some things. I am hoping Sundar will review this list and let me know. Jan and Moinak.. there are questions for you in this doc as well.
In terms of Orchestrator changes, the biggest issue that we have is that we need to have the api's to plug in to for the TI and Transfer services to get the changes made, and then tested. We need to clearly understand the api's we will be using. So, based on Jan's estimate of 2 weeks, and Moinak's of 3, we cannot really start too much of the orchestrator, except perhaps stubbing in the calls, for at least 2 weeks. Testing and validation requires working subordinate services. I need some data on the Transfer service in particular at this point. And,I need more data on the TI design. I would estimate 2 weeks for changes to orchestrator. I do think that TI needs more than 2 weeks based on additional callback support that must be added. We need to handle post install tasks as well, which will require about a weeks worth of work. Just so folks know we have additional work to add to the schedule. Please review, answer questions, ask questions. Regards, sarah -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: orchnotes.txt URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20070921/9719e042/attachment.txt>
