That would be fantastic. I think there's a great deal of people using
self-signed certs with vsphere.
On Friday, January 15, 2016 at 12:25:42 AM UTC-6, Brian Coca wrote:
>
> we should add validate_certs=yes|no option as we do in other modules.
>
> On Fri, Jan 15, 2016 at 1:09 AM, Larry Smith >
Looking forward to this patch!
For those testing vmware, i've added a few features to vmware.py dynamic
inventory which ec2.py inventory comes with but were sorely missing in
vmware.py.
instance_filters and --refresh-cache. Plus a bug fix that allows cache_dir
to be found.
https://github.com/
Awesome...Looking forward to the outcome...I really do not want to hack any
python modules to make it work...But understand if that is the only way
short-term.
On Friday, January 15, 2016 at 6:40:51 PM UTC-5, cp...@ansible.com wrote:
>
> I am currently testing a PR for module_utils/vmware.py whi
I ran into a need for this today. How goes your testing? Need any help?
Thanks,
-- Jess
On Friday, January 15, 2016 at 3:40:51 PM UTC-8, cp...@ansible.com wrote:
>
> I am currently testing a PR for module_utils/vmware.py which adds
> 'validate_certs' as an argument.
>
> On Friday, January 15,
I am currently testing a PR for module_utils/vmware.py which adds
'validate_certs' as an argument.
On Friday, January 15, 2016 at 11:30:23 AM UTC-6, Kesten Broughton wrote:
>
> vsphere_guest is based on pysphere and the ansible-extra-modules vmware
> modules are based on psphere, (both of which
vsphere_guest is based on pysphere and the ansible-extra-modules vmware
modules are based on psphere, (both of which are largely abandoned)
but this PR for pyVmomi supported by VWmare should work.
https://github.com/vmware/pyvmomi-community-samples/pull/213/files
A thing you could do, but shouldn
vsphere_copy already supports this, though we really should do it in
the module_utils shared code
On Fri, Jan 15, 2016 at 11:31 AM, Larry Smith wrote:
> Absolutely that would be the way to do this.
>
> On Friday, January 15, 2016 at 1:25:42 AM UTC-5, Brian Coca wrote:
>>
>> we should add validate
Absolutely that would be the way to do this.
On Friday, January 15, 2016 at 1:25:42 AM UTC-5, Brian Coca wrote:
>
> we should add validate_certs=yes|no option as we do in other modules.
>
> On Fri, Jan 15, 2016 at 1:09 AM, Larry Smith > wrote:
> > Yup. I know about the default self-signed but I
we should add validate_certs=yes|no option as we do in other modules.
On Fri, Jan 15, 2016 at 1:09 AM, Larry Smith wrote:
> Yup. I know about the default self-signed but I would assume that either
> pyvmomi module and/or the Ansible documentation might explain on how to get
> around this error. E
Yup. I know about the default self-signed but I would assume that either
pyvmomi module and/or the Ansible documentation might explain on how to get
around this error. Especially just for testing purposes. Thanks for the
reply though.
On Thursday, January 14, 2016 at 3:35:47 AM UTC-5, Marcus Fr
Hi,
by default VMware uses a self signed certificate for the vcenter web
interface.
You could change this against an official one with a trust anchor your
system can verify or configure your play not to verify the certificate. If
that is possible, never used that module myself.
Regards,
Marcus
Just getting started messing with these new 2.0 VMWare modules and seem to
be stuck on an SSL error. Anyone know how to get around this? Any info
would be much appreciated.
fatal: [localhost -> localhost]: FAILED! => {"apierror": "[Errno 1]
_ssl.c:510: error:14090086:SSL
routines:SSL3_GET_SERV
12 matches
Mail list logo
