Data center containment is the practice of splitting the aisles of a data center into segregated hot and cold sections, depending on how each aisle is set up. For example, some data centers might have the front of their servers on the inside of the aisle, with fans blowing the exhaust outside the aisle. Others might have the front of their servers on the outside of the aisle, and vent heat inside the aisle.
Containment keeps the hot air exiting servers from mixing with the cold air coming in from the Computer Room Air Conditioning (CRAC), dramatically improving energy efficiency and also maintaining a more consistent temperature, which reduces the overall load on both air conditioning units and the servers themselves.
Green House Data uses full containment in our Cheyenne and East Coast data centers, but only recently implemented it in our Seattle, WA facility. This case study demonstrates how even a simple containment system can lead to significant energy efficiency improvements. We expect the system to pay for itself within the year, in part thanks to generous rebates from Seattle Public Utilities.
Our cloud engineering team wears many hats, with different roles taking on different pieces of the nationwide gBlock™ Cloud falling to different staff members, but everyone pulling their weight on a wide variety of projects simultaneously.
Our new blog series digs into the daily life of our technology staff, focusing on their challenges, routines, and goals, to provide insight for those who are eying the IT field, or customers and friends who may be curious what goes on behind the scenes at a cloud data center.
This week, we talk to Senior Cloud Technologist Josh Larsen, who has moved around in different roles for Green House Data for over six years. As Cloud Technologist, his job largely entails forecasting and planning for large-scale cloud projects across our entire environment.
The B Corp movement continues to grow and spread throughout the world, with more and more companies of all sizes and industries looking towards B Corp Certification as a guide towards sustainability, positive relationships with employees and stakeholders, community involvement, and overall impact.
Green House Data is proud to announce that our recertification last year placed us among the Best for the World: Changemakers list, which honors organizations that significantly improved their B Impact certification rating.
You did it — you passed your PCI (or SOX, HIPAA, GLB, etc) audit! But the work isn’t over. A recent Verizon study found that most companies fall out of PCI compliance after just nine months. And it doesn’t stop with PCI, either. Many companies work hard around audit time to ensure they can report compliance for the audit period and advertise their security, only to falter once the audit is complete.
For PCI, that also means being able to continue doing business with credit card companies. For other standards like HIPAA and SOX, it means avoiding hefty fines and legal consequences.
Unfortunately, simply checking the compliance boxes doesn’t mean you’re safe for the foreseeable future. You need to maintain compliance at all times throughout the year, not just when the auditors are knocking on your door.
It seems like every week some piece of your stack has a security advisory or a new version. While only the critical vulnerabilities or bugs might need immediate installation, inevitably you’ll be juggling dozens of versions, trying to decide which system requires a update and which you’ve already patched.
There are a few official and unofficial places to keep you in the loop on software lifecycle management, and by regularly using them in addition to your own tracking tools or spreadsheets, you can keep your IT environment safe and up-to-date.