Bug 144508 - Use RPC instead of signal for doing CCS updates
Summary: Use RPC instead of signal for doing CCS updates
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: ccs
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jonathan Earl Brassow
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-07 20:53 UTC by Jonathan Earl Brassow
Modified: 2009-04-16 20:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-01-11 23:43:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan Earl Brassow 2005-01-07 20:53:12 UTC
Description of problem:

A signal is currently used to tell ccsd to update a config file.  This
has a number of limitations:
1. signals are asynchornous, making it hard to error results
2. Although I believe most issues have been worked out, signals can be
recieved at any time, making the code more complex because it has to
do various forms of locking to ensure that processing doesn't happen
while things are changing

The code complexities and various hacks to do meaningful error
reporting should be replaced by a more eligant solution.  That
solution involves ccs_tool taking an update file and sending it to
ccsd for processing.

Because a sizeable amount of code will have to be changed to
facilitate this, it may not be advisable to change the code so close
to a release.

Comment 1 Jonathan Earl Brassow 2005-01-11 23:43:57 UTC
update now uses socket to communicate with ccsd to do updates rather
than signals.


Note You need to log in before you can comment on or make changes to this bug.