Hi Roberto: The documentation you are referring to must be updated. The LP#1460177 RFE implemented this feature. Actually there is a test class that is testing this functionality in the CI [1][2]. Regards. [1]https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/750355/ [2] https://github.com/openstack/neutron-tempest-plugin/blob/f10618eac3a12d35a35... On Fri, Nov 18, 2022 at 2:45 PM Roberto Bartzen Acosta < roberto.acosta@luizalabs.com> wrote:
Hey folks,
Can you confirm if the metadata should work in an ipv6-only environment?
As I understand from this discussion on LP:1460177 <https://bugs.launchpad.net/neutron/+bug/1460177> and the fork of the discussion in many opendev reviews #315604 <https://review.opendev.org/c/openstack/neutron-specs/+/315604>, #738205 <https://review.opendev.org/c/openstack/neutron-lib/+/738205> #745705 <https://review.opendev.org/c/openstack/neutron/+/745705>, ..., it seems like it should work.
However, this comment in the openstack doc [1] has me questioning if it really works. *"There are no provisions for an IPv6-based metadata service similar to what is provided for IPv4. In the case of dual-stacked guests though it is always possible to use the IPv4 metadata service instead. IPv6-only guests will have to use another method for metadata injection such as using a configuration drive, which is described in the Nova documentation on config-drive <https://docs.openstack.org/nova/latest/user/config-drive.html>."*
Is anyone using metadata in an ipv6-only Openstack setup?
Regards, Roberto
[1] https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#configuring...
*‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’.*
*‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*