Misplaced Pages

OpenLMI: 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 editContent deleted Content addedVisualWikitext
Revision as of 19:55, 21 March 2014 editDsimic (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers39,664 edits Punctuation← Previous edit Latest revision as of 15:40, 26 September 2021 edit undoFireflyBot (talk | contribs)Bots329,313 editsm (BOT) Substituting Template:Date - should not be used in article space. 
(32 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Primary sources|date=December 2013}} {{Primary sources|date=December 2013}}
{{Use mdy dates|date=August 2014}}


'''OpenLMI''' (abbreviated from '''Open Linux Management Infrastructure''') provides a common management infrastructure for ] systems. Available operations include configuration of various operating system parameters and services, hardware components configuration, and ] of system resources. Services provided by OpenLMI can be accessed both locally and remotely, using multiple programming languages and standardized ]s. '''OpenLMI''' (abbreviated from '''Open Linux Management Infrastructure''') provides a common management infrastructure for ] systems. Available operations include configuration of various ] parameters and services, hardware components configuration, and ] of system resources. Services provided by OpenLMI can be accessed both locally and remotely, using multiple ]s and standardized ]s.

Project's source code is distributed under the ] (LGPL) and ].<ref name="fedorahosted">{{cite web
| url = https://fedorahosted.org/openlmi/
| title = OpenLMI development website
| accessdate = July 14, 2014
| website = fedorahosted.org
⚫ }}</ref>


== Overview == == Overview ==
OpenLMI distinguishes '']'', ''controllers'' and ''client applications'': OpenLMI distinguishes '']'', ''controllers'' and ''client applications'':


* OpenLMI agents are installed and running on managed Linux systems, performing the actual operations. * OpenLMI agents perform the actual operations; they are installed and run on managed Linux systems.
* OpenLMI controllers manage the OpenLMI agents. * OpenLMI controllers manage the OpenLMI agents.
* Client applications talk to the OpenLMI controllers through well-defined interfaces and ]s based on open industry standards for remote systems management. * Client applications talk to the OpenLMI controllers through well-defined interfaces and ]s, which are based on open industry standards for the management of remote systems.


Thus, instead of delivering a complete management solution, OpenLMI provides low-level functions and APIs that can be used by, or integrated into, various management platforms, applications or configuration scripts.<ref name="openlmi-home">{{cite web Thus, instead of delivering a complete management solution, OpenLMI provides low-level functions and APIs that can be used by, or integrated into, various management platforms, applications or configuration scripts.<ref name="openlmi-home">{{cite web
| url = http://www.openlmi.org/ | url = http://www.openlmi.org/
| title = OpenLMI: Configure, Manage and Monitor Linux Systems | title = OpenLMI: Configure, Manage and Monitor Linux Systems
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
| archive-url = https://web.archive.org/web/20151028220327/http://www.openlmi.org/
⚫ }}</ref>
| archive-date = October 28, 2015
| url-status = dead
}}</ref>


OpenLMI extends the already existing Linux infrastructure by providing management agents which also perform system configuration tasks, in addition to monitoring and reporting functions. By exporting those operations through standard-based interfaces, and by providing agents performing the actual operations, OpenLMI creates a management ] that various applications can use{{snd}} both for system configuration, and for monitoring resources and performance. Usage targets for OpenLMI include bare-metal production servers, on which it can perform initial configurations through a set of predefined "recipes".<ref name="openlmi-home" /> OpenLMI extends the already existing Linux infrastructure by providing management agents which also perform system configuration tasks, in addition to monitoring and reporting functions. By exporting those operations through standard-based interfaces, and by providing agents performing the actual operations, OpenLMI creates a management ] that various applications can use{{snd}} both for system configuration, and for monitoring resources and performance. Usage targets for OpenLMI include bare-metal production servers, on which it can perform initial configurations through a set of predefined "recipes".<ref name="openlmi-home" />


{{As of|2013|December}}, implemented agents primarily perform operations related to the storage, networking and local user accounts. Plans exist to expand the variety of implemented agents, aiming at providing complete coverage of Linux management and configuration tasks.<ref name="openlmi-home" /> {{As of|2013|December}}, implemented agents primarily perform operations related to storage, networking and local user accounts. Plans exist to expand the variety of implemented agents, aiming at providing complete coverage of Linux management and configuration tasks.<ref name="openlmi-home" />

The OpenLMI's source code is licensed under the GNU Lesser General Public License (]) and Simplified BSD License (also known as the ]).<ref name="fedorahosted" />


== Architecture == == Architecture ==
Line 25: Line 38:
| url = http://www.openlmi.org/architecture | url = http://www.openlmi.org/architecture
| title = OpenLMI: Architecture | title = OpenLMI: Architecture
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


Each agent implements an object model that specifies the attributes (information), methods (functions), and associations (links to other objects). This object model is made available to the client applications in an interoperable way, through the controller. While it is possible to build all of the required logic into an agent, the general approach is to use and invoke existing Linux tools. For example, OpenLMI's network agent uses the ], and the storage agent uses the Blivet storage library.<ref name="openlmi-architecture" /> Each agent implements an object model that specifies the attributes (information), methods (functions), and associations (links to other objects). Through the controller, this object model is interoperably made available to client applications. While it is possible to build all required logic into an agent, the general approach is to use and invoke existing Linux tools; for example, OpenLMI's network agent uses the ], and the storage agent uses the Blivet storage library.<ref name="openlmi-architecture" />


The actual communication protocol is using ] data transferred over ]. While directly using XML is possible, a set of client ] provides native interfaces for a number of programming languages. Client libraries supplied by OpenLMI provide support for C/C++, Python and Java. These interfaces are implemented as language bindings to the operations in underlying system agents, with all supplied libraries providing the same feature sets. Support for ] (CLI) utilities is also provided.<ref name="openlmi-home" /><ref name="openlmi-architecture" /> The actual communication protocol is using ] data transferred over ]. While it is possible to use XML directly, a set of client ] provides native interfaces for a number of programming languages; client libraries supplied by OpenLMI provide support for ], ], ] and ]. These interfaces are implemented as language bindings to the operations in underlying system agents, with all supplied libraries providing the same feature sets. Support for ] (CLI) utilities is also provided.<ref name="openlmi-home" /><ref name="openlmi-architecture" />


Internally, OpenLMI is based on the Distributed Management Task Force (DTMF) ] (CIM), with internal functions exposed in form of CIM ]s. A few open-source CIM clients are available, as an additional way for using data and operations exported through OpenLMI.<ref>{{cite web Internally, OpenLMI is based on the ] (DMTF) ] (CIM), with internal functions exposed in form of CIM ]s. A few open-source CIM clients are available, as an additional way for using data and operations exported through OpenLMI.<ref>{{cite web
| url = http://blog.fpmurphy.com/2013/06/openlmi-open-linux-management-interface.html | url = http://blog.fpmurphy.com/2013/06/openlmi-open-linux-management-interface.html
| title = OpenLMI - Open Linux Management Interface | title = OpenLMI - Open Linux Management Interface
| date = 2013-06-30 | accessdate = 2013-12-11 | date = June 30, 2013 | accessdate = December 11, 2013
| publisher = blog.fpmurphy.com | website = blog.fpmurphy.com
}}</ref><ref>{{cite web }}</ref><ref>{{cite web
| url = http://www.kernel-labs.org/node/1 | url = http://www.kernel-labs.org/node/1
| title = OpenLMI Project - Part I | title = OpenLMI Project - Part I
| date = 2012-10-02 | accessdate = 2013-12-13 | date = October 2, 2012 | accessdate = December 13, 2013
| publisher = kernel-labs.org | website = kernel-labs.org
}}</ref> }}</ref>


=== Agents === === Agents ===
OpenLMI ''agents,'' also called ''providers,'' do the actual work. OpenLMI distribution includes a set of standard management agents, and also includes a set of development resources required for developing new agents. These are the standard OpenLMI agents, as of December 2013:<ref>{{cite web OpenLMI ''agents'', also called ''providers'', do the actual work. OpenLMI distribution includes a set of standard management agents, and also includes a set of development resources required for developing new agents. Standard OpenLMI agents, {{As of|2014|04|lc=yes}}, are the following:<ref>{{cite web
| url = http://www.openlmi.org/agents | url = http://www.openlmi.org/agents
| title = OpenLMI: Agents | title = OpenLMI: Agents
| accessdate = 2013-12-11 | accessdate = April 18, 2014
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


Line 57: Line 70:
| url = http://www.openlmi.org/agent_storage | url = http://www.openlmi.org/agent_storage
| title = OpenLMI: Storage Agent | title = OpenLMI: Storage Agent
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


Line 65: Line 78:
| url = http://www.openlmi.org/agent_network | url = http://www.openlmi.org/agent_network
| title = OpenLMI: Networking Agent | title = OpenLMI: Networking Agent
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


; System Services ; System Services
: ''System Services Agent'' performs management of the system services and underlying ], by exposing the ability for services to be started, stopped, restarted etc. through the standard OpenLMI interface. It also has the ability to enumerate (discover) available system services, using the ]'s ] interface.<ref>{{cite web : ''System Services Agent'' performs the management operations associated with the system services and underlying ], by exposing the ability for services to be, for example, started, stopped or restarted through the standard OpenLMI interface. This agent also has the ability to enumerate (discover) available system services, using the ]'s ] interface.<ref>{{cite web
| url = http://www.openlmi.org/agent_services | url = http://www.openlmi.org/agent_services
| title = OpenLMI: System Services Agents | title = OpenLMI: System Services Agents
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


; User Accounts ; User Accounts
: ''User Accounts Agent'' configures and manages local user accounts, local user groups, groups membership, and accounts parameters (such as default shell, home directory, password and password expiration). It also has the ability to enumerate (discover) available local user accounts and local user groups.<ref>{{cite web : ''User Accounts Agent'' configures and manages local user accounts, local ]s, groups membership, and accounts parameters such as the default ], ], password, and password expiration. This agent also has the ability to enumerate (discover) available local user accounts and local user groups.<ref>{{cite web
| url = http://www.openlmi.org/agent_accounts | url = http://www.openlmi.org/agent_accounts
| title = OpenLMI: User Accounts Agent | title = OpenLMI: User Accounts Agent
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


; Software ; Software
: ''Software Agent'' configures and manages software on a managed system. It has the ability to list the software installed on a system, install new software, update existing software, and remove installed software. It also has the ability to verify integrity of installed packages and their files, while using all configured repositories.<ref>{{cite web : ''Software Agent'' configures and manages ] on a managed system. It has the ability to list the software installed on a system, install new software, update existing software, and remove installed software. It also has the ability to verify integrity of installed packages and their files, while using all configured ].<ref>{{cite web
| url = http://www.openlmi.org/agent_software | url = http://www.openlmi.org/agent_software
| title = OpenLMI: Software Agent | title = OpenLMI: Software Agent
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


; Hardware ; Hardware
: ''Hardware Agent'' manages hardware components, providing detailed information on their presence and associated configurations. Provided information includes the ] (cores, clock and FSB speeds, caches etc.), system memory (size, speed, available memory slots, installed modules etc.), physical asset data (chassis, ports, slots etc.), battery (capacity, voltage etc.), and ] devices and bridges (buses, IDs of devices, vendors etc.)<ref>{{cite web : ''Hardware Agent'' manages hardware components, providing detailed information on their presence and associated configurations. Provided information includes the ]-related data (number of cores, clock and ] speeds, ] sizes, etc.), system ] (size, speed, available memory slots, installed ], etc.), physical asset data (chassis info, available ports and slots, etc.), battery (available capacity, running voltage, etc.), and ] devices and bridges (available ], ], device vendors, etc.)<ref>{{cite web
| url = http://www.openlmi.org/agent_hardware | url = http://www.openlmi.org/agent_hardware
| title = OpenLMI: Hardware Agent | title = OpenLMI: Hardware Agent
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref> }}</ref>


; Logging ; Logging
: ''Journald Agent'' gives access to logging records through the standard OpenLMI interface. It is a client of systemd's ] service, accessing the journald records in several ways, and providing a way to store new log records. Journald is a structured logging system, storing supplemental information along each record, thus making it easier to find and extract information from the resulting log files.<ref>{{cite web : ''Journald Agent'' provides access to logging records through the standard OpenLMI interface. It is a client of systemd's ] service, accessing the journald records in several ways and providing a way to store new log records. Journald, as a structured logging system, stores supplemental information along each record, making it easier to find and extract information from the resulting ].<ref>{{cite web
| url = http://www.openlmi.org/agent_journald | url = http://www.openlmi.org/agent_journald
| title = OpenLMI: Logging with Journald | title = OpenLMI: Logging with Journald
| accessdate = 2013-12-11 | accessdate = December 11, 2013
| publisher = openlmi.org | website = openlmi.org
}}</ref>

; Performance CoPilot
: ''Performance CoPilot Agent'' provides access to various system statistics and performance monitoring data collected by the ] (PCP) service running locally on a monitored host. PCP is capable of providing monitoring data for various services, including web, email and ]s, and ]s. Collected data may have any type of value, including ], ], ], and arbitrary composite ]s.<ref>{{cite web
| url = http://www.openlmi.org/agent_performancecopilot
| title = OpenLMI: Performance CoPilot
| date = September 23, 2013 | accessdate = April 18, 2014
| website = openlmi.org
}}</ref><ref>{{cite web
| url = http://www.performancecopilot.org/doc/pcp-users-and-administrators-guide.pdf
| title = Performance Co-Pilot User's and Administrator's Guide
| date = January 6, 2014 | accessdate = April 18, 2014
| website = oss.sgi.com | format = PDF
}}</ref> }}</ref>


== Comparison == == Comparison ==
OpenLMI is different from other configuration management systems like ] or ], in a way that OpenLMI does not require details of the system configuration to be already known, in order for appropriate configuration recipes to be created. This nature of the OpenLMI is favorable in case of initial configuring being performed on a broader variety of systems, having different hardware configurations.<ref>{{cite web OpenLMI is different from other configuration management systems like ] or ], in a way that OpenLMI does not require details of the system configuration to be already known in order for appropriate configuration recipes to be created. This nature of the OpenLMI may provide advantages in case initial configuration is to be performed on a broader variety of systems having different hardware configurations.<ref>{{cite web
| url = http://techponder.wordpress.com/2013/11/14/openlmi-vs-puppet/ | url = http://techponder.wordpress.com/2013/11/14/openlmi-vs-puppet/
| title = OpenLMI vs. Puppet | title = OpenLMI vs. Puppet
| date = 2013-11-14 | accessdate = 2013-12-11 | date = November 14, 2013 | accessdate = December 11, 2013
| publisher = techponder.wordpress.com | website = techponder.wordpress.com
}}</ref> }}</ref>


== Reception == == Reception ==
First beta release of the ] 7.0 includes support for the OpenLMI.<ref>{{cite web ] 7.0 includes support for OpenLMI since the first beta release of this ], which was made available on December 11, 2013.<ref>{{cite web
| url = http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7
| title = Red Hat Unveils Red Hat Enterprise Linux 7, Redefining the Enterprise Operating System
| date = June 10, 2014 | accessdate = June 11, 2014
| publisher = ]
}}</ref><ref>{{cite web
| url = http://www.redhat.com/about/news/archive/2013/12/red-hat-announces-availability-of-red-hat-enterprise-linux-7-beta | url = http://www.redhat.com/about/news/archive/2013/12/red-hat-announces-availability-of-red-hat-enterprise-linux-7-beta
| title = Red Hat Announces Availability of Red Hat Enterprise Linux 7 Beta | title = Red Hat Announces Availability of Red Hat Enterprise Linux 7 Beta
| date = 2013-12-11 | accessdate = 2013-12-11 | date = December 11, 2013 | accessdate = December 11, 2013
| publisher = ] | publisher = ]
}}</ref> ] 20, released on December 17, 2013, also includes support for OpenLMI.<ref>{{cite web
| url = http://rhelblog.redhat.com/2013/12/20/managing-linux-with-openlmi/
| title = Managing Linux with OpenLMI
| date = December 20, 2013 | accessdate = June 12, 2014
| author = Russ Doty | publisher = ]
}}</ref><ref>{{cite web
| url = http://fedoraproject.org/Releases/20/Schedule
| title = Releases/20/Schedule
| date = January 18, 2014 | accessdate = June 12, 2014
| publisher = ]
}}</ref> }}</ref>


== See also == == See also ==
{{Portal|Free software|Linux}} {{Portal|Free and open-source software|Linux}}


* ] * ]
Line 136: Line 177:
{{Reflist|30em}} {{Reflist|30em}}


==External links== == External links ==
* {{Official website|http://www.openlmi.org/}} * {{Official website|http://www.openlmi.org/}}
* *
* *
* (DTMF) * (DMTF)


] ]

Latest revision as of 15:40, 26 September 2021

This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources.
Find sources: "OpenLMI" – news · newspapers · books · scholar · JSTOR (December 2013) (Learn how and when to remove this message)

OpenLMI (abbreviated from Open Linux Management Infrastructure) provides a common management infrastructure for Linux systems. Available operations include configuration of various operating system parameters and services, hardware components configuration, and monitoring of system resources. Services provided by OpenLMI can be accessed both locally and remotely, using multiple programming languages and standardized APIs.

Project's source code is distributed under the GNU Lesser General Public License (LGPL) and Simplified BSD License.

Overview

OpenLMI distinguishes agents, controllers and client applications:

  • OpenLMI agents perform the actual operations; they are installed and run on managed Linux systems.
  • OpenLMI controllers manage the OpenLMI agents.
  • Client applications talk to the OpenLMI controllers through well-defined interfaces and language bindings, which are based on open industry standards for the management of remote systems.

Thus, instead of delivering a complete management solution, OpenLMI provides low-level functions and APIs that can be used by, or integrated into, various management platforms, applications or configuration scripts.

OpenLMI extends the already existing Linux infrastructure by providing management agents which also perform system configuration tasks, in addition to monitoring and reporting functions. By exporting those operations through standard-based interfaces, and by providing agents performing the actual operations, OpenLMI creates a management framework that various applications can use – both for system configuration, and for monitoring resources and performance. Usage targets for OpenLMI include bare-metal production servers, on which it can perform initial configurations through a set of predefined "recipes".

As of December 2013, implemented agents primarily perform operations related to storage, networking and local user accounts. Plans exist to expand the variety of implemented agents, aiming at providing complete coverage of Linux management and configuration tasks.

The OpenLMI's source code is licensed under the GNU Lesser General Public License (LGPL) and Simplified BSD License (also known as the FreeBSD License).

Architecture

Based on their placement and usage role, OpenLMI architecture contains two major components: management modules (also known as agents), and management tools. A set of management modules is installed and running on each of the managed systems, performing the configuration and monitoring tasks. Management tools are running on a management system, performing aggregation of the collected monitoring data, and dispatching the requests to management modules. The agents are talking to the outside world through an OpenLMI Object Broker, which is also known as a controller. This object request broker provides a standard-based communications protocol, handles the security and access control, and provides deployment methods for the agents.

Each agent implements an object model that specifies the attributes (information), methods (functions), and associations (links to other objects). Through the controller, this object model is interoperably made available to client applications. While it is possible to build all required logic into an agent, the general approach is to use and invoke existing Linux tools; for example, OpenLMI's network agent uses the NetworkManager, and the storage agent uses the Blivet storage library.

The actual communication protocol is using XML data transferred over HTTPS. While it is possible to use XML directly, a set of client libraries provides native interfaces for a number of programming languages; client libraries supplied by OpenLMI provide support for C, C++, Python and Java. These interfaces are implemented as language bindings to the operations in underlying system agents, with all supplied libraries providing the same feature sets. Support for command-line interface (CLI) utilities is also provided.

Internally, OpenLMI is based on the Distributed Management Task Force (DMTF) Common Information Model (CIM), with internal functions exposed in form of CIM namespaces. A few open-source CIM clients are available, as an additional way for using data and operations exported through OpenLMI.

Agents

OpenLMI agents, also called providers, do the actual work. OpenLMI distribution includes a set of standard management agents, and also includes a set of development resources required for developing new agents. Standard OpenLMI agents, as of April 2014, are the following:

Storage
Storage Agent configures and manages local and remote storage. The ability to enumerate (discover) and configure local storage devices is built-in. As of December 2013, remote storage devices can be configured, with no support for their discovery or provisioning. Thus, remote storage must be already provisioned using other approaches, and the resulting logical unit number (LUN) made available to this agent. Support for provisioning of remote storage is planned for future releases.
Networking
Networking Agent configures and manages network interface controllers (NICs) and Linux networking configuration in general. It has the ability to enumerate (discover) and configure devices, including configuration of IPv4 and IPv6 addresses, default gateways, DNS servers, management of static routes, and configuration of interfaces bridging and bonding.
System Services
System Services Agent performs the management operations associated with the system services and underlying background processes, by exposing the ability for services to be, for example, started, stopped or restarted through the standard OpenLMI interface. This agent also has the ability to enumerate (discover) available system services, using the systemd's D-Bus interface.
User Accounts
User Accounts Agent configures and manages local user accounts, local user groups, groups membership, and accounts parameters such as the default shell, home directory, password, and password expiration. This agent also has the ability to enumerate (discover) available local user accounts and local user groups.
Software
Software Agent configures and manages software packages on a managed system. It has the ability to list the software installed on a system, install new software, update existing software, and remove installed software. It also has the ability to verify integrity of installed packages and their files, while using all configured repositories.
Hardware
Hardware Agent manages hardware components, providing detailed information on their presence and associated configurations. Provided information includes the CPU-related data (number of cores, clock and FSB speeds, cache sizes, etc.), system memory (size, speed, available memory slots, installed modules, etc.), physical asset data (chassis info, available ports and slots, etc.), battery (available capacity, running voltage, etc.), and PCI devices and bridges (available buses, IDs of devices, device vendors, etc.)
Logging
Journald Agent provides access to logging records through the standard OpenLMI interface. It is a client of systemd's journald service, accessing the journald records in several ways and providing a way to store new log records. Journald, as a structured logging system, stores supplemental information along each record, making it easier to find and extract information from the resulting log files.
Performance CoPilot
Performance CoPilot Agent provides access to various system statistics and performance monitoring data collected by the Performance Co-Pilot (PCP) service running locally on a monitored host. PCP is capable of providing monitoring data for various services, including web, email and database servers, and virtualization environments. Collected data may have any type of value, including integers, strings, floating point numbers, and arbitrary composite data structures.

Comparison

OpenLMI is different from other configuration management systems like Puppet or Bcfg2, in a way that OpenLMI does not require details of the system configuration to be already known in order for appropriate configuration recipes to be created. This nature of the OpenLMI may provide advantages in case initial configuration is to be performed on a broader variety of systems having different hardware configurations.

Reception

Red Hat Enterprise Linux 7.0 includes support for OpenLMI since the first beta release of this Linux distribution, which was made available on December 11, 2013. Fedora 20, released on December 17, 2013, also includes support for OpenLMI.

See also

References

  1. ^ "OpenLMI development website". fedorahosted.org. Retrieved July 14, 2014.
  2. ^ "OpenLMI: Configure, Manage and Monitor Linux Systems". openlmi.org. Archived from the original on October 28, 2015. Retrieved December 11, 2013.
  3. ^ "OpenLMI: Architecture". openlmi.org. Retrieved December 11, 2013.
  4. "OpenLMI - Open Linux Management Interface". blog.fpmurphy.com. June 30, 2013. Retrieved December 11, 2013.
  5. "OpenLMI Project - Part I". kernel-labs.org. October 2, 2012. Retrieved December 13, 2013.
  6. "OpenLMI: Agents". openlmi.org. Retrieved April 18, 2014.
  7. "OpenLMI: Storage Agent". openlmi.org. Retrieved December 11, 2013.
  8. "OpenLMI: Networking Agent". openlmi.org. Retrieved December 11, 2013.
  9. "OpenLMI: System Services Agents". openlmi.org. Retrieved December 11, 2013.
  10. "OpenLMI: User Accounts Agent". openlmi.org. Retrieved December 11, 2013.
  11. "OpenLMI: Software Agent". openlmi.org. Retrieved December 11, 2013.
  12. "OpenLMI: Hardware Agent". openlmi.org. Retrieved December 11, 2013.
  13. "OpenLMI: Logging with Journald". openlmi.org. Retrieved December 11, 2013.
  14. "OpenLMI: Performance CoPilot". openlmi.org. September 23, 2013. Retrieved April 18, 2014.
  15. "Performance Co-Pilot User's and Administrator's Guide" (PDF). oss.sgi.com. January 6, 2014. Retrieved April 18, 2014.
  16. "OpenLMI vs. Puppet". techponder.wordpress.com. November 14, 2013. Retrieved December 11, 2013.
  17. "Red Hat Unveils Red Hat Enterprise Linux 7, Redefining the Enterprise Operating System". Red Hat. June 10, 2014. Retrieved June 11, 2014.
  18. "Red Hat Announces Availability of Red Hat Enterprise Linux 7 Beta". Red Hat. December 11, 2013. Retrieved December 11, 2013.
  19. Russ Doty (December 20, 2013). "Managing Linux with OpenLMI". Red Hat. Retrieved June 12, 2014.
  20. "Releases/20/Schedule". Fedora Project. January 18, 2014. Retrieved June 12, 2014.

External links

Categories: