Bug 1193649

Summary:	[RFE] Begin migration from Samba 3 to Samba 4
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jose A. Rivera <jarrpa>
Component:	samba	Assignee:	Jose A. Rivera <jarrpa>
Status:	CLOSED ERRATA	QA Contact:	surabhi <sbhaloth>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	annair, bmohanra, jarrpa, nlevinki, pprakash, rcyriac, rjoseph, ssamanta, vagarwal
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	RHGS 3.0.4
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Samba 4.1 provides a large number of performance and feature enhancements that would greatly benefit Red Hat Storage. In addition this would bring Samba in Red Hat Storage closer to the main branch of development for the project which would ensure a greater access to new technologies being developed, such as open source implementations of features found in SMB 3.x.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-26 06:22:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1182947, 1198104

Description Jose A. Rivera 2015-02-17 20:04:52 UTC

We should begin the process of migrating the product from Samba 3 to Samba 4.

Samba 4.1 provides a large number of performance and feature enhancements that would greatly benefit RHS. In addition this would bring Samba in RHS closer to the main branch of development for the project which would ensure a greater access to new technologies being developed such as open source implementations of features found in SMB 3.x. However, while Samba 4 can still serve the same clients Samba 3 can, within a single RHS cluster Samba 4 can not coexist (e.g. serve the same shares) with Samba 3.

In order to best keep up with new feature development while still providing a stable product to our customers, we should begin by making Samba 4 an optional upgrade via a new distribution channel. This way customers currently on Samba 3 can continue to keep their current systems online while planning for adopting the next major release of RHS. At that time we would not longer ship Samba in the base product, and only have Samba 4 available via our new distribution channel.

Comment 4 surabhi 2015-03-24 14:19:35 UTC

Verified the upgrade as follows:

2.1U6 -> 3.0.4 : Upgrade of samba from 3.6.9 to samba4.1 from satellite and CDN repo 
3.0.3 -> 3.0.4 : Upgrade of samba from 3.6.9 to samba4.1 from satellite and CDN repo 

Two upgrade paths:
from 2.1U6 ->3.0.4 : RHS + samba upgrade together
                     First upgrade RHS then upgrade samba

from 3.0.3 ->3.0.4 : RHS + samba upgrade together
                     First upgrade RHS then upgrade samba


For CDN :repo used:
rh-gluster-3-samba-for-rhel-6-server-rpms
For RHN :
rhel-x86_64-server-6-rh-gluster-3-samba

Verified the Install of samba on 3.0.4 ISO.
Verified there is no dependency of samba on redhat-storage-server.
Verified samba is not installed by default on RHS3.0.4, and provided as a seperate group.
Verified group install using groups that has been provided in CDN and RHN stage:
Active Directory Integration
Samba (SMB) server for gluster

Moving the BZ to verified as tested the upgrade paths where we are migrating from samba3.6.9 to samba4.1.

Comment 5 Bhavana 2015-03-25 16:33:44 UTC

Updated the doc text.

Comment 7 errata-xmlrpc 2015-03-26 06:22:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0680.html