Handle OpenStack resources for Octavia Amphora by operator

Summary

The octavia-operator (!2679 (merged)) currently doesn't create all required resources in OpenStack for an OctaviaDeplyment to become fully functional. Currently those resources have to be created manually (see Octavia operator - Yaook documentation). Ideally they should be created automatically.

Use cases

• Manual configuration steps are automated
• Allow smooth cluster bootstrap

Proposal

The following resources should be handled by operator:

• typical Octavia roles, but at least
  • load-balancer_admin and
  • load-balancer_member
• Amphora image(s) uploaded from URL and tagged with the tag given by controller_worker.amp_image_tag (default amphora)
• Amphora flavor(s) with the default flavor id set to controller_worker.amp_flavor_id (default octavia-amphora)
• adjust the quotas of the service project
• if controller_worker.amp_ssh_key_name is present create "key-pair" for the octavia service user from given public key named as the value of controller_worker.amp_ssh_key_name.

It is to be decided if this should be handled by the Yaook Octavia operator or a separate operator

Specification

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this issue are to be interpreted in the spirit of RFC 2119, even though we're not technically doing protocol design.