Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is SAP Cloud Platform, Getting Started and in
this video, we are going to take a look at the workflow for account set up.
This video has been recorded in October 2018.
For the most recent tutorial videos on this topic, please check the playlist on the SAP HANA Academy.
Hi, I am Denys van Kempen.
In the previous videos of this series, we looked at the prerequisite checklist and discussed the
different ways how you can set your account model up.
In this video, I will cherry pick a bit from the different sample models, just to show
the options we have got to set this up and show you the workflow.
We will create a staged development environment —so with development, test and production—
using the DevOps approach most of you will be familiar with, for continuous integration
/ continuous delivery with separate subaccounts for development and a consolidated subaccount,
one of testing, and one for production.
For Neo, we can combine this with model 2, where we can use a subaccount as base template.
For Cloud Foundry, as discussed, this is not possible, as Cloud Foundry, at least today
—at the time of the recording that is— only runs in the data centers of our partner
cloud providers, again, today: Amazon, Google and Microsoft.
We will also weave in model 1, with a staged environment combining both Neo and Cloud Foundry.
There is no reason to choose between both environments, you can very well use both,
depending on the objective of your development project.
That will be our account model.
Now before doing so, lets briefly review the workflow from the SAP Cloud Platform guide.
There is one for Cloud Foundry and one for Neo.
I will show them here side-by-side, so we can do a quick comparison and focus on the differences.
I will assume you already have a global account either as a customer or through the Partner Program,
so we can skip step 1 - Getting a Global Account.
In Step 2 - Setting Up Your Account Model, we are going to create a subaccount.
For this, we need to log on as administrator of our global account (the only privilege there is at this level)
For Cloud Foundry, we will also need to create a space.
To keep my Cloud Foundry in synch with Neo, for the purpose of DevOps and staging,
I will only create a single space.
However, as discussed, there are reasons why you might want to decide otherwise.
It is just an example, not the holy grail.
OK —Optionally, you can download the Cloud Foundry CLI, command line interface.
If you have any experience with working with the SAP HANA XS Advanced client (xs login, xs apps),
you will have a zero learning curve as it is pretty much the same.
We will look into the cf CLI in another video tutorial.
In Step 3 - Configuring your environment.
For Neo, we want to add members to our subaccounts and add quotas.
For Cloud Foundry, we can add members at both the Org level, in our case, the subaccount,
and the space level.
Again, we need to add quotas.
Optionally, we can create a quota plan for this subaccount and assign quota plans to a space.
As I am only going to create a single space, I won’t be doing this, but should you decide
otherwise, know that you have this flexibility.
Why?
Well, it is perfectly possible in the world of Cloud Foundry to create a staged development
environment under a single Org (again, think subaccount) with a separate space for development,
test and production.
In this case, you probably want to assign different quotas, different limits to production
versus development.
We cannot do this in Neo, so I will not be doing this in Cloud Foundry in our example
but should you not be using Neo, you might very well implement such a model.
Again, this all comes to the Account Model setup, which we discussed in the previous video.
Finally, Step 4 - Developing and Deploying Applications
Well, this works a bit differently as well, of course, for both environments: development and deployment.
Also note that on Cloud Foundry, we will need to create service instances and subsequently,
bind these service instances to applications or, alternatively, optionally, we can create
service keys and user-provided service instances.
Of course, this will assume a certain familiarity with developing cloud native applications
in Cloud Foundry and before we deep dive into the development and deployment part of the
workflow, let’s first set our account model up and configure our environment.
This we will do in the next video.
Thanks for watching.
You can find more video tutorials on our YouTube channel.
If you would like to be informed about new video tutorials, please subscribe to our channel.
You can connect with us on LinkedIn or follow us on Twitter, as well for updates, and if
you are watching this video on YouTube, do not hesitate to leave your comments to the
video page and, if you like, give us your vote on this video.
Have a great day and thank you for watching.