Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ModelOwner field to ARMs #188

Open
ibaldin opened this issue Jul 10, 2023 · 2 comments
Open

Add ModelOwner field to ARMs #188

ibaldin opened this issue Jul 10, 2023 · 2 comments
Assignees
Labels
1.6 For release 1.6

Comments

@ibaldin
Copy link
Contributor

ibaldin commented Jul 10, 2023

In order to properly find which aggregate owns a particular model we need an explicit designation at least on some nodes of ARM who originally created this model. This needs to be carefully handled when the models are merged on stitch nodes, but it will help finding e.g. who the owner of the network model is when three-way merges (like EDC+NCSA+Network Model) are done.

@ibaldin ibaldin self-assigned this Jul 11, 2023
@ibaldin ibaldin added the 1.6 For release 1.6 label Jul 11, 2023
@ibaldin
Copy link
Contributor Author

ibaldin commented Sep 13, 2023

How are we getting around this now? Just so I know how to test @kthare10 ?

@kthare10
Copy link
Collaborator

This is typically an issue for sites like EDC and NCSA which share a switch which results in the merged model to have multiple network delegation id and no way for the code to know the owner of the delegation id.

The current hack is to look for L3 Service in the the Switch and use it's delegation id.

@ibaldin ibaldin changed the title Add ModelOwner field to ASMs Add ModelOwner field to ARMs Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.6 For release 1.6
Projects
None yet
Development

No branches or pull requests

2 participants