Jira (FACT-2879) Networking fact improvements for Solaris

11 views
Skip to first unread message

Andrei Filipovici (Jira)

unread,
Nov 27, 2020, 12:40:04 PM11/27/20
to puppe...@googlegroups.com
Andrei Filipovici created an issue
 
Facter / Task FACT-2879
Networking fact improvements for Solaris
Issue Type: Task Task
Assignee: Unassigned
Created: 2020/11/27 9:39 AM
Priority: Normal 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 Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Andrei Filipovici (Jira)

unread,
Nov 27, 2020, 12:42:04 PM11/27/20
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
Change By: Andrei Filipovici
Sprint: ready for triage

Bogdan Irimie (Jira)

unread,
Jan 5, 2021, 3:23:03 AM1/5/21
to puppe...@googlegroups.com
Bogdan Irimie commented on Task FACT-2879
 
Re: Networking fact improvements for Solaris

We should investigate differences between Facter 3 and Facter 4.

Bogdan Irimie (Jira)

unread,
Jan 5, 2021, 3:27:02 AM1/5/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
 
Change By: Bogdan Irimie
Sprint: ready for triage ghost-13.01.2020

Andrei Filipovici (Jira)

unread,
Jan 6, 2021, 7:25:03 AM1/6/21
to puppe...@googlegroups.com
Andrei Filipovici updated an issue
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)

Florin Dragos (Jira)

unread,
Jan 12, 2021, 3:54:03 AM1/12/21
to puppe...@googlegroups.com
Florin Dragos assigned an issue to Florin Dragos
Change By: Florin Dragos
Assignee: Florin Dragos

Bogdan Irimie (Jira)

unread,
Jan 13, 2021, 9:04:03 AM1/13/21
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-13.01.2020 , ready for triage 3
Reply all
Reply to author
Forward
0 new messages