How can we reproduce it (as minimally and precisely as possible)?
Run estimator to see that log report the specpower pkl files (generated using python 3.7) are incompatible with newer python.
fail to load pkl /mnt/download/acpi/AbsPower/platform.pkl: No module named 'sklearn.ensemble._gb_losses'
estimator-1 | set NODE_TOTAL_ESTIMATOR to true.
estimator-1 | set NODE_TOTAL_INIT_URL to https://raw.githubusercontent.com/sustainable-computing-io/kepler-model-db/main/models/v0.7/specpower/acpi/AbsPower/BPFOnly/GradientBoostingRegressorTrainer_0
.zip.
estimator-1 | set NODE_COMPONENTS_ESTIMATOR to true.
estimator-1 | set NODE_COMPONENTS_INIT_URL to https://raw.githubusercontent.com/sustainable-computing-io/kepler-model-db/main/models/v0.7/ec2-0.7.11/rapl-sysfs/AbsPower/BPFOnly/GradientBoostingRegres
sorTrainer_0.zip.
estimator-1 | clean socket
estimator-1 | get archived model
estimator-1 | get init url https://raw.githubusercontent.com/sustainable-computing-io/kepler-model-db/main/models/v0.7/specpower/acpi/AbsPower/BPFOnly/GradientBoostingRegressorTrainer_0.zip
estimator-1 | try getting archieved model from URL: https://raw.githubusercontent.com/sustainable-computing-io/kepler-model-db/main/models/v0.7/specpower/acpi/AbsPower/BPFOnly/GradientBoostingRegress
orTrainer_0.zip for AbsPower
estimator-1 | <Response [200]>
estimator-1 | load model from config: /mnt/download/acpi/AbsPower
estimator-1 | fail to load pkl /mnt/download/acpi/AbsPower/platform.pkl: No module named 'sklearn.ensemble._gb_losses'
estimator-1 | /usr/local/lib/python3.10/site-packages/sklearn/base.py:376: InconsistentVersionWarning: Trying to unpickle estimator MaxAbsScaler from version 1.1.2 when using version 1.5.1. This migh
t lead to breaking code or invalid results. Use at your own risk. For more info please refer to:
estimator-1 | https://scikit-learn.org/stable/model_persistence.html#security-maintainability-limitations
Anything else we need to know?
No response
Kepler image tag
latest (but shouldn't matter if you used 0.7.11)
Deployment
[X] Model server
[X] Estimator
[ ] Online trainer
[ ] Offline trainer
[ ] Profiler
Kepler model server image tag if deployed
0.7.11
Kepler estimator image tag if deployed
latest
Kepler online trainer image tag if deployed
Kepler offline trainer image tag if deployed
Kepler profiler image tag if deployed
Kubernetes version
```console
$ kubectl version
# paste output here
```
Install tools
Kepler deployment config
For on kubernetes:
```console
$ KEPLER_NAMESPACE=kepler
# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE}
# paste output here
# provide kepler model server configmap if Kepler Model Server is deployed
$ kubectl get configmap kepler-model-server-cfm -n ${KEPLER_NAMESPACE}
# paste output here
# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE}
```
For standalone:
# put your Kepler command argument here
What happened?
Run kepler
vm
compose pointing to latest release model server. See diff belowWhat did you expect to happen?
Pkl files should load without any warning.
How can we reproduce it (as minimally and precisely as possible)?
Run estimator to see that log report the
specpower
pkl files (generated using python 3.7) are incompatible with newer python.Anything else we need to know?
No response
Kepler image tag
Deployment
Kepler model server image tag if deployed
Kepler estimator image tag if deployed
Kepler online trainer image tag if deployed
Kepler offline trainer image tag if deployed
Kepler profiler image tag if deployed
Kubernetes version
Install tools
Kepler deployment config