-
Notifications
You must be signed in to change notification settings - Fork 4
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
126 grapher registration with chronovisor #153
Conversation
ibrodkin
commented
Apr 18, 2024
- Finished Grapher RPC registration with ChronoVisor
- Introduced RecordingGroup
- Reworked KeeperRegistry organization to have Keepers & Graphers organized by RecordingGroups
- added notion of Active recordingGroups and activeStories-to-recordingGroups mapping in the KeeperRegistry
- added uniform_distribution with Mersene Twister generator to choose recording group for the new story recording
- reworked grapher & keeper notification logic for story recording start/stop
Always use high-speed network IP (172.25.x.x for Ares)
Move getting IP from hostname to a separate function
…DataStoreAdminService set to their own IP
Add work_dir, conf_file and help command line argument Add color formatting
Change from getent to dig to get IP from hostname Rename HOSTNAME_HS_NET_POSTFIX to HOSTNAME_HS_NET_SUFFIX'
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.
pls check my comments. all of them can be addressed with TODOs. no immediate actions have to be taken.
, story_id); | ||
} | ||
theKeeperRegistry->notifyRecordingGroupOfStoryRecordingStop(story_id); | ||
|
||
return chronolog::CL_SUCCESS; |
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.
TODO: we need a chronolog::ReleaseStoryResponseMsg
to return error code to clients.