[MUSIC] Welcome to Oracle University's Oracle Cloud infrastructure training on the Oracle Autonomous Database Compartment Quotas. My name is Angela wall and I am looking forward to sharing with you About OCI compartment quotas and how they enable customers to allocate resources with a high level of flexibility. Service limits or quotas or allowances that are set on a specific resource. Do be aware that service limits are defined and set by Oracle. They're set by the service you have subscribed to, and they can change automatically based on your OCI resource usage, or by changing your account type. Let's look at a couple of examples. First of all, the service limit is based on the service you've subscribed to. The service could be a database service, where the storage is something that is controlled for you, for example, the autonomous database where storage could be anywhere from 1- 128 terabytes, that's the type of service that could be limited. Secondly, in addition to that, the service may change. So what is available for you may change based on your service. In the example of upgrading your account from always free to paid. If you're defining an autonomous database that would be limited to 10CPU maximum in the always free account. If you were to convert that account to a paid account, that limit will be lifted from 1OCPU to 128OCPUs that can be configured. Compartment quotas are very similar to service limits. However, whereas a service limit is set by Oracle compartment quotas are set by customer administrators. Now, I do want to point out that in the Dedicated Infrastructure world this is managed by the Fleet Administrator and it is one of their key roles and responsibilities. Compartment quotas are set using policy statements that are very simple and very easy to follow. And similar to the identity and access management, which we'll be seeing in the following slides. If we look at service limits and compartment quotas, keep in mind that tenancy limits, quotas, and usage can be viewed using your cloud console. The console may not display the information for all of the OCI services or resources. And that's because it only shows the information for the OCI services you have subscribed to. Also keep in mind that the usage may be greater than the limit that's available to you and that's because the limit may have been reduced after the resource was initially created. The other thing to keep in mind, is that the limits are sometimes displayed as 0. But that's not necessarily a bad thing this could be the case if the account has been suspended. Now, accounts can be suspended due to a lack of activity. Which actually means you're not being billed or charged for the resources that would potentially be consumed. This is a parent in the always free account when a database becomes idle for an extended period of time then those services or that environment is set to zero. Now, let's see how to control a resource by fixing a limit on the storage in a compartment. You will see this Oracle Cloud Service console when you log into your Oracle Cloud account. On this Oracle Cloud Service console, you'll see the hamburger menu on the top left hand corner. If you click that hamburger menu, navigate down to the governance, and administration section, and click governance you can view the limits, quotas and the usage. If you click limits, quotas and usage, it will bring you to this screen. Within this screen, it defaults to an alphabetic listing of services, compute. We're actually going to choose database in this case. Upon choosing the database, we will choose the service that we're specifically interested in. We're interested in the autonomous database data warehouse and its total storage. The service has a service limit of 128, this is a shared account that we're running in Oracle autonomous shared. And the usage is currently at 11, which means we have 11 terabytes available to us. You can also see that the compartment we are running in, is a team. So, if we click the little dots to the very right of that option it will bring up Create Quota Policy Stub. When we click that, t will then bring up a panel where we can then go in and enter in the fields there. In this case, we're going to say set database quota, ATW total storage terabytes or TB to a number in our compartment team. By doing that, we will then fix the limit in which anyone connecting to this compartment, can actually create the storage of their database. This is a way of controlling that resource. Compartments, compartments help you organize and isolate your cloud resources. You can create sub compartments in compartments to create hierarchies that are six levels deep. Most resources can be moved between compartments. Compartments also inherit any policies from their parent compartment. If you're an administrator, you'll have permission to view all compartments and work with any compartments resources. But if you're a user with limited access, you probably won't. So, a newly created compartment requires at least one policy for the user to be able to access it. Compartment quotas are similar to service limits. The biggest difference is that service limits are set by Oracle. And compartment quotas are set by administrators using policies that allow them to allocate resources with a high level of flexibility. Compartment quotas are set using policy statements within a simple declarative language that is similar to the I am policy language. You use the compartment quotas feature by creating set unset and zero policy statements to limit the availability of a given resource in a given compartment. To manage quotas in a compartment, you must belong to a group that has the correct permissions. For example, allow group QuotaAdmins to | QUOTA_READ, QUOTA_CREATE, QUOTA_DELETE, QUOTA_UPDATE, QUOTA_INSPECT ) in tenancy. Quotas can have different scopes and work at the availability domain, the region or globally. There are a few important things to understand about scope when working with compartment quotas. First, when setting a quota at the Availability Domain or AD level, the quota is allocated to each AD. So for example, setting a quota of 120x7 OCPU's A compartment actually sets a limit of 120 CPUs per AD. To target a specific AD, use the request AD parameter in the where clause. Next, regional quotas applied to each region. For example, if a quota of 10 functions is set on a compartment 10 functions will be allocated per region. To target a specific region, use the request region parameter in the where clause. And lastly, usage for sub compartments counts towards the usage for the main compartment. Here are the compartment quotas for autonomous database. When viewing the limits quotas and usage page of the console, you will see the value in A, in the service limit column for storage and OCPU resources related to autonomous transaction processing. And autonomous data warehouses with dedicated Exadata infrastructure. You might also see this value in the available column for these resources. This is because limits for these resources are based on the capacity of your provisioned Exadata hardware, and are not service limits controlled by Oracle Cloud infrastructure. If you desire compartment quota policies for either of these resources the available column will display a value for the amount that is available to be allocated based on your existing usage in the Exadata hardware Here are a few examples. The first example shows how to limit the number of Autonomous Data Warehouse resources in a compartment. This first policy Limits the Autonomous Data Warehouse CPU core count to 2 in the MyCompartment compartment. The second example shows how to set a quota for OCPU cores in an autonomous data warehouse with dedicated Exadata infrastructure. This second policy limits the number of ATP- Dedicated OCPUs to 20 in the my compartment compartment. To wrap up, compartment quotas give tenant and compartment administrators better control over how resources are consumed in Oracle Cloud infrastructure, enabling administrators to easily allocate resources to compartments using the console. Thanks so much for watching.
