Server Automation Practitioners Forum

Multiple OS Revisions for SA Install

P Seymour

Multiple OS Revisions for SA Install


Is it possible to have HP-Server Automation provision and install minor OS revisions. i.e. RHEL5.1, 5.3, and 5.5 for example ?

The policy setters guide doesn't seem clear and the names are all based on major revisions only.

How would multiple initrd's be handled etc ?




P.S. This thread has been moved from Data Center Automation Support and News to Server Automation Support and News Forum - HP Forums Moderator

Jim Olsen ASE
New Member.

Re: Multiple OS Revisions for SA Install

This is possible, however all minor OS revisions will be grouped together by their major version number from within HP SA.

For example, say you upload three different OS Media kits to HP SA using import_media: RHEL 5.1, 5.2, and 5.3. Each would have their own MRL that would point to the media specific to that version, but each MRL's "OS Version" within HP SA would be the same (Red Hat Enterprise Linux Server 5), which would make the "OS Media" tab look like so from within the HP SA Web Client:

Name | Path | OS Version
RHEL 5.1 | nfs://mediasrv/media/linux/rhel-5.1-server | Red Hat Enterprise Linux Server 5
RHEL 5.2 | nfs://mediasrv/media/linux/rhel-5.2-server | Red Hat Enterprise Linux Server 5
RHEL 5.3 | nfs://mediasrv/media/linux/rhel-5.3-server | Red Hat Enterprise Linux Server 5

You would want to change the name of your OS Media, OS Profile, and OS Sequences to reflect the minor version accordingly, else wise you will not be able to tell them apart.

As far as the multiple initrd's aspect of your question, I don't understand what you are asking. If you are asking how does HP SA keep the packages for each minor release separate, that is done via import_media during package upload -- each package gets a unique unit ID that gets associated with the specific MRL that you are creating at that time.

HTH. - DCA Experts
P Seymour

Re: Multiple OS Revisions for SA Install

Thanks for that it's a little silly the grouping but I have got it.

The initrd question is based on the fact that RHEL installations will only continue from the release/kernel that is loaded via the initrd.