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.

Sign up for GitHub

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

Jump to bottom

No ability to rename interfaces using OpenStack cloud-init provider #1111

Open
vinceaperri opened this issue Jul 27, 2023 · 9 comments
Open

No ability to rename interfaces using OpenStack cloud-init provider #1111

vinceaperri opened this issue Jul 27, 2023 · 9 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@vinceaperri
Copy link

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
@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jul 27, 2023
@Rozzii
Copy link
Member

Rozzii commented Aug 2, 2023

I think this is a legit feature request but it is very low on our priority list at the moment would you be willing to propose a design document to metal3-docs and then implement it ? @vinceaperri
/triage accepted
/help

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Aug 2, 2023
@metal3-io metal3-io deleted a comment from metal3-io-bot Aug 2, 2023
@vinceaperri
Copy link
Author

I think this is a legit feature request but it is very low on our priority list at the moment would you be willing to propose a design document to metal3-docs and then implement it ? @vinceaperri /triage accepted /help

Yes I can do that. Thanks for the feedback.

@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2023
@Rozzii
Copy link
Member

Rozzii commented Nov 1, 2023

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 1, 2023
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@vinceaperri
Copy link
Author

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2024
@Rozzii
Copy link
Member

Rozzii commented May 6, 2024

I think there is no movement on this issue for a long time, I will move it to frozen, @vinceaperri or anyone else feel free to continue the work on this whenever you feel like it.
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 6, 2024
@Rozzii
Copy link
Member

Rozzii commented May 6, 2024

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Metal3 - Roadmap
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vinceaperri @Rozzii @metal3-io-bot