[acumosaicommunity]Help: Unable to on-board python models using web-client or python acumos package
I am unable to on-board a very simple python model (see attachment model.py) using web or cli on-boarding. All Acumos pods are running.
I have deployed Acumos on a pre-existing k8s cluster using the AIO guide for the Demeter release, where I defined acumos.example.com as the FQDN in the setup_prereqs.sh process. Could you perhaps take a look at my hosts file and tell me if there are any entries that are perhaps missing? The logs of the on-boarding and portal-be pods are not really helping me in troubleshooting this. It might also be worth noting that both the license editor and ML Workbench also fail to load, although their pods are up and running. I am accessing the portal by way of port-forwarding ussing ssh.
Here are some details concerning the deployment of Acumos:
Acumos Release: 3.0.3
OS: Ubuntu 18.04
Kubernetes v1.19.0
Docker v18.09.2
Python 3.6.5
acumos on-boarding package v.0.9.7
I tried to see if Nexus was running out of space and applied the fix (as described here) and also reverted to acumos==0.8.0, but to no avail. I am out of my depth here, so any help would be greatly appreciated.
Best,
Felix
Hi Felix, Yeseterday I had exactly the same error on Acumos 3.0.24, but what is very strange is that this morning I tried again with an R model and a Python model and I succeeded to onboard them
You forgot to share your model.py file in the previous e-mail, could you send it to me or send me your model bundle I will try it on my local Acumos clio
Thanks
De : acumosai-community@... [mailto:acumosai-community@...]
De la part de felix.oertel@...
Envoyé : mercredi 16 septembre 2020 18:27
À : acumosai-community@...
Objet : [Acumos AI Community-Committee] [acumosaicommunity]Help: Unable to on-board python models using web-client or python acumos package
Hello,
I am unable to on-board a very simple python model (see attachment model.py) using web or cli on-boarding. All Acumos pods are running.
I have deployed Acumos on a pre-existing k8s cluster using the AIO guide for the Demeter release, where I defined acumos.example.com as the FQDN in the setup_prereqs.sh process. Could you perhaps take a look at my hosts file and tell me if there are any entries
that are perhaps missing? The logs of the on-boarding and portal-be pods are not really helping me in troubleshooting this. It might also be worth noting that both the license editor and ML Workbench also fail to load, although their pods are up and running.
I am accessing the portal by way of port-forwarding ussing ssh.
Here are some details concerning the deployment of Acumos:
Acumos Release: 3.0.3
OS: Ubuntu 18.04
Kubernetes v1.19.0
Docker v18.09.2
Python 3.6.5
acumos on-boarding package v.0.9.7
I tried to see if Nexus was running out of space and applied the fix (as described here) and also reverted to acumos==0.8.0, but to no avail. I am out of my depth here, so any help would be greatly appreciated.
Best,
Felix
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Hi Felix,
I tried your model bundle and it failed with the same error message than you. When I look at the json file I found this :
{"schema": "acumos.schema.model:0.6.0", "runtime": {"name": "python", "version": "3.6.5", "dependencies": {"pip": {"indexes": [], "requirements": [{"name": "acumos", "version": "0.9.7"},
CLIO is not able to work with "acumos.schema.model:0.6.0", this schema is link to the version 0.9.7 of “acumos” and is intended to work with Demeter. So what I would recommend you is to uninstall acumos 0.9.7, then install acumos 0.8.0 and build again your model bundle
I think I made the same error yesterday. You will find enclosed a model bundle onboarded successfully on my Acumos CLIO if you look at the json file you will find this :
"schema": "acumos.schema.model:0.4.0", "runtime": {"name": "python", "encoding": "protobuf", "version": "3.6.9", "dependencies": {"pip": {"indexes": [], "requirements": [{"name": "acumos", "version": "0.8.0"},
PS : I didn’t receive your . py file again, I think some security rules are applied, on my side or on your side, to remove this kind of file.
-Philippe
De : Oertel, Felix Immanuel [mailto:felix.oertel@...]
Envoyé : jeudi 17 septembre 2020 11:25
À : DOOZE Philippe TGI/OLN <philippe.dooze@...>
Objet : AW: [Acumos AI Community-Committee] [acumosaicommunity]Help: Unable to on-board python models using web-client or python acumos package
Hi Philippe,
thank you for your reply! I have tried again this morning, but unfortunately I did not have the same luck as you. I have attached both the model.py file and the model bundle to this mail. It might help to also know that when onboarding using the web client, the error message occurs during the step Create Solution => Add Artifacts. Again, thanks for trying to help me out.
Best,
Felix
Von:
philippe.dooze@... [mailto:philippe.dooze@...]
Gesendet: Donnerstag, 17. September 2020 09:33
An: Oertel, Felix Immanuel <felix.oertel@...>;
acumosai-community@...
Cc: EDEL Nicolas TGI/OLN <nicolas.edel@...>
Betreff: RE: [Acumos AI Community-Committee] [acumosaicommunity]Help: Unable to on-board python models using web-client or python acumos package
Hi Felix, Yeseterday I had exactly the same error on Acumos 3.0.24, but what is very strange is that this morning I tried again with an R model and a Python model and I succeeded to onboard them
You forgot to share your model.py file in the previous e-mail, could you send it to me or send me your model bundle I will try it on my local Acumos clio
Thanks
De :
acumosai-community@... [mailto:acumosai-community@...]
De la part de felix.oertel@...
Envoyé : mercredi 16 septembre 2020 18:27
À : acumosai-community@...
Objet : [Acumos AI Community-Committee] [acumosaicommunity]Help: Unable to on-board python models using web-client or python acumos package
Hello,
I am unable to on-board a very simple python model (see attachment model.py) using web or cli on-boarding. All Acumos pods are running.
I have deployed Acumos on a pre-existing k8s cluster using the AIO guide for the Demeter release, where I defined acumos.example.com as the FQDN in the setup_prereqs.sh process. Could you perhaps take a look at my hosts file and tell me if there are any entries
that are perhaps missing? The logs of the on-boarding and portal-be pods are not really helping me in troubleshooting this. It might also be worth noting that both the license editor and ML Workbench also fail to load, although their pods are up and running.
I am accessing the portal by way of port-forwarding ussing ssh.
Here are some details concerning the deployment of Acumos:
Acumos Release: 3.0.3
OS: Ubuntu 18.04
Kubernetes v1.19.0
Docker v18.09.2
Python 3.6.5
acumos on-boarding package v.0.9.7
I tried to see if Nexus was running out of space and applied the fix (as described here) and also reverted to acumos==0.8.0, but to no avail. I am out of my depth here, so any help would be greatly appreciated.
Best,
Felix
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.