Misplaced Pages

Opsi: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 15:05, 3 January 2011 editOpsidoc (talk | contribs)6 edits Update screenshot← Previous edit Revision as of 09:33, 6 January 2011 edit undoOpsidoc (talk | contribs)6 edits Text update to opsi 4Next edit →
Line 14: Line 14:
}} }}


'''Opsi''' (open pc server integration) is a software distribution and management system for ] Clients, based on ] servers. '''Opsi''' (open pc server integration) is a software distribution and management system for ] Clients, based on ] servers. Opsi is developed and maintained by uib gmbh from Mainz, Germany.
⚫ The main parts of of opsi are ] licensed under the ]<ref>http://www.opsi.org/license/</ref>.


== Features == == Features ==


The core features<ref>http://www.opsi.org/features/</ref> of opsi are: The key features<ref>http://www.opsi.org/features/</ref> of opsi are:


* Automatic operating system installation (OS Deployment) * Automated operating system installation (OS deployment)
* Software distribution * Software distribution
* ]-Management * ]-Management
* Inventory (Hardware and Software) * Inventory (Hardware and Software)
* License Management / ] * License Management / ]
* Administrative Tasks (])


A tools for automated installations is important and necessary for standardization, maintainability and cost saving of larger PC networks.
⚫ Developer and maintainer is the company uib gmbh in Mainz, Germany. The product is ] licensed under the ]<ref>http://www.opsi.org/license/</ref>.


Supported client operating systems are ], ], ], ]. Support for ], ] and ] is available, but subject to a ] and not released as open source yet. For the installation of an opsi-server there are packages available for the Linux distributions ], ] and ]. opsi Supports the client operating systems ], ], ], ], ] and ]. The 32- and the 64-bit versions are supported. For the installation of an opsi-server there are packages available for the Linux distributions ], ], ], Univention Corporate Server, ], ] and ].


== Automatic operating system installation == == Automated operating system installation ==

⚫ Via management interface a client may be selected for OS-Installation. If the client boots via ]it loads a ] from the opsi-depotserver. This bootimage prepares the hard disk, copies the required installation files, drivers and the opsi client agent and starts finally an ]. Opsi uses the automatic detection of the necessary drivers for PCI-, HD-Audio- and USB-Devices. OS-installation via ] is also supported.


Via management interface a client may be selected for OS-Installation. If the client boots via ]
⚫ it loads a ] from the opsi-depotserver. This bootimage prepares the hard disk, copies the required installation files, drivers and the opsi client agent and starts finally an ]. An OS-installation via ] is also supported.


== Software distribution == == Software distribution ==


For the automatic software distribution a client agent (the opsi-preloginloader) has to be installed on the client. For the automatic software distribution some software, the opsi-client-agent, has to be installed on each client.
Every time the client boots the opsi-client-agent connects to the opsi-server and asks if there is anything to install (default).
This client agent starts at boot time, connects to the opsi configuration-server and starts if scheduled a script driven installation program (opsi-winst) which installs the required software on the client. During the installation process the user login can be blocked for integrity reasons. To integrate a new software packet into the software deployment system, a script must be written to specify the installation process. This script provides all the information on how this software packet has to be installed ] or by using tools like ] or ]. If this shall be done a script driven installation program (opsi-winst) starts and installs the required software on the client. During the installation process the user login can be blocked for integrity reasons. To integrate a new software packet into the software deployment system, a script must be written to specify the installation process. This script provides all the information on how this software packet has to be installed ] or by using tools like ] or ]. With the opsi-winst steps like copy files or edit the registry can be done.
The the opsi-client-agent can also be triggered by other events or via push-installation from the opsi-server


== Patch-Management == == Patch-Management ==
Line 47: Line 49:
== Inventory (Hardware and Software) == == Inventory (Hardware and Software) ==


The Hard- and Software Inventory uses also the opsi client agent. The Hardware Information is collected via calls to ] while the Software Information is gathered from the ]. The inventory data are sent back to the opsi-configuration-server by ]. The Hard- and Software Inventory also uses the opsi-client-agent. The hardware information is collected via calls to ] while the Software Information is gathered from the ]. The inventory data are sent back to the opsi-server by ]. The inventory data may imported via web service to a ] e.g. in ]. <ref>http://www.cape-it.de/product-kix4otrs.html</ref>


== License Management / ] == == License Management / ] ==
The opsi License Management module supports the administration of different kinds of licenses like Retail, OEM and Volume licenses. It keeps track of the licenses that are used while the ]. Using the connection between the License Management and the software inventory, ] reports on the number of free and installed licenses can be generated. The License Management module is part of a ] and not released as open source yet. The opsi License Management module supports the administration of different kinds of licenses like Retail, OEM and Volume licenses. It counts the licenses that are used with the ]. Using the combination of the License Management and the software inventory, ] reports on the number of free and installed licenses can be generated. The License Management module is part of a ] and not released as open source yet.

== Administrative tasks (Configuration Management) ==

The opsi client runs a script in a administrative context, which can be used also for configuration purpose.
The opsi script interpreter supports:
* Start of programs and exit code detection
* Detection of the running OS, language and national settings as well as evaluation of Ini-files, text files, registry entries and environment variables
* Editing of registry, start menu and desktop entries, Ini-files, XML files and text files
* Editing of user specific profile registry entries and files (in case of not using 'roaming profiles')
* Calling external programs and scripts, catch and provide their output as variables for further processing
* File copy with or without version control


== opsi-server == == opsi-server ==


The opsi server provides the following services: The opsi server provides the following services:
* The configuration-server stores the configuration data for the clients and the software packages. For the data storage a file- or ] based storage can be chosen. For administration of these data the configuration-server provides a graphical management interface via https as well as a command line interface. * The configuration-server stores the configuration data of the clients and provides the methods to manage these data via web service or command-line based. The data can be stored in files, in ] or in a ] Database.
* The depot-server stores software packages that may be installed by the clients. To provide support for multiple locations, multiple depot-servers may be controlled by one configuration-server. * The depot-server stores software packages that may be installed on the clients. To provide support for multiple locations, multiple depot-servers may be controlled by one configuration-server.
* A ]-Server provides the ]s for the OS-Installations. * A ]-Server provides the ]s for the OS-Installations.
* A ]-Server may be integrated in the opsi-server * A ]-Server may be integrated in the opsi-server


== Management-Interface == == Management-Interface ==
For the management of opsi there is a graphical user interface<ref>http://www.opsi.org/screenshots/</ref>, which is available as application as well as Browser ]. For managing opsi a graphical user interface<ref>http://www.opsi.org/screenshots/</ref> is available as an application or as a Browser ].
Management is also possible with a command line tool or via ]<ref>http://download.uib.de/opsi_stable/doku/opsi-manual-en.pdf, Chapter opsi-admin</ref>. Management is also possible with a command line tool or via ]<ref>http://download.uib.de/opsi_stable/doc/opsi-manual-stable-en.pdf , Chapter opsi-admin</ref>.

== License ==
The opsi core features are ] according to the ] Version 3 and are free of charge.
The core features are software distribution (or ]), OS deployment and hard- and software-inventory.
These free components can be supplemented with ] add-ons that are fee required. They are called ] <ref>http://www.opsi.org/license/</ref>.



== Co-funding Projects == == Co-funding Projects ==
Even though opsi is open source, there are some components which are not free at the moment. These components are developed in a co-funding project which means that until the complete development costs are paid by co-funders, they are only allowed to use by the co-funders or for evaluation purposes. Even though opsi is open source, there are some components which are not for free at the moment. These components are developed in a co-funding project. This means, that these parts are only available for those customers who paid a contribution to the cost of development. As soon as the development of a co-funding project is refinanced, the component will be part of the free opsi-version and can be used free of charge. It will be open source (as long as not prevented caused by technical reasons). The first of these co-funding Projects was the opsi support for ]/]. It was completed on 1st of February 2008 and is free of charge since 1st of March 2010. The source code was divided form the not yet paid parts and is open source since since 30th of November 2010.
At the moment (January 2011) there are three co-funding projects: Treewiew allows to build hierarchical groups of clients to manage them, MySQL as backend for all data and the license management module.
The main focus of co-funding projects is to create software once for a pool of purchaser who share the cost and make it open source as soon as it paid in full <ref>http://uib.de/en/opsi%20cofunding/index.html</ref> <ref>http://www.opsi.org/statistics/cofunding%20opsiclientd/</ref>.


==References and sources== ==References and sources==
Line 83: Line 82:
== External links == == External links ==
* http://opsi.org * http://opsi.org
* http://www.linux-magazine.com/Issues/2009/108/Opsi


] ]

Revision as of 09:33, 6 January 2011

opsi
opsi management interface
Developer(s)uib gmbh, Mainz, Germany
Stable release4.0 / 1. oct 2010
Repository
Written inPython Java
Operating systemLinux, Windows
Available inEnglish, French, German, Spanish, Turkish
TypeNetwork management System administration
LicenseGPL
Websitehttp://www.opsi.org/

Opsi (open pc server integration) is a software distribution and management system for Windows Clients, based on Linux servers. Opsi is developed and maintained by uib gmbh from Mainz, Germany. The main parts of of opsi are Open Source licensed under the GNU General Public License.

Features

The key features of opsi are:

  • Automated operating system installation (OS deployment)
  • Software distribution
  • Patch-Management
  • Inventory (Hardware and Software)
  • License Management / Software Asset Management

A tools for automated installations is important and necessary for standardization, maintainability and cost saving of larger PC networks.

opsi Supports the client operating systems Windows XP, Server 2003, Windows Vista, Server 2008, Windows 7 and Server 2008R2. The 32- and the 64-bit versions are supported. For the installation of an opsi-server there are packages available for the Linux distributions Debian, Ubuntu, SLES, Univention Corporate Server, CentOS, RHEL and OpenSuse.

Automated operating system installation

Via management interface a client may be selected for OS-Installation. If the client boots via PXEit loads a boot image from the opsi-depotserver. This bootimage prepares the hard disk, copies the required installation files, drivers and the opsi client agent and starts finally an unattended OS-Installation. Opsi uses the automatic detection of the necessary drivers for PCI-, HD-Audio- and USB-Devices. OS-installation via Disk image is also supported.


Software distribution

For the automatic software distribution some software, the opsi-client-agent, has to be installed on each client. Every time the client boots the opsi-client-agent connects to the opsi-server and asks if there is anything to install (default). If this shall be done a script driven installation program (opsi-winst) starts and installs the required software on the client. During the installation process the user login can be blocked for integrity reasons. To integrate a new software packet into the software deployment system, a script must be written to specify the installation process. This script provides all the information on how this software packet has to be installed silent or unattended or by using tools like AutoIt or Autohotkey. With the opsi-winst steps like copy files or edit the registry can be done. The the opsi-client-agent can also be triggered by other events or via push-installation from the opsi-server

Patch-Management

The mechanism of the software deployment can also be used to deploy software patches and hotfixes.

Inventory (Hardware and Software)

The Hard- and Software Inventory also uses the opsi-client-agent. The hardware information is collected via calls to WMI while the Software Information is gathered from the registry. The inventory data are sent back to the opsi-server by web service. The inventory data may imported via web service to a CMDB e.g. in OTRS.

License Management / Software Asset Management

The opsi License Management module supports the administration of different kinds of licenses like Retail, OEM and Volume licenses. It counts the licenses that are used with the software deployment. Using the combination of the License Management and the software inventory, Software Asset Management reports on the number of free and installed licenses can be generated. The License Management module is part of a Co-funding Project and not released as open source yet.

opsi-server

The opsi server provides the following services:

  • The configuration-server stores the configuration data of the clients and provides the methods to manage these data via web service or command-line based. The data can be stored in files, in OpenLDAP or in a MySQL Database.
  • The depot-server stores software packages that may be installed on the clients. To provide support for multiple locations, multiple depot-servers may be controlled by one configuration-server.
  • A TFTP-Server provides the boot images for the OS-Installations.
  • A DHCP-Server may be integrated in the opsi-server

Management-Interface

For managing opsi a graphical user interface is available as an application or as a Browser Applet. Management is also possible with a command line tool or via web service.

License

The opsi core features are Open Source according to the GNU General Public License Version 3 and are free of charge. The core features are software distribution (or software deployment), OS deployment and hard- and software-inventory. These free components can be supplemented with closed source add-ons that are fee required. They are called Co-funding Projects .


Co-funding Projects

Even though opsi is open source, there are some components which are not for free at the moment. These components are developed in a co-funding project. This means, that these parts are only available for those customers who paid a contribution to the cost of development. As soon as the development of a co-funding project is refinanced, the component will be part of the free opsi-version and can be used free of charge. It will be open source (as long as not prevented caused by technical reasons). The first of these co-funding Projects was the opsi support for Vista/Windows 7. It was completed on 1st of February 2008 and is free of charge since 1st of March 2010. The source code was divided form the not yet paid parts and is open source since since 30th of November 2010. At the moment (January 2011) there are three co-funding projects: Treewiew allows to build hierarchical groups of clients to manage them, MySQL as backend for all data and the license management module. The main focus of co-funding projects is to create software once for a pool of purchaser who share the cost and make it open source as soon as it paid in full .

References and sources

  1. http://www.opsi.org/license/
  2. http://www.opsi.org/features/
  3. http://www.cape-it.de/product-kix4otrs.html
  4. http://www.opsi.org/screenshots/
  5. http://download.uib.de/opsi_stable/doc/opsi-manual-stable-en.pdf , Chapter opsi-admin
  6. http://www.opsi.org/license/
  7. http://uib.de/en/opsi%20cofunding/index.html
  8. http://www.opsi.org/statistics/cofunding%20opsiclientd/

External links

Categories: