{"action":"opened","issue":{"url":"https://api.github.com/repos/vmware/vic/issues/3087","repository_url":"https://api.github.com/repos/vmware/vic","labels_url":"https://api.github.com/repos/vmware/vic/issues/3087/labels{/name}","comments_url":"https://api.github.com/repos/vmware/vic/issues/3087/comments","events_url":"https://api.github.com/repos/vmware/vic/issues/3087/events","html_url":"https://github.com/vmware/vic/issues/3087","id":188381932,"number":3087,"title":"Adding VCH 0.7.0 as a host in Admiral (lightweight Container Management platform)","user":{"login":"vmwarelab","id":19843322,"avatar_url":"https://avatars.githubusercontent.com/u/19843322?v=3","gravatar_id":"","url":"https://api.github.com/users/vmwarelab","html_url":"https://github.com/vmwarelab","followers_url":"https://api.github.com/users/vmwarelab/followers","following_url":"https://api.github.com/users/vmwarelab/following{/other_user}","gists_url":"https://api.github.com/users/vmwarelab/gists{/gist_id}","starred_url":"https://api.github.com/users/vmwarelab/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vmwarelab/subscriptions","organizations_url":"https://api.github.com/users/vmwarelab/orgs","repos_url":"https://api.github.com/users/vmwarelab/repos","events_url":"https://api.github.com/users/vmwarelab/events{/privacy}","received_events_url":"https://api.github.com/users/vmwarelab/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-09T23:41:58Z","updated_at":"2016-11-09T23:41:58Z","closed_at":null,"body":"**VIC Version: 0.7.0**\r\n\r\n```\r\n// A self-contained demonstration of the problem follows...\r\n\r\nTrying to add a VCH VM deployed with TLS as a host in Admiral\r\nA new TLS options were introduced it seems in VIC 0.7.0 and and i m trying to understand which is the right option to use.\r\n\r\nif someone can explain what each of those options means and which one to use . or can direct me to a document that outlines what each of the options means or maybe provide examples :\r\n```\r\nCommon Name must be provided when generating certificates for client authentication:\r\n--tls-cname=<FQDN or static IP>    # for the appliance VM\r\n--tls-cname=<*.yourdomain.com>  # if DNS has entries in that form for DHCP addresses (less secure)\r\n--no-tlsverify                                     # disables client authentication (anyone can connect to the VCH)\r\n--no-tls                                              # disables TLS entirely\r\n```\r\n\r\nOne of the things i used to see with VIC 0.6.0 without explicitly using any TLS options during the deployment, that it used to create one pair of public and private (key) certificates on the client machine for you after the deployment.. I used these certificate as credentials in Admiral when adding the host. \r\n\r\nand that is where i m finding difficulties with the VIC 0.7.0 where \r\n1. if you use TLS the certificates are created in a folder named after the deployed VCH VM \r\n2. there was more than one certificate pair which was confusing to decide which pair to use as the host credentials in Admiral .\r\n\r\nany guidance on this is appreciated. \r\n"}}
{"actor":{"display_login":"vmwarelab"}}