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

Monthly Archives: March 2017

April 12 Meetup in Palo Alto: KuberNETes – Networking for Containers

We’re excited to once again be sponsoring the combined Containers #101 and SF Bay Area OpenStack Meetup next month.

KuberNETes (see what we did there? 🙂
Wednesday, April 12, 2017
6:30 PM to 8:30 PM
Cafeteria in the Promontory C Building, VMware Campus
3405 Hillview Ave., Palo Alto, CA


Containers require a new approach to networking. How are your containers communicating with each other? This talk will go through the different network topologies of Kubernetes. How Kubernetes addresses networking compared to traditional physical networking concepts. What are your options for networking using Kubernetes. What is the CNI (Container Network Interface) and how it affects Kubernetes networking. And we will tie this all in to OpenStack, should you want to run K8s with an OpenStack Infrastructure.

A general understanding of basic networking concepts is a good prerequisite for this session. (All are welcome to join, but if you’re a networking beginner, you may want to do a little homework first. 😉

Our presenter will be Nathan Ness, a Technical Product Manager in the Cloud Native Apps BU at VMware. Nathan has spent the last 15 years in the world of networking from physical to the new world of Cloud Native Networking. He has experience with OpenStack and virtualization technologies with an emphasis on software defined networking.

See who else is going and sign up.

Featured Member: Brian Bunke

There are so many great people connecting through the VMware {code} program, it’s hard to keep track. This week, we’re introducing a new feature here on the VMware {code} blog: brief interviews with some of our key contributors to help everyone get a better sense of what’s going on.

Below is the first one. As always, we love to hear your feedback in the comments below, on Twitter or on Slack. If you’d like to be interviewed or know someone we should feature – please get in touch. Thanks!

Who are you, what do you do, and what brings you to VMware {code}?

My name is Brian Bunke, and I’m a Systems Automator for a manufacturing customer in the Seattle area. I joined the VMware {code} community because I interact with VMware products often, and I’m passionate about developing and improving tooling that fellow admins and I consume in our day-to-day lives. Currently, most of my work in the {code} community has revolved around the Vester project.

Briefly, what is Vester?

Vester is a community-driven, open source project written in PowerShell. It uses PowerCLI and Pester to provide a lightweight configuration management solution for VMware administrators. Vester runs tests to ensure your environment matches your config file, and is capable of automatically fixing any problems it finds.

Neat! How can people get involved?

A main goal of maintaining Vester is making tests easy to write and contribute. We hope this interests users in giving a little something back to the project! If you’re interested in learning more, you can review my three-part blog series on how to get started.

You recently shared some code via VMware {code} Sample Exchange. What was that about? And what was your experience?

I wrote a PowerShell function, Get-VMotion, because I found I was reviewing vMotion history often enough that it was worth packaging into a simple command. I wanted to provide it to the community as a way to pay it forward, and the Sample Exchange has some really slick integration with GitHub that made sharing very simple.

Any other ways you’ve made use of this piece of functionality on the VMware {code} website?

The “Requests” area is a cool idea that hasn’t seen much traction yet. If you have an idea for some code that you’re not sure how to write, you can post your request to the community at large. Maybe someone else agrees that it’s a problem worth solving, and has the means to do so!

VMware {code} was launched about a year or so ago. What would you like to see going forward? As we continue to grow and evolve the program, where do you see the biggest opportunities?

I believe there is still a lot of untapped potential in unlocking the developer community on common goals. The Slack team is a great way to self-organize, and I hope {code} can continue to promote those contributions. If community work is encouraged and celebrated, more will be incentivized to participate, and the VMware ecosystem will continue to flourish.

Thanks, Brian! Where can people find you online?

Thanks for the opportunity! I blog at www.brianbunke.com, and you can find me as @brianbunke on Twitter, GitHub, and Slack.

VMware {code} Town Hall: 03/16 Event Follow-Up

Last week, we held our first-ever community town hall over on Slack. Not bad for a first attempt: good turnout, lots of great questions and comments, and participants seemed to enjoy it overall. Thanks again to Alan Renouf, Kyle Ruddy and the rest of their team for trying it out with us.

We’re talking to a number of teams to see when we can schedule the next one. Stay tuned! Have a favorite product team you’d like to ask questions? Leave a comment below, find us on Slack, or tweet us at @vmwarecode – we’ll do our best to make it happen!

Please find the transcript of some of the key questions below, with minor edits for clarity and style.

Summary of questions & answers

Q: How about a method of tying together Windows disks and vSphere disks – it’s a real pain to deal with at the moment when trying to script server builds.
A: Yes, it is a pain. Did you see the scripts available for this already? It gets hard when there are multiple partitions per disk and other OS as well.

Q: Will PowerCLI be joining the others in being open-sourced?
A: Great question! It’s certainly a long-term goal but we have a way to go internally to get to that point.

Q: Any ETA on module auto-loading/discovery for PowerCLI?
A: Can’t give any official dates, but soon!

Q: In PowerCLI, I am using the new abilities to do Linked-Clones for DevOps. Will VMware ever officially release the ability to do Instant Clones?
A: Yes, this is definitely on the short-term roadmap. We need the APIs to be public first.

Q: Are there plans in the work to attach vmk’s to other TCPIP stacks? It can be painful constructing the objects and spec’s.
A: Yeah, clearly this is available in Get-View but agreed it needs to be surfaced up. It’s on the backlog!

Q: For PowerCLI, will VMware ever release a fully supported NSX module?
A: Have you seen PowerNSX? Would love to know what you think of that. We are working closely with the NSX team.

Q: Now that PowerShell is in Linux, when will we be able to run PowerCLI on a Linux box?
A: Yes, check out the PowerCLI Fling and Docker images etc.

Q: Can we hope/expect to see more functionality brought to REST in updates to 6.5, or will it be more along releases?
A: You will see more functionality released via these APIs in future versions.

Q: Are there plans to try and unify all products using the same API approach to reduce the headaches associated with learning all of these different API’s?
A: Our plan is to make all APIs at VMware as easy to use with the tools that developers and admins want to use. More to come on this in the future!

Q: Any ideas if vSphere Replication will get some API support?
A: Wouldn’t that be nice! We’ve been forwarding this to the PM. Can’t comment on his plans for this, though.

Q: For PowerCLI, has VMware put together any packages yet to fully backup vCenter (all configuration settings)? Don’t care about the DB. But having all the backups via PowerCLI would allow for very granular restore of items/settings. I have a version of this I have written myself, but it is not all encompassing, so some things get missed/not restored when you do a full restore/migration.
A: Not as of today (at least that we’re aware of). There is at least one project that’s currently being worked on, though. So, it is certainly on the radar as a known pain point.

Q: Does anyone know of a way to programmatically set Post Power-On Steps under VM Recovery Properties in SRM? I add a command entry for each VM (executed on recovery SRM server) and creating those entries for hundreds of VMs is a big pain.
A: Have you checked the SRM API Guide? Might be in there: https://www.vmware.com/support/developer/srm-api/

Q: Speaking of vCenter alarms… is there any effort to make creation/manipulation of vCenter alarms via PowerCLI easier?
A: Working on getting the APIs made public for this so we can surface it up via PowerCLI.

Q: I’ve got the REST SDK for 6.5. Love it! Do you know if it will work for versions other than 6.5?
A: Content library and tagging work in 6.0, but the rest is exclusive to 6.5. Docs for the 6.0 stuff: https://code.vmware.com/web/sdk/60/vcloudsuite-rest

Q: How long will PowerCLI (officially) support ESXi/vSphere 5.5?
A: As long as ESXi/vSphere 5.5 is supported we will maintain the versions that work with PowerCLI. However, future versions of PowerCLI may not maintain complete backwards compatibility that far.

Q: REST API stuff looks great, honestly. Breath of fresh air! As a PowerShell user, though, I just haven’t been motivated to explore the functionality yet. Any use cases you guys would recommend right now?
A: If you’re happy with PowerCLI and it meets all of your use cases, probably not. It does allow you to more easily consume the API than SOAP and allows for the creation of other language bindings that may not be officially supported such as for Rust, Erlang, etc. As a PowerShell user you are spoiled but if you are building modern applications or looking to use industry REST based tools its worth checking out. “Evolving the vSphere APIs” is a great starting point from the last VMworld.

vSphere Automation SDKs – Open Sourced!

It’s an exciting time! We have started the process of open sourcing our vSphere Automation SDKs! The first ones to be released are the Software Development Kits (SDKs) for REST and Python: https://vmware.github.io/vsphere-automation-sdk

Alan Renouf, the Product Line Manager for the vSphere Automation SDKs (among other things), has a great post detailing the significance of it over on the VMware Open Source blog: https://blogs.vmware.com/opensource/2017/03/09/integration-vmware-vsphere-using-new-open-sourced-software-development-kits

vSphere Automation SDK Open Source Logo

What to Expect

Open sourcing these SDKs are going to have a considerable impact on how they’re consumed, so what should you be expecting with these changes?

The biggest impact: these SDKs are available on GitHub, with no authentication required. Users can clone or download the repository locally or even fork it to their own GitHub account. The use of modern Github integrated tools can ensure these SDKs fit well into your development tooling and procedures.

The first part leads to the next big impact: the frequency of updates. These SDKs being on GitHub allow us to release updates, bug fixes, and other corrections on a much quicker basis!

One of the other big impacts this change is going to have is on contributions. We are actively seeking contributions! Regardless of whether it’s a new sample, an update, or even a request, we want to hear from you! We are dedicated in making these samples relevant to you and making your development experience easier and better than ever before. Please, let us know how we can help you do this.

Getting Started

There are a lot of ways to get started with this new method of access. The easiest way is to check each repo’s README and follow the instructions there.

However, let’s walk through an example. One of the simplest ways, downloading it directly from the SDK’s repo.

Using the vSphere Automation SDK for Python:
Repository Link: https://github.com/vmware/vsphere-automation-sdk-python

Click the “Clone or Download” button, selecting the “Download ZIP” option.
Find the downloaded zip file and expand it.

Downloading the vSphere Automation SDK for Python


If you happen to hit an issue when using one of the SDKs in your environment, or if you’re doing something that doesn’t already exist as a sample, there’s a good chance someone else could benefit from that input. Therefore, we highly encourage contributions to these SDKs.

Each SDK will have the contribution and/or issue process documented in the README. However, I’ll provide an overview of both the sample and issue submission process.

Sample Submission:

  • Include information as part of the resource or folder’s README:
    • Author Name (basic contact info)
    • Date
    • Description (high level description)
    • Known Limitations or Dependencies
    • vSphere Version/s Developed and/or Tested (suggested, but not mandatory)
    • SDK Version/s Developed and/or Tested (suggested, but not mandatory)
    • Language Version/s Developed and/or Tested (suggested, but not mandatory)

Contribution Process:

  1. Follow the GitHub process
  2. Use one branch per sample or change-set
  3. Use one commit and pull request per sample
  4. Post the sample output along with the pull request
  5. If including a license with the sample, use the project license

Issue Submission: Each repo has their own “Issues” tab and should be used to submit any issues or requests

  1. Once on the “Issues” tab, click the green “New issue” button
  2. Provide a title and as much detail as possible in the comment section

vSphere Automation Issue Submission

If you’re submitting a sample, we also recommend adding them to the VMware Code Sample Exchange!


This transition to open source is a big step for us at VMware. This is also just one of the first steps of many which are focused on helping to enable developers and automation focused admins!

Keep an eye on this blog, the Open Source blog, and especially the vSphere Automation SDK page for all the exciting updates and additional news.

March 16 VMware {code} Town Hall: Your Direct Line to the VMware Product Team Behind the vSphere Automation REST APIs, PowerCLI, ESXCLI and vCLI

Do you wish you could have a direct line back to the product teams at VMware?

Something annoyed you about the product and maybe you never knew where to send your feedback?

Perhaps you just love the product and want to give a “virtual” thanks to the wizards behind the curtains?

Following the vSphere Automation team’s big announcement yesterday, we thought it might be a good idea to give everyone an opportunity to check in with them directly and get your questions answered and feelings heard on this and also the other products worked on by this team.

We’re excited to announce our first-ever VMware {code} town hall! For one full hour next week, the team – including Alan Renouf (@alanrenouf), Kyle Ruddy (@kmruddy) and members of the development teams – will be available to answer your questions and discuss the road ahead:

VMware {code} Town Hall
Thursday, March 16
9-10am Pacific Time
Online on VMware {code} Slack
Channel #vsphere-sdks

How to join:

Hope to see you there. Should be fun!

Our Slack Team Is Now 1,500 Members Strong

Since the early days last year, VMware {code} has been running on Slack as its primary community channel. Everyone who signs up for VMware {code} automatically receives their personal Slack invite within seconds, and so far about 5 out of 9 registrants have followed through and joined the VMware {code} Slack team.

Earlier this week, we surpassed the 1,500-team-member mark, an important milestone on our 2017 roadmap. What better opportunity to give a brief overview of what’s currently on offer:

Top 10 largest channels (number of members)

Not taking into account #general and #random (everyone gets tossed into those by default). Anecdotally, the ten below also tend to be among our most active channels:

  1. #powercli (297)
  2. #devops (263)
  3. #nsx (197)
  4. #vra (171)
  5. #cloud-native (158)
  6. #vro (158)
  7. #vsphere (145)
  8. #photon (128)
  9. #vcheck (115)
  10. #events (105)

Top 6 newest channels (number of members)

Our five newest channels were launched between January 28 and February 20, 2017:

  1. #iot (12)
  2. #rbvmomi (3)
  3. #vcd (3)
  4. #vic-doc (18)
  5. #kubernetes (38)
  6. #vcenter (16)

Top 5 fastest growing channels, past 30 days (number of members)

Only taking into account channels that have 25 or more members:

  1. #vrops (49 / +21)
  2. #api-sdk-rest (63 / +21)
  3. #vsphere (145 / +33)
  4. #admiral (40 / +9)
  5. #chef (60 / +12)

Latest question successfully answered in #general

Q: What channel should I join for API coding?

A: There is #api-sdk-rest, #pyvmomi, #govmomi, #powercli, and #rbvmomi. Also, #chef and #puppet, if you are working with those. Finally, #vsphere for general vSphere questions.

Average number of channels joined per team member


Most creative channels, past 30 days

OK, we’re not micro-monitoring every conversation, but over on #vmworld-hackathon and #hackathon-europe people have been sharing a lot of great ideas about what this year’s hackathons should look like. Check it out!
Look forward to seeing you around. In case you haven’t done so already, get started by signing up for free today: https://code.vmware.com/join