{"action":"created","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":1,"created_at":"2016-11-09T23:41:58Z","updated_at":"2016-11-10T07:47:41Z","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 supported option that i can use so i can successfully add it as a host in Admiral \r\n\r\nTLS Options\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 cause they simply didnt exists, that it used to create one pair of public and private (key) certificates on the client machine for you after the deployment in the same folder where VIC files were extracted.. then I would use these certificate as credentials  leveraging the credential certificate option in Admiral when adding VCH as a host.\r\n\r\nProblems\r\n======\r\n1. When using --no-tls . no certificate is generated, there for i am simply forced to use a username 'root' and a password when adding theVCH VM as a host in Admiral but again i have no idea what the password is. so i m stuck . \r\n\r\n2. When using --no-tlsverify . it Generate a self-signed certificate/key pair - private key in ./VCH01/key.pem (VCH01 is a folder named after the name of the deployed VCH VM) . When i switch to the folder the referenced file isnt there.!!! there is no key.pem file . the only file found in that folder is a file called VCH01.env. so here i m stuck again.\r\n\r\n3. When using the --tls-cname=<FQDN or static IP> the difficulties i find here with the VIC 0.7.0 is that \r\n the certificates now are created in a folder named after the name of the deployed VCH VM which is great but there were more than one certificate pair generated here which was confusing to decide which pair i am suppose to use for the host credentials in Admiral leveraging the credential certificate option\r\n```\r\nGenerating CA certificate/key pair - private key in ./VCH01/ca-key.pem\r\nGenerating server certificate/key pair - private key in ./VCH01/server-key.pem\r\nGenerating client certificate/key pair - private key in ./VCH01/key.pem\r\nGenerated browser friendly PFX client certificate - certificate in ./VCH01/cert.pfx\r\n```\r\n\r\nAny guidance on this is appreciated. \r\n"},"comment":{"url":"https://api.github.com/repos/vmware/vic/issues/comments/259622880","html_url":"https://github.com/vmware/vic/issues/3087#issuecomment-259622880","issue_url":"https://api.github.com/repos/vmware/vic/issues/3087","id":259622880,"user":{"login":"vdeger","id":23375020,"avatar_url":"https://avatars.githubusercontent.com/u/23375020?v=3","gravatar_id":"","url":"https://api.github.com/users/vdeger","html_url":"https://github.com/vdeger","followers_url":"https://api.github.com/users/vdeger/followers","following_url":"https://api.github.com/users/vdeger/following{/other_user}","gists_url":"https://api.github.com/users/vdeger/gists{/gist_id}","starred_url":"https://api.github.com/users/vdeger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vdeger/subscriptions","organizations_url":"https://api.github.com/users/vdeger/orgs","repos_url":"https://api.github.com/users/vdeger/repos","events_url":"https://api.github.com/users/vdeger/events{/privacy}","received_events_url":"https://api.github.com/users/vdeger/received_events","type":"User","site_admin":false},"created_at":"2016-11-10T07:47:41Z","updated_at":"2016-11-10T07:47:41Z","body":"Your progress is better than me,  I can not communicate with Admiral with vchhostip:8282 yet :)\r\nVIC 0.6 credentials:  root/password\r\nVIC 0.7 credentials: root/Vmware123!  or root/'Vmware123   I did not try yet."}}
{"actor":{"display_login":"vdeger"}}