You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@couchdb.apache.org by Robert Kowalski <ro...@kowalski.gd> on 2015/06/03 03:42:22 UTC

[DISCUSSION] nmo to the ASF

Hi folks,

I wrote nmo (speaks: nemo) as part of COUCHDB-2598 and I would like to
donate nemo - a tool to manage CouchDB clusters officially to the ASF.

Website with a short video demoing the main functionality at [1] and
code at [2] - as I said I wrote it as part of COUCHDB-2598 [3] and
would love to donate it as a next step now that I have something that
can get a review and demoes the basic concept of the cli client.

Features:

 - define cluster inventories and manage the clusters by their name
 - if one or more node(s) is/are down, you have to use --force to join
nodes into a cluster
 - parseable json output with --json as commandline argument
 - next to the cli an api to write own custom scripts, websites, services
 - website with docs for every command (both docs for api, cli
versions of the commands - see right navigation on website [1])
 - manpages
 - 100% test coverage.

Upcoming features:

 - streaming imports from MongoDB and Postgres (the version with JSON
support) into CouchDB

Best,
Robert

[1] http://robertkowalski.github.io/nmo/
[2] https://github.com/robertkowalski/nmo
[3] https://issues.apache.org/jira/browse/COUCHDB-2598

Re: [DISCUSSION] nmo to the ASF

Posted by Andy Wenk <an...@apache.org>.

The tool is awesome and I am very much  +1 on accepting it as a donation.

Alex, as Jan already stated. The split from Node.js and IO.js was the best
what could happen to the project. Because Node.js realised that they did
things wrong and the community brought everybody back on a healthy
community track. They are both more than alive and it is a good example for
how strong a community can be.

Sorry for the wall of text. Robert, awesome work. Thanks a lot ;-)
On Jun 3, 2015 15:13, "Jan Lehnardt" <ja...@apache.org> wrote:

>
> > On 03 Jun 2015, at 15:09, Alexander Shorin <kx...@gmail.com> wrote:
> >
> > On Wed, Jun 3, 2015 at 4:01 PM, Jan Lehnardt <ja...@apache.org> wrote:
> >>> On 03 Jun 2015, at 14:43, Alexander Shorin <kx...@gmail.com> wrote:
> >>>
> >>> On Wed, Jun 3, 2015 at 1:40 PM, Jan Lehnardt <ja...@apache.org> wrote:
> >>>>> On 03 Jun 2015, at 04:38, Alexander Shorin <kx...@gmail.com> wrote:
> >>>>>
> >>>>> Hi Robert,
> >>>>>
> >>>>> What's the rationale of your donation?
> >>>>
> >>>> The benefit then is that we can ship it with CouchDB :)
> >>>>
> >>>> I’m +1000, I’ve wanted something like this forever.
> >>>
> >>> I'm not sure that we'll have consensus on shipping nodejs tools,
> >>> especially with current state of nodejs.
> >>
> >> The current state of Node.js is fine.
> >
> > I wouldn't say that: node.js is dead, io.js develops quite fast, but
> > they provides broken releases for Windows and Linux quite often (2.1.0
> > was broken for instance for me and I had to wait for 2.2.1).
>
> Node.js is not dead. Please stop posting FUD.
>
> The io.js and Node.js projects are going to be merged in the future, work
> is currently ongoing. Node.js has stable releases all around, there is no
> technical reason, not to bet on it. There is a significant community and
> industry around Node.js/io.js.
>
> >
> >>> No problem if it was made in
> >>> Erlang (which gives more power on what it can do, like repare database
> >>> file).
> >>
> >> We can always shell out to Erlang-only tools. I just don’t see a whole
> >> lot of people working on those.
> >>
> >> Saying “we can’t use this because that one theoretical use-case might be
> >> a bit harder” seems short-sighted :)
> >
> > Ok, let's start the one (: People will come after.
> >
> >> Also, Node.js could work on .couch files just fine (with a bit more work
> >> of course).
> >
> > No code sharing with CouchDB what means hard to sync work with file
> > format which means easy to make a mistake and corrupt the database.
> > Not good perspective.
>
> Well, changes are usually small, and Node.js is fast to write :) — But
> yeah,
> would prefer those tools be in Erlang, and we’ve covered how to handle
> that :)
>
> Best
> Jan
> --
>
>
> >
> > --
> > ,,,^..^,,,
>
> --
> Professional Support for Apache CouchDB:
> http://www.neighbourhood.ie/couchdb-support/
>
>

Re: [DISCUSSION] nmo to the ASF

Posted by Robert Kowalski <ro...@kowalski.gd>.

Hi after some vacations!

Just to clarify and to give answers to the questions asked in the
thread and the discussion:

It was never my direct intention to ship nmo with CouchDB in a release
(see initial post). While I am +1 to make it an official tool for
managing clusters (at least for now as we don't have a better
alternative), I really don't have hard feelings to _not_ include it in
an official release - feel free to discuss this, my donation/repo move
is not tied to any decision or opinion regarding that and I am also
happy to _not_ take part in that discussion, as these discussions tend
to be very time consuming and demanding, at least for me. Whatever the
final decision is, I am happy to help in any way once it is decided.

I also think the right way is to add it to the ASF - I am a single
person and CouchDB has some awesome JavaScripters that can help
maintaining it. I built it because I saw that CouchDB was missing such
a tool while I was working on the "install-wizard-ticket". I built it
for the CouchDB project with a limited personal use-case for me.

I can just double Jan's answer to io and node. I also want to add that
I think we, the CouchDB project, can learn a lot from the two projects
and the now forming foundation, as they have a lot more contributors
(339 folks currently - that is a lot for a singe project). They also
have more momentum and companies participating in core development: it
seems they have done at least some things right. In general, not tied
to node/io I can just recommend to everyone to also take a look beyond
CouchDB and to try to identify what other big projects do right or
where they fail, we can learn a lot!

I just wanted to answer the questions/statements from my perspective
as I started the thread and as I see the thread moves to a +1 for
moving robertkowalski/nmo to apache/couchdb-nmo I think I am starting
the process this week.

Best,
Robert

On Wed, Jun 3, 2015 at 8:13 PM, Joan Touzet <wo...@apache.org> wrote:
> Thanks for the info on the separate repos. I assumed that since
> we already have Couch scattered across a large # of repos.
>
> It's all about what sort of build instructions we put in the "main"
> CouchDB distribution. As long as the main build script doesn't
> auto-forcibly-invoke building of all of these other tools, I'm fine.
>
> Assuming the above is true I'm +1.
>
> -Joan
>
> ----- Original Message -----
>> From: "Jan Lehnardt" <ja...@apache.org>
>> To: dev@couchdb.apache.org, "Joan Touzet" <wo...@apache.org>
>> Sent: Wednesday, June 3, 2015 2:06:41 PM
>> Subject: Re: [DISCUSSION] nmo to the ASF
>>
>>
>> > On 03 Jun 2015, at 19:35, Joan Touzet <wo...@apache.org> wrote:
>> >
>> > Is the intent with all of these contributions to ship them in
>> > a contrib/ tree? We're starting to get cluttered with tools and
>> > languages, and with couchdb-python also in the wings as potential
>> > contribution, I am concerned about the build process for the
>> > tool mandating npm, python, etc.
>>
>> I see them in different repos with their own build/release cycles
>> that aren’t bound to core CouchDB.
>>
>> The CouchDB distribution then can choose to bundle whatever latest
>> version of whatever tool when its time to release comes up. I see
>> it making more sense for nmo (I think of it as Fauxton-CLI) and less
>> for couchdb-python and nano, but this is all open for debate, my
>> main point here is that these are not bound to an Apache CouchDB
>> Release necessarily.
>>
>> Does this address your concerns?
>> >
>> > -Joan
>> >
>> > ----- Original Message -----
>> >> From: "Jan Lehnardt" <ja...@apache.org>
>> >> To: dev@couchdb.apache.org
>> >> Sent: Wednesday, June 3, 2015 9:32:00 AM
>> >> Subject: Re: [DISCUSSION] nmo to the ASF
>> >>
>> >>
>> >>> On 03 Jun 2015, at 15:24, Alexander Shorin <kx...@gmail.com>
>> >>> wrote:
>> >>>
>> >>> On Wed, Jun 3, 2015 at 4:12 PM, Jan Lehnardt <ja...@apache.org>
>> >>> wrote:
>> >>>>> On 03 Jun 2015, at 15:09, Alexander Shorin <kx...@gmail.com>
>> >>>>> wrote:
>> >>>>>
>> >>>>> On Wed, Jun 3, 2015 at 4:01 PM, Jan Lehnardt <ja...@apache.org>
>> >>>>> wrote:
>> >>>>>>> On 03 Jun 2015, at 14:43, Alexander Shorin <kx...@gmail.com>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>> On Wed, Jun 3, 2015 at 1:40 PM, Jan Lehnardt <ja...@apache.org>
>> >>>>>>> wrote:
>> >>>>>>>>> On 03 Jun 2015, at 04:38, Alexander Shorin
>> >>>>>>>>> <kx...@gmail.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Hi Robert,
>> >>>>>>>>>
>> >>>>>>>>> What's the rationale of your donation?
>> >>>>>>>>
>> >>>>>>>> The benefit then is that we can ship it with CouchDB :)
>> >>>>>>>>
>> >>>>>>>> I’m +1000, I’ve wanted something like this forever.
>> >>>>>>>
>> >>>>>>> I'm not sure that we'll have consensus on shipping nodejs
>> >>>>>>> tools,
>> >>>>>>> especially with current state of nodejs.
>> >>>>>>
>> >>>>>> The current state of Node.js is fine.
>> >>>>>
>> >>>>> I wouldn't say that: node.js is dead, io.js develops quite
>> >>>>> fast,
>> >>>>> but
>> >>>>> they provides broken releases for Windows and Linux quite often
>> >>>>> (2.1.0
>> >>>>> was broken for instance for me and I had to wait for 2.2.1).
>> >>>>
>> >>>> Node.js is not dead. Please stop posting FUD.
>> >>>>
>> >>>> The io.js and Node.js projects are going to be merged in the
>> >>>> future, work
>> >>>> is currently ongoing. Node.js has stable releases all around,
>> >>>> there is no
>> >>>> technical reason, not to bet on it. There is a significant
>> >>>> community and
>> >>>> industry around Node.js/io.js.
>> >>>
>> >>> I don't watch the TV. Good news then (:
>> >>
>> >> Hahahah :D
>> >>
>> >> Best
>> >> Jan
>> >> --
>> >>
>> >>
>>
>> --
>> Professional Support for Apache CouchDB:
>> http://www.neighbourhood.ie/couchdb-support/
>>
>>