Add launch plugin and launch CFn template after Tenant is added

Created on 24 February 2023, almost 2 years ago
Updated 2 March 2023, almost 2 years ago

Problem/Motivation

  • Create launch plugin and launch CFn template after Tenant is added
โœจ Feature request
Status

Fixed

Version

1.0

Component

Code

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States baldwinlouie

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @baldwinlouie
  • @baldwinlouie opened merge request.
  • Status changed to Needs review almost 2 years ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States baldwinlouie

    @yas, please review this patch that adds support for launching Cloud Orchestrator after a OpenStack Tenant is created.

    - The patch adds a `Tenant Launch plugin manager` and `OpenStack Provider plugin`
    - Add `OpenStackProviderService` which takes a parameter yaml file under `openstack_provider/deployments/parameters/` and gathers the parameter values. The parameter values can be fetched from Config, the Tenant Entity, or generated using a method in the `OpenStackProviderService`
    - Adds an OpenStack Provider specific configuration page at `admin/config/services/facade/openstack_provider/settings` to ask an administrator to setup CFn values that are not to be shown to a regular Tenant user.

  • Status changed to RTBC almost 2 years ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States yas California ๐Ÿ‡บ๐Ÿ‡ธ

    @baldwinlouie

    Thank you for the patch. I'll merge the patch to 4.x and 5.x, and close this issue as Fixed.

  • Status changed to Fixed almost 2 years ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States yas California ๐Ÿ‡บ๐Ÿ‡ธ
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024