VMware Cloud Community
davlloyd
Hot Shot
Hot Shot

vSphere Update Manager and the Missing PowerShell Libraries

So as we move into the vSphere world and look to updating and porting the existign automation scripts from our VI3.5 environment a slight hickup occurs. First hint of an issue is the lack of of a PowerTools installer with the Update Manager install source. Looking further and it sinot included in the version 4.0 VIM set either. OK then install the prior release version as indicated as an option within the administration guide, problem is that it will not instalkl with 4.0 installed as it wants 1.5.

So this is all great and looking at other opions which can be either direct through the SDK which as with the Update Manager CLI seems to lack any form of documentation let along a WSDL. So going forward interested in hearing how others are approaching the automation of the Update Manager environment in vSphere as there may be something I am missing. We automated everything we can through the SDK and were hoping to transition to powershell which Update Manager was the first full PowerShell manasged service. Looks like going to the VUM SDK is the only option as the CLI is the spawn of the devil!

Reply
0 Kudos
13 Replies
harkamal
Expert
Expert

Pheww... am also stuck with the same issue. PS library does not work with PowerCLI. VMware said they have made this functionality in vSphere orchestrator, but thats not needed.

I have been using VI SDK for all around automation, but never heard of VUM SDK -- can you point me to the right link please, thanks.

Reply
0 Kudos
AllanChristians
Enthusiast
Enthusiast


Same here, this points to a component that lacks the nessesay tools to be "ready", would love to get this fixed.



/Allan

http://doitsmarter.blogspot.com/

/Allan http://doitsmarter.blogspot.com
Reply
0 Kudos
Harkamals
Contributor
Contributor

Has anyone used vOrchestrator API's for VUM automation

Reply
0 Kudos
AllanChristians
Enthusiast
Enthusiast

Prev this worked without vSphere, and when using vcenter 2.5 at some sites makes this not feasible.

/Allan

/Allan http://doitsmarter.blogspot.com
Reply
0 Kudos
harkamal
Expert
Expert

But have u worked or do you know how to manage VUM using vOrchestrator ? I am interested in knowing more

For VC2.5 it is no issue, we have VITK

For vSphere VUM automation becomes a challenge

Reply
0 Kudos
davlloyd
Hot Shot
Hot Shot

So the VUM powershell libraries were only experimental hence they felt it was acceptable to drop them all together. This goes away to explain some of the bugs int eh cmdlets that we had to write around but still seems unusual as PowerShell is supposedly the strategic way forward for VMware products. Still no joy getting anything that may be usable around the SDK as defined in the VUM web services.

The use of the Orchestrator API is a possibility if it suits...

Reply
0 Kudos
harkamal
Expert
Expert

What do you mean by "VUM web services" ?

As far as I know, Web service running on esx host is VI SDK, which we access as https://virtualCenterServer/sdk or https://esxServer/sdk

If there is a VUM webservice, please point me to the directions, I will write equivalent code as vum cmdlets

Thanks.

Reply
0 Kudos
harkamal
Expert
Expert

..

Reply
0 Kudos
davlloyd
Hot Shot
Hot Shot

The Powershell cmdlets will not be available for a possible 9 months so it is not a quick fix for anyone trying to move to vSphere and automate the update manager service. At least they are reversing their stance on pulling them!

Reply
0 Kudos
LucD
Leadership
Leadership

I suspect this info comes from a VMW source ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
harkamal
Expert
Expert

...

Reply
0 Kudos
davlloyd
Hot Shot
Hot Shot

So in closing I thought I would have a final whinge in relation to this. In the end they are looking at the re-introduction of the powershell libraries for VUM but this will not occur within the next 6 months. here is also a notable absence of any alternate recommendation for automation around Update Manager that VMware can suggest which is interesting.

So in summary if you are looking at going forward with vSphere and have a singificent estate that is focused around delivery and process automation you shoudl drop any consideration for the use of Update Manager in the design. You also need to question going forward the adoption of the PowerShell as the automation framework as this seems to demonstrate a questionable commitment in that area.

Reply
0 Kudos
admin
Immortal
Immortal

Our commitment to PowerCLI, to put it another way, PowerShell automation for core vCenter/ESX is considerable. At this point PowerCLI is very popular and as of now there is no other alternative with any real traction coming out of VMware. PowerCLI is in it for the long run. Agreed that other VMware solutions need to improve their offerings and level of commitment.

=====

Carter Shanklin

Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]

Reply
0 Kudos