In terms of the CORS pattern, I think it's just pattern matching the origin headers (i.e. Origin with Access-Control-Allow-Origin), so if you can make it configurable, that would be good.
If it simplifies your implementation and resolves the XSS issues, you can co-deploy helix-admin-webapp with your dashboard (along with any components other than helix controller or helix participant). Other than that, I don't have any specific suggestions as I'm not an expert in this. Kanak Date: Tue, 22 Jul 2014 08:26:31 +0530 Subject: Re: [GSOC] Current Status From: ayolajayamah...@gmail.com To: dev@helix.apache.org; kana...@hotmail.com Hi All, Currently I'm going through Charting with regard to UI components. Also I'm looking where to put the headers to enable CORS. I'm writing a simple Restlet and removing cross domain issue in that. Any suggestions? I'm going through AngularJS and writing some blog posts with regard to charting and Restlet. http://ayolajayamaha.blogspot.com/2014/07/restlet.html http://ayolajayamaha.blogspot.com/2014/07/angularjs-charts.html http://ayolajayamaha.blogspot.com/2014/07/angularjs-pie-charts.html http://ayolajayamaha.blogspot.com/2014/07/angularjs-line-charts.html On 27 June 2014 18:00, Ayola Jayamaha <ayolajayamah...@gmail.com> wrote: Hi, I have added theme (css) for plugin screen shoot[2] with data[3] is attaching. Clean pom file[4] with setting up properties and dependencies. later we can move those parent pom, set the parent pom.This will build as successful and sample-1.5-SNAPSHOT.war file can be host any web server. (I am using tomcat) Helix dashboard looks with themes Helix dashboard with Helix rest details Here I am sharing 'gist' that I used for hawtio dashboard install[1] (dashboard json).Now we have initial hawtio plugin for Helix[4]. If any thing is not clear please let me know Thanks [1] https://gist.github.com/AyolaJayamaha/f54d3178516e8c4875b7 [2] https://docs.google.com/file/d/0ByWGexlJqMwbTVNBSC1nM09ON1U/edit?pli=1[3] https://drive.google.com/file/d/0ByWGexlJqMwbWGZDRENXaV9obm8/edit?usp=sharing [4] https://github.com/AyolaJayamaha/helix/tree/master/helix-dashboard On 26 June 2014 17:02, Ayola Jayamaha <ayolajayamah...@gmail.com> wrote: On 26 June 2014 10:07, Ayola Jayamaha <ayolajayamah...@gmail.com> wrote: Hi, 1. I have updated the Mock UI document as the feedback given by my mentor. https://docs.google.com/document/d/177-drFSIBOh_aln25v-gpka9TNW8TFmJifLRdVptxz8/edit?usp=sharing > Is the portal on the document address the needs mentioned? 2. The steps I followed next are the transitions from Mock UI ---> Static HTML ----->Angular Module >http://ayolajayamaha.blogspot.com/2014/06/simple-ui-with-angularjs.html The sample UI is not the final version. It would be \ improved graphical wise in the final versions. The given UI is the structure of the interface showing all the details that will be given to users. ui33.png ui11.png ui22.png ui49.png ui9.png ---> hawtio plugin plugin.png js.png As you can see in the screenshots you can find the plugin in github. https://github.com/AyolaJayamaha/helix/tree/master/helix-dashboard You can get clone and build the dashboard. But some configurations in hawtio dashboard has to be done manually. I plan to automate it in the future. Note: I used a mock rest service since the Cross Domain Issue. To enable CORS we need to add the following headers to the response. responseHeaders.add("Access-Control-Allow-Origin", "*"); responseHeaders.add("Access-Control-Allow-Methods", "POST,OPTIONS"); responseHeaders.add("Access-Control-Allow-Headers", "Content-Type"); responseHeaders.add("Access-Control-Allow-Credentials", "false"); responseHeaders.add("Access-Control-Max-Age", "60"); In building war file, the plugin will be added to .war file. But current plugin needs to be installed to hawtio manually. On 20 June 2014 21:31, Ayola Jayamaha <ayolajayamah...@gmail.com> wrote: Hi, Thanks for the comments. I will make necessary changes and update the document. On 20 June 2014 02:41, Kanak Biscuitwala <kana...@hotmail.com> wrote: Hi Ayola, Looks good so far. I have some comments about your mockups: 1. Enabling/disabling a cluster and enabling/disabling the controller are actually the same thing. What is missing is "activateCluster." activateCluster is useful when you have a cluster of controllers, and you want those controllers to manage other clusters. The controller cluster is called the "grand cluster." 2. Resources are added to cluster upon creation and cannot be moved or added to other clusters afterwards. Thus, the "add to cluster" on existing resources doesn't make sense. The resources screen should allow enable/disable, read external view, read/write configs and read/write ideal state. There should also be an "add resource" button on the clusters page. 3. Same comment for instances. There should be an "add instance" button on the cluster pages, and on the instance page it should allow read current state, read messages, read/write configs. 4. There's a separate page for all configs, but it may make sense to integrate them into the configs at each scope (i.e. cluster, resource, participant). 5. There should be a button on the clusters page for adding a state model definition. I think the overall comment is that the clusters page needs to be a portal for the rest of the dashboard, so there should be a link to all the cluster pages, and within a cluster page, there should be ways to access all the resources, instances, configs, and constraints for that cluster. Kanak ---------------------------------------- > Date: Thu, 19 Jun 2014 22:23:01 +0530 > Subject: Re: [GSOC] Current Status > From: ayolajayamah...@gmail.com > To: dev@helix.apache.org; kana...@hotmail.com > > Hi, > Below is the Mock UIs for Apache Helix. The UIs will be created with hawtio > dashboard. A .war file can be used to deploy on any server as a separate > module. The UIs get data from the REST API. This is just initial one. They > will be developed as Angular plugin. Towards the end I will provide some > chart as well for cluster management. > Presently I'm doing the hawtio and helix integration and towards next week > I'm writing some angularjs plugins. > > https://docs.google.com/document/d/177-drFSIBOh_aln25v-gpka9TNW8TFmJifLRdVptxz8/edit?usp=sharing > Thank you. > > > On 19 June 2014 13:14, Ayola Jayamaha <ayolajayamah...@gmail.com> wrote: > >> >> >> >> On 19 June 2014 01:38, Kanak Biscuitwala <kana...@hotmail.com> wrote: >> >>> Local deployment is fine. >> >>> >> >>> Here is the git repo that I will be using, later I will share Git >>> location (Angular plugin) that can be used in dashboard of hawtio. I will >>> blog on those as well. >>> >>> >> >> >>> The main thing we would like you to deliver is the package so that it is >>> available for anyone to deploy within their own cluster. >> >>> >> Sure, >> helix-dashboard[2] module will build 'sample-1.5-SNAPSHOT.war' with helix >> dashboard. This war can be host any server (tomcat etc.. ) by anyone with >> helix rest web app (own cluster). >> I just found[1] function 'start()' line 43. I too can follow that model >> even. >> >> Therefore finally you will have web app as 'helix-admin-webapp' that can >> be deployed within their own cluster. >> >> [1] >> https://github.com/AyolaJayamaha/helix/blob/master/helix-admin-webapp/src/main/java/org/apache/helix/webapp/HelixAdminWebApp.java >> [2] https://github.com/AyolaJayamaha/helix/tree/master/helix-dashboard >> >> >>> >>> Kanak >>> >>> ---------------------------------------- >>>> Date: Wed, 18 Jun 2014 22:30:43 +0530 >>>> Subject: Re: [GSOC] Current Status >>>> From: ayolajayamah...@gmail.com >>>> To: kana...@hotmail.com >>>> CC: dev@helix.apache.org >>>> >>>> Hi, >>>> Currently I'm creating mock UIs, helix and hawt.io integration as >>> module >>>> and plugins with angularjs in hawtio dashboard. >>>> Upto now I'm almost created the mock UIs. And in helix and hawtio >>>> integration where should I create the headers to cater for the cross >>> domain >>>> issue and if I'm deploying the .war file where can I deploy it? >>>> For the time being the code is in my local machine. I will commit to >>> repo >>>> tomorrow and share with you. But it is still in initial phase. >>>> >>>> >>>> On 18 June 2014 09:53, Kanak Biscuitwala <kana...@hotmail.com> wrote: >>>> >>>>> Sounds reasonable. Is your current code available in a public >>> repository? >>>>> I would be interested in taking a look if it is. >>>>> >>>>> Kanak >>>>> >>>>> ________________________________ >>>>>> Date: Wed, 18 Jun 2014 09:31:40 +0530 >>>>>> Subject: Re: [GSOC] Current Status >>>>>> From: ayolajayamah...@gmail.com >>>>>> To: dev@helix.apache.org; kana...@hotmail.com >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> In Hawt.io, from a plugin developer's perspective a plugin is just a >>>>>> set of resources; usually at least one JavaScript file. For all the >>>>>> plugins in hawt.io<http://hawt.io> done so far they have picked >>>>>> AngularJS as the UI framework, which has a nice two-way binding >>>>>> between the HTML markup and the JS data model along with >>>>>> modularization, web directives and dependency injection. These >>>>>> AngularJS modules can be added and removed at runtime inside the same >>>>>> single page application without requiring a reload. I will be using >>>>>> AngularJS Directives[2] and angular UI. Finally we will have Plugins >>> in >>>>>> Hawt.io (Collection of AngularJS modules) >>>>>> >>>>>> In my approach I will build pluggins from AngularJS (plug can be just >>>>>> js file or js files) that will use $http to call rest API in helix. >>>>>> Final Helix Plugin in Hawt.io (Helix dashboard) will use all those >>>>>> AngularJS that I am building now. >>>>>> >>>>>> >>>>>> >>>>>> Those AngularJS (js and html file) store in separate modules in helix >>>>>> and we can use a maven WAR project and add the hawtio-web WAR >>>>>> dependency and use the maven war plugin we can then add my develop >>>>>> plugins into the war. This module will create .war file and can be >>>>>> deploy as web app (dashboard) in Helix (rest admin web application is >>>>>> running) >>>>>> >>>>>> >>>>>> >>>>>> [1] http://hawt.io/plugins/howPluginsWork.html >>>>>> >>>>>> [2] http://hawt.io/developers/directives.html >>>>>> >>>>>> [3] http://hawt.io/plugins/index.html >>>>>> >>>>>> >>>>>> On 12 June 2014 22:44, Kanak Biscuitwala >>>>>> <kana...@hotmail.com<mailto:kana...@hotmail.com>> wrote: >>>>>> +1 feel free to use whatever approach is easier >>>>>> >>>>>> ---------------------------------------- >>>>>>> Date: Thu, 12 Jun 2014 10:07:36 -0700 >>>>>>> Subject: Re: [GSOC] Current Status >>>>>>> From: g.kish...@gmail.com<mailto:g.kish...@gmail.com> >>>>>>> To: dev@helix.apache.org<mailto:dev@helix.apache.org> >>>>>>> CC: kana...@hotmail.com<mailto:kana...@hotmail.com> >>>>>>> >>>>>>> I think it should be ok to either have helix-dashboard module to >>>>> generate >>>>>>> the war or merge into helix-admin-webapp. We can probably start with >>>>>>> helix-dashboard first and then merge it into helix-admin-webapp >>> later. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 12, 2014 at 9:55 AM, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> If we start two server in different ports Since hawtio dashboard >>> will >>>>> use >>>>>>>> Helix REST API there can be a CROS domain issue.As we discussed, >>>>> desperate >>>>>>>> module (eg: Helix-dashboard) will create Hawt.io dashboard as web >>>>>>>> application and it will be 'war' file, that can be deploy. >>>>>>>> Is it possible to deploy dashboard war file in helix? >>>>>>>> (I think helix rest API (helix-admin-webapp) is also deployed as web >>>>> app, >>>>>>>> am I correct) so can we use same server to deploy dashboard? >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> >>>>>>>> On 27 May 2014 06:12, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> You can find all of the REST API URLs on: >>>>>>>>> http://ayolajayamaha.blogspot.com/2014/05/rest-api-further.html >>>>>>>>> >>>>>>>>> >>>>>>>>> On 27 May 2014 05:44, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>>> From: Kanak Biscuitwala >>>>>> <kana...@hotmail.com<mailto:kana...@hotmail.com>> >>>>>>>>>> Date: 26 May 2014 23:00 >>>>>>>>>> Subject: RE: [GSOC] Current Status >>>>>>>>>> To: "dev@helix.apache.org<mailto:dev@helix.apache.org>" >>>>>> <dev@helix.apache.org<mailto:dev@helix.apache.org>> >>>>>>>>>> Cc: >>>>>> "d...@helix.incubator.apache.org<mailto:d...@helix.incubator.apache.org >>>>" >>>>>> <d...@helix.incubator.apache.org<mailto:d...@helix.incubator.apache.org >>>>>, >>>>>>>>>> kishore g <g.kish...@gmail.com<mailto:g.kish...@gmail.com>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Yes everything is implemented in Java at the lowest level. The >>>>> command >>>>>>>>>> line API is implemented in ClusterSetup.java. >>>>>>>>>> >>>>>>>>>> ---------------------------------------- >>>>>>>>>>> Date: Mon, 26 May 2014 12:55:45 +0530 >>>>>>>>>>> Subject: Re: [GSOC] Current Status >>>>>>>>>>> From: ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com >>>> >>>>>>>>>>> To: dev@helix.apache.org<mailto:dev@helix.apache.org>; >>>>>> kana...@hotmail.com<mailto:kana...@hotmail.com> >>>>>>>>>>> CC: >>>>>> d...@helix.incubator.apache.org<mailto:d...@helix.incubator.apache.org >>>>; >>>>>> g.kish...@gmail.com<mailto:g.kish...@gmail.com> >>>>>>>>>>> >>>>>>>>>>> Thanks Kanak. >>>>>>>>>>> >>>>>>>>>>> I too noticed from RestAdminApplication[1],I think it covers all >>> of >>>>>>>> the >>>>>>>>>>> REST API of HELIX. >>>>>>>>>>> Is Commmand line api also implemented using java API? Therefore >>> is >>>>>>>> java >>>>>>>>>> API >>>>>>>>>>> the main top interface? >>>>>>>>>>> >>>>>>>>>>> Your ideas and suggestions are deeply appreciated and valued. >>>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> References: >>>>>>>>>>> [1 >>>>>>>>>>> ] >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>> https://github.com/apache/helix/blob/master/helix-admin-webapp/src/main/java/org/apache/helix/webapp/RestAdminApplication.java >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 10 May 2014 08:54, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> >>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Installing hawtio dashboard and building it from source code. >>>>>>>>>>>> >>>>>>>>>> >>>>> >>> http://ayolajayamaha.blogspot.com/2014/05/running-hawtio-dashboard.html >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 5 May 2014 09:30, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> >>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Steps followed in checking REST API >>>>>>>>>>>>> http://ayolajayamaha.blogspot.com/2014/05/helix-rest-api.html >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 3 May 2014 12:21, Ayola Jayamaha >>>>>> <ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com>> >>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks Jason for the instructions. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I will follow the steps that you have given. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 3 May 2014 04:24, Zhen Zhang >>>>>> <nehzgn...@gmail.com<mailto:nehzgn...@gmail.com>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Ayola, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks for the update. To test/check the rest API, you can >>> start >>>>>>>>>>>>>>> Helix-rest-admin when you are running the Helix example in >>> quick >>>>>>>>>> start. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>> $HELIX_HOME/helix-admin-webapp/target/helix-admin-webapp-pkg/bin/run-rest-admin.sh >>>>>>>>>>>>>>> usage: java org.apache.helix.webapp.RestAdminApplication >>>>>>>>>>>>>>> --help Prints command-line >>>>>>>>>>>>>>> options info >>>>>>>>>>>>>>> --port <web service port, default: 8100> Provide web service >>>>>>>>>>>>>>> port >>>>>>>>>>>>>>> --zkSvr <ZookeeperServerAddress(Required)> Provide zookeeper >>>>>>>>>>>>>>> address >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It asks for a http port (default 8100) and the zkAddress >>> (e.g. >>>>>>>>>>>>>>> localhost:2199). After you start Helix-rest-admin, you can >>> use >>>>> the >>>>>>>>>> rest >>>>>>>>>>>>>>> api: >>>>>>>>>>>>>>> >>>>> http://helix.apache.org/0.6.2-incubating-docs/tutorial_admin.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Jason >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, May 2, 2014 at 5:53 AM, Ayola Jayamaha < >>>>>>>>>>>>>>> ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com >>>>>>>wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I was able to build helix from the source code with out >>> test (I >>>>>>>> got >>>>>>>>>>>>>>> some >>>>>>>>>>>>>>>> test failures in TestZKUtil>ZkUnitTestBase.afterTest:93 >>> there >>>>>>>> fore >>>>>>>>>> I >>>>>>>>>>>>>>> skip >>>>>>>>>>>>>>>> the test in helix building). I have started blog on those >>> task, >>>>>>>>>> Think >>>>>>>>>>>>>>> it is >>>>>>>>>>>>>>>> OK with helix Developers? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Helix build with out test was success[1]. >>>>>>>>>>>>>>>> I try out helix admin API with helix sample ('Quick >>> start')[2] >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> How can I test/check the rest API sample or tutorial >>>>>>>>>>>>>>>> Currently I'm looking at hawtio dashboard samples. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>> http://ayolajayamaha.blogspot.com/2014/03/build-helix-from-source-code.html >>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>> http://ayolajayamaha.blogspot.com/2014/05/how-to-run-helix-example-from-source.html >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 25 April 2014 22:56, Kanak Biscuitwala >>>>>> <kana...@hotmail.com<mailto:kana...@hotmail.com>> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This is a good time to make sure you can run get started >>> with >>>>>>>>>> Helix >>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>> can successfully build it. As you go along, we will be >>>>> available >>>>>>>>>> to >>>>>>>>>>>>>>>> answer >>>>>>>>>>>>>>>>> questions about the Helix codebase, architecture, the issue >>>>>>>>>>>>>>>>> tracking/communication/code review processes, and so on. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Your plan sounds reasonable. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Kanak >>>>>>>>>>>>>>>>> ________________________________ >>>>>>>>>>>>>>>>>> Date: Fri, 25 Apr 2014 22:32:25 +0530 >>>>>>>>>>>>>>>>>> Subject: [GSOC] Current Status >>>>>>>>>>>>>>>>>> From: >>>>>> ayolajayamah...@gmail.com<mailto:ayolajayamah...@gmail.com> >>>>>>>>>>>>>>>>>> To: kana...@hotmail.com<mailto:kana...@hotmail.com> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks and I accept all your support to achieve it >>>>>>>> successfully. >>>>>>>>>>>>>>> Since >>>>>>>>>>>>>>>>>> this is my first gsoc project. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> What is the best thing to do on this phase of gsoc? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Plan to do on this phase (2 weeks time) >>>>>>>>>>>>>>>>>> - helix api try out mainly for dashboard >>>>>>>>>>>>>>>>>> -hawito dashboard samples in other product >>>>>>>>>>>>>>>>>> - understanding and finding the best approach to helix >>>>>>>> dashboard >>>>>>>>>>>>>>>>>> [https://mail.google.com/mail/u/0/images/cleardot.gif] >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Best Regards, >>>>>>>>>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Best Regards, >>>>>>>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Best Regards, >>>>>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Best Regards, >>>>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>>>> >>>>>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Best Regards, >>>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>>> >>>>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Best Regards, >>>>>>>>>>> Ayola Jayamaha >>>>>>>>>>> >>>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best Regards, >>>>>>>>>> Ayola Jayamaha >>>>>>>>>> >>>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best Regards, >>>>>>>>> Ayola Jayamaha >>>>>>>>> >>>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Best Regards, >>>>>>>> Ayola Jayamaha >>>>>>>> >>>>>>>> http://ayolajayamaha.blogspot.com >>>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best Regards, >>>>>> Ayola Jayamaha >>>>>> >>>>>> http://ayolajayamaha.blogspot.com >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Ayola Jayamaha >>>> >>>> http://ayolajayamaha.blogspot.com >>> >>> >> >> >> >> -- >> Best Regards, >> Ayola Jayamaha >> >> http://ayolajayamaha.blogspot.com >> > > > > -- > Best Regards, > Ayola Jayamaha > > http://ayolajayamaha.blogspot.com -- Best Regards,Ayola Jayamaha http://ayolajayamaha.blogspot.com -- Best Regards,Ayola Jayamaha http://ayolajayamaha.blogspot.com -- Best Regards,Ayola Jayamaha http://ayolajayamaha.blogspot.com -- Best Regards,Ayola Jayamaha http://ayolajayamaha.blogspot.com -- Best Regards,Ayola Jayamaha http://ayolajayamaha.blogspot.com
