In my last series of blog posts I detailed the considerations for Stage 2 of the new EucaStart 2.0 methodology, which covered the architectural discussions that should be had before choosing and deploying cloud hardware. In this blog post, I will provide a high-level overview of what you can expect to receive during the third stage of your EucaStart program, and what you should do with that information.
Architecture Diagram and Bill of Materials
Getting to Stage 3 means you have successfully completed one or more detailed conversations with a Eucalyptus Cloud Architect around your cloud, as well as the hardware, software, and business processes that need to be in place in order to ensure success. Once this is done, the Cloud Architect will begin work on cloud architecture diagrams that go into detail about specific hardware that should be purchased (or used, if already in place), how software on it should be installed and configured, and the procedures we expect to be documented and in place prior to cloud installation.
Since there are a *large* number of variables at this stage, a detailed description of what the Cloud Architect will deliver is nearly impossible to write. The process can take anywhere from a couple of days to a few weeks depending on the complexity of the deployment. To get some idea of what to expect, you should check out Dan Nurmi's great work on Eucalyptus Reference Architectures on our wiki:
Generally speaking, the architecture documentation and bill-of-materials you can expect to receive at this stage of the EucaStart will follow the same format and information flow as the examples listed on this page, except with more specific detail, detailed configuration information, and a bill of materials (BOM) for the specific hardware we expect you to have in place prior to cloud installation.
The key thing to be aware of at this point is that in the next phase of the EucaStart, we will be inspecting this hardware, software, and procedural setup to ensure that all of the pieces are in place *prior to* scheduling a consultant to perform a cloud install and configure engagement. You should ensure that you understand everything in the architecture document and BOM before you purchase and set up your environment, and if you have questions, your Cloud Architect will be available to answer them. Our primary concern is a successful deployment, and we will delay actually installing your cloud until we can be sure your success is guaranteed once we begin, whether we come onsite or perform the installation remotely.
What do you think? Can we be more specific about this stage? What do you suggest? I would love to hear your feedback either in the comments below, or via email at email@example.com.