Hi list, over the last weeks we have been working on a revised Provisioning model for Amdatu Platform 1.0. This included (partially offline) discussions on what we will and wont cover as well as how we will implement it. In a nutshell, we will cover software/configuration provisioning and use Apache ACE as our software provisioning engine with an off the shell UI and fully manageable trough REST interfaces. The results are covered in the pages listed below providing an architectural overview [0][1], requirements [2], use-cases [3] and a more detailed design[4].
Note that there is also a still rather empty scenarios page [5] that is intended to describe some possible high level use cases and map them to the solution. This is work inn progress and feel free to add a scenario that you would like to see so we can discuss it. This is not the end and it is not a done deal as over the next couple of weeks we will spend some more iterations to refine, implement and proof the model. Therefore at this point we would very much appreciate feedback from the community and specifically anyone interested in Provisioning. Do you feel requirements and use cases cover your needs? Do the design and proposed implementation make sense? Any feedback will be most valuable to our end goal, which is to come up with a stable future proof model for 1.0! Thanks and greetz, Bram [0] http://www.amdatu.org/confluence/display/Amdatu/Provisioning [1] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Provisioning [2] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Provisioning+Requirements [3] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Provisioning+Use+Cases [4] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Provisioning+Design [5] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Provisioning+Scenarios _______________________________________________ Amdatu-users mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-users
