juicefs | JuiceFS is a distributed POSIX file system built on top | Storage library

by juicedata Go Version: v1.1.0-beta1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | juicefs Summary

juicefs is a Go library typically used in Storage, Amazon S3 applications. juicefs has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

JuiceFS is a high-performance POSIX file system released under Apache License 2.0, particularly designed for the cloud-native environment. The data, stored via JuiceFS, will be persisted in object storage (e.g. Amazon S3), and the corresponding metadata can be persisted in various database engines such as Redis, MySQL, and SQLite based on the scenarios and requirements. With JuiceFS, massive cloud storage can be directly connected to big data, machine learning, artificial intelligence, and various application platforms in production environments. Without modifying code, the massive cloud storage can be used as efficiently as local storage. Video: What is JuiceFS?. Document: Quick start guide.

Support

Quality

Security

License

Reuse

Support

juicefs has a medium active ecosystem.

It has 8149 star(s) with 714 fork(s). There are 111 watchers for this library.

It had no major release in the last 12 months.

There are 102 open issues and 869 have been closed. On average issues are closed in 12 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of juicefs is v1.1.0-beta1

Quality

juicefs has 0 bugs and 0 code smells.

Security

juicefs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

juicefs code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

juicefs is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

juicefs releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 46305 lines of code, 2290 functions and 254 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of juicefs

Get all kandi verified functions for this library.

juicefs Key Features

No Key Features are available at this moment for juicefs.

juicefs Examples and Code Snippets

No Code Snippets are available at this moment for juicefs.

Community Discussions

Trending Discussions on juicefs

How to get IAM/service account used by juicefs to access GCS in GKE?

QUESTION

How to get IAM/service account used by juicefs to access GCS in GKE?

Asked 2021-Dec-16 at 10:43

I'm using a juicefs-csi in GKE. I use postgre as meta-store and GCS as storage. The corresponding setting is as follow:

...

ANSWER

Answered 2021-Dec-15 at 13:53

Ok I misunderstood you at the beginning.

When you are creating GKE cluster you can specify which GCP Service Account will be used by this cluster, like below:

By Default it's Compute Engine default service account (71025XXXXXX-compute@developer.gserviceaccount.com) which is lack of a few Cloud Product permissions (like Cloud Storage, it has Read Only). It's even described in this message.

If you want to check which Service Account was set by default to VM, you could do this via

Compute Engine > VM Instances > Choose one of the VMs from this cluster > In details find API and identity management

So You have like 3 options to solve this issue:

1. During Cluster creation

In Node Pools > Security, you have Access scopes where you can add some additional permissions.

Allow full access to all Cloud APIs to allow access for all listed Cloud APIs
Set access for each API

In your case you could just use Set access for each API and change Storage to Full.

2. Set permissions with a Service Account You would need to create a new Service Account and provide proper permissions for Compute Engine and Storage. More details about how to create SA you can find in Creating and managing service accounts.

3. Use Workload Identity

Workload Identity on your Google Kubernetes Engine (GKE) clusters. Workload Identity allows workloads in your GKE clusters to impersonate Identity and Access Management (IAM) service accounts to access Google Cloud services.

For more details you should check Using Workload Identity.

Useful links

Configuring Velero - Velero is software for backup and restore, however steps 2 and 3 are mentioned there. You would just need to adjust commands/permissions to your scenario.
Authenticating to Google Cloud with service accounts

Source https://stackoverflow.com/questions/70348036

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install juicefs

Before you begin, make sure you have:.
Redis database for metadata storage
Object storage for storing data blocks
JuiceFS Client downloaded and installed