|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||HP HPOM Policies||Recommended Links||Reference||Version Management||Comparing Policies|
|Creating and Uploading Policies||Listing policies installed on the node||Removal of policies||Assigning Policies||Deploying Policies||How to find out which policies are associated with the particular node|
|Policy Groups||Default Policy Groups||node groups||Layout groups||Message groups||Policy Files Naming Conventions|
In HPOM 9 Policies can have multiple versions (version control), and are organized in a tree-like structure. See “Policy Versions” on page 87 and the HPOM Concepts Guide for more information. Policies can also contain category assignments linking them to scripts. This is useful, for example for message policies.
A policy container represents a set of policies with the identical name and the type, but different versions. All policy versions in the policy container are unique. Some operations can be performed on policy containers, which means that they are performed on each policy in the container. Each container has a unique ID that is shared by all the policies in that container. Containers are identified by their names and types, or by their IDs. Policy Types It is possible to have multiple types of policies on the management server mapped to the same policy type on the managed nodes. Therefore, during the policy type registration you can specify the type by which the policy is classified on the managed node. If this type is not specified, the policy type name registered on the management server is used instead. In this case, if there are no corresponding consumers on the managed node, the policies will nevertheless be deployed, but ignored afterwards.
With HPOM 9.0x, it is possible to have multiple versions of policies stored on the management server. Having multiple versions of policies on the HPOM 9.0x management server enhances the flexibility in operating with policies and policy groups, and allows simplified interoperability between HPOM on Unix, Linux, and Windows platforms. All policies have version numbers. A version number consists of two digits with the format major.minor, for example, 1.0. Major digits can be reserved for the specified purposes, for example, for SPIs release tracking. The version of all newly created policies is set to 1.0, while the version of all default policies delivered with HPOM 9.0x is 9.0.
It also ensures the following:
When the policy content is modified, the minor digit of the policy version number is automatically incremented, for example, from 1.0 to 1.1. If the new version already exists, the next available value is chosen, for example 1.2. To learn how to overcome the conflicts between the versions, see “Managing Conflicts between Policy Versions” on page 259.
NOTE A change in the policy header (for example, changing the policy description) does not result in the creation of a new policy version. The policy version can be replaced according to your preferences by using the opcpolicy command-line tool. The policy version numbers can also be changed without the need to modify the policy content. This is especially useful when aligning the policy versions that are released together. For usage details, see the opcpolicy (1M) manpage. For more information about the available APIs, see the HPOM Developer’s Reference.
NOTE The new version number creation results in the creation of a new policy, even if the content is unchanged. The new policy has a new version UUID, but the container ID is same as before. On the other hand, changing the policy name results in a new object in the database with a new version UUID and a new container ID.
Only one version of each policy can be installed on a managed node. When deploying a new policy version to a managed node, the new policy version replaces the existing version, regardless of its version number. This is because both versions use the same container UUID that is used on the managed node to identify the policies. Managing Conflicts between Policy Versions Policy versions come into conflict when the version number of a policy that you intend to assign already exists in the database. The following modes are available for managing conflicts between versions:
There are two types of checksums:
A policy type is an agent-known string (for example: monitor, le, trapi, and so on) that also includes the UUID and the syntax version.
With HPOM 9.0x, it is possible to have multiple versions of policiesstored on the management server. Having multiple versions of policies onthe HPOM 9.0x management server enhances the flexibility in operatingwith policies and policy groups, and allows simplified interoperabilitybetween HPOM on Linux and Windows platforms.❏ “Changing the Policy Version” on page 87
❏ “Migrating HPOM 8.xx Policys to HPOM 9.0x Policies” on page 88 For more information about the concepts of policy versions and theorganization of the policy-group hierarchy, see the HPOM ConceptsGuide.
All policies have version numbers. To replace a particular policy version, use the opcpolicy command with the -update parameter as follows:
# opcpolicy -update version=<policy_version>
You can also upload and download specific versions of a policy andinstruct HPOM what to do if a version already exists. For more information about the opcpolicy command and the -update parameter, refer to the opcpolicy(1m) reference page. The policy version numbers can also be changed without the need tomodify the policy content. This is especially useful when aligning thepolicy versions that are released together. Refer to the opcpolicy (1M)HPOM Configuration reference page for more information about command options.
NOTE The new version number creation results in the creation of a new policy, even if the content is unchanged. The new policy has a new version UUID, but the container ID is same as before. On the other hand, changing the policy name results in a new object in the database with anew version UUID and a new container ID.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: October 11, 2015