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

Datacenter blueprint needs interface-map import resource #847

Open
chrismarget-j opened this issue Sep 5, 2024 · 0 comments
Open

Datacenter blueprint needs interface-map import resource #847

chrismarget-j opened this issue Sep 5, 2024 · 0 comments

Comments

@chrismarget-j
Copy link
Collaborator

chrismarget-j commented Sep 5, 2024

This might be trickier than it looks.

  • on import, a blueprint IM uses the ID from the import payload as its graph node ID. When import is done by the GUI, that ID is the one used in the global catalog.
  • FFE operations clone the IM, using a random ID for the clone, and changing the label to something like "label_v2"
  • The original IM may be destroyed by FFE if it determines that no remaining logical devices link to this IM.
@chrismarget-j chrismarget-j changed the title Datacenter blueprint needs logical device import resource Datacenter blueprint needs interface-map import resource Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant