Common services model for multi-cloud platform
A platform-as-a-service infrastructure and application lifecycle manager is configured to implement a common services model to deploy selected services from a common set of services to service domains hosted on multiple different cloud platforms by abstracting dependence on availability of various additional supporting services, such as services that are platform-specific. The platform-as-a-service infrastructure and application lifecycle manager may also manage a lifecycle of available services, such as managing upgrades and/or patches to services.
1. At least one non-transitory computer-readable storage medium including instructions that, when executed by a computing node, cause the computing node to:
receive a request to provide access to or enable a common service for a project hosted on both a first service domain of a first computing platform and a second service domain hosted on a second computing platform having a different architecture than the first computing platform;
determine a scope of the common service; and
bind the common service to the project or instantiate the common service in the project based on the scope of the common service.
2. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to bind the common service to the project in response to the scope of the common service being a service domain-level scope.
3. The at least one computer-readable storage medium of claim 2 , wherein the instructions further cause the computing node to bind a second version of the common service to the project in response to receipt of a second request, wherein the second version of the common service has different configuration settings than the common service.
4. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to instantiate the common service in the project in response to the scope of the common service being a project-level scope.
5. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to apply received configuration setting selections to the common service.
6. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to provide access to the common service to clients external to the project in response to receipt of a user selection.
7. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to monitor health of the common service after deployment to the first and second service domains.
8. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to monitor a service-specific entity report from the common service.
9. The at least one computer-readable storage medium of claim 1 , wherein the common service includes a read/write data service.
10. The at least one computer-readable storage medium of claim 1 , wherein the common service includes a runtime service.
11. The at least one computer-readable storage medium of claim 1 , wherein the common service includes a machine learning inference service.
12. The at least one computer-readable storage medium of claim 1 , wherein the instructions further cause the computing node to disable the common service on the project hosted on each of the first and second service domains in response to receipt of a request to disable the common service for the project.
13. A system, comprising:
a first service domain hosted on a first computing platform having a first architecture, wherein the first service domain includes a project and a common service;
a second service domain hosted on a second computing platform having a second architecture, wherein the second service domain includes the project and the common service; and
a platform-as-a-service (PaaS) manager hosted on a computing node, wherein, in response to receipt of a request to provide access to the common service to the project, determine a scope of the common service, and bind the common service to the project or instantiating the common service in the project based on the scope of the common service.
14. The system of claim 13 , wherein the PaaS manager is further configured to bind the common service to the project in response to the scope of the common service being a service domain-level scope.
15. The system of claim 14 , wherein the PaaS Manager is further configured to bind a second version of the common service to the project in response to receipt of a second request, wherein the second version of the common service has different configuration settings than the common service.
16. The system of claim 13 , wherein the PaaS Manager is further configured to instantiate the common service in the project in response to the scope of the common service being a project-level scope.
17. The system of claim 13 , wherein the PaaS manager is further configured to apply received configuration setting selections to the common service.
18. The system of claim 13 , wherein the PaaS manager is further configured to provide access to the common service to clients external to the project in response to receipt of a user selection.
19. The system of claim 13 , wherein the PaaS manager is further configured to monitor health of the common service after deployment to the first and second service domains.
20. The system of claim 13 , wherein the PaaS manager is further configured to disable the common service on the project hosted on each of the first and second service domains in response to receipt of a request to disable the common service for the project.
21. A method, comprising:
receiving a request to provide access to or enable a common service for a project hosted on both a first service domain of a first computing platform and a second service domain hosted on a second computing platform of a first cloud service provider different than a second cloud service provider for the first computing platform;
determining a scope of the common service; and
binding the common service to the project or instantiate the common service in the project based on the scope of the common service.
22. The method of claim 21 , further comprising binding the common service to the project in response to the scope of the common service being a service domain-level scope.
23. The method of claim 21 , further comprising binding a second version of the common service to the project in response to receipt of a second request, wherein the second version of the common service has different configuration settings than the common service.
24. The method of claim 21 , further comprising instantiating the common service in the project in response to the scope of the common service being a project-level scope.
25. The method of claim 21 , further comprising applying received configuration setting selections to the common service.
26. The method of claim 21 , further comprising providing access to the common service to a client external to the project in response to receipt of a request via an exposed endpoint generated for the common service.
27. The method of claim 21 , further comprising monitoring health of the common service after deployment to the first and second service domains.
28. The method of claim 21 , further comprising receiving the request to provide access to or enable at least one of a read/write data service, a runtime service, or a machine learning inference service as the common service for the project.
29. The method of claim 21 , further comprising disabling the common service on the project hosted on each of the first and second service domains in response to receipt of a request to disable the common service for the project.