Serviceguard 11.18 with 11.23 OS

[UVA]

HI Gurus,

I had implemented SG-Cluster 11.18 with legacy pkg,however it has ability for moduler pkg configuration with only pkg configuration file without pkg control file.

Now what i wanted to know from u guys is which one will be good for HP-UX 11.23 OS. ( legacy or Moduler )

Thanks.

[Matti_Kurkela]

Some of the new package features of Serviceguard 11.18 are usable with modular package configuration only.

But if you don't need those features, choose whichever is more convenient for you. It makes no difference for the OS.

MK

[SoorajCleris]

Hi ,

Use of modular packages is preferred, keeping in mind the guidelines that follow.

New Serviceguard Installations:-

For new Serviceguard installations, modular packages are the preferred style. In this case, you can immediately benefit from the new 11.18 features. See chapter 6 of Managing Serviceguard. In subsequent Serviceguard releases, new package features may be available only in modular packages.


Existing Serviceguard Installations:-

In existing installations, you may prefer not to redefine existing packages because they are well-tested and operating as desired. You can continue to use and maintain your legacy packages on Serviceguard A.11.18. See chapter 7 of Managing Serviceguard.

Whether or not you convert existing packages, HP recommends that you create new packages as modular packages to take advantage of the new features. Modular Packages and legacy packages can coexist on the same cluster.


You can still migrate the packages.

Regards,
Sooraj

[UVA]

Hi,

Thanks for your reply.

what are the advantages to use moduler package rather leagacy package?

Since i hve implemented with legacy package which is running fine. bcz ther are guys who is pointing this at me.

[S.N.S]

Hi UVA,

When there is something tested and proved to work really well - then plan to go for it...

Your answer, from the docs:

- Simplified Package Configuration:-
o All configuration data for the package is now in the package configuration file. Previously, configuration data was included in both the configuration file and in the package control script.

- Modularized Approach to packages:-
o All package parameters are now configured in one place, the package configuration file. You no longer need to create and distribute a separate package control file.
o External scripts offer an improved means of application integration. These replace the Customer Defined Functions in the legacy package control script. You do need to distribute these scripts to all the nodes that can run the package.
o The modular approach allows you to build a package from building blocks containing only the functions needed by this package.
o Packages are built from a set of modules that define only the specific functionality that each package needs; paramters that are not needed are not included.
o There are well-defined entry points for user-defined scripts
o Software partnerscan easily plug in custom modules for their products


The complete doc would help you in migration:
http://docs.hp.com/en/12120/migrating-packages.pdf

Plan well, though

HTH
SNS

[Wim Rombauts]

I recently upgrade our 11.17 cluster to 11.19. For now, I leave all the legacy packages as they are, but I plan to migrate them in the future, because :

Patching ServiceGuard with legacy packages means you should recreate the control script of every package, because fixes to the control script are not applied automatically to the packages. With modular packages, this is done automatically because the control script is no longer part of the package.

Als, modular packages allow a lot more online changes that cannot be done with a legacy package.

If I need to create a new package, I will certainly only create modular packages.

If you think about converting legacy packages to modular packages, first get used to these modular packages, that will make the final migration of your legacy package easier and quicker.