Today Pivotal announced the availability of Pivotal CF. Jointly developed with VMware, the Pivotal CF product includes a packaged and supported version of the Cloud Foundry open PaaS for VMware vSphere.
In April 2011 VMware first launched Cloud Foundry, an Apache-licensed open source Platform as a Service (PaaS) and an associated vSphere-based public cloud service. A year later, in April 2012, we announced a DevOps toolchain called BOSH, used to deploy and manage Cloud Foundry at scale on virtualized infrastructure. In April 2013 VMware and EMC formed Pivotal, a spinout company using technology from both companies including Cloud Foundry.
VMware’s vision for Cloud Foundry has always been to deliver maximum agility to application developers across both public and private cloud environments. In working with Pivotal to deliver Pivotal CF we have fulfilled that vision, bringing the incredible productivity of Cloud Foundry to vSphere customers.
Updated based on feedback. Thanks for the comments!
I’d like to revisit the question “are ESXi patches cumulative”? This time I hope to hammer home the point with an example.
In short, the answer is yes, the ESXi patch bundles are cumulative. However, when applying patches from the command line using the ESXCLI command you do need to be careful to ensure you update the complete image profile and not just select VIBs.
There are two ways to update VIBs using the ESCLI command. You can use either the “esxcli software vib update …“ command or the “esxcli software profile update …” command. The “vib” namespace is typically used with the optional “-n <vib name>” parameter in order to update individual VIBs, where the “profile” namespace is typically used to update the host’s image profile, which may include multiple VIB updates. The key is when applying patches use the “profile” namespace to update the complete image profile opposed to using the “vib” namespace to update selected VIBs.
The 2013 VMware Fling Contest is now open. Do you have an idea on how certain features or functionality could be improved upon? Can you think of an app that would make the life of a system administrator so much easier? Do you have a repetitive task that you wished you could have automated in your vSphere environment? Or a decision making tool for certain tasks? We are looking for you, our customers & users, to propose ideas for new VMware Flings. Our panel of judges will pick the winner. The submitter of the winning entry will win a free pass to VMworld 2014.
Last year we got over 120 submissions. We’re also planning to release a new Fling (Proactive DRS) at VMworld that was built based on last year’s winning winning idea.
Recently I installed vCenter Log Insight, which by the way has one of the easiest and intuitive installers and configuration wizards ever!
After the Install and during the configuration you can easily add your vCenter server and vCOPs server so that monitoring can start straight away.
As an extra configuration step you can extend the default logging by setting up each ESXi host to use the Syslog server which is built into Log Insight, the process for this can be found in the documentation located here.
As per the documentation this means either going to each host and configuring the Syslog settings, configuring them manually through the shell or running the configure-esxi script through an SSH session.
As I already had a PowerCLI session open to my environment I wrote a quick PowerCLI script to achieve the same thing, the following script will configure the Syslog settings for each ESXi host to send their events to Log Insight…..
A commonly requested thing that people ask for from vSphere Replication is more consolidated reporting. You can set alerts in vCenter to key off of various things that surface from vSphere Replication, but it is not exactly a consolidated list when doing so. What people are looking for is a common interface to pull together *just* vSphere Replication alerts for things like RPO violations.
My good friends and colleagues Alan Renouf and Lee Dilworth have identified a really elegant way to pull this information from vCenter to generate a report that will tell you about any RPO related alerts, such as historical RPO that is violations, when they occurred, and for how long using the ever useful PowerCLI.
Every fellow geek who first saw Jurassic Park twenty years ago (Has it really been that long??) cringed when Lex Murphy sat down at a Silicon Graphics workstation and exclaimed the line above. I’m reminded of this line all the time when I talk to some customers who I find treat their ESXi systems like they would a Unix or Linux system. I’m here to tell you, it’s not.
A shell does not an OS make
Did you know you can run a Unix bash shell on Windows? Heck, you can even run a Unix bash shell on OpenVMS! Neither of them are Unix systems, obviously! And neither is ESXi.
Logging into an ESXi shell, whether via SSH or via the local console using ALT-F1, brings you into a Unix-like shell.
This week I was reminded of that great Wayne Gretzky quote,
“I skate to where the puck is going to be, not where it has been”.
How is that relative to the Software Defined Data Center (SDDC)? Well, because things are moving so fast! That virtualization infrastructure you have today (thank you for my paycheck!) is introducing new challenges in IT and Security management. What was once a few servers, some network and storage and a firewall is growing into hundreds, if not thousands of VM’s, hybrid clouds, tiered storage and stretched networks. There are new tools to learn and new innovative capabilities to leverage.
But it’s getting very complex!
Yes. It is. Every new technology seems complex at first. Every new technology brings benefits and challenges. (Remember the pre-PC era? I do!) But, here’s the good, no, AWESOME part, it’s becoming increasingly easier to automate, validate and assess. However, if you are still managing and securing this new infrastructure using your old methods, you may find yourself skating to where the puck was and not where it’s going.
For those of you who have tried to import an OVA directly into vCloud Director have probably noticed that this is not supported and only an OVFfile can be uploaded. However, it is possible to upload an OVA directly into vCloud Director, but it does require the use of another tool called the ovftool which is multi-platform command-line utility for OVF/OVA management. This article was motivated by a recent internal discussion and I thought I share this little tidbit in case it was not very well known.
vSphere 5.1 Update 1 was just released last week and one of the things that caught my eye while reading through the release notes for ESXi 5.1 Update 1 was a new enhancement to hostd logging:
Component-based logging and advanced configurations added to hostd log level
To avoid difficulties in getting appropriate logs during an issue, this release introduces component-based logging by dividing the loggers into different groups and prefixing them. Also, new advanced configuration allows you to change hostd log’s log level without restarting.
Though this enhancement is targeted for troubleshooting purposes and will most likely be used when working with GSS. I thought I would walk you through on how this feature works as there were not much detail in the release notes.