This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hey Austin,
I wanted to clarify how 9.0 and 9.1 fit into the lifecycle and the path forward for JPMC.
Both 9.0 and 9.1 follow the same lifecycle policy, so with 9.0 you can continue using the existing NMS reporting functionality through the EOS date. The EOS date is the same across all 9.x versions, so there’s no additional lifecycle impact by staying on 9.0 for the time being.
This also gives you some flexibility around the transition to 9.1. Our Engineering teams are currently working on the Data Insight resiliency initiative, which we’re targeting for the 9.1 release. Once that capability is available, you’ll be able to move DI to 9.1 and take advantage of the N-1 support with NMS to test and validate the new setup before making any changes to your NMS environments. Once you’re comfortable with the results, you can then move your NMSs to 9.1.
We’ve taken JPMC’s feedback into account as part of this planning and have delayed the reporting deprecation by an additional release to give you more time to transition. This does require us to continue supporting the existing NMS reporting experience for an extended period, but we felt it was important to provide JPMC with a practical transition path.
Longer term, we’re continuing to move toward a One UI experience, which we believe will provide a more consistent and streamlined experience across the product. We want to make sure JPMC has the time and flexibility to validate the new capabilities and make the transition at a point that works well for your environment.
Regards,
Deva Dash
Hi Deva,
As you are aware, we requested SevOne NMS reporting features to be maintained until there is a ‘productized’ resiliency capability for Data Insight nodes, which we were expecting to be available in version 9.0.
I did not see resiliency explicitly mentioned in the Data Insight release notes for 9.0. Can you point me to where this is documented?
If Data Insight resiliency is not addressed in this release, NMS Reporting features need to be maintained. The ask is to maintain NMS Reporting features for at least 1 major release after Data Insight has resiliency (the ability to replicate settings / data between nodes, essentially HSA) as part of its standard offering.
https://www.ibm.com/docs/en/sevone-npm/9.0.0?topic=notes-release-sevone-data-insight-900
Hey Austin,
After considering this request, we have made the decision to delay the deprecation to a 9.1 release. So the 9.0 release in Sept will still retain the SURF reporting functions.
Regards,
Deva Dash