commit | 7382fc876836f812368697cb365da57ce28f572d | [log] [tgz] |
---|---|---|
author | Matthieu Morel <mmorel@apache.org> | Fri Nov 11 19:09:18 2011 +0100 |
committer | Matthieu Morel <mmorel@apache.org> | Mon Jan 09 15:49:49 2012 +0100 |
tree | dfb19dc6e57d8d640d5576ccff4acb2f42c0adbf | |
parent | 25c379f2c29c509d6892146636cb124ad4dd53b7 [diff] |
S4-24 dynamic app deployment - triggerable through zookeeper - S4R downloadable from a file system or a web server - minor updates to ZNRecord (consistency with map semantics) - added a CustomModule that can be passed when bootstrapping an S4 node, in order to start an S4 node with Zookeeper cluster management and the distributed deployment manager - support for fetching S4R files through http - also some improvements / fixes to the deployment manager (feedback from Kishore) - added test for deployment of multiple apps - Tests that classes with same signature are loaded in different class loaders (through the S4RLoader), even when referenced through reflection, and even when referencing classes present in the classpath of the S4 node - test applications are in a separate folder test-apps - each test application has its packaging script (NOTE : should be factored out) - test apps are built and deployed automatically during the deployment tests - propagate thread interruption during initial deployment
The goal of this project is to incorporate feedback from various users and create a prototype with a cleaner, simpler API. The base classes are the foundation on top of which higher level layers and tools can be built. For example, one could write a domain specific language to create the application graph. Look at this as the foundation and not as the end product.
Here is a list of ideas:
Please post feedback and suggestions in the s4 forum.
The repo is here:
https://github.com/leoneu/s4-piper
In this version:
Note that when we create a PE in App, we are really creating a prototype of the PE. The actual PE instances get created every time a node receives an event that is dispatched to a specific PE prototype. The first PE has Map that holds the instances by a specific key. PE instances are clones which means that we don't call the constructor. Instead we provide an init method. Also, the instance variables are cloned. This means that references are also copied. If you wanted to have a List per PE instance, you would have to create it in the init method. This design pattern, makes thing very simple and efficient but has the downside that programmers have to understand how instances are created via clone.
For now we identify PEs using a composite string produced by KeyFinder. We must also pass the raw data types used to create the composite key. Need to think how to do this with type safety in mind.
Examples: