search for: boot_protocol

Displaying 5 results from an estimated 5 matches for "boot_protocol".

2009 May 18
0
[PATCH server] fixed functional tests after recent controller refactoring and managed node controller fixes.
...-- a/src/test/functional/managed_node_configuration_test.rb +++ b/src/test/functional/managed_node_configuration_test.rb @@ -48,7 +48,7 @@ class ManagedNodeConfigurationTest < Test::Unit::TestCase expected = <<-HERE # THIS FILE IS GENERATED! -ifcfg=#{nic.mac}|breth0|BOOTPROTO=#{nic.boot_protocol}|TYPE=bridge|PEERDNS=no|ONBOOT=yes +ifcfg=#{nic.mac}|breth0|BOOTPROTO=#{nic.boot_protocol}|TYPE=Bridge|PEERDNS=no|ONBOOT=yes ifcfg=#{nic.mac}|eth0|BRIDGE=breth0|ONBOOT=yes HERE @@ -67,7 +67,7 @@ ifcfg=#{nic.mac}|eth0|BRIDGE=breth0|ONBOOT=yes expected = <<-HERE # THIS FILE IS G...
2010 Jul 21
1
[PATCH] Add support for tagged VLAN
...n tagging + + nic.network.usages.map do |usage| + usage.networks.map do |net| + if net.type == "Vlan" + eth_vlan_name = "#{nic.interface_name}.#{net.number}" + add_bridge(result, 'none', eth_vlan_name, + nic.boot_protocol, nic.ip_address, + nic.netmask, nic.broadcast, + nic.gateway) + add_vlan(result, eth_vlan_name) + end + end # end of : usage.networks.map do |net| + end # end of : nic.network.usages.map do |usage| end end end...
2009 Jun 30
0
[PATCH server] permit many-to-many vms / networks relationship
...ope => :host_id, - :unless => Proc.new { |nic| nic.physical_network_id.nil? } - # Returns whether the nic has networking defined. def networking? - (physical_network != nil) + (network != nil) end # Returns the boot protocol for the nic if networking is defined. def boot_protocol - return physical_network.boot_type.proto if networking? + return network.boot_type.proto if networking? end # Returns whether the nic is enslaved by a bonded interface. @@ -66,30 +76,44 @@ class Nic < ActiveRecord::Base # Returns the netmask for the nic if networking is defin...
2009 Jul 24
1
permit many-to-many vms / networks relationship redux
redux patchset permitting a vm to be associated with multiple networks and vice-versa. updated patchset so as to be applicable against current oVirt server HEAD these patches may be applied in any order, they all need to be pushed together
2009 Jul 09
2
permit many-to-many vms / networks relationship
This patchset contains changes to the ovirt server frontend, backend, and tests components, permitting vms to be associated with multiple networks and vice versa. Also included are two patches which are required for the frontend bits; a patch adding collapsable sections to the vm form, which in itself depends on the second patch that provides default values for the cpu and memory vm table fields