Paeesler is a German company founded in 1997 by Dirk Paeesler, who wanted to create an easy to deploy and operate network monitoring solution, having no idea that what was at the time a “one man show” would have become in 20 years a company with 150,000 deployments worldwide and a staff of 170 people based in different countries. Paessler is a quite peculiar company as it is completely independent and owned by its founders and staff. It is also interesting to note that PRTG, Paessler’s solution, is adopted by 70% of Fortune 100 companies worldwide and acknowledged in Gartner’s magic quadrant.
When it was launched, vRealize Operations Manager was immediately perceived by its user base as a complete rework of its predecessor, vCenter Operations Manager. Changes were introduced not only in terms of features and capabilities, but also in the product’s architecture. Having hit version 6.2 and incorporating even some functionalities inherited by Hyperic, vROps is now definitely a mature product, which makes it an essential and indispensable component of any modern VMware virtualization infrastructure.
In this article I will try to cover most of the design considerations that need to be made when facing a vROps implementation scenario; I don’t mean to cover all the facets of the “vROps Design Dilemma”, neither will I go too much in depth analyzing all the possible design considerations. Nevertheless I hope to give you enough food for thought to succeed with your vROps implementation.
Today Ravello Systems and Nutanix have announced the availability of Nutanix CE on Ravello’s Smart Labs by means of a jointly developed blueprint.
For those not familiar with any of the two vendors, let me briefly recap for your convenience.
Ravello Systems has developed a product called HVX, which can be defined as a “nested hypervisor” capable of running on top of public clouds like Amazon AWS and/or Google Cloud Engine, together with a proprietary network overlay. This solution is designed to address specific use cases such as Labs, Demo/Sales environments, Dev/Test disposable infrastructures etc; this result is achieved leveraging commodity public clouds but at the same time allowing users to deploy workloads in the very same format they use on their own premises. Therefore the underlying AWS or Google Cloud Engine is completely hidden and not relevant when it comes to design and implement your infrastructure on Ravello’s platform. One interesting point is that VMware ESXi is already supported as a blueprint, so it is possible to deploy nested vSphere labs on top of Ravello’s HVX running inside AWS or Google Cloud Engine. It might sound confusing but it actually isn’t!
I have recently purchased a Synology DS713+ unit as I needed a reliable storage solution for my new “all physical” vSphere Home Lab. Synology has a great reputation for quality, features and performances and it is one of the manufacturers of choice among home labbers. I was particularly intrigued by the fact that the DS7123+ comes with full VAAI capabilities at a reasonable price (I was able to find it for less than 400 Euros without disks).
I will spare you all the fancy stuff about the unboxing, the initial configuration and the detailed (and indeed impressive) features list and I will go straight to the point: I will show you how I managed to correctly set up a fully VAAI backed iSCSI DataStore for my ESXi 5.5 U1 hosts, after some trial and error: unfortunately the Synology documentation is a bit lacking on this topic and it took me a few attempts before I succeeded to do it correctly.
For my current job I work a lot with NexentaOS (an OpenSolaris based distribution) VMs. Today I had to validate the procedure to upgrade VMware Tools on such VMs for a customer and came across some interesting issues.
During this edition of VMworld Europe I followed only a few sessions, included two focusing on the new vCloud Hybrid Service directly offered by VMware, one presented by Massimo Re Ferre’ and another one by Chris Colotti and David Hill on “How to build a Hybrid Cloud in less than a day”.
In this post I will present Massimo’s session: PHC5070 – vCloud Hybrid Service: Architecture and Consumption Principles. This session was the first of a five part series, completely focused on vCHS.
This post should hopefully be the first one in a series revolving around my new vSphere homelab. I have been running vSphere nested labs for quite a while, self-built or using the mighty Autolab, but recently I had both the need and the opportunity to put together a small “all-physical” lab. I will publish a post in the coming weeks with more details about its architecture and setup (hey! I’m still building it!) but I decided to pull the trigger and document a little inconvenience I managed to overcome quite easily. I hope you might find this info useful!
In the last few years virtualization technologies have changed dramatically and irreversibly the way modern Data Centers are designed, implemented and managed. In modern DCs, virtual to physical ratios are growing constantly, due to the commonly accepted evidence that every workload is now a candidate for successful virtualization: cases where 100% of the systems are virtual are not uncommon anymore.
This clearly requires a different approach to many – if not all – the tasks that fall into the Operations area. Backup and Replication are probably the two tasks that more than any other have changed as a consequence of the opportunities that virtualization has presented to infrastructure designers, engineers and administrators.