jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-971) On adding an etcd (or coreos fame) provider
Date Mon, 27 Jul 2015 07:04:04 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642370#comment-14642370

Ignasi Barrera commented on JCLOUDS-971:

Although it does not belong to any of the current available abstractions, I see it as a valuable
API that could be very useful for people using the Docker provider. We have other APIs like
Chef that don't belong to an abstraction but that integrate pretty well with the ComputeService,
and I see etcd as an API that will help us build a better and more general Docker support.
I'd say go ahead and send the PR!

> On adding an etcd (or coreos fame) provider
> -------------------------------------------
>                 Key: JCLOUDS-971
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-971
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-labs
>    Affects Versions: 2.0.0
>            Reporter: Christopher Dancy
>              Labels: coreos, etcd, jclouds-labs
> We've already got a full (all API/features, mock and integration tests) implementation
of etcd using jclouds here and would like to essentially donate the code to jclouds for others
to use. This api does not and really can not have a compute api so it's just supporting the
API as described here: https://github.com/coreos/etcd/blob/master/Documentation/api.md
> What do you guys think? Not sure if you guys would take it seeing as how there is no
compute front-end but others I have to imagine, those working with coreos for whatever reason,
would love to have an easy to use jclouds-API to work with an administer an etcd cluster ...
lord knows we do.
> And if you say yes don't worry I will NOT be sending in the entire code base as 1 giant
PR. I'll break up it up into much smaller chunks for folks to digest.
> Thoughts? [~nacx]

This message was sent by Atlassian JIRA

View raw message