diff --git a/exadata-database-service-on-cc-masterclass/workshops/ocw23-tenancy/manifest.json b/exadata-database-service-on-cc-masterclass/workshops/ocw23-tenancy/manifest.json index 70700ae..79d660d 100644 --- a/exadata-database-service-on-cc-masterclass/workshops/ocw23-tenancy/manifest.json +++ b/exadata-database-service-on-cc-masterclass/workshops/ocw23-tenancy/manifest.json @@ -1,5 +1,5 @@ { - "workshoptitle": "Deliver Exadata Database Performance and Scale with Oracle Cloud Master Class", + "workshoptitle": "Exadata Database Service on Cloud@Customer Masterclass", "help": "livelabs-help-db_us@oracle.com", diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md index 58362ac..5dab537 100644 --- a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md +++ b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/configure-notifications-for-exascale-ecpu.md @@ -1,21 +1,56 @@ -# Configure Notifications for Enabled OCPU or License Type change +# Configure & Validate Notifications for Monitoring ECPU Scaling changes ## Introduction -This lab walks you through the steps to configure notifications to get notified for VM Cluster Event Types such as Enabled OCPU or License Type change. +The OCI Notifications service communicates when something happens with your resources in Oracle Cloud Infrastructure. + +**How Notifications Work?** + +The Notifications service lets you to set up communication channels for publishing messages using topics and subscriptions. When a message is published to a topic, the Notifications service sends the message to all of the topic's subscriptions. + +![Introduction Notifications](./images/notifications-events-intro.png "Introduction Notifications") + +**Notifications Concepts** + +The following concepts are essential to working with OCI Notifications Service: + +***Notification*** - A configuration for sending messages, such as an alarm or event rule. Each message is sent to subscriptions in the specified topic. + +***Subscription*** - An endpoint for a topic. Published messages are sent to each subscription for a topic. + + You can get human-readable messages through supported subscription protocols: + + * **Email** + * **Function** + * **HTTPS (Custom URL)** + * **PagerDuty** + * **Slack** + * **SMS** + +***Topic*** - A communication channel for sending messages to subscriptions. Each topic name is unique across the tenancy. + +***Event Rules*** - When triggered, an event rule sends an event message to the configured topic. Notifications then deliver the message to active subscriptions. + +***Database Service Events*** - Database Service Events enables you to be notified about health issues with your Oracle Databases or other components on the Database Cloud Service. + +**Create Events Rule to Create Notification Automation for Database Service Events** + +The Database Service Events feature implementation generates events for Data Plane operations and conditions and Notifications by leveraging the existing OCI Events service and Notification service. Users can subscribe to the Database Service Events and receive notifications. To receive notifications, subscribe to the Database Service Events and get notified using the Oracle Notification service. + +This lab walks you through the steps to configure & validate notifications for monitoring ECPU Scaling changes. Estimated Lab Time: 15 minutes - +Watch the video below for a quick walk-through of the lab. +[Configure & Validate Notifications for Monitoring ECPU Scaling changes](youtube:"placeholder") + ### Objectives -- After completing this lab, you should be able to configure notifications and events rules for Exadata Database Service on Cloud@Customer +- After completing this lab, you should be able to configure notifications and events rules for monitoring ECPU Scaling changes for Exadata Database Service on Exascale Infrastructure ### Prerequisites @@ -23,17 +58,17 @@ This lab requires completion of the following: * Completion of **Lab1** -## Task 1: Configure Notification Topic and Subscription for Enabled OCPU or License Type change +## Task 1: Configure Notification Topic and Subscription for Enabled ECPU change 1. Open the navigation menu and click **Developer Services**. Under **Application Integration**, click **Notifications**. ![Navigate to Notifications](./images/navigate-notifications.png " ") -2. **Topics** page is selected by default, select your ***Assigned Compartment*** and Click **Create Topic**. +2. The **Topics** page is selected by default, select your ***Assigned Compartment*** and Click **Create Topic**. ![Click Create Topic](./images/create-topic.png " ") -3. Provide the Topic name. For this lab, use ***MyExaDBCCTopic*** for the Topic name. +3. Provide the Topic name. For this lab, use ***MyExaDBXSTopic*** for the Topic name. ![Provide Topic display name and Create Topic](./images/create-topic-name.png " ") @@ -41,11 +76,11 @@ This lab requires completion of the following: ![Click Create Topic](./images/click-create-topic.png " ") - Once Topic has been created you will see the created Topic with the state of ***Active*** + Once the Topic has been created, you will see the created Topic with the state of ***Active***. ![Display Topic Status](./images/create-topic-active.png " ") -5. Click the name of the Topic you created to open the **Topic Details** page +5. Click the name of the Topic you created to open the **Topic Details** page. ![Click on Created Topic](./images/click-on-created-topic.png " ") @@ -53,30 +88,30 @@ This lab requires completion of the following: ![Click Create Subscription](./images/create-subscriptions.png " ") -7. In the Create Subscription panel, for **Protocol**, select ***Email***. Provide your ***assigned Email Address*** then Click **Create** +7. In the Create Subscription panel, for **Protocol**, select ***Email***. Provide your ***assigned Email Address***, then Click **Create** ![Create Subscription](./images/click-create-subscription.png " ") >**Note:** Notifications creates the email subscription and sends a confirmation URL to your assigned email address. - The subscription is ***pending*** until confirmation is received + The subscription is ***pending*** until confirmation is received. ![Subscription Pending Status](./images/subscription-pending-status.png " ") -8. Open your assigned Email, Check for the ***OCI Notifications Service Subscription Confirmation*** email and Click on the ***Confirm subscription*** link +8. Open your assigned Email, Check for the ***OCI Notifications Service Subscription Confirmation*** email, and Click the ***Confirm subscription*** link. ![Confirm Subscription](./images/confirm-subscription.png " ") - By clicking the confirmation link, it will launch a browser displaying subscription has been confirmed and that you have subscribed your assigned Email to the Topic you have selected. + By clicking the confirmation link, it will launch a browser displaying that the subscription has been confirmed and that you have subscribed your assigned Email to the Topic you selected. ![Subscription Confirmation Display](./images/subscription-confirmation-page.png " ") - You can now see the subscription is now ***Active*** + You can now see that the subscription is ***Active***. ![Subscription Active](./images/subscription-active.png " ") -## Task 2: Create Events Rule to create notification automation based on Enabled OCPU or License Type change +## Task 2: Create Events Rule to Create Notification Automation for Enabled ECPU Change 1. Open the navigation menu and click **Observability & Management**. Under **Events Service**, click **Rules**. @@ -86,7 +121,7 @@ This lab requires completion of the following: ![Click Create Rule](./images/click-create-rule.png " ") -3. In the Create Rule panel, provide the Rule name. For this lab, use ***MyExaDBCCEventsRule***. +3. In the Create Rule panel, provide the Rule name. For this lab, use ***MyExaDBXSEventsRule***. ![Create Events Rule](./images/create-events-rule.png " ") @@ -94,7 +129,7 @@ This lab requires completion of the following: * In the **Rule Conditions** section, For Condition, Select ***Event Type***. * For **Service Name**, select ***Database*** - * For **Event Type**, Select ***VM Cluster - Update Begin*** and ***VM Cluster - Update End*** + * For **Event Type**, Select ***Exadb VM Cluster - Update Begin*** and ***Exadb VM Cluster - Update End*** ![Configure Rule Conditions](./images/configure-rule-conditions.png " ") @@ -102,7 +137,8 @@ This lab requires completion of the following: * In the **Actions** section, For **Action Type**, Select ***Notifications***. * For **Notifications Compartment**, select your ***Assigned Compartment*** - * For **Topic**, Select ***MyExaDBCCTopic*** + * For **Topic**, Select ***MyExaDBXSTopic*** + ![Configure Actions](./images/configure-actions.png " ") @@ -110,13 +146,94 @@ This lab requires completion of the following: ![Create Rule](./images/create-rule.png " ") +## Task 3: Validate the Current VM Cluster Resource Allocation and Scale up the Enabled ECPUs using the Console + +1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Exascale Infrastructure**. + +2. Select your ***Assigned Compartment***, and Click your assigned **VM Cluster** named ***MyDemoVMClusterXX***. + + ![Navigate to the VM Cluster ](./images/navigate-vmcluster.png "Navigate to the VM Cluster") + + The VM Cluster Details page displays information about the selected VM cluster. Under the **Resource allocation**, pay attention to the number of ***Enabled ECPUs:*** + + ![Navigate to the Resource allocation](./images/resource-allocation.png "Navigate to the Resource allocation") + +3. In the VM Cluster Details page, Click **Scale VM Cluster**. + + ![Scale VM Cluster](./images/scale-vmcluster.png "Scale VM Cluster") + + ![View Enabled ECPU](./images/current-ecpu.png "View Enabled ECPU") + + Scale Up the number of ***ECPUs enabled per VM*** from ***8 ECPU*** to ***12 ECPU*** + + ![Scale Up ECPU](./images/scale-ecpu.png "Scale Up ECPU") + + +4. Click **Save Changes** + + >**Note:** ECPU scaling activities are done online with no downtime. Once the scale up operation is complete, the VM Cluster status changes from ***Updating*** to ***Available***. + +## Task 4: List VM Cluster Configuration using CLI + +To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***. + +1. In the VM Cluster Details page, Copy the VM Cluster OCID by clicking on the ***copy*** button in the ***OCID*** field under the **General Information** section. + + ![copy vmcluster ocid](./images/copy-vmcluster-ocid.png "copy vmcluster ocid") + + Paste the VM Cluster OCID to a text editor. + +2. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. + + ![navigate to oci cloudshell](./images/oci-cloud-shell.png "navigate to oci cloudshell") + + This displays the Cloud Shell in a "drawer" at the bottom of the console: + + ![oci cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") + +3. Run the OCI CLI Command to get the VM Cluster Configuration. + + >**Note:** Replace ***{VMClusterId}*** with VM Cluster OCID copied from *(Task 4 Step 1)* + ``` + -You may now **proceed to the next lab** + oci db exadb-vm-cluster get --exadb-vm-cluster-id {VMClusterID} --query 'data.{DisplayName:"display-name", EnabledECPU:"enabled-e-cpu-count",LifecycleState:"lifecycle-state"}' + + + ``` + + After running the command, you will see similar output below. + + ![show new enabled ecpus](./images/show-new-enabled-ecpu-ocicli.png "show new enabled ecpus") + + You can see the new ***Enabled ECPU*** for the VM Cluster and with the ***Lifecycle State*** of ***Available***. + +## Task 5: Confirm Notifications output in the notification email that was configured + +1. Open your assigned email. You should be receiving two notification emails. + + Review the details of the following notification email events: + + * Start of the ECPU scale up operation - ***(updateexadbvmcluster.begin)*** + + ![Image showing sample notification email for update vm cluster begin](./images/begin-notification.png "Image showing sample notification email for update vm cluster begin") + + * End of the ECPU scale up operation ***(updateexadbvmcluster.end)*** + + ![Image showing sample notification email for update vm cluster begin](./images/end-notification.png "Image showing sample notification email for update vm cluster begin") + + The Notification email for the Update VM Cluster Events shows the before and After VM Cluster ECPU Allocation. + + Pay attention to the following fields from the notification email message: + * ***CPU Core Count*** + * ***Reserved CPU Core Count*** + * ***Enabled ECPU Core Count*** + * ***Reserved ECPU Core Count*** ## Learn More -* Click [here](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-customer-events.html#GUID-1BDBB213-B153-48F9-BE06-D85CAD6386B8) to learn more about Exadata Database Service on Cloud@Customer Events. +* Click [here](https://docs.oracle.com/en-us/iaas/exadb-xs/doc/exadata-cloud-infrastructure-events.html) to learn more about Oracle Exadata Database Service on Exascale Infrastructure Events. ## Acknowledgements @@ -124,4 +241,4 @@ You may now **proceed to the next lab** * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Leo Alvarado, Product Management, September 2023. +* **Last Updated By** - Leo Alvarado, Product Management, August 2024. diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/begin-notification.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/begin-notification.png new file mode 100644 index 0000000..19bbf8f Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/begin-notification.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png index 71e0509..5cea5bb 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-create-topic.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png index b2de86d..e73b3e7 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/click-on-created-topic.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png new file mode 100644 index 0000000..94d968e Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png index 099cf7e..708c9cb 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-actions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png index 623c617..4166697 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/configure-rule-conditions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png index b76d67d..4de451b 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/confirm-subscription.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png new file mode 100644 index 0000000..81674f1 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/copy-vmcluster-ocid.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png index e34a16f..de83859 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-events-rule.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png index 0d60b35..89f6245 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-rule.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png index f496fd0..b16c295 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-subscriptions.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png index dad7582..f6b702d 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-active.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png index ef6825e..3b749cb 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/create-topic-name.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/current-ecpu.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/current-ecpu.png new file mode 100644 index 0000000..02a9a80 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/current-ecpu.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png new file mode 100644 index 0000000..02a9a80 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/enabled-ecpu.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/end-notification.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/end-notification.png new file mode 100644 index 0000000..0fec12f Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/end-notification.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png new file mode 100644 index 0000000..d3d5728 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/navigate-vmcluster.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png new file mode 100644 index 0000000..5b4be29 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/notifications-events-intro.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png new file mode 100644 index 0000000..7154802 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/resource-allocation.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/resource-allocation.png new file mode 100644 index 0000000..2a76420 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/resource-allocation.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png new file mode 100644 index 0000000..f361b4a Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-ecpu.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png new file mode 100644 index 0000000..3ae47c6 Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/scale-vmcluster.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png new file mode 100644 index 0000000..360a51e Binary files /dev/null and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/show-new-enabled-ecpu-ocicli.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png index cb68e09..4b198b0 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-active.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png index 27b8a0c..b56b50f 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-confirmation-page.png differ diff --git a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png index cbd156a..2814d23 100644 Binary files a/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png and b/exadata-database-service-xs/configure-notifications-for-exascale-ecpu/images/subscription-pending-status.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png index c420124..e8e4cfc 100644 Binary files a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshell.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png index ee78be0..d5b5bf0 100644 Binary files a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/cloudshelllaunch.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png new file mode 100644 index 0000000..c8b0928 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-details-page.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png new file mode 100644 index 0000000..a53ee3e Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/exascale-storage-vault-list.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png new file mode 100644 index 0000000..be0383b Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/get-storage-vault-details.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png index ad2d999..b30b28f 100644 Binary files a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/navigateocimenu.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png new file mode 100644 index 0000000..7154802 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/oci-cloud-shell.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png new file mode 100644 index 0000000..7420932 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-available.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png new file mode 100644 index 0000000..4214ac7 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault-updating.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png new file mode 100644 index 0000000..772da36 Binary files /dev/null and b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/images/scale-up-storage-vault.png differ diff --git a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md index e0266df..2e1bc7b 100644 --- a/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md +++ b/exadata-database-service-xs/scale-exascale-storage-vault-resources-using-oci-console/scale-exascale-storage-vault-resources-using-oci-console.md @@ -1,29 +1,23 @@ -# Scale Exadata VM Cluster Resources using OCI CLI +# Scale Exascale Storage Vault Resources ## Introduction -The OCI CLI is a small footprint tool that you can use on its own or with the Console to perform Database Cloud Services resource tasks and other OCI tasks. The CLI provides the same core functionality as the Console, plus additional commands. Some of these, such as the ability to run scripts, extend the Console's functionality. +This lab walks you through the steps to Scale the Exascale Storage Vault Resources using the OCI Console. -**Cloud Shell**: The CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell. - -**Oracle Linux Cloud Developer image**: The CLI is pre-installed on the Oracle Linux Cloud Developer platform image. For more information. +Estimated Time: 10 minutes -The CLI is built on the Oracle Cloud Infrastructure SDK for Python and runs on Mac, Windows, or Linux. The Python code makes calls to Oracle Cloud Infrastructure APIs to provide the functionality implemented for the various services. These are REST APIs that use HTTPS requests and responses. +Watch the video below for a quick walk-through of the lab. +[Scale Exascale Storage Vault Resources](youtube:"placeholder") -This lab walks you through the steps to Scale the Exadata VM Cluster OCPU resource using OCI CLI. -Estimated Time: 10 minutes - - ### Objectives -- After completing this lab, you should be able to scale Exadata VM Cluster OCPU resource using OCI CLI +- After completing this lab, you should be able to scale the Exascale Storage Vault Resources using the OCI Console. +- List Exascale Storage Vault configuration using CLI ### Prerequisites @@ -33,57 +27,81 @@ This lab requires the completion of the following: * Completion of **Lab1** -## Task 1: Scale Exadata VM Cluster OCPU using OCI CLI +## Task 1: Scale the Exascale Storage Vault Resources using the OCI Console -1. Open the navigation menu. Under **Oracle Database**, click **Exadata Database Service on Cloud@Customer**. +1. Open the navigation menu. Under ***Oracle Database***, Click ***Oracle Exadata Database Service on Exascale Infrastructure***. - ![navigage oci console](./images/navigateocimenu.png " ") + ![navigate oci console](./images/navigateocimenu.png " ") -2. In the left rail, **Exadata VM Clusters** is selected by default. Select your assigned Compartment ***MyCompartmentXX***. +2. On the left rail, click **Exascale Storage Vaults**. - Click on the name of your assigned VM Cluster ***MyVMClusterXX***. The VM Cluster Details page displays information about the selected VM cluster. + Select the name of your assigned Vault ***MyDemoStorageVaultXX*** that you want to scale. + + ![Display Exascale Storage Vaults](./images/exascale-storage-vault-list.png "Display Exascale Storage Vaults") - Under the **General Information**, In the OCID Field. Click on **Show** to display the VM Cluster OCID, and Click on **Copy** and paste the **VM Cluster OCID** to your notepad or text editor. +3. The Exascale Storage Vault Details page displays information about the selected Vault. + + Click on ***Scale storage vault***. - Under the **Resource allocation**, pay attention to the number of ***OCPUs:*** which has the value of ***6*** - - ![vm cluster details page](./images/vmcluster-details-page.png " ") + ![Display Exascale Storage Vaults](./images/exascale-storage-vault-details-page.png "Display Exascale Storage Vaults") -3. To use OCI CLI for this lab, we will be using the ***Cloud OCI Shell tool***, where CLI is pre-configured with your credentials and ready to use immediately from within Cloud Shell in the OCI Web Console. + On the Scale Storage Vault dialog, enter a number for the capacity for High Capacity storage. + >**Note:** This number should be the value for the total storage that you want to have provisioned after the scaling operation completes. + - Click the Cloud Shell/Code Editor icon in the Console header and select Cloud Shell from the drop-down menu. + + For this lab, enter the value of ***400*** for the ***Storage capacity for Databases (GB)***, as we will scale up the Exascale Database Storage Vault from **300 GB to 400 GB**. + + ![Scale Exascale Database Storage Vault](./images/scale-up-storage-vault.png "Scale Exascale Database Storage Vault") + +4. Click ***Save Changes***. Your Vault will be scaled automatically. - ![oci cloudshell](./images/cloudshell.png " ") + >**Note:** Once the scale up operation is complete, the Exascale Storage Vault status will change from ***Updating*** to ***Available***. + + ![copy storage vault ocid](./images/scale-up-storage-vault-updating.png "copy storage vault ocid") + + In the Exascale Storage Vault Details page, Copy the Storage Vault OCID by clicking the ***copy*** button in the **OCID** field under the **General Information** section. + Paste the copied ***Exascale Storage Vault OCID*** to a text editor. + + ![copy storage vault ocid](./images/scale-up-storage-vault-available.png "copy storage vault ocid") + +## Task 2: List Exascale Storage Vault Configuration using CLI + +To use OCI CLI for this lab, we will be using the ***OCI Cloud Shell tool***. + +1. Click the **Developer tools** icon in the console header and select ***Cloud Shell*** from the drop-down menu. + + ![navigate to oci cloudshell](./images/cloudshell.png "navigate to oci cloudshell") This displays the Cloud Shell in a "drawer" at the bottom of the console: - ![oci cloudshell](./images/cloudshelllaunch.png " ") + ![oci cloudshell launch](./images/cloudshelllaunch.png "oci cloudshell launch") -4. Run the OCI CLI Command to Scale down the **VM Cluster OCPU Resources** from **6 OCPUs** to **4 OCPUs** +2. Run the OCI CLI Command to get the Exascale Storage Vault Configuration. - >**Note:** Replace ***{vmClusterId}*** with VM Cluster OCID copied from *(Task 1 Step 2)* + >**Note:** Replace ***{ExascaleVaultID}*** with the Exascale Storage Vault OCID copied from *(Task 1 Step 4)* ``` - oci db vm-cluster update --vm-cluster-id {vmClusterId} --cpu-core-count 4 --query 'data.{VMClusterOCID:id, DisplayName:"display-name", LifecycleState:"lifecycle-state", CompartmentOCID:"compartment-id"}' + oci db exascale-db-storage-vault get --exascale-db-storage-vault-id {ExascaleVaultID} ``` - ![scale number of ocpus](./images/scale-ocpu.png " ") - After running the command, you will see similar output below. - ![LifecycleState of updating is displayed for scale number of ocpus](./images/scale-vm-cluster-updating.png " ") - - While the scale up process is running, you can see the LifecycleState of the VM cluster is changed to ***Updating***. Copy the ***Compartment OCID*** from the extracted values of the OCI CLI command results and paste it in your notepad or text editor for later use. + ![show storage vault details](./images/get-storage-vault-details.png "show storage vault details") -You may now **proceed to the next lab** + The output of the command displays information about the configuration of the selected ***Exascale Storage Vault***, such as: -## Learn More + * ***Storage Vault Display Name*** + * ***Exascale Database Storage Capacity Available size in gbs*** + * ***Exascale Database Storage Capacity Total size in gbs*** + * ***Lifecycle state*** + * ***Exascale Storage Vault Associated VM Cluster Count and OCID*** -* Click [here](https://docs.oracle.com/en/engineered-systems/exadata-cloud-at-customer/ecccm/ecc-manage-vm-clusters.html#GUID-B9529795-C3D0-423A-B83F-BDD96AB29E32) to learn more about Scaling Up or Scaling Down the VM Cluster Resources for Exadata Database Service on Cloud@Customer. +***Congratulations!!!*** You may now **proceed to the next lab**. ## Acknowledgements @@ -91,4 +109,4 @@ You may now **proceed to the next lab** * **Contributors** - Tammy Bednar, Product Management -* **Last Updated By** - Leo Alvarado, Product Management, September 2023. +* **Last Updated By** - Leo Alvarado, Product Management, August 2024.