Ticket #307 (closed task: duplicate)

Opened 5 years ago

Last modified 5 years ago

Testing distributed actor registry (aka CouchDB)

Reported by: claris Owned by: claris
Priority: major Milestone:
Component: ORCA: Shirako Core Version: baseline
Keywords: Cc: vjo@…, ibaldin@…, jonmills, pruth, anirban


This ticket is to host discussion on the testing process for the new actor registry with couchdb backend.

The new client code is all sitting in core.shirako. The server code is mostly Jquery and is hosted in Couchdb (slookup.exogeni.net/actor)

Copy/paste from email discussion:
n Feb 14, 2014, at 12:00 PM, Ilya Baldin <ibaldin@…> wrote:

There are several issues

1. Incorporating the code into aydan-recovery in such a way that it doesn't break recovery testing

I can’t see how would this code break recovery testing since old XMLRPC actor code and execution path is intact. It is on by default. The new code is running in redundant mode (or emulation mode if you wish).

2. Testing this in some way
I think we need to modify the code to set properties in the orca.properties to use none, one or both of the registration mechanisms (old XMLRPC+MySQL back end and new REST+Coach), so it can be easily configured. The CoachDB API should be off by default.

Agree. I’ll add that property to switch both mechanisms on/off individually.

Right now we have both working by default. They both should coexist in harmony since the execution path of the old XMLRPC is intact and completely isolated from the new one.
I am persisting via the logger all the events of the emulated code. This helps me verify correctness in warm mode.


Ilya Baldin
Director, Networking Research and Infrastructure
RENCI/UNC Chapel Hill

Change History

Changed 5 years ago by ibaldin

  • cc jonmills, pruth, anirban added

It is time to begin the deployment of CouchDB for production use, so we can start using it for ExoGENI.

Claris - we need a plan for how many instances and where should be deployed and how they should be configured (so Jonathan can do it). I'd like to have master-master replication set up upfront.

The first uses for it will be

1. Actor registry
2. Image registry
3. Stitchport registry (top-level)

Later on we may use it for metadata service if we decide Couch is the right way to do it.

Changed 5 years ago by ibaldin

  • summary changed from Testing distributed actor registry to Testing distributed actor registry (aka CouchDB)

Need to know how the orca.properties file changes to use Couch instead of MySQL/jsp based registry of old.

Changed 5 years ago by ibaldin

  • status changed from new to closed
  • resolution set to duplicate

The issues in this ticket have migrated to ORCA5.0 teseting ticket #341. Closing.

Note: See TracTickets for help on using tickets.