...

Ideally, the Anylog component should not need root-level access.    That is correct. 

The Anylog component maintains its own P2P network. That is correct.

APIs

<Describe and new/changed/deprecated APIs, including before and after snippets for clarity. Include which components or users will use the APIs.>

Link to Anylog docs.

• Each AnyLog instance includes a CLI option.
• Data monitored can be generated by AnyLog existing functionalities. For example, disk space, memory usage, networking status, cpu state, processes running etc. are build-in functionalities that can be leverage on each node.
• Southbound Connectors are detailed in the Adding Data document.
• Northbound connectors are based on SQL and AnyLog CLI commands that are transferred to the network using REST. 

AnyLog documentation:

• Table of Content
• Getting Started

Build, Install, Packaging

<Describe any changes to the way any component of the system is built (e.g. agent packages, containers, etc), installed (operators, manual install, batch install, SDO), configured, and deployed (consider the hub and edge nodes).>

Will be done using Open Horizon (we had a prototype working).

A detailed Docker based deployment training is available with this link.

Documentation Notes

<Describe the aspects of documentation that will be new/changed/updated. Be sure to indicate if this is new or changed doc, the impacted artifacts (e.g. technical doc, website, etc) and links to the related doc issue(s) in github.>

• Document deployment with Open Horizon.
• AnyLog CLI extending the Open Horizon CLI.

Test

<Summarize new automated tests that need to be added in support of this feature, and describe any special test requirements that you can foresee.>

Simulate edge nodes deployed with AnyLog.