ibrodkin
commented
1 year ago Changes are ready for review:
- Added DataCollectionService & DataCollectionClient implementations. DataCollectionService is the service that will be running as part of he ChronoKeeper process expecting instructions from the ChronoVisor to start/stop story recording. this same service can be used for communication with the other keepers in the future if needed.
- Added KeeperRegistrationMsg that ChronoKeeperProcess sends to ChronoVisor on startup, includes information about both KeeperRecordingService ( service facing client application connections) and DataCollectionService ( service for communication with the ChronoVisor)
- Added state management logic to KeeperRegistry
- Integrated DataCollectionClient with KeeperRegistry
- Implemented KeeperRegistry::notifyKeepersOfStoryRecordingStart() and KeeperRegistry::notifyKeepersOfStoryRecordingStop Added KeeperDataStore & StoryPipeline classes that are not yet fully implemented and are only included in this Pull Request to show how the DataCollectionService, KeeperDataStore, IngestionQueue, and KeeeperRecordingService will be working together.
Extend ChronoVisor Story Acquisition/Release API to include communication with the ChronoKeeper processes that should be ready to except messages for the acquired story
KeeperRegistryService needs to have API for communicating story acquisition and release events to the KeeperRegistryClients KeeperProcess needs to have functionality to maintain some new registry of active storyteller clients to expect. IT would make sense to at least add some stubs for client-story authentication tokens , that KeeperProcess should be expecting/maintaining