VMware Cloud Community
cdecanini_
VMware Employee
VMware Employee

vCO VIX plug-in released !

Read the announcement.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
23 Replies
bzjeurd
Contributor
Contributor

Hello Christophe,

Where can we dowload this vCO plug-in ?

In general, where can we dowload VMware vCO plug-ins ?

Another question, plugin-in related : is the vCO Microsoft WMI plug-in available for version 4.1.0 ?

Thank you for your help.

Bz

Reply
0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi,

MS-PlugIn look here:

There you can find the DAR-File for 4.1

-


don't forget: award points to helpful answers

Regards,

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Reply
0 Kudos
Burke-
VMware Employee
VMware Employee

The last line of our announcement included a link to the Fling download page:

"Be one of the first one to download, try, rate and comment it on the VMware labs vCO VIX plug-in fling page." <-- The VIX plugin can be downloaded there at the VMware labs website.

Availability of vCO plugins will vary depending on who the author is and the level of support for the plugin in question. In this case (VIX), the author was the PSO team and we received clearance to release the plugin as a Fling in the labs. Plugins developed by Vendors and other 3rd parties "may" provide downloads via their websites such as MightyCare's recent announcement on a plugin they developed. In other cases, a vCO plugin may be incorporated and released as part of a solution provided by VMware or 3rd parties such as the one demonstrated by NetApp at VMworld this year.

We try to encourage plugin publishers to make announcements here in the forums as well as notifying my team for inclusion on our blog, but that doesn't always happen.

Visit me at for vCenter Orchestrator tips and tutorials Smiley Happy

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
Reply
0 Kudos
bzjeurd
Contributor
Contributor

Thanx a lot guys!

It seemed I need to wear glasses... Smiley Happy

Bz

Reply
0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hello Christophe,

i've installed VIX-Plugin and configured it.

I can not connect to VIX-Server (returns NULL on connect).

Where should i post my problem & configuration?

-


Regards,

visit

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

Have you installed the 64 bits DLLs included in the archive and added them in the path ?

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi Christophe,

thanx for fast reply Smiley Happy

I've unzipped the DLL's in a own folder and add this to PATH (like describred in doku) - on VCO, I have a seperated VC - VCO environment.

After severals non functional test and doing, i also deploy the DLLs on VC and add PATH (cause i'm not so deep in VIX, I try everything 😐 ) - including restarting them.

Server log only show:

2010-11-08 17:28:21.665+0100 INFO Executing workflow 'Check for directory in guest'

2010-11-08 17:28:52.473+0100 INFO (com.vmware.pso.vix/connectToServer) Unable to create object : VixServer : null

2010-11-08 17:28:52.473+0100 WARN Script execution error on workflow : Check for directory in guest / 'connectToServer'(item0) : Unable to create object : VixServer : null

-


Regards,

visit

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

It may be the dns resolution if you use VC domain name.

Change your VC plug-in config to use its IP instead of host name.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi Christophe,

sorry for late response - I've changed the VC-Plugin from DNS to IP in three environments and all works fine now - tomorrow I will do some other changes to test this behavior.

This does not make sense for me. I think my DNS is clean and functional, the two others are customers DEV-Environments - their DNS is sometimes a problem (but actually not) - first i thought some AD policy would break me, but not DNS .

Is this a VIX problem? All other VMware / vSphere parts (VC, VUM, VCO, VCO-WMI, ...) are working fine

Do you think is it a real Environment-DNS problem or a VIX-DNS-IP-problem. I don't wan't to change customers production site to IP.

Thanx again

-


Regards,

visit

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

Setting up the IP address at the VC level is a quick and dirty work around.

If the VIX connection string need a mandatory address then the workflow / action that get the connection string can be modified with using var ip = System.resolveHostName(string_hostName)

I do not have the VIX workflows at hand to provide the fix but it should not be hard for you to do it on your own.

Also please remember that if you want to use the VIX plug-in at customer in production environment you are on your own for supporting the solution (which is technically feasible since the source code is included).

I take the opportunity to thank you for the vcoteam link in your signature Smiley Happy

Regards, Christophe.

visit http://www.vcoteam.info

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
crago
Contributor
Contributor

Has anyone had any success including the example VIX workflows in any of their own workflows? Specifically the run program / script in a guest workflows. It appears that no matter what I try I end up with 'TypeError: Cannot read property "length" from null'

Thanks,

Deric

Thanks, Deric
Reply
0 Kudos
tschoergez
Leadership
Leadership

Hi!

hm, I posted an answer last weekend, but it got lost because of the communities update...

anyway:

Yes, I got the VIX-.Plugin running in my lab.

(See also:

http://communities.vmware.com/message/1636989

Workflow-Example on http://www.vcoportal.de/downloads/extendGuestPartition.workflow

)

Have you add the libraries to your PATH-environment-variable, as mentioned in the docs?

Can you specify, which workflow element is responsible for the error?

Cheers,

Joerg

Reply
0 Kudos
crago
Contributor
Contributor

Thanks Joerg for your reply...  I've checked out the links and that example workflow works.  I was trying to include any of the (but specifically the run program/script in guests) example workflows in one of my own workflows as to not recreate the wheel so to speak.

Simple example schema with get directory contents:

orchestrator.png

This example errors out with "TypeError: Cannot read property "length" from null"

However, I am able to run the Get directory content from guest (or any of the other example workflows) directly without any errors.  Have you been able to include any of the example workflows inside of your own workflow?

Thanks,
Deric

Thanks, Deric
Reply
0 Kudos
crago
Contributor
Contributor

So I've made a little more progress...  Run script in guest does not appear to actually run anything in linux (ran directly or embedded in my own workflow).  Run program in guest does (direct or embedded) and runs fine with the following presentation.  No errors, it just works.

Here's the presentation:

orchestrator-inputs.png

However, if I take that same custom workflow and choose either async = no OR waitcompletion = no then it errors out with the following.

Here's the output:

orchestrator-output.png

[2010-12-21 11:29:23.134] [I] TypeError: Cannot read property "length" from null

The problem is that if I'm running it inside of my own workflow I will probably want to run it synchronously instead of trying to decipher the "trigger" or find and watch a workflow token.

Thanks for any insight...

Deric

Thanks, Deric
Reply
0 Kudos
crago
Contributor
Contributor

I continue to keep digging...  this appears to be completely unrelated to the VIX plugin and more related to how orchestrator handles embedded workflows.  I will continue this discussion in separate, more appropriate thread.

http://communities.vmware.com/thread/296963

Thanks,
Deric

Thanks, Deric
Reply
0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi Deric,

after opening the new thread, could you please leave a link here to follow up - this would be great.

Regards, Andreas

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Reply
0 Kudos
crago
Contributor
Contributor

So after figuring out how to get the `Run program in a guest` workflow working (nested or directly)...  I can't seem to get it to recognize an error.

I've created a simple bash script:

# cat /root/testError.sh
#!/bin/bash
echo "ERROR!!!" 1>&2
exit 1

However, when I run this, the workflow completes successfully.  What would be the proper / preferred way to recognize an error with the `Run program in a guest` workflow?


Thanks,
Deric

Thanks, Deric
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

For those who add to change VC plug-in to its IP address because of VIX failing here is a simple patch I had done some time ago but never released because I had no time to test it enough. As always try this in a test environment first.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
robrtb12
Enthusiast
Enthusiast

Hello,

Would someone be able to compile a new plugin object for this?  I'm not a java expert  Smiley Happy

Thank you

Reply
0 Kudos