ClusterInfo v1.3 is not very wieldy and extendible

[vogxn]

As a part of this commit the ClusterInfoV13 class was introduced to deal with the newer version of the cluster API. The previous form ClusterInfo had setters for each property (spot, security settings, ec2 settings etc) to update the specific parts of the cluster. Eg: If I needed to update only the spot instance properties I had only to call set_spot_instance_settings(..). Now I have to call the long form set_cluster_info(..) on each update. I cannot call the double underscored __set_spot_instance_settings(..) anymore since these are changed into _ClusterInfoV13__set_spot_instance_settings(..) because of python's name mangling. This is supremely frustrating and breaks a lot of test code that we have built up which needs to be rewritten as __Cluster_set_spot_instance_settings(..) or the long form update Cluster.set_cluster_info(..) for each update call to a cluster object.

Is it possible to convert these setters to @property-ies because that's how setters are exposed in Python. Was there a strong reason to hide the v1.3 setters deviating from the norm that was in v1.2 where setters were public?

[vogxn]

This was merged a while ago. Closing