Skip to main content
Version: Develop

a9s Harbor Resources Considerations

This document describes concerns and limitations to be considered when allocating resources for your a9s Harbor plans.

An a9s Harbor comes with a9s Redis and a9s PostgreSQL, so all the concerns for this service apply here.

Max Number of Buckets

Some storage backend services set a limit on the number of buckets for an account. a9s Harbor creates a bucket with every new instance, when this limit is reached, the creation of new instances might fail. The bucket is removed by the SPI when triggering a service delete. However when deleting the instances manually using bosh -d <deployment> delete-deployment, the bucket is not deleted, leaving leftovers on your account.

Billing Information

The Internet connection is required in order to send the statistics to the a9s Billing endpoint.

How to Configure the Limit for the a9s Harbor Service Plans

To ensure that the VMs in use are not overloaded, the property quota_parallel_requests was introduced.

  • quota_parallel_requests - Configure the parallel request limit of the a9s Harbor service plan. (required)

Every plan that wants to have the quota_parallel_requests limit, needs to add quota_parallel_requests to the default_placeholder_values section.

...
plans:
...
harbor-single-small:
...
default_placeholder_values:
...
quota_parallel_requests: 40
...