Grounded in the Cloud
Showing results for 
Search instead for 
Did you mean: 

Cool things to do with an HP CloudSystem


HP CloudSystem is a pre-integrated, pre-tested hardware/software system for creating clouds. What can you do with one?


For the Applications Department

  1. Get the “why don’t we just use Amazon?” people off your back - create an internal “Infrastructure as a service”  (you can do this using CloudSystem/Matrix. But if you ever plan to add other services like those listed below, best go for CloudSystem/Enterprise because this is what you’ll need for offering applications are part of your “cloud products”)
  2. Go one stage further and offer “development environments as a service” - i.e. stand-up a server/storage/network, but also the development tools the developers need  (You’ll need CloudSystem/Enterprise for this because it deploys middleware and applications)
  3. Offer “testing environment as a service” - stand-up the virtual machine and the testing tools you need to do testing  (You’ll need CloudSystem/Enterprise for this because it deploys middleware and applications)
  4. Offer “test systems as a service” - create a catalog entry for each of the systems you need to test against. E.g. an SAP system or a DB system with an application in it. Watch this space for more help in doing this from HP’s ALM products  (You’ll need CloudSytem/Enterprise for this because you’re deploying applications)

For the Operations Department

  1. Offer server/storage/network - i.e. production IaaS systems (You could do this with CloudSystem/Matrix. However, if you want to link the production systems into, for example, your change management system, then you may want our orchestration systems to do that automatically for you. For this, you’ll need the CloudSystem/Enterprise. Also, if you ever plan to offer more than simply IaaS [e.g. include middleware], CloudSystem/Enterprise is what you need)
  2. Offer internal, production, platform as a service - server/storate/network plus middleware like App Server (e.g. LAMP stack) and database. (You’ll need CloudSystem/Enterprise for this)
  3. Add the ability to automatically move code from test to production. You may or may not have this as a catalog entry, but it’s something your CloudSystem/Enterprise system can automate for you. So why not? - if you’ve got an internal PaaS, why not go the next stage and support the Agile development process and automate the movement of the code into production.
  4. Icing on the cake : for each of your deployed systems, “plumb them into the data center”. Link them into the compliance scanning and remediation systems. Link them into the security monitoring systems. Link them into the control management systems. And get them under availability and performance management. Some of these happen automatically (like getting the service under availability and performance management). But others have either to be done manually (not good - slow, people intensive and error prone) or thru CloudSystem/Enterprise’s orchestration capability. Needless to say, plumbing-in production systems using CloudSytem/Enterprise’s orchestration is the best approach.

For a Service Provider

  1. Simply offering infrastructure as a service. (CloudSystem/Matrix may be enough for you. If you want to get sophisticated, then consider CloudSystem/Service Provider)
  2. However, you almost certainly are using IaaS as a starting point - who wants to compete directly with EC2 (actually EC2 offers a lot more than IaaS now)?  You’ll probably want to add platforms and applications like email and sharepoint as services. And you’ll probably want to do more than just stand-up platforms and applications. Once an application is up, you’ll get requests to add users, delete users, change users’ capabilities, and so on. While these requests are not strictly cloud, they ARE important and as a service provider, you will need to handle them, automatically if possible. CloudSystem/Enterprise has the orchestration capabilities you need for this. If you want to get sophisticated, CloudSystem/Service Provider can also be used.
  3. Full-on SaaS provider. What we’re talking about here is someone whose main business is developing an application and offering it as a SaaS service. This market will go from $27b next year to $250b by the end of the century, according to Gartner. That’s a huge growth. CloudSystem helps here - you obviously stand up the capacity you need to run your SaaS. But you can also use the automation in CloudSystem/Enterprise to move your application from test into production. And, all the things we talked about above for the application department apply to a SaaS provider - cloud-provided dev environments (“internal DaaS”), cloud-provide test environments (“internal TaaS”) and test systems. You will need CloudSystem/Enterprise for this because you’ll be deploying middleware, databases and applications.


Mike Shaw
Director Strategic Marketing

linkedin.gifMike Shaw

0 Kudos
About the Author


Mike has been with HPE for 30 years. Half of that time was in research and development, mainly as an architect. The other 15 years has been spent in product management, product marketing, and now, strategic marketing. .


>>This market will go from $27b next year to $250b by the end of the century, according to Gartner


I wish I had their cystal balls.  Either that's a typo, or somebody in Gartner has a Messiah complex.  How many readers beliee that Gartner's prediction of what he world will be like in 88 years time will stand up to scrutiny?!

Jan 30-31, 2018
Expert Days - 2018
Visit this forum and get the schedules for online HPE Expert Days where you can talk to HPE product experts, R&D and support team members and get answ...
Read more
See posts for dates
HPE Webinars - 2018
Find out about this year's live broadcasts and on-demand webinars.
Read more
View all