Skip to content

Commit 4eecde1

Browse files
authored
Update Tabs.md
1 parent cb4013b commit 4eecde1

File tree

1 file changed

+0
-40
lines changed
  • cd3_automation_toolkit/documentation/user_guide/learn_more

1 file changed

+0
-40
lines changed

cd3_automation_toolkit/documentation/user_guide/learn_more/Tabs.md

Lines changed: 0 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -59,23 +59,6 @@ Once terraform apply is done, you can view the resources under Governance -> Tag
5959

6060
On re-running the same option you will find the previously existing files being backed up under directory → \<outdir>/\<region>/backup_Tagging/\<Date>-\<Month>-\<Time>.
6161

62-
## Create Network
63-
64-
**Pre-requisite:**
65-
66-
Run the script **fetch_compartments_to_variablesTF.py**
67-
Execute CD3 Validator, to avoid any errors during the creation of VCN objects. (Check out Support for CD3 Validator for the details)
68-
69-
<ins>Fetch Compartments to Varaibles TF file:</ins>
70-
71-
This script will fetch OCIDs of all compartments that exist in the tenancy and place them in variables_\<region>.tf directory.
72-
73-
Command used to execute from OCSWork VM: (Fetch Compartments) - python fetch_compartments_to_variablesTF.py /cd3user/tenancies/<customer_name>/terraform_files
74-
75-
For other workstations - example: laptop, specify the path of 'outdir' and path of 'config' file for Python OCI - python fetch_compartments_to_variablesTF.py \<path to outdir> --configFileName \<path to config file>
76-
77-
To create network objects like VCN, subnets etc in OCI; VCNs, VCN Info, Subnets and DHCP tabs of CD3 are required to be configured.
78-
7962
## a. VCNs Tab
8063

8164
**Note:**
@@ -146,29 +129,6 @@ Output files generated:
146129
|<br>\<prefix>_nsgs.auto.tfvars<br>\<prefix>_nsg-rules.auto.tfvars</br></br>| Contains TF for NSGs in each region |
147130

148131

149-
## Export and Modify Rules
150-
151-
You can export existing security rules and route rules in OCI. On choosing **"Network"** in the SetUpOCI menu and **"Export existing secrules and RouteRules to CD3"** and **"Export existing DRG Routerules to CD3**" submenu will allow to export existing security and route rules.
152-
153-
On choosing this option, you will get a prompt to enter the Compartment Name for which you want to export the rules. When left blank, rules will be exported for all Compartments in the tenancy.
154-
155-
Exported rules are written to 'SecRulesinOCI', ‘RouteRulesinOCI’ and 'DRGRouteRulesinOCI' tab of the cd3 excel.
156-
157-
**DO NOT** open your CD3 file during the export process.
158-
159-
This option is useful when you want to present the CD3 to the customer as the Actual Representation of OCI console.(i.e provide the contents of OCI in the CD3 excel)
160-
161-
**<ins>Modify Rules</ins>**
162-
163-
On choosing **"Network"** in the SetUpOCI menu and **"Modify SecRules"** and **"modify RouteRules"** and **"Modify DRG RouteRules"** submenu will allow to modify existing route rules and security rules in OCI tenancy.
164-
165-
**SecRulesinOCI tab** – The tool reads this sheet and deletes(backs up to the backup directory) all existing security rules in OCI and replace them with the contents of this Tab.
166-
167-
**RouteRulesinOCI tab** – The tool reads this sheet and deletes(backs up to the backup directory) all existing route rules in OCI and replace them with the contents of this Tab.
168-
169-
**DRGRouteRulesinOCI tab** – The tool reads this sheet and deletes(backs up to the backup directory) all existing DRG route rules in OCI and replace them with the contents of this Tab.
170-
171-
172132
## Modify Network
173133

174134
<ins>Modify Network</ins>

0 commit comments

Comments
 (0)