Comment 6 for bug 1476957

Using "fuel --env 1 deployment upload" is not the best way to change ip addresses, and non-working plugin is not the worst case which user can get, since this data do not get deserialized from json into db models form, you can get ips duplication problem easily.

It will be much easier to implement and to support fully functional cli for ip management, instead of a hack ("fuel --env 1 deployment upload") which creates only problems, also I don't see that we have documented somewhere that user mustn't use until he understands consequences pretty well.

1. there won't be simple backport, we should document that user should not use "fuel --env 1 deployment upload" to change ip addresses, and it should be used for developers only

2. for 7.0 (or higher) we should create appropriate handler for ip management, I think we should decide weather it's feature or not and how difficult it will be to implement