- capacity planning
- Cloud computing
- cloud native apps
- fault domain
- Graph Database
- graph databases
- Platform as a service
- powerpath virtual
- relational database management systems
- VMware View
DisclaimerThe opinions expressed here are my personal opinions. Content published here is not read or approved in advance by any company and reflects only views and opinions. This is my blog, nobody else's. I am an employee of VMware, but this is not a VMware blog.
Buckle in, this may be a long post….
I have been working recently with a customer that happens to have a large vSAN environment – indeed, one of the largest vSphere clusters I have encountered at 48 hosts – and as a result I have been doing a good bit of thinking about how to give guidance for this customer, what sort of recommendations VMware should be providing, and generally how to approach fault domains in a vSAN environment.
In this post, I hope to address some of the design considerations for building out a vSAN cluster with fault domains beyond what is addressed in VMware’s vSAN Design and Sizing Guide. Nonetheless, if you are not already familiar with how to size a vSphere cluster to include vSAN storage, that is a great place to start, and required reading, as far as I am concerned. Continue reading
Recently a customer posed a question about what they were seeing in vSAN when they moved a virtual machine over to a vSAN datastore. Essentially, they were seeing vCenter report the VMDK as consuming more space than they had expected. I began to compose a response, but then realized I might be missing some things in my explanation myself, so I took the opportunity to leverage our Hands-On-Labs to do a little experimenting.
By the way, if you don’t already use the HOL, it’s a great resource for learning, experimenting, and understanding behavior…. there are a ton of products you can play with and it is all available through your web browser.https://hol.vmware.com
So I wanted to answer the following questions for my customer:
- How does the reporting of free / used space differ between vCenter and the guest operating system of a virtual machine?
- What is the difference – if any – between the utilization of capacity between a normal datastore and a vSAN datastore?
- What should we expect to see when the protection scheme used by vSAN changes?
I have had the privilege to begin to work with the Cloud Native Apps team at VMware a bit over the past couple months, and I am becoming more and more convinced that this is a topic and a trend that will be come more and more impactful as time passes.
There is much to be said (written) about the rise of Continuous Integration and Continuous Deployment (CI/CD), how DevOps is changing the way our customers go about the business of IT, and how applications are being written in new ways with new tools (think ‘microservices’). However, without getting bogged down by the noise created by everything that’s going on in the market, there are some fundamental truths we have to come to grips with… Continue reading
Found this great resource for anyone looking to get Mesos running in their lab / environment! Thanks Marco @massenz
I have just published a gist that shows how to build and install Apache Mesos on a Ubuntu 14.04 VM or physical box.
The Getting started instructions are a good start (well…) but are somewhat incomplete and currently look a bit outdated (I plan to fix them soon): however, the outcome has been that I have struggled more than I felt necessary in building and running Mesos on a dev VM (Ubuntu 14.04 running under VirtualBox).
Some of the issue seem to arise from the unfortunate combination of Mesos Master trying to guess its own IP address, the VM being (obviously) non-DNS resolvable and, eventually, the Slave and the Framework failing to properly communicate with the Master.
In the process of solving this, I ended up automating all the dependencies installation, building and running the framework; I have then broken it down into the following modules to make it easier…
View original post 7 more words
VMware recently released Photon OS – Tech Preview 2. You can find it here, along with some of their other open-source initiatives. This post is intends to (hopefully) introduce folks to Photon and demonstrate how easy it is to use as part of a larger solution.
Photon OS is an RPM-based Linux distribution built expressly to support containers and container-cluster frameworks, like Kubernetes and Mesos, and optimized to run on vSphere. Support for Docker, Rocket, and Pivotal Garden are built right into Photon OS, though only the binaries for Docker are included by default. What’s more, with the release of Tech Preview 2, the binaries for Kubernets and Mesos are built-in as well, making working with your favorite cluster resource scheduler easier than ever. You can read more about Photon OS here.
One thing to note, however, is that when you first install Photon OS, you have a choice of installation types – Micro, Minimal, Full, and something else named OS Tree, which I won’t go into now. The difference(s) between Micro, Minimal and Full are – as one would expect – in the packages and binaries that are included with each installation. For example, if I install a “minimal installation of Photon, take a look at the output of a couple of “list” commands in the console: Continue reading
I am thrilled to have been able to present at VMworld this year! Nothing like a last-minute request to goad you into action… I received a call about 10 days before the event to cover for another speaker that couldn’t make it, so there was much scurrying and preparation!
I co-presented with Andrew Nelson for session CNA4725 – Scalable Cloud Native Apps with Docker and Mesos.
You can check out the recording here: http://vmware.mediasite.com/mediasite/Play/bc636c07aa1e4fc68cedb19ab50141e41d?catalog=1c95c1d4-0353-4ae1-b3ed-a5067afb57aa.
I would love to hear any feedback!