On 02/17/15 at 06:23pm, Baoquan He wrote:
> On 02/15/15 at 03:45pm, Minfei Huang wrote:
> > Now the dracut does not have enough info to setup the ipv6 to connect
> > the iscsi target in the 2nd kernel, if the iscsi connecting is ipv6
> > protocal.
> > For this patch, we will parse the iscsi connecting,
pass the config to
> > the dracut to setup the ipv6 in the 2nd kernel.
> > Signed-off-by: Minfei Huang
> > ---
> > dracut-module-setup.sh | 25 ++++++++++++++++++++-----
> > 1 file changed, 20 insertions(+), 5 deletions(-)
> What's your suggestion or plan on testing of ipv6
iscsi? Just think that
> once ipv6 is merged and declare to support, customers will report bugs
> on kinds of features with ipv6.
The way which supports the iscsi with ipv6 is same as ipv4. So I think
the general testcase is fine. Meanwhile we can fix the bug in the
future, if we meet.
I am fine with it. Actually the test could be very complicated. E.g the
bridge, vlan tag, bond. And they can configure over each other. It's OK
to do it later when customer really deploy it and report bugs. Otherwise
too much effort is needed.