You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Mikołaj Zalewski <mi...@google.com> on 2014/03/28 11:34:19 UTC
Google cloud support
Hi,
My colleges and I are considering contributing into jclouds' Google cloud
support. I've found there is GCE support in labs. Are there pieces missing
for it to graduate out of labs? Are there things you would recommend to
implement. So far I've found:
- there is no support for TargetPool, TargetInstance and HttpHealthCheck
API.
- there is no implementation of the generic loadbalancer API on top of it.
- we could write some examples for the APIs.
- there is bug 495 in JIRA.
- there is a feature that a GCE instance get an OAuth token from
http://metadata/ for which code could be written.
Is there something different you would recommend to look into?
Mikołaj Zalewski
Re: Google cloud support
Posted by Andrea Turli <an...@gmail.com>.
Hi,
I've just issued a PR to support TargetPool, TargetInstance and
HttpHealthCheck API https://github.com/jclouds/jclouds-labs-google/pull/22
Please have a look and comment on it.
Andrea
On Sat, Mar 29, 2014 at 8:55 AM, Ignasi Barrera <na...@apache.org> wrote:
> Hi Mikolaj,
>
> Thanks for your interest! Few weeks ago there was a thread [1]
> offering help too. Some ideas were discussed there, so check it out to
> have an overview of some things we'd like to have. The list you passed
> is good too, and it would be great if you could file them in JIRA [2]
> so we can properly track them. Having them implemented would be great!
>
> Regarding the Load Balancer implementation, the current abstraction is
> very limited and provides little value. There is a proposed GSoC
> project [3, 4] to extend it and make it usable, so I'd wait until the
> new abstraction/model is done before implementing the LB abstraction.
> It would be great, though, to have your input when it comes to
> re-design the abstraction, so stay tuned to the list!
>
> Finally, in order to graduate a project, we need to know it is
> working, and some feedback from some users. Alex's input is highly
> appreciated, and as he says it can be considered ready to be moved to
> the main repo.
>
> Once there, we need to make sure tithe provider works and is kept up
> to date. To do that we need to be able to run the live test suite
> (tests that actually deploy and do stuff) in each release to make sure
> everything is working as expected. This obviously requires an account,
> and we often use our personal/company ones, but as long as the number
> of supported providers grows, this is getting more difficult. Some
> providers are helping us [5] by providing testing accounts. Is there
> any offering for non-profits or some plan we could use for the live
> tests? (This can be discussed off-list if it is more convenient). That
> would definitely help speed the promotion of the provider to the main
> repo, but I'm just asking! :)
>
>
>
> Thanks for your interest!
>
> Ignasi
>
>
> [1] http://markmail.org/message/srurgqweemg47a7j
> [2] https://issues.apache.org/jira/browse/JCLOUDS
> [3]
> https://www.google-melange.com/gsoc/proposal/review/org/google/gsoc2014/suriyapriya/5707702298738688
> [4] http://markmail.org/message/fmgrx5fn7tlv7p6h
> [5] https://wiki.apache.org/jclouds/Test%20Provider%20Thanks
>
>
>
> On 28 March 2014 23:52, Alex Heneveld <al...@cloudsoftcorp.com>
> wrote:
> >
> > side question -- GCE currently presents itself as an api (implementing
> > ApiMetadata) rather than a provider. is there a reason why? it seems
> to me
> > it should be a provider.
> >
> > as for it leaving labs, having used the library a lot, i'd suggest it be
> > promoted now -- kudos to abayer and dralves for a great job. mikolaj,
> your
> > list is a good one for next steps (LB support in particular for me!),
> but i
> > don't see anything on there which should block promotion.
> >
> > --a
> >
> >
> >
> > On 28/03/2014 10:34, Mikołaj Zalewski wrote:
> >>
> >> Hi,
> >> My colleges and I are considering contributing into jclouds' Google
> >> cloud
> >> support. I've found there is GCE support in labs. Are there pieces
> missing
> >> for it to graduate out of labs? Are there things you would recommend to
> >> implement. So far I've found:
> >> - there is no support for TargetPool, TargetInstance and
> >> HttpHealthCheck
> >> API.
> >> - there is no implementation of the generic loadbalancer API on top
> of
> >> it.
> >> - we could write some examples for the APIs.
> >> - there is bug 495 in JIRA.
> >> - there is a feature that a GCE instance get an OAuth token from
> >> http://metadata/ for which code could be written.
> >> Is there something different you would recommend to look into?
> >>
> >> Mikołaj Zalewski
> >>
> >
>
Re: Google cloud support
Posted by Ignasi Barrera <na...@apache.org>.
Hi Mikolaj,
Thanks for your interest! Few weeks ago there was a thread [1]
offering help too. Some ideas were discussed there, so check it out to
have an overview of some things we'd like to have. The list you passed
is good too, and it would be great if you could file them in JIRA [2]
so we can properly track them. Having them implemented would be great!
Regarding the Load Balancer implementation, the current abstraction is
very limited and provides little value. There is a proposed GSoC
project [3, 4] to extend it and make it usable, so I'd wait until the
new abstraction/model is done before implementing the LB abstraction.
It would be great, though, to have your input when it comes to
re-design the abstraction, so stay tuned to the list!
Finally, in order to graduate a project, we need to know it is
working, and some feedback from some users. Alex's input is highly
appreciated, and as he says it can be considered ready to be moved to
the main repo.
Once there, we need to make sure tithe provider works and is kept up
to date. To do that we need to be able to run the live test suite
(tests that actually deploy and do stuff) in each release to make sure
everything is working as expected. This obviously requires an account,
and we often use our personal/company ones, but as long as the number
of supported providers grows, this is getting more difficult. Some
providers are helping us [5] by providing testing accounts. Is there
any offering for non-profits or some plan we could use for the live
tests? (This can be discussed off-list if it is more convenient). That
would definitely help speed the promotion of the provider to the main
repo, but I'm just asking! :)
Thanks for your interest!
Ignasi
[1] http://markmail.org/message/srurgqweemg47a7j
[2] https://issues.apache.org/jira/browse/JCLOUDS
[3] https://www.google-melange.com/gsoc/proposal/review/org/google/gsoc2014/suriyapriya/5707702298738688
[4] http://markmail.org/message/fmgrx5fn7tlv7p6h
[5] https://wiki.apache.org/jclouds/Test%20Provider%20Thanks
On 28 March 2014 23:52, Alex Heneveld <al...@cloudsoftcorp.com> wrote:
>
> side question -- GCE currently presents itself as an api (implementing
> ApiMetadata) rather than a provider. is there a reason why? it seems to me
> it should be a provider.
>
> as for it leaving labs, having used the library a lot, i'd suggest it be
> promoted now -- kudos to abayer and dralves for a great job. mikolaj, your
> list is a good one for next steps (LB support in particular for me!), but i
> don't see anything on there which should block promotion.
>
> --a
>
>
>
> On 28/03/2014 10:34, Mikołaj Zalewski wrote:
>>
>> Hi,
>> My colleges and I are considering contributing into jclouds' Google
>> cloud
>> support. I've found there is GCE support in labs. Are there pieces missing
>> for it to graduate out of labs? Are there things you would recommend to
>> implement. So far I've found:
>> - there is no support for TargetPool, TargetInstance and
>> HttpHealthCheck
>> API.
>> - there is no implementation of the generic loadbalancer API on top of
>> it.
>> - we could write some examples for the APIs.
>> - there is bug 495 in JIRA.
>> - there is a feature that a GCE instance get an OAuth token from
>> http://metadata/ for which code could be written.
>> Is there something different you would recommend to look into?
>>
>> Mikołaj Zalewski
>>
>
Re: Google cloud support
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
side question -- GCE currently presents itself as an api (implementing
ApiMetadata) rather than a provider. is there a reason why? it seems
to me it should be a provider.
as for it leaving labs, having used the library a lot, i'd suggest it be
promoted now -- kudos to abayer and dralves for a great job. mikolaj,
your list is a good one for next steps (LB support in particular for
me!), but i don't see anything on there which should block promotion.
--a
On 28/03/2014 10:34, Mikołaj Zalewski wrote:
> Hi,
> My colleges and I are considering contributing into jclouds' Google cloud
> support. I've found there is GCE support in labs. Are there pieces missing
> for it to graduate out of labs? Are there things you would recommend to
> implement. So far I've found:
> - there is no support for TargetPool, TargetInstance and HttpHealthCheck
> API.
> - there is no implementation of the generic loadbalancer API on top of it.
> - we could write some examples for the APIs.
> - there is bug 495 in JIRA.
> - there is a feature that a GCE instance get an OAuth token from
> http://metadata/ for which code could be written.
> Is there something different you would recommend to look into?
>
> Mikołaj Zalewski
>
Re: Google cloud support
Posted by Mikołaj Zalewski <mi...@google.com>.
On Fri, Mar 28, 2014 at 11:34 AM, Mikołaj Zalewski <mi...@google.com>wrote:
> Hi,
> My colleges and I are considering contributing into jclouds' Google
> cloud support. I've found there is GCE support in labs. Are there pieces
> missing for it to graduate out of labs? Are there things you would
> recommend to implement. So far I've found:
> - there is no support for TargetPool, TargetInstance and
> HttpHealthCheck API.
> - there is no implementation of the generic loadbalancer API on top of
> it.
> - we could write some examples for the APIs.
> - there is bug 495 in JIRA.
> - there is a feature that a GCE instance get an OAuth token from
> http://metadata/ for which code could be written.
> Is there something different you would recommend to look into?
>
> Mikołaj Zalewski
>
Thanks for all the answers. I see the GCE support is better than I
thought and even the target pool APIs should be also available soon. As I
understand, one should wait with implementing the generic loadbalancing API.
I've opened JIRA 518 [1] for the instance OAuth token feature. I would
welcome suggestion how to expose it in the API.
I didn't read the other thread carefully before, so I missed the
suggestion to a user guide in addition to examples, which sounds good.
I will look into if we can provide you with instances for testing.
Mikołaj
[1] https://issues.apache.org/jira/browse/JCLOUDS-518