Jira (FACT-2876) Networking fact improvements for Windows

[Andrei Filipovici (Jira)]

Andrei Filipovici created an issue

Facter / FACT-2876 Networking fact improvements for Windows Issue Type: Task Assignee: Unassigned Created: 2020/11/27 9:36 AM Priority: Normal Reporter: Andrei Filipovici Expand networking resolver to display VLANs and secondary IPs. All secondary IPs must be displayed in the bindings/bindings6 section of the physical interface. Secondary IPs that have a label, will also be displayed as a separate interface. Make sure inactive interfaces are also displayed. Make sure the resolver is able to extract IPs from interfaces inside an OpenVZ environment. E.g. a normal ip might be displayed like inet *11.0.0.2/24* scope global ens192:2 an OpenVz ip might be displayed like this inet 11.0.0.5 peer *11.0.0.2/24* scope global ens192:2 Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2876 Networking fact improvements for Windows

Change By: Andrei Filipovici Sprint: ready for triage

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie commented on FACT-2876

Re: Networking fact improvements for Windows We should investigate differences between Facter 3 and Facter 4

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie updated an issue

Facter / FACT-2876

Networking fact improvements for Windows

Change By: Bogdan Irimie Sprint: ready for triage ghost-13.01.2020

Add Comment

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2876 Networking fact improvements for Windows

Change By: Andrei Filipovici

Expand networking resolver to display VLANs and secondary IPs.

- All secondary IPs must be displayed in the bindings/bindings6 section of the physical interface. Secondary IPs that have a label, will also be displayed as a separate interface. - Make sure inactive interfaces are also displayed. - Make sure the resolver is able to extract IPs from interfaces inside an OpenVZ environment. E.g. a normal ip might be displayed like {code:}

inet *11.0.0.2/24* scope global ens192:2

{code}

an OpenVz ip might be displayed like this

{code:}

inet 11.0.0.5 peer *11.0.0.2/24* scope global ens192:2

{code} The OpenVz part is not important because we can't create an environment to test it. - Check that if primary interface can not be retrieved it's returned as the first interface with a valid ip.(Better check the facter 3 implementation)

Add Comment

[Oana Tanasoiu (Jira)]

Oana Tanasoiu assigned an issue to Oana Tanasoiu

Facter / FACT-2876 Networking fact improvements for Windows

Change By: Oana Tanasoiu Assignee: Oana Tanasoiu

Add Comment

[Oana Tanasoiu (Jira)]

Oana Tanasoiu commented on FACT-2876

Re: Networking fact improvements for Windows Facter 3 and facter 4 output are identical, the test scenario implied deactivating an interface.

Add Comment