cancel
Showing results for 
Search instead for 
Did you mean: 

Contradicting info on scalability

Meinrad
Participant
0 Kudos

Hi,

 

maybe somebody can have a look at the screenshots below. Both are taken from Learning Journey about SAP HANA Cloud.

There is this statement claiming that we can scale storage (which for me is memory in case of HANA) and Computing power independently.

file1.jpg

And here is a clear statement that whenever I increase memory the number of vCPUs will be adapted. 

file2.jpg

Same is stated in this one:

file3.jpg

 

Besides, I think it is not possible to change the amount of vCPU directly, i.e. without changing the memory

So, how can this be explained?

Kind Regards

Meinrad

View Entire Topic
Jarmo_Tuominen
Participant
0 Kudos

Today I got the log below for cf push.

user: risk-management $ cf push
Pushing apps risk-management-srv, risk-management-db-deployer to org 081025f1trial / space dev as jarmo.tuominen@accenture.com...
Applying manifest file /home/user/projects/risk-management/manifest.yml...
Manifest applied
Packaging files to upload...
Uploading files...
77.21 KiB / 77.21 KiB 100.00% 1s

Waiting for API to complete processing files...

Staging app and tracing logs...
Downloading nodejs_buildpack...
Downloaded nodejs_buildpack (182.9M)
Cell a5d98efb-e5e2-4d57-b93d-3f6287838766 creating container for instance 49fea11c-4157-436a-8111-94ded63deb9a
Cell a5d98efb-e5e2-4d57-b93d-3f6287838766 successfully created container for instance 49fea11c-4157-436a-8111-94ded63deb9a
Downloading app package...
Downloaded app package (331.1K)
-----> Nodejs Buildpack version 1.7.65
-----> Installing binaries
engines.node (package.json): >=12.18
engines.npm (package.json): unspecified (use default)
**WARNING** Dangerous semver range (>) in engines.node. See: http://docs.cloudfoundry.org/buildpacks/node/node-tips.html
-----> Installing node 16.13.1
Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/6ba42799f8211c597989b95ad2db3de2/node_16.13.1_linux_x64_cflinuxfs3_7f893010.tgz]
Using default npm version: 8.1.2
-----> Installing yarn 1.22.17
Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/4984aeaaf5967be21b1e442d431a1957/yarn_1.22.17_linux_noarch_any-stack_08892f64.tgz]
Installed yarn 1.22.17
-----> Creating runtime environment
PRO TIP: It is recommended to vendor the application's Node.js dependencies
Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring
NODE_ENV=production
NODE_HOME=/tmp/contents1555682101/deps/0/node
NODE_MODULES_CACHE=true
NODE_VERBOSE=false
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
-----> Building dependencies
Installing node modules (package.json + package-lock.json)
BuildpackCompileFailed - App staging failed in the buildpack compile phase
FAILED
user: risk-management $

When I in browser go to https://sandbox.api.sap.com/s4hanacloud/sap/opu/odata/sap/API_BUSINESS_PARTNER/ , I get the error below.

{"code":"SERVICE_UNAVAILABLE","message":"From Friday, Feb 25th 14:00 CET until Thursday, Mar 3rd 10:00 CET there is a planned downtime for the API sandbox system. During this period you cannot use the Try it Out feature on our API sandbox system to test an API service."}