Config & Depot server

dorian.borovina
Beiträge: 34
Registriert: 24 Aug 2017, 12:32

Config & Depot server

Beitragvon dorian.borovina » 15 Nov 2017, 12:50

Hello everyone,

i would appreciate some help on this case.

Location A => Slave (OS Installations, software deployment, testings)
Location B => Master (Software deployment)

The thing is I have OPSI server (Debian 8.8) installed on location A (SLAVE) where we use it for client roll out, OS Installation and some testings.
Now I installed another fresh OPSI server (Debian 8.8) on a remote location B which I would like to use as MASTER server and connect all future OPSI servers to the master.

I fired

Code: Alles auswählen

opsi-setup --register-depot

on location A (SLAVE) and registered depot at config server.
Everything went fine, after I refreshed opsi-configed, another Depot-Server showed up.

The problem is, all my clients and local products from slave server are gone.
Clients are not "existing" on both servers.
Local products are still there on "workbench" and "depot", but they're like uninstalled from server or something.
Like I did some factory reset :D

Backup is restored and everything is back like it was before.

Is there a way to "sync" a slave server with master and vice-versa in order to control all the slaves from master?

Example;

Create a OPSI client on slave or vice-versa, is it visible on master?


Best regards,
Dorian Borovina

Benutzeravatar
n.wenselowski
Beiträge: 2823
Registriert: 04 Apr 2013, 12:15

Re: Config & Depot server

Beitragvon n.wenselowski » 17 Nov 2017, 14:47

Hi Dorian,

the terms used are usually configserver for the server holding metadata and depot(server) for the ones holding installation data.
A depot does not hold any metadata but instead relies all requests to the config server.

If you now register your old configserver (server A) to a new configserver (server B) your location A server get's demoted to a depot.
What you miss here is migrating all the data from server A to the server b before doing so.


Kind regards

Niko
Kein Support per DM!
_________________________
opsi support - uib gmbh
For productive opsi installations we recommend support contracts.

dorian.borovina
Beiträge: 34
Registriert: 24 Aug 2017, 12:32

Re: Config & Depot server

Beitragvon dorian.borovina » 27 Nov 2017, 13:31

Hi Niko,

Thank you very much for your answer.

I will try it out and let you know about the outcome.

n.wenselowski hat geschrieben:Hi Dorian,

the terms used are usually configserver for the server holding metadata and depot(server) for the ones holding installation data.
A depot does not hold any metadata but instead relies all requests to the config server.

If you now register your old configserver (server A) to a new configserver (server B) your location A server get's demoted to a depot.
What you miss here is migrating all the data from server A to the server b before doing so.


Kind regards

Niko

dorian.borovina
Beiträge: 34
Registriert: 24 Aug 2017, 12:32

Re: Config & Depot server

Beitragvon dorian.borovina » 19 Feb 2018, 12:41

Hi Niko,

Sorry for the late response.
I took me some time to research and figure out how does it work.
Now I'm able to send commands from the Config to the Depot server.
This was the idea I wanted to accomplish.

Admin => Config server => Depot server => End device

Best regards! :D