My name’s Michael
Goddard, I’m going to give you a quick
introduction to the Azure Quickstart for Viya 3.4. The Quickstart is a template
for doing an automated deployment of Viya 3.4. It is automated in
that no intervention is required while the
software is being installed. There is a template and a form. Once you have provided
the input parameters, the process is automated. It provides a new build from
scratch, in that all the Azure resources will be built
and configured as part of running the template. The virtual servers,
the VMs will be set up, the networking, storage,
the network security groups, et cetera, will all be
configured and set up as part of this process. It is templated but
it is extensible. The template keeps the process
simple with a number of options pre-coded so we do not have
to ask you a lot of questions to be able to kick
off a deployment. However, if you need
a more custom install, the code is available
on GitHub, which you can download and update
to meet your specific needs. And finally, it is
supported, as running the template uses a
standard configuration approach and customization. So you end up with a standard
supported Viya configuration. Some considerations
for the Quickstart. So currently it is for SMP or
a single server CAS deployment. A multi-server or
MPP deployment is not supported at this point in time. It is also not for
all Viya products. As you can see, it supports
SAS Visual Analytics, Visual Statistics, Visual Data
Mining and Machine Learning. And importantly,
it’s not the only way to deploy Viya and Azure. You can still do
your own deployment using a standard
approach and techniques. Setup your virtual machines, the
storage, networking, et cetera, create a local mirror, and
install your software that way. It is still fully supported. Finally, it is not
free of charge. The Azure infrastructure
costs will be billed to you. You also require a
valid SAS software license for the Viya software. However, the Quickstart
code is available on GitHub that you can download
and use free of charge. So what do I need to know
to use the Quickstart? Well firstly I must be
familiar with Azure. You will be using
the Azure portal and potentially there is
your command line interface as part of the ongoing running
and maintenance of the system. You need to be familiar with
the Quickstart documentation for the SAS Viya deployment. You need a user account with
contributor and admin roles. Basically you need
the permissions to create the resources as
part of running the template. You need Azure Blob storage. This also requires
a storage account. And we use the storage to upload
the software order from SAS. To secure and configure the
servers, when need SSH keys. And finally you
need an awareness of your own IP address. This is required so we can
set up the network security roles and the firewall
roles to allow access to your environment. There’s a couple of
notes at the bottom here that I want to point out. There can only be one Quickstart
deployment per resource group. So I cannot run multiple
deployments into a single resource group. However, you could use an
existing resource group that your enterprise
already has. However, we do recommend that
each Quickstart deployment has its own dedicated
resource group. This just makes ongoing
management and maintenance of it a lot easier. You know that all the
SAS Viya resources are in a single resource
group that is dedicated to it. What does the
deployment look like? This graphic illustrates
what is built as part of running the template. Firstly, there is an
Ansible/bastion host that is created. This will run the
Ansible controller and also provide the
bastion host– or jump host, if you like– for
accessing the Viya servers. So the SAS Viya
software is installed on two virtual machines. There is the Viya services
machine in the CAS controller machine. For access for the
web applications, an application gateway is
provided as part of the setup. And as I say, this will be used
by the Viya visual interfaces to access the platform. And finally there
is the blob storage that I talked about before. It’s time for a demo. What we like to do is take
you through the steps involved with actually creating the
Viya Quickstart deployment. But first I’ve created a bit of
a checklist for all the steps that we need to go through
as part of running it. So the four key areas
or high level areas you can see here,
there is some prep work that we need
to do in Azure. Once we’ve done that, we
can execute the Quickstart template. When that’s running I will
show you how to monitor it. And finally we need to
validate the deployment. We want to know that it has
been successfully installed. So the first steps
we’ll go through here– obviously we need to be able to
access the template, which is done through the Azure portal. As I said, we want to have
a dedicated resource group. This can be created
in advance, or we can do it as part of
running the template. And that’s what
I’ll show you today. We will actually create
the resource group as part of this
template execution. We need to create
the blob storage, and that is really
the first step for us. And then once we
have that created, we need to upload our
Viya software order. So let’s have a look at creating
the blob storage I’ve already logged on to the
Azure portal and I’ve come through to the storage
accounts here and the summary. And what I need to do is
create a new blob storage. And to do this I use
the Create Container or Add Container button. And as part of that, comes
up with this dialogue box, and I need to give it a name. So let’s call it
Quickstart Blob Storage. Now you can see that we have
successfully created this. And at this point, all we
have is an empty container. So I need to upload
the Viya software order to this container. And I do the three
using the Upload button. I can browse the file
system for my orders. And at this point I actually
have two software orders– one for VA only deployment,
which we call our reporting environment, and
a second which has got the Visual Data Mining
and Machine Learning software order. So I’ll upload the VA
only order to start with. And here, note if it already
existed I could tick the box to override it. And we’ll just upload
it through there. Then, while I’m here, I
will upload the second order for the VDMML order. So again, we’ll upload that. So if I come back to
my checklist in here, and I’ll just change my pen– my laser pointer to a pen here– we can see that we have
actually logged onto Azure. We have skipped that. We’ve created our blob storage. Now we’ve uploaded
our software order. But we need to do
these two tasks here. We need to generate the
blob SAS token and URL. And then we need to note
down the SAS blob token. So take you through
those steps now. So we come back to
the Azure portal. And here, for each
one of these, we need to generate the SAS token. Now this isn’t referring
to SAS the company. This is actually a
Shared Access Signature is what SAS stands
for in this case. So it is an Azure thing
for securing those two files that we uploaded. So we generate the SAS token
URL, and here the strings full. And at the moment, we just need
to note down that blob SAS URL. So I’m going to copy
that to the clipboard and I’m going to
take note of this, because I need to
use that later on. So our reporting environment,
I will just paste that in here so that we can use it later on. Now, I need to do the same thing
for the other software order. So again I come and generate
our shared access signature. So generate the
token and the URL. Again, we’ll copy
the URL for that. And I’ll come back
to my notepad and I will put that in here as well
for the discovery environment. So now we have both
of those captured. So if we come back to our
checklist, we have come through and we’ve actually
created those. I’ve noted them down
for future use in here. And the next step that
we need is some SSH keys. Now, you may already
have SSH keys set up. But if you don’t, there
is a way we can do that using the Azure console again. So if I come back to
the Azure console, I’ll show you how to do that. So up here there
is the cloud shell. So if you don’t have an existing
Linux server or an existing pair of SSH keys, you can
use this bash environment to actually create
the keys for you. And so that’s what
I’m doing here. Because I haven’t created
any existing virtual machines or Linux virtual
machines at the moment, so I need to be able to
create those keys for me. So this is just connecting in. And as you can see it’s
connecting to the terminal. And in the moment I will have
my bash shell environment and I’ll be able to
issue the command. So here we go. Just check that we’re in there. Now if I come back
to my notepad, I actually did a
bit of prep work. So this is the command
that I want to issue to actually create the keys. So I’ll just copy that for a
moment and we’ll come down here and we’ll paste that in there
and we’ll run the command. So the first thing
it does is request a name for this, because
I didn’t actually provide it as part of running
the SSH key gen command. So let’s call it
Quickstart Demo– and if I could type
properly, there would be a wonderful thing– Quickstart Demo Keys. I’m going to override. I already had a pair here,
and accept that are false. The only reason I hit overwrite
that is in my testing I already had a key named that. So if I came in here you can
see we’ve actually created this Quickstart Demo Key. The private key. The public key. And our previously
created two keys as well. So now that we’ve got them
created in this environment, I need to download them so
I can use them later on. So I can do this using this
upload download facility. And I’ve already done
this for the two keys that I previously had created. So for speed I will just
exit out of that now. So I’ll quit from this. So if we come back
to our checklist, you can see that we’ve actually
run through all the things on our prep list here. We now have some SSH keys. So we can actually tick
that off as completed. So our next step is to
execute the template itself. So we access that
by this URL here. And we need to fill
in those parameters. So let’s have a look at that. So here is the Microsoft page
for the SAS Viya Quickstart. And there’s two buttons
here, as you can see. This one to launch the
deployment template. And also to access the
information on GitHub through here. So if we come
straight to this, this is going to log me on
to the Azure portal again and bring up
the template form. So in here we need to
specify which subscription. And you may have an existing
subscription that you will use. Or you may have created one
for the Viya deployment. I’m just going to use this
existing subscription. As I said, we do recommend
having a dedicated resource group. You can use something
that’s pre-existing. And if I did have one I could
use this dropdown to get to it. But we actually want to
create a new one in here. So I’m going to give it a name
for my reporting environment, and Demo Reporting
is the name I’m going to give this resource group. The Quickstart Demo
Reporting resource group. As part of creating that,
you can choose the location in Azure where you want
this deployment to run. So depending where you
are around the world you can select the
appropriate location. I am in Asia-Pacific,
so leave that at Australia East for this. Now, the settings in here
are the things specific to the SAS deployment
that we need to capture. So the first one is the
shared access signature that we copied before. So I now need to
get back my notepad. And for our reporting
environment, I want to take this URL and
copy it into this field here. I also need to provide the SSH
public key that will be used to generate the Linux servers. So in doing this I’ve
already downloaded the keys from before, as
you can see here. So the public key– if I just come and hit this
with Notepad or some other– your favorite editor–
select that string and I’m going to copy
that into this field here. By pasting in there. We do not need to touch
the location field. As you can see this
is made up of a string which is the resource
group and location. So using these two fields here. The next bit we need to know
is the web ingress location. And this is we need to
know your own IP address, and we need to
specify it in here. So to do that, I’m
going to find this out using what’s my IP address. And if I have a
look at that, this is a quick way of finding out
I can see my IP address here. And this is what we need
to use in the template. So I’ll copy that
into this field. Now, if were are actually
dealing with your organization, there’s bound to be more
than one person that needs to access this. So you would actually specify
a range of IP addresses. And that’s how you would
do something like that. For this, I just want my
own laptop to be available. So I’m going to paste that
into both of these fields. So this is for the
web applications. The bottom one,
the other admin, is to get to their Ansible
controller, our bastion host. Now, the next two
fields that we have here is for the SAS
admin user, I need to set the password for that. So I type in the password that
I want to use for that user. And for the first user or
the SAS user of the platform, again I need to provide a
password for that user as well. Now, there are these
other fields in here. I can leave those
for the moment. There is the deployment mirror. This is optional, so if I
had created a local mirror I could use that, or
I can just use the SAS mirrors, which is what I’ll do. You can also specify the size
of the Ansible virtual machine and the services virtual
machine in there if needed. And there’s another
optional step around the location of
the SAS token, which we don’t need to do this
for standard deployments. Leave this empty,
which we will do. And then the final field is for
standard deployments accepting the default. So we will
just accept the defaults for those things. Now, if we go ahead
and purchase that, we have now launched
the deployment. We can view the progress
of this at this point. And we can see it
started running. So we’ll leave that
running in the background. And that was our
reporting environment. As I said, we actually
had two orders here. And so we’ll kick off the
second one for our discovery environment and doing the
same sort of thing here. Again, I’ll use the
same subscription. I’ll create a new
resource group in here for the demo
discovery environment. So I will create that. Again, I need to specify the
SAS URL for the license file. And so if I come
back to my notepad, where I captured this
earlier, at this point I need to grab this
string and copy it into the field in there. So I’m going to paste that in. Again I need my public
SSH key, and I still have that open in
my editor here. So if I grab that again, and
I’ll copy that and paste it into the field, I need my IP
address the same as last time. And luckily I did
not capture that. Sorry. I should have pasted that into
my notepad in preparation. So again, we’ll just
grab this IP address. And we’ll come back
into here and paste that into both of these fields. And as you briefly saw, the
other installment deployment is progressing away. We’ll also need to set– specify
the password for the user again. So we can do that. And again we will
accept the defaults through here, the terms and
conditions, and purchase. So, we now have our second
deployment up and running for our VDMML deployment. So if I come and
have a look at that. So we now have these
two deployments going. The first one,
the reporting one, has been going for some time
now and it’s progressing nicely. And here is our second
deployment that’s underway. So if we actually come
back to our checklist here, we’ve come through and we’ve
filled in all the required parameters in here. So we can take that off. We’ve launched our deployment. So this is completed
at this step. And we’ve seen how we can
actually monitor it as it’s progressing through there. So this will take
a wee while to run. So while the installation is
happening in the background, I will pause the video and
be back with you shortly. Welcome back. So both our deployments
have finished now. And we can come and
have a look at them. So here we are seeing that the
deployment for our discovery environment has
completed successfully. So as I showed you
before pausing the video, this is a way of actually
tracking and monitoring the installation as
it’s going forward. For our reporting
environment, again, that has finished
successfully over here. And one of the things
you can do to check the deployment and
the status of it is to come in and look at the
services status in the Ansible controller. So if I find the
public IP address for this, which
is listed here, I can copy that in and then
using your favorite terminal, such as MobaXterm
as I have here, I’ve logged into the
Ansible controller and have issued the
command to actually see whether the services
are up and running. So this command
is actually here, documented in the
GitHub documentation. And this playbook comes
and shows us the status. So as we can see here, we
have monitored our deployment. And that step’s complete. And the next and
final step is actually to validate the deployment. And I’ve really
started to look at that by going to the services
and seeing that everything has started successfully. But what we really want to do
is to log on to the environment and log into the
visual interfaces. So to do that, coming back
to our reporting environment, our Visual Analytics
environment, I need to find out the public IP
address for the load balancer. And so this is down here this
public Viya load balancer. So if I take that IP
address, copy it into here, and go to this, I’ll first
get prompted for the fact that we’re using a
self-signed certificate. So the connection
is not private. And we’ll proceed to that. And now we’re actually
accessing the Viya environment. So what I want to
do now is actually to log on with the SAS user
and the SAS administrator that we have set up as
part of the template. So you can check the
visual interfaces. So first let’s come
in as SAS user. I’ll use the password that
I set in the template. And we’re logging on here. So the first time you
actually come and log onto the environment you will
be prompted to set up a profile. You can add pictures,
et cetera, for yourself. And that’s what
we’ll see in a moment here when we’re prompted. So this is the step
that we can come in here and set up a profile, profile
picture, theme, et cetera. But we’ll skip that
for the moment. And here we are
at the SAS drive. So we have a working
Viya environment. From here I could do
a number of things. I could actually start
working with reports. Or I could develop some code. And coming in here I’m
actually starting up and accessing SAS Studio. And this is the coding
interface for the Viya platform. So once this is started up,
one of the things I can do is check that I can
actually make a connection to the CAS server in here. And we do that
using code snippets. So I can actually
run a code snippet to connect to the CAS
server and start a session. And that’s what
we’ll do in here. So going to the snippets,
the cloud analytics services snippets, and
then new CAS session. If I drop that on here
and then submit it, basically I can see– and this may be a
little hard to read– but if we look at
this line here, we can see that we
successfully started a session with the cloud
analytics services. So it’s all looking very good. So this is logging on as just
the standard application user. If I come over to
here and sign out, I don’t want to save
that studio project. So we’ll just
signs straight out. I can also sign in with the SAS
admin user that was created. And this user is in the
SAS administrators group. So as part of logging
on, we will actually get prompted as to
whether we want to assume the administrator roles. And I’m going to
select yes here. And again it’s going to come
in and give us the default SAS drive. From here we will be able to– sorry, again, first time log on. We can personalize
it for ourselves. I’ll just skip over that. And once we get
logged on there, we can actually come in and
access the environment manager and come in here. As you can see, the
SAS Environment Manager is available to us. And that’s going to come
in and build the dashboards and show us the status
of the server that way. So this is using
the SAS Environment Manager to look at the
status of the deployment. So it’s just in the process
of initializing and building the base dashboard as we speak. And it’s coming up now. So what we’ll see in
a moment is the fact that we had a two
server deployment. If you remember there was the
services server and the CAS server. So in here you can see
we’ve got two machines. The CAS controller
is up and running and the Viya services
server is the– and all our services are
showing in a green state. So the deployment
is looking good. So if we come back
to our presentation, we can see that our
deployment steps, our checklist here, we have
validated our deployment and everything’s looking good. And wrapping up, we’ve had a
successful deployment, or two deployments, of
the Viya software. And as we’ve seen,
the Azure Quickstart can be used to provide
an automated deployment of the Viya environment with a
SMP or single server CAS server environment. For more control
and customization, you need to be familiar with
Azure and the Azure CLI. And also the Ansible and the
deployment processes for Viya. You can download the
templates from the GitHub and customize those for
your– to meet your own needs. And as I’ve
previously said, it’s recommended that you dedicate
a resource group for the Viya deployment and that only one
quickstart deployment can be put into each resource group. I hope this has been useful
and informative for you, and thank you for your time.