You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
7. Select **My Configuration**, choose the **.ZIP FILE** button, click the **Browse** link and select the zip file (tf-fpp-1.2.1.zip) that you downloaded. Click **Select**.
35
-
35
+
36
36
8. Review the information. You can leave the default values.
14. Review the **Stack Information** and click **Create**
46
-
46
+
47
47
48
48
Your Stack has now been created!
49
-
49
+
50
50
51
51
## Task 2: Terraform Plan (OPTIONAL)
52
52
This is optional, you may skip directly to Step 3.
53
53
54
54
When using Resource Manager to deploy an environment, execute a **Terraform plan** to verify the configuration.
55
55
1.**[OPTIONAL]** Click **Plan** to validate your configuration.
56
-
56
+
57
57
58
58
2. Select the **Plan** button in the bottom right of the screen. This takes about a minute, please be patient.
59
-
59
+
60
60
61
61
## Task 3: Terraform Apply
62
62
When using Resource Manager to deploy an environment, execute a **Terraform Apply** to actually create the configuration. Let's do that now.
63
63
64
64
1. At the top of your page, click on **Stack Details**. click the **Apply** button.
65
65
66
-
66
+
67
67
68
68
2. Select the **Apply** button in the bottom right of the screen. This will create your cloud network, the db system and the compute instance. The job will take some time (90-120 minutes).
69
-
69
+
70
70
71
71
3. Once this job succeeds, you will get an apply complete notification from Terraform. Examine it closely.
5. Click on **Show** next to **fppserver** to show the IP address of the FPP Server. Note it down, you will need it to access it as **opc** user with the private key that you have supplied when creating the stack.
77
-
77
+
78
78
79
79
You may now [proceed to the next lab](#next) and connect to the server.
80
80
81
81
## Acknowledgements
82
82
83
83
-**Author** - Ludovico Caldara
84
-
-**Contributors** - Kamryn Vinson
85
-
-**Last Updated By/Date** - Kamryn Vinson, April 2021
84
+
-**Contributors** - Kamryn Vinson - Philippe Fierens
85
+
-**Last Updated By/Date** - Philippe Fierens, March 2023
Copy file name to clipboardExpand all lines: fpp/create-db/create-db.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ In this lab, you will:
35
35
-dbname fpplive1_site1 -datafileDestination DATA -dbtype SINGLE \
36
36
-sudouser opc -sudopath /bin/sudo
37
37
```
38
-
39
-
38
+
39
+
40
40
41
41
Notice that you have not specified the target name: the FPP server knows what is the target node (or cluster) because the working copy named `WC_db_previous_FPPC` has been provisioned there. This information is stored in the FPP metadata schema.
42
42
@@ -52,7 +52,7 @@ In this lab, you will:
52
52
sudo su - oracle
53
53
```
54
54
55
-
55
+
56
56
57
57
2. As user `oracle`, set the environment for the new database:
58
58
@@ -62,19 +62,19 @@ In this lab, you will:
62
62
The Oracle base has been set to /u01/app/oracle
63
63
[oracle@fppc ~]$
64
64
```
65
-
65
+
66
66
67
67
3. Check the status of the database with `srvctl` and `sqlplus`:
68
68
69
69
```
70
70
srvctl status database -db fpplive1_site1 -verbose
71
71
```
72
-
72
+
73
73
74
74
```
75
75
sqlplus / as sysdba
76
76
```
77
-
77
+
78
78
79
79
```
80
80
set lines 220
@@ -87,12 +87,12 @@ In this lab, you will:
87
87
```
88
88
exit
89
89
```
90
-
90
+
91
91
92
92
The database is there, wasn't that easy? You may now [proceed to the next lab](#next) and try to patch it.
93
93
94
94
## Acknowledgements
95
95
96
96
- **Author** - Ludovico Caldara
97
-
- **Contributors** - Kamryn Vinson
98
-
- **Last Updated By/Date** - Kamryn Vinson, May 2021
97
+
- **Contributors** - Kamryn Vinson - Philippe Fierens
98
+
- **Last Updated By/Date** - Philippe Fierens, March 2023
Copy file name to clipboardExpand all lines: fpp/environment/environment.md
+21-21
Original file line number
Diff line number
Diff line change
@@ -44,24 +44,24 @@ To create your LiveLabs reservation, you used a ssh key that you created on your
44
44
2. Under **List Scope**, verify that you select the **same compartment** that you received in the reservation confirmation.
45
45
3. To start the Oracle Cloud Shell, click the Cloud Shell icon at the top right of the page. *Note: Ensure before you click the console you have selected your assigned compartment or you will get an error.*
![Click on upload in cloud shell to upload private key](https://oracle-livelabs.github.io/common/labs/generate-ssh-key-cloud-shell/images/upload-key.png"")
56
56
57
57
3. To connect to the compute instance that was created for you, you will need to load your private key. This is the key that does *not* have a .pub file at the end. Locate that file on your machine and click **Upload** to process it.
![Key is uploaded](https://oracle-livelabs.github.io/common/labs/generate-ssh-key-cloud-shell/images/upload-key-select-3.png"")
65
65
66
66
5. Once finished run the command below to check to see if your ssh key was uploaded. Create a .ssh directory, and move the ssh key into your .ssh directory
67
67
@@ -78,7 +78,7 @@ To create your LiveLabs reservation, you used a ssh key that you created on your
In particular, the *Transfer port range* has been customized from the default so that is uses a fixed port range (by default it is dynamic and would require permissive firewall rules).
127
127
@@ -131,20 +131,20 @@ E.g. if you have a terminal with ssh available:
@@ -153,7 +153,7 @@ E.g. if you have a terminal with ssh available:
153
153
```
154
154
ls -l /u01/app/grid/crsdata/fpps01/rhp/
155
155
```
156
-
156
+
157
157
158
158
2. The main log file is `rhpserver.log.0`, you can use it during the workshop to verify what happens. It is verbose, but useful whenever you encounter any problems.
159
159
@@ -169,5 +169,5 @@ You have now successfully connected and verified the environment. You may now [p
169
169
## Acknowledgements
170
170
171
171
- **Author** - Ludovico Caldara
172
-
- **Contributors** - Kamryn Vinson
173
-
- **Last Updated By/Date** - Kamryn Vinson, May 2021
172
+
- **Contributors** - Kamryn Vinson - Philippe Fierens
173
+
- **Last Updated By/Date** - Philippe Fierens, March 2023
If the target server already has a GI stack (either Oracle Restart or a full GI stack), then the new working copy is provisioned as Software Only: the existing stack is untouched.
101
101
102
102
3. Verify that Restart is up and running:
103
103
104
104
```
105
105
crsctl stat res -t
106
106
```
107
-
107
+
108
108
109
109
Congratulations! You have successfully configured an Oracle Restart environment with a single command. Easy, huh? You may now [proceed to the next lab](#next).
110
110
111
111
## Acknowledgements
112
112
113
113
- **Author** - Ludovico Caldara
114
-
- **Contributors** - Kamryn Vinson
115
-
- **Last Updated By/Date** - Kamryn Vinson, May 2021
114
+
- **Contributors** - Kamryn Vinson - Philippe Fierens
115
+
- **Last Updated By/Date** - Philippe Fierens, March 2023
0 commit comments