Catena-X N.G INT migration to Catena-X e.V INT environment

[matbmoser]

PROPOSAL: Create a discussion for easing the process of the migration to the new Catena-X eV environment. So we can align all together which are the core services "URLs" and how we coordinate with the migration. If anyone has any problem or question please add it here and we as community can solve it together!

[matbmoser]

I can start with a question I have regarding the integration: @evegufy should we keep all our URLs with the same format? But without the demo part? What is the plan for the portal??

[evegufy]

Yes, let's stick to known subdomains where it makes sense

[stephanbcbauer]

not sure if this is related, but the URL for the environment will be https://int.catena-x.net @ds-hzimmer

[Siegfriedk]

As a side note: ask for getting the app dashboard installed too if they use argocd (which they probably will)

[stephanbcbauer]

@ds-hzimmer

[ds-asmierzchalski]

It is our plan to deploy the app dashboard as well.

[mabige]

Should be considered to open a Matrix Chat for Testing topics.

[evegufy]

Generally a good point, but as this a once time action I think a discussion is fine

[ds-hzimmer]

Thanks for the suggestion. We definetely want to create a room in Matrix Chat - or potentially Teams if more people would prefer that - for the ongoing regular release testing activities. But as Evelyn said it's maybe better to keep discussion for the environment change here now.

And as disussed yesterday, invite for a new Daily series (frequency could still be changed as needed) beginning next week, for the people involved in the end-to-end testing to communicate about status and potential blockers.

[ds-lcapellino]

FAQ regarding ArgoCD deployment

Things you must apply to your ingresses

• The tls-secretName must be unique in each ingress, for e.g.:

  tls:
    - hosts:
        - guestbook.int.catena-x.net
      secretName: tls-secret-{name of the service}

• There must be the following annotation present in the ingress, otherwise HTTPS will not work:

metadata:
  annotations:
    cert-manager.io/cluster-issuer: "letsencrypt-prod"

[amoldashwant]

@evegufy,
If there is a change in the portal URL then we need some config change in clearing house and SD factory.
Clearing house URL will remain same but the auth client ID will change. Portal also need to make this client id change while using any API of clearing house.
We might need separate deployment of SD factory. In this case SD factory URL will be different.

[evegufy]

Hi @adkumar1 I don't run into the 400 anymore 👍
but I'm waiting now since at least half an hour for the callback from your end to the following endpoint:

[adkumar1]

Hi @evegufy Modifications in client id . Try again

[evegufy]

Hi @adkumar1 I'm currently waiting for your response... I could intervene and start from scratch with requesting the self description, are you certain that I should do that and is clearinghouse also fine with sending the same request twice?

[adkumar1]

Yes, it can be sent again

[evegufy]

done, it worked now

[matbmoser]

@evegufy or portal team, we need to register our app and get the IAM from Catena-X to deploy successfully our application...

Do anyone knows the status of the DIM wallet and the EDC configuration in the portal?

[evegufy]

Hi @matbmoser today there was quite some progress regarding the dim connection but there are still some things missing.
I recommend that you join the e2e testing daily which is taking place every morning.

[matbmoser]

@saudkhan116 is now responsible for the DPP team in the Test Management Part and is taking part in the meetings. Good to know there are updates on this part.

[evegufy]

Status about BDRS: was deployed successfully by @lgblaumeiser and initial/operator BPN and DID were added via management by portal

[lgblaumeiser]

BDRS accesses the vault via the token bdrs-vault/token which you have created to be rotated. Has this changed?

[ds-asmierzchalski]

@lgblaumeiser it should stay the same. Maybe there was an issue caused by the security update on sunday. I reran the terraform script. Could you check if it works now?

[lgblaumeiser]

@ds-asmierzchalski , no it does not, it still gets an 403 when accessing the vault. Call?

[lgblaumeiser]

It runs again, thanks @ds-asmierzchalski

[ds-asmierzchalski]

@evegufy @lgblaumeiser A hard refresh in ArgoCD did the trick. Service should be running now.

[lgblaumeiser]

BDRS has been updated to 24/08 version.

[matbmoser]

Is someone able to register their EDCs in the Association Portal?

[evegufy]

I'm checking, the dim middle layer appears to be missing a permission on IAM side:

call to external system https://dim.int.catena-x.net/api/dim/technical-user/BPNLxxxx failed with statuscode 403

I'll let you know once I know more.

[evegufy]

It's solved, the technical users which couldn't be created due the missing permission are created now as well

[matbmoser]

Ok some how I could register one, but If I try to register another one I cant...

[matbmoser]

Ok I found the problem:

When you do the following thing:

1º Create the edc with tech user: (tech user is created) but when you submit it fails the registration
2º Refresh
3º Create again the EDC but select the previous created tech user then it will work.

[evegufy]

Exactly, the technical user needs to be created before you can register the connector

[tom-rm-meyer-ISST]

TLDR; the role upload in the release process in firefox is not working - use chrome

Is anyone els currently facing any issues during the app release process that the roles are not processed?

I tried:

• my previous template (since R24.03)
• download the current one and copy the rows in there

Using drag and drop the are gets red, then it's not editable anymore and no roles are processed. Anyone faced that.

@evegufy in which repo can I create the issue?

[evegufy]

Hi @tom-rm-meyer-ISST not aware that already reported that yes, but would be great to add an issue in the frontend

[tom-rm-meyer-ISST]

Hi @tom-rm-meyer-ISST not aware that already reported that yes, but would be great to add an issue in the frontend

Alright, raised issue #961