Cloud Foundry Environment
Cloud Foundry Environment is already enabled.
Cloud Foundry is the most commonly used environment in SAP BTP.
It supports application development, extensions, integrations, and services.
That’s why SAP enables it by default for learning and trial accounts.
As admins, we should note one thing clearly:
Just because an environment is enabled does not mean everyone should get access to it.
Access is always controlled separately.
Org and Space
Inside the Cloud Foundry environment, SAP introduces two important concepts:
-
Org
-
Space
-
Org is the top-level container inside Cloud Foundry
-
Spaces are smaller areas inside the Org
Spaces are usually created to separate:
-
development
-
testing
-
different teams or applications
In the trial account, SAP has already created one space called dev.
Creating a space in Cloud Foundry
Inside the Cloud Foundry environment, we can create spaces.
A space is where applications and services actually live.
Admins use spaces to separate work — for example, dev, test, or prod.
Here, I clicked on Create Space, and SAP asks for:
-
a space name
-
roles to assign for the user
By default, SAP allows us to assign roles like:
-
Space Developer
-
Space Manager
-
Space Supporter
-
Space Auditor
For learning, it’s okay to assign multiple roles to yourself.
In real projects, these roles are usually given to different people based on responsibility.
After creating spaces, this is how the Cloud Foundry section looks.
Here, we can see two spaces:
-
dev -
testing
Spaces are used to separate work.
For example, one space for development and another for testing.
Right now, both spaces are empty:
-
no applications
-
no service instances
That’s expected at this stage.
The important thing to understand is this:
Admins create spaces first.
Applications and services come later inside these spaces.
Comments
Post a Comment