I see. Thanks. I was string searching for aws-elb all around the jclouds main project, and concluding its not at all implemented. Now, I see, its a separate project.
On Thu, Mar 20, 2014 at 12:58 AM, Ignasi Barrera <[email protected]>wrote: > Reading the proposal again, I think you should include also some time to > work in the aws-elb api (in the jclouds-labs-aws repo). > > The Rackspace load balancer api is complete, but the AWS one has just the > methods directly needed by the current abstraction. When building the new > one, the ELB api will have to be completed too, so make sure the proposal > reflects and allocates time for that. > El 20/03/2014 07:16, "Ignasi Barrera" <[email protected]> escribió: > > > I referred to the ones in jclouds-loadbalancer. There is only the > > LoadBalancerMetadata, and that model has to be extended so the new > methods > > of the service can be built. > > El 20/03/2014 03:25, "Sathyasuriya Priya" <[email protected]> > > escribió: > > > >> Thanks for the feedback. > >> > >> I guess you are mentioning about org.jclouds.domain.* classes in > >> jclouds-core, jclouds-compute for example. > >> I will look into more & improve based on that. > >> > >> Dear jclouds devs, > >> > >> Anybody else would like to be mentor of this project. > >> Pls point who could assign mentors officially. > >> > >> > >> > >> On Wed, Mar 19, 2014 at 3:00 AM, Ignasi Barrera < > [email protected] > >> >wrote: > >> > >> > Hi Suriya, > >> > > >> > A couple comments on the proposal: > >> > > >> > There is still no assigned mentor, so remove it until it is officially > >> > assigned. > >> > > >> > I'd differentiate the "Analysis and Design" phase form the > >> > "Development and Testing" one. Having a good design is key here (as > >> > the project is about building a proper abstraction), and I think we'll > >> > spent some time in the design phase. In it we should come up with: > >> > > >> > * A portable domain model that allows us to carry as much information > >> > as we can, to be used by all providers. > >> > * The improved service interface, enabling the new operations you > >> > described. > >> > > >> > The domain model, and how users will use it will be the key for the > >> > project and the success of the abstraction. > >> > > >> > > >> > Nice proposal, BTW. Look forward to seeing it progress! > >> > > >> > > >> > Ignasi > >> > > >> > > >> > [1] > >> > > >> > http://docs.aws.amazon.com/ElasticLoadBalancing/latest/APIReference/API_CreateLoadBalancer.html > >> > > >> > > >> > > >> > On 18 March 2014 11:41, Sathyasuriya Priya <[email protected]> > >> wrote: > >> > > hi Ignasi, > >> > > > >> > > I have come up with proposal for the gsoc idea - > >> > > JCLOUDS-483<https://issues.apache.org/jira/browse/JCLOUDS-483> > >> > > This is my 2nd proposal (first is to *STRATOS-480 > >> > > <https://issues.apache.org/jira/browse/STRATOS-480>*). > >> > > > >> > > If you could take a quick look at the doc (especially 'Detailed > >> design' > >> > > section), and let me know of your quick comments, that would be > >> helpful. > >> > > > >> > > > >> > > >> > https://docs.google.com/document/d/1HicFnW0TwU5mi05HQMrwfCpZ3rHH-SE1ITzMJpAJTm4/ > >> > > > >> > > Thanks for your time > >> > > > >> > > Suriya > >> > > >> > > >
