I tend to think of cloud computing as a business model underpinned by
virtualization. Just as the virtualization layer abstracts the
underlying hardware, there's a front-layer that abstracts the cost,
sla, workload definition from the underlying computing
infrastructure.
We,and many startups, are using EC2 because the low, standard,
predictable and variable cost with elastic provisioning of resources
in minutes. And this is all accessed on a self-service basis with full
control of the life cycle. This change is hugely revolutionary vs
what we faced before with dedicated hosting.
Now when I hear customers talking about building a private cloud,
generally they mean the ability to deliver all or a subset of the
"standard, predictable variable, elastic, self-service, etc" value.
So where's the difference between private cloud and public cloud? It
is wholly dependent on your role. If you are building the
technology,the technologies and issues are very similar. If you are a
consumer, you'd like to treat them both the same,
But if you are the owner or operator, the private cloud is very
challenging. You need to think of a couple of things, One, what are
the standard environments and workload variations I will allow? How do
I condense everything we do into a predictable unit cost? And, how do
I provide elasticity? There are many other challenges as well, but
those three are biggies for your typical IT geek.
-Rodrigo Flores
http://www.cloudfrontoffice.com (blog)
http://www.servicecatalogs.com (blog)
On Jun 26, 12:01 pm, "Lisa Noon, IBM" <
ln...@us.ibm.com> wrote:
> Hello Doug,
>
> As a matter of fact I was having this discussion the other day with an
> architect at a major financial services company. He made the point
> very clearly that for reasons of pure governance they will create
> "bounded" clouds, meaning purposefully constructed and auditably (is
> that a word :)) described boundaries. From the outside they conduct
> penetration tests, and on the inside perform all manner of similar
> tests, including virus scans, etc. So the point I put forth that I
> think this gentleman would support is that private clouds have a
> boundary attribute that is not characteristic of public (non-private)
> clouds.
>
> On Jun 25, 1:28 pm, Doug Tidwell <
dtidw...@us.ibm.com> wrote:
>
> > Whenever I disagree with people whose opinions I respect, my
> > assumption is that I've missed something. (Learning Mode is always
> > more productive than Arguing Mode.) But as much as I've thought about
> > it, I can't understand why the private cloud isn't a valid use case.
> > The only difference between a private cloud and a public one is the
> > fact that none of my data or processing goes outside my firewall, but
> > that's a *huge* difference. (The DoD is particularly finicky on this
> > point.)
>
> > So with all due respect (which is a lot) to Sam Johnston andhttp://
twitter.com/coteandothers, what am I missing? Does anybody