There is an interesting project/experiment that helps users see what it is like to be free from Facebook for 99 Days or more.
If you want to check it out, head over to:
As all forms of Cloud Computing become more popular, it is increasingly important to understand the contractual implications of integrating cloud providers into an organizations computing portfolio. Recently, Stanford Technology Law Review posted a great paper that covers the fundamental aspects of cloud contracts. It is a must read for anyone interested in contractual concepts and issues with cloud providers and those involved in the due diligence around using cloud technologies in their organization.
Click HERE for access to the Stanford Technology Law Review website.
Since I am the creator of the CriKit, let me explain a bit about it’s genesis. Like many others in the Private Cloud space, I was very frustrated with the state and cost of Private Cloud platforms. I have been watching the entry point for Private Cloud hardware and software dropping over time. However, it was still nowhere near the level for a small company or individual tinkerer to acquire. It was still in the realm of larger businesses with budgets for projects. I set out to change all that and make Private Cloud platforms available to the masses at a reasonable price point. The vision was to create a Desktop Private Cloud platform that is Compact, Powerful, Energy-efficient and Reasonably Priced. The result of a lot of effort is CriKit – Cloud Resource and Infrastructure Kit. Make no mistake, it may be small, but it is very capable and only sips electricity to provide an entire Private Cloud platform. Further, in many critical ways, CriKit also represents the future of small business computing. It can run as many virtual servers as can be accomplished by adjusting CPU and Memory and it can certainly participate in a Hybrid Cloud arrangement, so it has all the makings of a future cloud solution now. Today, a company can run 8 virtual servers on each node and burst to public clouds if necessary. With 4 nodes, that is 32 virtual servers, plus burst capabilities to public clouds. That sounds like a nice small business solution to me. However, that is not CriKit’s initial audience. It is aimed at people like me and maybe you. Those that need to develop, test, evaluate, investigate and educate on Private Cloud technologies. I want to run Eucalyptus today and Nimbula tomorrow, and Open Nebula the next and save my entire multi-node configurations so I can build what I want, when I want. With CriKit, I can do that. CriKit is unique in the market today but others will follow. As a solution, it makes too much sense and is too valuable to certain roles for companies not to develop something like it. But, for now, CriKit is the only one of its kind and if you develop, test and educate around multi-node cloud technologies and you want an entire cloud on your desk, it is ok to drool. 32 threads, 64GB of RAM in 4 nodes, Multi-TeraBytes of Storage, a powerful Management/Development Workstation plus KVM and Network switches make this one very, very cool Desktop Private Cloud solution ….
This concept primarily applies to Public Cloud environments and should be considered when determining the ROI of any Cloud-based solution.
Morse Uncertainty Principle of Cloud Computing© (MUPCC)
The primary objective of business computing is to run applications that provide a benefit to the organization. MUPCC postulates that, in Cloud Computing environments, the amount of the environment being used specifically for the business application is adversely affected by variables that are dynamic and arguably uncontrollable. MUPCC has direct relevance to the ROI from Cloud Computing environments.
In Cloud Computing implementations there is a wide variety of software that is loaded and running on the application compute node. This software includes the Hypervisor, Operating System(s), General Management, Monitoring/Metering, Firewall, Antivirus, Backup, and others depending on the infrastructure design. MUPCC contends that the CPU, Disk, Network and Storage utilization of the combination of all the node software is sufficiently dynamic and unpredictable so as to adversely affect the primary application workload and reduce the business benefit expected from that workload relative to the investment in the environment.
When you add the effects of random workload migration between physical compute nodes in a virtualized environment, the adverse effects on the compute environment are increased because all workloads on both nodes – the sending node and the receiving node- are affected by the migration. CPU, Memory, Networking and Storage are consumed to perform the migration which affects all other workloads on the node. Further, depending on the overall computing environment, several, to many, nodes may be affected by inter-node workload migration because network bandwidth and storage are shared by some number of additional nodes.
The high level variables that affect each compute node include:
1. Primary business application demand
2. Number of installed Software Applications
3. Efficiency, quality and operational characteristics of all installed software
4. Virtual Machine density
5. Amount of node memory consumed at any given time
6. Amount of node CPU consumed at any given time
7. Amount of node-available network bandwidth consumed at any given time
8. Amount of data transferred in the storage environment at any given time
9. Number of VM node-to-node migrations at any given time
10. Policies and processes of the organization that affect the computing environment – backup schedule, VM snapshots, antivirus scans, patching schedule, etc.
11. Random Operating System behavior – indexing, disk maintenance, etc.
All of these variables directly affect the amount of compute resources that are available to the primary business application on a given cloud compute node.
Further, the infrastructure of the Public Cloud implementation could be sufficiently dynamic and unpredictable as to effect the creation of new computing instances simply because existing instances are resource constrained, precisely because of MUPCC. Organizations using Public Clouds need to investigate this concept to their satisfaction to ensure they are getting the resources they think they are and are getting billed according to the resources they use for their applications.
MUPCC should be considered when determining the ROI of a Cloud Computing infrastructure investment.
The term, “Morse Uncertainty Principle for Cloud Computing” is a copyright ©2011 of Paul Morse, Redmond Wa.