You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Benoit Chesneau <bc...@gmail.com> on 2014/02/14 10:59:09 UTC
intention of couchdb-couch-stats and some other
I saw that the following repositories have been created but empty at that time:
intention of couchdb-couch-stats
couchdb-query-server-node
couchdb-query-server-spidermonkey
What are the intentions of these repositories?
couchdb-couch-stats looks like the one in rcouch:
https://github.com/refuge/couch_core/tree/master/apps/couch_stats
Maybe I should split it couch_stat as well. DO we care about the
historyy at that point?
For the others i only gues that the spidermonkey one should contain
couchjs. Paul what was your idea bout it?
FAter thinking a little more I am thinking we could also create the
following repositories:
couchbd-couch-compaction-daemon
couchdb-couch-os-daemon or simply couchdb-couch-external
couch-db-update-notifier at least the code using the port.
>From couchdb-couch-httpd i am thinking we could also split couch_httpd_proxy.
Thoughts?
- benoit
Re: intention of couchdb-couch-stats and some other
Posted by Paul Davis <pa...@gmail.com>.
On Fri, Feb 14, 2014 at 4:03 AM, Dave Cottlehuber <dc...@jsonified.com> wrote:
> On 14 February 2014 10:59, Benoit Chesneau <bc...@gmail.com> wrote:
>> I saw that the following repositories have been created but empty at that time:
>>
>> intention of couchdb-couch-stats
>> couchdb-query-server-node
>> couchdb-query-server-spidermonkey
>>
>> What are the intentions of these repositories?
>>
>> couchdb-couch-stats looks like the one in rcouch:
>>
>> https://github.com/refuge/couch_core/tree/master/apps/couch_stats
>>
>> Maybe I should split it couch_stat as well. DO we care about the
>> historyy at that point?
>>
>> For the others i only gues that the spidermonkey one should contain
>> couchjs. Paul what was your idea bout it?
>>
>>
>> FAter thinking a little more I am thinking we could also create the
>> following repositories:
>>
>> couchbd-couch-compaction-daemon
>> couchdb-couch-os-daemon or simply couchdb-couch-external
>> couch-db-update-notifier at least the code using the port.
>>
>>
>> From couchdb-couch-httpd i am thinking we could also split couch_httpd_proxy.
>>
>> Thoughts?
>>
>> - benoit
>
> This seems like an excellent time to suggest we have so many
> repositories we could do with some automated way to create & name
> them... perhaps a couch-couch-repo-factory is needed ;-)
>
> *ducks*
:D
For reference, the naming pattern is couchdb-(app name with
underscores replaced with hyphens). The couchdb- prefix is mandated by
ASF infra for git repositories. I replaced the underscores with
hyphens because couchdb-couch_mrview looked funny. So there is an
automated method for naming things, just no factor for it.
Re: intention of couchdb-couch-stats and some other
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 14 February 2014 10:59, Benoit Chesneau <bc...@gmail.com> wrote:
> I saw that the following repositories have been created but empty at that time:
>
> intention of couchdb-couch-stats
> couchdb-query-server-node
> couchdb-query-server-spidermonkey
>
> What are the intentions of these repositories?
>
> couchdb-couch-stats looks like the one in rcouch:
>
> https://github.com/refuge/couch_core/tree/master/apps/couch_stats
>
> Maybe I should split it couch_stat as well. DO we care about the
> historyy at that point?
>
> For the others i only gues that the spidermonkey one should contain
> couchjs. Paul what was your idea bout it?
>
>
> FAter thinking a little more I am thinking we could also create the
> following repositories:
>
> couchbd-couch-compaction-daemon
> couchdb-couch-os-daemon or simply couchdb-couch-external
> couch-db-update-notifier at least the code using the port.
>
>
> From couchdb-couch-httpd i am thinking we could also split couch_httpd_proxy.
>
> Thoughts?
>
> - benoit
This seems like an excellent time to suggest we have so many
repositories we could do with some automated way to create & name
them… perhaps a couch-couch-repo-factory is needed ;-)
*ducks*
Re: intention of couchdb-couch-stats and some other
Posted by Benoit Chesneau <bc...@gmail.com>.
On Fri, Feb 14, 2014 at 6:40 PM, Paul Davis <pa...@gmail.com> wrote:
> On Fri, Feb 14, 2014 at 3:59 AM, Benoit Chesneau <bc...@gmail.com> wrote:
>> I saw that the following repositories have been created but empty at that time:
>>
>> intention of couchdb-couch-stats
>> couchdb-query-server-node
>> couchdb-query-server-spidermonkey
>>
>> What are the intentions of these repositories?
>>
>> couchdb-couch-stats looks like the one in rcouch:
>>
>> https://github.com/refuge/couch_core/tree/master/apps/couch_stats
>>
>> Maybe I should split it couch_stat as well. DO we care about the
>> historyy at that point?
>
> Looks similar. I created it preemptively for the merge work. BigCouch
> has lots of calls to an internal app called margaret that was
> responsible for shipping metrics to our internal monitoring
> infrastructure. couch_stats is a rewrite of that work which is based
> on Folsom. This way users that want to do fancy things with their
> monitoring can add a small shim application to forward to their stats
> destination of choice.
>
> https://github.com/cloudant/couch_stats
>
> Here's a PR that shows how it'd be used:
>
> https://github.com/cloudant/fabric/pull/144
>
>>
That's quite interesting. I could play with that.
>> For the others i only gues that the spidermonkey one should contain
>> couchjs. Paul what was your idea bout it?
>>
>
> That was someone else's idea, but that's the idea. I don't intend to
> move to this pattern until after the merge but the idea is to make the
> couchjs implementation pluggable.
OK
>
>>
>> FAter thinking a little more I am thinking we could also create the
>> following repositories:
>>
>> couchbd-couch-compaction-daemon
>> couchdb-couch-os-daemon or simply couchdb-couch-external
>> couch-db-update-notifier at least the code using the port.
>>
>
> I think these are good candidates. I'd like to delay as much until
> after the merge as possible so that we're not duplicating work that
> just makes the merge harder.
>
>>
>> From couchdb-couch-httpd i am thinking we could also split couch_httpd_proxy.
>>
>
> This one seems a bit over specific. If we want to disable the proxy
> I'd just make that a config option.
>
>> Thoughts?
>>
>> - benoit
>
> A lot of these repos are just prepatory work because I don't like
> asking infra to keep creating repos for us so I've been trying to
> predict what we'd want in the future as I ask for things. The
> query-servers repos were suggested by someone (Dirkjan maybe?) and I
> thought would be reasonable moves in the future.
>
> The couch_stats stuff is specifically so that we can move forward
> pulling out anything that's Cloudant specific and continue with the
> merge.
I agree.
- benoit
Re: intention of couchdb-couch-stats and some other
Posted by Paul Davis <pa...@gmail.com>.
On Fri, Feb 14, 2014 at 3:59 AM, Benoit Chesneau <bc...@gmail.com> wrote:
> I saw that the following repositories have been created but empty at that time:
>
> intention of couchdb-couch-stats
> couchdb-query-server-node
> couchdb-query-server-spidermonkey
>
> What are the intentions of these repositories?
>
> couchdb-couch-stats looks like the one in rcouch:
>
> https://github.com/refuge/couch_core/tree/master/apps/couch_stats
>
> Maybe I should split it couch_stat as well. DO we care about the
> historyy at that point?
Looks similar. I created it preemptively for the merge work. BigCouch
has lots of calls to an internal app called margaret that was
responsible for shipping metrics to our internal monitoring
infrastructure. couch_stats is a rewrite of that work which is based
on Folsom. This way users that want to do fancy things with their
monitoring can add a small shim application to forward to their stats
destination of choice.
https://github.com/cloudant/couch_stats
Here's a PR that shows how it'd be used:
https://github.com/cloudant/fabric/pull/144
>
> For the others i only gues that the spidermonkey one should contain
> couchjs. Paul what was your idea bout it?
>
That was someone else's idea, but that's the idea. I don't intend to
move to this pattern until after the merge but the idea is to make the
couchjs implementation pluggable.
>
> FAter thinking a little more I am thinking we could also create the
> following repositories:
>
> couchbd-couch-compaction-daemon
> couchdb-couch-os-daemon or simply couchdb-couch-external
> couch-db-update-notifier at least the code using the port.
>
I think these are good candidates. I'd like to delay as much until
after the merge as possible so that we're not duplicating work that
just makes the merge harder.
>
> From couchdb-couch-httpd i am thinking we could also split couch_httpd_proxy.
>
This one seems a bit over specific. If we want to disable the proxy
I'd just make that a config option.
> Thoughts?
>
> - benoit
A lot of these repos are just prepatory work because I don't like
asking infra to keep creating repos for us so I've been trying to
predict what we'd want in the future as I ask for things. The
query-servers repos were suggested by someone (Dirkjan maybe?) and I
thought would be reasonable moves in the future.
The couch_stats stuff is specifically so that we can move forward
pulling out anything that's Cloudant specific and continue with the
merge.