Skip to content

Fixing the meaning of "container_prefix" API attribute#78

Merged
Levovar merged 1 commit into
masterfrom
prefix_fix
Apr 16, 2019
Merged

Fixing the meaning of "container_prefix" API attribute#78
Levovar merged 1 commit into
masterfrom
prefix_fix

Conversation

@Levovar
Copy link
Copy Markdown
Collaborator

@Levovar Levovar commented Apr 16, 2019

Currently this API attribute means "exact name of a container" interface, but it was never the original intention.
It was just a temporary change I needed to administer when we have moved to the asynchronous interface provisioning method.
Even the name suggest this is just a prefix of the NICs :)
Functionally speaking this makes it hard to attach multiple NICs to the same DanmNet.

After this change implicit and explicit naming schemes will be aligned: in both cases we will postfix the interface names with the provisioning sequence number.

Currently this API attribute means "exact name of a container" interface, but it was never the original intention.
It was just a temporary change when we have moved to the asynchronous provisioning method.
Even the name suggest this is just a prefix of the NICs :)
Functionally speaking this change was making it hard to attach multiple NICs to the same DanmNet... but nevermore!
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

Successfully merging this pull request may close these issues.

1 participant