I think quotas are certainly something to discuss and consider. I
often hear contradictory things like, "you can scale as much as you
want to on X" and, "I'm not sure you could really launch 5 billion
instances on X". Primarily, it's an SLA issue.
If cloud infrastructure providers claim that deployment rates are
unlimited, that is pure deception, that's just impossible. However,
they could certainly provide an SLA that accounts for the deployment
of physical resources. As such, it might be best to define quotes not
in terms of hard limits, but in terms relative to time. Provider X
could specify in its SLA a quota/rate as "10,000 instances per day",
or "10TB per day".
Regards,
Eric Windisch
By mid next week, we will re-post for redistribution, in multiple
formats, removing the numbering on the left side, etc. We also planned
to cut up the graphics so people could easily grab and reuse as Sam
suggest. I like the idea of scribd. I also thought of eventually
creating a presentation that is a summary of the whitepaper so others
can reuse if they want (perhaps in slideshare also). Any other
suggestions for file format / or best ways to redistribute...let us
know.
DocBook has served us well on the Zend Framework project- we've been able to render our reference guide in several formats with few problems. Of course, there are some formatting limitations that you have to accept, but DocBook and should be expressive enough for this white paper and the available stylesheets can be configured/tweeked as necessary to get the desired results. One of our contributors actually wrote a stylesheet to render the manual in one of the wiki markup formats (can't remember exactly which one- one of the markups that's supported by Confluence). That might help in this case, although putting it back in to DocBook could prove much more difficult. I've never used the use case feature in Drupal, although I have some PHP experience I could bring to bear. ;) Have we thought about where the source might live? I'm assuming a some kind of source code repository somewhere, although there are certainly alternative solutions that may be simpler. ,Wil On Monday, August 03, 2009, at 12:48AM, "Sam Johnston" <sa...@samj.net> wrote: >
DocBook has served us well on the Zend Framework project- we've been able to render our reference guide in several formats with few problems.
Have we thought about where the source might live? I'm assuming a some kind of source code repository somewhere, although there are certainly alternative solutions that may be simpler.
I don't think that vendors are relevant for a use case document such as this. I can certainly understand why people might be interested in whether Amazon, MS, Google, etc. have contributed to the effort, but I agree with Doug that associating any vendor's name with this document will compromise the work that we have all put in to it.
No one is hiding the fact that Doug started the effort and that he's from IBM. For that matter, I'm from Zend Technologies, and I'm also doing this on the clock. But these are really interesting historical footnotes; an open effort is an open effort. Having run a popular open source, company-backed PHP framework project, I am convinced that it's about the ecosystem around the effort, and not the origins.
I do understand and appreciate your points, but as for the matter of vendor names on the doc or whether it should be associated with one primary author, I agree 100% with Doug.
I asked the Sys-con folks to edit the title of the post and remove the
mention of IBM.
http://cloudcomputing.ulitzer.com/node/1056403
I just want to point something.... and I do not want to put more wood
in the fire.
But is there anybody who contributed to the paper with a use case or a
paragraph and he doesn't appear as a contributor? Because that is my
case, I contributed with a use case and I have been ignored. I wonder
if the brownie point is only for the IBM folks, and that is not fair
from the aim of this group.
@Jian
I don't think that what I said really impacts their idea of calling
the "internal cloud"/"external cloud" hybrid a "private cloud".
However, I know for sure is that they are avoiding the usage of the
term "public cloud" entirely. i.e. in cases where it's purely an
"external cloud", it may also be referred to as a "private cloud".
They certainly are not referring to "external clouds" as "public clouds"
It's also possible that I am recalling this incorrectly, it's been a
few months since the conference. VMware 2009 is at the end of this
month, this usage may appear in the keynote then.
In the whitepaper, we may want to mention that a "public cloud" may
also be referred to as an "external cloud", and that a "private cloud"
located on-premise (hosted on an enterprise's infrastructure) may be
referred to as an "internal cloud".
Either way, I think footnote number 2 on page 6 I think covers this
usage.
Andrew
On Aug 4, 2009, at 5:31 PM, Jian Zhen wrote:
Lines 457-459
Do you guys think that maybe "cloud databases" should be presented as
its own use case?
Line 464
again, "common file format for the VM and its associated metadata"
Line 468-471
It should also be possible to download and upload standard format VM
images. Do you guys consider these specifics to be covered by "move"?
Section 3.4
Is there any need to mention ownership of the contracted cloud service?
Lines 497-498
Per the discussion Ken and I are having, should we instead say that a
private cloud "is logically contained within the enterprise (i.e.
behind the same firewall, on the same network, connected by a VPN)".
Or will our usage of "private cloud" only include those that
physically located within the enterprise?
Lines 508-510
Add "Chargeback". I also think that interoperability here needs to
address linking specifically to a billing system such as SAP.
Lines 3.6.4.1
Add "Common API for VM Management". Without this, cloud users will
have to adapt their applications to each cloud provider.
========
In the customer scenarios section, I think we have completely left out
one of the most common uses of Amazon EC2 and Google AppEngine --> Web
Startups.
The 5 scenarios listed are extremely big enterprise and government
focused. What about individuals and SMBs?
Also, given that nearly 25% of the US workforce is self-employed (and
this is growing), what about considering the cloud needs of these free
agents? Most free agent needs I imagine will be met by SaaS solutions
such as Plaxo, Google Docs, Zoho, MobileMe, etc.
If this document becomes an introductory reference answering the
question "what is cloud computing?", I think it's important that the
customer scenarios vary a bit more.
Andrew
@Andrew, that's news to me but I think since "Public" and "Private"
match NIST we should stick with them, but I think I'll start using
"Internal" and "External" more...
Hmm, then that begs the question; "What do you call a cloud I run
(i.e. internally) that provides access to the public at large?"
You can see how it works here:
http://us.php.net/manual/en/function.fopen.php
Comments are at the bottom of the page.