Project

General

Profile

Actions

Feature #1951

closed

Support libvirt named NAT networks

Added by Dominic Cleal almost 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Currently libvirt compute resources support bridged interfaces, but not libvirt NAT networks.

The NICs on a fog compute resource have both a bridge and network attribute, but the libvirt network view (app/views/compute_resources_vms/form/libvirt/_network.html.erb) only sets the bridge.

nics=[    <Fog::Compute::Libvirt::Nic
mac="52:54:00:9a:34:98",
type="network",
network="default",
bridge=nil,
model="virtio"
>],

This is compounded because the getter for libvirt networks (lib/foreman/model/libvirt.rb, networks) calls fog's interfaces getter which returns a list of physical interfaces (eth0, wlan0) and doesn't include bridges (virbr*). If the getter doesn't return data, the view allows a bridge interface to be manually entered and so you can get around it in some configurations. Entering the network name is more reliable across reboots of the hypervisor.

The way it should probably work is:

  • allow selection of either an interface or a libvirt network name
  • offer a list of interfaces, including bridges
  • always offer a text box for manual interface override
  • offer a list of libvirt network names

Related issues 1 (0 open1 closed)

Has duplicate Foreman - Bug #2477: Wrong interface for libvirt bridgeDuplicate05/08/2013Actions
Actions #1

Updated by Dominic Cleal almost 12 years ago

  • Status changed from New to Assigned
Actions #2

Updated by Ohad Levy over 11 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Ohad Levy over 11 years ago

  • Assignee set to Ohad Levy
  • Target version set to 1.2.0
Actions

Also available in: Atom PDF