Hi Rebecca,

Could you please try with the Acumos host IP instead of the hostname as https://xx.xx.xx.xx:30030. As the federation pod has no errors, it means that the connection was not forwarded yet to Acumos. Hence, the problem lies with the Acumos-DCAE adapter pod. Two issues I often faced were related to certificate and hostname resolution. You can also get the exact error details in the acumos-adapter container . The acumos-adapter-docker-dind container only logs docker related issues if any. For example, kubectl logs -n onap acumos-dcae-acumos-adapter-dd4d4f969-bqz9k -c dcae-acumos-adapter

Regards,
Shabnam


On 24.03.22 20:21, Rebecca Aben-Athar wrote:
Hi Shabnam,

The Acumos-Federation pod has no errors, just two WARNs. The Acumos-DCAE-Adapter pod presented the error /"level=error msg="No zfs dataset found for root" backingFS=extfs root=/var/lib/docker storage-driver=zfs"/ which has already been fixed, now only warnings appear. We also tried with the NodePort type  9084:31353/TCP, 9011:30030/TCP --> /https://acumos:30030 /and /https://acumos:31353/

The Acumos catalogs still do not appear on the NiFi Dashboard, only the ONBOARD option.

Regards,
Rebecca Aben-Athar

Em qui., 24 de mar. de 2022 às 07:53, Shabnam Sultana <[email protected]> escreveu:

    Hi Rebecca,

    Do you have any errors inside the Acumos-DCAE adapter pod or the
    Acumos-Federation pod?
    If Acumos and ONAP are running in two different clusters, you will
    need to use the external port number (NodePort type- 30xxx) for
    the federation url in place of 9084.

    Regards,
    Shabnam

    On 24.03.22 02:46, Rebecca Aben-Athar wrote:
    Dear Community,

    We are integrating Acumos with the DCAE, but we are facing some
    difficulties related to this integration process that can be
    viewed in Figure. 1. We have the Acumos catalog working, and the
    Acumos DCAE Adapter is successfully connected to the DCAE Mod,
    but we can't connect the Acumos catalog with the Acumos DCAE
    adapter.

    Some tutorials we are following:
      -
    
https://wiki.onap.org/display/DW/DEMOS+-+R8+Honolulu+Demos?preview=/107251757/111118005/Realization

      - https://wiki.onap.org/display/DW/Acumos+Adapter+Installation
      -
    
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-private-docker-registry-on-ubuntu-20-04

    Used versions:
    *  .* Acumos CLIO
    *  .* ONAP Honululu

    What we have done:
      - Creation of a catalog on the Acumos platform, with models in
    it, to be accessed by DCAE.
      - Creation of a Docker Registry.
      - DCAE-Adapter installation on the ONAP machine.
      - We set to True "Enable DCAE" in SITE ADMIN in Acumos Dashboard.

    Issues:
    *.* Current result:
        - When we access the Acumos Federation URL in the DCAE NiFi
    GUI, only the option "ONBOARD" shows up.
       The IP of the machine where Acumos is running is /<acumos_ip>/
       So, the URL federation that we have tried. -->
    /https://<acumos_ip>:9084/ and we also tried with
    /https://<acumos_ip>:9011/
       We have already tried the
    *.* ${ACUMOS_FEDERATION_LOCAL_PORT} with the value 9011
    *.* ${ACUMOS_FEDERATION_PORT} with the value 9084

    . Expected result:
        - When providing the Acumos URL Federation, the options
    'Select Catalog', 'Select Solution' and 'Select Revision' should
    appear.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#23948): https://lists.onap.org/g/onap-discuss/message/23948
Mute This Topic: https://lists.onap.org/mt/89996363/21656
Mute #honolulu:https://lists.onap.org/g/onap-discuss/mutehashtag/honolulu
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to