Re: Dump/Add users yaml/json

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

In this case, the tool that adds the account should perform a caps check
(for security reasons) and probably use get-or-create/caps (not import)


Le mer. 4 déc. 2024 à 10:42, Albert Shih <Albert.Shih@xxxxxxxx> a écrit :

> Le 03/12/2024 à 18:27:57+0100, David C. a écrit
> Hi,
>
> >
> > (open question, without judgment)
> > What is the purpose of importing users recurrently ?
>
> No the point is not to importing users recurrently.
>
>
> > It seems to me that import is the complement of export, to restore.
> > Creating in ceph and exporting (possibly) in json format is not enough ?
>
> We use puppet to manage our all infrastructure. In our team each person has
> his own speciality. But everyone has a set of «standard» procedures to
> answer «standards tickets» (or level 1 tickets if you prefer).
>
> So with NFS we use puppet to export to client, anyone in our team can add a
> client through puppet. He just have to edit a «standard» file in puppet and
> the puppet go to do his thing to configure the server nfs and the client.
> Even for the person who know nothing how nfs works it's doable.
>
> With cephfs I like to do the same thing, I was able to do that for the
> «first» export by using the some ceph command but that's working only the
> first time (link to the way I do it with puppet).
>
> So the first time, to configure a export cephfs to a client currently the
> member of the team has just to add some
>
>     client_hostname:
>       volume_name:
>         right: rw
>         subvolume: erasure
>         mountpoint: /mountpoint
>
> the puppet module would create/install/configure everything. My colleague
> don't need to learn any ceph command.
>
> But...only the first time...something like
>     client_hostname:
>       volume_name1:
>         right: rw
>         subvolume: erasure
>         mountpoint: /mountpoint
>       volume_name2:
>         right: rw
>         subvolume: erasure
>         mountpoint: /mountpoint2
>
> would not work.
>
> To be more flexible I need to be able to launch ceph command through ruby,
> and it's much more easy to do it with yaml/json because it's native to
> puppet, don't need to add some library to use ini file. It's more easy to
> check if something already exist (so don't do something already here).
>
> Regards.
>
> JAS
> --
> Albert SHIH 🦫 🐸
> Observatoire de Paris
> France
> Heure locale/Local time:
> mer. 04 déc. 2024 10:27:57 CET
>
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux