You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I summarize here the feedback from the internal review process of the REAR data model, highlight what might be included in the next release.
Flavor data model
SLA/SLO. There's currently no support for Service Level Agreement in the REAR data models. The Flavor might be the perfect candidate to host such information.
The price is currently represented as <amount, currency, period>. The period is currently considered as "for how much time the resources will be available". This is because the only available purchase option right now is "pay up front". No "pay-per-use" model is currently implemented. I believe the price of the Flavor must be refined to include at least these two purchase options.
K8SSlice
When we describe the amount of resources of the slice (CPU, GPU, ...), it is not possible to specifiy how these resources are organized (e.g., how many nodes?). It might be relevant because it makes a big difference if the resources come from the aggregation of 10 servers or 2. To this end, I think a field like "number of physical servers" might be helpful. Also considering the features introduced by the latest release of Liqo which allow to create multiple virtual nodes instead of just one.
Sensor
Currently, a sensor is considered to be a passive entity to gather data from. Actuators are not included in the picture. In the next release we may need to either create a new data model for actuators or manage to re-use the sensor model to include also actuators (among the two options I personally prefer the first).
The text was updated successfully, but these errors were encountered:
Hi everyone,
I summarize here the feedback from the internal review process of the REAR data model, highlight what might be included in the next release.
Flavor data model
K8SSlice
Sensor
Currently, a sensor is considered to be a passive entity to gather data from. Actuators are not included in the picture. In the next release we may need to either create a new data model for actuators or manage to re-use the sensor model to include also actuators (among the two options I personally prefer the first).
The text was updated successfully, but these errors were encountered: