Jira (FACT-2877) Networking fact improvements for OSX

[Andrei Filipovici (Jira)]

Andrei Filipovici created an issue

Facter / FACT-2877 Networking fact improvements for OSX Issue Type: Task Assignee: Unassigned Created: 2020/11/27 9:38 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-2877 Networking fact improvements for OSX

Change By: Andrei Filipovici Sprint: ready for triage

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie commented on FACT-2877

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

Add Comment

[Bogdan Irimie (Jira)]

Bogdan Irimie updated an issue

Facter / FACT-2877

Networking fact improvements for OSX

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

Add Comment

[Florin Dragos (Jira)]

Florin Dragos assigned an issue to Florin Dragos

Facter / FACT-2877 Networking fact improvements for OSX

Change By: Florin Dragos Assignee: Florin Dragos

Add Comment

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2877 Networking fact improvements for OSX

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}

Add Comment

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2877 Networking fact improvements for OSX 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}

- Check that if primary interface can not be retrieved it's returned as the first interface with a valid ip

Add Comment

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2877 Networking fact improvements for OSX 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}

- 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

[Andrei Filipovici (Jira)]

Andrei Filipovici updated an issue

Facter / FACT-2877 Networking fact improvements for OSX 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

[Florin Dragos (Jira)]

Florin Dragos updated an issue

Facter / FACT-2877 Networking fact improvements for OSX

Change By: Florin Dragos Release Notes: Not Needed

Add Comment