Home > Blogs > VMware {code} > Monthly Archives: May 2017

Monthly Archives: May 2017

SF Bay Area Microservices and Cloud Native Apps Meetup: 05/16 Event Follow-up

We had the pleasure the other week to once again host the SF Bay Area Microservices and Cloud Native Apps Meetup, this time in collaboration with our Cloud Native Apps team (thanks for the refreshments!). More than 100 people showed up, thanks everyone for making the trip!

Please find the presentations and the video recording below.

Kubernetes on AWS

First talk came from Shri Javadekar, MTS at Applatix. AWS provides a feature-rich and battle-hardened infrastructure to run Kubernetes. However, getting the architecture right for running a production grade, reliable and scalable Kubernetes cluster is not straightforward. In this talk, Shri presented his team’s experiences in running Kubernetes on AWS to achieve that and talked about the problems and limitations they ran into.

Download slides (PDF).

Deploying Microservices With Spring Cloud Netflix On Nirmata

Deen Aariff, Santa Clara University, shared his experience learning Microservices and deploying the Spring Pet Clinic Application, which uses Spring Cloud Netflix OSS components, on Nirmata. Deen highlighted some key features of Spring Cloud and Nirmata that both helped him as a student better understand microservices and made deployment of the application a smooth and accessible task.

Micro-segmenting Containers: The Why and The How

Last but not least, our very own Ali Khayam, Director, Photon Networking at VMware, showed how containers are the new vehicle for delivering applications in private and public clouds. Many container PaaS and orchestration projects have emerged over the past few years; each aiming to simplify the lifecycle of application development and maintenance. However, many open questions around security of containerized workloads remain unanswered. Similar security questions existed for VMs in the past, until microsegmentation allowed security to migrate from the perimeter to the VM. Ali covered some of the key security requirements that an enterprise-grade container IaaS solution is expected to meet and discussed which aspects of VM microsegmentation are readily applicable to containers, and which ones are not. Finally, he went into explaining how VMware NSX is operating as a base networking and security platform that provides container micro-segmentation for both vSphere and non-vSphere environments.

Download slides (PDF).


As usual, if you haven’t done so already, please check out the VMware {code} program to learn, code and connect. Sign up for free: https://code.vmware.com/join

vSphere HTML Client SDK Version and Plug-Ins Compatibility

This post was authored by Ina Uzunova, Product Owner of vSphere Client SDK

This blog gives a brief overview of the HTML Client SDK version and plug-ins compatibility. It will answer a common question among plug-in developers: “Which SDK version should I use?”

There are three major variables in the compatibility matrix you need to consider:

  • vCenter Server version
  • vSphere HTML Client version
  • vSphere HTML Client SDK version

vSphere HTML Client is released for the first time in vSphere 6.5 release and its compatibility with vCenter server is officially documented here.

vSphere Web Client SDK 5.1 contained initially Java and Flex libraries, Extension points and tools. JavaScript APIs are released for the first time in the vSphere Web Client SDK 5.5 U1. They have been improved, extended and alongside the existing Java libraries, extension points and tools became an independent section of the vSphere Web Client SDK 6.5 called the vSphere HTML Client SDK 6.5. It lets you build plug-ins which are supported on both the vSphere Client and the Flex-based vSphere Web Client.

SDK Version used to create the HTML plug-in vSphere Web Client 5.5 U1 vSphere Web Client 6.0 vSphere Web Client 6.5
vSphere Client 6.5
5.5 U1 Yes Yes Yes
6.0 No Yes Yes
6.5 No Yes Yes

Note: To ensure plug-in compatibility you must follow the instructions for upgrading your plug-in.

vSphere Web Client SDK 5.5 U1 has several known limitations and a smaller set of supported JavaScript APIs compared to the vSphere HTML Client SDK 6.5.

Unless you need to support the vSphere Web Client 5.5 U1, we recommend that you use the latest vSphere HTML Client SDK 6.5. It will ensure that your plug-in is compatible with Flex-based vSphere Web Client 6.0, Flex-based vSphere Web Client 6.5 and vSphere Client 6.5, and you can take advantage of all latest APIs, tools and improvements. The differences between vSphere Web Client SDK 6.0 and 6.5 are documented in the vSphere Web Client SDK 6.5 release notes.

For more details please refer to the official documentation.

VMware {code} Briefing: 05/11 Event Follow-Up

We had a fun time at our first-ever VMware {code} Briefing last week. Thanks again to Kyle Ruddy for the presentation (click here to watch the recording) and to Alan Renouf and Jake Robinson for answering questions in real-time.

Here’s a transcript of the Q&A part of the webinar, edited slightly for clarity:

Q: When might we expect to see functionality for Instant Clones worked into PowerCLI?
A: The APIs are not public for Instant Clone as yet, once they are we’re sure it will be a high priority.

Q: Please include cmdlets for vSphere Replication.
A: Thanks for the request! We are waiting for a public API for this feature from the feature team. Please do pass on your need to the vSphere Replication team and we will also remind them (again).

Q: Cmdlets for VDS NIOC shares and such would be useful at some point if it’s not already in there.
A: Thanks for the feature request! And just to be sure you know, you can do this today via Get-View (we know it’s more complicated this way).

Q: Do you have the PSversion value from $psversiontable that is needed for the prereq?
A: Good question! It’s basically any version of PowerShell that supports the nuget cmdlets as shown on the screen right now. Can’t remember how far that goes back but quite a way. Powershell 3 (any build) and on should work. Of course, we recommend using the latest available.

Q: Offline installation process is cumbersome, especially for data center and DMZ machines. One EXE is much easier.
A: You can also just copy the folders straight to the modules folder, no admin rights required unlike the EXE/MSI. You can download the modules zip files from the gallery API as well. Some orgs that use Powershell as a strategic advantage also run their own private gallery, enabling all machines without access to the Internet to use the install and update cmdlets.

Q: Do you always have to use Connect-? to initiate the auto loading of the modules?
A: No, any cmdlet in the PowerCLI module will auto load it. Connect- is just normally the first run.

Q: We need Mr Lam’s xVC-vMotion script made into a cmdlet!
A: Check this out: https://blogs.vmware.com/PowerCLI/2017/01/spotlight-move-vm-cmdlet.html As Jake said, this is already part of Move-VM in the latest PowerCLI version.

Q: How come no one uses the new Show-Command? It clarifies parameters so much easier for demos.
A: Love that cmdlet! http://www.virtu-al.net/2013/05/31/using-show-command-with-powercli/

Q: I can’t upgrade to PSV 5 on my Windows 7 Box, but am able to get it to work on my Win10 box.
A: Powershell 5 is a part of WMF 5. Hit us up on the VMware {code} #PowerCLI Slack channel to share some more detail!

Q: Is Log Insight going to get any cmdlets soon? I saw someone had a GitHub one but is a bit dated and limited.
A: Please ping us on the VMware {code} #PowerCLI Slack channel with what Log Insight tasks you want to automate!

Q: Any plans or timeline to add NSX into PowerCLI?
A: Yes, we’re working hard on it. Stay tuned!

Q: What is a practical use case for the vROPs cmdlets?
A: We have seen customers use the cmdlets for many use cases ranging on custom reporting to actions based on the information in vROPs using PowerCLI to react to issues etc. With the entire Public API being available through the cmdlets it really is down to your imagination/requirements.

Q: What about Onyx for vSphere 6.5?
A: Our hope is to provide support for this on the HTML 5 client in the near future. Onyx is important to us!

Q: Onyx for the HTML5 client?
A: Coming in the future to a Fling site near you.

Q: Any plans on porting the vic-create cmd over to powercli?
A: The long term goal of PowerCLI is to support all VMware products, including VIC! 🙂

Q: Is there going to be an officially supported version of PowerVRA by VMware in the future? https://www.powershellgallery.com/packages/PowervRA/2.0.0
A: We want to support Powershell modules for all of our products. 🙂

We hope that was helpful. If you have further questions regarding this latest PowerCLI release or PowerCLI in general, just head on over to the #PowerCLI channel on Slack. In case you’re not a member yet, go and sign up first (you’ll receive your personal Slack invite right away).

VMware {code} Briefing: What’s New with VMware PowerCLI 6.5.1

VMware PowerCLI 6.5.1 was released on April 20th and it contained some significant improvements and changes! Whether you’re an occasional PowerCLI user or a power user, you’re not going to want to miss this special briefing!

VMware {code} Briefing – What’s New with VMware PowerCLI 6.5.1
Thursday, May 11, 2017
9am Pacific (12pm Eastern)
Via WebEx
Online registration

Kyle Ruddy will be our guide and presenter. Make sure to join the #PowerCLI Slack channel to join the conversation before, during and after. Not a VMware {code} member yet? Join here.

See you there!