On 05/11/09 12:19, Dave Miner wrote: > Susan Sohn wrote: >> Below are the notes generated from the service redesign meeting >> yesterday, >> May 6. In addition, I've added what I consider to be the use cases we'd >> like to address. >> >> Please provide feedback and comments. >> >> Thanks, >> Sue >> >> >> User problem to solve: >> Ensure that an AI client can deterministically be installed with the >> same boot >> image in a repeatable, consistent way, without client specific setup. >> > > I'm not sure why the term "the same" is used above. Would not "a > predictable" be more accurate? And please define what you mean by a > "boot image". I would assume the goal is to install the client with a > specific configuration, in terms of software and associated > configuration metadata, and I'm not sure how a "boot image" relates to > that.
Yea, predictable would be more accurate here. By boot image, I mean the image that contains the automated installer tools as well as the kernel that the client boots from. In our meeting today, we discussed decoupling the boot image from the "service", but we do want the automated installer that runs on the client to be compatible with the manifest and to support what the manifest designates. We need to walk through use cases and see if the decoupling is the right thing to do. >> Why can't we do this today? >> 1. Client may not always get image of same architecture. >> 2. Client may not always get same service every time it is booted. >> >> What use cases do we want to address? >> 1. Small office environment, homogeneous setup (clients either all x86 >> or all >> SPARC), the server and clients are in the same subnet, OpenSolaris >> needs to be >> installed on the first disk of each client. >> 2. Large company with 200 clients, roughly half x86 and half SPARC. >> The same >> version of OpenSolaris needs to be installed on each set of systems. >> 3. Same as #2, except that a few clients need to be installed with >> something >> different. >> 4. Lab environment with 40 x86 clients, where 20 need OpenSolaris v1, >> 15 need >> OpenSolaris v2 and 5 need OpenSolaris v3. >> >> Notes/Questions: >> 1. Need to come up with definition of install service. >> 2. In original design, service discovery was considered a major >> feature. It is >> not being used. Do we still need it? Would using it conflict with our >> goal of >> having a repeatable, consistent client install? >> 3. Consistent behavior needs more thought - how do we advertise and >> get services? >> 4. What should overall experience be with respect to remote servers? >> 5. User experiences should be scalable. >> 6. Investigate idea of default service. >> 7. Could a single service serve both x86 and SPARC clients? >> > > I suppose #5 might be meaning this, but statements of goals around > usability and observability seem to be lacking. Thanks - will add that. Sue > Dave
