Version Management

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:

• SPI and customer config migration-related issues get simplified With HPOM 8.xx, it was necessary to rename SPI policys so that they do not get overwritten when an SPI patch is applied. Having multiple SPI versions on the server allows their deployment to different group of nodes, without the need to rename policies or policy groups. This enables a flexible approach to the migration plans. For the migration details, see “Migration of HPOM 8.xx Policys to HPOM 9.01 Policies” on page 261.
• Easier management of the configuration data With policy versioning, it is possible to determine the versions of configuration elements (for example, policies) that are present on the management server and the managed nodes. For example, the simplified administration of different subagent versions is enabled, as well as their assignment and deployment to the managed nodes. For detailed information, see “Managing of Subagents in HPOM” on page 267 and the HPOM Administrator’s Reference. HPOM for different platforms (Unix, Linux, and Windows) uses the aligned policy versioning functionality. This allows a single set of SPI policies to be delivered for HPOM on both platforms, as well as the simplified data exchange between them. For data exchange considerations, see “Policy Data Exchange Model” on page 260.

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:

• Overwrite mode The conflicting version in the database is replaced. Configuring and Maintaining HPOM Managing Policies in HPOM 260 Chapter 3
• New version mode • In case of the conflict between the versions, the minor digit is automatically incremented for the version being uploaded. If the new version also exists, the first available value is chosen. The user is informed about the version number and the UUID. • If there are no conflicting versions, the policy is uploaded with the current version.
• Error mode In case of the conflict between the versions, an error is returned and the upload is canceled. Policy Data Exchange Model HPOM 9.0x for Unix and Linux and HPOM 8.xx for Windows share the common data exchange model for policies and policy groups. Consider the following:
• The policy is identified on the management server in one of the following ways: • By UUID • By name, version, and type
• All policies with the identical name and the type have a common identifier named container UUID. The policies that share the same container UUID have a different version number and a corresponding individual identifier named policy ID.
• It is possible to compare policies by using checksums. The checksum fields, stored in a policy header, are considered during the configuration download and upload.

There are two types of checksums:

• Policy header checksum Used to detect prohibited policy modifications (license violations).
• Policy data file checksum Used for faster content comparison.

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.

Policy Versions

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.

Etc

Society

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

Quotes

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

Bulletin:

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

History:

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

Classic books:

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 Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

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 Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019