Kazoo Version 5 open source

[RuhNet]

On 11/11/2024 at 1:51 PM, teknogk said:

Does anyone have an updated install plan for creating the multizone cluster on couchdb 2/3? Im having trouble understanding the placement and zoning options for couch, but would like to be running on a newer version when building a 4.3 cluster. Also can you post the discord invite again, it expired. id love to be able to help in anyway that i can.

Don't want to get too off topic with this thread, but:

Couch v2 is the supported/approved version, but I use v3. You need to modify a Trunkstore view (if you use Trunkstore) and do a redirection of the admin port using HAProxy or other server like Nginx/Caddy/whatever.

There is a thread about the Trunkstore view mod here in the forums.

Placement and zoning depends on your cluster size. If you are in a single DC, then there isn't a reason to do multi-zone, unless you have a large number of servers. The most common scenario I encounter when setting up clients is they have 2 zones, and I recommend a minimum of 3 DB servers in each if they want full redundancy with good performance. Then for placement I usually recommend a 2+2 split; in other words put 2 copies of each document in the local zone, and 2 copies in the remote zone. 

NOTE that CouchDB zones are disconnected from and have no relationship to Kazoo zones---it's a totally different system. You could have a single zone Kazoo, with 5 Couch zones if you wanted, or vice versa. 

I generally recommend to have as few zones as you can get by with, both for Couch and for Kazoo. 

(I sent you an invite as well)

 

 

Edited November 12, 2024 by RuhNet (see edit history)

[Mooseable]

You can use couchdb v3 fine on 4.3. it's more about couchdb zoning, which is well documented.

This is the discord invite again for another 7 days. It's not a support channel though, it's for those wanting to contribute to efforts in maintaining 4.3.

https://discord.gg/r77hSf89

[Mark McDonald]

Hi RuhNet/Mooseable,

Our BigCouch cluster is old and dying and we're looking to move to CouchDB (preferably v3).  Is it possible to provide any information as to what's needed to be done with HAProxy to redirect the admin port (5986) to 5984?  It's not just simple forwarding but rewriting the URL's, correct?

[RuhNet]

10 hours ago, Mark McDonald said:

Hi RuhNet/Mooseable,

Our BigCouch cluster is old and dying and we're looking to move to CouchDB (preferably v3).  Is it possible to provide any information as to what's needed to be done with HAProxy to redirect the admin port (5986) to 5984?  It's not just simple forwarding but rewriting the URL's, correct?

Sure---and you are correct, it needs a redirect since the path has changed. All you need is something like this:

frontend couch-5986-admin-port
    bind 127.0.0.1:15986
    default_backend couch-redir-node-admin-port

backend couch-redir-node-admin-port
  balance roundrobin
    reqrep ^([^\ :]*)\ /(.*)     \1\ /_node/_local/\2
    #http-request replace-uri ^/(.*)     /_node/_local/\1
    server couch1 172.31.12.34:5984 check
    server couch2 172.31.23.45:5984 check
    server couch3 172.31.34.56:5984 check

If you are using a version of HAProxy v2.0 or later then comment out the `reqrep` line and uncomment the `http-request replace-uri` line.

[Mark McDonald]

Awesome, thank you!  We've been migrating databases for the past 24 hours.  For whatever reason the connection from BigCouch times out and we have to re-run the _replicate on it numerous times to finally get all the documents over.  Have you seen anything like this?

After running the same command a few (or a few dozen) times, everything eventually makes it over.  We tried everything from connection timeout, waiting between replicates, etc with the same result. 
 

% curl -X POST http://user:pass@xx.xx.xx.xx:5984/_replicate \

-H "Content-Type: application/json" \

-d '{

"source": "http://xx.xx.xx.xx:5984/anonymous_cdrs",

"target": "http://user:pass@xx.xx.xx.xx:5984/anonymous_cdrs",

"create_target": true,

"connection_timeout": 1000000

}'

{"error":"error","reason":"{http_request_failed,\"POST\",\n \"http://xx.xx.xx.xx:5984/anonymous_cdrs/_bulk_get?latest=true&revs=true&attachments=false\",\n {error,sel_conn_closed}}"}

Edited December 5, 2024 by Mark McDonald (see edit history)

[teknogk]

On 10/22/2024 at 11:25 AM, mc_ said:

Sadly the update is 5.x release is now targeting early 2025. Your guess is as good as mine whether that target will be hit. Continual assurances on open sourcing being the goal but the delays keep mounting so...

@mc_ Has there been any updated target dates discussed yet on this?

[KNERD]

1 hour ago, teknogk said:

@mc_ Has there been any updated target dates discussed yet on this?

To quote Doctor McCoy, "It's dead, Jim."

[teknogk]

On 2/10/2025 at 12:42 PM, KNERD said:

To quote Doctor McCoy, "It's dead, Jim."

Did someone say that officially or are you just speculating based on the fact they keep pushing back further and further?

[KNERD]

19 minutes ago, teknogk said:

Did someone say that officially or are you just speculating based on the fact they keep pushing back further and further?

There is an old saying which goes something like Actions speak louder than words.

[RuhNet]

25 minutes ago, teknogk said:

Did someone say that officially or are you just speculating based on the fact they keep pushing back further and further?

He's just speculating. Most people don't understand the complexities of a large project like Kazoo, so it's very common for many to assume that multiple delays == cancellation. When in reality that isn't the case. I don't have any inside information on it, but having worked on some large projects myself before, 2600Hz/Ooma's timeline for bringing it out, although disappointing and frustrating so far, isn't a clear indication of Kazoo v5.x staying closed source. 

[KNERD]

Just now, RuhNet said:

He's just speculating. Most people don't understand the complexities of a large project like Kazoo, so it's very common for many to assume that multiple delays == cancellation. When in reality that isn't the case. I don't have any inside information on it, but having worked on some large projects myself before, 2600Hz/Ooma's timeline for bringing it out, although disappointing and frustrating so far, isn't a clear indication of Kazoo v5.x staying closed source. 

It does not take six years to complete a project with a team. Even a single person being paid full time could have it completed.

[RuhNet]

Just now, KNERD said:

It does not take six years to complete a project with a team. Even a single person being paid full time could have it completed.

LOL -- I'm working with some companies on projects that are taking even longer than that. But the thing is, Kazoo v5 is completed and has been in production for several years. It's just the open source release of it that has been delayed. Now, that's not to say that they _couldn't_ have released it sooner if things were planned/managed better. But the thing is, they run a business, and releasing the open source code is only a "side gig" thing and isn't actually a huge benefit to the business side of things (it is some, but not nearly as much as people think). Clearly the open source release isn't their "priority" or it would have already been released, but that doesn't mean it isn't an important thing on their list; and that is why this amount of time, although painful to all the persons waiting on it, isn't unreasonable.

[KNERD]

2 minutes ago, RuhNet said:

LOL -- I'm working with some companies on projects that are taking even longer than that. But the thing is, Kazoo v5 is completed and has been in production for several years. It's just the open source release of it that has been delayed. Now, that's not to say that they _couldn't_ have released it sooner if things were planned/managed better. But the thing is, they run a business, and releasing the open source code is only a "side gig" thing and isn't actually a huge benefit to the business side of things (it is some, but not nearly as much as people think). Clearly the open source release isn't their "priority" or it would have already been released, but that doesn't mean it isn't an important thing on their list; and that is why this amount of time, although painful to all the persons waiting on it, isn't unreasonable.

I have been aware it has been completed, but they also mentioned waiting on the Marketplace  to be completed. Sounds like a different team working on it. I would think even less time to complete that.

In addition it's not a "side gig." They offer hosting for it, as well selling a deal with OneBill for a billing system.

[RuhNet]

6 minutes ago, KNERD said:

I have been aware it has been completed, but they also mentioned waiting on the Marketplace  to be completed. Sounds like a different team working on it. I would think even less time to complete that.

In addition it's not a "side gig." They offer hosting for it, as well selling a deal with OneBill for a billing system.

I meant that their releasing anything open source is a "side gig" since it's not integral to their business at this point.

[fmateo05]

Watching the thread over here.. just in case...