ArticlesBlog

Tech TopX: Installing Nutanix Calm and Launching Apps from the Marketplace

Tech TopX: Installing Nutanix Calm and Launching Apps from the Marketplace


Imagine you want your end-users to be
able to install applications at the click of a button. Now with Nutanix
Calm, you can. I’m going to show you guys how to install Nutanix Calm and get it
configured. Hi, welcome to Tech TopX. I’m Michael Hague – a Systems Reliability
Engineer out of the Durham, North Carolina office. Today we’re going to be
talking about Nutanix Calm. Calm allows you to select provision and manage your
business applications across both your public and private clouds. It allows your
end-users to do self-service application, deployment, and management. It also allows your admins to do budgeting and costing across your public and private cloud. So
here’s our freshly deployed AOS 5.5 Prism Central instance. We’re going
to walk through this steps to enable Nutanix Calm. The Nutanix Calm is
integrated into Prism Central, so there’s no extra VM that you have to
deploy. So now with 5.5, if you click on this question mark icon, we’ll
see this “New in Prism Central” option. We’re going to walk through the self-service and apps section. So first off if you haven’t already connected to an active
directory instance, we’ll need to walk through that. So I’m going to click new
directory and fill out the relevant details. Obviously these are going to be
different for your environment. The next I’ll need to do a service account. This
can be any sort of read-only account that you need for. For more info on what
this is doing, feel free to scope out the Nutanix support port. So now that we’ve got AD connected, the next step is to configure self-service
so the self-service portal and Nutanix column share the same back-end so we’ll
need to have both enabled here. We see that we’re going to.. First, we have an
opportunity to add an SSP admin. In this case, I’m going to do an admin group, but
feel free to add whichever group or users that you feel is applicable. Next
we see here, the default cluster. I’m going to stick with the ceres cluster
which is an AHV 5.5 cluster and next I’m going to choose which networks I want to
have the ability to deploy to. I’m just going to go with the DHCP network in
this case. You can always come back and modify this if needed. So we’ll hit next.
We’ll finally be on the Apps section. So again if you are only looking to do SSP
you can hit finish here, but obviously we want to enable Nutanix Calm so we’re
going to hit the check box for Enable App Management. There’ll be some info
here we see. And then finally down here the Nutanix seeded blueprints. We’re
going to leave this checked because we want to include about 20 as of this
release. 20 Nutanix official seeded blueprints – which allows your end users
to have one-click deployment. So finally we’re going to go ahead and click finish
and we’ll see a pop up that we received their request to enable Calm. We’ll hit
OK and then now we’ll just wait for about five minutes and come into the
Apps tab up at the top and Nutanix Calm will be deployed. So I’m going to go
ahead and log back into Prism Central with the engineer and Nutanixdemo.com AD account. This is a project admin account. So I’m going to go ahead and click on apps here at the top. This is for the Nutanix Calm UI. We’ll next go into the
marketplace, so we’re going to see all the available marketplace apps to this
particular user. So this is going to be a combination of Nutanix official Nutanix
seeded blueprints and then also custom blueprints that developers have created
in your organization and then published to the marketplace. So for instance, here, you see about four different LAMP icons and also who
published them. So this upper left lamp icon, we see Nutanix. So that is the
official Nutanix seeded blueprint. And then we see these other items published
by Chris so [email protected] We’ll see both things. Today we’re going
to walk through deploying the Jenkins blueprint. This is an official Nutanix
seeded blueprint. Before we hop into that actual deployment we’re going to need to
do one thing that is required for our marketplace launches, which is to create
the environment section in projects. So if I click on the projects icon, I’m
going to come to the engineering project and then click on environment at the top.
So we’re going to be configuring the AHV on Nutanix environment section. Again
this is required for all marketplace launches, so essentially this defines
information about your Nutanix blueprints at the project level. So this
allows Calm to know specific things about your environment. For instance, the
network adapters – so Calm actually is going to need to know which network to
deploy these applications on. So we’ll start there. We’ll go ahead and select
the DemoVMs network and then essentially for this project, all of your
marketplace apps will be deployed on that DemoVM network. So we’ll select these credentials here. Typically, you need both a key based
and password based credentials, so we’ll select that and then finally I’ll come
up back up to the top here. For other items within your project you might not
want to have it configured project-wide, you know for all settings. So for certain
things like the VM name, we’re going to want to be able to, you know, configure that on
a per application basis. So we’re going to go ahead and click on the running man
and watch it turn blue. That will enable the users to specify the VM names at
launch. Same thing with the image. We’re going to specify that at runtime and down
here depending on how your environment is set up, you know, you might wish to specify these vCPUs or you might want your end
user to specify them. I’m going to go ahead and specify them in this case and that’s
all there is to it. We’ll go ahead and click ‘Save’ and make sure it saves
correctly. We see that it was. So next we’ll come back to this – to the market
place. So now that we’re back in the market place tab, I’m going to go ahead
and click on the Jenkins app. We’re going to see some information here. This could
be provided again by Nutanix or your developer if it’s a custom blueprint. And
we’re next going to hit launch. We have to select the project. Obviously for the
particular user I’m logged in as, they only have access to one project but if
you have a user that’s in multiple projects, this allows them to
differentiate where they want that application deployed. I’ll hit launch and
wait for the application page to pop up. I’m going to name this application. It’ll
just be JenkinsDemo, but name it anything. This does have to be unique.
Otherwise, name it to your liking. So next I want to walk
through a couple of things here that are important. So if we expand this VM
configuration we’re gonna see a couple of settings here that are already have
been defined by the blueprint. One important thing is the #cloud-config and
using Cloud-init and we see here we’re going be adding the public key of the
Prism Central VM into the authorized key section of the Jenkins’ VMs. That will
allow us to do password lists SSH. So in order to do that, I’m going to specify
the public key here. I have it copied into the clipboard already from the
Prism Central VM and I will paste that in. And then scrolling back down another
thing we’ll notice is that we need to select the network adapters. We’ll go
ahead and click the demo VMs again and finally we’ll do the same thing on
Jenkins Slave. We’ll see the NIC needs to be selected and that’s it. We’ll go ahead
and hit create and this will take about ten minutes to deploy. We can see the
steps that it’s going through in just one second as we go to the application
page. So we see it’s provisioning up in the upper left. We’re going to have VM
information here in the middle once the VM starts getting spun up and we also see some variables down at the bottom. So the most interesting part is coming here
to audit and we can expand this create section and we’ll see a step-by-step
process of Calm deploying the Jenkins application. So now we see that the create task is
finished up, I’m going to go over here to overview. Verify we see that the
application is running and now for the the final setup, we’re going to go to the
services here and click on the Jenkins Master. So I’m going to go ahead
and grab this IP and browse to it and we’ll see that Jenkins is currently
locked. So what I’m going to do is SSH into this master VM and grab the initial
Admin password as located on the server. So here I am – SSH’d into it. If I do a cat
on that file, we’ll get the initial Admin password and
we’ll go ahead and paste that in. Click on continue. I’m going to go ahead and
install the suggested plugins and we’ll just give Jenkins a couple minutes to
get set up. So now that Jenkins is finished setting up, I’m going to go ahead
and create an Admin user and hit ‘Save and Finish’ and we’ll click ‘Start using
Jenkins’. And here we have, a fully configured and running Jenkins
application. So the last thing I want to show is, back in Calm we’ll come here to
the manage tab and we’ll see all the actions that we can run on it. So
upgrading Jenkins is included in this Nutanix blueprint. We can stop the application, get it to start back up again, and then
finally we can delete it if we want to delete the underlying VMs or we can do a
soft delete which will remove the application from Calm but will leave
the underlying VMs up and running. I hope that was helpful. Thank you for watching
and be sure to subscribe to our channel for more Calm videos.

Comments (3)

  1. Awesome, Well done!

Comment here