All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
	Pavel Shilovsky <piastryyy@gmail.com>,
	"Kenneth D'souza" <kdsouza@redhat.com>,
	Ronnie Sahlberg <lsahlber@redhat.com>
Subject: Re: [PATCH 2/2] smbinfo: rewrite in python
Date: Tue, 15 Oct 2019 15:29:47 +1000	[thread overview]
Message-ID: <CAN05THRgk3t=snmey6QJ-H5tBPx4Re5ccOXrXm6OsTSVYWb4BA@mail.gmail.com> (raw)
In-Reply-To: <87a7a3b67w.fsf@suse.com>

Very nice, thanks for doing this!

Does this make the other python tools we have in cifs-utils obsolete?
I don't think so.

I think we should keep both smbinfo as well as the dedicated tools.
Leave smbinfo as a generic read and dump the info to the screen
utility for any/all types of info,
but additionally have specialized tools that are much more complex for
some specific tasks.

What comes to my mind here would be specialized tools for quota,
security descriptors, snapshots to start with.
These tools would be much more specialized than smbinfo and also
provide command line arguments (and optional GUI)
to set and mutate the object they operate on.
I.e. do a lot of things that would possibly be outside the scope of smbinfo.

For quota for example I could imagine it having an optional GUI as
well as command line arguments to also SET the quota.
Maybe having integration with winbind to allow mapping SIDs to/from
Account Names,
possibly even having a configuration file so that a hypothetical
smb2-quota --check   would check the quota limits and provide
alerts/emails based on the configuration file.

I.e. full blown utility to manage the quota as well as a "--check"
command that can be run as a cron job.


For snapshots it would be nice with a dedicated tool, with optional
GUI, that would list all mounted cifs filesystems,
and possibly also read additional server/shares from a configuration
file that would allow you to fully manage snapshots, including
mounting and unmounting them.
I.e. everything you can do from windows explorer you should be able to
do from this tool.
Of course we are not nearly there yet but we have to start from
somewhere and it is just a matter of continue to incrementally improve
these tools.


We could of course do this to smbinfo too but I think it would be
better to keep these specialized tools as separate programs
even if there is some functionality overlap between them and smbinfo.


regards
ronnie sahlberg

On Tue, Oct 15, 2019 at 3:19 AM Aurélien Aptel <aaptel@suse.com> wrote:
>
>
> Note that I haven't tested the `quota` and `list-snapshots` sub-commands
> as I don't know how to set that up easily on my Windows Server vm (let
> me know how if you know, thx) so please give it a try, these are
> untested.
>
> Cheers,
> --
> Aurélien Aptel / SUSE Labs Samba Team
> GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
> SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
> GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)

  reply	other threads:[~2019-10-15  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 17:07 [PATCH 2/2] smbinfo: rewrite in python Aurelien Aptel
2019-10-14 17:13 ` Aurélien Aptel
2019-10-15  5:29   ` ronnie sahlberg [this message]
2019-12-13  0:33 ` Pavel Shilovsky
2019-12-17 22:36   ` Pavel Shilovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN05THRgk3t=snmey6QJ-H5tBPx4Re5ccOXrXm6OsTSVYWb4BA@mail.gmail.com' \
    --to=ronniesahlberg@gmail.com \
    --cc=aaptel@suse.com \
    --cc=kdsouza@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=piastryyy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.