Hi Guys,
In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI? Should I install a cockpit plugin to each 389 machine in my environment? Any docs about it?
Thanks
Alberto Viana
On 14 Dec 2019, at 11:07, Alberto Viana albertocrj@gmail.com wrote:
Hi Guys,
In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI? Should I install a cockpit plugin to each 389 machine in my environment? Any docs about it?
Yes, you'll need a cockpit plugin per-machine for the instances on that machine.
There are things that cockpit can do that requires local filesystem access, that's why you can't remotely administer it with this.
If you want remote administration capability, I'd advise you look into dsconf as a tool which can do remote administration and you could script it to perform tasks repeatedly.
Thanks
Alberto Viana _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs
On 12/13/19 8:29 PM, William Brown wrote:
On 14 Dec 2019, at 11:07, Alberto Viana albertocrj@gmail.com wrote:
Hi Guys,
In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI? Should I install a cockpit plugin to each 389 machine in my environment? Any docs about it?
You can install the cockpit-bridge package on remote servers and then register then in your local cockpit instance. Then you can switch between machines from a single interface. It's not the exact same thing as the old console, but the result is the same (from a central location you can manage all your systems).
https://cockpit-project.org/guide/0.82/cockpit-bridge.8.html
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...
HTH,
Mark
Yes, you'll need a cockpit plugin per-machine for the instances on that machine.
There are things that cockpit can do that requires local filesystem access, that's why you can't remotely administer it with this.
If you want remote administration capability, I'd advise you look into dsconf as a tool which can do remote administration and you could script it to perform tasks repeatedly.
Thanks
Alberto Viana _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
On 12/15/19 8:06 PM, Mark Reynolds wrote:
On 12/13/19 8:29 PM, William Brown wrote:
On 14 Dec 2019, at 11:07, Alberto Viana albertocrj@gmail.com wrote:
Hi Guys,
In the old 389-console was possible to manage remote instances (installations in different machines) and what about in new UI? Should I install a cockpit plugin to each 389 machine in my environment? Any docs about it?
You can install the cockpit-bridge package on remote servers and then register then in your local cockpit instance. Then you can switch between machines from a single interface. It's not the exact same thing as the old console, but the result is the same (from a central location you can manage all your systems).
https://cockpit-project.org/guide/0.82/cockpit-bridge.8.html
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...
To be precise, please see sections: 3.1.1, and 3.1.2
HTH,
Mark
Yes, you'll need a cockpit plugin per-machine for the instances on that machine.
There are things that cockpit can do that requires local filesystem access, that's why you can't remotely administer it with this.
If you want remote administration capability, I'd advise you look into dsconf as a tool which can do remote administration and you could script it to perform tasks repeatedly.
Thanks
Alberto Viana _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
389-users@lists.fedoraproject.org