Skip to content
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

DP-6 discover iface bound ip, for API entry points coverage #84

Closed
wants to merge 16 commits into from

Conversation

hmmr
Copy link

@hmmr hmmr commented Mar 3, 2015

New functions: which_eth0(), to report the bound ip of the first non-loopback iface
in the system, and get_active_listener_entrypoints(Proto), to combine which_eth0()
with the ports of all http and pbc listening services on a node.

New functions: which_eth0(), to report the bound ip of the first non-loopback iface
in the system, and get_active_listener_entrypoints(Proto), to combine which_eth0()
with the ports of all http and pbc listening services on a node.
@hmmr hmmr force-pushed the feature/az/api-entrypoints-coverage branch from 9115169 to 4e5d016 Compare March 26, 2015 16:43
This leads to injection of all previously cached nodes into a
(possibly restricted) selection of nodes to consider for the current
query.

This should fix
https://bashoeng.atlassian.net/browse/DP-6?focusedCommentId=20361
@hmmr hmmr force-pushed the feature/az/api-entrypoints-coverage branch from 84dbd77 to b2a1b96 Compare April 15, 2015 00:38
@mdigan
Copy link

mdigan commented Jun 16, 2015

Closing this pull request. We're taking a different approach. John and Mark will be enhancing the coverage plan API, and we'll be adding functionality in the java client to use the new API features, and using all of those in the spark connector.

@mdigan mdigan closed this Jun 16, 2015
@martincox martincox deleted the feature/az/api-entrypoints-coverage branch June 14, 2019 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants