-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing the connection b/w ports #194
Conversation
0eee543
to
3986386
Compare
3986386
to
9b42359
Compare
This pull request is not mergeable. Please rebase and repush. |
9b42359
to
2c7cfb8
Compare
2c7cfb8
to
ad3e842
Compare
spec/manageiq-schema
Outdated
@@ -0,0 +1 @@ | |||
/home/douglas/workspace/manageiq-schema |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Delete this, have to be careful with git commit -a --amend
😄
@rodneyhbrown7 assigning to you to review, looks fine from the MIQ side but need you to review the LXCA stuff |
ad3e842
to
4abe17f
Compare
Checked commit douglasgabriel@4abe17f with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@douglasgabriel or if you can get a review from another member of your team I'll merge this given how long it has been sitting here |
@caiocmpaes could you review that, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I tested mocking data of PhysicalNetworkPorts and the connection is created with success.
I only had a suggestion about the naming of one method. You can see It on the inline comments.
@@ -139,6 +141,18 @@ def get_config_patterns | |||
config_patterns = @connection.discover_config_pattern | |||
config_patterns.map { |config_pattern| @parser.parse_config_pattern(config_pattern) } | |||
end | |||
|
|||
def bind_network_ports(inventory) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the method changes the inventory hash, shouldn't It be bind_network_ports!
(with the !
)? The same way you put on the parser method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, @caiocmpaes, it's a fair concern, but our methods in this class doesn't use this pattern and to keep the consistence I would say to keep this name. Also the method that is really doing the changes has already its name ending with !
. What do you think? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I Agree with you. Let It be the current name, then. 👍
Parsing the connection b/w ports
Thanks @douglasgabriel really awesome enhancement from schema all the way to the parser |
This PR is able to
uid_ems
;Informations
A port is connected to another if its MAC address is described in the
peer_mac_address
of the other port.Depends on
ManageIQ/manageiq-schema#208- MergedManageIQ/manageiq#17311Merged