Eucalyptus-based solution that is bundled into the Ubuntu installation from 9.10 onwards and allows you to install a IaaS cloud into which you subsequently install Ubuntu Server instances, rather than directly installing an Ubuntu Server. The Eucalyptus proposition is that the cloud you create is identical from an API – and therefore a tooling – perspective to an Amazon EC2 cloud, and the same Ubuntu instances can run inside it, and even can be cloud-bursted out to it. Canonical make a lot of this duality in their positioning of Eucalyptus and the Ubuntu Enterprise Cloud. It feels very-much like an “onramp” message that we hear from VMware.
TVP Category Archives
Rackspace Hijacks OpenStack
Rackspace has got the OpenStack governance model spectacularly wrong, and as a result the whole initiative is in peril. Not only are the Chair and the Chief Architect appointed directly by Rackspace, but 3 additional members are appointed directly by Rackspace, meaning that the 4 independently-elected Community members (even if they could agree) could never form a majority. There is actually no need to gain control explicitly. You control by contribution. Since Rackspace contributes most it will gain most control. Rackspace doesn’t actually need control to satisfy its business objectives. ll it needs is to make sure the project is successful and retain enough control over the project to ensure its own needs are met. So our suggestion to OpenStack is to take their Governance model, rip it up and start again.
How Many VM’s Can I Run?
I saw a question get posted on twitter that kind of intrigues me a little. The question was pretty straight forward. “How many virtual machines should I be able to run on a host?” That is really a fair question in itself but what I find intriguing is that this is the first question he asks. Is this really the first thing administrators think to ask when designing their environment? After all there is no set formula on how many virtual machines you can run on a host. You can be a little more exact when working with VDI because for the most part all the virtual machines would be set up pretty much the same way and the numbers can be a little more predictable. That would not be the case when working with server virtualization. You are going to have servers all with different configurations and amount of resources provisioned to the virtual machines. This variation is what will change your slot count and the amount of virtual machines you can run on the host.
Does Public or Private make a difference to Cloud Security?
When we talk about Cloud Security, the main concept is to separate, as an example, Coke from Pepsi. This implies that Tenant’s cannot impact the availability of each others data, the integrity of that data, and the confidentiality of that data. But what does this actually mean? Does this apply to all types of clouds in the same way?
There are three types of cloud families: Private, Hybrid, Public. There are at least 3 types of clouds: SaaS, PaaS, and IaaS. Do the same rules for one cloud family work for all cloud families? as well as for the types of clouds?
I believe the answer is yes.
The Effects of Virtualization on Data Center Power and Cooling
Although virtualization technologies have been a great help to data center managers looking to reclaim power in an overburdened environment, virtualization can also create problems. As IT organizations complete their server virtualization initiatives and as their virtualization management skills mature, use of the physical server power management features and dynamic workload shifting capabilities will increase. This, coupled with increased adoption of server hosted desktop virtualization, will create new opportunities for improving the efficiency of data center power and cooling systems, as well as new challenges for keeping up with increasing demand.
Sum of the Parts… Not equal to the Whole
Christofer Hoff (@Beaker) and I had a short discussion on twitter the other day about the VMware Cloud Director (vCD) security guidance. We both felt it was a bit lite and missed the point of Secure Multi Tenancy. However, I feel even more strongly that people will implement what is in the vCD Guidance, vBlock Security Guidance, and the vSphere Hardening Guidance, and in effect have a completely insecure cloud. These three guides look at the problem as if they were singular entities and not as a whole.