Simon Jakesch ([email protected]) wrote:
> Everyone,
>
> for tomorrow's design meeting, we will discuss various topic around
> Crowbar 2.0. The detailed topics are documented and available at
> http://www.fileswap.com/dl/H4seAxa4o/.
Thanks - greatly appreciate the effort that went into writing this
document and sharing thoughts on it in the call earlier. Brief
feedback follows (with the caveat that my understanding of the area is
still fairly shallow relative to those of you who have been working
closely on this design and code for a long time!)
- I'm either in favour of most numbered points in the document (very
strongly in the case of 1. and 2.), and unable to comment (through
lack of understanding) on the others. IOW, I don't disagree with
any of them.
- It would be *much* easier to understand the design if some
fictitious "real world" scenarios were mapped out as examples
showcasing how this model would handle them.
- Not yet convinced we need to number states as in point 1., but
am interested to hear arguments for.
- I'd like to see some examples of how dependencies on networking
roles would be expressed. In particular do we want to allow
policy- or constraint-based resolution of network dependencies
based on the characteristics of the network resource(s) available
(e.g. speed, redundancy etc.) ? Or is that overkill?
- How do we handle removal of nodes from roles?
Also, one minor point on process: I'd prefer that design documents
were shared either as an etherpad, wiki page, or plain-text email.
Read-only PDF is not too conducive to collaboration ;-)
Thanks again!
Adam
_______________________________________________
Crowbar mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
