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
