Page History

...

The operator should be able to list capacities for specialized resources. To enable this, refactor listCapacities API to allow listing for a specific tag. When no tag is passed then return capacities for tags specified in resource.limit.*.tags global settings along with the overall capacities.

3. Allow listing tagged resource count for domains and accounts

The following APIs should return a new response parameter - taggedresources to return a list of the count of resources for the tags specified in the resource.limit.*.tags global settings and resource type - user_vm, cpu, memory, volumes, primary_storage

• listAccounts
• listDomains

4. Allow updating tagged resource counts for domains and accounts

The resource counts for domains and accounts can be recalculated using the updateResourceLimit API. API should allow update for a sub-limit for the tags specified in the resource.limit.*.tags global settings for the respective resource types - user_vm, cpu, memory, volumes, primary_storage


...

A new response parameter - tag  should be added for the API.

5. Allow updating tagged resource limits for domains and accounts

The updateResourceLimit API should allow specifying a sub-limit for the tags specified in the resource.limit.*.tags global settings for the respective resource types - user_vm, cpu, memory, volumes, primary_storage


...

The specified limit in such a case should be lower than the overall limit for the resource type.

6. Allow listing tagged resource limits for domains and accounts

The listingResourceLimits API should allow listing sub-limits for a given tag which is specified in the resource.limit.*.tags global settings for the respective resource types - user_vm, cpu, memory, volumes, primary_storage


...

A new response parameter - tag  should be added for the API.

7. Template tags must be used by different host allocators

Template tag is similar to host tag specified for a compute offering. It should be 

8. UI should not allow using a compute offering that is not suitable for the selected template

To facilitate this listServiceOfferings API should refactored to allowing list offerings for a given template.

...

When this parameter is passed API should return only those service offerings that would be suitable for instance deployment using the given template.

9. UI should not allow using a disk offering for volume creation that is not suitable for a given instance

To facilitate this listDiskOfferings API should refactored to return a flag with each of the disk offerings in the response list

...

UI should handle the filtering. As the suitability is not just a factor of DB stored values and could depend on the hypervisor, filtering from the server side will break pagination for the API.

10. Ensure during deployments (specifically instance and volume) tagged limits are enforced

During deployments, CloudStack should adhere to the overall limits for resource types. It should also adhere to tagged limits for accounts and domains. Resource reservation mechanism should be refactored to prevent any over-utilization.

...

2. New tag column in cloud.resource_count table

3. Update indexes for cloud.resource_count table

4. New tag column in cloud.resource_reservation table

5. Recreate cloud.account_view to prevent duplicates for tagged resource types

...

        .home-banner {
        background: #0052cc;
        color: #c2d6d6;
        font-size: 20px;
        padding: 20px;
        }
        .home-banner h2 {
        color: #f2f2f2;
        }

References

• https://www.cisco.com/c/en/us/solutions/service-provider/network-functions-virtualization-nfv/index.html#~virtual-routers
• https://www.cisco.com/c/en/us/solutions/service-provider/network-functions-virtualization-nfv/index.html#~featured-vnfs
• https://www.exoscale.com/marketplace/
• https://www.exoscale.com/marketplace/listing/vyos/
• https://www.exoscale.com/marketplace/listing/cisco-adaptive-security-virtual-appliance-byol/
• https://www.exoscale.com/marketplace/listing/vmware-sd-wan-by-velocloud-virtual-edge-byol/