diff options
| author | Fabian Mastenbroek <mail.fabianm@gmail.com> | 2022-10-04 10:04:50 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-04 10:04:50 +0200 |
| commit | 92cc0908b7ad6c94b08e6016f8815ab07cd1714d (patch) | |
| tree | b5edaff69212986265f9edc620e40bb8695f11eb /opendc-faas/opendc-faas-service/src | |
| parent | 2d2a3854d355bd4b074ef651f291d34081e70d96 (diff) | |
| parent | bd476d11ab24fe745bb54e97a11133706bb96cb1 (diff) | |
merge: Add provisioning tool for experiments (#104)
This pull request implements a new tool to help provision and manage the
experimental environment.
## Implementation Notes :hammer_and_pick:
* Add service registry for cloud services
* Add provisioning tool for experiments
* Add provisioning step for workflow service
* Add provisioners for FaaS service
* Use experiment base for Capelin experiments
* Use experiment base for web runner
* Integrate compute workload classes
* Remove Topology interface
## Breaking API Changes :warning:
* Removal of the `opendc-compute-workload`, `opendc-faas-workload`,
and `opendc-workflow-workload` modules. These are now located
inside `opendc-experiments`
* Removal of `ComputeServiceHelper`. Use `Provisioner` to provision
a `ComputeService`.
Diffstat (limited to 'opendc-faas/opendc-faas-service/src')
| -rw-r--r-- | opendc-faas/opendc-faas-service/src/main/kotlin/org/opendc/faas/service/deployer/FunctionDeployer.kt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/opendc-faas/opendc-faas-service/src/main/kotlin/org/opendc/faas/service/deployer/FunctionDeployer.kt b/opendc-faas/opendc-faas-service/src/main/kotlin/org/opendc/faas/service/deployer/FunctionDeployer.kt index 049f1cc7..18d16d06 100644 --- a/opendc-faas/opendc-faas-service/src/main/kotlin/org/opendc/faas/service/deployer/FunctionDeployer.kt +++ b/opendc-faas/opendc-faas-service/src/main/kotlin/org/opendc/faas/service/deployer/FunctionDeployer.kt @@ -28,7 +28,7 @@ import org.opendc.faas.service.FunctionObject * A [FunctionDeployer] is responsible for ensuring that an instance of an arbitrary function, a [FunctionInstance], * is deployed. * - * The function deployer should combines the configuration stored in the function registry, the parameters supplied by + * The function deployer should combine the configuration stored in the function registry, the parameters supplied by * the requester, and other factors into a decision of how the function should be deployed, including how many and * what kind of resources it should receive. * |