Oracle Launches 'Private Cloud' Box
aesoteric writes "Oracle chief executive Larry Ellison has used the keynote of Oracle OpenWorld to launch the 'Exalogic Elastic Compute Cloud' — an appliance combining server and storage hardware with a pre-tuned web server, hypervisor and other middleware. Introducing the product as 'a honking big cloud in a box,' Ellison shifted from his previous criticism of the terms 'cloud computing' and 'private cloud' by using the exact same terms to sell a physical appliance."
Oracle also took the wraps off Unbreakable Enterprise Kernel for Oracle Linux, which is based on the 2.6.32 Linux kernel.
On-demand self-service. - A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider.
Broad network access. - Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling. - The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.
Rapid elasticity. - Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured Service. - Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Then as far as deployment models we have:
Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.
Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.
Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
NIST has not defined "cloud in a box" as a deployment model. The document you copy from It is more of a journalistic storytelling than a standard. NIST defines units of measure and probably verify encryption methods that is part of the internet, but they are no authority on "cloud computing" anymore than WSJ. IEEE has an annual conference on cloud computing, and NIST has not shown up in discussions not as a presenter on any other level than secure transport verification.
don't cut it off www.mgmbill.org