yahoo-eng-team team mailing list archive

["Dr. Jens Rosenboom" <j.rosenboom@xxxxxxxx>]

Public bug reported:

There are two issues affecting the useability of the network information
presented to an instance via the metadata API:

1. For networks using DHCP, the IP address information is omitted. There
are however use cases where an instance would want to use static address
configuration even when DHCP is available. So adding the information
would make deploying such an instance easier.

2. For IPv6 subnets, the type is always "ipv6_dhcp", regardless of
whether the subnet has mode "slaac", "dhcpv6-stateless" or
"dhcpv6-stateful". This makes is impossible for an instance to decide
whether it should use DHCPv6 for address and/or additional
configuration.

Here is the current output for an instance with one network for IPv4 and
one for IPv6:

{
  "services": [
    
  ],
  "networks": [
    {
      "network_id": "fb1ca77c-624d-42ab-9102-16f21313a6cb",
      "link": "tap92b3d1dd-12",
      "type": "ipv4_dhcp",
      "id": "network0"
    },
    {
      "network_id": "6179a9e5-e370-4ee4-8ff6-d83f118b08fd",
      "link": "tap2fa5e368-de",
      "type": "ipv6_dhcp",
      "id": "network1"
    }
  ],
  "links": [
    {
      "ethernet_mac_address": "fa:16:3e:e0:b3:ad",
      "mtu": 1500,
      "type": "ovs",
      "id": "tap92b3d1dd-12",
      "vif_id": "92b3d1dd-12c2-49cd-82a5-298c071896fd"
    },
    {
      "ethernet_mac_address": "fa:16:3e:aa:71:95",
      "mtu": 1500,
      "type": "ovs",
      "id": "tap2fa5e368-de",
      "vif_id": "2fa5e368-de18-416f-b6f7-063687d4b9e5"
    }
  ]
}

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1676363

Title:
  The network metadata should be more useful

Status in OpenStack Compute (nova):
  New

Bug description:
  There are two issues affecting the useability of the network
  information presented to an instance via the metadata API:

  1. For networks using DHCP, the IP address information is omitted.
  There are however use cases where an instance would want to use static
  address configuration even when DHCP is available. So adding the
  information would make deploying such an instance easier.

  2. For IPv6 subnets, the type is always "ipv6_dhcp", regardless of
  whether the subnet has mode "slaac", "dhcpv6-stateless" or
  "dhcpv6-stateful". This makes is impossible for an instance to decide
  whether it should use DHCPv6 for address and/or additional
  configuration.

  Here is the current output for an instance with one network for IPv4
  and one for IPv6:

  {
    "services": [
      
    ],
    "networks": [
      {
        "network_id": "fb1ca77c-624d-42ab-9102-16f21313a6cb",
        "link": "tap92b3d1dd-12",
        "type": "ipv4_dhcp",
        "id": "network0"
      },
      {
        "network_id": "6179a9e5-e370-4ee4-8ff6-d83f118b08fd",
        "link": "tap2fa5e368-de",
        "type": "ipv6_dhcp",
        "id": "network1"
      }
    ],
    "links": [
      {
        "ethernet_mac_address": "fa:16:3e:e0:b3:ad",
        "mtu": 1500,
        "type": "ovs",
        "id": "tap92b3d1dd-12",
        "vif_id": "92b3d1dd-12c2-49cd-82a5-298c071896fd"
      },
      {
        "ethernet_mac_address": "fa:16:3e:aa:71:95",
        "mtu": 1500,
        "type": "ovs",
        "id": "tap2fa5e368-de",
        "vif_id": "2fa5e368-de18-416f-b6f7-063687d4b9e5"
      }
    ]
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1676363/+subscriptions