Description of problem:
At the moment, it is only possible to rename virtual networks only when no VMs are using it since the name is uesd directly on hosts to create bridges. This RFE is to enable this kind of editing. This may be achieved for example by separating user-visible virtual network names from bridge names on hosts (use IDs instead?)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
log in to rhev-m
go to networks tab
select a network with attached VMs
change the name
error is displayed:
Error while executing action: Cannot edit Network. Several virtual machines (1) are using this logical network:
- Please remove it from all virtual machines that are using it and try again.
network renamed successfully
http://www.ovirt.org/Features/Unrestricted_Network_Names would allow that.
Is there any chance this can be implemented in a release soon?
Created attachment 1285322 [details]
We will add the ability to make networks name editable in new networks or for existing networks. There is no way to revert to non-editable after this is enabled. The default will stay as non-editable since the majority of cases do not require this and non-editable is more debug friendly.
Bridge name should be available in GUI and API.
I am unhappy with the request of modifying editability of host-attached networks. Doing so would necessary lead to a network named "new net" while on the hosts it is named "old net" rather than onXXXXX, which I find confusing.
We agreed to remove RFEs component from Bugzilla, if you feel the component has been renamed incorrectly please reach out.
*** Bug 1647092 has been marked as a duplicate of this bug. ***
Martin Marina and Dominik seems content with the following.
When a new network is created, we would show an Editable checkbox next to it.
As long as the network name is Latin-only and short, the checkbox is off by default. However, the user CAN turn it off, signifying that s/he is fine with onXXXXX bridge names.
If the network is long or has fancy chars, the checkbox is on and cannot be turned off.
The EditableName boolean should be exposed by REST, validated on input, and stored in the DB.
This request is not currently committed to 4.4.z, moving it to 4.5
We are not putting any more effort into CloudForms, this product has been put into Maintenance. If customer still requires this feature, he need to open an RFE to IBM, who took over of future ManageIQ productization.