Feature #10539

Automatically assign oVirt name and network

Added by Michael Bassler about 3 years ago. Updated 9 days ago.

Status:Closed
Priority:Normal
Assignee:Baptiste Agasse
Category:Compute resources - oVirt
Target version:1.15.0
Difficulty: Team Backlog:
Triaged: Fixed in Releases:
Bugzilla link: Found in Releases:
Pull request:https://github.com/theforeman/foreman/pull/4096, https://github.com/theforeman/foreman/pull/4095

Description

When building a oVirt/RHEV VM using Foreman it would be nice if the interface name could be defaulted and network could be assigned based on the subnet that is selected.

Thank You
-Michael


Related issues

Blocks Foreman - Feature #18088: Automatically assign oVirt network from foreman network Ready For Testing 01/16/2017

Associated revisions

Revision 12a32535
Added by Baptiste over 1 year ago

Fixes #10539 - Add default names for ifaces for oVirt CR VMs

History

#1 Updated by Dominic Cleal about 3 years ago

  • Category set to Compute resources - oVirt

#2 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Assignee set to Baptiste Agasse
  • Pull request https://github.com/theforeman/foreman/pull/4095 added

#3 Updated by The Foreman Bot over 1 year ago

  • Pull request https://github.com/theforeman/foreman/pull/4096 added

#4 Updated by Anonymous over 1 year ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Baptiste Agasse over 1 year ago

Someone can re-open this ? The second PR is not accepted ATM (network assignment part). Thanks.

#6 Updated by Dominic Cleal over 1 year ago

  • Legacy Backlogs Release (now unused) set to 209

The second PR should use a separate ticket, or they should have been in the same pull request (and commit) if it was to fix the same issue. Please change the ticket number.

#7 Updated by Dominic Cleal over 1 year ago

  • Blocks Feature #18088: Automatically assign oVirt network from foreman network added

Also available in: Atom PDF