Go implementation of FrostFS SDK
sdk
Find a file
Alex Vanin 6e81e13e1b [#218] client: Decode status at io.EOF in the client-side stream
Object service of NeoFS API contains one client-side stream method:
object.Put. In client-side streams, server can return an error after
processing stream message. In this case write method returns `io.EOF`
and actual error reason is encoded in response status, which is
obtained after `Close()`. Client library should process such case.

Signed-off-by: Alex Vanin <alexey@nspcc.ru>
2022-04-21 15:57:37 +03:00
.github/workflows [#37] ci: Add github workflows 2021-10-15 17:37:18 +03:00
accounting [#170] accounting: Remove message sub-string from V2-methods 2022-03-21 12:37:53 +03:00
acl [#170] acl: Document package functionality 2022-03-25 19:15:22 +03:00
audit [#170] oid, cid: Add marshal format checks 2022-04-13 17:32:25 +03:00
bearer [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
checksum [#170] checksum: Drop Empty method 2022-04-13 10:53:57 +03:00
client [#218] client: Decode status at io.EOF in the client-side stream 2022-04-21 15:57:37 +03:00
container [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
crypto [#190] crypto/ecdsa: Actualize package docs 2022-04-19 12:55:11 +03:00
eacl [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
netmap [#168] netmap: Add simple selector benchmark 2022-03-15 16:59:59 +03:00
ns [#170] oid, cid: Refactor and document package functionality 2022-04-13 17:32:25 +03:00
object [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
policy [#168] policy: Adopt replacement of pointer slices with struct slices 2022-03-15 16:59:59 +03:00
pool [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
reputation [#190] crypto/ecdsa: Use separate types for RFC-6979 signature algo 2022-04-19 12:55:11 +03:00
session [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
storagegroup [#170] storagegroup: Refactor and document package functionality 2022-04-13 18:33:33 +03:00
subnet [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
user [#199] owner: Rename to user, refactor and doc 2022-04-19 18:44:02 +03:00
version [#170] version: Add specification string encoder 2022-04-13 10:28:12 +03:00
.gitattributes [#3] policy: use ANTLRv4 parser generator 2021-06-15 11:42:14 +03:00
.gitignore Add vendor directory to gitignore 2021-07-07 17:20:36 +03:00
.golangci.yml [#37] ci: Replace golint by revive 2021-10-15 17:37:18 +03:00
go.mod [#170] checksum: Drop Empty method 2022-04-13 10:53:57 +03:00
go.sum [#170] checksum: Drop Empty method 2022-04-13 10:53:57 +03:00
LICENSE Initial commit 2021-02-25 11:35:04 +03:00
Makefile [nspcc-dev/neofs-node#166] *: Add project files 2021-05-20 23:57:51 +03:00
README.md [#179] Rename resolver package to ns 2022-04-13 10:46:27 +03:00

neofs-sdk-go

Go implementation of NeoFS SDK. It contains high-level version-independent wrappers for structures from neofs-api-go as well as helper functions for simplifying node/dApp implementations.

Repository structure

accounting

Contains fixed-point Decimal type for performing balance calculations.

eacl

Contains Extended ACL types for fine-grained access control. There is also a reference implementation of checking algorithm which is used in NeoFS node.

checksum

Contains Checksum type encapsulating checksum as well as it's kind. Currently Sha256 and Tillich-Zemor hashsum are in use.

owner

owner.ID type represents single account interacting with NeoFS. In v2 version of protocol it is just raw bytes behing base58-encoded address in Neo blockchain. Note that for historical reasons it contains version prefix and checksum in addition to script-hash.

token

Contains Bearer token type with several NeoFS-specific methods.

ns

In NeoFS there are 2 types of name resolution: DNS and NNS. NNS stands for Neo Name Service is just a contract deployed on a Neo blockchain. Basically, NNS is just a DNS-on-chain which can be used for resolving container nice-names as well as any other name in dApps. See our CoreDNS plugin for the example of how NNS can be integrated in DNS.

session

To help lightweight clients interact with NeoFS without sacrificing trust, NeoFS has a concept of session token. It is signed by client and allows any node with which a session is established to perform certain actions on behalf of the user.

client

Contains client for working with NeoFS.

c, _ := client.New(
    client.WithAddress("localhost:40005"), // endpoint address
    client.WithDefaultPrivateKey(key),     // private key for request signing
    client.WithNeoFSErrorHandling(),       // enable erroneous status parsing
    client.WithTLSConfig(&tls.Config{}))   // custom TLS configuration
    
ctx, cancel := context.WithTimeout(context.Background(), 5 * time.Second)
defer cancel()

res, err := c.BalanceGet(ctx, owner)
if err != nil {
    return
}

fmt.Printf("Balance for %s: %s\n", owner, res.Amount())

Response status

In NeoFS every operation can fail on multiple levels, so a single error doesn't suffice, e.g. consider a case when object was put on 4 out of 5 replicas. Thus, all request execution details are contained in Status returned from every RPC call. dApp can inspect them if needed and perform any desired action. In the case above we may want to report these details to the user as well as retry an operation, possibly with different parameters. Status wire-format is extendable and each node can report any set of details it wants. The set of reserved status codes can be found in NeoFS API. There is also a client.WithNeoFSErrorHandling() to seamlessly convert erroneous statuses into Go error type.

policy

Contains helpers allowing conversion of placing policy from/to JSON representation and SQL-like human-readable language.

p, _ := policy.Parse(`
    REP 2
    SELECT 6 FROM F
    FILTER StorageType EQ SSD AS F`)

// Convert parsed policy back to human-readable text and print.
println(strings.Join(policy.Encode(p), "\n"))

netmap

Contains CRUSH-like implementation of container node selection algorithm. Relevant details are described in this paper http://ceur-ws.org/Vol-2344/short10.pdf . Note that it can be outdated in some details.

netmap/json_tests subfolder contains language-agnostic tests for selection algorithm.

import (
    "github.com/nspcc-dev/neofs-sdk-go/netmap"
    "github.com/nspcc-dev/neofs-sdk-go/object"
)

func placementNodes(addr *object.Address, p *netmap.PlacementPolicy, neofsNodes []netmap.NodeInfo) {
    // Convert list of nodes in NeoFS API format to the intermediate representation.
    nodes := netmap.NodesFromInfo(nodes)

    // Create new netmap (errors are skipped for the sake of clarity). 
    nm, _ := NewNetmap(nodes)

    // Calculate nodes of container.
    cn, _ := nm.GetContainerNodes(p, addr.ContainerID().ToV2().GetValue())

    // Return list of nodes for each replica to place object on in the order of priority.
    return nm.GetPlacementVectors(cn, addr.ObjectID().ToV2().GetValue())
}

pool

Simple pool for managing connections to NeoFS nodes.

acl, checksum, version, signature

Contain simple API wrappers.

logger

Wrapper over zap.Logger which is used across NeoFS codebase.

util

Utilities for working with signature-related code.