Project

General

Profile

Actions

User story #3670

closed

Support IPv6 address in inventory

Added by François ARMAND almost 11 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Web - Nodes & inventories
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Rudder does not take into accound IPv6 address in Fusion report.

They are reported like that:

    <NETWORKS>
      <DESCRIPTION>eth0</DESCRIPTION>
      <DRIVER>virtio_net</DRIVER>
      <IPADDRESS>192.168.100.34</IPADDRESS>

      <IPADDRESS6>fe80::5054:ff:fef5:dca3/64</IPADDRESS6>

      <IPDHCP>192.168.100.1</IPDHCP>
      <IPGATEWAY>192.168.100.1</IPGATEWAY>
      <IPMASK>255.255.255.0</IPMASK>
      <IPSUBNET>192.168.100.0</IPSUBNET>
      <MACADDR>52:54:00:F5:DC:A3</MACADDR>
      <SLAVES></SLAVES>
      <STATUS>Up</STATUS>
      <TYPE>Ethernet</TYPE>
      <VIRTUALDEV>0</VIRTUALDEV>
    </NETWORKS>

Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #7136: Rudder doesn't store and display the IPV6 of the nodesReleasedFrançois ARMAND2016-03-01Actions
Actions #1

Updated by François ARMAND almost 11 years ago

We just don't collect them when parsing Fusion report:

      case Some(desc) =>
        Some( Network(
            name = desc
          , ifAddresses = optText(n\"IPADDRESS") match {
              case None => Seq()
              case Some(a) => getAddresses(a)
            }
          , ifDhcp = optText(n\"IPDHCP").flatMap(getAddressByName( _ ))
          , ifGateway = optText(n\"IPGATEWAY").flatMap(getAddressByName( _ ))
          , ifMask = optText(n\"IPMASK").flatMap(getAddressByName( _ ))
          , ifSubnet = optText(n\"IPSUBNET").flatMap(getAddressByName( _ ))
          , macAddress = optText(n\"MACADDR")
          , status = optText(n\"STATUS")
          , ifType = optText(n\"TYPE")
          , typeMib = optText(n\"TYPEMIB")
          , speed = optText(n\"SPEED")
        ) )

We can either add them in the same IP field as ipv4, or create an ipv6 field for them. Mixing both category could lead to funny result, but creating a new field for them implies modifying LDAP schema (what is fastidious).

Actions #2

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #3

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #4

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #5

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #6

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #7

Updated by Nicolas PERRON over 10 years ago

  • Status changed from New to Discussion
  • Assignee set to Jonathan CLARKE

I wonder if this is a bug or a feature. I seems to me that this is a feature of a Rudder "ipv6-compatible", isn't ?

Actions #8

Updated by Jonathan CLARKE over 10 years ago

  • Tracker changed from Bug to User story
  • Subject changed from IPv6 address are ignored. to Support IPv6 address in inventory
  • Status changed from Discussion to 8
  • Assignee deleted (Jonathan CLARKE)
  • Target version changed from 2.4.12 to Ideas (not version specific)

Agreed

Actions #9

Updated by Benoît PECCATTE about 9 years ago

  • Category changed from 26 to Web - Nodes & inventories
Actions #10

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from 8 to New
Actions #11

Updated by Alexis Mousset about 8 years ago

  • Is duplicate of Bug #7136: Rudder doesn't store and display the IPV6 of the nodes added
Actions #12

Updated by Alexis Mousset about 8 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF