Ability to update container network via vic-machine configure

[chengwang86]

VIC Product version:

OVA version VIC-1.2.1 GA Deployment details:

Environment where the OVA is deployed Production and Dev test Steps to reproduce: Created a VCH with container network without --cnr. Then update container network with network range using vic-machine-linux configure.

Actual behavior: vic-machine-linux configure throws ERROR Found changes to existing container network Container-NW

Expected behavior: vic (vic-machine-os configure) should allow user to update the container network settings if no containers are running on that network. If any containers are running display them, so user can make a decision

[chengwang86]

@kumuduh I moved your issue https://github.com/vmware/vic-product/issues/1029 from the vic-product repo to this repo (for the vic engine team) to better track the progress of this feature.

(Please correct me if I'm wrong) @kumuduh was trying to help a customer with setting up a VCH on their dev environment (to be transitioned to production). They set up a VCH with a certain mal-configured container network, which didn't work (I don't know if vic-machine create succeeded or not). Since they didn't have other container networks available, they wanted to reconfigure the settings of the container network but vic-machine configure does not have the functionality to update the settings of an existing container network (even if it does not have any existing containers).

[renmaosheng]

@yuyangbj is this supported now?

[tsimchev]

We just tested it with VIC 1.4.4 and still there.

[renmaosheng]

@yuyangbj let's try to decide whether we would like to support this or not.