|
| 1 | +# STEP1. ORM ONE-OE Deployment Steps <!-- omit from toc --> |
| 2 | + |
| 3 | + |
| 4 | +## **Using Output and Dependencies features with ORM** |
| 5 | + |
| 6 | +Our Landing Zone extensions are designed to integrate seamlessly with our core Landing Zone models, such as ONE-OE or Multi-OE. We onboard a LZ extension as an additional operation performed after the initial deployment of the core Landing Zone. |
| 7 | + |
| 8 | +When you press the provided magic button, a new ORM stack is created. Follow these steps: |
| 9 | +1. Accept terms, wait for the configuration to load. |
| 10 | +2. Set the working directory to “rms-facade”. |
| 11 | +3. Set the stack name you prefer. |
| 12 | +4. Set the terraform version to 1.5.x. Click Next. |
| 13 | +5. In our example, we include the required JSON files stored in our open Landing Zone GitHub repository. Running it as-is will deploy the ONE-OE Landing Zone in your tenancy. However, if you want to use the **Dependencies** and **Output** features, some minor modifications will be necessary. Click next. |
| 14 | +6. Un-check run apply. Click Create. |
| 15 | + |
| 16 | +<img src="../content/MagicButton.png" width="1000" height="auto"> |
| 17 | + |
| 18 | +To minimize customizations and leverage the provided extension templates, we highly recommend using the output feature. This feature automatically generates a file containing key-resource pairs, simplifying subsequent operational deployments. |
| 19 | + |
| 20 | +To store the Json files in a OCI bucket follow the next steps: |
| 21 | + |
| 22 | +# Create your own OCI Bucket <!-- omit from toc --> |
| 23 | + |
| 24 | +1. **Main Menu-> Storage -> Buckets** |
| 25 | +2. **Create a new Bucket**. |
| 26 | + |
| 27 | +<img src="../content/Bucket.png" width="1000" height="auto"> |
| 28 | + |
| 29 | + |
| 30 | +# Upload your customized JSON files |
| 31 | + |
| 32 | +Click on each file to download it, and make any necessary changes if required. |
| 33 | + |
| 34 | +* IAM: |
| 35 | +[oci_open_lz_one-oe_iam.auto.tfvars.json](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/v2.2.0-oneoe_v2/blueprints/one-oe/runtime/one-stack/oci_open_lz_one-oe_iam.auto.tfvars.json) |
| 36 | +* Security: |
| 37 | +[oci_open_lz_one-oe_security_cisl1.auto.tfvars.json](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/v2.2.0-oneoe_v2/blueprints/one-oe/runtime/one-stack/oci_open_lz_one-oe_security_cisl1.auto.tfvars.json) |
| 38 | +* Network: |
| 39 | +[oci_open_lz_hub_a_network_light.auto.tfvars.json](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/v2.2.0-oneoe_v2/blueprints/one-oe/runtime/one-stack/oci_open_lz_hub_a_network_light.auto.tfvars.json) |
| 40 | +* Observability: |
| 41 | +[oci_open_lz_one-oe_observability_cisl1.auto.tfvars.json](https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/blob/v2.2.0-oneoe_v2/blueprints/one-oe/runtime/one-stack/oci_open_lz_one-oe_observability_cisl1.auto.tfvars.json) |
| 42 | + |
| 43 | +<img src="../content/UploadBucket.png" width="1000" height="auto"> |
| 44 | + |
| 45 | +Upload the files to your new bucket or drag and drop them directly. |
| 46 | + |
| 47 | +<img src="../content/UploadObjects.png" width="1000" height="auto"> |
| 48 | + |
| 49 | +You can now view the uploaded files in your bucket, giving you full control over them. |
| 50 | + |
| 51 | +<img src="../content/BucketFiles.png" width="1000" height="auto"> |
| 52 | + |
| 53 | + |
| 54 | + |
| 55 | +# Update the ORM with your own JSON links |
| 56 | + |
| 57 | +In the configuration variables page: |
| 58 | + |
| 59 | +1. Review the region selected for the deployment. |
| 60 | +2. Set the configuration source to OCI bucket. |
| 61 | +3. Enter the name of the bucket created in the previous step. |
| 62 | +4. Remove the default files in the Configuration Files section and upload the four new updated files to the bucket. |
| 63 | +5. In the Output Files section, click 'Save Output' and specify a folder where the output files will be saved. |
| 64 | +6. Click next. |
| 65 | +7. Un-check run apply. Click Create. |
| 66 | + |
| 67 | +<img src="../content/ORMUpdated.png" width="1000" height="auto"> |
| 68 | + |
| 69 | + |
| 70 | +First, execute a plan job (1) to review all the resources that Terraform will create. Once verified, proceed to run the apply job (2) to initiate the deployment. |
| 71 | + |
| 72 | +<img src="../content/ORMJobs.png" width="500" height="auto"> |
| 73 | + |
| 74 | +After deployment, you can visit your bucket to check the new files created using the output option. |
| 75 | + |
| 76 | +<img src="../content/output.png" width="1000" height="auto"> |
| 77 | + |
| 78 | +Example of compartment_output.json |
| 79 | + |
| 80 | +``` |
| 81 | +{"compartments": |
| 82 | +{ |
| 83 | +"CMP-LANDINGZONE-P-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-NETWORK-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-NETWORK-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PLATFORM-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PROJ1-APP-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PROJ1-DB-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PROJ1-INFRA-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PROJ1-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-PROJECTS-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-P-SECURITY-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PLATFORM-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-NETWORK-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PLATFORM-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PROJ1-APP-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PROJ1-DB-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PROJ1-INFRA-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PROJ1-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-PROJECTS-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PP-SECURITY-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-PREPROD-KEY":{"id":"ocid1.compartment.oc1..xxx"}, |
| 84 | +"CMP-LZP-PROD-KEY":{"id":"ocid1.compartment.oc1..xxx"},"CMP-LZP-SECURITY-KEY":{"id":"ocid1.compartment.oc1..xxx"} |
| 85 | +} |
| 86 | +} |
| 87 | +``` |
| 88 | + |
| 89 | +# License <!-- omit from toc --> |
| 90 | + |
| 91 | +Copyright (c) 2025 Oracle and/or its affiliates. |
| 92 | + |
| 93 | +Licensed under the Universal Permissive License (UPL), Version 1.0. |
| 94 | + |
| 95 | +See [LICENSE](/LICENSE) for more details. |
0 commit comments