tag:blogger.com,1999:blog-2948803553779035122024-03-04T22:14:42.652-08:00The Keene View on ComputingOccasional jottings of an incurable entrepreneur.Unknownnoreply@blogger.comBlogger150125tag:blogger.com,1999:blog-294880355377903512.post-60723617453413008272021-06-29T18:49:00.003-07:002021-06-29T18:49:22.705-07:00Why Crypto Matters – Digital Scarcity<p><br /></p><p class="p1" style="font-family: "Helvetica Neue"; font-size: 12px; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"></p><div class="separator" style="clear: both; text-align: left;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmiCpbmd5AT0Up7Zdd3tSyplOwuyNWwkPSXYFv7JZvff-uidGMbxPuAAcWhDAsPoHy0xRxqING6xiu9B2WvY6Xnu19upWTgsjRvFj6aIUitRE6jU70r5RACBienvUMd5GWTm4gbjKkx1k/s1200/scarce_water_drought.jpeg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img alt="crypto is digital scarcity" border="0" data-original-height="900" data-original-width="1200" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmiCpbmd5AT0Up7Zdd3tSyplOwuyNWwkPSXYFv7JZvff-uidGMbxPuAAcWhDAsPoHy0xRxqING6xiu9B2WvY6Xnu19upWTgsjRvFj6aIUitRE6jU70r5RACBienvUMd5GWTm4gbjKkx1k/w320-h240/scarce_water_drought.jpeg" width="320" /></a><span style="font-family: arial;">The internet introduced digital abundance - making it dramatically easier to create and transfer any kind of information. This in turn transformed the previously monopolistic world of books, movies, and music. <br /></span><span style="font-family: arial;"><br />I</span><span style="font-family: arial;">n contrast, cryptocurrency introduces digital scarcity - making it dramatically easier to create and transfer anything of value. </span><span style="font-family: arial;">Just as the internet upended the media world, the cryptocurrency economy will transform the (also highly monopolistic) financial world.</span></div><div class="separator" style="clear: both;"><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><b><span style="font-family: arial;">What Is a Cryptocurrency?</span></b></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">A traditional currency is backed by a government. The dollar is worth what it is because the government has built a set of policies and actions to support a particular value. When people lose trust in their government, the value of that currency falls.</span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">Similarly, the value of a cryptocurrency is based on the trust investors have in a computer program running on a network of independent computers. The most famous cryptocurrency is Bitcoin.<span class="Apple-converted-space"> </span></span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">In practical terms, bitcoin is a computer program that pays computer owners (called miners) to run copies of itself on their computers. Investors then pay miners protect a highly secure ledger that records which investor owns each bitcoin. Bitcoin is a very clever computer program that incents miners and investors to collaborate in order to profit from each other.</span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">Although there are thousands of cryptocurrencies, 75% of the $2 Trillion cryptocurrency market is split between just two currencies: Bitcoin (valued at $1.1T) and Ethereum (valued at $0.4T). These two cryptocurrencies are very different:</span></p><ul class="ul1"><li class="li1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;"><span class="s1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;"></span>Bitcoin is a speculative asset like gold, based on a secure ledger.</span></li><li class="li1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;"><span class="s1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;"></span>Ethereum is similar to Bitcoin but adds a programming language to a secure ledger, making it much more flexible. This flexibility makes Ethereum the choice of developers who are building the next generation of Decentralized Finance (DeFi) applications. These applications will upend the world of finance.</span></li></ul><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><b><span style="font-family: arial;">What Is Decentralized Finance (DeFi)?</span></b></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">Any financial application can be broken down into an agreement between two parties to transfer value according to certain rules. A Decentralized Finance application creates agreements – called smart contracts – makes them part of an Ethereum transaction to record an unbreakable agreement between two parties.<span class="Apple-converted-space"> </span></span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><b><span style="font-family: arial;">Why Is DeFi Better?</span></b></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">The traditional finance world is composed of heavily regulated, monopolistic companies. They face limited competition and even more limited opportunity for innovation.</span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">In contrast, the DeFi world is composed of companies who are “born integrated” with every other value creation and transfer application in the cryptocurrency ecosystem. Entirely new financial solutions are being created on a daily basis that incorporate elements of the financial world that have never been combined before.</span></p><p class="p3" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px; min-height: 14px;"><span style="font-family: arial;"><br /></span></p><p class="p1" style="font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal; margin: 0px;"><span style="font-family: arial;">For example, it is easy to make an investment and at the same time insure against exchange rate risk and security risk for that investment. The only market disruption that matches the level of innovation and change going on in DeFi is the Internet boom of the early 2000s.</span></p></div><p><br /></p>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-7815460446956703322016-07-05T16:05:00.000-07:002016-07-05T16:05:54.966-07:00Orchestration Sets The Beat For Agile IT<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_a9WHM3ps_3qu-X7G-c13Lb9PiFT_A3YOonfBdnJcmQlpP-gV7WbnDudVoIncf-tbpkPYhyK_d4CkrDL1JIS6Y8RXmyXgWv08gEgZOncWj6W8X8Z7uuQECHAvSj3xRzOnRtbOZ7UxjS0/s1600/vv54ede21d.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_a9WHM3ps_3qu-X7G-c13Lb9PiFT_A3YOonfBdnJcmQlpP-gV7WbnDudVoIncf-tbpkPYhyK_d4CkrDL1JIS6Y8RXmyXgWv08gEgZOncWj6W8X8Z7uuQECHAvSj3xRzOnRtbOZ7UxjS0/s400/vv54ede21d.jpg" width="400" /></a></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<a href="http://www.gartner.com/newsroom/id/3220220" target="_blank">Agile IT</a> has been widely heralded (and equally widely <a href="http://www.forbes.com/sites/jasonbloomberg/2015/09/26/bimodal-it-gartners-recipe-for-disaster/#689e88e74937" target="_blank">decried</a>) as a way to align the pace of change in IT with the pace of change in the broader business.</div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
At its core, Agile IT is making the very basic point that if in house IT cannot keep pace with the business there are a rapidly increasing number of cloud and SaaS providers for whom that is not a problem.</div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
In short, IT must innovate around time to market or die a death of a thousand credit card cuts as individual developers outsource the IT they need to Amazon and other public cloud providers.</div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
But what is the core activity that drives the shift to agility? Most often this shift is characterized as a vat migration to cloud. This is true, but it misses the key driver of IT agility: orchestration.</div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<b>How Orchestration Drives The Cloud</b></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
IT automation deals with performing a particular task, such as setting up a single compute node. IT orchestration manages execution of multiple, interdependent tasks. For example, an orchestration workflow manage dependencies such as the need install a database before installing an app.</div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
A cloud without effective orchestration is more like a demo - if it works at all, it is likely to break the first time the need arises to update the apps, data or infrastructure supporting that cloud. Key areas of focus for cloud orchestration include:</div>
<ul style="font-family: 'Helvetica Neue'; font-size: 14px;">
<li><b>Reference architecture</b> - any orchestration solution must start with a clear understanding of how the pieces fit together, particularly to guarantee reliability at a specific scale and set of workloads. </li>
<li><b>OS patching </b>- far from being a settled capability, OS patching remain more of a dark art than a science. While patching itself is straightforward, for every 100 servers patched, several will not reboot properly, causing cascading faults across the cloud. Next-gen computing companies like <a href="http://www.coreos.com/" target="_blank">CoreOS</a> are offering some innovative approaches to solving the OS patching problem.</li>
<li><b>Infrastructure lifecycle management</b> - OpenStack upgrades are notoriously challenging and one of the reasons companies like <a href="https://www.mirantis.com/blog/yes-can-upgrade-openstack-heres/" target="_blank">Mirantis</a> have achieved such success in helping customers build and manage large OpenStack installations.</li>
<li><b>Application lifecycle management </b>- a cloud is only as valuable as the applications running on it. Orchestration and DevOps is needed at the application, infrastructure and OS level.</li>
</ul>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<b>How to Get To Agile IT</b></div>
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
Here are a few hints to simplify the task of building an orchestration-first cloud:</div>
<ol style="font-family: 'Helvetica Neue'; font-size: 14px;">
<li><b>Usage drives design</b> - Understand intended usage (workloads and scale) before you design the architecture. There is no such thing as a “one size fits all” cloud - the cloud architecture is dictated by its intended use.</li>
<li><b>Don’t skimp on designing and testing the reference architecture</b> - understand what happens to network, storage and compute at scale running realistic workloads. Work through failure scenarios (think chaos monkey) and ensure that HA and DR work under real-world conditions</li>
<li><b>Don’t just automate, orchestrate </b>- while small, pilot clouds can be managed with manual processes and single-node automation, large, production-quality clouds require a significant investment in multi-node orchestration and change management.</li>
<li><b>Address organizational and business process disruptions up front</b>. Understand the impact of cloud on individual IT roles/responsibilities, career paths and opportunities for advancement</li>
</ol>
<span style="font-family: 'Helvetica Neue'; font-size: 14px;"></span><br />
<div>
</div>
<br />
<div style="font-family: 'Helvetica Neue'; font-size: 14px;">
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-68109933003564029452016-06-20T18:30:00.003-07:002016-06-20T18:30:51.710-07:00How Not To Build A Cloud<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHUunJrR5Qk-df9AgBWA0E50vjNpnvqkU-GbuciCrrO1FmIuQArZGEJ8lTA4zezLy2IBIo3udhsAXX1Q8mYrGppGV9RMyil9qV4t0F9rMYbK8lJPBGOjBp_20q1x-wveyyfC7ZqdtFao4/s1600/bad+construction.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img alt="" border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHUunJrR5Qk-df9AgBWA0E50vjNpnvqkU-GbuciCrrO1FmIuQArZGEJ8lTA4zezLy2IBIo3udhsAXX1Q8mYrGppGV9RMyil9qV4t0F9rMYbK8lJPBGOjBp_20q1x-wveyyfC7ZqdtFao4/s400/bad+construction.jpg" title="" width="400" /></a></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">Thomas Bitman of Gartner wrote a <a href="http://blogs.gartner.com/thomas_bittman/2015/02/05/why-are-95-of-private-clouds-failing/">blog
post</a> last year about why OpenStack projects fail. In that article, he
outlined three particular metrics which together cause 60% of OpenStack
projects to fall short of expectations:</span></div>
<div class="MsoNormal">
</div>
<ul>
<li><b style="font-family: Verdana, sans-serif; text-indent: -0.25in;">Wrong people (31% of failures):</b><span style="font-family: Verdana, sans-serif; text-indent: -0.25in;"> a
successful cloud needs commitment both from the operations team as well as from
“anchor” tenants.</span></li>
<li><b style="font-family: Verdana, sans-serif; text-indent: -0.25in;">Wrong processes (19% of failures):</b><span style="font-family: Verdana, sans-serif; text-indent: -0.25in;"> a
successful cloud automates across silos in the software development lifecycle,
not just within silos.</span></li>
<li><b style="font-family: Verdana, sans-serif; text-indent: -0.25in;">Wrong metrics (10% of failures):</b><span style="font-family: Verdana, sans-serif; text-indent: -0.25in;"> a
successful cloud focuses on top line transformation by accelerating delivery of
innovative applications and services, not merely on squeezing bottom line
costs. </span></li>
</ul>
<br />
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><b>Wrong people</b><o:p></o:p></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>"Agile clouds need agile processes — and people are
your biggest supporters, </i></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>or your biggest roadblocks.” - Thomas Bitman </i><o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">Many OpenStack projects start as technology pilots with part
time technical staff. If there is not a single champion responsible for the
success of an OpenStack cloud initiative as their full-time job, the chance of
failure is high. There are two critical roles that govern cloud success: <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l1 level1 lfo2; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Cloud operations champion</b>: this champion
is not just responsible for building and operating the cloud (supplying cloud
capacity), they are equally responsible for on-boarding developers and
workloads onto the cloud (building cloud demand). Their job is to work closely
with developer tenants to make sure that the developer on boarding process is
smooth and that key developer tools are available in the cloud application
catalog.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l1 level1 lfo2; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Cloud anchor tenant</b>: developers are
overwhelmingly the most important early adopters of private cloud. Accelerating
the software development lifecycle through DevOps automation is by far the
highest value of private cloud. Therefore the most important validation for a
private cloud is to on-board a key set of developers and show the impact of
accelerating the development and go live process for their
applications. Having an anchor tenant committed to using the cloud is a
key prerequisite for achieving success.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><b>Wrong processes</b><o:p></o:p></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>"Is this really cloud? Or just virtualization? And what
about </i></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>the stuff running inside the VMs?” - Thomas Bitman </i><o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">Many OpenStack projects start with very limited goals around
provisioning generic VMs or delivering relatively limited development services.
This effectively automates just a silo within the software development
lifecycle. Business value comes from being able to automate not just within but
also across the silos of the software development lifecycle. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l2 level1 lfo3; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Beware of automating silos</b>: for many IT
organizations, the tragedy of virtualization has been that developers can
provision a VM within 20 minutes, but getting a fully configured development
environment takes over 6 weeks. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l2 level1 lfo3; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Aim to automate entire Go Live process</b>:
The ultimate goal of a private cloud should be to accelerate the delivery of
applications and features by automating the entire process from code check in
to go live. This level of automation is also the only way a traditional
enterprise can compete with “born in the cloud” SaaS businesses.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><b>Wrong metrics</b><o:p></o:p></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>“Not putting the right metrics in place - usually, this is
focusing </i></span></div>
<div class="MsoNormal" style="text-align: center;">
<span style="font-family: Verdana, sans-serif;"><i>on cost-savings, not agility." - Thomas Bitman </i><o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">Private cloud has often been sold as a natural extension of
virtualization - as such, customers often justified their OpenStack investments
based on IT cost savings. While cost savings are one value of a successful
cloud, enabling business agility is the core value delivered by OpenStack. <o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">OpenStack projects should measure business value not just
for the cloud overall but for each tenant. In particular, they should focus on
two tenant metrics: <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l3 level1 lfo4; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]--><b>Uptime dashboard</b>: public clouds have long
delivered detailed uptime metrics. Private clouds must do the same if they are
to build trust with tenants and create a business case to justify additional
cloud investments.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l3 level1 lfo4; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]--><b>Value dashboard</b>: private cloud value is
primarily driven by its ability to accelerate the software development
lifecycle. McKinsey has documented that <a href="http://www.mckinsey.com/insights/business_technology/beyond_agile_reorganizing_it_for_faster_software_delivery">DevOps
automation</a> can accelerate the go live process by 80%, which in turn can
deliver top line revenue growth, for example by enabling greater innovation in
customer facing apps. Tracking continuous integration deployments is a proxy
for the overall acceleration enabled by private cloud.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><b>Planning for OpenStack Success</b><o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">The antidote for OpenStack project failure is to build a
business case for private cloud that addresses people, process and metric
issues. This business case should lay out a phased approach for rolling out
their private cloud. <o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">The starting point is identifying a full time cloud champion
and teaming them with an anchor tenant who will use the cloud and provide input
on how to deliver value by accelerating delivery of new applications and
features. The next step is to define a phased set of investments, each with
clear success metrics that govern timing for subsequent investment: <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l4 level1 lfo5; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Phase 1</b>: stand up cloud and on-board
anchor tenant. Success metric: 99% uptime, 1.5X software development
acceleration. Once these metrics are achieved, the company should invest in
phase 2 of their rollout.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l4 level1 lfo5; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Phase 2</b>: on-board additional tenants.
Success metric: 99.9% uptime, 2.0X software development acceleration.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in; mso-list: l4 level1 lfo5; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Verdana, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;"> </span></span></span><b>Phase 3</b>: automate go live process from
code checkin to production. Success metric: 99.99% uptime, 4.0X software
development acceleration.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
<o:PixelsPerInch>96</o:PixelsPerInch>
</o:OfficeDocumentSettings>
</xml><![endif]-->
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>JA</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="380">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Level 9"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
</w:LatentStyles>
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Calibri;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
<!--StartFragment-->
<!--EndFragment--><br />
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">An ideal approach for a company looking to make a strategic
investment in private cloud is to conduct a short pilot in an OpenStack lab
that allows them to validate the business case. This kind of a pilot can also
allow the cloud champion and “anchor” tenant to work together on clarifying
requirements for successfully on-boarding an initial application to the private
cloud. </span><o:p></o:p></div>
Anonymoushttp://www.blogger.com/profile/18127333968108116583noreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-29564604981336869952015-09-23T16:19:00.002-07:002015-09-23T16:19:25.735-07:00For Private Cloud, No Pain Means Big Gains<div class="MsoNormal">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdhCiikqdNZMTZq_BXnmwptGYE65CWGY3tnLX6hIjcgRjlkwxF8R-Gh29sw5Vuta-xL_hEIYfhOnfvMOgLN1tF43Y7rSIKCT0kvN6mUvtP0swgZCvXIueLYN6N2s2eJ1H6gsEU9I6vaDc/s1600/NO-PAIN-NO-GAIN.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="160" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdhCiikqdNZMTZq_BXnmwptGYE65CWGY3tnLX6hIjcgRjlkwxF8R-Gh29sw5Vuta-xL_hEIYfhOnfvMOgLN1tF43Y7rSIKCT0kvN6mUvtP0swgZCvXIueLYN6N2s2eJ1H6gsEU9I6vaDc/s320/NO-PAIN-NO-GAIN.jpg" width="320" /></a></div>
When virtualization took the data center, it offered huge
cost savings for IT ops and zero migration pain for developers. Coming
at a time when IT was being pressed by the business for savings, vSphere took
the data center by storm.<br />
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
This example is instructive when trying to consider why
private cloud has had a slower adoption. The short answer is that
cloud offers fuzzier benefits for IT ops while forcing a lot of pain on developers.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
The lack of a smooth migration path for existing workloads
to the cloud goes a long way to explain the relatively bumpy growth of the
private cloud market itself. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
For example, the latest craze for “<a href="https://cncf.io/" target="_blank">cloud native</a>” apps seems like an explicit acknowledgement that vendors are giving up on minimizing
cloud migration pain. Rather than focusing on simplicity,
the cloud native initiative seems to make a virtue needing to
rebuild existing apps for the cloud.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Of course, for greenfield apps, cloud native and <a href="http://12factor.net/" target="_blank">12 factorapps</a> make great
sense. But for the enterprise, greenfield is a small part of what
they do (<a href="http://www.zdnet.com/article/heres-what-your-tech-budget-is-being-spent-on/" target="_blank">like less than 10%</a>). There is still a big white space in the market
for a vendor who can provide cloud benefits for existing workloads.</div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
This may be the reason for the buzz behind next generation cloud companies like
<a href="http://www.apcera.com/" target="_blank">Apcer</a>, <a href="https://mesosphere.com/" target="_blank">Mesosphere</a> and Google's <a href="http://kubernetes.io/" target="_blank">Kubernetes</a> who offer ways to support existing Windows and vSphere
workloads. The idea of getting improved automation and security while having a
migration to new technologies like Docker gives enterprise the best of both
worlds.</div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Of course it is early days for these new cloud technologies, but my
bet is on whichever vendor can duplicate the original VMware offer of max cloud ops gain for minimum dev pain.</div>
<div class="MsoNormal">
<o:p></o:p></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-58690951730433244142015-09-16T09:08:00.001-07:002015-09-16T09:08:19.671-07:00Entrepreneur’s Note to Self - Don’t Die
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS 明朝";
panose-1:0 0 0 0 0 0 0 0 0 0;
mso-font-charset:128;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:fixed;
mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
{font-family:"MS 明朝";
panose-1:0 0 0 0 0 0 0 0 0 0;
mso-font-charset:128;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:fixed;
mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"MS 明朝";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"MS 明朝";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<br />
<blockquote class="tr_bq">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcVUoBZ15q63m_HGn7XL1T5zrihYpzKjMlF48iGQdEJYM2XlS9xUrmPuBjZC6Qt-xJ2jODnyaUF-BXW4mK8prBhmOBjdoTPJQLokWyCEmt6HXTYPBlq2feY_GcbGd-q_mzMB8c-K3U84A/s1600/chris-hadfield.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="212" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcVUoBZ15q63m_HGn7XL1T5zrihYpzKjMlF48iGQdEJYM2XlS9xUrmPuBjZC6Qt-xJ2jODnyaUF-BXW4mK8prBhmOBjdoTPJQLokWyCEmt6HXTYPBlq2feY_GcbGd-q_mzMB8c-K3U84A/s320/chris-hadfield.jpg" width="320" /></a></div>
<blockquote class="tr_bq">
<div class="MsoNormal">
<i>“Note to self: don't change for anyone / Note to self: don't
die / Note to self: don't change for anyone / Don't change, just lie” - Ryan
Adams
</i></div>
</blockquote>
</blockquote>
<div class="MsoNormal">
If Woody Allen is right that 80% of life is just showing up,
then the bulk of an entrepreneur’s job is keeping the company alive long enough
to succeed. That in turn means constantly scanning the horizon for what is most
likely to kill you next.
</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
It turns out, this is how NASA trains their astronauts to
stay alive in the unforgiving environment of space. The <a href="https://www.youtube.com/watch?v=KaOC9danxNo" target="_blank">singing astronaut</a> Chris
Hadfield gave an <a href="http://www.npr.org/2013/10/30/241830872/astronaut-chris-hadfield-brings-lessons-from-space-down-to-earth" target="_blank">interview</a> where he described this approach:</div>
<blockquote class="tr_bq">
<div class="MsoNormal">
“Half of the risk of a six-month flight is in the first nine
minutes, so as a crew, how do you stay focused? How do you not get paralyzed by
the fear of it? The way we do it is to break down: What are the risks? And a
nice way to keep reminding yourself is: What's the next thing that's going to
kill me?”</div>
</blockquote>
In the startup world, death comes most quickly through
failing to grow rapidly. That means the two most critical tasks are keeping
current customers happy and getting new ones. Growth is the bait that attracts
capital and capital is oxygen for a startup.
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Once a startup company is funded, there is an immediate
desire to draw a huge sigh of relief and think about how to fix everything that
is wrong with the product, starting with a ground up redesign. However,
startups are fragile creatures. Customers pay for solutions - for them, elegance
is secondary. </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
A company can easily die while it is “fixing” its product. A
better approach is to prioritize resources guarantee growth and approach
product redesign in a modular fashion that still enables a steady stream of
customer-facing enhancements.</div>
<div class="MsoNormal">
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-41214414053836962962015-08-26T11:53:00.001-07:002015-08-26T12:14:34.468-07:00People Only Buy To Get Promoted - The Key To Enterprise Sales<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqz-pEbgSgnlRaAJq7g4cAhW5p4KGnjUXsk8HfuQEaScO_sakapstSYFV6secE0-7hMvtYV46_BJ-awcaY80RfSQFrPKs5eRKgfc4_p2s4zOhbW_K5izwGyH2xTOC2hgGMfAJQLWV81vg/s1600/Getting-Promoted.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqz-pEbgSgnlRaAJq7g4cAhW5p4KGnjUXsk8HfuQEaScO_sakapstSYFV6secE0-7hMvtYV46_BJ-awcaY80RfSQFrPKs5eRKgfc4_p2s4zOhbW_K5izwGyH2xTOC2hgGMfAJQLWV81vg/s1600/Getting-Promoted.png" /></a>I have been fortunate to have many good sales mentors in my career but the best hands down was <a href="http://consultingadultblog.blogspot.com/2010/03/life-in-boys-dorm-my-career-at-sun_16.html" target="_blank">Joe Roebuck</a>. Joe headed sales at Sun Microsystems for 17 years and was on my board at Persistence Software for 5 years.<br />
<br />
Joe also gave me the most important insight about how to sell enterprise software:<br />
<br />
<i>People only buy to get promoted.</i><br />
<br />
The enterprise software version of this pithy statement would be something like: enterprise buyers will only buy your shiny object if they see it leading directly to recognition, acclaim and promotion or at least a raise.<br />
<br />
There is a lifetime of sales knowledge encapsulated in that quote. Here is how I interpret it:<br />
<br />
<ul>
<li><b>Status quo is easy</b>: enterprise software is a business in which innovative upstarts try to unseat incumbents. The easy purchase decision in enterprise software is always to go with the incumbent. </li>
<li><b>Shiny objects are risky</b>: Enterprise buyers always have a choice between safe status quo vendors and an array of risky but alluring new vendors</li>
<li><b>Career advancement is why buyers take risks</b>: if a buyer does not get a personal benefit - attention, a raise, a promotion - the risk quite literally does not outweigh the reward</li>
<li><b>Advancing customer careers is how companies win</b>: most sales people think only through the customer signature and maybe the initial implementation. Making a customer successful is a longer-term venture and extends at least to the buyer’s next HR review cycle.</li>
</ul>
<br />
There is no more passionate evangelist than a successful buyer and it only takes a few really happy buyers for the market herd instinct to kick in. For example, VMworld pulls in 10,000 attendees a year, all of whom believe that VMware products are advancing their career.<br />
<br />
Buyers know that product features don't guarantee success. Just because a product is objectively better doesn’t mean it will be successfully implemented, integrated and maintained by the vendor. A key success in sales it to structure a deal in such a way that the company has incentive to stay focused on the success of the deal over time.<br />
<br />
It is interesting that people always say of incumbents like IBM, “nobody gets fired for buying IBM.” The flip side of that is the only reason a buyer would make a riskier choice would be for the opportunity to be promoted, aka the opposite of being fired.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-62576426470447945082015-08-19T12:15:00.002-07:002015-08-19T12:15:35.073-07:00When Will Cloud Come to PaaS?<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPAAO6XRads_Ayn2fYDRdoHKoHZiRnDwFu78eXsix76mJxdT5AvAIvOAvoW14jnFawnGjvCQeOiTUr2yuEjq7oV71c65OZcA5dkDvchsj1wCs3cyGn70XLaO6DmsXIUveHaW13Jhfbvz4/s1600/san-francisco-fog-2+%25281%2529.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="212" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPAAO6XRads_Ayn2fYDRdoHKoHZiRnDwFu78eXsix76mJxdT5AvAIvOAvoW14jnFawnGjvCQeOiTUr2yuEjq7oV71c65OZcA5dkDvchsj1wCs3cyGn70XLaO6DmsXIUveHaW13Jhfbvz4/s320/san-francisco-fog-2+%25281%2529.jpg" width="320" /></a></div>
One of the perennial cloud predictions has been that 200x would be the year of the Platform as a Service (PaaS) cloud. The logic goes that if an automated data center in the sky is good, an automated development platform in the sky must be even better.<br />
<div>
<br /></div>
<div>
“Normal” clouds like Amazon AWS give the developer a virtual computer to load their OS and App onto. PaaS gives the developer a virtual computer with the OS, database and middleware “pre-loaded,” thereby simplifying the deployment.</div>
<div>
<br /></div>
<div>
Yet so far, PaaS adoption has been anemic and Gartner puts PaaS at 1% of the overall <a href="http://www.forbes.com/sites/louiscolumbus/2015/01/24/roundup-of-cloud-computing-forecasts-and-market-estimates-2015/" target="_blank">cloud market</a>. At the same time, new technologies like Docker and containers have attracted far more attention from the developer community.</div>
<h3>
PaaS Lacks “Write Once, Run Anywhere” Simplicity</h3>
<div>
Developers love the simplicity of “write once, run anywhere.” This is what gave Java its initial allure and it is at the core of Docker’s recent ascendance to the top of the shiny tech object heap. PaaS has traditionally been more of a “write differently for each place” kind of solution. Issues include:</div>
<div>
<ol>
<li><b>PaaS lock-in</b> – there is no example in the industry of PaaS portability – each PaaS has its own unique services and configuration. While IaaS also suffers from similar lock in issues, the effort required to port from one cloud to another is much lower here. </li>
<li><b>Anemic ecosystem</b> - real applications use many different services, such as database, file storage, security and messaging. In order to deploy an application in a PaaS, the PaaS must support every service that app needs,.</li>
<li><b>Public/private inflexibility</b> – many PaaS offerings are cloud only (Heroku) or on premise (OpenShift). Even for PaaS offerings that can run on or off premise, replicating the exact service ecosystem in each environment is challenging.</li>
</ol>
</div>
<h3>
PaaS For SaaS Is a Winner</h3>
<div>
A no-brainer use of PaaS is to extend existing SaaS applications. In this case, the write once run anywhere problem goes away because there is only one place to build and run the application. </div>
<div>
<br /></div>
<div>
The big winner in PaaS to date has been SalesForce. Their <a href="http://venturebeat.com/2013/11/06/should-you-build-on-force-com/" target="_blank">Force.com platform</a> makes it easy for companies to extend their CRM applications or build entirely new applications. With this platform, SalesForce has created huge competitive differentiation in CRM space while also building a PaaS revenue stream approaching $1B a year, dwarfing any other PaaS offering. </div>
<h3>
Cloud Native PaaS Could Go Mainstream</h3>
<div>
Google recently released their cloud native platform, called <a href="http://www.businessinsider.com/google-brendan-burns-kubernetes-docker-dockercon-2015-2015-6" target="_blank">Kubernetes</a> (which means pilot in Greek). Kubernetes is a cloud operating system for containers that runs anywhere. A number of PaaS vendors are banding together to define the requirements for <a href="http://techcrunch.com/2015/07/21/as-kubernetes-hits-1-0-google-donates-technology-to-newly-formed-cloud-native-computing-foundation-with-ibm-intel-twitter-and-others/" target="_blank">cloud native computing</a>.</div>
<div>
<br /></div>
<div>
The promise is to simplify still further the process of provisioning services to cloud containers, regardless of where they are running. It will be exciting to see how existing PaaS vendors like <a href="http://redmonk.com/sogrady/2015/05/15/cloud-foundry-summit-2015/" target="_blank">CloudFoundry</a> incorporate these new technologies into their offerings.</div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-61805829452070478052015-08-10T10:47:00.000-07:002015-08-10T10:47:10.443-07:00Enterprises Need A Panic Button for Security Breaches<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjiQAqOCj6n3x6xuZwP7gPbCFeDvFz4bL9PHdxRTRiqQYPYVFQgwhHrQdnOu1jNwjBCR4-1jfJ1z86Sjxfhrd2nXuz72xQyUu7MI-xYrzLd1iDquIS0QWYDYDZFCoJWa-ESvlrzlc-MXLg/s1600/panic+button.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjiQAqOCj6n3x6xuZwP7gPbCFeDvFz4bL9PHdxRTRiqQYPYVFQgwhHrQdnOu1jNwjBCR4-1jfJ1z86Sjxfhrd2nXuz72xQyUu7MI-xYrzLd1iDquIS0QWYDYDZFCoJWa-ESvlrzlc-MXLg/s320/panic+button.jpg" width="320" /></a></div>
Most home security systems have a panic button - if you hear something go bump in the night you can push a panic button to starts the sirens wailing, call the cops and hopefully sends the bad guys scurrying. As useful as this is for home owners, enterprises need a security panic button even more.<br />
<br />
Security spending is heavily weighted towards keeping bad guys out. Media coverage has demonstrated how often they get in anyway. According to the <a href="http://dc.bluecoat.com/CyberEdge_Cyberthreat_Defense_Report" target="_blank">CyberEdge Group</a>, 71% of large enterprises reported at least 1 successful hacking attack in 2014.<br />
<br />
While there is extensive advice around the <a href="http://smallbusiness.chron.com/company-should-respond-security-breach-37191.html" target="_blank">manual steps</a> to take to respond to a malicious attack, there is little in the way of an automated response to an attack. This is important area to extend enterprise automation.<br />
<br />
What might a Panic Button for automated response to security incidents look like? Essentially this would be an automated workflow that would implement a set of tasks to eliminate the current attack, identify existing losses and minimize future damage. An example workflow could include:<br />
<br />
<ol>
<li>Identify compromised systems from intrusion detection tools and disconnect compromised systems from network</li>
<li>Search for unauthorized processes or applications currently running or set to run on startup and remediate</li>
<li>Run file integrity checks and restore files to last known good state</li>
<li>Examine authentication system for unauthorized entries/changes and role back suspect changes </li>
<li>Make backup copies of breached systems for forensic analysis</li>
<li>Identify information stolen from OS and database logs</li>
</ol>
<br />
By creating automated “Panic Button” workflows that respond to security incidents, enterprises can reduce the damage of an attack. This automated approach can also show customers that an enterprise is taking full precautions to protect their personal information from falling into the wrong hands.<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-64715483987204283402015-05-13T13:09:00.001-07:002015-08-10T10:42:23.245-07:00Entrepreneurial Management – The Loose-Tight Loop<div class="MsoNormal">
For the last 20 years, I have been leading teams both small (2 partners and a turtle) and large (over 850 employees). During that time I have had big successes (IPO on Nasdaq, sale to VMware) and crushing failures (remember the Y2K bubble?) Sitting on numerous boards also gave me a ring-side seat to observe different management styles.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Through this experience I have evolved a management style to drive rapid business transformation and growth. I call this style the “loose-tight loop (a mash-up of ideas from the Tom Peters book “<a href="http://en.wikipedia.org/wiki/In_Search_of_Excellence" target="_blank">In Search of Excellence</a>” and <a href="http://en.wikipedia.org/wiki/OODA_loop" target="_blank">OODA loops</a>). </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
In the very dynamic startup world, it is often hard to strike the right balance between “if I do it myself I know it will get done right” and letting chaos rule. Because the market is evolving at the same time as the company, assumptions about customers, competitors and technology change rapidly as well.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
I see the job of the CEO as aligning the team on a set of audacious goals and orchestrating the achievement of those goals through three activities:</div>
<div class="MsoNormal">
</div>
<ul>
<li><b>Tight on what to do</b> – align the team on goals and priorities</li>
<li><b>Loose on how to do it </b>– trust the team to reach those goals efficiently and creatively</li>
<li><b>Loop to learn</b> – communicate regularly to learn what is working and not working (aka trust but verify)</li>
</ul>
<br />
<div class="MsoNormal">
Over time, I have adopted a number of agile process ideas to put the loose-tight loop into practice:</div>
<div class="MsoNormal">
</div>
<ul>
<li><b>Daily standup</b> – 15 min call to communicate actions and identify issues </li>
<li><b>Weekly top 5s</b> – on Monday, each exec lists their 5 priorities for that week , summarizes status for the top 5 priorities for last week and updates MBOs</li>
<li><b>Weekly check in</b> – 1 hr one on one meeting to collaborate and coach</li>
<li><b>6 week sprint</b> – 2 hr meeting to go deep on 1-2 issues, review MBOs for last sprint and & set MBOs for next spring</li>
<li><b>Annual plan</b> – 2 day planning session to rebuild business plan for next year</li>
</ul>
<br />
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<a href="http://en.wikipedia.org/wiki/Management_by_objectives" target="_blank">Management By Objectives</a> (MBOs) are critical as they are the explicit link between team objectives and executive priorities. Linking MBOs too closely to compensation can reduce their value. MBOs should represent challenging tasks – 100% achievement is not expected and is likely a sign that the goals were too easy. These MBOs become calls to action for the team to support each other in accomplishing tough tasks. </div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
In the loose-tight loop, the CEOs job is to get everyone onto the same map and working together to reach the same destination. The executives’ job is to execute in alignment with the plan and ask for help if it turns out our assumptions are wrong.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
In fact, the biggest risk execution risk is that execs are too slow in asking for help when they run into trouble. More experienced execs have the confidence to ask for help when they need it. Less experienced execs try to bluff their way through the problem. This is dangerous to the whole team because often execution challenges mask underlying mistaken assumptions.</div>
<div>
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-13579724271824718842014-03-08T09:51:00.003-08:002014-03-08T09:51:46.654-08:00Location, location, location - Why I Joined BMC<div class="separator" style="clear: both; text-align: left;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbTs18lnrIcIP1zCBJjOR7AyunQR84FevrA98AMrBHZI3i7VLxAFMCsKIe_rSdPKOKfLkNJxhlBZfkwYA-FcB4_gRIYvY3KMULQLrPADRJ9xhJqbCCz85r2ZcMajYFMnLF6pnBCqfh564/s1600/location-location.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbTs18lnrIcIP1zCBJjOR7AyunQR84FevrA98AMrBHZI3i7VLxAFMCsKIe_rSdPKOKfLkNJxhlBZfkwYA-FcB4_gRIYvY3KMULQLrPADRJ9xhJqbCCz85r2ZcMajYFMnLF6pnBCqfh564/s1600/location-location.jpg" /></a></div>
The enterprise software market is not that different than the real estate market - where you are positioned in the market is everything.<br />
<br />
In the nerdier-than-thou Bay Area, moving from VMware to BMC is not the most obvious move, so here are some of my thoughts on my decision.<br />
<br />
At this point, I have started 2 companies (Persistence, Medaid), gone public once (PRSW - never again!), sold 3 companies (Persistence, WaveMaker, Reportive) and led one spinout (Pivotal).<br />
<br />
Figuring out what to do next was a challenge.<br />
<br />
I had always felt that in evaluating a job, team comes first and opportunity comes second (or in Jim Collins-speak, <a href="http://en.wikipedia.org/wiki/Good_to_Great" target="_blank">first who, then wha</a>t).<br />
<br />
When I was first introduced to BMC, I spoke to <a href="http://ca.linkedin.com/pub/eric-yau/0/26/a07" target="_blank">Eric Yau</a> and was impressed by his vision about transforming BMC — I felt it was very similar to the transformation project I had worked on at VMware. As I met with other BMC executives, I was struck by the overall quality of the executives and their commitment to make BMC the leader in the cloud and automation management.<br />
<br />
I believe that BMC has a unique position in the cloud space because they are not tied to a particular cloud platform. The other key players in the space - VMware, Amazon, Microsoft - all have a dog in the fight. They <b>*care* </b>which underlying platform their cloud automation manages.<br />
<br />
In short, the other production-class cloud managers are focused on building a purebred cloud backed by their OS or hypervisor - only BMC has a singular focus on hybrid cloud.<br />
<br />
If a key reason to move to cloud is greater customer choice, those same customers will be looking for the “Switzerland of cloud managers” to preserve their choice.<br />
<br />
Time will tell, but so far I am thrilled with both the market opportunity in front of BMC and the collaborative culture within BMC.<br />
<br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-31516347359790499982013-09-12T16:50:00.002-07:002013-09-12T16:50:26.873-07:00Engineering Management - Shaolin Style<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVdPA4s_6JIHkIHrX6FTJF6zxVv0MfS6AuR4ppp47WpmpqSLRIsO63iujeB9hkQXwBO70Fgqs5ZqaZDdEP0oBiHkClU_rABj8hPBeEAB2Np3tSg04AEWfJtIhvHS2Z5dc74OfY4iLrMC4/s1600/kung-fu_tv-master_po-young_grasshopper-300x199.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVdPA4s_6JIHkIHrX6FTJF6zxVv0MfS6AuR4ppp47WpmpqSLRIsO63iujeB9hkQXwBO70Fgqs5ZqaZDdEP0oBiHkClU_rABj8hPBeEAB2Np3tSg04AEWfJtIhvHS2Z5dc74OfY4iLrMC4/s1600/kung-fu_tv-master_po-young_grasshopper-300x199.jpg" /></a></div>
A friend of mine just got a well-deserved promotion from code horse to manager. Here are my quick thoughts on making that transition.<br />
<br />
The basic idea is that when you are given a little more responsibility, your words and actions carry more weight. For that reason, it is important to be careful about throwing that weight around.<br />
<br />
You job is no longer to optimize your output, but to optimize the output of your group. Don't be the <a href="http://jimmyunderwood.wordpress.com/2009/02/20/a-genius-with-a-thousand-helpers/" target="_blank">genius with a thousand helpers</a>!<br />
<br />
In particular, here is some advice to ease into a new engineering manager role:<br />
<br />
<ul>
<li><b>Listen more</b>. There is an expression about argumentative people - "they don't listen, they just reload." Since your words carry more weight, make sure you really understand other people's point of view before you offer your own. Once you wade in with guns blazing, other engineers will be less likely to confront you.</li>
<li><b>Code less.</b> The tradeoff for more human communication is less computer communication. The time you spend helping make other people effective comes directly out of your average daily KLOC. Remember, you are making the team's total output better at the expense of your own output - this will smart a bit at first!</li>
<li>Start team building.</li>
<li><b>Stop architecting</b>. If your vote counts for more than other engineers by dint of your hierarchical position, you can win architecture arguments just by yelling louder. To build a real engineering team, you have to separate the team leadership position from the tech leadership position. If you are the team leader, you just can't be the tech leader as well.</li>
</ul>
<br />
The net of it all is to use more influence, less telling; more carrot, less stick; you get the picture!<br />
<div>
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-21358081545348466082013-05-20T13:42:00.004-07:002013-05-20T13:42:59.215-07:00Health Care Transparency Requires Open Data<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]-->
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>JA</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
<w:UseFELayout/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="276">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
</w:LatentStyles>
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
<!--StartFragment-->
<br />
<div class="MsoNormal">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEixNAH6wUOYhAz-gUHFWazuqmueG4B51kLhftdrUIA3uQuJqB8sXfBLbJTyJ4wtJKsb1tf-FstGGqZeteV5VGFhULo94l8bsWDQv2B1iGCBz7kZ1c3wCvyRG0TmbtYH0K2jddLi-8HDCCY/s1600/window.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEixNAH6wUOYhAz-gUHFWazuqmueG4B51kLhftdrUIA3uQuJqB8sXfBLbJTyJ4wtJKsb1tf-FstGGqZeteV5VGFhULo94l8bsWDQv2B1iGCBz7kZ1c3wCvyRG0TmbtYH0K2jddLi-8HDCCY/s320/window.jpg" width="239" /></a></div>
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;">Transparent
pricing and quality data is the foundation of the US economy, yet is entirely
lacking in our Health Care industry. New players like Castlight have raised
over $130 million to provide greater transparency, but only to selected
customers who pay for that data.<o:p></o:p></span><br />
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;"><br /></span>
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;"></span><br />
<div class="MsoNormal" style="font-family: Times;">
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;"><span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;">I believe making health care pricing information freely available (like Wikipedia for health care data) will help reduce these inequities in our health care system. </span></span></div>
<div class="MsoNormal" style="font-family: Times;">
</div>
</div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;">Last week's release of <a href="http://www.cms.gov/research-statistics-data-and-systems/statistics-trends-and-reports/medicare-provider-charge-data/index.html" target="_blank">Medicare provider charge data</a> from hospitals across the US pointed the way forward - making pricing data publicly available to everyone. Because the government pays in a unique way, this data is only a starting point - what is needed is a public data set showing what employers and individuals pay for these same services.</span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><span style="font-family: Arial; mso-bidi-font-family: Arial;">Several
years ago, I had a personal experience that ignited a passion to drive change
in US healthcare. </span>While
our family was living in Paris, my son was diagnosed with a benign brain tumor.
We went through a series of medical procedures in France and then repeated them
on our return to San Francisco.</span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;">Because
our insurance only covered major medical procedures, we had to pay these bills
personally. We found that medical costs for in the US averaged a factor of
seven to ten times higher than what we had paid in Paris.</span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><span style="font-family: Arial; mso-bidi-font-family: Arial;">A good first step would</span> be to analyze claims data from 3-5 large US employers to create
a dataset showing the prices eployers paid for the most common procedures across providers (including the top 100 most frequently billed discharges information published by Medicare). This
analysis would help employers verify the health care prices they are paying.</span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Verdana, sans-serif; mso-bidi-font-family: Arial;">Making this information available on a publicly available web site could unlock a wave of innovation in the world of health care, much as open source communities have transformed the software world.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<br /></div>
<!--EndFragment-->Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-294880355377903512.post-82745215720207258072013-03-18T09:08:00.000-07:002013-03-18T09:08:13.093-07:00Hadoop Will Not Mow Your Lawn<!--?xml version="1.0" encoding="UTF-8" standalone="no"?-->
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi2FUdtExdBeyUy26IQseiwH67NjGNJ8EdC1M5KWbMbuCPAf4tk51EiBlO-VyqK1V7BGZwrBGH7TFnDBfN6X6WDjoOQsSTDE3au0xEaX2YR0HD5LPu4CZLJ-js0ul5beCaFShmg_d5NY3U/s1600/Screen+Shot+2013-03-18+at+8.54.51+AM.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="171" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi2FUdtExdBeyUy26IQseiwH67NjGNJ8EdC1M5KWbMbuCPAf4tk51EiBlO-VyqK1V7BGZwrBGH7TFnDBfN6X6WDjoOQsSTDE3au0xEaX2YR0HD5LPu4CZLJ-js0ul5beCaFShmg_d5NY3U/s320/Screen+Shot+2013-03-18+at+8.54.51+AM.png" width="320" /></a></div>
<div style="font-family: Arial;">
<i>"The best minds of my generation are thinking about how to make people click ads.</i>" <i>- <a href="http://jeffhammerbacher.com/" target="_blank">Jeff Hammerbacher</a> ex- Facebook Architect</i></div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
It turns out that when you have a lot of "best minds" working on the same problem, you come up with some pretty interesting technology - no matter how inane that problem may be.</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
The technology that those "best minds" at Yahoo came up with to target ads to users is called Hadoop. </div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Hadoop is a powerful technology and like most new IT solutions is being touted at being able to solve a vast number of technical ills. When companies discover that Hadoop will not in fact cure male pattern balding, they will fall into the inevitable <a href="http://blogs.gartner.com/svetlana-sicular/big-data-is-falling-into-the-trough-of-disillusionment/" target="_blank">trough of disillusionment</a>. </div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Here are some thoughts about what Hadoop can and cannot do:</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<div>
<b>1. RDBS are for business data, Hadoop is for web data</b></div>
<div>
<b><br /></b></div>
<div>
Almost all traditional business data fits well into the relational model, including data about customers (CRM), products (ERP) and employees (HR). This data should continue to live in relational databases, where it is much easier to manage and access than in Hadoop.</div>
<div>
<br /></div>
<div>
Almost all web data fits well into the Hadoop model, including log files, email and social media. This data would be almost impossible to store in a relational database, not just because of the volume, but because of the inherently nested quality of the data (threaded email conversations, web site directory structures, social media graphs).</div>
</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<b>2. Hadoop is really good at analyzing web data</b></div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Hadoop is incredibly good at looking at huge amounts of web data and figuring out why people clicked on the blue button instead of the red one. This can be generated to a few other computer log formats, but the list is relatively small, including:</div>
<div style="font-family: Arial;">
<ul>
<li><a href="http://www.tom-e-white.com/2008/01/hadoop-and-log-file-analysis.html" target="_blank">Log file analysis</a></li>
<li><a href="http://blogs.igalia.com/dpino/2012/08/07/metamail-email-analysis-with-hadoop/" target="_blank">Email analysis</a>: </li>
<li><a href="http://www.slideshare.net/jakehofman/largescale-social-media-analysis-with-hadoop" target="_blank">Social media analysis</a>: </li>
</ul>
</div>
<div style="font-family: Arial;">
How many other data types look like click streams? <a href="http://gigaom.com/2012/06/05/10-ways-companies-are-using-hadoop-to-do-more-than-serve-ads/" target="_blank">Not very many</a>. How many other real world problems lend themselves to analysis using web data analytic techniques? Also not as many as you might think.</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
This is not to take anything from the Hadoop market opportunity - as more of the world interacts with each other via web applications and devices, more of the world's data will be reducible to click-stream-like formats. </div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
The big data craze has taken over the tech media world much like the cloud craze. Most people know it is important but they don't know why. Many vendors get caught up in the hype cycle and start to believe that their technology has some sort of manifest destiny that will allow it to do much more than it can reasonably be expected to do.</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<b>3. Hadoop is a Pay Me Later Technology</b></div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Traditional data warehouses work on a "pay me now" basis. To get data into the data warehouse - even data that may not end up being useful in any way - you have to massage the data into a formal relational model. This is expensive and the data normalization process itself may make it impossible to get at the data in exactly the way you want to.</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
In contrast, Hadoop works on a "pay me later" basis. Data can be shoved into the Hadoop file system any old way. It is not until someone wants to analyze the data that you have to worry about how to connect all the pieces. The gotcha is that the price you pay in this "pay me later" model is much higher, requiring extensive programming in order to ask each question. </div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
In addition, because the normalization process wasn't done up front, it won't be until later that you may discover that you were missing crucial pieces of information all along. Thus it does bear some thinking up front on what sort of data to store in your Hadoop database and what kinds of questions you might want to be able to answer about that data in the future. </div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Realistically, it will take most businesses who implement several years to figure out whether all the data they are dumping into Hadoop produces real value out the back end, just as it was several years before companies started to get a payout from their investments in relational data warehouses.</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<b>4. Use the right tool for the right job</b></div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
Back in my - very brief - high school shop days, we learned that the trick to making a really nice looking ash tray is picking the right tool for the right job.</div>
<div style="font-family: Arial;">
<ul>
<li>Hadoop is web data query engine that requires a high level of effort for each new query. </li>
<li>Relational is a business data query engine that requires a high level of effort to format and load data into the datastore.</li>
</ul>
<div>
The fastest way for companies to get into trouble with Hadoop is to try to use it as a one-size-fits-all data warehouse. Much of the news in the Hadoop world today has to do with SQL parsers that run on top of Hadoop data. This is a powerful and valuable technology, but does not mean that you can throw out your data warehouse and replace it with Hadoop just yet.</div>
</div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<br /></div>
<div style="font-family: Arial;">
<br /></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-27275973830505030852013-02-05T13:34:00.000-08:002013-02-05T13:34:01.780-08:00What I'm Talking About When I'm Talking About PaaS<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXq98ejyC1G0eIsvKI6WzAwXQJaA-iden3bbb0sLsa6tTxjaQxSBDZmlGApTWGZ0-on31wfZ-fOeMmoChOTj8xlVURn_wcxT5-COO1tiug3EQsK-L75ofPpMuX3BtGHdUnLK5kO8iO4zg/s1600/extremely-dangerous-gumball-machine-9061-1301416684-5.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="204" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXq98ejyC1G0eIsvKI6WzAwXQJaA-iden3bbb0sLsa6tTxjaQxSBDZmlGApTWGZ0-on31wfZ-fOeMmoChOTj8xlVURn_wcxT5-COO1tiug3EQsK-L75ofPpMuX3BtGHdUnLK5kO8iO4zg/s320/extremely-dangerous-gumball-machine-9061-1301416684-5.jpg" width="320" /></a></div>
I recently got some feedback on <a href="http://www.keeneview.com/2012/10/paas-is-automation.html">my previous musing that from the customer viewpoint, PaaS equals automation</a>. That led me to think of ways to articulate better what this means both to customers and vendors.<br />
<br />
Customers are basically indifferent to PaaS. This can be seen in the very modest market for PaaS as opposed to all the other aaS-es. Where is the PaaS that is producing anywhere near the value of the biggest SalesForce's $2.3B in SaaS revenues or Amazon's ~$1B in IaaS revenues?<br />
<br />
Customers are indicating - in the only way that matters - that they value they perceive from PaaS is orders of magnitude lower that the value of other cloud offerings.<br />
<br />
Are customers right to be so indifferent about PaaS? In a word, yes.<br />
<br />
Vendors have not done a good job of explaining the value of PaaS beyond singing paeans to productivity that comes from being able to deploy a complete application without having to configure the platform services for that application.<br />
<br />
The <a href="http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf" target="_blank">NIST definition of PaaS</a> defines it as "the capability to deploy applications onto the cloud without requiring the consumer to manage the underlying cloud infrastructure." (note: paraphrasing here as the NIST folks don't seem to write in English)<br />
<br />
Here's the problem with that definition: it mirrors exactly how 99% of Enterprise developers already work! In the enterprise, the functional equivalent of PaaS is IT. Once an enterprise developer is done with their app, they throw it over the wall to dev ops/app ops folks who magically push it through the production cycle.<br />
<br />
For most developers, the value proposition articulated by PaaS vendors just doesn't seem all that different from what they can get from internal IT or external IaaS.<br />
<br />
<br />
<ul>
<li><b>IaaS</b> allows me to rent a data center with a credit card and zero delay versus going through a six month IT acquisition cycle - eureka!</li>
<li><b>SaaS</b> allows me to deploy whole new business capabilities without a two-year funding and development cycle - hallelujah!</li>
<li><b>PaaS</b> has a lot more to offer than just productivity, but so far, that is all customers understand about it - so they let out a collective yawn.</li>
</ul>
<br />
<br />
Until PaaS vendors find ways to connect their platform to solving critical IT and business problems, PaaS will remain an under-perfoming member of the cloud family.<br />
<div>
<br /></div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-294880355377903512.post-569352912028052712012-11-30T14:23:00.001-08:002012-11-30T14:23:13.578-08:00Big Data And The Open Source Model - Can This Marriage Be Saved?<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsVsRfeIRECe1aoeo24tgwxZHSxuIqUCmKao_2k8YqtqB9o327eJ5nyT1fovnwPPMEfwBEttj4BQ8PeJqJe42XcY7zGzZztW4g4ZNCYeILkDtfkhmixnNMQ14G0TYB5yQDi8nLq5sxJ3c/s1600/Screen+Shot+2012-11-30+at+2.22.01+PM.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsVsRfeIRECe1aoeo24tgwxZHSxuIqUCmKao_2k8YqtqB9o327eJ5nyT1fovnwPPMEfwBEttj4BQ8PeJqJe42XcY7zGzZztW4g4ZNCYeILkDtfkhmixnNMQ14G0TYB5yQDi8nLq5sxJ3c/s320/Screen+Shot+2012-11-30+at+2.22.01+PM.png" width="320" /></a></div>
It is amazing how many open source software companies out there are trying to get hit by the same $1B bolt of lightning that hit MySQL without realizing that the MySQL result is not repeatable.<br />
<br />
Looking at the current batch of big data high flyers, from TenGen to Cloudera to Horton Works, each seems to be vying for the same kind of ubiquitous usage that enabled MySQL to get a more than 20x multiple. What they don't realize is that the failure of early open source acquisitions to deliver substantial value to owners has made buyers much more wary.<br />
<br />
Companies like MySQL were valued based on a mystical belief that downloads could be monitized (not unlike the similarly wishful belief in monetizing eyeballs that motivated disastrous dot com acquisitions in the 90s). Moving forward, open source companies will be valued the old-fashioned way: by the viability of their business model.<br />
<br />
Here are the top three places most big data open source companies are missing the boat:<br />
<br />
<ol>
<li><b>Prioritizing business model behind buzz</b>: although buzz is critical for adoption growth, a viable business model trumps all in positioning a company for IPO or acquisition. First and foremost, this means being able to charge significant prices for add-on product pieces that customers want, such as security, clustering and monitoring.</li>
<li><b>Confusing services with sales</b>: low margin services revenues are no substitute for high quality license revenues. More importantly, companies that build up large services teams often neglect to fully integrate their product, as product integration provides a driver for services engagement. This lack of product maturity in turn prevents customers from being willing to pay much for the product itself - a classic vicious cycle.</li>
<li><b>Hoping for a desperate buyer</b>: companies that purchased open source players have by and large to translate open source leadership into commercial market share. The open source downloads generate lots of buzz but little license revenue, saddling their owners with an expensive, services-led business. In the immortal words of Mitt Romney, hope is not a strategy (although it *did* turn out to be an ok strategy for the incumbent in that case).</li>
</ol>
<br />
<div>
<br /></div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-294880355377903512.post-5579223168290653482012-11-15T12:46:00.002-08:002012-11-15T12:48:21.380-08:00The Genius, The Conductor and The Bureaucrat<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5tzievC7qcJ7I1JhkqZgvwBQmyGybn7YkHBntZb3XA94fdpik2EuXydo59k0YOk7ove77cZMXMFp5eCMB2CjI5CIvLMs-QJHHLr2W5TLZm8NHSiTPi5kVKfCZB9-U7TDRCNX-8AB5eeQ/s1600/leaders.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="136" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5tzievC7qcJ7I1JhkqZgvwBQmyGybn7YkHBntZb3XA94fdpik2EuXydo59k0YOk7ove77cZMXMFp5eCMB2CjI5CIvLMs-QJHHLr2W5TLZm8NHSiTPi5kVKfCZB9-U7TDRCNX-8AB5eeQ/s400/leaders.png" width="400" /></a></div>
No, this is not a joke about three guys walking into a bar but the result of some recent musing about how the art of management is practiced in Silicon Valley.<br />
<br />
The classic Silicon Valley stories often feature what Jim Collins calls "the genius with a thousand helpers" (from his book <a href="http://www.jimcollins.com/">Good to Great</a>). Steve Jobs, Larry Ellison and many other valley icons were known for their vice-like control over all aspects of their business.<br />
<br />
When that Genius individual really is the smartest person in the world, you get the iPhone. When they are not, you get Palm's WebOs. Working for a boss who always has to be the smartest man in the room is a humbling experience but at least you know where you stand - at the bottom.<br />
<br />
The contrast to the Genius is the conductor, a person who - without playing an instrument themselves - is judged purely on their ability to draw great performances out of others. This is the idealized, servant CEO that is touted in all of the business school texts but seen much less frequently in the wild.<br />
<br />
Examples of the Conductor style of leadership would include people like Paul Maritz of VMware. In my experience, there is nothing in the work world that beats the thrill of working with a committed team on big, hairy, audacious goals where the person leading the charge is focused purely on helping the team win.<br />
<br />
The third category is the Bureaucrat. The thing to remember about Bureaucrats is that what they are best at producing is more Bureaucrats. These are people who are always overwhelmed with work but never make decisions that would offload that work. In a way, they follow the same model as the Genius, in that all decisions have to come through them.<br />
<br />
The goal for all CEOs should be to aspire to play the Conductor role, while realizing that it is human nature to slip into Genius and Bureaucrat now and again.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-39180315299833582842012-10-29T14:05:00.002-07:002012-10-29T14:05:50.141-07:00PaaS *Is* Automation<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhD-6WhtR82yATCfTDcwYFxOmlkEfNCxIw6QAxL1xAucfboKhykkXE-j7T750ahUiPg2t-6seNx5O05pRdkNt-fYZyx9XTZvwlOeM4u8O4hNFWEb12iYsPUjfqmaOM8fg-h5C8IgNsVZRw/s1600/robot.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="286" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhD-6WhtR82yATCfTDcwYFxOmlkEfNCxIw6QAxL1xAucfboKhykkXE-j7T750ahUiPg2t-6seNx5O05pRdkNt-fYZyx9XTZvwlOeM4u8O4hNFWEb12iYsPUjfqmaOM8fg-h5C8IgNsVZRw/s320/robot.jpg" width="320" /></a></div>
Cloud computing has a challenge endemic to many Silicon valley advances - a great technology triumph somewhat disconnected from a clear business benefit.<br />
<br />
The developer version of cloud computing is PaaS (Platform as a Service). Like cloud computing in general, PaaS has struggled to articulate clearly why it deserves to capture the hearts and minds of enterprise developers<br />
<br />
Hipper web developers have had no such hesitations and have collectively leapt to cloud computing platforms like Heroku and Cloud Foundry for Ruby on Rails.<br />
<br />
This difference in adoption tells an important story. By and large, enterprise developers have spent years building highly automated toolchains centered around tools like Eclipse and Clearcase and targeting both desktop and web clients.<br />
<br />
In contrast, platforms like Ruby on Rails were designed for web deployment and web tooling, so fit the online/PaaS model more naturally.<br />
<br />
I would argue that from an enterprise developer's point of view, PaaS is just about automation. When a PaaS appears with associated tooling that makes it easier for enterprise developers to do their work in the cloud than on their desktop, we will see a big spike in adoption. At a minimum, this will require the following:<br />
<br />
1. <b>Seamless integration with existing tools:</b> developers will want an easy on-ramp that doesn't require them to abandon existing tools like Eclipse, Clearcase<br />
2. <b>Automated build and test</b>: this is where an integrated cloud tool chain can really rock, but only if it is easier to use than existing internal solutions.<br />
3. <b>Opinionated client stack</b>: one of the biggest things holding Java back for full web development is that Java is not opinionated about how to build a client stack in the way that for example Ruby on Rails is. This means every development team has to come up with its own scaffolding and build process, making it difficult to deliver an automation solution that satisfies.<br />
<br />
Of these three, the third is the real show stopper. More on this later.<br />
<br />
ps. I thought briefly about coining a new acronym, PaaS *Is* Automation Stupid, but decided that we have enough acronyms in this space.<br />
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-77274654300517720102012-08-23T14:51:00.003-07:002012-08-23T14:51:37.371-07:00Evolutionary and Revolutionary Clouds<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYevuKz0ASLEKBRlLTRt8MPm7YuMAMAf18gG-xTBxj7NJpyi3dCSyx-TKoT8uyw9FIEFT_H5RTNoWL9kvlSCTgUdRNYfh3I2W5UUcqkneR8fCys8EDDNxbrmIh4oW5VzbueSy77suoAjU/s1600/revolution.jpeg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYevuKz0ASLEKBRlLTRt8MPm7YuMAMAf18gG-xTBxj7NJpyi3dCSyx-TKoT8uyw9FIEFT_H5RTNoWL9kvlSCTgUdRNYfh3I2W5UUcqkneR8fCys8EDDNxbrmIh4oW5VzbueSy77suoAjU/s1600/revolution.jpeg" /></a></div>
Now that we are a couple of years into the great cloud journey is it pretty clear that the big bang theory of cloud conversion is ain't happening.<br />
<br />
Yes, ISVs are moving rapidly to the SaaS model and it would be hard to find a software startup who is *not* starting in the cloud, but enterprise adoption of the public cloud is happening at a more stately pace.<br />
<br />
In large part this is due to the simplification required to make public clouds efficient and the complexity that characterizes most enterprise IT environments. To put it differently, the public cloud makes app deployment simple by pruning app deployment options to the point that few enterprise applications can fit.<br />
<br />
Moving forward, I see two paths for cloud adoption: evolutionary and revolutionary.<br />
<br />
<ul>
<li><b>Revolutionary cloud: </b>Public clouds like Amazon EC2 and CloudFoundry.com represents a revolutionary leap forward for companies that are willing/able to abandon their current platforms. The revolutionary cloud offers a high degree of operational productivity at the expense of service choice (e.g., you can have any color you want as long as its black).</li>
<li><b>Evolutionary cloud:</b> public/private clouds like VMware's vCloud Director enable enterprises to get cloud benefits (public/private deployment, low upfront cost, elastic scaling, self-healing) without having to make major changes to their application architecture. The evolutionary cloud offers a lower level of productivity with a greater range of choice (e.g., you trade of productivity for flexibility).</li>
</ul>
<br />
Over time, the revolutionary cloud will offer more choice and flexibility while the evolutionary cloud will offer higher automation. Some questions for enterprise developers to answer as they move along this path include:<br />
<br />
<ol>
<li><b>How much control do I have over the deployed application environment? </b>The more flexible the deployment environment, the easier it is to move that application to the public cloud.</li>
<li><b>How do I move applications between different clouds? </b>Having a way to move applications between evolutionary and revolutionary cloud architectures is just as important as being able to move apps between different flavors of public clouds</li>
</ol>
<br />
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-294880355377903512.post-29859253674889177222012-06-07T14:07:00.001-07:002012-06-07T15:19:22.622-07:00Building Killer Apps with Big Data<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJn9gKvJYSm2lMaWQq9oLJFa06Po7absoAsSuazRoAjHUQZaObooxCr8OHRsb2HiTJHCs12S9nOAVQh8Vq2GnOomq1daYb_drpUiEOg09fZT7s7INu6xM165OhA3KZHoLIbIGYX1GsjvM/s1600/big+data+cloud.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJn9gKvJYSm2lMaWQq9oLJFa06Po7absoAsSuazRoAjHUQZaObooxCr8OHRsb2HiTJHCs12S9nOAVQh8Vq2GnOomq1daYb_drpUiEOg09fZT7s7INu6xM165OhA3KZHoLIbIGYX1GsjvM/s320/big+data+cloud.png" width="319" /></a></div>
One thing that gets lost in the general Big Data hubbub is the critical question of apps. Big Data can provide stunning business insights but unless those insights are embodied into an application that can galvanize new business behaviors they are not worth much.<br />
<br />
VMware has been a thought leader in the area of cloud application platforms for some time. Now we are turning our attention to the intersection of Big Data and Cloud Computing.<br />
<br />
What does it take to build applications that can move easily between private and public cloud while accessing data inside and outside of the firewall?<br />
<br />
In particular, what are the best practices for building cloud applications that leverage big data? Here are some of our initial thoughts:<br />
<br />
<br />
<ol>
<li><b>Lightweight services: </b>REST is the new SOA - lightweight services form the basis for supporting web front ends while pub/sub messaging like <a href="http://www.rabbitmq.com/">RabbitMQ</a> forms the basis for back end workflow and transactions.</li>
<li><b>Mobile-first UI: </b>the <a href="http://twitter.github.com/bootstrap/">twitter bootstrap library</a> finally enables developers to build HTML5 apps for Mobile devices that scale beautifully to tablet and browser-based desktops.</li>
<li><b>Fast data:</b> scaling the front end of the application often requires in-memory data management. The easiest way to interact with core data is through a SQL interface such as <a href="http://communities.vmware.com/community/vmtn/appplatform/vfabric_sqlfire">SQLFire</a>.</li>
<li><b>Big Data:</b> knowing what is going on right now takes fast data, knowing what to do about it takes access to large amounts of historical data. The key here is to provide integration between the two data sources so that the data warehouse is kept as up to date as possible with the in-memory database.</li>
<li><b>Application-level management:</b> <a href="http://www.vmware.com/products/application-platform/vfabric-application-performance-manager/overview.html">managing application performance</a> as a series of logical tiers rather than physical instances eliminates a great deal of complexity for systems admins.</li>
<li><b>Cloud deployment:</b> automated, dev/ops solutions like <a href="http://www.vmware.com/products/application-platform/vfabric-application-director/overview.html">Application Director</a> take the black magic out of large scale systems deployment, collapsing a multi-day deployment sequence into a few minutes of scripted wonder. </li>
<li><b>Elastic scaling:</b> a core value of cloud computing environment like <a href="http://www.cloudfoundry.com/">Cloud Foundry</a> is sizing the compute resources to the task at hand - when demand is high, the resources scale up and vice versa.</li>
<li><b>Self healing: </b>cloud means never having to say you're sorry that your web site went down because a component croaked and couldn't restart - again, <a href="http://www.cloudfoundry.com/">Cloud Foundry</a> comes to the rescue.</li>
</ol>
<div>
I will be discussing <a href="http://event.gigaom.com/structure/schedule/">how to build killer apps for big data at the GigaOm Structure conference</a> at the end of this month along with Tom Roloff, COO, EMC Consulting.</div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-82990436227483728892011-10-04T09:35:00.000-07:002011-10-04T09:43:33.299-07:00The Web is the New App Store<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj0NnizLk9HMMHi1zyNQGnHijVeFXEfowTZtPDp84UV8dQClTln5QDR04v7zO6cx9ydFIEglnoKT1wwJf-_cO9YIrUFpE_fbky8BW8uJ_D4W6TO5TE7OoLACT9w3Kd-DEAjxjIqLVWNS28/s1600/6000th_store.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 30px 10px 0px;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj0NnizLk9HMMHi1zyNQGnHijVeFXEfowTZtPDp84UV8dQClTln5QDR04v7zO6cx9ydFIEglnoKT1wwJf-_cO9YIrUFpE_fbky8BW8uJ_D4W6TO5TE7OoLACT9w3Kd-DEAjxjIqLVWNS28/s320/6000th_store.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5659677850752299650" /></a>I attended the <a href="http://event.gigaom.com/mobilize/">GigaOm Mobilize</a> conference (where VMware was well represented by <a href="http://communities.vmware.com/community/vmtn/cto">CTO Steve Herrod</a>) and came away with a few observations that are relevant for our overall mobile strategy:<br /><ol><li><b><span class="Apple-style-span" style="font-weight: normal; "><b>The web is the new app store. </b></span></b><b><span class="Apple-style-span" style="font-weight: normal; ">I had dinner with the heads of mobile for two large retail chains. Although each of them have multiple App Store apps, the vast majority of their mobile business is coming through the safari browser and not the app store. Consumer behavior is to go to the web to buy things, even on mobile.</span></b></li><li><b> There are only two mobile markets, native iPhone and mobile web.</b>The shift to HTML5 (+Phone gap if necessary) is happening rapidly. Almost every speaker talked of the html5/jquery/phonegap stack with a few native iPhone holdouts (e.g., gaming, iPhone only apps like Hipmonk). Phone gap allows html5 apps to access native smartphone features and be packaged for native app stores, effectively erasing the lines between html5 and native. There was zero discussion of native development for Android or any other non-iPhone platform.</li></ol>Here are some intriguing, but less well formed conference themes:<br /><ul><li>Notifications are the "home page" for mobile apps. Mobile apps force developers to rethink and simplify enterprise apps - making them more modular and "attention-driven"</li><li>iPad is rapidly changing expectations about how web apps work. SalesForce's Do.com is using the iPad as their primary web platform and porting from there to browsers and smartphones.</li></ul>Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-294880355377903512.post-30838685754898216442011-09-01T15:51:00.000-07:002011-09-01T16:07:50.639-07:00Darwin's Cloud<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipOWt2mFXu1lmNTssyhSxHQ3oQRsgKlpEEbuCnUubRNQ0DVSbO8E0npgMyt6oakXaWGFshnpxloKzRTLA8zgLDKODla3UvQXrSI4yrKMq8cOu8J9GDi0B9ELoEr9mR8MmBlnRTLpdySHM/s1600/Charles+Darwin.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 30px 10px 0;cursor:pointer; cursor:hand;width: 240px; height: 320px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipOWt2mFXu1lmNTssyhSxHQ3oQRsgKlpEEbuCnUubRNQ0DVSbO8E0npgMyt6oakXaWGFshnpxloKzRTLA8zgLDKODla3UvQXrSI4yrKMq8cOu8J9GDi0B9ELoEr9mR8MmBlnRTLpdySHM/s320/Charles+Darwin.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5647529917397662418" /></a>RedHat conducted a <a href="http://www.redhat.com/evolutiontocloud/">survey</a> of over 1,200 VMworld attendees on their cloud plans. Here is the question that I found most interesting:
<br />
<br /><i>What primary development framework are you planning to use in the cloud?
<br /></i><ul><li><i>Java EE 32%</i></li><li><i>.NET 29%</i></li><li><i>PHP 14%</i></li><li><i>Python 6%</i></li><li><i>Spring 6%</i></li><li><i>Ruby/Rails 5%</i></li></ul>If you take this at face value, the ideal PaaS for the enterprise would support Java EE, .NET and PHP. So far, this is well beyond the capabilities of the existing PaaS vendors.
<br />
<br />In particular, there is no PaaS vendor bridging the Java/.NET divide. This raises a natural question: what is the fastest way to evolve cloud platforms?
<br />
<br />There are two approaches to filling in these PaaS framework holes:
<br /><ul><li><b>Do it yourself</b>: <a href="http://gigaom.com/cloud/java-developers-meet-heroku/">Heroku just added Java support</a> to their cloud. Because PaaS offerings from Amazon and Heroku are proprietary, they are pretty much stuck with the go it alone approach.</li><li><b>Create an ecosystem</b>: <a href="http://gigaom.com/cloud/cloud-foundry-adds-php-python-appfog-now-a-user/">Cloud Foundry just added PhP and Python</a> support through partners. A huge advantage for open source clouds is that they can leverage the work of their communities to move farther and faster than closed-source competitors. </li></ul>Open source clouds should be able to sustain a faster rate of revolution, provided that they can continue to build vibrant communities that contribute back to the core project.
<br />
<br />
<br />
<br />Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-294880355377903512.post-49069134515386033392011-08-25T11:31:00.000-07:002011-08-25T12:05:42.312-07:00Cloud Foundry is the LAMP Stack of Cloud Computing<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8wO4GEGAdbs2S1yxljZZBH1cMHd114hZoMHnMZj1MpcS3M65zfWf9f21TgzT2Rsx6UR3m4By5cGLSiKKdzJOlIMIdZ2EeJpHNrew1zzJAE0-0b8W5SxSQncRo6EdOhOWEHZYXZPimqkE/s1600/cloud_foundry_lamp_for_cloud.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 249px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8wO4GEGAdbs2S1yxljZZBH1cMHd114hZoMHnMZj1MpcS3M65zfWf9f21TgzT2Rsx6UR3m4By5cGLSiKKdzJOlIMIdZ2EeJpHNrew1zzJAE0-0b8W5SxSQncRo6EdOhOWEHZYXZPimqkE/s320/cloud_foundry_lamp_for_cloud.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5644868543163553026" /></a><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">Just as the LAMP stack provided a core foundation next gen for web applications, Cloud Foundry is providing a core foundation for next gen cloud platforms.</span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">
<br /></span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;"><a href="http://www.cloudfoundry.com/">Cloud Foundry</a> announced today that <a href="http://blog.cloudfoundry.com/post/9374366916/cloud-foundry-adds-php-and-python-through-community">two new startups are building their clouds based on Cloud Foundry</a>.</span></span></div><div><span class="Apple-style-span" style="font-family:arial;">
<br /></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">Cloud Foundry is proving itself to be truly the foundry for creating entirely new cloud offerings:</span></span></div><div><ul><li><span class="Apple-style-span" style=" ;font-family:arial;"><a href="http://www.activestate.com/">ActiveState</a> is building a cloud for Python and Django and contributing code to support Python back to the Cloud Foundry open source project.</span></li><li><span class="Apple-style-span" style=" ;font-family:arial;"><a href="http://www.appfog.com/">Appfog</a> is building a cloud for PHP developers and contributing code to support PHP back to the Cloud Foundry open source project</span></li></ul></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">The beauty of this is that innovative startups are able to start with a scalable cloud "stack" that gives them a multi-language PaaS without locking them into a particular cloud provider. </span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">
<br /></span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">So for example, Appfog gets to use Cloud Foundry's best in class PaaS services and then target deployment to <a href="http://aws.amazon.com/ec2/">Amazon's EC2</a> and services like <a href="http://aws.amazon.com/s3/">S3</a>. Appfog CEO <a href="http://twitter.com/#!/cardmagic">Lucas Carlson</a> blogged <a href="http://blog.phpfog.com/2011/08/25/appfog-reveals-cloud-foundry-integration-for-multi-language-support/">here</a> about how standing on the shoulders of cloud computing giants will allow Appfog to win in the cloud by providing the most compelling user experience.</span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">
<br /></span></span></div><div><span class="Apple-style-span" style="font-family:arial;"><span class="Apple-style-span" style="font-size:medium;">Expect to see the pace of innovation accelerate dramatically going forward!</span></span></div><div>
<br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-89402384425916397502011-08-18T11:44:00.000-07:002011-08-18T12:21:53.365-07:00DevOps and PaaS - Friend or Foe?<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicJNy-7PurOksm3uayYDZR3uTgn9P8gVWjOsv7lwbCccS5cqjyrRrg93opA4lwWqHRRgxqOvBJXu76TUNDUEzNpqhwCnEL2bcXVSIT6xCA4yNf7n5VlGmjLUbTpF4-rJbnoyZwxa2QJEE/s1600/wolf-sheep1.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 30px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 267px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicJNy-7PurOksm3uayYDZR3uTgn9P8gVWjOsv7lwbCccS5cqjyrRrg93opA4lwWqHRRgxqOvBJXu76TUNDUEzNpqhwCnEL2bcXVSIT6xCA4yNf7n5VlGmjLUbTpF4-rJbnoyZwxa2QJEE/s320/wolf-sheep1.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5642269818995794626" /></a>DevOps, which I will arbitrarily define here as "automating SysAdmin tasks to streamline application lifecycle management," raises important questions about the cloud.
<br /><ul><li>Developers may ask: "if I have a self-service portal for deploying applications (aka PaaS), do I need SysAdmins at all?"</li><li>SysAdmins may ask: "isn't PaaS just a monstrous black box that prevents me from provisioning the specific services we need to deploy real-world apps?"</li><li>VMware asks: "what if you could get a PaaS that wasn't black box, enabling developers to deploy apps easily while still giving SysAdmins the ability to provision any services they needed (aka <a href="http://www.cloudfoundry.org">Cloud Foundry</a>)? </li></ul>I had a good conversation recently with <a href="http://www.johnmwillis.com/">John Willis of DTO Solutions</a> (twitter feed <a href="http://twitter.com/#!/botchagalupe">here</a>) in which he waxed eloquent on how DevOps and Cloud Foundry can live together in harmony. Here were the key points I took away:
<br /><ul><li><b>SysAdmins distrust the black box nature of PaaS</b>: Typical sysadmin thinks that they can get to 75% of PaaS functionality with DevOps tools like <a href="https://github.com/opscode/chef">Chef</a> without giving up any systems architecture flexibility. In contrast, PaaS solutions like <a href="http://www.heroku.com">Heroku</a> provide developers an easy to use PaaS but gives SysAdmins zero ability to add services that Heroku doesn't support. </li><li><b>Cloud Foundry solves the SysAdmin aversion to cloud vapor</b>: CloudFoundry runs anywhere, incuding on your laptop. Cloud Foundry's service container concept is particularly strong, kind of an appliance on steroids.</li></ul>There is a strong natural between DevOps and PaaS. Products like Chef and <a href="https://github.com/puppetlabs/puppet">Puppet</a> are strongest for installing and configuring the OS and middleware stack. PaaS solutions like Cloud Foundry excel it deploying application architectures.<div>
<br /></div><div>The holy grail is to use Chef or Puppet provisioning Cloud Foundry services that can then be easily consumed by developers. <a href="http://www.dtosolutions.com/">DTO Solutions</a> is putting on events to show SysAdmins how to make this happen.</div><div>
<br />You can also <a href="http://dtolabs.eventbrite.com/">register for the a DevOps HackDay featuring CloudFoundry</a>. The first one is being put on at VMware, September 8, 2011.
<br />
<br />
<br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-294880355377903512.post-31010335377828413462011-07-27T09:30:00.000-07:002011-07-27T10:06:18.800-07:00PaaS is a Cloaking layer for clouds<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiKH6TUYr_txVyIjraQ3WRPNCzM1JhqV29lLjqmtFHHoBVPcavyukgWRmEObT37MHsOQy7AC2G8wS-1vOF1z737mQPCKC-Z0FBjREdM80qxdxH8hzhFYFJzrC0MnAcQoEGSFftiI_pGiNc/s1600/USSEnterprise_1762648b.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 200px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiKH6TUYr_txVyIjraQ3WRPNCzM1JhqV29lLjqmtFHHoBVPcavyukgWRmEObT37MHsOQy7AC2G8wS-1vOF1z737mQPCKC-Z0FBjREdM80qxdxH8hzhFYFJzrC0MnAcQoEGSFftiI_pGiNc/s320/USSEnterprise_1762648b.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5634072666183358338" /></a>We seem to be coming to the end of the <a href="http://www.keeneview.com/2009/03/what-is-platform-as-service-paas.html">definition of Platform as a Service (PaaS)</a> blog posts and are now moving on to the more pressing question of what is PaaS good for?<br /><br />In a recent <a href="http://gigaom.com/broadband/vmwares-preparing-for-the-post-document-era/">Paul Maritz talk at GigaOm Structure conference</a>, he referred to PaaS as "a cloaking layer for clouds." This is an elegant definition for a rapidly expanding market of add-on cloud services.<br /><br />If Cloud 1.0 is a set of servers in the sky (think <a href="http://aws.amazon.com/ec2/">Amazon EC2</a>), then Cloud 2.0 is a layer of services that hide the complexity of developing, deploying and managing applications in the cloud (think <a href="http://www.cloudfoundry.com/">CloudFoundry</a>).<div><br /></div><div>The API for Cloud 1.0 is the virtual machine/OS. The API for Cloud 2.0 is the application container itself - services like CloudFoundry, Elastic Beanstalk from Amazon and Heroku allow a developer to hand over an application to the application container without having to know anything about what operating system that application is running on or how it communicates with other services like load balancing, failover and database.<br /><br /><div>Here are several examples of PaaS cloaking to simplify cloud development:<br /><ol><li><b>Dev/test environment</b>: <a href="http://www.wavemaker.com">WaveMaker</a> pioneered the market for cloud-based development of standard Java applications. In addition, simply virtualizing the provisioning of servers has huge value for development and testing purposes. Today, this is a major driver for developer adoption of cloud in general and PaaS in particular. I have talked to CIOs who claim that over 30% of their resources for new projects goes into provisiong and managing the dev/test environment.</li><li><b>Scalable application deployment</b>: Amazon EC2 has made its mark by providing a highly scalable data center in the sky. <a href="http://gigaom.com/2010/06/08/how-zynga-survived-farmville/">Zynga uses Amazon as a safety net</a> when it has no idea how popular one of its games will be. Once Zynga has a handle on demand, they move the game over to their own data center. Just a year ago, getting this kind of scaling required detailed understanding of cloud architecture and a whole lotta scripting. Now it's as easy as "vmc push --instances 8"!</li><li><b>Resilient application deployment</b>: infinite scaling is great, but what happens when a <a href="http://www.infoq.com/news/2011/04/Amazon-EC2-Outage-Explained">network configuration error brings down in your infinitely scalable data center</a>? In that case, having a PaaS service that automatically mirrors applications across multiple data centers makes a critical difference.</li></ol>In a sense, PaaS is just a new kind of virtualization, one that operates at the level of an application container instead of an operating system. No wonder then that VMware has a lot of firepower to bring to the PaaS market.</div></div>Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-294880355377903512.post-7835907645399873322011-06-02T16:08:00.000-07:002011-06-02T16:57:22.797-07:00Where is the Killer App for PaaS?<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIbl9falPpKACpY5qKP2avHEF1J6s0toU__K0bOV81jwWeSgUkk9iVRPzgEzGCQ2IdKmffgq_iFSt3wnlQ7V1oEd4IXxMppCNS3t4PhcfAmRj9vD-a4oPHBMOBK2ZQGGkeTK6bCc-B3-k/s1600/killerapp.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img style="float:left; margin:0 25px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 320px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIbl9falPpKACpY5qKP2avHEF1J6s0toU__K0bOV81jwWeSgUkk9iVRPzgEzGCQ2IdKmffgq_iFSt3wnlQ7V1oEd4IXxMppCNS3t4PhcfAmRj9vD-a4oPHBMOBK2ZQGGkeTK6bCc-B3-k/s320/killerapp.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5613764151653333570" /></a><p></p><p>Over the last month, I have had lengthy discussions about developer adoption of Platform as a Service with two of my favorite cloud computing analysts - John Rymer of Forrester and Michael Cote of RedMonk.</p><p>The net of these conversations that we are still early in the adoption curve for PaaS. In particular, developers are not yet demanding PaaS the way operations people are demanding Virtualization.</p><p>Here is my summary of these discussion:</p><p></p><ul><li><b>Developers are wary of PaaS:</b> developers are not overly keen on PaaS at the moment. They are not yet mentally prepared to give up the middleware layer of their applications. Lacking a compelling reason to use PaaS, developers are sticking with tried and try development stacks.</li><li><b>PaaS for existing apps has limited benefit:</b> For existing applications, there's not much to gain by simply moving from non-cloud modes to cloud modes. This is the foundation of Cote's Cloud Rule - "<a href="http://www.keeneview.com/2011/04/cotes-rule-if-it-aint-broke-dont-cloud.html">if it ain't broke, don't cloud it</a>". </li><li><b>PaaS fits best for new apps:</b> with new applications, the benefits of PaaS (cost and agility) all seem to line up.</li></ul><p>This means that cloud vendors need to "connect the dots" for developers and business managers to accelerate their adoption of cloud platforms. In particular, there are two </p><p></p><ul><li><b>PaaS lowers the bar for web development: </b>PaaS solutions like <a href="http://www.cloudfoundry.com/">Cloud Foundry</a> and <a href="http://www.wavemaker.com">WaveMaker</a> make the cloud's benefits available to everyone, not just the A-Team. Of course, this requires significant education to let business developers know that easier web dev tools exist.</li><li><b>PaaS speeds the delivery of apps for all developers:</b> Michael Cote recently argued that <a href="http://www.redmonk.com/cote/2011/06/02/how-to-do-cloud-marketing/">speed is the killer app for cloud</a>. Again, this requires market education to get the word out that quantifies these benefits. </li></ul><p></p><p><br /></p><p><br /></p><p><br /></p><div><br /></div><p></p>Unknownnoreply@blogger.com0