odb / Paginator / ListDbSystemShapes

ListDbSystemShapes

class odb.Paginator.ListDbSystemShapes
paginator = client.get_paginator('list_db_system_shapes')
paginate(**kwargs)

Creates an iterator that will paginate through responses from odb.Client.list_db_system_shapes().

See also: AWS API Documentation

Request Syntax

response_iterator = paginator.paginate(
    availabilityZone='string',
    availabilityZoneId='string',
    PaginationConfig={
        'MaxItems': 123,
        'PageSize': 123,
        'StartingToken': 'string'
    }
)
Parameters:
  • availabilityZone (string) – The logical name of the AZ, for example, us-east-1a. This name varies depending on the account.

  • availabilityZoneId (string) – The physical ID of the AZ, for example, use1-az4. This ID persists across accounts.

  • PaginationConfig (dict) –

    A dictionary that provides parameters to control pagination.

    • MaxItems (integer) –

      The total number of items to return. If the total number of items available is more than the value specified in max-items then a NextToken will be provided in the output that you can use to resume pagination.

    • PageSize (integer) –

      The size of each page.

    • StartingToken (string) –

      A token to specify where to start paginating. This is the NextToken from a previous response.

Return type:

dict

Returns:

Response Syntax

{
    'dbSystemShapes': [
        {
            'availableCoreCount': 123,
            'availableCoreCountPerNode': 123,
            'availableDataStorageInTBs': 123,
            'availableDataStoragePerServerInTBs': 123,
            'availableDbNodePerNodeInGBs': 123,
            'availableDbNodeStorageInGBs': 123,
            'availableMemoryInGBs': 123,
            'availableMemoryPerNodeInGBs': 123,
            'coreCountIncrement': 123,
            'maxStorageCount': 123,
            'maximumNodeCount': 123,
            'minCoreCountPerNode': 123,
            'minDataStorageInTBs': 123,
            'minDbNodeStoragePerNodeInGBs': 123,
            'minMemoryPerNodeInGBs': 123,
            'minStorageCount': 123,
            'minimumCoreCount': 123,
            'minimumNodeCount': 123,
            'runtimeMinimumCoreCount': 123,
            'shapeFamily': 'string',
            'shapeType': 'AMD'|'INTEL'|'INTEL_FLEX_X9'|'AMPERE_FLEX_A1',
            'name': 'string',
            'computeModel': 'ECPU'|'OCPU',
            'areServerTypesSupported': True|False
        },
    ],
    'NextToken': 'string'
}

Response Structure

  • (dict) –

    • dbSystemShapes (list) –

      The list of shapes and their properties.

      • (dict) –

        Information about a hardware system model (shape) that’s available for an Exadata infrastructure. The shape determines resources, such as CPU cores, memory, and storage, to allocate to the Exadata infrastructure.

        • availableCoreCount (integer) –

          The maximum number of CPU cores that can be enabled for the shape.

        • availableCoreCountPerNode (integer) –

          The maximum number of CPU cores per DB node that can be enabled for the shape.

        • availableDataStorageInTBs (integer) –

          The maximum amount of data storage, in terabytes (TB), that can be enabled for the shape.

        • availableDataStoragePerServerInTBs (integer) –

          The maximum amount of data storage, in terabytes (TB), that’s available per storage server for the shape.

        • availableDbNodePerNodeInGBs (integer) –

          The maximum amount of DB node storage, in gigabytes (GB), that’s available per DB node for the shape.

        • availableDbNodeStorageInGBs (integer) –

          The maximum amount of DB node storage, in gigabytes (GB), that can be enabled for the shape.

        • availableMemoryInGBs (integer) –

          The maximum amount of memory, in gigabytes (GB), that can be enabled for the shape.

        • availableMemoryPerNodeInGBs (integer) –

          The maximum amount of memory, in gigabytes (GB), that’s available per DB node for the shape.

        • coreCountIncrement (integer) –

          The discrete number by which the CPU core count for the shape can be increased or decreased.

        • maxStorageCount (integer) –

          The maximum number of Exadata storage servers that’s available for the shape.

        • maximumNodeCount (integer) –

          The maximum number of compute servers that is available for the shape.

        • minCoreCountPerNode (integer) –

          The minimum number of CPU cores that can be enabled per node for the shape.

        • minDataStorageInTBs (integer) –

          The minimum amount of data storage, in terabytes (TB), that must be allocated for the shape.

        • minDbNodeStoragePerNodeInGBs (integer) –

          The minimum amount of DB node storage, in gigabytes (GB), that must be allocated per DB node for the shape.

        • minMemoryPerNodeInGBs (integer) –

          The minimum amount of memory, in gigabytes (GB), that must be allocated per DB node for the shape.

        • minStorageCount (integer) –

          The minimum number of Exadata storage servers that are available for the shape.

        • minimumCoreCount (integer) –

          The minimum number of CPU cores that can be enabled for the shape.

        • minimumNodeCount (integer) –

          The minimum number of compute servers that are available for the shape.

        • runtimeMinimumCoreCount (integer) –

          The runtime minimum number of CPU cores that can be enabled for the shape.

        • shapeFamily (string) –

          The family of the shape.

        • shapeType (string) –

          The shape type. This property is determined by the CPU hardware.

        • name (string) –

          The name of the shape.

        • computeModel (string) –

          The OCI model compute model used when you create or clone an instance: ECPU or OCPU. An ECPU is an abstracted measure of compute resources. ECPUs are based on the number of cores elastically allocated from a pool of compute and storage servers. An OCPU is a legacy physical measure of compute resources. OCPUs are based on the physical core of a processor with hyper-threading enabled.

        • areServerTypesSupported (boolean) –

          Indicates whether the hardware system model supports configurable database and server storage types.

    • NextToken (string) –

      A token to resume pagination.