Releasing Samba 4.0 RC1?

[Juan Pablo Lorier]

Hi Denis,

Glad to hear your experience with samba 4, just let me tell you that 
I've been trying to set it to work aside a couple of windows DCs keeping 
all the domain intact until I can securely turn of windows and I've been 
unable to get it to work (most likely for I'm no so qualified as I 
should, though I'm not a rookie) and have talked to others users that 
had problems too. I'm also aware that many people managed to get it to 
work, but maybe they have other scenarios, some I know just started with 
a brand new domain, which I can't as I've have to deal with a company 
with over 100 hosts and almost 200 users.
Anyway, nothing further to my intentions than criticizing Samba, I'm a 
huge fun and I'm really enthusiast of having Samba 4 asap as I've been 
waiting for it for over 2 years now, but I felt the need to show my 
concerns.
There's no point in having a final release that you may "sell" and after 
selling it you have to deal with problems that create a bad image of the 
product. Again, I'm not up to date with the betas as I'm not in the 
office, I need to try all the hard work the team has managed to offer us 
in fixing and improving the product.
Hope I could get to explain myself, don't want to create noise in a list 
meant for technical contribution.
Regards,

Juan Pablo Lorier


On 17/08/12 10:00, Denis Cardon wrote:
> Hi Juan,
>
>> First my apologies as I know this threat is not for users, but I just
>> wanted to add an "outside" point of view.
> >
>> You are doing a great job with samba4 and us, the users, are eager to
>> use it in our production environments, but I think that you shouldn't
>> rush to the RC before having fixed some mayor (at my point of view)
>> features as many users will be encouraged to get samba running and they
>> may disappoint after having issues or even corruption of their
>> production environments.
>
> a sysadmin ought to read the release notes before deployement. 
> Otherwise he should stick to the "buy and click" kind of software so 
> he may harrass some tech support when he will have screwed up his 
> network.
>
> I have been using samba4 in non-critical production environement for a 
> year (3 primary schools, 2 libraries, 3 SMBs, total around 90 windows 
> workstations) with only a few minor hiccups.
>
> And with the project going forward, everything is going so smoothly 
> now that one can get an AD setup by just typing apt-get samba4, 
> modifying 2 files and lauching one command line...
>
> Proposing an infrastructure with software that is tagged as "Beta" is 
> not an easy sale, even if stability is well tested and rock solid in 
> simple target setup (no replication, no forest, etc.). I'm eager to 
> see this great samba4 project going to RC then to Release so that it 
> becomes and easy sell for SMBs and then larger networks.
>
> Granted I always setup a separate samba3 member server for file and 
> print service, but in a world where virtualisation is ubiquitous, it 
> should not make a sysadmin afraid (at least not the sysadmin that 
> would deploy an AD).
>
> Cheers,
>
> Denis
>
>> In my opinion, an RC should be for a product that you have almost
>> completed and need more testing to get new bugs you just missed, but at
>> this time, you already have many important bugs waiting to get time to
>> be fixed.
>> I'm trying to get samba to substitute windows but domain controller is
>> not working properly yet, so I'm not even trying to test s3fs just to
>> pile up more problems. But I'm a fun of your work and I'll keep trying
>> until I'll get it working, others may not have such enthusiasm and just
>> think "this doesn't work, I'm not wasting time... let's keep windows".
>> Again, just an user's opinion.
>> Regards,
>>
>> Juan Pablo Lorier
>>
>> PS: I'll be back from vacation next week and I'll try this new betas :-)
>>
>
>