Bug 1194055 - [RFE] Support IPv6 addresses for fencing
Summary: [RFE] Support IPv6 addresses for fencing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Ondra Machacek
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: RHEV_IPv6 1425315
TreeView+ depends on / blocked
 
Reported: 2015-02-18 21:36 UTC by Ondřej Svoboda
Modified: 2019-04-28 13:32 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this update, fence agents can now be specified using an IPv6 address. The whole fencing flow is now functional on IPv6 networks.
Clone Of:
Environment:
Last Closed: 2016-07-05 07:40:22 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.0+
gklein: testing_plan_complete+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)

Description Ondřej Svoboda 2015-02-18 21:36:58 UTC
It is currently not possible to enter an IPv6 address to oVirt GUI that a host could be fenced on. I tested manually (and Dan mentioned on [1]) that:

  # vdsClient -s 0 fenceNode '2620:52::1040:221:5eff:fe11:a22d' 23 rsa fencetest fencetest status on

works, given that the fenced host has an IPv6-enabled iLo or a similar module.

It is also said there that the schema does not need to change. So I think that all that is needed is to allow IPv6 in address validation.

  @Host.fenceNode - we need to put just one IP address of host, we can use field @addr for IPv6 also because type of @addr is str 

This sounds like low hanging fruit :-)

Comment 1 Ondřej Svoboda 2015-02-18 21:45:10 UTC
[1] is http://www.ovirt.org/Features/IPv6_support

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:55:11 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Dan Kenigsberg 2016-02-17 15:51:23 UTC
Beyond typing an ipv6 address for power management, we should support users who type an fqdn. Per emesika's suggestions, we should let them specify whether that fqdn is ipv6-only or ipv4-only (in case one of the resolutions is not responsive, or points to a completely wrong fencing device).

Comment 4 Oved Ourfali 2016-03-07 09:32:42 UTC
Martin - please estimate this one, so that we'll know if to move to 4.1 or not.

Comment 5 Martin Perina 2016-03-07 10:57:47 UTC
It seems to me that following should be enough to fulfill the task:

 1. Adding possibility to specify IPv6 address in Fence Agent Address in Power Management tab (currently we allows only hostname or IPv4 address)

 2. Adding a radio button group "Address resolution":
    Both - IPv4 and IPv6 can be used (default)
    IPv4 only - (corresponds to --inet4-only fence agent option)
    IPv6 only - (corresponds to --inet6-only fence agent option)

Dan, is it enough from networking point of view?

If so, it seem to me as an easy task to fix input validator and pass new options to fence agent. IMO it's possible to get it into 4.0.

Comment 6 Oved Ourfali 2016-04-21 06:32:53 UTC
We discussed that offline.
It will be enough to:
1. Adding possibility to specify IPv6 address in Fence Agent Address in Power Management tab (currently we allows only hostname or IPv4 address) (UI/API).
2. Make sure it propagates well all the way

No need to make the configuration complex.

Comment 7 Sandro Bonazzola 2016-05-02 09:49:35 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 8 Ondra Machacek 2016-05-05 11:15:47 UTC
This patch[1], added the support already.
Since fence agent call 'HostAddressValidation' default contructor, which by default validates also IPv6.

[1] https://gerrit.ovirt.org/#/c/53174/55

Comment 9 Petr Matyáš 2016-06-08 08:53:45 UTC
IPv6 can be used in new power management setup, but most agents use ipmitool, which doesn't support IPv6. This will work for most HP servers but not many others.

IPv6 address verification works, so verified on ovirt-engine-4.1.0-0.0.master.20160606111312.gitc7af584.el7.centos.noarch

Comment 10 Sandro Bonazzola 2016-07-05 07:40:22 UTC
oVirt 4.0.0 has been released, closing current release.

Comment 11 Martin Perina 2017-08-18 08:12:47 UTC
(In reply to Martin Perina from comment #5)
> It seems to me that following should be enough to fulfill the task:
> 
>  1. Adding possibility to specify IPv6 address in Fence Agent Address in
> Power Management tab (currently we allows only hostname or IPv4 address)
> 
>  2. Adding a radio button group "Address resolution":
>     Both - IPv4 and IPv6 can be used (default)
>     IPv4 only - (corresponds to --inet4-only fence agent option)
>     IPv6 only - (corresponds to --inet6-only fence agent option)
> 

During implementation we have decided not to add Address resolution radio button. This is advanced option, so administrators need to use Options field and fill-in relevant options for specific fence agent. For example for iLO4 agent following options are available:

 Both IPv4 and IPv6 can be used
   - Default behaviour, no option needed
 IPv4 only
   - Need to add following into Options field: inet4_only=1
 IPv6 only
   - Need to add following into Options field: inet6_only=1


Note You need to log in before you can comment on or make changes to this bug.