hello Aniello

I am doing some corrections. Should  not be long. I will tell you.


René


---- Aniello Paolo Malinconico a écrit ----


Hi Rene',
thanks for replying.


I have done  2 tests:
1. Service Resolver github from 23-09-2019
I have direct access to ONAP, no proxy used. In this version I have found new 
files for docker-compose. I am expecting to use the 
docker-compose-no-proxy.yaml with no changes.
So I have used the docker-compose-no-proxy.yaml to run the docker images:
command -> docker-compose -f docker-compose-no_proxy.yaml build and 
docker-compose -f docker-compose-no_proxy.yaml up.

The last command turns all container into running state, but for the :
- api_rfs_spec_server_1 returns OSError: Address not availble
- api_service_server_1 returns OSError: Address not availble
- api_service_spec_server_1 returns OSError: Address not availble
- instantiation_decision_server_1 returns OSError: Address not availble

Only Portal_1 returns no error and so its GUI on 6005 port is avaible.


2. Service Resolver github from 19-09-2019
On the other hand,
In this version I have only one file docker-compose.yaml.
After running the docker-compose up, all the GUIs are exposed properly, but 
then when I GET the status from the API, it returns the following error:

api_rfs_spec_server_1            |   File 
"/usr/src/app/swagger_server/controllers/rfs_specification_controller.py", line 
201, in statusFind
api_rfs_spec_server_1            |     nbi_healthcheck()
api_rfs_spec_server_1            | TypeError: nbi_healthcheck() missing 1 
required positional argument: 'onap_platform_name'
api_rfs_spec_server_1            | ERROR:tornado.access:500 GET 
/serviceResolver/serviceCatalogManagement/api/v1/status (172.19.0.1) 97.63ms



Any fix? Should I change some configurational pointers?
Thanks,

Aniello Paolo Malinconico


_________________________________________________________________________________________________________________________

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.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#19035): https://lists.onap.org/g/onap-discuss/message/19035
Mute This Topic: https://lists.onap.org/mt/34173460/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to