Skip to Content
Technical Articles

SAP Cloud Platform Automation Pilot 101 – Managing your HANA Cloud Instances via Automation Pilot

What are you going to learn?

In the series “SAP Cloud Platform Automation Pilot 101,” we will explore this brand new service. We are going to start with this general article and continue to deep-dive into the service details. We will learn more about how to automate your repetitive DevOps work on top of the SAP Cloud Platform without effort.

In this blog post, we will explore the Automation Pilot capabilities for managing the HANA Cloud. And how you can easily execute lifecycle management steps for your HANA Cloud instance.

 

Automation Pilot and HANA Cloud

Automation Pilot provides a special HANA Cloud catalog with a set of predefined. Automation content for your HANA Cloud instance. Note that this is not final content, and we will extend it based on your feedback, so you are welcome to give it.

To locate the commands, you can simply filter them out by name in the Commands section of Automation Pilot.

As you can see, currently, we provide lifecycle management operations on top of your HANA Cloud instance. We are also working on scenarios for polling monitoring data.

 

How can I use those?

Let’s have a look at a particular scenario.

This is a straightforward two-step scenario of restarting a HANA cloud instance. Of course, this scenario can be executed via the command line; however, this brings with it a couple of downsides:

  • We have to maintain a script which consists of two commands (this script might grow in more complex scenarios)
  • We have to maintain a JSON input for each and every HANA instance that we have. So if we have to operate multiple instances in multiple locations, this can become a pain.
  • Whenever a new REST API is introduced, we should adapt our scripts.
  • We should use another system or a cron job for scheduling the execution of those.

All of those can be easily eliminated with Automation Pilot.

To easily test the scenario, do the following.

 

  1. Locate the RestartHANACloudInsatnce command.
  2. Hit the Trigger button.
  3. Fill your instance information – resource name, region.
  4. Add your user/password or refreshToken
  5. Hit the Trigger button.

Once you get used to the command’s usage and understand how they work, you can easily extract the required inputs into the Inputs section so you can re-use them and not enter them every time.

As a next step, you can try out to schedule the execution instead of manually triggering. And to make it more complex, if you have multiple HANAs, you can easily make this a mass operation on all or a subset of them.

 

What’s next?

  1. Explore the Automation Pilot HANA Cloud catalog and set up your automation scenarios. Feel free to get in touch and give us feedback.
  2. Explore the additional blog posts right here

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Hi Kiril,

    We’d like to automatically stop our HANA Cloud instances in the integration and validation environments when they are not in use and then restart them automatically when we need them. Is there a way to achieve this with the this solution (or using other tools)?

    Thanks,

    Pierre

    • Dear Pierre,

      thank you for getting in touch.

      I can think of a couple of ways of achieving this with Automation Pilot:

      • Schedule a stop of those systems at a certain point of time regularly or once.
      • Figure out a metric which shows that the HANA system is not used, then configure Alert Notification service (or another alerting system) to send alert to Automation Pilot that the system is not used and it will stop the system for you.
      • Of course manual stop is always an option.

      If you need a meeting to elaborate more on that just drop me an email to k.gavrailov at sap dot com and we will discuss it.

      Thanks,

      Kiril