There are myriad ways to bill colocation customers, making a comparison between multiple bids an occasionally daunting process. The industry does seem to be shifting towards an accepted standard billing model based on metered electricity use, but older billing methods based on footprint and telecom connections are still in play.
This can make it difficult to compare bids based on different models. What are the distinctions in colocation pricing models and what is the fairest method for customers and providers alike?
Happy Earth Day! As we reflect on environmental impact, let’s take a look at some solid data to see how much energy and carbon dioxide emissions are really saved by data center energy efficiency and renewable energy use. The recent memo from the Greed Grid reintroducing their metrics for data center efficiency provides a great jumping off point to estimate the environmental impact of an average data center.
With recent headlines like Apple’s shift towards renewables and Google’s funding of wind farms, not to mention our own efforts at Green House Data to improve efficiency and overall Power Usage Effectiveness (PUE), many in the data center industry are curious about the actual data at hand. If a company improves 2% of its overall carbon footprint through efficient or renewably powered data centers, what does that actually mean? Is it a large impact or just a PR opportunity?
We took a theoretical 10 MW facility and assumed it was operating at capacity for simplicity of math and comparison. We measured this facility’s emissions at 1.8 and 1.2 PUE to see how improving operations and data center location would each affect emissions.
What is Heartbleed?
This vulnerability takes advantage of a memory configuration within the ever-popular OpenSSL software library. The TLS heartbeat extension (RFC 6520) on an exploited version of OpenSSL allows an attacker to view up to 64k of what is in memory with each “heartbeat.” Thus, a multitude of information can be obtained unnoticed. It is important to note that this exploit is found in OpenSSL's implementation of SSL/TLS, not within the TLS protocol itself.
How does this affect Green House Data's services?
We are actively pursuing efforts to mitigate any presence of vulnerable systems within Green House Data's cloud infrastructure. From what we have seen so far, these efforts are primarily focused on systems using OpenSSL to encrypt TLS connections. Green House Data provides service and customer portals that use SSL and have taken the necessary actions to secure our systems.
What steps can be taken to fix this?
Datacenter Dynamics reports that the Telecommunications Industry Association (TIA) will remove “tiers” from its data center benchmarking system. We've previously explained the differences between TIA and the Uptime Institute data center tier benchmarks here on the blog—they mainly differ in the requirement of raised floors. The article also explains that the Uptime Institute and TIA will work together to establish a unified front for data center ratings.
You signed the SOA, logged in to your cloud provider web portal, and spun up some servers. You’re ready to get to work, but one thing is missing: the apps! Raw infrastructure is all well and good, but without software running in the cloud, you’re not going to get much work done. The days when companies could buy a single license or the rights to 200-odd users and use that software for life are disappearing quickly.
When assessing software licenses for the cloud, make sure to evaluate how many users will access the software and how many physical and virtual processors might be involved. Here are the top factors to consider for software licensing in the cloud.