Product Requirement Portal

It would be great if we wouldn't have to open firewalls to both repository and ISM from iRMC addresses. Repository should be selectable as just a "cache" for the ISM in my opinion and with that selection all the updates should come through the ISM even though it is going to degrade performance etc but in some cases it doesn't matter.

We have security critical customers who will never accept a server between internet and iRMC (even through a proxy). Then again if the flow would be "Internet -> Repository -> ISM -> iRMC" it would be okay for them.

The idea of providing the firmware repository (GlobalFlash) as a web service in the ISM, as in the SV Repo Server, is desired by many customers.

However, the SV Repo Server must also exist as an independent server, as there are also many customers who do not have direct access from the ISM/iRMC to the Internet and have to use the SV Repo Server in a DMZ.

Solution

- Firmware repository (Globalflash) as a web service in the ISM

- Independent SV Repo Server for DMZ solutions, must continue to exist

2 more customer need this Feature to avoid an extra server for an Fujitsu repository beside ISM.
So an integration of the ServerView Repository Server inside ISM ist necessary so the irmc Features elcm online and elcm offline Update and deployment may use ISM as repository source only.

This feature was planned 1-2 year ago but at the end we have no planned date for this feature.

Thank you Philippe for this idea. Internally this idea came up for quite a while. It is accepted as a valid idea, but not scheduled for implementation yet.