|
1 | | -# **Landing Zone Framework** |
| 1 | +# **OCI Landing Zone Framework** |
2 | 2 |
|
3 | 3 | |
4 | 4 |
|
5 | 5 |
|
6 | | -Welcome to the **Landing Zone Framework (LZF)**. |
| 6 | +Welcome to the **OCI Landing Zone Framework (LZF)**. |
7 | 7 |
|
8 | | -The LZF was created by the EMEA Landing Zone Specialists, collaborating with worldwide Oracle, customers, and partners, to **simplify the OCI onboarding experience** and **reduce OCI day-one and day-two efforts**. It provides **best practices** covering the complete spectrum of OCI landing zones, from the **standards** to the **tailored** approaches. |
| 8 | +The LZF was created by the EMEA Landing Zone Specialists, collaborating with worldwide Oracle, customers, and partners, to **simplify the OCI onboarding experience** and **reduce OCI day-one and day-two efforts**. It provides **best practices** covering the complete spectrum of OCI landing zones, from the **standards** to the **tailored** approaches, including landing zone extensions for specific **workloads**. |
9 | 9 |
|
10 | 10 | |
11 | 11 |
|
12 | 12 |
|
13 | | -| APPROACH | DESCRIPTION | |
14 | | -|---|---| |
15 | | -| <a href="/landing-zones/standard_landing_zones/standard_landing_zones.md" ><img src="images/slz.png" alt= “” width="500" height=""></a> | **Prescribed** and **ready to use** solutions with a **guided setup** and **IaC**. This is the recommended approach for initial landing zone deployments covering the most-common workload scenarios. | |
16 | | -| <a href="tailored_landing_zones/tailored_landing_zones.md" ><img src="images/tlz.png" alt= “” width="500" height=""> </a> | An approach to solve **specific requirements** when the standard is not enough. These LZs run with **configuration-as-code** and are used to scale/bridge with existing **operating models**, complying with fine-grained **segregations of duties**, strong **network isolation**, and heterogeneous **workloads**. | |
| 13 | +| APPROACH | OBJECTIVE | DESCRIPTION | |
| 14 | +|---|---|---| |
| 15 | +| <a href="/landing-zones/standard_landing_zones/standard_landing_zones.md" ><img src="images/slz.jpg" alt= “” width="500" height=""></a> | **Basic Workloads** | **Prescribed** and **ready to use** solutions with a **guided setup** and **IaC**. This is the recommended approach for initial landing zone deployments covering the **most-common workload scenarios**. | |
| 16 | +| <a href="workload_landing_zones/workload_landing_zones.md" ><img src="images/wlz.jpg" alt= “” width="500" height=""> </a> | **Specific Workloads** | A set of landing zones extension ready for specific **workloads**. Each flavour has a **design** with **IaC configurations** ready to be deployed. Examples are EBS, ExaCC, OCVS, OIC, OKE, CCC, etc. | |
| 17 | +| <a href="tailored_landing_zones/tailored_landing_zones.md" ><img src="images/tlz.jpg" alt= “” width="500" height=""> </a> | **All Workloads** | An approach to solve **specific requirements** when the standard is not enough. These LZs run with **configuration-as-code** and are used to scale/bridge with existing **operating models**, complying with fine-grained **segregations of duties**, strong **network isolation**, and heterogeneous **workloads**. | |
| 18 | + |
17 | 19 |
|
18 | 20 | |
19 | 21 |
|
20 | 22 | If you're **starting with OCI landing zones**: |
21 | 23 | 1. Start with a **standard** landing zone as they're full of best practices. If it needs adjustments or **extensions on top** of the prescribed design, customize it by code or manually. |
22 | | -2. If your design is very **specific**, requiring **structural changes** to a standard landing zone, and/or you need a **highly scalable operating model**, use the **tailored** approach. |
| 24 | +2. If you have a **specific target workload** that is available as a **workload landing zone**, use it directly. If it's not available, talk to us or use the tailored approach to set up your extensions. |
| 25 | +3. If your design is very **customized**, requiring **structural changes** to a standard landing zone (IAM or Network), and/or you need a **highly scalable operating model**, use the **tailored** approach to create your solution. |
23 | 26 |
|
24 | 27 | |
25 | 28 |
|
26 | 29 | The following **assets** are also available to improve the OCI landing experience: |
27 | | -- [Executive Overview of the Available Approaches](/landing-zones/commons/EMEA_LandingZonesSpecialists_ExecOverview.pdf) |
28 | | -- [How a Tailored OCI Landing Zone Looks Like (The OCI Open LZ)](https://github.com/oracle-quickstart/terraform-oci-open-lz) |
29 | | -- [Resource Naming Conventions](/landing-zones/commons/resource_naming_conventions.md) |
30 | | -- [User Identity Management](/landing-zones/commons/user_identity_management.md) |
31 | | -- [Budgets and Tagging](/landing-zones/commons/budgets_and_tagging.md) |
| 30 | +1. **Overview**: [Executive Overview of the Available Approaches](/landing-zones/commons/EMEA_LandingZonesSpecialists_ExecOverview.pdf) |
| 31 | +2. **Solution Definition**: [Creating a Landing Zone Solution Definition (**SDD**)](/landing-zones/commons/lz_solution_definition.md) |
| 32 | +3. **Workloads**: [How an OCI Workload Landing Zone Looks Like (**EBS**)](https://github.com/oracle-quickstart/terraform-oci-open-lz/tree/master/examples/oci-ebs-lz) |
| 33 | +4. **Tailored**: [How an OCI Tailored Landing Zone Looks Like (**OCI Open LZ**)](https://github.com/oracle-quickstart/terraform-oci-open-lz) |
| 34 | +5. **Naming**: [Resource Naming Conventions for OCI](/landing-zones/commons/resource_naming_conventions.md) |
| 35 | +6. **Identity**: [OCI User Identity Management](/landing-zones/commons/user_identity_management.md) |
| 36 | +7. **Budgets**: [OCI Budgets and Tagging Recommendations](/landing-zones/commons/budgets_and_tagging.md) |
32 | 37 |
|
33 | 38 |
|
34 | 39 | |
|
0 commit comments