Virginia Wray wrote: > Hi - > > I've been thinking about requirements for the mechanism that will > transfer the automated installation, i.e. the manifest, the zlib > files, etc, basically any data that must be transferred to the client > before the installation of the OS bits occurs. > > I've gotten a bit of insight into some of the requirements we should > be thinking about, such as, making the mechanism modular for users to > be able to implement the protocol of their choice, and the need for > secure transfer. I would like > to solicit input from the community, as well as an redesign projects > that think they could be consumers of the transfer mechanism, for > additional requirements that we should be thinking about for the > redesign.
At this point in the derived profiles work, I don't have enough data about how we're going to precede design wise to give you any solid requirements yet. In the worse case scenarios: - there may be scripting that has to run on the server on behalf of the client (this may have impact on your webserver choice for the webserver implementation of the transfer mechanism). - there may be more than just the manifest file being flung across from server to client (on the order of more files) - there may be more data (the attributes about the client, such as MAC address, platform, etc) sent from client to server than there currently is today thanks, -ethan
