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

LZF.2024-10.01

Author: jpalmeiro

landing-zones/README.md

@@ -3,42 +3,50 @@
   
 
 
-Welcome to the **OCI Landing Zone Framework (LZF)**.
+Welcome to the **EMEA OCI Landing Zones**.
 
-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**.
+This area is owned 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**.
+
+Before starting we recommend viewing a [13-minutes video](https://www.linkedin.com/feed/update/urn:li:activity:7206600588216659968/) with EMEA OCI Landing Zones **approach** and **strategy**. Note that all the EMEA OCI Landing Zones elements are aligned with [OCI Landing Zones Framework](https://blogs.oracle.com/cloud-infrastructure/post/new-standardized-oci-landing-zones-framework) and are part of the [OCI Landing Zones Git Organization](https://github.com/oci-landing-zones) - excluding Tailored Landing Zones. 
+
+  
+
+<img src="images/framework.jpg" alt= “” width="800" height="value">
 
-Before starting we recommend viewing a [13-minutes video](https://www.linkedin.com/feed/update/urn:li:activity:7206600588216659968/) with EMEA OCI Landing Zones **approach** and **strategy**.
 
 
 &nbsp; 
 
 
-| APPROACH  |  OBJECTIVE | DESCRIPTION | 
+| AREA  |  OBJECTIVE | DESCRIPTION | 
 |---|---|---|
-| <a href="/landing-zones/standard_landing_zones/readme.md"><img src="images/slz.jpg" alt= “” width="500" height=""></a>  | **Best Practices</br>3 Shapes** | **Three standard shapes/models** 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 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="workload_extensions/readme.md" ><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 zones. Examples are EBS, ExaCC, OCVS, OIC, OKE, CCC, etc. |  
+| <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="/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; 
 
 
 If you're **starting with OCI landing zones**:
-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).
+1. Start with [**Standard Landing Zones**](/landing-zones/standard_landing_zones/readme.md) as they're full of best practices. There are [**several blueprints**](/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, feel free to reach out to us or use the tailored approach to set up your extensions.
+3. 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, feel free to reach out to us or use the tailored approach to set up your extensions.
 
 
 &nbsp; 
 
 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/oracle-quickstart/terraform-oci-open-lz)
-2. **Workloads Extensions**: [How an OCI Workload Extensions Looks Like (**OCI EBS LZ**)](https://github.com/oracle-quickstart/terraform-oci-open-lz/tree/master/workload-extensions/oci-lz-ext-ebs)
-3. **Infrastructure-as-Code (IaC)**: [The Configurable IaC approach to OCI Landing Zones **(CIS Modules)**](/landing-zones/commons/oci_landingzones_iac.md).
-4. **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)
-5. **Naming Conventions**: [Resource Naming Conventions for OCI](/landing-zones/commons/resource_naming_conventions.md)
-6. **Identity**: [OCI User Identity Management](/landing-zones/commons/user_identity_management.md)
-7. **Budgets**: [OCI Budgets and Tagging Recommendations](/landing-zones/commons/budgets_and_tagging.md)
-8. **Solution Definition**: [Creating a Landing Zone Solution Definition (**SDD**)](/landing-zones/commons/lz_solution_definition.md)
+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)**)
+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)
+8. **Budgets**: [OCI Budgets and Tagging Recommendations](/landing-zones/commons/budgets_and_tagging.md)
+9. **Solution Definition**: [Creating a Landing Zone Solution Definition (**SDD**)](/landing-zones/commons/lz_solution_definition.md)
 
 
 &nbsp; 

landing-zones/commons/oci_landingzones_iac.md

@@ -11,11 +11,11 @@
 
 ## 1.  Approach 
 
-To simplify and reduce overall efforts on OCI Landing Zones creation, deployment, and operations, we moved from classic Terraform programmatic/coded Landing Zones to **completely declarative IaC Landing Zones**. In other words, for [**Standard Landing Zones**](../standard_landing_zones/readme.md), [**Tailored Landing Zones**](../tailored_landing_zones/readme.md), and [**Workload Extensions**](../workload_extensions/readme.md), all OCI core resources are human-readable configuration files (json or yaml) - with zero coding needs.
+To simplify and reduce overall efforts on OCI Landing Zones creation, deployment, and operations, we moved from classic Terraform programmatic/coded Landing Zones to **completely declarative IaC Landing Zones**. In other words, for [**Standard Landing Zones**](../standard_landing_zones/readme.md), [**Tailored Landing Zones**](../tailored_landing_zones/readme.md), [**Workload Extensions**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/workload-extensions), and [**Addons**](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons) all OCI core resources are human-readable configuration files (json or yaml) - with zero coding needs.
 
   
 
-<img src="../images/iac_1.png" alt= “” width="500" height="value">
+<img src="../images/iac_1.jpg" alt= “” width="500" height="value">
 
 &nbsp; 
 
@@ -51,9 +51,9 @@ The diagram below presents the runtime architecture following a top-down flow, f
 
 
 
-1. **The first layer** presents the **design** elements for the [Standard Landing Zones](../standard_landing_zones/readme.md), [Tailored Landing Zones](../tailored_landing_zones/readme.md), and [Workload Extensions](../workload_extensions/readme.md).
+1. **The first layer** presents the **design** elements for the [Standard Landing Zones](../standard_landing_zones/readme.md), [Tailored Landing Zones](../tailored_landing_zones/readme.md), [Workload Extensions](../workload_extensions/readme.md), and [Addons](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/addons).
 2. **The second layer** (green) presents the IaC Configurations for all the design elements of the layer above. All designs are translated into declarative configurations.
-3. **The third layer** (grey) presents the **tooling** used to run the **configurations** (green) against one set of **modules** (yellow). Note all the terraform modules available including the orchestration on top of core resources. Any automation tool, or even a manual command, can provide this execution.
+3. **The third layer** (grey) presents the **tooling** used to run the **configurations** (light green) against one set of **modules** (darker green). Note all the terraform modules available including the orchestration on top of core resources. Any automation tool, or even a manual command, can provide this execution.
 4. **In the last layer**, it's possible to see the **OCI resources** instantiated by the Terraform modules in the previous layer.
 
 &nbsp; 
@@ -71,7 +71,7 @@ The next diagram depicts the key capabilities/benefits enabled by each building
 ## 3. The IaC Engine 
 
 
-The following Git repositories contain the Terraform engine that enables the IaC Configurable approach. For a high-level overview please refer to [OCI CIS Landing Zone Modules](https://www.ateam-oracle.com/post/cis-landing-zone-enhanced-modules).
+The following Git repositories contain the Terraform engine that enables the IaC Configurable approach. For a high-level overview please refer to [OCI Landing Zone Git Organization](https://github.com/oci-landing-zones).
 
 
 
@@ -87,7 +87,7 @@ Name         | Description
 
 &nbsp; 
 
-For **unitary examples** of usage please review the examples on each repository. For **complete end-to-end examples** using the orchestrator and several other modules please refer to the [OCI Open LZ Blueprints](https://github.com/oracle-quickstart/terraform-oci-open-lz).
+For **unitary examples** of usage please review the examples on each repository. For **complete end-to-end examples** using the orchestrator and several other modules please refer to the [OCI Open LZ Blueprints](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/blueprints).
 
 
 &nbsp;