This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
See this idea on ideas.ibm.com
When defining deploy templates for self service usage. While we can specify a network to use, we cannot limit deployment to a range of IP addresses within the network.
The reason we need this is because currently multiple projects can be configured with the same network, but the reservations are not cross polinated. As a result IP addresses allocations during self service deployments needs more granular control.
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
PowerVC 1.3.3 now supports the concept of shared networks across tenants.
Hey Barry - thanks for the request. I've marked this as "planned for the future" as the pain point you describe will be solved in an upcoming release, although not exactly by specifying an IP range in the deploy templates. The issue you call out stems from the fact that, at present, PowerVC networks can't be shared across multiple projects. Once you can share a network across the various projects, you won't run into the overlap concerns that you call out and this should then be non-existent... and in fact, less administrator work since you just define the network once, and you're done!
Hope this helps!