client: don't disable TLSv1, TLSv1.1 by default that breaks VMware env

[yadvr]

This fixes the issue that TLSv1 and TLSv1.1 are still used by CloudStack
management server to communicate with VMware vCenter server. With the
current defaults, the setup/deployment on VMware fails. Users/admins
can however setup the security file according to their env needs to
disable TLSv1 and TLSv1.1 for server sockets (8250/agent service for
example).

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

[yadvr]

Without this fix, by default the env deployment fails for older versions of VMware such as 5.5 and 6.0 (less than up3).
@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[borisstoyanov]

LGTM, let's trigger vmware tests on this one

[blueorangutan]

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2648

[yadvr]

@blueorangutan test centos7 vmware-55u3

[blueorangutan]

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests

[blueorangutan]

Trillian test result (tid-3446)
Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 34232 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3238-t3446-vmware-55u3.zip
Intermittent failure detected: /marvin/tests/smoke/test_deploy_vm_root_resize.py
Smoke tests completed. 68 look OK, 0 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File

[DaanHoogland]

lgtm, block dev. let's think of additional procedure for production sites