Table of Contents
Jibe Documentation
Jibe processes provider event streams and logs to update Access Anywhere metadata in near real-time.
Getting Started
Event Sources
Advanced Settings
Background
Nasuni Access Anywhere delivers high-performance file access for remote and hybrid (distributed) users along with productivity tools that let them manage files from anywhere on any device.
The Access Anywhere supports bi-modal access. Users and applications may update files and objects through Access Anywhere or directly through storage APIs like SMB, or Amazon S3. When objects and files are updated outside of Access Anywhere, the metadata index must be updated, or “resynced”.
Many storage systems produce update notifications that can be used to update Access Anywhere metadata. Jibe is an application that can process notifications to keep the Access Anywhere index updated. This way, searching and other services will always be using up-to-date metadata.
Jibe is able to process SMB notifications, AWS API calls, S3 event notifications, and AWS CloudTrail files.
Architecture
Jibe is a Python application that runs as a Docker container. The Docker image is designed to run inside a Access Anywhere node and call out to multiple nodes in a Access Anywhere cluster.
Settings for Jibe include event “sources” - log files or event streams providing storage change events.
Worker threads listen for events, or monitor folders for new log files and then process events using the syncOnProviderEvent API call.
Usage
See the documentation pages for different event sources. One Jibe instance may use different types of event sources or “flavors”.