One of the recent enhancement released in PowerCLI 6.5 R1 was the addition of a new Horizon View Module which allows you to manage Horizon View from a remote connection, this is a huge enhancement from the previous PowerShell implementation which fell short by many means.
This year at VMworld SFO and BCN I was involved in organizing a couple of great hackathons with the @VMwareCode guys and William Lam, these were highly successful and I have to say the highlight of both my VMworlds. The teams were great, the end projects were fantastic and most of all, everyone that attended told me they learned something, this if you ask me was the main objective for the hackathon.
If you attended I do want to extend a huge thanks for joining in, having fun and learning with us.
To put the hacakthon together we needed to build up some environments for people to use, William came up with the idea of using Intel NUCs as these were easily transportable and packed a punch for their size, the equipment we purchased is listed below:
|Quantity: 2||Crucial 16GB Single DDR4 2133 MT/s (PC4-17000) SODIMM 260-Pin Memory – CT16G4SFD8213|
|Quantity: 1||Intel NUC Kit NUC6i3SYH BOXNUC6I3SYH Silver/Black|
|Quantity: 1||Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD (MZ-75E500B/AM) (For Capacity)|
|Quantity: 1||Samsung SM951 128 GB Internal Solid State Drive MZHPV128HDGM-00000 (For Performance)|
For the hackathon we needed to build a lot of these units, whilst we did some parts of it manually William and I recently took the time to complete the automated deployment of these units, in fact the script is not specific to these units, it will work on any ESXi host with 2 disks, one for performance and 1 for capacity. Of course you can also adjust the script to use more disks if you have them!
Once you have ESXi on a USB insert it into the machine and configure it to boot from the USB, after the ESXi machine is on the network you can alter the configuration settings in the start of the script and run the script in the Deployment Script section of this blog to automate the following:
- Configure VSAN in a single node configuration (Unsupported)
- Use the smaller SSD for performance
- Use the larger SSD for Capacity
- Configure NTP on the ESXi Host
- Enable SSH on the ESXi Host for debugging
- Configure the Syslog settings on the ESXi Host
- Deploy the VCSA on the ESXi Host
- Enable VSAN Traffic on the Management Network
- Create a Datacenter
- Create a Cluster
- Create a subscribed content library for William Lams Nested ESXi Library
- Enable Autostart so the VCSA VM starts when the ESXi machine powers on
- Enable SSH on the VCSA Server
One of my most memorable and enjoyable times this year at
VMworld USA was the Hackathon, basically 5 teams of developers and scripters, who had mainly never met each other before were formed and took part in a Hackathon organized by myself, William Lam and the VMware Code team. These dedicated coders gave up free vendor meals and alcohol (OK well maybe we provided both as well) to essentially come code with us on 5 Intel NUC units we had pre-built with vCenter/ESX and VSAN.
The people who were involved ranged from people just learning to coding ninjas and API experts, that’s what I loved, seeing these people learning and working together was truly awesome!
What was involved?
The 5 teams each individually worked on a project which they had come up with and registered before the event, they ended up producing 5 individual projects which were judged and a winning team was selected.
The projects will soon all be available on github or commits to existing projects so the entire VMware community can benefit.
The projects were varied throughout the VMware product range and are listed below:
- Team 1 – Worked on a project which provided community health check against the vSphere platform (vCheck Enhancements)
- Team 2 – Worked on Autoscaling Groups for vSphere
- Team 3 – Worked on writing vSphere DSC resources for Configuration Management
- Team 4 – Worked on Visualizing Ops: VMware Telemetry with Snap and Grafana
- Team 5 – Worked on Using Test Driven Development to validate NSX
I know everyone who attended thoroughly enjoyed the event whether they were part of a team or just turned up to spectate, drink, eat and heckle. Continue reading VMworld VMware Code Hackathon to hit Barcelona 2016
A while back I was contacted by someone who knew that PowerCLI now worked with vRealize Operations (vROPS) and knew it covered the entire API but was unsure how to get to the point where they could achieve what they wanted.
Before I go into what they were doing I highly recommend that if you are interested in learning what is available via VROPs and PowerCLI you check out the following awesome posts by John Dias
- Getting started with PowerCLI for vRealize Operations (vR OPs)
- Working with Recommendations and Statistics in vR OPs with PowerCLI
And specifically check out this post which tells you the more advanced feature of being able to access the entire API and create your own functions.
So, the story around this script was that this person was heavily using vROPs in their environment to monitor and troubleshoot their VMware infrastructure, they had it highly tuned but also used PowerCLI to automate some maintenance and updates of the infrastructure, the problem was that every time they performed these tasks they would get automated alerts from vROPs to tell them that things were down or not behaving correctly.
This while expected was clearly a pain as we all know that unwanted email from a monitoring system can get tedious and eventually ignored to the detriment of something important being missed.
Do you use Cisco UCS? If you do then this will interest you. vCheck is basically a FREE HTML reporting framework that was written to originally check a VMware environment but as it uses PowerShell it is easily adjustable to check anything that is PowerShell enabled, like for instance…. UCS environments.
One of the objectives of me putting vCheck into github was the hope that people would be able to easily pick up the framework and create their own projects to check other PowerShell enabled products, this has already been done with a number of different products as listed below:
|Download Link||Github Project||Example Output Page|
|vCheck for vSphere||Click here||Click here|
|vCheck for Exchange 2010||Click here||Click here|
|vCheck for vCD||Click here||Coming soon|
|vCheck for SCVMM||Click here||Click here|
|vCD Audit script||Click here||Click here|
|vCloud Air Audit||Click here||Click here|
And now you can add Cisco UCS to the list, Joshua Barton has done a great job of using the framework to create a new vCheck edition that will enable UCS Admins to run a check on their systems and bring back any known issues that may be a problem. Don’t forget, this as with all the other vCheck editions is a community project so you can add your own checks very easily in the plugins folder, if you need help then check out this early video which was recorded of me showing how to easily do that.
So what does it check currently?
- General Details
- Recent Faults
- Unassociated Profiles
- High Pool Utilization
- Fault Retention Policy
- Default Adapter Behavior
- Non-Functioning Enabled Ports
- Switching Mode
- Inactive Servers
- Uplink Flow Control
- LACP Policies
- UDLP Policies
- Maintenance Policies
- Default Pool Schema
- Chassis Discovery Policy
- Power Policy
- SEL Policy
What does it look like?
As you can see, the html file that is created, which can also be scheduled to be sent to you as an email looks pretty awesome:
The full example can be seen here: http://www.foobartn.com/assets/examples/example-report.html
How do I download this and get involved?
Visit the Github Rep here: https://github.com/FooBartn/vCheck-UCS/tree/dev
Download it directly from here: https://github.com/FooBartn/vCheck-UCS/archive/dev.zip
And make sure you thanks Joshua on twitter via @FooBartn
I had a conversation with a VMware customer the other day and they were asking if there was a way to automate the addition and removal of a vGPU to a VM dynamically on a requested or scheduled basis, VMGuru has a great post here on what exactly a vGPU is, I highly recommend reading it.
They asked for a PowerCLI command or function to configure the VM graphics card, specifically to assign a vGPU resources to the VM, a desktop user’s VM is configured by default with vSGA (to not tie up vGPU resources) then the user schedules the vGPU resource for a specific time frame using their end user portal, before the scheduled vGPU reservation time frame the user is logged out and the script would kick in. The script would reconfigure the VM settings and assigns a vGPU profile to it, the equivalent of what is being done in the UI as follows:
Recently I was asked to participate in a video where I spoke about the recent Onyx For Web Client fling, this was the winner of the Fling contest held in 2015 and produced and released a while back, more information on the fling and how to use it can be found here, and an informational video can be seen at the end of this post.
As part of the fling I was asked some questions on how it was achieved and what flings take to produce at VMware, I have always liked the idea of flings and fully support a number of flings from VMware both internally to the company and externally, as an addition to the video I thought I would also share the answers to the questions I was asked and give you an insight on what it takes to get a fling out and what it means to the development staff at VMware. Something I would highly recommend in any company to help create and spread innovation throughout the products.
Onyx For the Web Client was certainly close to my heart, being able to give developers and system administrators a record and show feature that allows them to investigate our APIs and learn more is always a good thing.
Find below some Q&A on the fling:
How did you and your team bring the concept from vision to reality?
When someone from the CTO office calls your phone, you answer! But honestly, we already had seen the value and the tremendous following with the old version of Onyx and were aware of the limitations it had, specifically when moving to the web client. We had already been looking at a web client version of Onyx so when this item won the fling contest we jumped at the chance to be involved.
As a customer I used the original version of Onyx on a weekly basis, the value of being able to automate your infrastructure is huge and if you can find out how VMware does a particular task and convert that to code it doesn’t take much to include it in your custom automation solution and prevent yet another manual task, after all isn’t this the promise of the SDDC J
Being the Product Manager of the PowerCLI team all I needed to do was share the vision with an eager team member, in this case it was Atanas Atanasov, a forward thinking developer in the PowerCLI team, someone who is keen to make an impact and provide the best solution for our customers. He took some original work that had already been started as part of an intern project and polished it up, added features and ran through the entire development and internal feedback process to produce an awesome fling!
Innovation is hard to manufacture. How did your team at VMware collaborate to innovate in the context of this project?
Innovation in my mind is coming up with a unique way to solve an important customer issue, this is exactly what we did in this case.
When moving towards an automated datacenter, VMware customers need all the help they can get to quickly move from manual tasks to automated tasks and the most popular method of doing this at the moment is PowerCLI, this fling helps our customers understand exactly what happens “under the covers” and replicate this in their scripts.
How does the VMware leadership team help support innovation within the company? How did this affect the development of the Onyx for the Web Client Fling?
The VMware leadership team were fully supportive. Flings are often worked on in the developers spare time at VMware and I can tell you as the PM for PowerCLI we do not give the developers any spare time! The VMware leadership team helped me to bring incentives to the engineer, in this case a fully endorsed trip to VMworld where he could share his hard work with the customers that he has helped in producing this very fling. Atanas and I were able to stand on the Office of the CTO booth talking about the fling and helping customers with automation. It was great to receive their direct feedback and watch their faces when they saw it in action and how much time it would save them.
What’s the reaction been to the Fling since its release?
WOW! The community for PowerCLI and automation was abuzz with the news of this fling, I lost count of the social media comments and blog posts which called this out as an amazing achievement from VMware and a great help to our customers. When you have a good solution that customers see the value in it is a great day to be a Product Manager at VMware!
Besides this Fling, what’s your favorite Fling?
There are many amazing flings on the flings site, it’s hard to choose just one. I guess I would need to stay on the automation theme though.
PowerActions is probably my favorite fling, this is kind of the reverse of “Onyx for the web client”, it gives our customers a way to feed their automation back into the web client and perform custom scripted reports and actions on the items in the web client. Essentially it allows our customers to customize the GUI and gives them a way to perform automated tasks in their day to day console. Not only this but also share the wealth of expertise that the senior automation engineers have by allowing them to create custom actions for everyone who uses the web client.
Together with “Onyx for the web client” I believe PowerActions is an amazing solution for the automated Software Defined Datacenter.
Make sure you check out the VMware RADIUS site here for more information on this and watch the video below:
This week VMware released a new version of PowerCLI and this release is the most advanced version ever made. As the Product Manager for PowerCLI I am particularly proud of this release as we not only add core functionality to the vSphere cmdlets allowing access to report, manage and automate even more of the core infrastructure but yet again we introduce a number of new features allowing PowerCLI to reach even further into the SDDC and automate and integrate more products.
I always like to ask people what they want to see from PowerCLI next and for a long time now people have been talking to me about vROPs and telling me their use cases of being able to use the rich dataset and analytics provided by vROPs to make decisions and take further action with PowerCLI, something as simple as monitoring a web server to know when it is under duress and provision many more based on these statics all the way to being able to take action on storage systems by monitoring the workload over time. The use cases are endless and now achievable by the latest version of PowerCLI. More on this to come in a future post but lets just say I am excited to see what the awesome PowerCLI community does here.
There is so much to talk about in this release, I wanted to give you an overview in this post and then dive deeper into some of the key features in the future.
More Module Enhancements
The community made it clear that we had to move to modules, and whilst we are still getting there, in this release we made even more module enhancements, both to the core distribution model of PowerCLI cmdlets and also converting more of our code base from snapins to modules. In this version the License snap-in has been converted to a PowerShell module. In the new release the PowerCLI Modules have also been moved to the System PSModulePath allowing all users of a machine to access them once installed.
As briefly mentioned above, a new module and cmdlets have been added to this release to allow access to vRealize Operations, access to the entire public API is available from the $global:DefaultOMServers variable using the ExtensionData property and full cmdlets have been included for the most used features, this gives us a good mix of fully functional easy to use cmdlets and yet the access for advanced users to be able to access the entire API through the ExtensionData property to create their own functions to expose anything to automate vROPs. The following cmdlets were added for using with vROPs:
- Connection: Connect-OMServer , Disconnect-OMServer
- Alerts: Get-OMAlert, Get-OMAlertDefinition, Get-OMAlertSubType, Get-OMAlertType, Set-OMAlert
- Recommendations: Get-OMRecommendation
- Resources: Get-OMResource
- Statistics: Get-OMStat, Get-OMStatKey
- User Management: Get-OMUser
PowerCLI for Update Manager has always been available as a separate downloadable installer but it was hard to work with, you needed to work out which version of Update Manager you had installed on the server and install the exact version of PowerCLI cmdlets to work with it, this was obviously a pain when using multiple versions of vCenter or when trying to manage them from one machine. In this version PowerCLI for vSphere Update Manager is no longer a separate downloadable component or installer and is now included in the core PowerCLI installer, it is selected by default during the PowerCLI install wizard which allows for simpler and quicker deployment and management of VMware products through PowerCLI. Enhancements have also been made to ensure a better backwards compatibility experience of this module and now supports versions of vSphere Update Manager all they back to 5.5.
In the previous release we introduced PowerCLI for vCloud Air, allowing you to connect to your dedicated resources you have purchased and transfer your automation skillset into the cloud. In this release you can now also connect to and manage vCloud Air On-Demand (vCA) instances with the –VCA parameter added to the Connect-PIServer and the new Get-PIComputeInstance cmdlet to list all available compute instances. Existing cmdlets for managing vCloud Director and vCloud Air can be used to work with vCloud Air On-Demand where applicable. Additional to these enhancements a new cmdlet has been added to make it easier and enhance the ability to work with OrgVDC Networks called Get-OrgVdcNetwork.
ESXi Host Hardware
This feature was asked for in the PowerCLI Communities, this is just one of the places we monitor to work out what our future releases look like. New cmdlets have been added to work with ESXi host hardware, these cmdlets give the ability to interrogate your ESXi hosts and provide core system and hardware information.
Two new cmdlets have been added to work with this area:
- Get-VMHostHardware lists host information
- Get-VMHostPCIDevice lists all PCI Devices
Over the last number of releases we keep making enhancements to the storage cmdlets, with VSAN, IO Filters and now a number of enhancements have been made to the storage module introducing new cmdlets for working with VMware vSphere® API for Storage Awareness (VASA), NFS 4.1 and updated vSphere API for IO Filtering (VAIO) cmdlets.
The following new additional cmdlets are now available:
- New VASA Cmdlets : New-VasaProvider, Remove-VasaProvider, Get-VasaProvider and Get-VasaStorageArray
- New NFS Cmdlets: New-NfsUser, Remove-NfsUser, Get-NfsUser and Set-NfsUser
- Added VAIO filters Cmdlet: Set-VAIOFilter
A pet peeve of mine and others
In previous versions of PowerCLI when you started the interactive shell it would always start PowerCLI in the directory where we installed the components, as I watched people use PowerCLI I would see them run a CD\ to get back to the root of the C: or they would use it from the install directory and often their commands would line wrap making it slightly harder to read, a small but hugely beneficial change was made in this release, the PowerCLI starting directory has now been changed from the full install path of PowerCLI to the root of the installation drive.
Business as usual
As usual updates have been made for PowerCLI to support the latest versions of the software it works with, in this case Site Recovery Manager (SRM) was updated to 6.1 and additional functionality has been added to discover SRM servers when they are deployed in a “shared recovery model” and support has been added for the vCloud Director 8.0 features which are provided by the backwards compatibility agreement of the VCD API. All this and many more bug fixes and speed enhancements.