Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 21 2018 20:54
    bbansalWolfPack commented #9
  • Jan 16 2018 10:31
    lenniebriscoe opened #11
  • Aug 21 2017 19:26
    kguirguis synchronize #13
  • Aug 14 2017 14:42
    kguirguis synchronize #10
  • Aug 14 2017 13:45
    kguirguis commented #13
  • Aug 09 2017 21:13
    reedog117 commented #13
  • Jul 31 2017 20:19
    kguirguis opened #10
  • Jul 31 2017 20:18
    kguirguis opened #13
  • Mar 27 2017 14:26
    korzhev commented #9
  • Mar 13 2017 20:04
    Syavne opened #9
  • Feb 09 2017 21:52
    reedog117 commented #8
  • Feb 09 2017 17:34

    reedog117 on master

    Update the version number. Merge pull request #12 from cha… (compare)

  • Feb 09 2017 17:34
    reedog117 closed #12
  • Feb 09 2017 17:34
    reedog117 closed #11
  • Feb 08 2017 10:23
    chabou-san opened #8
  • Feb 08 2017 08:53
    chabou-san commented #11
  • Feb 08 2017 08:51
    chabou-san opened #12
  • Feb 07 2017 21:17
    reedog117 commented #11
  • Feb 07 2017 09:02
    chabou-san opened #11
  • Nov 10 2016 20:14

    reedog117 on master

    Add HostSystem to managed objec… Merge pull request #7 from mzeh… (compare)

Patrick C
@reedog117
usually when you pass in creds to either it handles the connect process and defines sessionManager for you
if you're curious what the whole handshake process looks like it's at https://github.com/reedog117/node-vsphere-soap/blob/master/lib/client.js#L131
first step that it always does is call RetrieveServiceContent with 'ServiceInstance' as the argument -- then it grabs the SessionManager variable from the result of that for logging in
Jspenc72
@jspenc72
n-vs-soap
Ya i was looking through that code earlier today.
Jspenc72
@jspenc72

It might be the same error as

reedog117/node-vsphere-soap#2

I will test with 0.8 of soap dependency.
Patrick C
@reedog117
ah -- i thought i locked the soap version to .8 -- i might be wrong
Jspenc72
@jspenc72
Looks like that was the issue.
It worked after I installed soap 0.8.
So this project i told you about that will use node-vsphere-soap is scheduled to start tomorrow.
Do you have time to discuss via Skype tomorrow night?
Jspenc72
@jspenc72
As far as updating the plugin I am thinking it will be best to start by creating a promise version of node-vsphere-soap and then building up the higher services from there.
Let me know if you are available to discuss or if you can provide testing and feedback.
Patrick C
@reedog117
I can discuss tomorrow via skype
I need to double check that my module is locking to v0.8 soap
Jspenc72
@jspenc72
Ok sounds good
After doing a little research I am sold on bluebird.
I am excited to test it out on this provisioned version of node - vsphere - soap
Promisified** version
Patrick C
@reedog117
i'll be free anytime after 10p mountain tonight to chat
just let me know what works best and we can go from there
Jspenc72
@jspenc72
Ok can we plan on 10:15?
Patrick C
@reedog117
sounds good -- just got online now
gitter on my iphone was acting funky so couldn't reply earlier
Jspenc72
@jspenc72
No worries
Jspenc72
@jspenc72
Im on Skype now jspenc72
Patrick C
@reedog117
ok
Patrick C
@reedog117
all righty so npm is finally updated so it locks the nv-soap module at 0.8.0
i'm going to get the nv module ready and upload as is at first, then start throwing comments in
Jspenc72
@jspenc72
Wonderful!
Thank you
Patrick C
@reedog117
so the nv module is up
it's npm install vsphere not npm install node-vsphere
i want to rename node-vsphere-soap to vsphere-soap in npm but not sure how to do it
Jspenc72
@jspenc72
I think you may need to just create a new module and remove the old one.
Patrick C
@reedog117
hopefully that examples folder in nv should be helpful for people
Jspenc72
@jspenc72
I think it will be!
Jspenc72
@jspenc72
Ok so I've replaced the event emitter setup you had in nvs.
With bluebird promises
And restructured the module a bit.
Patrick C
@reedog117
nice! awesome -- thanks. we should probably add you to the README.md as contributing
Jspenc72
@jspenc72
Ill commit and send you a pull request.
Im taking a little different approach than you did.
Id like your feedback
It may not be until this evening.
Patrick C
@reedog117
no problem
Mumshad Mannambeth
@mmumshad
Anyone there?
I am unable to catch error with the vSphere client. If I give a bad address or credentials it throws an uncaught error as below
error contents : <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring>Cannot complete login due to an incorrect user name or password.</faultstring><detail><Invalid
LoginFault xmlns="urn:vim25" xsi:type="InvalidLogin"></InvalidLoginFault></detail></soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
events.js:146
      throw err;
      ^

Error: Uncaught, unspecified "error" event. (<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring>Cannot complete login due to an incorrect user name or password.</faultstring><detail><Invalid
LoginFault xmlns="urn:vim25" xsi:type="InvalidLogin"></InvalidLoginFault></detail></soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>)
    at Client.emit (events.js:144:17)
    at EventEmitter.<anonymous> (\node_modules\node-vsphere-soap\lib\client.js:178:14)
    at EventEmitter.g (events.js:260:16)
    at emitOne (events.js:77:13)
    at EventEmitter.emit (events.js:169:7)
    at _soapErrorHandler (\node_modules\node-vsphere-soap\lib\client.js:236:13)
    at \node_modules\node-vsphere-soap\lib\client.js:92:9
    at \node_modules\soap\lib\client.js:130:7
    at \node_modules\soap\lib\client.js:230:16
    at Request._callback (\node_modules\soap\lib\http.js:60:7)
KevinDavidMitnick
@KevinDavidMitnick
does anyone use pyVmomi to get esxi content ?i have a question, how to know which host one virtual machine belong to ?