Hello all, For issue http://jira.amdatu.org/jira/browse/AMDATUKSINK-2, I have created a proof of concept for the kitchensink. My new implementation uses the Amdatu management-server and the Ace launcher as the base for the kitchensink demos. This is how it works: you - start a management-server; - start an agent - run the installer (included in the kitchensink); - open http://localhost:8080/ace; - retrieve the bundles; - drag the desired demo onto the target; - store and retrieve the changes. After having done this, you'll find that the demo bundles are provisioned on the management agent and are running on your machine. Currently, this all runs local and can easily be rewritten to run with an external server. This basic implementation has the bundles included in the kitchensink demo-installer, but another option is to provide (instead of all the bundles) a single file in the installer download. This makes the download way smaller. The installer would than locate and download the bundles using the information in the file, which is either a list of all required bundles, or simply the location of some repository with all the bundles. This would provide imho a very tiny solution to the kitchensink/demo problem.
My question to you: is this an acceptable solution? Could you think of any other solution which might prove better than this one? Is there anything on the current design that is flawed, or could you think of any improvements on this? I'd like to do this in the best way possible, so feel free to discuss this and propose cool things. My implementation can be found here: https://bitbucket.org/mhendriks91/amdatu-kitchensink/changesets/tip/provisioning Thanks, Matthijs
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
