User story #3670: Support IPv6 address in inventory - Rudder - Issue Tracker

Actions

Copy link

User story #3670

closed

Support IPv6 address in inventory

Added by François ARMAND over 11 years ago. Updated almost 9 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

Web - Nodes & inventories

Target version:

Ideas (not version specific)

Pull Request:

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 open — 1 closed)

Actions

Copy link

Updated by François ARMAND over 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

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.4.7 to 2.4.8

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.4.8 to 2.4.9

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.9 to 2.4.10

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.10 to 2.4.11

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.11 to 2.4.12

Actions

Copy link

Updated by Nicolas PERRON about 11 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

Copy link

Updated by Jonathan CLARKE about 11 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)