Remove 'make redundant' option from the restart network pop-up.

[borisstoyanov]

ISSUE TYPE

• Bug Report

COMPONENT NAME

UI and Primate

CLOUDSTACK VERSION

4.14

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

This should be defined at an offering level, simply having the option to turn a network into redundant shouldn't be available on restart as it's confusing people

STEPS TO REPRODUCE

Restart a network and observe the option

[andrijapanicsb]

@borisstoyanov did you report this to the Primate project (raised bug there?)

[borisstoyanov]

No, I've marked the component as UI and Primate, it needs to be tested against both when picket up.

[yadvr]

@borisstoyanov this is fixed in Primate

[borisstoyanov]

with latests master installed from nightly I can still see this

[borisstoyanov]

this is cloudstack-primate-1.0.0-20201110.x86_64.rpm

[weizhouapache]

@rhtyd @borisstoyanov
I think this works fine in old UI, why remove it from Primate ?

[borisstoyanov]

@weizhouapache while it is working good in majority of cases, this is something that should be set on a service offering level, it's simply not in the right place.

[weizhouapache]

@borisstoyanov what you said is an option to change a network to redundant.

makeredundant is an optional parameter of restartnetwork. it would be better to support it on Primate UI.

(local) mgt01 > restart network
cleanup=        filter=         id=             makeredundant=

[borisstoyanov]

yes @weizhouapache, what I mean is not just the UI but this API shouldn't be there at all. Cloudstack uses offering model to set limits on the resources it gives to users. So if a user wants to have a redundant VR he should have such offering, simply changing that with a VR restart is in conflict with this model.

[borisstoyanov]

As you see this seems to be available to users as well which is not really great.

[weizhouapache]

As you see this seems to be available to users as well which is not really great.

yeah. however we have used that feature for years.
so if you want to change it, could you add a global setting to enable/disable the feature to keep backwards compatibility ?