Proto commits in google/gnxi

These 10 commits are when the Protocol Buffers files have changed:

2021-02-23

fix issue #261 (#262) https://github.com/google/gnxi/issues/261

The documentation is generated from this commit.

2020-12-17

regenerate go code from protos (#255)

2020-07-10

Added test for target activate and verify together Moved activationFailMessage to manager, Install has a failMessage argument now

2020-07-09

Fixed activate service Changed mockos.Unsupported to Incompatible ActivationFailMessage flag in mock os generator and embedded in OS Added FailMsgs map to Os Manager

2020-07-08

gNOI Mock OS Generator library (#110) * Wrote Mock OS generator library, outputs file where first line is version, second line is build date. This is followed by random bytes, the last 16 bytes are an md5 hash value * Corrected package name and removed main function, added period to comment * Update osgenerator.go * Update osgenerator.go Fixed function call * osgenerator now serializes a MockOS proto message * Added a "Supported" bool to the MockOS message * Changed package name from osgenerator to mockos. The library now uses protobuf to serialize the OS package. Hash hashes everything but the hash, and CheckHash can be used to validate data integrity. * Staged deleted file changes * Inserted Copyright and License Text * Removed unnecessary byte conversion * Modularised hash calculation to remove repetition * Added test for hash validation * Comments fixes * Tidy hashCalc and adjust flags Changed supported flag to unsupported, filename and version are mandatory, tidied hash calculation * Updated supported fields and arguments to unsupported, removed unnecessary temp vars * return directly fix * fix back the byte to byte thing * Update mockos.go Co-authored-by: Sam Ribeiro <ribeiro@google.com>

2020-07-02

Added manager for os service

2020-07-01

gNOI Client (#102) * Initial client for gNOI factory_reset (Issue #97), checks for errors in gRPC response and invokes Start service * Adjust comment * Removed unnecessary log of response * Added Copyright and License text * Fixed year in license text and included pb to pass Travis * Changed impossible to unsupported * Assuming all errors may be triggered simultaneously, now reporting all * Created New ResetError struct which facilitates multiple error messages Altered tests to compare error response * Added comments to ResetError * Updated Comment and removed log * Included ResetSuccess test, used continue to avoid segfail * Removed log from client_test * Changed CheckResponse() to return *ResetError

2020-06-30

Added server for factory reset service

2019-06-07

Update cert.proto

2018-07-18

gNOI Certificate Management server and client example (#25) How does a Client use gNMI and gNOI to configure or operate a Target, when the Target has not been given the state and trust to be able to establish a Secure Connection? The gNOI Certificate Management service has the methods to install Certificates in the Target, however these only work in a Secure Connection. This problem can be addressed by asserting certain conditions. When used, it allows provisioning Targets without the use of external mechanisms. In practice it allows Network Elements to be provisioned without human interaction or the need for peripheral automated systems like CLI scrapers over a Console connection. This adds a prototype gNOI Server and Clients that exemplify the above functionality.