If RUN is followed by two commands only the return value of second
determines whether RUN was successful or not. This may lead to cases
where docker build succeeds even when it should not.

For example
RUN /bin/false; /bin/true

would be considered a success.

Important thing to consider is that all yum/dnf commands should perform
clean in the same RUN operation if we wish to keep the container image
size small. Running clean in a second RUN operation leads to bigger
image size contrary to expectation because each operation leads to a
layer in the image.

With the above two points considered, I have replaced ";" with "&&"
where necessary and split a single RUN operation to two or many
operations in other places.

Signed-off-by: Raghavendra Talur <rtalur@redhat.com>

Add python-setuptools to install, as it is a requirement with
openstack-newton

Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

This file will be installed during yum install itself.

Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

user.

Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

GLUSTER_VOLUMES -> S3_ACCOUNT
GLUSTER_USER -> S3_USER
GLUSTER_PASSWORD -> S3_PASSWORD

Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

changed the proxy-server.conf to enable authentication and scripts to add user

Signed-off-by: venkata edara <redara@redhat.com>

level directory gluster-object as gluster-s3object

Update README and test scripts to reflect name change.

Signed-off-by: Saravanakumar <sarumuga@redhat.com>