Skip to content

Commit a84d951

Browse files
committed
Update from SAP DITA CMS (squashed):
commit 5749a0e1b9094e59a51a51cf14b5b83924b01f15 Author: REDACTED Date: Wed Feb 5 11:40:16 2025 +0000 Update from SAP DITA CMS 2025-02-05 11:40:15 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap Output: loio2080d0faf9d84ce6aa14caa4caa32935 Language: en-US Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap commit d6cff20a2d05978743a6c8e3ed5f15e6e1baa207 Author: REDACTED Date: Wed Feb 5 08:01:14 2025 +0000 Update from SAP DITA CMS 2025-02-05 08:01:14 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap Output: loio2080d0faf9d84ce6aa14caa4caa32935 Language: en-US Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap commit 83edb9bf32ab46076f9b639222564caeaabce1c3 Author: REDACTED Date: Tue Feb 4 16:52:02 2025 +0000 Update from SAP DITA CMS 2025-02-04 16:52:02 Project: dita-all/jjq1673438782153 Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap ################################################## [Remaining squash message was removed before commit...]
1 parent 7f7c31d commit a84d951

File tree

348 files changed

+6992
-15251
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

348 files changed

+6992
-15251
lines changed

docs/10-concepts/account-model-8ed4a70.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Global accounts are region- and environment-independent. Within a global account
3232

3333
## Subaccounts
3434

35-
**Subaccounts** let you structure a global account according to your organization’s and project’s requirements with regard to members, authorizations, and entitlements.
35+
In **Subaccounts**, you deploy applications, use services, and manage your subscriptions. You can use them to manage members, authorizations, and entitlements.
3636

3737

3838

Lines changed: 218 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,218 @@
1+
<!-- loio1c6cba872ce24f2ba24f53feb6dbce6d -->
2+
3+
# Additional Information About Cloud Foundry
4+
5+
Links to additional information about Cloud Foundry that is useful to know but not necessarily directly connected to the SAP BTP, Cloud Foundry environment.
6+
7+
8+
9+
10+
<table>
11+
<tr>
12+
<th valign="top">
13+
14+
Content
15+
16+
</th>
17+
<th valign="top">
18+
19+
Location
20+
21+
</th>
22+
</tr>
23+
<tr>
24+
<td valign="top">
25+
26+
BOSH
27+
28+
</td>
29+
<td valign="top">
30+
31+
[http://bosh.cloudfoundry.org](http://bosh.cloudfoundry.org)
32+
33+
</td>
34+
</tr>
35+
<tr>
36+
<td valign="top">
37+
38+
BOSH documentation
39+
40+
</td>
41+
<td valign="top">
42+
43+
[http://bosh.io/docs](http://bosh.io/docs)
44+
45+
</td>
46+
</tr>
47+
<tr>
48+
<td valign="top">
49+
50+
Buildpacks
51+
52+
</td>
53+
<td valign="top">
54+
55+
[http://docs.cloudfoundry.org/buildpacks](http://docs.cloudfoundry.org/buildpacks)
56+
57+
</td>
58+
</tr>
59+
<tr>
60+
<td valign="top">
61+
62+
Components of Cloud Foundry
63+
64+
</td>
65+
<td valign="top">
66+
67+
[http://docs.cloudfoundry.org/concepts/architecture/](http://docs.cloudfoundry.org/concepts/architecture/)
68+
69+
</td>
70+
</tr>
71+
<tr>
72+
<td valign="top">
73+
74+
Cloud Foundry Concepts
75+
76+
</td>
77+
<td valign="top">
78+
79+
[http://docs.cloudfoundry.org/concepts/](http://docs.cloudfoundry.org/concepts/)
80+
81+
</td>
82+
</tr>
83+
<tr>
84+
<td valign="top">
85+
86+
Deployment of Cloud Foundry
87+
88+
</td>
89+
<td valign="top">
90+
91+
[http://docs.cloudfoundry.org/deploying](http://docs.cloudfoundry.org/deploying)
92+
93+
</td>
94+
</tr>
95+
<tr>
96+
<td valign="top">
97+
98+
Developer Guide for Cloud Foundry
99+
100+
</td>
101+
<td valign="top">
102+
103+
[http://docs.cloudfoundry.org/devguide](http://docs.cloudfoundry.org/devguide)
104+
105+
</td>
106+
</tr>
107+
<tr>
108+
<td valign="top">
109+
110+
Diego Application Process Balancing
111+
112+
</td>
113+
<td valign="top">
114+
115+
[https://docs.cloudfoundry.org/concepts/diego/diego-auction.html](https://docs.cloudfoundry.org/concepts/diego/diego-auction.html)
116+
117+
</td>
118+
</tr>
119+
<tr>
120+
<td valign="top">
121+
122+
Glossary for Cloud Foundry
123+
124+
</td>
125+
<td valign="top">
126+
127+
[http://docs.cloudfoundry.org/concepts/glossary.html](http://docs.cloudfoundry.org/concepts/glossary.html)
128+
129+
</td>
130+
</tr>
131+
<tr>
132+
<td valign="top">
133+
134+
Overview of Cloud Foundry
135+
136+
</td>
137+
<td valign="top">
138+
139+
[http://docs.cloudfoundry.org/concepts/overview.html](http://docs.cloudfoundry.org/concepts/overview.html)
140+
141+
</td>
142+
</tr>
143+
<tr>
144+
<td valign="top">
145+
146+
Sample applications for Cloud Foundry
147+
148+
</td>
149+
<td valign="top">
150+
151+
[https://github.com/cloudfoundry-samples](https://github.com/cloudfoundry-samples)
152+
153+
</td>
154+
</tr>
155+
<tr>
156+
<td valign="top">
157+
158+
Security settings for Cloud Foundry
159+
160+
</td>
161+
<td valign="top">
162+
163+
[http://docs.cloudfoundry.org/concepts/security.html](http://docs.cloudfoundry.org/concepts/security.html)
164+
165+
</td>
166+
</tr>
167+
<tr>
168+
<td valign="top">
169+
170+
Cloud Foundry Services
171+
172+
</td>
173+
<td valign="top">
174+
175+
[http://docs.cloudfoundry.org/services](http://docs.cloudfoundry.org/services)
176+
177+
[http://docs.cloudfoundry.org/devguide/services/user-provided.html](http://docs.cloudfoundry.org/devguide/services/user-provided.html)
178+
179+
</td>
180+
</tr>
181+
<tr>
182+
<td valign="top">
183+
184+
Considerations for designing and running an application in the cloud
185+
186+
</td>
187+
<td valign="top">
188+
189+
[http://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html](http://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html)
190+
191+
</td>
192+
</tr>
193+
<tr>
194+
<td valign="top">
195+
196+
Installing the Cloud Foundry command line interface
197+
198+
</td>
199+
<td valign="top">
200+
201+
[http://docs.cloudfoundry.org/devguide/installcf/install-go-cli.html](http://docs.cloudfoundry.org/devguide/installcf/install-go-cli.html)
202+
203+
</td>
204+
</tr>
205+
<tr>
206+
<td valign="top">
207+
208+
Blog about Cloud Foundry
209+
210+
</td>
211+
<td valign="top">
212+
213+
[http://blog.cloudfoundry.org/](http://blog.cloudfoundry.org/)
214+
215+
</td>
216+
</tr>
217+
</table>
218+
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
<!-- loiob6a7e11c3a58416a9ab1175bba17193a -->
2+
3+
# Availability Zones in the Cloud Foundry Environment
4+
5+
The Cloud Foundry environment follows the recommendations of our partner IaaS providers by leveraging the availability zones \(AZ\) concept.
6+
7+
8+
9+
<a name="loiob6a7e11c3a58416a9ab1175bba17193a__section_nty_twt_wjb"/>
10+
11+
## About Availability Zones
12+
13+
**Availability zones** \(AZ\) are single failure domains within a single geographical region and are separate physical locations with independent power, network, and cooling. Multiple AZs exist in one region and are connected with each other through a low-latency network.
14+
15+
16+
17+
**2-AZ and 3-AZ Deployments**
18+
19+
![](images/Availability_Zone_af5d046.png "2-AZ and 3-AZ Deployments")
20+
21+
To achieve better fault-tolerance, our partners recommend deploying services across multiple AZs, which improves the availability of a service if there are issues with the region infrastructure of one AZ.
22+
23+
24+
25+
<a name="loiob6a7e11c3a58416a9ab1175bba17193a__section_av2_yvs_mmb"/>
26+
27+
## High Availability at Platform and Application Level
28+
29+
The SAP BTP Cloud Foundry environment follows these recommendations to support high availability at the platform and application level:
30+
31+
- **High availability of the platform components:**
32+
33+
- The building blocks of Cloud Foundry and the virtual machines on which the Cloud Foundry application instances are scheduled run in a high availability setup. Their instances are distributed across different AZs.
34+
35+
- The technology that manages the deployment of the Cloud Foundry environment monitors the health of the platform. If there are infrastructure failures, it re-creates the faulty components.
36+
37+
38+
- **High availability on the application level:**
39+
40+
- We recommend running multiple application instances to increase availability. For more information, see [Run Multiple Instances to Increase Availability](https://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html#increase-availability). On SAP BTP, there are three ways to increase application instances:
41+
42+
- Scaling your application using the application manifest. The `manifest.yml` allows you to make and save configurations for your application. To scale, you can configure the instance count in the manifest and push the application again with the new configuration. See [App Manifest Attribute Reference](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#instances). To avoid downtimes when updating your application configuration, you can also consider using rolling application deployments. See [Rolling App Deployments](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html).
43+
- Scaling your application using the `cf scale` command in the Cloud Foundry command line interface \(CF CLI\). See [Scaling an App Using cf scale](https://docs.cloudfoundry.org/devguide/deploy-apps/cf-scale.html).
44+
- Scaling your application using the SAP BTP cockpit. See [Add or Remove Application Instances](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/75836f1b68ce439e9c169b05597f97e4.html?q=high%20available).
45+
46+
- The Cloud Foundry container scheduler takes care of distributing the different instances of one application on virtual machines in different AZs. For more information, see [How Diego Balances App Processes](https://docs.cloudfoundry.org/concepts/diego/diego-auction.html).
47+
48+
- Cloud Foundry is constantly monitoring the health state of application instances and restarts instances that are considered unhealthy. See [Using App Health Checks](https://docs.cloudfoundry.org/devguide/deploy-apps/healthchecks.html).
49+
50+
- When the number of desired instances doesn't match the number of actually running instances, Cloud Foundry reschedules the missing instances, for example, when the virtual machines that an application instance was initially scheduled on become unresponsive.
51+
52+
53+
For more information on high availability configuration, see [High Availability in Cloud Foundry](https://docs.cloudfoundry.org/concepts/high-availability.html#overview).
54+
55+
For more information on application stability and resilience, see [Developing Resilient Applications](https://help.sap.com/docs/BTP/0c8c1db388f645159e134a005aaabbcf/b1b929a5aea64571b2f74e810b622568.html?locale=en-US&state=PRODUCTION&version=Cloud).
56+
57+

docs/10-concepts/basic-platform-concepts-73beb06.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ SAP BTP offers users the ability to turn data into business value, compose end-t
66

77

88

9-
SAP Business Technology Platform is built on a multi-cloud foundation, which lets you choose from different infrastructures and runtimes. The services and solutions of SAP BTP are available on multiple cloud infrastructure providers, and it supports different runtimes, such as Cloud Foundry, ABAP, and Kyma, as well as multiple different regions, and a broad choice of programming languages.
9+
SAP Business Technology Platform is built on a multi-cloud foundation, which lets you choose from different infrastructures and runtimes. The services and solutions of SAP BTP are available on multiple cloud infrastructure providers, and it supports different runtimes, such as Cloud Foundry, ABAP, and Kyma, as well as multiple regions, and a broad choice of programming languages.
1010

1111
The central point of entry to the platform is the **SAP BTP cockpit**, where you can access your accounts and applications and manage all activities associated with them.
1212

@@ -61,7 +61,7 @@ Environments constitute the actual platform-as-a-service offering of SAP BTP tha
6161

6262
SAP BTP provides the following environments:
6363

64-
- [Cloud Foundry Environment](cloud-foundry-environment-9c7092c.md#loio9c7092c7b7ae4d49bc8ae35fdd0e0b18)
64+
- [Cloud Foundry Environment](cloud-foundry-environment-9c7092c.md)
6565

6666
The Cloud Foundry environment enables you to develop new business applications and business services, supporting multiple runtimes, programming languages, libraries, and services. You can leverage a multitude of buildpacks, including community innovations and self-developed buildpacks.
6767

@@ -135,7 +135,7 @@ The SAP BTP cockpit is structured according to global accounts, directories, and
135135

136136
- With **directories**, you can organize and manage your subaccounts according to your technical and business needs.
137137

138-
- **Subaccounts** let you structure a global account according to your organization’s and project’s requirements with regard to members, authorizations, and entitlements.
138+
- In **Subaccounts**, you deploy applications, use services, and manage your subscriptions. You can use them to manage members, authorizations, and entitlements.
139139

140140
In the SAP BTP, Cloud Foundry environment, the subaccount is divided into one or more spaces, which is where application development, deployment, and maintenance take place.
141141

0 commit comments

Comments
 (0)