It is that time of year again. Wow, another year has gone by so quickly. If you are reading this post, then most likely you have heard about VMworld 2015, which is happening at the end of this month in San Francisco. I am happy to say that I have the privilege of attending the conference again this year. This annual virtualization reunion is a chance to see people you only get to see once a year, though you probably have been communicating with each other in the meantime. If you are attending this year, I hope our paths can cross sometime during the week.
Android devices recently suffered a spate of attacks. Similar attacks have been made against Apple devices and nearly every other brand of smart device. Does this mean that this is the end of Android or of mobile devices? Or does this mark the rise of mobile device management (MDM) and other software specifically designed to secure end user computing (EUC) devices? EUC security has two failure points: the handheld device and further in the network. But does an insecure device imply loss of data? Perhaps. Loss of credentials? Once more, perhaps. But do we really care? That is not known. So, let us look at a typical use case. Continue reading Should We Care If the Handheld Is Secure?
Whenever an innovation or buzzword gets popular, it is natural for marketing to pile on and apply the word to products. We are starting to see “hyperconverged” achieve this sort of recognition. Early hyperconverged vendors built their solutions from the beginning to be hyperconverged and deliver a set of values. These vendors continue to work at educating the market on the nature and value of hyperconvergence. Now, the customer appetite for hyperconverged solutions is proven and lucrative. Other vendors are calling their products “hyperconverged” because they have some of the characteristics, but giving something a name doesn’t change its nature. At the same time, giving something the wrong name doesn’t mean that thing isn’t valuable. So, what does make a solution hyperconverged? What is it about these solutions that makes them deserve a different name?
There are many reasons to use cloud resources, and there are many reasons to enter the cloud, of which we have spoken about fairly regularly as part of our IT Transformation series. The real question is: “When should you use cloud services?” Or, more to the point, “When should you use new cloud services in control of IT and not the business?” That is really the crux of the discussion; business users use cloud resources all the time. The choice to use them is based on getting your job done and not IT’s decisions. We often call this “shadow IT,” but is it? Let us look at a few examples and decide—is it shadow IT (as in, should be in IT’s hands to control?), or is it part of doing business and therefore a business decision? Does the definition change as we grow a business or change the scale of the business? Continue reading IT Transformation: SME
One of the main goals of DevOps is to streamline the software development lifecycle (SDLC) by removing waste from the system. Waste is often found in the form of bottlenecks, things within the system the slow down forward progress and introduce unnecessary wait time or tasks. This waste can be caused by inefficient processes, technology issues, and organizational or people issues. Successful companies are able to look at the entire value stream to identify the waste and then systematically work on reducing that waste from the SDLC to continuously improve, resulting in better speed to market, improved quality, and higher reliability. Companies the can continuously improve in this fashion become high performing companies which often results in improved customer satisfaction, better productivity, and improved financial results. This is the ultimate dream of the C-level types who are looking to transform their companies with DevOps. Continue reading DevOps and Bottlenecks
As technologists and analysts for the virtualization and cloud spaces, we are always talking about various places within the IT stack. Actually, as we talked about within the article Technical Arc of Virtualization, we have noticed that many people are moving up the IT stack, forming new and more interesting substrates of IT. These substrates are used to simplify the actions one takes to deploy new and more interesting applications, while at the same time abstracting away the physical and virtual layers of the stack—in essence, forming new substrates on top of which to build. Continue reading The Substrates of IT