Added release notes

- Granular Entry self-heal for AFR
- Gdeploy packaged for Fedora and EPEL
- Glusterfind and Bareos Integration
- Heketi

Change-Id: Ie40bf46951862ec674e5557fe3dc81b3f72abb36
BUG: 1317278
Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
Reviewed-on: http://review.gluster.org/14725
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>

1 files changed, 41 insertions, 3 deletions

diff --git a/doc/release-notes/3.8.0.md b/doc/release-notes/3.8.0.md
index 2c8f13fcc60..3f06a5e9ef5 100644
--- a/doc/release-notes/3.8.0.md
+++ b/doc/release-notes/3.8.0.md
@@ -29,8 +29,6 @@ parameters.
 Building directly from the git repository has not changed.
 
 
-### FIXME: insert more useful release notes here
-
 ### Mandatory lock support for Multiprotocol environment
 *Notes for users:*
 With this release GlusterFS is now capable of performing file operations based
@@ -61,7 +59,7 @@ command:
 ```
 
 Existing volumes that have gnfs enabled will remain enabled unless explicitly
-disabled. You cannot run both gnfs and NFS-Ganesha servers on the same host. 
+disabled. You cannot run both gnfs and NFS-Ganesha servers on the same host.
 
 The plan is to phase gnfs out of Gluster over the next several releases,
 starting with documenting it as officially deprecated, then not compiling and
@@ -194,6 +192,46 @@ The current implementation is experimental. Hence it is not recommended for a
 production environment. This feature is planned to be stabilized in future
 releases.  Feedback from the community is welcome and greatly appreciated.
 
+### Granular Entry self-heal for AFR
+*Notes for users:*
+This feature can be enabled using the command
+
+```bash
+gluster volume set <vol-name> granular-entry-heal on
+```
+
+*Limitations:*
+1) The feature is not backward compatible. So please enable the option only after you have upgraded all your clients and servers to 3.8 and op-version is 30800
+2) Make sure the volume is stopped and there is no pending heal before you enable the feature.
+
+### Gdeploy packaged for Fedora and EPEL
+*Notes for users:*
+With gdeploy, deployment and configuration is a lot easier, it abstracts the complexities of learning and writing YAML files. And reusing the gdeploy configuration files with slight modification is lot easier than editing the YAML files, and debugging the errors.
+Setting up a GlusterFS volume involves quite a bit of tasks like:
+1. Setting up PV, VG, LV (thinpools if necessary).
+2. Peer probing the nodes.
+3.  CLI to create volume (which can get lengthy and error prone as the number of nodes increase).
+
+gdeploy helps in simplifying the above tasks and adds many more useful features like installing packages, handling volumes remotely, setting volume options while creating the volume so on...
+
+*Limitations:*
+We cannot have periodic status checks or similar health monitoring of the Gluster setup using gdeploy.
+So it does not keep track of the previous deployments you have made. You need to give every detail that gdeploy would require at each stage of deployment as it does not keep any state.
+
+### Glusterfind and Bareos Integration
+*Notes for users:*
+This is a first integration of Gluster with a Backup & Recovery Application. The integration enabler is a Bareos plugin for Glusterfs and a Gluster python utility called glusterfind. The integration provides facility to backup and restore from and to Glusterfs volumes via the libgfapi library which interacts directly with the Glusterfs server and not via a Glusterfs mount point.
+During the backup operation, the glusterfind utility helps to speed up full file listing by parallelly running on bricks' back-end  instead of using the more expensive READDIR file operation needed when listing at a mount point. For incremental changes, the glusterfind utility picks up changed files from file system changelogs instead of crawling the entire file system scavenging for the files' modification time.
+
+*Limitations:*
+Since bareos intrerfaces with Glusterfs via the libgfapi library and needs to execute the glusterfind tool, bareos needs to be running on one of the Gluster cluster nodes to make the most of it.
+
+### Heketi
+*Notes for users:*
+Heketi provides a RESTful management interface which can be used to manage the life cycle of GlusterFS volumes. With Heketi, cloud services like OpenStack Manila, Kubernetes, and OpenShift can dynamically provision GlusterFS volumes with any of the supported durability types
+
+*Limitations:*
+Currently, Heketi only provides volume create, delete, and expand commands.
 
 ## Bugs addressed