Create an environment and deploy your assembly

An environment is an intersection of your assembly and a cloud. You will attach a cloud to your assembly to create an environment. As your assembly progresses through different environments, you can go on attaching either different or the same cloud with a different name to the assembly to deploy it. Thus, you will want to create descriptive names, which clearly state their purpose, such as development, QA, staging, production, and so on. Depending on how you deploy your assembly, the environment name also gets appended to the FQDN and will become part of how you address your server or call your app, so how you pick your environment name is crucial. Go ahead and click on Transition on the left-hand side and then click on New Environment on the screen. Let's call this environment Dev:

You can set the administrative status as Provision for now, which means your app is being provisioned. However, if you are confident that the deployment will go forth without error, then you can also set it to active. As you can see, OneOps has already generated a subdomain for you based on a combination of environment, assembly, and organization. This subdomain will be appended to the domain name that you configured to make your app accessible. For this test, I had registered a domain named practicalops.tk. This means my test Java deployment will be accessible at Dev.test-java.OneOps.practicalops.tk .

Tip

.tk, .ml, and lots of other kinds of domains can be registered for free (at least for 90 days) on various sites. One good site is http://www.freenom.com/en/index.html?lang=en. You can use it along with Rackspace DNS (which is also free) to run all kinds of tests.

Because my installation has only one organization, that is OneOps, I can uncheck the organization box. In this case, after deployment, my application will be accessible at Dev.test-java.practicalops.tk. Go ahead and commit your changes. You are now ready to deploy your assembly. Click on deploy. Once you click on deploy, OneOps will generate a deployment plan. You will get a chance to review it and back out if necessary. If all looks in order, go ahead and click on deployagain. OneOps will now start the deployment step-by-step. Depending on the steps, it may take some time.

You can view the logs by clicking on a particular step, expanding it, and clicking on the log link:

Once an assembly is deployed successfully, you can click on the assembly name on the left-hand side and see the status of the deployment at any time. Examples shown later are statuses of various deployments of an assembly named test-mysql, which is very similar to test-java but has a MySQL database deployed on it and also has block storage attached to it:

You can also view various reports and the health of your assembly by clicking on the health and reports tabs. The reports tab will show you details such as how many cores are used by your applications, whereas the health tab will show you the overall health of your assembly.