Posts Tagged 'Data Center'

August 20, 2014

SoftLayer is in Canada, eh?

Last week, we celebrated the official launch of our Toronto (TOR01) data center—the fourth new SoftLayer data center to go live in 2014, and our first in Canada! To catch you up on our progress this year, we unveiled a data center in Hong Kong in June to provide regional redundancy in Asia. In July, we added similar redundancy in Europe with the grand opening of our London data center, and we cut the ribbon on a SoftLayer data center designed specifically for federal workloads in Richardson, TX. The new Toronto location joins our data center pods in Washington, D.C., as our second location in the northeast region of North America.

As you can imagine, our development and operations teams have been working around the clock to get these new facilities built, so they were fortunate to have Tim Hortons in Toronto to keep them going. Fueled by countless double-doubles and Timbits, they officially brought TOR01 online August 11! This data center launch is part of IBM’s massive $1.2 billion commitment to in expanding our global cloud footprint. A countless number of customers have asked us when we were going to open a facility in Canada, so we prioritized Toronto to meet that demand. And because the queue had been building for so long, as soon as the doors were opened, we had a flood of new orders to fulfill. Many of these customers expressed a need for data residency in Canada to handle location-sensitive workloads, and expanding our private network into Canada means in the region will see even better network performance to SoftLayer facilities around the world.

Here are what a few of our customer had to say about the Toronto launch:

Brenda Crainic, CTO and co-founder of Maegan said, “We are very excited to see SoftLayer open a data center in Toronto, as we are now expanding our customer base in Canada. We are looking forward to host all our data in Canada, in addition to their easy-to-use services and great customer service."

Frederic Bastien, CEO at mnubo says, “We are very pleased to have a data center in Canada. Our customers value analytics performance, data residency and privacy, and deployment flexibility—and with SoftLayer we get all that and a lot more! SoftLayer is a great technology partner for our infrastructure needs.”

With our new data center, we’re able to handle Canadian infrastructure needs from A to Zed.

While we’d like to stick around and celebrate with a Molson Canadian or two, our teams are off to the next location to get it online and ready. Where will it be? You won’t have to wait very long to find out.

I’d like to welcome the new Canucks (both employees and customers) to SoftLayer. If you’re interested in getting started with a bare metal or virtual server in Canada, we’re running a limited-time launch promotion that’ll save up to $500 on your first order in Toronto: Order Now!

-John

P.S. I included a few Canadianisms in this post. If you need help deciphering them, check out this link.

March 19, 2014

An Inside Look at IBM Cloud Event 2014 in Hong Kong

On March 17 in Hong Kong, IBM and SoftLayer successfully concluded the first of many intimate cloud events. IBM Cloud Event 2014 marked the beginning of the $1.2 billion investment committed towards our global expansion plans.

Growing from 13 to 40 data centers is no mean feat, and Hong Kong is the starting point. Not only does this give our customers data redundancy in Asia-Pacific, but also provides data residency to our Hong Kong-based customers. Quite simply, we are growing where you want to grow.

For me, there were three key takeaways from the event.

We’re seeing overwhelming support from our customers.
Not only did we have an opportunity to host our Hong Kong clientele, but many also traveled from cities in Greater China to be a part of this milestone. It was immensely gratifying to see them being vocal advocates of SoftLayer services. Natali Ardianto from Tiket.com, Chris Chun from 6waves and Larry Zhang representing ePRO all shared their brilliant stories with the audience.

Tiket.com’s co-founder, Natali, is especially proud of the fact that the company sold out 6,000 tickets for the K-Pop Big Bang Alive concert in 10 minutes, while their competitor’s site was unable to meet the huge demand and shut down for four hours during the peak period. Tiket.com, founded in 2011, faced TCP, DoS and DDoS attacks and tried hosting unsuccessfully on two different IaaS providers before moving to SoftLayer’s infrastructure services in 2012.

6Waves, a gaming publisher, was started in 2008. Today, built on SoftLayer, 6waves has grown to the #1 third-party publisher on Facebook. 6waves manages 14 million monthly active users and 2 million daily active users. Chris, 6waves’ CTO and co-founder, shared that since 2009 6waves has launched more than 200 games on SoftLayer.

Larry Zhang, ePRO’s senior IT manager and architect, had a similar story to share. The B2C e-commerce platform, part of China-based DX Holdings, supports more than 200,000 items in 15 categories and saw a 66 percent increase in customers from October 2011 to September 2013. ePRO is now looking to cater to the US and Australian markets, and Larry believes that SoftLayer’s aggressive expansion plans will help them meet their goal.

SoftLayer in Hong Kong

There is a vested interest in the SoftLayer-IBM integration roadmap.
Large enterprises are moving towards the cloud. This is not a forward-looking statement, it's a fact. And from the feedback gathered and the questions put up by these organizations, it is clear that they are investing in leveraging cloud services for improving their internal processes and for bringing services to their end customers more quickly. Lance Crosby presented a SoftLayer-IBM integration roadmap. With SoftLayer forming the foundation of IBM's cloud offerings—SaaS, PaaS and BPaaS—there is no doubt that we are as invested in this partnership as our clientele.

The strong startup community in Hong Kong is committed to growing with Softlayer.
Catalyst, SoftLayer's startup incubator, has always had a strong presence in Hong Kong, and the startup spirit was evident on March 17 as well. The dedicated roundtable conducted for the community with Lance Crosby and Casey Lau, SoftLayer's Catalyst representative for APAC, was the highlight of the day. Lance left us with a powerful thought, "We are here to be an extension to your infrastructure... The question is what can you build on us."

All in all, this was a great start to our new journey!

- Namrata

August 22, 2013

Network Cabling Controversy: Zip Ties v. Hook & Loop Ties

More than 210,000 users have watched a YouTube video of our data center operations team cabling a row of server racks in San Jose. More than 95 percent of the ratings left on the video are positive, and more than 160 comments have been posted in response. To some, those numbers probably seem unbelievable, but to anyone who has ever cabled a data center rack or dealt with a poorly cabled data center rack, the time-lapse video is enthralling, and it seems to have catalyzed a healthy debate: At least a dozen comments on the video question/criticize how we organize and secure the cables on each of our server racks. It's high time we addressed this "zip ties v. hook & loop (Velcro®)" cable bundling controversy.

The most widely recognized standards for network cabling have been published by the Telecommunications Industry Association and Electronics Industries Alliance (TIA/EIA). Unfortunately, those standards don't specify the physical method to secure cables, but it's generally understood that if you tie cables too tight, the cable's geometry will be affected, possibly deforming the copper, modifying the twisted pairs or otherwise physically causing performance degradation. This understanding begs the question of whether zip ties are inherently inferior to hook & loop ties for network cabling applications.

As you might have observed in the "Cabling a Data Center Rack" video, SoftLayer uses nylon zip ties when we bundle and secure the network cables on our data center server racks. The decision to use zip ties rather than hook & loop ties was made during SoftLayer's infancy. Our team had a vision for an automated data center that wouldn't require much server/cable movement after a rack is installed, and zip ties were much stronger and more "permanent" than hook & loop ties. Zip ties allow us to tighten our cable bundles easily so those bundles are more structurally solid (and prettier). In short, zip ties were better for SoftLayer data centers than hook & loop ties.

That conclusion is contrary to the prevailing opinion in the world of networking that zip ties are evil and that hook & loop ties are among only a few acceptable materials for "good" network cabling. We hear audible gasps from some network engineers when they see those little strips of nylon bundling our Ethernet cables. We know exactly what they're thinking: Zip ties negatively impact network performance because they're easily over-tightened, and cables in zip-tied bundles are more difficult to replace. After they pick their jaws up off the floor, we debunk those myths.

The first myth (that zip ties can negatively impact network performance) is entirely valid, but its significance is much greater in theory than it is in practice. While I couldn't track down any scientific experiments that demonstrate the maximum tension a cable tie can exert on a bundle of cables before the traffic through those cables is affected, I have a good amount of empirical evidence to fall back on from SoftLayer data centers. Since 2006, SoftLayer has installed more than 400,000 patch cables in data centers around the world (using zip ties), and we've *never* encountered a fault in a network cable that was the result of a zip tie being over-tightened ... And we're not shy about tightening those ties.

The fact that nylon zip ties are cheaper than most (all?) of the other more "acceptable" options is a fringe benefit. By securing our cable bundles tightly, we keep our server racks clean and uniform:

SoftLayer Cabling

The second myth (that cables in zip-tied bundles are more difficult to replace) is also somewhat flawed when it comes to SoftLayer's use case. Every rack is pre-wired to deliver five Ethernet cables — two public, two private and one out-of-band management — to each "rack U," which provides enough connections to support a full rack of 1U servers. If larger servers are installed in a rack, we won't need all of the network cables wired to the rack, but if those servers are ever replaced with smaller servers, we don't have to re-run network cabling. Network cables aren't exposed to the tension, pressure or environmental changes of being moved around (even when servers are moved), so external forces don't cause much wear. The most common physical "failures" of network cables are typically associated with RJ45 jack crimp issues, and those RJ45 ends are easily replaced.

Let's say a cable does need to be replaced, though. Servers in SoftLayer data centers have redundant public and private network connections, but in this theoretical example, we'll assume network traffic can only travel over one network connection and a data center technician has to physically replace the cable connecting the server to the network switch. With all of those zip ties around those cable bundles, how long do you think it would take to bring that connection back online? (Hint: That's kind of a trick question.) See for yourself:

The answer in practice is "less than one minute" ... The "trick" in that trick question is that the zip ties around the cable bundles are irrelevant when it comes to physically replacing a network connection. Data center technicians use temporary cables to make a direct server-to-switch connection, and they schedule an appropriate time to perform a permanent replacement (which actually involves removing and replacing zip ties). In the video above, we show a temporary cable being installed in about 45 seconds, and we also demonstrate the process of creating, installing and bundling a permanent network cable replacement. Even with all of those villainous zip ties, everything is done in less than 18 minutes.

Many of the comments on YouTube bemoan the idea of having to replace a single cable in one of these zip-tied bundles, but as you can see, the process isn't very laborious, and it doesn't vary significantly from the amount of time it would take to perform the same maintenance with a Velcro®-secured cable bundle.

Zip ties are inferior to hook & loop ties for network cabling? Myth(s): Busted.

-@khazard

P.S. Shout-out to Elijah Fleites at DAL05 for expertly replacing the network cable on an internal server for the purposes of this video!

July 29, 2013

A Brief History of Cloud Computing

Believe it or not, "cloud computing" concepts date back to the 1950s when large-scale mainframes were made available to schools and corporations. The mainframe's colossal hardware infrastructure was installed in what could literally be called a "server room" (since the room would generally only be able to hold a single mainframe), and multiple users were able to access the mainframe via "dumb terminals" – stations whose sole function was to facilitate access to the mainframes. Due to the cost of buying and maintaining mainframes, an organization wouldn't be able to afford a mainframe for each user, so it became practice to allow multiple users to share access to the same data storage layer and CPU power from any station. By enabling shared mainframe access, an organization would get a better return on its investment in this sophisticated piece of technology.

Mainframe Computer

A couple decades later in the 1970s, IBM released an operating system called VM that allowed admins on their System/370 mainframe systems to have multiple virtual systems, or "Virtual Machines" (VMs) on a single physical node. The VM operating system took the 1950s application of shared access of a mainframe to the next level by allowing multiple distinct compute environments to live in the same physical environment. Most of the basic functions of any virtualization software that you see nowadays can be traced back to this early VM OS: Every VM could run custom operating systems or guest operating systems that had their "own" memory, CPU, and hard drives along with CD-ROMs, keyboards and networking, despite the fact that all of those resources would be shared. "Virtualization" became a technology driver, and it became a huge catalyst for some of the biggest evolutions in communications and computing.

Mainframe Computer

In the 1990s, telecommunications companies that had historically only offered single dedicated point–to-point data connections started offering virtualized private network connections with the same service quality as their dedicated services at a reduced cost. Rather than building out physical infrastructure to allow for more users to have their own connections, telco companies were able to provide users with shared access to the same physical infrastructure. This change allowed the telcos to shift traffic as necessary to allow for better network balance and more control over bandwidth usage. Meanwhile, virtualization for PC-based systems started in earnest, and as the Internet became more accessible, the next logical step was to take virtualization online.

If you were in the market to buy servers ten or twenty years ago, you know that the costs of physical hardware, while not at the same level as the mainframes of the 1950s, were pretty outrageous. As more and more people expressed demand to get online, the costs had to come out of the stratosphere, and one of the ways that was made possible was by ... you guessed it ... virtualization. Servers were virtualized into shared hosting environments, Virtual Private Servers, and Virtual Dedicated Servers using the same types of functionality provided by the VM OS in the 1950s. As an example of what that looked like in practice, let's say your company required 13 physical systems to run your sites and applications. With virtualization, you can take those 13 distinct systems and split them up between two physical nodes. Obviously, this kind of environment saves on infrastructure costs and minimizes the amount of actual hardware you would need to meet your company's needs.

Virtualization

As the costs of server hardware slowly came down, more users were able to purchase their own dedicated servers, and they started running into a different kind of problem: One server isn't enough to provide the resources I need. The market shifted from a belief that "these servers are expensive, let's split them up" to "these servers are cheap, let's figure out how to combine them." Because of that shift, the most basic understanding of "cloud computing" was born online. By installing and configuring a piece of software called a hypervisor across multiple physical nodes, a system would present all of the environment's resources as though those resources were in a single physical node. To help visualize that environment, technologists used terms like "utility computing" and "cloud computing" since the sum of the parts seemed to become a nebulous blob of computing resources that you could then segment out as needed (like telcos did in the 90s). In these cloud computing environments, it became easy add resources to the "cloud": Just add another server to the rack and configure it to become part of the bigger system.

Clouds

As technologies and hypervisors got better at reliably sharing and delivering resources, many enterprising companies decided to start carving up the bigger environment to make the cloud's benefits to users who don't happen to have an abundance of physical servers available to create their own cloud computing infrastructure. Those users could order "cloud computing instances" (also known as "cloud servers") by ordering the resources they need from the larger pool of available cloud resources, and because the servers are already online, the process of "powering up" a new instance or server is almost instantaneous. Because little overhead is involved for the owner of the cloud computing environment when a new instance is ordered or cancelled (since it's all handled by the cloud's software), management of the environment is much easier. Most companies today operate with this idea of "the cloud" as the current definition, but SoftLayer isn't "most companies."

SoftLayer took the idea of a cloud computing environment and pulled it back one more step: Instead of installing software on a cluster of machines to allow for users to grab pieces, we built a platform that could automate all of the manual aspects of bringing a server online without a hypervisor on the server. We call this platform "IMS." What hypervisors and virtualization do for a group of servers, IMS does for an entire data center. As a result, you can order a bare metal server with all of the resources you need and without any unnecessary software installed, and that server will be delivered to you in a matter of hours. Without a hypervisor layer between your operating system and the bare metal hardware, your servers perform better. Because we automate almost everything in our data centers, you're able to spin up load balancers and firewalls and storage devices on demand and turn them off when you're done with them. Other providers have cloud-enabled servers. We have cloud-enabled data centers.

SoftLayer Pod

IBM and SoftLayer are leading the drive toward wider adoption of innovative cloud services, and we have ambitious goals for the future. If you think we've come a long way from the mainframes of the 1950s, you ain't seen nothin' yet.

-James

Categories: 
February 8, 2013

Data Center Power-Up: Installing a 2-Megawatt Generator

When I was a kid, my living room often served as a "job site" where I managed a fleet of construction vehicles. Scaled-down versions of cranes, dump trucks, bulldozers and tractor-trailers littered the floor, and I oversaw the construction (and subsequent destruction) of some pretty monumental projects. Fast-forward a few years (or decades), and not much has changed except that the "heavy machinery" has gotten a lot heavier, and I'm a lot less inclined to "destruct." As SoftLayer's vice president of facilities, part of my job is to coordinate the early logistics of our data center expansions, and as it turns out, that responsibility often involves overseeing some of the big rigs that my parents tripped over in my youth.

The video below documents the installation of a new Cummins two-megawatt diesel generator for a pod in our DAL05 data center. You see the crane prepare for the work by installing counter-balance weights, and work starts with the team placing a utility transformer on its pad outside our generator yard. A truck pulls up with the generator base in tow, and you watch the base get positioned and lowered into place. The base looks so large because it also serves as the generator's 4,000 gallon "belly" fuel tank. After the base is installed, the generator is trucked in, and it is delicately picked up, moved, lined up and lowered onto its base. The last step you see is the generator housing being installed over the generator to protect it from the elements. At this point, the actual "installation" is far from over — we need to hook everything up and test it — but those steps don't involve the nostalgia-inducing heavy machinery you probably came to this post to see:

When we talk about the "megawatt" capacity of a generator, we're talking about the bandwidth of power available for use when the generator is operating at full capacity. One megawatt is one million watts, so a two-megawatts generator could power 20,000 100-watt light bulbs at the same time. This power can be sustained for as long as the generator has fuel, and we have service level agreements to keep us at the front of the line to get more fuel when we need it. Here are a few other interesting use-cases that could be powered by a two-megawatt generator:

  • 1,000 Average Homes During Mild Weather
  • 400 Homes During Extreme Weather
  • 20 Fast Food Restaurants
  • 3 Large Retail Stores
  • 2.5 Grocery Stores
  • A SoftLayer Data Center Pod Full of Servers (Most Important Example!)

Every SoftLayer facility has an n+1 power architecture. If we need three generators to provide power for three data center pods in one location, we'll install four. This additional capacity allows us to balance the load on generators when they're in use, and we can take individual generators offline for maintenance without jeopardizing our ability to support the power load for all of the facility's data center pods.

Those of you who are in the fondly remember Tonka trucks and CAT crane toys are the true target audience for this post, but even if you weren't big into construction toys when you were growing up, you'll probably still appreciate the work we put into safeguarding our facilities from a power perspective. You don't often see the "outside the data center" work that goes into putting a new SoftLayer data center pod online, so I thought it'd give you a glimpse. Are there an topics from an operations or facilities perspectives that you also want to see?

-Robert

July 27, 2012

SoftLayer 'Cribs' ≡ DAL05 Data Center Tour

The highlight of any customer visit to a SoftLayer office is always the data center tour. The infrastructure in our data centers is the hardware platform on which many of our customers build and run their entire businesses, so it's not surprising that they'd want a first-hand look at what's happening inside the DC. Without exception, visitors to a SoftLayer data center pod are impressed when they walk out of a SoftLayer data center pod ... even if they've been in dozens of similar facilities in the past.

What about the customers who aren't able to visit us, though? We can post pictures, share stats, describe our architecture and show you diagrams of our facilities, but those mediums can't replace the experience of an actual data center tour. In the interest of bridging the "data center tour" gap for customers who might not be able to visit SoftLayer in person (or who want to show off their infrastructure), we decided to record a video data center tour.

If you've seen "professional" video data center tours in the past, you're probably positioning a pillow on top of your keyboard right now to protect your face if you fall asleep from boredom when you hear another baritone narrator voiceover and see CAD mock-ups of another "enterprise class" facility. Don't worry ... That's not how we roll:

Josh Daley — whose role as site manager of DAL05 made him the ideal tour guide — did a fantastic job, and I'm looking forward to feedback from our customers about whether this data center tour style is helpful and/or entertaining.

If you want to see more videos like this one, "Like" it, leave comments with ideas and questions, and share it wherever you share things (Facebook, Twitter, your refrigerator, etc.).

-@khazard

July 19, 2012

The Human Element of SoftLayer - DAL05 DC Operations

One of the founding principles of SoftLayer is automation. Automation has enabled this company to provide our customers with a world class experience, and it enables employees to provide excellent service. It allows us to quickly deploy a variety of solutions at the click of a button, and it guarantees consistency in the products that we deliver. Automation isn't the whole story, though. The human element plays a huge role in SoftLayer's success.

As a Site Manager for the corporate facility, I thought I could share a unique perspective when it comes to what that human element looks like, specifically through the lens of the Server Build Team's responsibilities. You recently heard how my colleague, Broc Chalker, became an SBT, and so I wanted take it a step further by providing a high-level breakdown of how the Server Build Team enables SoftLayer to keep up with the operational demands of a rapidly growing, global infrastructure provider.

The Server Build Team is responsible for filling all of the beautiful data center environments you see in pictures and videos of SoftLayer facilities. Every day, they are in the DC, building out new rows for inventory. It sounds pretty simple, but it's actually a pretty involved process. When it comes to prepping new rows, our primary focus is redundancy (for power, cooling and network). Each rack is powered by dual power sources, four switches in a stacked configuration (two public network, two private network), and an additional switch that provides KVM access to the server. To make it possible to fill the rack with servers, we also have to make sure it's organized well, and that takes a lot of time. Just watch the video of the Go Live Crew cabling a server rack in SJC01, and you can see how time- and labor-intensive the process is. And if there are any mistakes or if the cables don't look clean, we'll cut all the ties and start over again.



 

In addition to preparing servers for new orders, SBTs also handle hardware-related requests. This can involve anything from changing out components for a build, performing upgrades / maintenance on active servers, or even troubleshooting servers. Any one of these requests has to be treated with significant urgency and detail.



 

The responsibilities do not end there. Server Build Technicians also perform a walk of the facility twice per shift. During this walk, technicians check for visual alerts on the servers and do a general facility check of all SoftLayer pods. Note: Each data center facility features one or more pods or "server rooms," each built to the same specifications to support up to 5,000 servers.



 

The DAL05 facility has a total of four pods, and at the end of the build-out, we should be running 18,000-20,000 servers in this facility alone. Over the past year, we completed the build out of SR02 and SR03 (pod 2 and 3, respectively), and we're finishing the final pod (SR04) right now. We've spent countless hours building servers and monitoring operating system provisions when new orders roll in, and as our server count increases, our team has grown to continue providing the support our existing customers expect and deserve when it comes to upgrade requests and hardware-related support tickets.



 

To be successful, we have to stay ahead of the game from an operations perspective. The DAL05 crew is working hard to build out this facility's last pod (SR04), but for the sake of this blog post, I pulled everyone together for a quick photo op to introduce you to the team.

DAL05 Day / Evening Team and SBT Interns (with the remaining racks to build out in DAL05):
DAL05 DC Ops

DAL05 Overnight Server Build Technician Team:
DAL05 DC Ops

Let us know if there's ever anything we can do to help you!

-Joshua

July 13, 2012

When Opportunity Knocks

I've been working in the web hosting industry for nearly five years now, and as is the case with many of the professionals of my generation, I grew up side by side with the capital-I Internet. Over those five years, the World Wide Web has evolved significantly, and it's become a need. People need the Internet to communicate, store information, enable societal connectivity and entertain. And they need it 24 hours per day, seven days a week. To affirm that observation, you just need to look at an excerpt from a motion submitted to the Human Rights Council and recently passed by the United Nations General Assembly:

The General Session ... calls upon all States to promote and facilitate access to the Internet and international cooperation aimed at the development of media and information and communications facilities in all countries.

After a platform like the Internet revolutionizes the way we see the world, it's culturally impossible to move backward. Its success actually inspires us to look forward for the next world-changing innovation. Even the most non-technical citizen of the Internet has come to expect those kinds of innovations as the Internet and its underlying architecture have matured and seem to be growing like Moore's Law: Getting faster, better, and bigger all the time. The fact that SoftLayer is able to keep up with that growth (and even continue innovating in the process) is one of the things I admire most about the company.

I love that our very business model relies on our ability to enable our customers' success. Just look at how unbelievably successful companies like Tumblr and HostGator have become, and you start to grasp how big of a deal it is that we can help their businesses. We're talking billions of pageviews per month and hundreds of thousands of businesses that rely on SoftLayer through our customers. And that's just through two customers. Because we're on the cutting edge, and we provide unparalleled access and functionality, we get to see a lot of the up-and-coming kickstarts that are soon to hit it big, and we get to help them keep up with their own success.

On a personal level, I love that SoftLayer provides opportunities for employees. Almost every department has a career track you can follow as you learn more about the business and get a little more experience, and you're even able to transition into another department if you're drawn to a new passion. I recently move to the misty northwest (Seattle) when given the opportunity by SoftLayer, and after working in the data center, I decided to pursue a role as a systems administrator. It took a lot of hard work, but I made the move. Hard work is recognized, and every opportunity I've taken advantage of has been fulfilled. You probably think I'm biased because I've done well in the organization, and that might be a fair observation, but in reality, the opportunities don't just end with me.

One of my favorite stories to share about SoftLayer is the career path of my best friend, Goran. I knew he was a hard worker, so I referred him to the company a few years ago, and he immediately excelled as an Operations Tech. He proved himself on the Go-Live Crew in Amsterdam by playing a big role in the construction of AMS01, and he was promoted to a management position in that facility. He had been missing Europe for the better part of a decade, SoftLayer gave him a way to go back home while doing what he loves (and what he's good at).

If that Goran's story isn't enough for you, I could tell you about Robert. He started at SoftLayer as a data center tech, and he worked hard to become a systems administrator, then he was named a site manager, then he was promoted to senior operations manager, and now he's the Director of Operations. You'll recognize him as the guy with all of the shirts in Lance's "Earn Your Bars" blog post from December. He took every rung on the ladder hand-over-hand because no challenge could overwhelm him. He sought out what needed to be done without being asked, and he was proactive about make SoftLayer even better.

I could tell you about dozens of others in the company that have the same kinds of success stories because they approached the opportunities SoftLayer provided them with a passion and positive attitude that can't be faked. If being successful in an organization makes you biased, we're all biased. We love this environment. We're presented with opportunities and surrounded by people encouraging us to take advantage of those opportunities, and as a result, we can challenge ourselves and reach our potential. No good idea is ignored, and no hard work goes unrecognized.

I'm struggling to suppress the countless "opportunity" stories I've seen in my tenure at SoftLayer, but I think the three stories above provide a great cross-section of what it looks like to work for SoftLayer. If you like being challenged (and being rewarded for your hard work), you might want to take this opportunity to see which SoftLayer Career could be waiting for you.

When opportunity knocks, let it in.

-Hilary

Categories: 
July 12, 2012

An Insider's Look at SoftLayer's Growth in Amsterdam

Last week, SoftLayer was featured on the NOS national news here in the Netherlands in a segment that allowed us to tell our story and share how we're settling into our new Amsterdam home. I've only been a SLayer for about nine months now, and as I watched the video, I started to reflect on how far we've come in such a surprisingly short time. Take a second to check it out (don't worry, it's not all in Dutch):

To say that I had to "hit the ground running" when I started at SoftLayer would be an understatement. The day after I got the job, I was on a plane to SoftLayer's Dallas headquarters to meet the team behind the company. To be honest, it was a pretty daunting task, but I was energized at the opportunity to learn about how SoftLayer became largest privately owned hosting company in the world from the people who started it. When I look back at the interview Kevin recorded with me, I'm surprised that I didn't look like a deer in the headlights. At the time, AMS01 was still in the build-out phase, so my tours and meetings in DAL05 were both informative and awe-inspiring.

When I returned to Europe, I was energized to start playing my role in the company's new pursuit of its global goals.

It didn't take long before I started seeing the same awe-inspiring environment take place in our Amsterdam facility ... So much so that I'm convinced that at least a few of the "Go Live Crew" members were superhuman. As it turns out, when you build identical data center pods in every location around the world, you optimize the process and figure out the best ways to efficiently use your time.

By the time the Go Live Crew started packing following the successful (and on-time) launch of AMS01, I started feeling the pressure. The first rows of server racks were already being filled by customers, but the massive data center space seemed impossibly large when I started thinking of how quickly we could fill it. Most of my contacts in Europe were not familiar with the SoftLayer name, and because my assigned region was Europe Middle East and Africa — a HUGE diverse region with many languages, cultures and currencies — I knew I had my work cut out for me.

I thought, "LET'S DO THIS!"

EMEA is home to some of the biggest hosting markets in the world, so my first-week whirlwind tour of Dallas actually set the stage quite nicely for what I'd be doing in the following months: Racking up air miles, jumping onto trains, attending countless trade shows, meeting with press, reaching out to developer communities and corresponding with my fellow SLayers in the US and Asia ... All while managing the day-to-day operations of the Amsterdam office. As I look back at that list, I'm amazed how the team came together to make sure everything got done.

We have come a long way.

As I started writing this blog, BusinessReview Europe published a fantastic piece on SoftLayer in their July 2012 magazine (starting on page 172) that seems to succinctly summarize how we've gotten where we are today: "Innovation Never Sleeps."

BusinessReview Europe

Our first pod is almost full of servers humming and flashing. When we go to tradeshows and conferences throughout Europe, people not only know SoftLayer, many of them are customers with servers in AMS01. That's the kind of change we love.

The best part of my job right now is that our phenomenal success in the past nine months is just a glimmer of what the future holds. Come to think of it, we're going to need some more people.

-@jpwisler

June 19, 2012

Proud to be a SLayer

Changing a career can be a challenge, especially when it feels like you are starting from scratch. I know that feeling well. I'd always been interested in networking, IT and cloud computing, but it wasn't until I joined SoftLayer that had an opportunity to start building a career on top of those interests. I know you might've already read a few introductions and SoftLayer culture posts in the past, but I wanted to share my experience in joining the hardware tech team to give my own unique perspective on what it was like becoming a SLayer.

Like Jonathan, I joined SoftLayer in San Jose (SJC01), and despite my interest in the technology SoftLayer manages for customers on a day-to-day basis, I didn't have many of the skills I'd need in the data center. That's where the training program came into play ... I can't tell you how valuable it was to learn how SoftLayer approaches cloud and data center operations. My previous jobs were in manufacturing, so I was accustomed to working with hardware and machines, so after a bit of a learning curve, I started to feel comfortable with the instruction and hands-on challenges that were put in front of me during the training program.

Once I was able to start applying what I learned in training, I started feeling "at home" when I got to the data center. I'm one of the many people responsible for supporting data center operations, and while I'm more of a "hands on" person, I don't forget the "big picture" of the significance of that responsibility. SoftLayer servers are the lifeblood of businesses around the world, and I owe it to those customers to provide the best service I can when it comes to managing their hardware. If that starts feeling daunting, I can look to my peers and ask questions about any problem, and I know I'll get a quick, helpful answer. I know SoftLayer is built on innovation and automation, but the unstated "education" piece is what has appealed to me the most as an employee.

One of my favorite resources to consult on a daily basis is the SoftLayer wiki — SLiki. If I ever forget any technical specifications or get confused about how to configure a specific type of hardware, I fire up my browser and hit the SLiki. If I'm not sure how to troubleshoot a given transaction or want to learn a little more about a topic like cloud computing or object storage, I can search the SLiki and get the answer in no time.

When friends and family have asked me what it's like to work at SoftLayer, I tell them that I'm constantly amazed and impressed impressed by my coworkers. It's hard to explain in a way that doesn't sound corny, but everyone I work with seems to enjoy supporting customers, interacting with other SLayers and making the SJC01 data center run like a top.

Pretty recently, I had my first Truck Day, and it made me love working for SoftLayer even more. It was pretty awe-inspiring to see SLayers from every department in our office joining the SBTs at the loading dock to unpack, sort and rack a huge shipment of SuperMicro servers. Everyone was sweaty, and I'm sure a few people were pretty sore the next day, but after all was said and done, we all felt like we'd accomplished something significant for our customers.

I'm proud to be a SLayer.

-Cuong

Subscribe to data-center