I came to know the Alpine Linux because of its small image size for Docker. Unlike almost 200MB in size of popular CentOS and Ubuntu, it just needs 5MB. That made me wonder if I can get much smaller Linux VM using the Alpine distro for special use cases like network tools.
Note: if you want to read PDF or print it, please feel to download it here.
With the increasing adoption of VMware WebClient, we got more support cases from customers who use it for deploying our search engine appliance. In one sentence, it does NOT work and you will get error messages like, “the provided manifest file is invalid OVF.”
Although it’s an issue caused by VMware, we have to deal with the issue and tell customers how to work around it. I think the issue goes beyond our OVA, but all the other OVA based appliances from all vendors including those from VMware. So the workarounds we suggested to our customers will also benefit you.
IP addresses are important resources and must be carefully managed to avoid duplicated IP issues, which are sometimes very hard to troubleshoot. I still remember that it took a few of us couple of days to root cause a failing new feature, which worked sometimes and did not other times. Because it’s a new feature, we mostly thought it was somehow our bug in code. It turned out not, but caused by the vCenter we were testing actually used a duplicated IP address.
On November 15, VMware offically announced the long-waited vSphere 6.5, which is a big release after 6.0 release early last year. Along with this vSphere release were a few other products like VMware vSAN 6.5, VMware vRealize Log Insight 4 and VMware vRealize Operations 6.4. According to the blog announcement, the vSphere 6.5 offers these high level features and benefits:
Over the weekend, I was trying to export a virtual machine from vSphere using ovftool command line. To my surprise, it was extremely slow. In fact, I wasn’t patient enough to wait for its finish and “Contrl+C” it. Initially I was thinking it could be ovftool issue, so I tried exporting from vSphere Client directly. Still very slow and I had to cancel it as it would run for a few hours according to the progress dialog box.
After more than 4 months of hard work, we are proud to announce the second major release of the product. On the high level, there are 3 major features besides many smaller improvements over the first release based on the customers’ feedback.
1. VM Actions and Group Actions
VMware published a blog “Goodbye vSphere Client for Windows (C#) – Hello HTML5” with two announcements: 1. There won’t be the traditional C# based vSphere Client for the next version of vSphere (no one knows the version yet but it’s safe to call it the next version.). 2. The vSphere HTML5 Web Client Fling will be supported soon (no exact timetable is given). My guess is that it will make into next release of vSphere if not earlier.
The recent release of DoubleCloud vSearch represents a paradigm shift in how we manage data center in the future. Before agreeing with me on that, let’s take a quick look at the history.
Yahoo vs. Google
When the Web first came out in the early 90s, there weren’t many Web sites and pages out there. To help us find pages of interest, a typical directory approach was used. That created the initial success for Yahoo in the first place.
After leaving VMware and VCE, I founded DoubleCloud Inc. While working with many of my clients, we found it’s really a pain point for people to use vSphere Web Client which is quite slow and based on obsolete Flash technology. The old vSphere Client is a lot better in performance and usability, but VMware stopped upgrading it with new features.
While building a new server product of its own kind, we chose virtual appliance as the package. During the development phase, we configured thin disk to save space. But for our beta customers to try out, we decided to switch to thick disk for better performance as the product has to do lots of processing and heavy disk I/O. BTW, we still have a few slots for new beta customers with have large vSphere deployments. Please contact me if you are interested.
Today is the second day of VMworld 2015 in San Francisco. The general session started at 9AM for about one and half hours. Today’s topic includes desktop, networking, and 5 imperatives for digital business.
Today is the first day of yearly VMworld in San Francisco (strictly speaking, it started yesterday with reception party). The general session started at 10 AM for about one and half hours. Having been with VMworld for many times, I found this general session was pretty exciting with quite a few things worth sharing.
When I was doing a demo today, I got an error saying “An internal error has occurred – Error #1099. Reloading the client is recommended, so as to clear any problems left by this error. Click Yes to reload the vSphere Web Client?” After reloading the Web Client, I got the same error. So something has to be fixed on the server side.
There is a big change in the vCenter 6.0 with the introduction of Platform Service Controller. To run vCenter 6.0, there must be a PSC server somewhere: either existing one, or new one installed together with vCenter. For most dev/test environments, you would choose the latter option which is also referenced as embedded mode. Because of this separation of vCenter and PSC, the installation process of vCenter appliance 6.0 is quite different from the previous versions.
Although we are all familiar with the username and password based login to the VMware vSphere, it’s also possible to login into vSphere with just certificates. If you are a third party vendor, either IHV (independent hardware vendor) or ISV (independent software vendor), the certificate based login is actually a better and preferred alternative to the one using username and password.
Let me explain why it’s the case, and how it can be done painlessly.
The esxcli is a command tool that is available on VMware ESXi for managing ESXi. Unlike the vim-cmd command, it focuses on underlying infrastructure and touches lower level of controls of the ESXi hypervisor itself. Although it’s just one command, it packs a lot of functionalities with different namespaces/sub-namespaces, and sub-commands. Because they are organized in nice tree hierarchy, it’s actually quite easy to use most times.
Even before VMware announced the GA of vSphere 6.0, I’ve started to work on the vijavaNG making sure that vijavaNG will keep up with the latest release of vSphere. Although it may take a bit time for customers and partners to move onto this new release, we want early adopters to have the choice to use the best Java APIs for managing vSphere.
APD stands for all path down. It’s a storage issue that is discussed in VMware KB article Intermittent NFS APDs on VMware ESXi 5.5 U1 (2076392). You can install a patch to address the issue with ESXi 5.5.
If you want to find out the information in the vCenter database, the VMware support bundle comes handy. For example, if you want to analyze the event history, task history, you can dig out these information from the support bundle. By default, the vCenter support bundle is collected as part of the VMware support bundle on standalone client, but not on the vSphere Web Client. So make sure to mark the check box if you want the vCenter info.