ronnie sahlberg | 1 Sep 2011 04:26
Picon

RFC: Readonly record support in ctdb and later samba

List,

CTDB has traditionally only supported exclusive record locks, where
only one single node may be the DMASTER for a record and hold an
authorative version of the record and its data.
This works well for most cifs workloads, but not when you multiple
clients accessing the same record at the same time.

For example when multiple clients read from the same file at the same
time. Each ReadAndX operation requires that the most up to date record
is re-fetched across the cluster network every time to investigate if
it may or may not conflict with a lock.
This both adds high cluster latency since there is an additional
roundtrip across the nodes for every single ReadAndX and also to a
limitation in scalability and performance.

To address this common case where many clients may require to just
read a record like this, we have implemented a shared readonly locks
for ctdb records.
The initial implementation is currently not in master but only in the
master-readonly-records  together with a text document
doc/readonlyrecords.txt

This adds a delegation mechanism where the DMASTER can hand out
special readonly copies of a record to other nodes on request, and
later revoke these delegations in case we need to take out an
exclusive writelock.

This will require some work in samba db_wrap to make it aware of the
new type of cached readonly records in the database and to utilize
(Continue reading)

tridge | 1 Sep 2011 05:25
Picon
Favicon
Gravatar

Re: Endpoint Mapper

Hi Andreas,

 > The implementation of the Endpoint Mapper is complete. All functions needed by
 > Windows clients are supported and fully implemented. In addition we support
 > epm_Insert and epm_Delete over ncalrpc to be able to register and remove
 > endpoints as the system user.

have you been able to confirm that the epm_Insert and epm_Delete
functions are wire compatible with Windows clients/servers? I tried
running the rpc.epmapper test against Windows and it fails with a RPC
fault, which may indicate that the wire format is not correct. Note
that our epmapper.idl doesn't use the same IDL form as the IDL in the
OpenGroup spec, so its quite plausible that we are not wire
compatible.

 > The epmd can detect if a rpc service dies cause of the open connection. If the
 > service dies and the connection is closed we delete the registered endpoints
 > of the service form the database.

this is certainly a good idea

 > The goal should be to use the epmd implementation of Samba3 in the future. The
 > Samba4 epmapper implementation is pretty simple and tied to S4. There is no
 > easy way to register new endpoints from external. 

I'm not convinced that adopting epmd as the normal approach for the
Samba 4.0 release is the right way to go. The 'tied to s4' argument
seems weak given we don't have any plans for another 3.x release.

What about extracting the work you have done into a library, and then
(Continue reading)

ronnie sahlberg | 1 Sep 2011 05:44
Picon

Re: Endpoint Mapper

On Thu, Sep 1, 2011 at 1:25 PM,  <tridge <at> samba.org> wrote:
> Hi Andreas,
>
>  > The implementation of the Endpoint Mapper is complete. All functions needed by
>  > Windows clients are supported and fully implemented. In addition we support
>  > epm_Insert and epm_Delete over ncalrpc to be able to register and remove
>  > endpoints as the system user.
>
> have you been able to confirm that the epm_Insert and epm_Delete
> functions are wire compatible with Windows clients/servers? I tried
> running the rpc.epmapper test against Windows and it fails with a RPC
> fault, which may indicate that the wire format is not correct. Note
> that our epmapper.idl doesn't use the same IDL form as the IDL in the
> OpenGroup spec, so its quite plausible that we are not wire
> compatible.

Do you have a network trace of that?
Many years ago at SNIA you and I saw some weird stuff in EPM on Windows where
it looked like they were using UNIQUE pointers in EPM where there
should have been full pointers.

regards
ronnie sahlberg

John H Terpstra | 1 Sep 2011 05:56
Picon
Favicon

Re: Endpoint Mapper

Pardon top-posting - I am replying purely to place on record the 
following link to info regarding debugging EPM issues in MS Windows. I 
suspect you already know about this KB article, but just FYI here it is:

http://support.microsoft.com/kb/839880

  - John T.

On 08/31/2011 10:25 PM, tridge <at> samba.org wrote:
> Hi Andreas,
>
>   >  The implementation of the Endpoint Mapper is complete. All functions needed by
>   >  Windows clients are supported and fully implemented. In addition we support
>   >  epm_Insert and epm_Delete over ncalrpc to be able to register and remove
>   >  endpoints as the system user.
>
> have you been able to confirm that the epm_Insert and epm_Delete
> functions are wire compatible with Windows clients/servers? I tried
> running the rpc.epmapper test against Windows and it fails with a RPC
> fault, which may indicate that the wire format is not correct. Note
> that our epmapper.idl doesn't use the same IDL form as the IDL in the
> OpenGroup spec, so its quite plausible that we are not wire
> compatible.
>
>   >  The epmd can detect if a rpc service dies cause of the open connection. If the
>   >  service dies and the connection is closed we delete the registered endpoints
>   >  of the service form the database.
>
> this is certainly a good idea
>
(Continue reading)

John H Terpstra | 1 Sep 2011 05:59
Picon
Favicon

Re: Endpoint Mapper

I am chiming in purely to place on record the following link to info 
regarding debugging EPM issues in MS Windows. I suspect you already know 
about this KB article, but just FYI here it is:

http://support.microsoft.com/kb/839880

  - John T.

okmanoj | 1 Sep 2011 06:29

Re: [Server signing] Samba fileshare not working with server signing =auto.

Dear Samba Team,

Any Updates or plan for fixing this.

I have logged a bug in bugzilla #8382. Please comment in this issue.

Regards,
Manoj

--
View this message in context: http://samba.2283325.n4.nabble.com/Server-signing-Samba-fileshare-not-working-with-server-signing-auto-tp3720645p3782760.html
Sent from the Samba - samba-technical mailing list archive at Nabble.com.

Andrew Bartlett | 1 Sep 2011 07:13
Picon
Favicon

Reduce build systems in master

Following up from my mail last month, attached is my proposal to reduce
the build systems we need to maintain to two, the top level waf build
and the autoconf build.

The s3-waf build has been incredibly important in getting us this far,
but I don't we should continue to maintain three build systems now that
the top level build provides all the functionality we need.

Thanks,

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org

Andreas Schneider | 1 Sep 2011 09:56
Picon
Favicon
Gravatar

Re: Endpoint Mapper

On Thursday 01 September 2011 13:25:21 you wrote:
> Hi Andreas,
> 
>  > The implementation of the Endpoint Mapper is complete. All functions
>  > needed by Windows clients are supported and fully implemented. In
>  > addition we support epm_Insert and epm_Delete over ncalrpc to be able
>  > to register and remove endpoints as the system user.
> 
> have you been able to confirm that the epm_Insert and epm_Delete
> functions are wire compatible with Windows clients/servers? I tried
> running the rpc.epmapper test against Windows and it fails with a RPC
> fault, which may indicate that the wire format is not correct. Note
> that our epmapper.idl doesn't use the same IDL form as the IDL in the
> OpenGroup spec, so its quite plausible that we are not wire
> compatible.

I think we have to modify the tests if you want to run them against Windows. 
epm_Insert and epm_Delete are not available on Windows. They are available in 
Samba so we test them.

See

http://msdn.microsoft.com/en-us/library/0beb2488-00a9-4bc4-b7c1-
a24793f99e97(v=PROT.13)

They raise an EPT_S_CANT_PERFORM_OP exception and we do the same if the 
connection is another than NCALRPC.

>  > The epmd can detect if a rpc service dies cause of the open
>  > connection. If the service dies and the connection is closed we
(Continue reading)

theoutlander@o2.pl | 1 Sep 2011 10:15
Picon
Favicon

RE: Samba 4.0 alpha 17 this week?

> I would like to release Samba 4.0 alpha 17 this week, if possible.  We
> have had some pretty important changes in the tree since the last alpha:
>
> Some particular user-visible fixes include
>
>  - fixing the standard process modal
>  - introducing 'samba-tool dbcheck'
>  - supporting renaming a DC into a different site
>  - an improved handling of ./configure options
>  - the start of an upgrade process for Samba3 DCs.
>
> As such, I think it's time our users were able to benefit from these
> changes.
>
> I'll of course seek to ensure that OpenChange builds correctly with this
> release, but if you have any other concerns about the current tree, can
> you please remind me of them, so I can handle them over the next few
> days.
>
> Thanks,
>
> Andrew Bartlett
> --
> Andrew Bartlett                                http://samba.org/~abartlet/
> Authentication Developer, Samba Team           http://samba.org

Hello,

Can someone explain what *supporting renaming a DC into a different
site *exactly
(Continue reading)

Andrew Bartlett | 1 Sep 2011 12:39
Picon
Favicon

RE: Samba 4.0 alpha 17 this week?

On Thu, 2011-09-01 at 10:15 +0200, theoutlander <at> o2.pl wrote:
> Hello,
> 
> Can someone explain what *supporting renaming a DC into a different
> site *exactly
> do? And how to use it?

If you create a site, and you then move a DC into that site, the DC
still works. 

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org


Gmane