Le 01/12/2024 à 13:13:35+0100, Joachim Kraftmayer a écrit Hi,

I think json format is not supported to add or change users.

S*it ;-) ;-)

But you could use:

https://docs.ceph.com/en/reef/rados/operations/user-management/#importing-a-...

and the -i is also available for ceph auth add and other commands.

https://docs.ceph.com/en/reef/rados/operations/user-management/#adding-a-use...

Yeah...I already check that. But that's mean I would need to edit some ini style file. And I don't like that. Especially when the purpose is to do that with some script. Anyway thanks. Regards -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: mar. 03 déc. 2024 13:27:23 CET

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

Hi Albert, we are working at the moment on a new ceph-api. https://github.com/clyso/ceph-api you can open an issue and I will discuss it with the team. Regards, Joachim joachim.kraftmayer@clyso.com www.clyso.com Hohenzollernstr. 27, 80801 Munich Utting | HR: Augsburg | HRB: 25866 | USt. ID-Nr.: DE275430677 Am Mi., 4. Dez. 2024 um 14:06 Uhr schrieb David C. <david.casier@aevoo.fr>:

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@obspm.fr> 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@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io