You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e4ccfcb
Browse filesBrowse the repository at this point in the historyBrowse files
@@ -24,16 +24,16 @@ Obstor Backend comes with an embedded web based object browser. Point your web b
24
24
`mc` provides a modern alternative to UNIX commands such as ls, cat, cp, mirror, diff etc. It supports filesystems and S3-compatible cloud storage services.
25
25
26
26
### Configure `mc`
27
-
```
27
+
```bash
28
28
mc aliasset myazure http://backend-ip:9000 azureaccountname azureaccountkey
29
29
```
30
30
31
31
### List containers on Microsoft Azure
32
-
```
32
+
```bash
33
33
mc ls myazure
34
-
[2017-02-22 01:50:43 PST] 0B ferenginar/
35
-
[2017-02-26 21:43:51 PST] 0B my-container/
36
-
[2017-02-26 22:10:11 PST] 0B test-container1/
34
+
[2026-05-22 01:50:43 PST] 0B ferenginar/
35
+
[2026-05-26 21:43:51 PST] 0B my-container/
36
+
[2026-05-26 22:10:11 PST] 0B test-container1/
37
37
```
38
38
39
39
### Use custom access/secret keys
@@ -53,7 +53,7 @@ Other limitations:
53
53
- Bucket notification APIs are not supported.
54
54
55
55
## Explore Further
56
-
-[Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
Copy file name to clipboardExpand all lines: docs/backend/gcs.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Obstor GCS Backend
2
2
3
-
Obstor GCS Backend allows you to access Google Cloud Storage (GCS) with S3-compatible APIs and [other supported protocols](https://obstor.net/docs/protocols)
3
+
Obstor GCS Backend allows you to access Google Cloud Storage (GCS) with S3-compatible APIs and [other supported protocols](/docs/protocols)
4
4
5
5
-[Run Obstor Backend for GCS](#run-obstor-backend-for-gcs)
6
6
-[Test Using Browser Dashboard](#test-using-obstor-browser)
@@ -20,7 +20,7 @@ Obstor GCS Backend allows you to access Google Cloud Storage (GCS) with S3-compa
20
20
**Note:** For alternate ways to set up *Application Default Credentials*, see [Setting Up Authentication for Server to Server Production Applications](https://developers.google.com/identity/protocols/application-default-credentials).
Copy file name to clipboardExpand all lines: docs/backend/hdfs.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
# Obstor HDFS Backend
2
-
Obstor HDFS backend adds S3 API and [other supported protocol](https://obstor.net/docs/protocols) support to Hadoop HDFS filesystem. Applications can use both the S3 and file APIs concurrently without requiring any data migration. Since the backend is stateless and shared-nothing, you may elastically provision as many Obstor instances as needed to distribute the load.
2
+
Obstor HDFS backend adds S3 API and [other supported protocol](/docs/protocols) support to Hadoop HDFS filesystem. Applications can use both the S3 and file APIs concurrently without requiring any data migration. Since the backend is stateless and shared-nothing, you may elastically provision as many Obstor instances as needed to distribute the load.
3
3
4
4
> NOTE: Intention of this backend implementation it to make it easy to migrate your existing data on HDFS clusters to Obstor clusters using standard tools like `mc` or `aws-cli`, if the goal is to use HDFS perpetually we recommend that HDFS should be used directly for all write operations.
5
5
6
6
## Run Obstor Backend for HDFS Storage
7
7
8
8
### Using Binary
9
9
Namenode information is obtained by reading `core-site.xml` automatically from your hadoop environment variables *$HADOOP_HOME*
10
-
```
10
+
```bash
11
11
export OBSTOR_ROOT_USER=obstor
12
12
export OBSTOR_ROOT_PASSWORD=obstor123
13
13
obstor backend hdfs
14
14
```
15
15
16
16
You can also override the namenode endpoint as shown below.
17
-
```
17
+
```bash
18
18
export OBSTOR_ROOT_USER=obstor
19
19
export OBSTOR_ROOT_PASSWORD=obstor123
20
20
obstor backend hdfs hdfs://namenode:8200
21
21
```
22
22
23
23
### Using Docker
24
24
Using docker is experimental, most Hadoop environments are not dockerized and may require additional steps in getting this to work properly. You are better off just using the binary in this situation.
25
-
```
25
+
```bash
26
26
docker run -p 9000:9000 \
27
27
--name hdfs-s3 \
28
28
-e "OBSTOR_ROOT_USER=obstor" \
@@ -44,13 +44,13 @@ To enable kerberos authentication, you need to set `hadoop.security.authenticati
44
44
```
45
45
46
46
Obstor will load `krb5.conf` from environment variable `KRB5_CONFIG` or default location `/etc/krb5.conf`.
47
-
```sh
47
+
```bash
48
48
export KRB5_CONFIG=/path/to/krb5.conf
49
49
```
50
50
51
51
If you want Obstor to use ccache for authentication, set environment variable `KRB5CCNAME` to the credential cache file path,
52
52
or Obstor will use the default location `/tmp/krb5cc_%{uid}`.
53
-
```sh
53
+
```bash
54
54
export KRB5CCNAME=/path/to/krb5cc
55
55
```
56
56
@@ -62,7 +62,7 @@ If you prefer to use keytab, with automatically renewal, you need to config thre
62
62
63
63
Please note that the username is not principal name.
64
64
65
-
```sh
65
+
```bash
66
66
export KRB5KEYTAB=/path/to/keytab
67
67
export KRB5USERNAME=hdfs
68
68
export KRB5REALM=REALM.COM
@@ -79,17 +79,17 @@ export KRB5REALM=REALM.COM
79
79
80
80
### Configure `mc`
81
81
82
-
```
82
+
```bash
83
83
mc aliasset myhdfs http://backend-ip:9000 access_key secret_key
84
84
```
85
85
86
86
### List buckets on hdfs
87
87
88
-
```
88
+
```bash
89
89
mc ls myhdfs
90
-
[2017-02-22 01:50:43 PST] 0B user/
91
-
[2017-02-26 21:43:51 PST] 0B datasets/
92
-
[2017-02-26 22:10:11 PST] 0B assets/
90
+
[2026-05-22 01:50:43 PST] 0B user/
91
+
[2026-05-26 21:43:51 PST] 0B datasets/
92
+
[2026-05-26 22:10:11 PST] 0B assets/
93
93
```
94
94
95
95
### Known limitations
@@ -101,7 +101,7 @@ Backend inherits the following limitations of HDFS storage layer:
101
101
- Concurrent multipart operations are not supported (HDFS lacks safe locking support, or poorly implemented)
102
102
103
103
## Explore Further
104
-
-[Supported Protocols](https://obstor.net/docs/protocols) - S3, SFTP, and more
Copy file name to clipboardExpand all lines: docs/backend/nas.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
# Obstor NAS Backend
2
2
3
-
Obstor Backend adds S3 and [other supported protocol](https://obstor.net/docs/protocols) compatibility to NAS storage. You may run multiple obstor instances on the same shared NAS volume as a distributed object backend.
3
+
Obstor Backend adds S3 and [other supported protocol](/docs/protocols) compatibility to NAS storage. You may run multiple obstor instances on the same shared NAS volume as a distributed object backend.
4
4
5
5
## Run Obstor Backend for NAS Storage
6
6
7
7
### Using Docker
8
8
9
9
Please ensure to replace `/shared/nasvol` with actual mount path.
0 commit comments