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.
APRIL 1, 2014 – CHEYENNE, WY – Green House Data, perhaps the greatest and greenest of cloud hosting providers, today announced a new business plan for Babysitting as a Service, or managed day care. The announcement comes alongside the creation of a new full-time position in the Network Operations Center of Red Bull Stockperson.
“I mean, the NOC is already open 24/7. We might as well toss some blocks and cots in the corner and let people leave their kids around,” said Art Salazar, data center manager. “It’s the easiest deployment we’ve ever performed. What could go wrong?”
As part of our commitment to transparency and support, Green House Data is sharing some statistics from the Network Operations Center. The NOC is home to our support team, the first responders to customer issues. The 2014 Support Report discovered several key statistics including a 12.8 minute average response time.
The data center is full of complex and intertwined roles. Each position is a part of the larger data center team. The team works to keep Green House Data running reliably, while developing our systems for future growth and implementing new products. Our team members work in a very dynamic setting which forces them to keep on their toes while applying a broad spectrum of knowledge.
We upgraded to vCloud Director v5.1 fairly recently and started receiving user tickets regarding a new issue with federation certificates. Users were sent automated e-mails reading as follows:
The federation certificate expiration is [DATE] [TIME]. An expired certificate may disable federation with the identity provider setup with your organization. The certificate can be regenerated from the Federation Settings page.
Federation certificates are set to expire after one year and warning e-mails go out a few weeks before they do. At the end of this one year cycle each certificate must be regenerated. Follow these steps to regenerate a federation certificate: