On May 29, 2012, at 9:44 AM, Matthijs Hendriks wrote: > 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.
If the download is only smaller because it later downloads bundles anyway, I think that is of little value. We can configure the AMS to use a remote OBR, but where would we host it and how would we do access control to it? There are plans to extend ACE to be able to use multiple OBRs (and then probably also read-only OBRs) but that does not work out of the box yet. One suggestion that could make things easier is to provide users with some initial content for the AMS. When configuring the internal repositories (shop, deployment, target, ...) one can provide some initial content. The user repository actually does that to provide a set of default users. We could already store our bundles in the "store" folder, and define artifacts, features and distributions for our various demos. That way, users could simply start the AMS, "retrieve" the initial content and associate the distribution of choice to their target(s). Greetings, Marcel
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
