Merge pull request #1437 from oracle-devrel/LZF-10.01

jpalmeiro · web-flow · commit 1900d8a3dfc5 · 2024-11-08T09:53:28.000+01:00
minor updates
diff --git a/landing-zones/README.md b/landing-zones/README.md
@@ -11,7 +11,7 @@ Before starting we recommend viewing a [13-minutes video](https://www.linkedin.c
 
 &nbsp; 
 
-<img src="images/framework.jpg" alt= “” width="1000" height="value">
+<img src="images/framework.jpg" alt= “” width="1100" height="value">
 
 
 
@@ -23,7 +23,7 @@ Before starting we recommend viewing a [13-minutes video](https://www.linkedin.c
 | <a href="/landing-zones/standard_landing_zones/readme.md"><img src="images/slz.jpg" alt= “” width="500" height=""></a>  | **Best Practices</br>4 Blueprints** | **Standard shapes/blueprints** for different organization scopes, **ready to use** with **design blueprints** and  **IaC configurations**. Use these models directly or tailor them to your needs.  | 
 | <a href="tailored_landing_zones/readme.md" ><img src="images/tlz.jpg" alt= “” width="500" height=""> </a>  | **Tailored Design </br> Any Shape** | An EMEA specialists approach to solve **specific requirements** when the standard models are not enough. A tailored model has **dedicated design views** to match requirements and an IaC runtime. This approach is commonly used to bridge **existing customer practices** in other CSPs. |  
 | <a href="https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/workload-extensions" ><img src="images/wext.jpg" alt= “” width="500" height=""> </a>  | **Workload Ready</br>Plug & Play** | **Complement your landing zone** with extensions ready for **specific workloads**. Each flavor has a **design** with **IaC configurations** ready to be deployed on top of standard or tailored landing zone. Examples are EBS, ExaCC, OCVS, OIC, OKE, CCC, etc. |  
-| <a href="https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons" ><img src="images/addon.jpg" alt= “” width="500" height=""> </a>  | **Addons</br>Plug & Play** | **Complement your landing zone** with **addons** full of best practices. Each **addon** can be used on top of standard or tailored landing zone. Examples are Network Hubs, Oracle Access Gorvernance, Sovereign Controls etc. |  
+| <a href="https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons" ><img src="images/addon.jpg" alt= “” width="500" height=""> </a>  | **Addons</br>Plug & Play** | **Complement your landing zone** with **addons** full of best practices. Each **addon** can be used on top of standard or tailored landing zone. Examples are Network Hubs, Oracle Access Governance, Sovereign Controls etc. |  
 | <a href="/landing-zones/commons/oci_landingzones_iac.md" ><img src="images/iac_modules.jpg" alt= “” width="500" height=""> </a>  | **Declarative</br>Terraform Modules** | Use the highly **generic** OCI Landing Zones Terraform **modules** to configure your Landing Zone instead of coding it.  |  
 
 &nbsp; 
@@ -40,8 +40,8 @@ If you're **starting with OCI landing zones**:
 The following **assets** are also available to improve the OCI landing experience:
 1. **Landing Zones**: [How a Complete OCI Landing Zone Looks Like (**OCI Open LZ**)](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities)
 2. **Workloads Extensions**: [How an OCI Workload Extensions Looks Like (**EBS Extension**)](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/workload-extensions/ebs)
-3. **Infrastructure-as-Code (IaC)**: [How We Configure and Not Code Landing Zones **(Landing Zone Modules)**](/landing-zones/commons/oci_landingzones_iac.md).
-4. **Network Hubs**: How OCI Network Hubs Look Like and How They Work (**[Network Addons](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons/oci-hub-models)**)
+3. **Infrastructure-as-Code (IaC)**: [How We Configure and Not Code Landing Zones **(Terraform Modules)**](/landing-zones/commons/oci_landingzones_iac.md).
+4. **Network Hubs**: [How OCI Network Hubs Look Like and How They Work (**Network Addons**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons/oci-hub-models))
 5. **Learn/DIY**: [How to Design and Configure OCI Landing Zones (**OCI Learn LZ**)](https://github.com/oracle-quickstart/terraform-oci-open-lz/tree/master/addons/oci-learn-lz)
 6. **Naming Conventions**: [Resource Naming Conventions for OCI](/landing-zones/commons/resource_naming_conventions.md)
 7. **Identity**: [OCI User Identity Management](/landing-zones/commons/user_identity_management.md)
diff --git a/landing-zones/commons/lz_solution_definition.md b/landing-zones/commons/lz_solution_definition.md
@@ -11,7 +11,7 @@
 
 ## **1. Introduction**
 
-Welcome to the [Landing Zone Framework (LZF)](/landing-zones/README.md) Solution Definition.
+Welcome to the [EMEA OCI Landing Zones](/landing-zones/README.md) Solution Definition.
 
 This asset provides guidance on the **landing zone design considerations**, and helps select the best **approach** and **solution** to setup and run your OCI Landing Zone.
 
@@ -81,9 +81,10 @@ Find in the table below a summary of the two approaches for OCI Landing Zones.
 &nbsp; 
 
 The general recommendation when **starting with OCI landing zones** is:
-1. Start with [**Standard Landing Zones**](/landing-zones/standard_landing_zones/readme.md) as they're full of best practices. There are [**three models/shapes**](/landing-zones/standard_landing_zones/readme.md#2-what-are-the-models-available) available for different scopes, we'll help you find the best fit [**here**](/landing-zones/standard_landing_zones/readme.md#3-decide-on-the-model-to-use).
-2. 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 Landing Zones**](/landing-zones/tailored_landing_zones/readme.md) approach to create your solution.
-3. Complementary, if you have a **specific target workload** that is available as [**Workload Extensions**](/landing-zones/workload_extensions/readme.md), use it directly on top of your landing zone. If it's not available, be free to reach out to us or use the tailored approach to set up your extensions.
+1. Start with [**Standard Landing Zones**](/landing-zones/standard_landing_zones/readme.md) as they're full of best practices. There are [**several blueprints/shapes**](/landing-zones/standard_landing_zones/readme.md#2-what-are-the-models-available) available for different scopes, we'll help you find the best fit [**here**](/landing-zones/standard_landing_zones/readme.md#3-decide-on-the-blueprint-to-use).
+2. Review our existing [**Addons**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons) catalog so you can enrich your model as needed.
+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 Landing Zones**](/landing-zones/tailored_landing_zones/readme.md) approach to create your solution. The [**OCI Open LZ**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities) is your reference model to follow and adjust.
+4. Complementary, if you have a **specific target workload** that is available as [**Workload Extensions**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/workload-extensions), use it directly on top of your landing zone. If it's not available, be free to reach out to us or use the tailored approach to set up your extensions.
 
 &nbsp; 
 
diff --git a/landing-zones/standard_landing_zones/readme.md b/landing-zones/standard_landing_zones/readme.md
@@ -13,10 +13,10 @@ A Standard Landing Zone is a reference design blueprint, full of best practices,
 1. **Complete**. A coherent – security, network, and operations – design views.
 2. **Scalable**. Scalable by design throughout organizations, teams, platforms, and projects, or workload types.
 3. **Runnable**. Tangible designs that are translatable into customer IaC Configurations.
-4. **Configurable**. Designs are implemented by human-readable IaC configurations and not code using the [OCI Landing Zone Terraform Modules]. 
+4. **Configurable**. Designs are implemented by human-readable IaC configurations and not code using the [OCI Landing Zone Modules](/landing-zones/commons/oci_landingzones_iac.md). 
 5. **Versionable**. IaC configurations are the source of truth, versioned on Git repositories.
 6. **Reusable**. Design blueprints and IaC are created, used, and adapted to new use cases.
-7. **Extendable**. Addon designs and configurations are pluggable and non-disruptive. 
+7. **Extendable**. Addon designs and configurations can be pluggable in a non-disruptive way. 
 8. **Open**. Design blueprints, IaC configurations, and IaC modules are publicly open to be used by Oracle, Customers, and Partners.
 
 
@@ -33,11 +33,11 @@ There are several **landing zone blueprints** available for different business n
 
 &nbsp; 
 
-| BLUEPRINTS  |  SIZE | DIAGRAM | DESCRIPTION | DETAILS  |  
+| LANDING ZONE | BLUEPRINTS  |  SIZE | DIAGRAM | DESCRIPTION | 
 ---|---|---|---|---|
-| **1. OCI Core Landing Zone -**</br> Quickstart Blueprint | **XS-S** | <img src="../images/slz_model1.jpg" alt= “” width="60" height="value"> | A quickstart landing zone blueprint that meets the ability to provision a hub and spoke topology and follow a general purpose three-tier architecture. | [Repository](https://github.com/oci-landing-zones/terraform-oci-core-landingzone)
-| **2. OCI Operating Entities Landing Zone -**  </br>One-OE and Multi-OE Blueprints | **M-L** | <img src="../images/slz_model2.jpg" alt= “” width="100" height="value">  | A landing zone - with several blueprints - that provides the ability to onboard **one** or **multiple operating entities (OEs)** into **one OCI tenancy**. An OE can be an organization unit, LoB, customer, partner, OpCo, subsidiary, or any type of managed service. It provides shared central services capabilities with a strong security posture and network segregation, with environments, projects, and platfoms adaptable for each OE.   | [Repository](https://github.com/oracle-quickstart/terraform-oci-open-lz)</br>[One-OE](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/master/blueprints/one-oe/readme.md)</br> [Multi-OE ](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints/multi-oe)
-| **3. OCI Operating Entities Landing Zone -**  <br>Multi-Tenancy Blueprint | **L-XXL** | <img src="../images/slz_model3.jpg" alt= “” width="400" height="value"> | This landing zone blueprint provides the ability to **onboard several organizations** into OCI using the **multi-tenancy** capabilities, with tenancies for shared/central services (e.g., Connectivity Hub) and tenancies dedicated to complete enterprise organizations such as customers, countries businesses, sub-organizations, departments, etc. It's a highly adaptable blueprint with the concept of landing zone environments, workload environments, hub-hub models, projects, and platforms, providing the highest levels of segregation on OCI. This blueprint fits any OCI flavor and it's ideal for the OCI DRCCs and Alloy use cases.  | [Multi-Tenancy](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/master/blueprints/multi-tenancy/readme.md)
+| **[OCI Core LZ](https://github.com/oci-landing-zones/terraform-oci-core-landingzone)** |  **Quickstart** | **XS-S** | <img src="../images/slz_model1.jpg" alt= “” width="60" height="value"> | A quickstart landing zone blueprint that meets the ability to provision a hub and spoke topology and follow a general purpose three-tier architecture. 
+| **[OCI Open LZ](https://github.com/oracle-quickstart/terraform-oci-open-lz)** | **[One-OE](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/master/blueprints/one-oe/readme.md) & [Multi-OE](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints/multi-oe)** | **M-L** | <img src="../images/slz_model2.jpg" alt= “” width="100" height="value">  | A landing zone - with several blueprints - that provides the ability to onboard **one** or **multiple operating entities (OEs)** into **one OCI tenancy**. An OE can be an organization unit, LoB, customer, partner, OpCo, subsidiary, or any type of managed service. It provides shared central services capabilities with a strong security posture and network segregation, with environments, projects, and platfoms adaptable for each OE.   | [OCI Open LZ](https://github.com/oracle-quickstart/terraform-oci-open-lz)</br>[One-OE](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/master/blueprints/one-oe/readme.md)</br> [Multi-OE](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints/multi-oe)
+| **[OCI Open LZ](https://github.com/oracle-quickstart/terraform-oci-open-lz)**|  [**Multi-Tenancy**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/master/blueprints/multi-tenancy/readme.md) | **L-XXL** | <img src="../images/slz_model3.jpg" alt= “” width="400" height="value"> | This landing zone blueprint provides the ability to **onboard several organizations** into OCI using the **multi-tenancy** capabilities, with tenancies for shared/central services (e.g., Connectivity Hub) and tenancies dedicated to complete enterprise organizations such as customers, countries businesses, sub-organizations, departments, etc. It's a highly adaptable blueprint with the concept of landing zone environments, workload environments, hub-hub models, projects, and platforms, providing the highest levels of segregation on OCI. This blueprint fits any OCI flavor and it's ideal for the OCI **DRCCs** and **Alloy** use cases.  
 
 
 
@@ -64,10 +64,10 @@ There are several **landing zone blueprints** available for different business n
 | STEP  |   DESCRIPTION | 
 |:---:|---|
 | 1 | **Select the most suitable shape/blueprint** taking into account **organization** scope and **workload** footprint size. | 
-| 2 | **Review the Landing Zone Design and potentially adjust** the required elements. For tailored guidelines review the [**Tailored Landing Zones**](/landing-zones/tailored_landing_zones/readme.md).| 
-| 3 | **Review the operations and related IaC Configurations**. Reflect your design on resource types and their configuration values. For guidelines review the [OCI Learn LZ](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons/oci-learn-lz) and [end-to-end operations examples](https://github.com/oracle-quickstart/terraform-oci-open-lz/tree/master/examples/oci-open-lz). | 
+| 2 | **Review the Blueprint Design and potentially adjust** the required elements. For tailored guidelines review the [**Tailored Landing Zones**](/landing-zones/tailored_landing_zones/readme.md).| 
+| 3 | **Review the operations and related IaC Configurations**. Reflect your design on resource types and their configuration values. For guidelines review the [OCI Learn LZ](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons/oci-learn-lz) and [end-to-end operations examples](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints/one-oe/runtime/one-stack) available on the [OCI Open LZ Blueprints](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints). | 
 | 4 | **Run your model** with OCI Terraform CLI, Oracle Resource Manager or your automation tooling.
-| 5 | **Extend your landing zone** with [**Workload Extensions**](/landing-zones/workload_extensions/readme.md) to reduce your efforts and time-to-value.
+| 5 | **Extend your landing zone** with [**Workload Extensions**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/workload-extensions) to reduce your efforts and time-to-value.
 
    
 &nbsp; 
