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

Problem
    gluster-blockd using POSIX signal handling but it not includes signal.h

Change-Id: Iecb3a17d70226a894bfe9a6fb5b8382d87afde7f
Signed-off-by: Ji-Hyeon Gim <potatogim@potatogim.net>

change in GB_TGCLI_GLOBALS macro:
's/set global/targetcli set global/' followed by a saveconfig

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

Currently, on each targetcli create call, rtslib will rebuild its bs_cache, so
as the /sys/kernel/config/target/core dir gets more entries this takes longer
and longer to scan. Hence using repetitive targetcli in the block create
for creating iqn, backend, setting acls, setting globals will induce too
much delay in block create. As the number of blocks on the node increases,
the delay will be too longer.

This does not happen if we open targetcli in interactive mode and just do
multiple create commands form it, since the bs_cache is build once.

Read More:
https://goo.gl/8aYT38

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

Currently the default logdir is DATADIR /log/gluster-block/

This patch will provide a way to change this default logdir via Env variable
$ export GB_LOGDIR=/var/log/gluster-block-new-path/

Note: make sure to restart the processes (cli & daemon) after you set GB_LOGDIR

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

In cases when svc_register fails, gluster-blockd will print the
reason and terminate gracefully.

Fixes: #26
Change-Id: Ia243771d99fbaa674f317e7c8e64174f4d8d6234
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

Change-Id: I9dd396737a6719fe3828ec3e9c26bfd8aa1da238
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

This patch adds '--log-level' options

supported log levels:
{
   "NONE",
   "ERROR",
   "WARNING",
   "INFO",
   "DEBUG",
   "TRACE"
}

TRACE being max logging

$ gluster-blockd --help
[...]
  --log-level <LOGLEVEL>
        Logging severity. Valid options are,
        TRACE, DEBUG, INFO, WARNING, ERROR and NONE [default: INFO]
[...]

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

$ gluster-blockd --help
gluster-blockd (0.2)
usage:
  gluster-blockd [--glfs-lru-count <count>]

commands:
  --glfs-lru-count <count>
        glfs objects cache capacity [max: 512] (default: 5)
  --help
        show this message and exit.
  --version
        show version info and exit.

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

Problem:
-------

1. Currently, each cli command take ~5 secs for execution. The Maximum
latency is due to initializing a glfs object (glfs_init() and friends).

2. OOM kills due to glfs_fini() leaks (~10MB per object)

Solution:
--------

Caching bipasses glfs_init() calls from the very next command, as in the first
command it goes via the glfs_init route, since there will be cache miss.
Hence with caching cli command on a local machine should take ~1 sec.

ATM, the cache query looks at the volume name only, as the host name will be
localhost in our case and transport will be tcp 24007 always.

The default cache capacity is 5 i.e there can be a max of five glfs entries in
the cache, anything more will lead to release of least recently used object.

This way, if there are <= 5 volume in use for block, there will be no
glfs_fini() calls, hence no leaks, no OOM's.

The next patch will help in making cache capacity configurable.

Change-Id: Ia891451cb92cf09959c1aff85976d78302ec7014
Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
[ndevos: correct compiling+linking against libgfapi.so]