AW: interest in creating a "cassandra-gossip" library?
Hi, Is there any progress on this topic? I would really like to see such a library. -Ursprüngliche Nachricht- Von: matthew hawthorne [mailto:mhawtho...@gmail.com] Gesendet: Mittwoch, 22. Dezember 2010 20:07 An: dev@cassandra.apache.org Betreff: interest in creating a "cassandra-gossip" library? hello, I'm starting a project at my day job to deploy a gossip protocol implementation. part of my initial work is to evaluate existing implementations. being loosely familiar with Cassandra, I read http://wiki.apache.org/cassandra/ArchitectureGossip and have looked over the related code a bit. is there interest in breaking out the gossip-related portions of Cassandra into a library that could be reused by other projects? I work on a team that is ready and willing to contribute heavily. we'd just need some guidance as to how to structure the Cassandra subcomponent(s) and properly integrate them with the builds, tests, etc. here are a few examples of functionality we're looking to add: 1) hierarchical state - our use case is cross data center gossip, where we don't want every node in the 2 clusters communicating, but do want a node from cluster1 to send a summary of the cluster's state to cluster2, and vice versa. essentially I'm talking about rolling up the state of multiple nodes into a single "virtual" node 2) mutual authentication - nodes verifying the identity of other nodes before gossipping 3) encryption - encrypted traffic, especially for the cross data center case any opinions on this? thanks in advance for any feedback! -matt
Re: AW: interest in creating a "cassandra-gossip" library?
Roland, I was also interested in this for very similar reasons. I was planning on working on this after tackling some of the thrift build clean and transport requests i've been working on. I created CASSANDRA-3125 to help track the progress of this a little easier -Jake On Sep 2, 2011, at 5:05 AM, Roland Gude wrote: > Hi, > > Is there any progress on this topic? > I would really like to see such a library. > > -Ursprüngliche Nachricht- > Von: matthew hawthorne [mailto:mhawtho...@gmail.com] > Gesendet: Mittwoch, 22. Dezember 2010 20:07 > An: dev@cassandra.apache.org > Betreff: interest in creating a "cassandra-gossip" library? > > hello, > > I'm starting a project at my day job to deploy a gossip protocol > implementation. part of my initial work is to evaluate existing > implementations. > > being loosely familiar with Cassandra, I read > http://wiki.apache.org/cassandra/ArchitectureGossip and have looked > over the related code a bit. > > is there interest in breaking out the gossip-related portions of > Cassandra into a library that could be reused by other projects? I > work on a team that is ready and willing to contribute heavily. we'd > just need some guidance as to how to structure the Cassandra > subcomponent(s) and properly integrate them with the builds, tests, > etc. > > here are a few examples of functionality we're looking to add: > > 1) hierarchical state - our use case is cross data center gossip, > where we don't want every node in the 2 clusters communicating, but do > want a node from cluster1 to send a summary of the cluster's state to > cluster2, and vice versa. essentially I'm talking about rolling up > the state of multiple nodes into a single "virtual" node > > 2) mutual authentication - nodes verifying the identity of other nodes > before gossipping > > 3) encryption - encrypted traffic, especially for the cross data center case > > any opinions on this? thanks in advance for any feedback! > > -matt >
Re: AW: interest in creating a "cassandra-gossip" library?
Would this help? http://svn.apache.org/viewvc?view=revision&revision=1157967 On Fri, Sep 2, 2011 at 10:01 AM, Jake Farrell wrote: > Roland, I was also interested in this for very similar reasons. I was > planning on working on this after tackling some of the thrift build clean > and transport requests i've been working on. I created CASSANDRA-3125 to > help track the progress of this a little easier > > -Jake > > On Sep 2, 2011, at 5:05 AM, Roland Gude wrote: > > > Hi, > > > > Is there any progress on this topic? > > I would really like to see such a library. > > > > -Ursprüngliche Nachricht- > > Von: matthew hawthorne [mailto:mhawtho...@gmail.com] > > Gesendet: Mittwoch, 22. Dezember 2010 20:07 > > An: dev@cassandra.apache.org > > Betreff: interest in creating a "cassandra-gossip" library? > > > > hello, > > > > I'm starting a project at my day job to deploy a gossip protocol > > implementation. part of my initial work is to evaluate existing > > implementations. > > > > being loosely familiar with Cassandra, I read > > http://wiki.apache.org/cassandra/ArchitectureGossip and have looked > > over the related code a bit. > > > > is there interest in breaking out the gossip-related portions of > > Cassandra into a library that could be reused by other projects? I > > work on a team that is ready and willing to contribute heavily. we'd > > just need some guidance as to how to structure the Cassandra > > subcomponent(s) and properly integrate them with the builds, tests, > > etc. > > > > here are a few examples of functionality we're looking to add: > > > > 1) hierarchical state - our use case is cross data center gossip, > > where we don't want every node in the 2 clusters communicating, but do > > want a node from cluster1 to send a summary of the cluster's state to > > cluster2, and vice versa. essentially I'm talking about rolling up > > the state of multiple nodes into a single "virtual" node > > > > 2) mutual authentication - nodes verifying the identity of other nodes > > before gossipping > > > > 3) encryption - encrypted traffic, especially for the cross data center > case > > > > any opinions on this? thanks in advance for any feedback! > > > > -matt > > > >
Re: [VOTE] release 0.7.9 (redux)
On Wed, Aug 31, 2011 at 3:57 PM, Eric Evans wrote: > If at first you don't succeed[3], try, try again; I propose the > following for release as 0.7.9. +1 -Brandon
Re: [VOTE] release 0.7.9 (redux)
+1 On Wed, Aug 31, 2011 at 3:57 PM, Eric Evans wrote: > If at first you don't succeed[3], try, try again; I propose the > following for release as 0.7.9. > > SVN: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1163795 > Debian Package Artifacts: http://people.apache.org/~eevans > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-008/ > > The vote will be open for 72 hours, or until the next lunar apogee if needed. > > Thanks, > > [1]: http://goo.gl/uenGn (CHANGES.txt) > [2]: http://goo.gl/AQ2KY (NEWS.txt) > [3]: http://article.gmane.org/gmane.comp.db.cassandra.devel/4081 > > -- > Eric Evans > Acunu | http://www.acunu.com | @acunu > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: [VOTE] release 0.7.9 (redux)
+1 On Wed, Aug 31, 2011 at 15:57, Eric Evans wrote: > If at first you don't succeed[3], try, try again; I propose the > following for release as 0.7.9. > > SVN: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1163795 > Debian Package Artifacts: http://people.apache.org/~eevans > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-008/ > > The vote will be open for 72 hours, or until the next lunar apogee if needed. > > Thanks, > > [1]: http://goo.gl/uenGn (CHANGES.txt) > [2]: http://goo.gl/AQ2KY (NEWS.txt) > [3]: http://article.gmane.org/gmane.comp.db.cassandra.devel/4081 > > -- > Eric Evans > Acunu | http://www.acunu.com | @acunu >
Re: [VOTE] release 0.7.9 (redux)
+1 On Fri, Sep 2, 2011 at 7:44 PM, Gary Dusbabek wrote: > +1 > > On Wed, Aug 31, 2011 at 15:57, Eric Evans wrote: >> If at first you don't succeed[3], try, try again; I propose the >> following for release as 0.7.9. >> >> SVN: >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1163795 >> Debian Package Artifacts: http://people.apache.org/~eevans >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-008/ >> >> The vote will be open for 72 hours, or until the next lunar apogee if needed. >> >> Thanks, >> >> [1]: http://goo.gl/uenGn (CHANGES.txt) >> [2]: http://goo.gl/AQ2KY (NEWS.txt) >> [3]: http://article.gmane.org/gmane.comp.db.cassandra.devel/4081 >> >> -- >> Eric Evans >> Acunu | http://www.acunu.com | @acunu >> >
Re: CQL Drivers
On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote: > I posed a similar question about the JDBC driver in CASSANDRA-2936. > > Should these tests be considered functional tests of Cassandra, and > left be left where they are? I know that was my intention WRT > test_cql.py (the driver itself has a few tests of its own that do not > require a server). > > I guess I don't have a strong opinion either way, though it seems > easier to say that Cassandra's tests will require you to have a driver > installed, versus having to configure the build/test of a driver to > point to a Cassandra tree. I'd lean towards "the tests should be in the client trees." It feels odd to move the drivers out, but leave their test suites in core. (Keeping in mind that, as you pointed out, we have two more drivers almost done.) -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: CQL Drivers
On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote: > On Wed, Aug 31, 2011 at 10:58 PM, Jonathan Ellis wrote: >> On Wed, Aug 31, 2011 at 4:24 PM, Eric Evans wrote: >>> CASSANDRA-2936 is in progress (patches attached), but is there any >>> reason not to get started with the Python driver now? >> >> Heads up that test/system/test_cql.py depends on the Python driver. >> It should probably be moved to the Python driver's test suite. (Which >> then needs the same kind of "start a Cassandra server" ability that >> the Cassandra system tests have.) > > I posed a similar question about the JDBC driver in CASSANDRA-2936. > > Should these tests be considered functional tests of Cassandra, and > left be left where they are? I know that was my intention WRT > test_cql.py (the driver itself has a few tests of its own that do not > require a server). > > I guess I don't have a strong opinion either way, though it seems > easier to say that Cassandra's tests will require you to have a driver > installed, versus having to configure the build/test of a driver to > point to a Cassandra tree. No opinions on this? To summarize, the options as I see them are: 1. Keep the tests that query Cassandra, as-is, with the drivers they use. 2. Leave the tests that query Cassandra with Cassandra, (i.e. consider them Cassandra tests). 3. Keep the tests that query Cassandra, but alter them to be idempotent and to connect to an existent node, instead of spinning up/down an instance in test setup/teardown. (1) requires that you have some way of pointing the build at a local copy of a Cassandra tree (as I remember it, there were some that didn't care for this). (2) means that you'd need the corresponding driver installed (or an embedded copy as the case may be) in order to run those tests. (3) seems to be most consistent with how other people do it for code that connects to some service. -- Eric Evans Acunu | http://www.acunu.com | @acunu
Re: CQL Drivers
On Fri, Sep 2, 2011 at 3:49 PM, Jonathan Ellis wrote: > On Thu, Sep 1, 2011 at 9:08 AM, Eric Evans wrote: >> I posed a similar question about the JDBC driver in CASSANDRA-2936. >> >> Should these tests be considered functional tests of Cassandra, and >> left be left where they are? I know that was my intention WRT >> test_cql.py (the driver itself has a few tests of its own that do not >> require a server). >> >> I guess I don't have a strong opinion either way, though it seems >> easier to say that Cassandra's tests will require you to have a driver >> installed, versus having to configure the build/test of a driver to >> point to a Cassandra tree. > > I'd lean towards "the tests should be in the client trees." It feels > odd to move the drivers out, but leave their test suites in core. > (Keeping in mind that, as you pointed out, we have two more drivers > almost done.) Referring to the mail I sent before seeing this does that mean option #1 or #3, require a Cassandra tree, or point to running instance? -- Eric Evans Acunu | http://www.acunu.com | @acunu
