Hi All, I have updated the page with the students we have so far and also listed possible mentors. Can the prospective mentors review the projects list add/modify their preferences?
Regards, Rajith On Mon, Mar 31, 2008 at 11:30 AM, <[EMAIL PROTECTED]> wrote: > Page Edited : qpid <http://cwiki.apache.org/confluence/display/qpid> : > GSoC <http://cwiki.apache.org/confluence/display/qpid/GSoC> > > GSoC <http://cwiki.apache.org/confluence/display/qpid/GSoC> has been > edited by Rajith > Attapattu<http://cwiki.apache.org/confluence/display/%7Erajith> (Mar > 31, 2008). > > (View > changes)<http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=81314&originalVersion=1&revisedVersion=2> > Content: > GSoC Projects and who is doing what: Qpid Demo - two projects (one for > AMQP 0-9 and one for AMQP 0-10) > > Candidates: Senaka Fernando, Buddika Laknath > > Project Goal: Create a multi language Demo for Qpid, and use the demo as > source to create the Qpid getting Started pages > > Mentor: Carl/Rajith > > Project Description: > > The Qpid project likes to have an enterprise grade demo that reflects the > messaging capabilities of the AMQP (www.amqp.org) protocol that uses > brokers written in Java and C++ and the clients written in Java/JMS, c++, > python, ruby, .NET > > The Demo ca use any client server problem (like bank, stock, render farm, > travel site etc) to illustrate the capabilities of the Qpid. > AMQP mgmt Bridge - JMX > > Candidates: Le Duc Bao,Lahiru Gunathilaka > > Project Goal: Create a dynamic bridge from AMQP-mgmt protocol to JMX to > facilitate std management console integration > > Mentor: Marnie/Aidan/Arnaud ? > > Project Description: > > Project is to create a process will receive management Data through the > AMQP mgmt protocol and translate those into JMX. This will allow the C++ > broker to also be hooked into a JMX allow for all the instrumentation data > to be read from JMX, all the methods to be invoked, and the configuration to > be updated through standard JMX consoles. > > Note that all the schema is dynamic, so the bridge need to configure > itself at runtime, so this service should derive it's behavior from the > schema provided to it. > > AMQP mgmt side protocol can be found here: > http://cwiki.apache.org/qpid/management-design-notes.html > > To play with it, build the C++ broker > ./bootstrap > ./configure > make > > on linux, the to run the cmd line mgmt set the PYTHONPATH and run it from > mgnt-cli > > You should pretty quickly see how the objects get dynamically build and > how they are layed out, these can then quite simple be dynamically mapped to > JMX. > > Implementation language is Java > AMQP mgmt Bridge - WS-DM > > Candidates: Rahul Metha > > Project Goal: Create a dynamic bridge from AMQP-mgmt protocol to JMX to > facilitate std management console integration > > Mentor: Arnaud > > Project Description: > > Project is to create a process will receive management Data through the > AMQP mgmt protocol and translate those into WS-DM This will allow the C++ > broker to also be hooked into any WS-DM console and allow for all the > instrumentation data to be read, all the methods to be invoked, and the > configuration to be updated through standard WS-DM console like BMC, Tivoli, > etc. > > Note that all the schema is dynamic, so the bridge need to configure > itself at runtime, so this service should derive it's behavior from the > schema provided to it. > > AMQP mgmt side protocol can be found here: > http://cwiki.apache.org/qpid/management-design-notes.html > > To play with it, build the C++ broker > ./bootstrap > ./configure > make > > on linux, the to run the cmd line mgmt set the PYTHONPATH and run it from > mgnt-cli > > You should pretty quickly see how the objects get dynamically build and > how they are layed out, these can then quite simple be dynamically mapped > into the WS-DM intefaces. > > Implementation language is the choice of the implementor (suggested > languages are Python or Java) > JMX Cli > > Candidates: Lahiru Gunathilaka > > Project Goal: Provide the ability to access Java Broker mgmt info from cmd > line. > > Secondary Goal: Integrate with AMQP mgnt protocol ?? > > Mentor: Adian/Marnie/Martin > > Project Description: > > Design and implement a simple solution, runnable from the command line, > for extracting useful JMX information from the Qpid Java Broker. Solution > should be configurable at runtime to allow users to decide which bits of > info they're interested in and when. Might be nice to see the information > extracted in a report format > Qpid-java-broker-config > > Candidates: Sachith Danushka. > > Project Goal: Rationalize the configuration in the Java Broker to get it > more consistent > > Mentor: Adian/Marnie/Martin > > Project Description: > > Refactor Qpid Java Broker configuration into a more elegant xml schema, > with xsd, covering all existing configuration options and allowing for > extension. Additionally implement a module to validate broker configuration > files, which could be run standalone i.e. before starting a broker, to > check that they're well formed and validate against the xsd. > > Powered by Atlassian > Confluence<http://www.atlassian.com/software/confluence/default.jsp?clicked=footer>(Version: > 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature > request<http://jira.atlassian.com/secure/BrowseProject.jspa?id=10470> > > Unsubscribe or edit your notifications > preferences<http://cwiki.apache.org/confluence/users/viewnotifications.action> > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
