To view the original article click here- https://www.thewhir.com/web-hosting-news/web-host-hivelocity-building-out-phase-2-of-tampa-data-center
Web hosting provider Hivelocity announced on Thursday that it will expand its Tampa, Florida data center and headquarters, adding 7,000 square feet with the phase-two buildout that will begin in September and is expected to conclude in the first quarter of 2013.
The phase two construction will adjoin the company’s existing Tampa headquarters, as well as the data center facility on the site, adding data center space for approximately 4,000 Hivelocity-managed servers, as well as cage space for colocation customers.
Hivelocity provides a combination of colocation space, along with VPS hosting, cloud hosting and dedicated servers, making its facilities a multi-tenant and multi-use space.
In July, Hivelocity launched SparkNode, a site built specifically to promote its cloud hosting and virtualization solutions.
And earlier, in June, Hivelocity added new server configurations with Ivy Bridge E3, Sandy Bridge E5 and Westmere E7 systems.
According to the announcement, Hivelocity will also use the new space to build out a new NOC, along with new lab space for colocation customers, as well as a customer lounge.
Hivelocity says it anticipated the need for the new capacity two years ago, and at the time had surplus infrastructure and assets installed that would support the current expansion.
“A good portion of our phase two data center space will be purposed for colocation clientele,” says general manager Steve Eschweiler, quoted in the press release. “We have a blank canvas right now so this is a great opportunity to make this space a place our colocated customers can hang out, take a load off and really be comfortable and productive during the days they have to work on-site for extended periods of time. Colocated customers will have cages for their gear, lab space for their work and a lounge when they need a break.”
Latest Update Impacting Some RHEL / CentOS Servers ——————————————————————————— NOTE: This issue should now be resolved. A couple weeks ago Redhat released a set of patches which now seem to fix the issue, we are also getting confirmed reports that the fix from Redhat does resolve this. The ultimate cause …