-
Notifications
You must be signed in to change notification settings - Fork 113
Open
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Description
User Story
As a developer I would like to specify the name of an interface in Metal3DataTemplate when using the OpenStack cloud-init provider.
Detailed Description
The OpenStack cloud-init provider supports renaming an interface, but only through the "name" attribute. Metal3DataTemplate, however, does not recognize this attribute.
It is expected that Metal3DataTemplate optionally support the "name" attribute to employ the renaming functionality in the OpenStack cloud-init provider.
Anything else you would like to add:
The relevant code in cloud-init: openstack.py
/kind feature
Metadata
Metadata
Assignees
Labels
help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Type
Projects
Status
Backlog