trident
rfc8312bis
| trident | rfc8312bis | |
|---|---|---|
| 3 | 1 | |
| 713 | 13 | |
| 1.1% | - | |
| 8.8 | 0.0 | |
| 7 days ago | over 1 year ago | |
| Go | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
trident
-
An io_uring-based user-space block driver
I am amazed there isn't a built-in iSCSI volume driver for docker, podman, et al. There are third party things (netapp trident[1], etc.) but no generic driver. One would think -- given the ubiquity of SAN boxes populating racks outside of "cloud" operators -- you could "-v iscsi::/mountpoint" a network block device into a container out of the box. I suppose it's difficult to deal with in cross platform way. When you read the golang source for trident you see they're just exec-ing iscsiadm on linux container hosts.
[1] https://github.com/NetApp/trident
-
OpenShift Container Registry Storage on vSphere?
As for Trident, the operator can be found here, install and update in manual as it’s not yet an certified operator.
-
Simulating big infra cloud environment locally (vmware lab?)
Anyway, one thing I need to get up to speed with is the Netapp trident kubernetes storage driver.
rfc8312bis
-
S2n-QUIC (Rust implementation of QUIC)
CUBIC is a good baseline congestion controller. It's the default one that is being used in Linux, so it should provide adequate performance for a wide range of use-cases. Plus it's not so "olde" - the specification is actively improved (see https://github.com/NTAP/rfc8312bis), and the implementation of the algorithm inside s2n-quic even lead to the discovery of spec gaps that had been fixed as part of this effort.
Like most other QUIC libraries the congestion controller is also pluggable. So if a different one makes more sense for a particular use-case, it could be integrated in the future.
What are some alternatives?
harvest - Open-metrics endpoint for ONTAP and StorageGRID
s2n-quic - An implementation of the IETF QUIC protocol
okd4-cluster-infra-apps - OKDv4 Cluster Apps Repository
delight - A Spark UI and Spark History Server alternative with CPU and Memory metrics! Delight is free, cross-platform, and open-source.
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
beegfs-csi-driver - The BeeGFS Container Storage Interface (CSI) driver provides high performing and scalable storage for workloads running in Kubernetes.
quinn - Async-friendly QUIC implementation in Rust
netapp-dataops-toolkit - The NetApp DataOps Toolkit is a Python library that makes it simple for developers, data scientists, DevOps engineers, and data engineers to perform various data management tasks, such as near-instantaneously provisioning, cloning, or snapshotting a data volume or JupyterLab workspace.
s2n - An implementation of the TLS/SSL protocols
neqo - Neqo, an implementation of QUIC in Rust