Thanks for the reminder. I am working on it Still some sections are incomplete. But if you could provide comments on the existing sections( is it too wordy ? any section needs improvement ? ) that would be helpful.
https://docs.google.com/document/d/1Zvdrorpm4jP40x37GRhVYAJ57V2GsxNem81gYdBkN7I Thanks Suriya On Thu, Mar 13, 2014 at 10:35 PM, Nirmal Fernando <[email protected]>wrote: > Hi Suriya, > > Also, it is high time to start building your proposal and get feedback > from the community. So, that you can write a proposal that stands out among > other proposals. > > > On Thu, Mar 13, 2014 at 11:58 PM, Sathyasuriya Priya < > [email protected]> wrote: > >> Thanks Nirmal. >> >> >> On Thu, Mar 13, 2014 at 4:05 AM, Nirmal Fernando >> <[email protected]>wrote: >> >>> Hi Suriya, >>> >>> >>> On Thu, Mar 13, 2014 at 3:15 PM, Sathyasuriya Priya < >>> [email protected]> wrote: >>> >>>> Just to give an update. >>>> We have got better control of how to use GCE with jclouds [1]. >>>> >>> >>> That's great! >>> >>> >>>> >>>> I have following queries about the testing aspects: >>>> Any pointers to email discussion/wiki would be helpful. >>>> >>>> >>>> 1. What kind of testing we do in general. >>>> >>>> Basic test would be to subscribe to a Cartridge and checking whether >>> the required instances are bringing up by Stratos in the configured IaaS. >>> >>>> >>>> 1. Any automated testing scripts we have. >>>> >>>> No, currently we do not have any. Those are most welcome. >>> >>>> >>>> 1. I see some unittestcases as part of the code. How do we run them. >>>> >>>> Those should be run if you build the code without skipping tests; i.e. >>> mvn clean install >>> >>>> >>>> 1. How/Why do we say EC2 is production supported & others are >>>> experimental. >>>> >>>> Cause EC2 is well tested and other IaaSes wasn't that well tested. But >>> I think we can get rid of that line. >>> >>>> >>>> 1. I see [2] can be a good way to setup a development setup. Any >>>> other suggestions. >>>> >>>> You might have noticed that in the dev list Damitha has discussed the >>> possibility of using docker-lxc as an IaaS in Stratos. >>> You might want to try that too. >>> >>>> >>>> [1] http://www.mail-archive.com/[email protected]/msg04420.html >>>> [2] https://github.com/snowch/stratos-developer-tools >>>> >>>> >>>> >>>> On Mon, Mar 3, 2014 at 3:31 AM, Sathyasuriya Priya < >>>> [email protected]> wrote: >>>> >>>>> Thanks Nirmal, >>>>> I will get back with more info on jclouds GCE. >>>>> >>>>> >>>>> On Mon, Mar 3, 2014 at 3:20 AM, Nirmal Fernando < >>>>> [email protected]> wrote: >>>>> >>>>>> Hey Suriya, >>>>>> >>>>>> It's glad to hear that you are interested in the GCE support >>>>>> integration project. Please find my comments in-line. >>>>>> >>>>>> >>>>>> On Mon, Mar 3, 2014 at 4:30 PM, Sathyasuriya Priya < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Dear Stratos developers, >>>>>>> >>>>>>> I am Suriyapriya Veluchamy, currently an MS CS student at NPU, >>>>>>> Fremont, CA, USA. >>>>>>> I am interested in the GSOC project listed in jira - adding support >>>>>>> for Google Compute Engine. >>>>>>> https://issues.apache.org/jira/browse/STRATOS-480 >>>>>>> >>>>>>> I had a few clarifications after going through Stratos documentation >>>>>>> and codebase, in the last couple of days. >>>>>>> >>>>>>> I see that Cloud Controller is the component that directly interacts >>>>>>> with laases. Rest of the components are lass agnostic (mostly?). >>>>>>> >>>>>> >>>>>> Correct. >>>>>> >>>>>> >>>>>>> I also see that jclouds is adding support for GCE - >>>>>>> https://github.com/jclouds/jclouds-labs-google >>>>>>> Not sure on the working status of the support. If somebody could >>>>>>> brief on this, that would be helpful. >>>>>>> >>>>>> >>>>>> I see... so we need to first identify the status of the GCE support >>>>>> of jclouds. >>>>>> >>>>>> >>>>>>> Since stratos uses jclouds, it should have support for GCE ? (may be >>>>>>> not all features may work) >>>>>>> >>>>>> >>>>>> Yes, at least the basic functionality should work. >>>>>> >>>>>>> >>>>>>> My question is about the scope of the project. Does it involve >>>>>>> working with jcloud team as well to get the required support ? >>>>>>> Or stratos will directly use the GCE apis to get the required >>>>>>> support. >>>>>>> >>>>>> >>>>>> It's not feasible to implement jclouds API for GCE as part of this >>>>>> project. So, initial idea was generated based on the fact that jclouds >>>>>> has >>>>>> support for GCE. >>>>>> >>>>>>> >>>>>>> I would like to measure the complexity of the work. Do you expect it >>>>>>> to be more of integration with jclouds GCE support + fixing bugs + >>>>>>> testing >>>>>>> in stratos. >>>>>>> >>>>>> >>>>>> Yes, exactly. You might have to fix issues that you will encounter in >>>>>> jclouds GCE too. >>>>>> >>>>>> >>>>>>> Or would it be more full-fledged development needed to get the >>>>>>> things working. >>>>>>> >>>>>>> I also see large scale testing as one of the goals. I haven't >>>>>>> thought about it in detail. But, any suggestions on how much percent of >>>>>>> total work would this item cover (may be 25-40%)? >>>>>>> >>>>>>> >>>>>> I hope above answers clarified this question too. >>>>>> >>>>>>> Please let me know if I am not clear in any of the questions. >>>>>>> >>>>>> >>>>>> So, as a starting point, if you can contact jclouds developer list >>>>>> and get clarified on the status of the GCE support, that'll be great. >>>>>> >>>>>>> >>>>>>> Thank you >>>>>>> Suriya >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best Regards, >>>>>> Nirmal >>>>>> >>>>>> Nirmal Fernando. >>>>>> PPMC Member & Committer of Apache Stratos, >>>>>> Senior Software Engineer, WSO2 Inc. >>>>>> >>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>> >>>>> >>>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ >
