OPSI.Backend.BackendManager module

BackendManager.

If you want to work with an opsi backend in i.e. a script a BackendManager instance should be your first choice. A BackendManager instance does the heavy lifting for you so you don’t need to set up you backends, ACL, multiplexing etc. yourself.

copyright:uib GmbH <info@uib.de> author:Jan Schneider <j.schneider@uib.de> author:Niko Wenselowski <n.wenselowski@uib.de> license:GNU Affero General Public License version 3

class OPSI.Backend.BackendManager.BackendAccessControl(backend, **kwargs)

Bases: object

accessControl_authenticated()

accessControl_userIsAdmin()

accessControl_userIsReadOnlyUser()

class OPSI.Backend.BackendManager.BackendDispatcher(**kwargs)

Bases: OPSI.Backend.Backend.Backend

backend_exit()

backend_getOptions()

backend_setOptions(options)

dispatcher_getBackendNames()

dispatcher_getConfig()

class OPSI.Backend.BackendManager.BackendExtender(backend, **kwargs)

Bases: OPSI.Backend.Backend.ExtendedBackend

class OPSI.Backend.BackendManager.BackendManager(**kwargs)

Bases: OPSI.Backend.Backend.ExtendedBackend

The BackendManager manages the backend and glues together various parts.

This includes extending the backends, dispatching calls to backends, limiting the access through ACL.

backend_exit()

class OPSI.Backend.BackendManager.MessageBusNotifier(startReactor=True)

Bases: OPSI.Backend.Backend.BackendModificationListener

backendModified(backend)

objectInserted(backend, obj)

objectUpdated(backend, obj)

objectsDeleted(backend, objs)

stop()

OPSI.Backend.BackendManager.backendManagerFactory(user, password, dispatchConfigFile, backendConfigDir, extensionConfigDir, aclFile, depotId, postpath, context, **kwargs)