The new VMFork for pyVmomi Fling brings the VMFork APIs to your vSphere environment
This one landed under the radar somewhat with relatively little fanfare, but July 26th 2016 saw the release of the VMFork for pyVmomi Fling which exposes the Instant Clone APIs to your existing vSphere environment without the need for PowerCLI.
vMustard readers of old will understand my joy of seeing this release after I wrote a part-rant-part-begging letter blog post in early 2015.
Who could blame me, Project Fargo as it was known promised to disrupt the EUC arena and many more after it caught the eye in many a session at VMWorld 2014, however the feature was strangely lacking from the latest vSphere and Horizon releases and it all went very quiet. Since then Fargo/Instant Clone/VMFork has been making it’s way into great swathes of VMware’s product catalog, but API access to the functionality was private and ‘in-house’ only for a long time.
Now however, the new Fling comes as a module that can be imported into pyVmomi- the Python SDK for the VMware vSphere API allowing all access to the Instant Clone greatness with very little overhead.
For the uninitiated, VMFork allows you to spawn live, powered-on VM clones from an existing VM, each with its own unique identity. Leveraging the linked-clone technology that has delighted VDI enthusiasts for years, VMFork uses Copy-on-Write memory to allow near-instant creation of Virtual Machines with ridiculously little overhead. It’s pretty cool stuff.
The requirements to run the Fling are simple, you need to be running the following in your environment:
- Python 2.7.x
- pyVmomi version 6.0.0 or later
- paramiko version 1.16.0 or later
- vCenter and ESXi 6.0
Then you can fork to your heart’s content. You can download the module from the VMware Flings site, where you’ll also find instructions on use and any updates as and when they arrive.