<div dir="ltr"><div dir="ltr">Hello Ratan, </div><div dir="ltr"><br></div><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Are you proposing that filter to be done at gui side? Suppose at first boot, By default DHCP and Zero config is enabled, In that case back end will get two IP address (DHCP/ZeroConfig) and suppose after that user has not disabled the Zeroconfig than GUI will keep getting the two ipaddresses, in that case does the GUI apply the filter to show single IP address.</blockquote></div><div dir="ltr"><p>No filter on GUI side - In the case you are describing where by default DHCP and zeroconfig are enabled and the user has not disabled the zero config, the GUI will still show both. At any time, an interface will have MAXIMUM two IP addresses, but one of those two must be from zero config. The GUI should always reflect what is in the backend, it will not be a good experience if we hide information from users.</p><p><br></p><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Are we planning to propose new settings for GUI for IPv6.<br>In IpV6 we may have multiple IPaddresses on the same interface (LinkLocal,autoconf,static)</blockquote><p>As of now, all customers we have spoken with have said they do not currently use IPV6 and have no plans to do so in the future, so this was put on hold. If/when we choose to support IPV6, the design will be updated to reflect it. Likely, it will be a very similar design with the addition of an IPV6 section containing its own DNS servers and IP addresses. </p><p><br></p><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">What about the existing client network deployment where management traffic has been separated from the host traffic through VLAN?<br>We got this request from one of our IBM Internal team(HPC)</blockquote><p>I would love to know more about this as it is the first time I hear where the requirement came from. Once we understand the use case for it and the user needs, we can discuss prioritizing it for the GUI. </p><p><br></p><p>Regards,</p><p>Jandra A</p></div><div dir="ltr"><br></div><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 11, 2019 at 10:10 PM Ratan Gupta <<a href="mailto:ratagupt@linux.vnet.ibm.com">ratagupt@linux.vnet.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi Jandra,</p>
<p>Please find my comments inline in<font color="#33cc00"> green</font>.</p>
<p>Regards</p>
<p>Ratan Gupta<br>
</p>
<div class="gmail-m_4581134513326033599moz-cite-prefix">On 10/06/19 8:53 PM, Jandra A wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello all,<br>
<div><br>
</div>
<div>Here is the proposal for the Network Settings GUI: <a href="https://ibm.invisionapp.com/share/8ENYRVXAPFD#/319115961_Physical" target="_blank">https://ibm.invisionapp.com/share/8ENYRVXAPFD#/319115961_Physical</a> <br>
To navigate, click on any flashing blue rectangles or use the
right and left keyboard arrows.</div>
<div><br>
</div>
<div>The design is based on the needs found by our research with
stakeholders and users. </div>
<div><br>
</div>
<div>With the GUI, a user is able to assign a Fully Qualified
Domain Name (FQDN), and choose either DHCP or static
configuration, for any selected interface.</div>
<div><br>
</div>
<div>If DHCP is chosen, the GUI will reflect the appropriate
default gateway, DNS server, and IP address assigned by the
DHCP server. If static is selected, users manually assign the
default gateway, as well as multiple DNS servers and a single
IP address (not including the one assigned by zeroconf). </div>
<div><br>
</div>
<div>Despite the type of configuration selected (DHCP or
static), zero-configuration is always on to protect the user
and ensure there is always an IP address assigned. However,
once an interface has a non zeroconf IP address assigned,
users have the flexibility to permanently delete that address.
Currently, users can only temporarily delete these using CLI;
once they reboot, the addresses come back. Permanently
removing IP addresses assigned by zero-configuration is
important to customers who need to account for every single IP
address. <br>
</div>
</div>
</blockquote>
<p>Are you proposing that filter to be done at gui side? Suppose at
first boot, By default DHCP and Zero config is enabled, In that
case back end will get two IP address <br>
</p>
<p>(DHCP/ZeroConfig) and suppose after that user has not disabled
the Zeroconfig than GUI will keep getting the two ipaddresses, in
that case does the GUI apply the filter <br>
</p>
<p>to show single IP address.<br>
</p>
<p>Are we planning to propose new settings for GUI for IPv6</p>
<p>In IpV6 we may have multiple IPaddresses on the same interface
(LinkLocal,autoconf,static)<br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div><br>
</div>
<div>NOTE: The reason for limiting to a single IP address per
interface is that our research from users and stakeholders
indicates that multiple would never be used and in fact it
could make it easy to make a mistake, so for this reason we
will not support it in the GUI. Additionally, there will be no
support for VLAN as it was not expected by users and added
unnecessary confusion. <br>
</div>
</div>
</blockquote>
<p>What about the existing client network deployment where
management traffic has been separated from the host traffic
through VLAN?</p>
<p>We got this request from one of our IBM Internal team(HPC).<br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Regards,</div>
<div>Jandra Aranguren</div>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote>
</div>
</blockquote></div></div>