Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.Problem/Motivation
Add Tenant entity to Facade module and its associated CRUD pages.
The entity holds information on launching Cloud Orchestrator using CFn templates.
Issue fork facade-3340656
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
baldwinlouie commented@yas, Please review this patch.
I decided to use the cloud_config->aws_cloud/k8 entity type to bundle model for Tenant. This way, if we want to have different Tenant types in the future, it is possible. There is a submodule called `tenant_providers/openstack_provider`, which provides the `Openstack Tenant` bundle. The bundle is fieldable.
1. It adds the Tenant entity. It then adds an entity bundle called `OpenStack`.
2. Sets up a `Tenant` link in the main menu
3. It adds any/own permission checking for Tenant entity.
4. During Tenant creation, I think it is useful to ask for username and email. (We can default it to some other value) This will be sent to CFn to create Cloud Orchestrator. My plan is to not ask for password because we can have Drupal send a `one-time` login link during user creation. The user can then login and update their password.
5. The Tenant creation form shows a `Region` select box. Right now it doesn't do anything, but it will be used to to determine which regions to create after saving the Tenant.
6. I've moved the `OpenStack Region` configuration entity into the `openstack_provider` module to keep it implementation specific.
I don't have an hook_update_N yet, so you will need to uninstall the facade module and re-enable it to get all the new features.
To use this, the order of operations is
1. Enable the module
2. Create your OpenStack Regions
3. Create the Tenant entities.
Comment #4
yas@baldwinlouie
Thank you for the update. It looks good, and can you fix the following conding standard error?
Thanks
Comment #5
baldwinlouie commented@yas, the coding issue has been fixed.
Comment #6
yas@baldwinlouie
Thank you for the update. It looks good, so I'll merge the patch to
5.x, and close this issue as Fixed.Comment #8
yas