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(a)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
>> 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).
To be precise, please see sections: 3.1.1, and 3.1.2
> 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.
>> Alberto Viana
>> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
>> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
> William Brown
> Senior Software Engineer, 389 Directory Server
> SUSE Labs
> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
389 Directory Server Development Team