gluster-block: listen on unix and inet

from now We basically have 2 RPC connections,
1. Between gluster block CLI and local gluster-blockd
   This connection is basically UNIX/local netid ,listening on
   /var/run/gluster-blockd.socket file.

The CLI always Send/Receive the commands to/from the local
gluster-blockd via local rpc.

2. Between gluster-blockd's, i.e local (to cli) gluster-blockd and the
   gluster-blockd's running on remote(blockhost)
   This is the tcp connection. The rpc requests are listening on 24006

Also from now gluster-blockd is multi threaded (As of now 2 threads)

Lets consider the Create Request to understand what each thread solves

Thread1 (THE CLI THREAD)
 * Listening on local RPC
 * Generate the GBID (UUID) and create the entry with name GBID in the
   given volume with a requested size.
 * And Send the Configuration requests to remote hosts,
   waits for the replies
   (HINt: after this point Read Thread2 and come back)
 * Return to CLI.

Thread 2 (THE SERVER THREAD)
 * Listens on 24006
 * On Receiving an event, read the structure.
 * Executes the required "targetcli bla bla bla" command locally
 * Fills the command exitcode and the output in the RPC reply structure
   and send reply

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/glfs-operations.h b/glfs-operations.h
index dd3992b..1a1208d 100644
--- a/glfs-operations.h
+++ b/glfs-operations.h
@@ -19,6 +19,8 @@
 
 # include  <glusterfs/api/glfs.h>
 
+# include  "rpc/block.h"
+
 
 
 typedef struct glusterBlockDef {
@@ -31,8 +33,8 @@ typedef struct glusterBlockDef {
 typedef glusterBlockDef *glusterBlockDefPtr;
 
 
-int glusterBlockCreateEntry(glusterBlockDefPtr blk);
+int glusterBlockCreateEntry(blockCreateCli *blk, char *gbid);
 
-int glusterBlockDeleteEntry(glusterBlockDefPtr blk);
+int glusterBlockDeleteEntry(blockCreateCli *blk, char *gbid);
 
 #endif /* _GLFS_OPERATIONS_H */