“The UberCloud Experiment is a unique model to break the barrier to High Performance Computing in the cloud. It pools all resources required for us to get a hand on HPC in the cloud to solve our real-world problem. The experiment provides us with valuable information for our HPC decision-making.” . . . . . . . . Frank Ding, PhD, Simulation & Computing Manager, Simpson Strong-Tie
“Today, a single engineer has tremendous computing power available. I created a virtual prototype of the valve and ran mechanical simulations in my computer workstation. Collaborating with Autodesk and the UberCloud Experiment, I ran more than 200 flow simulations in the cloud to ensure the design met performance goals. This development path did not exist five years ago.” . . . . . . . . Mark A. Lobo, P.E. – Principal, Lobo Engineering PLC.
UberCloud is best known for the UberCloud Experiment, the free, community driven effort that explores the end-to-end processes of accessing and using remote computing resources in High Performance Computing (HPC) centers and tech computing clouds, on demand. Participants of the experiment get hands on experience on using remote computing resources for their own projects; in the process learning how to cope with the challenges and resolving many of the common roadblocks. The project teams working on the end-users applications discuss their experience, the hurdles they ran into, their lessons learned, and the best practices, on the UberCloud community web site.
The UberCloud Experiment was started in July 2012, and since then has grown to over 2000 organizations and individuals from more than 70 countries. More than 150 teams have been formed since then and many of these teams are covered on the UberCloud community web site. UberCloud Experiment offers free trials for up to 1,000 CPU core hours. We have the experience of having handled over 150 such projects.
Read UberCloud Experiment team reports from areas such as aerodynamics, fluid flow, multi-physics, finite element analysis, computational chemistry, and life sciences, and participate in forums and discussions.
After 6 rounds with 155 team experiments we have collected a few must-read recommendations on how to perform a successful experiment, and how to avoid some severe pitfalls. You as a participant want to follow this etiquette, to appreciate the precious time of your fellow team members and move your experiment forward quickly.
1. Consider that this is just an experiment, and not a production project. Nobody wants free experiments to compete with commercial service providers and thus jeopardize their business.
2. As the end-user in your team, select an application example which you know is manageable within a 4-6 weeks long experiment project.
3. Select a 6-8 week time window for your experiment where you know you will be able to spend at least 2-4 hours per week on average on this experiment.
4. Prepare for the experiment by defining the main goals and describing the needed hardware, software and expertise.
5. Once your experiment project is launched, you must complete the required team documents on the UberCloud Basecamp collaboration platform (Project Definition, Key Contacts, Computing Resources, and Software Resources).
6. All preparatory work such as testing of geometry meshes, boundary and initial conditions, physical parameters, etc., should be done on your in-house system. Only when the test problem runs smoothly on your system it should be moved to a remote system for larger runs with more resources (up to a max of 1000 cpu core hours).
7. While thinking about the set-up of the experiment, also start thinking about your next steps. What comes after the experiment if it concludes successfully? Would you be ready for including cloud computing as an option for additional computing needs? If pricing is reasonable, would you consider running production jobs in the cloud? Will you be ready for Requesting a Quote on the UberCloud Marketplace from selected service providers?
8. As a service provider, provide your services in time, for example access to resources, software, and expertise shouldn’t take longer than a few days. We don’t ask for Service Level Agreements for the experiments, but consider the opportunity that the end-user might become your customer in the near future.
9. Follow up with your team at least once a week. If you can’t be available, announce this to your team well ahead of time.
10. And finally, whenever your team faces a roadblock, contact immediately your Team Mentor who will help to resolve your roadblock.