Re: cephadm: Whether remoto can be replaced by paramiko

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

 



Hi Sebastia,

Wow, it is very suitable for our scene.

The version of ceph cluster which we are using is Octopus. So we want to backport some code of  Quincy whose are relative to asyncssh to Octopus.

Besides, we just modify a little bit code to fit the scene which connect with ssh by password. The method is as follows:
asyncssh.connect(... password=self.mgr.ssh_password ....)
How do you think of that? Look forward to receiving your reply.
Thank you very much.



Sebastian Wagner <sewagner@xxxxxxxxxx> 于2021年11月9日周二 下午9:11写道:

Hi hongloumeng,

turns out we already replaced remoto in Quincy with asyncssh. Do you want to have a quick look (Not for production obviously), if Quincy will support this setup?

Thanks, Sebastian

Am 09.11.21 um 08:20 schrieb hongloumeng a:
Hi,
We have some cases that the ssk key is not permitted when deploy ceph cluster by means of cephadm. And password is not supported by the remoto module of python. So we want to use the paramiko module of python.

Does the approach work? Thanks very much.

Best regards

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx

[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux