ProHoster > Blog > Ma'muriyat > S3, NFS dan foydalanadigan mijozlar bilan mos keladigan taqsimlangan nosozliklarga chidamli LeoFS ob'ektlarini saqlashni o'rnatish
S3, NFS dan foydalanadigan mijozlar bilan mos keladigan taqsimlangan nosozliklarga chidamli LeoFS ob'ektlarini saqlashni o'rnatish
Shunga ko'ra Opennet: LeoFS β taqsimlangan nosozliklarga chidamli ob'ektni saqlash LeoFS, Amazon S3 API va REST-API dan foydalanadigan mijozlar bilan mos keladi, shuningdek NFS server rejimini qo'llab-quvvatlaydi. Kichik va juda katta ob'ektlarni saqlash uchun optimallashtirish mavjud, o'rnatilgan keshlash mexanizmi mavjud va ma'lumotlar markazlari o'rtasida saqlashni takrorlash mumkin. Loyihaning maqsadlariga dublikatlarni ortiqcha takrorlash va bitta nosozlik nuqtasini bartaraf etish orqali 99.9999999% ishonchlilikka erishish kiradi. Loyiha kodi Erlang tilida yozilgan.
LeoFS uchta komponentdan iborat:
LeoFS saqlash β ob'ektlar va metama'lumotlarni qo'shish, olish va o'chirish operatsiyalariga xizmat qiladi, replikatsiya, tiklash va mijoz so'rovlarini navbatga qo'yish uchun javobgardir.
LeoFS Gateway β REST-API yoki S3-API yordamida HTTP so'rovlariga xizmat qiladi va javoblarni mijozlarga yo'naltiradi, xotira va diskdagi eng mashhur ma'lumotlarni keshlashni ta'minlaydi.
LeoFS menejeri β LeoFS Gateway va LeoFS Storage tugunlarining ishlashini nazorat qiladi, tugunlar holatini nazorat qiladi va nazorat summalarini tekshiradi. Ma'lumotlarning yaxlitligi va yuqori saqlash mavjudligini kafolatlaydi.
Ushbu postda biz Leofs-ni ansible-playbook va test S3, NFS yordamida o'rnatamiz.
Agar siz rasmiy o'yin kitoblari yordamida LeoFS-ni o'rnatishga harakat qilsangiz, turli xil xatolarga duch kelasiz: 1,2. Ushbu postda men bunday xatolarga yo'l qo'ymaslik uchun nima qilish kerakligini yozaman.
Ansible-playbook-ni ishga tushiradigan joyda siz netcat-ni o'rnatishingiz kerak.
Inventarizatsiya namunasi
Namuna inventar (hosts.sample omborida):
# Please check roles/common/vars/leofs_releases for available versions
[all:vars]
leofs_version=1.4.3
build_temp_path="/tmp/leofs_builder"
build_install_path="/tmp/"
build_branch="master"
source="package"
#[builder]
#172.26.9.177
# nodename of leo_manager_0 and leo_manager_1 are set at group_vars/all
[leo_manager_0]
172.26.9.176
# nodename of leo_manager_0 and leo_manager_1 are set at group_vars/all
[leo_manager_1]
172.26.9.178
[leo_storage]
172.26.9.179 [email protected]
172.26.9.181 [email protected]
172.26.9.182 [email protected]
172.26.9.183 [email protected]
[leo_gateway]
172.26.9.180 [email protected]
172.26.9.184 [email protected]
[leofs_nodes:children]
leo_manager_0
leo_manager_1
leo_gateway
leo_storage
Serverni tayyorlash
Selinux-ni o'chirish. Umid qilamanki, jamoa LeoFS uchun Selinux siyosatlarini yaratadi.
- name: Install libselinux as prerequisite for SELinux Ansible module
yum:
name: "{{item}}"
state: latest
with_items:
- libselinux-python
- libsemanage-python
- name: Disable SELinux at next reboot
selinux:
state: disabled
- name: Set SELinux in permissive mode until the machine is rebooted
command: setenforce 0
ignore_errors: true
changed_when: false
sozlama netcat ΠΈ redhat-lsb-core. netcat uchun zarur leofs-adm, redhat-lsb-core OS versiyasini aniqlash uchun kerak shu yerda.
Birlamchi LeoManager-da klaster holatini tekshirish
leofs-adm status
Boshlang'ich va ikkinchi darajali ansible-playbook jurnallarida ko'rish mumkin
Chiqish shunga o'xshash bo'ladi
[System Confiuration]
-----------------------------------+----------
Item | Value
-----------------------------------+----------
Basic/Consistency level
-----------------------------------+----------
system version | 1.4.3
cluster Id | leofs_1
DC Id | dc_1
Total replicas | 2
number of successes of R | 1
number of successes of W | 1
number of successes of D | 1
number of rack-awareness replicas | 0
ring size | 2^128
-----------------------------------+----------
Multi DC replication settings
-----------------------------------+----------
[mdcr] max number of joinable DCs | 2
[mdcr] total replicas per a DC | 1
[mdcr] number of successes of R | 1
[mdcr] number of successes of W | 1
[mdcr] number of successes of D | 1
-----------------------------------+----------
Manager RING hash
-----------------------------------+----------
current ring-hash | a0314afb
previous ring-hash | a0314afb
-----------------------------------+----------
[State of Node(s)]
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
type | node | state | rack id | current ring | prev ring | updated at
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
S | [email protected] | running | | a0314afb | a0314afb | 2019-12-05 10:33:47 +0000
S | [email protected] | running | | a0314afb | a0314afb | 2019-12-05 10:33:47 +0000
S | [email protected] | running | | a0314afb | a0314afb | 2019-12-05 10:33:47 +0000
S | [email protected] | attached | | | | 2019-12-05 10:33:58 +0000
G | [email protected] | running | | a0314afb | a0314afb | 2019-12-05 10:33:49 +0000
G | [email protected] | running | | a0314afb | a0314afb | 2019-12-05 10:33:49 +0000
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
leofs-adm add-bucket leofs 9c2615f32e81e6a1caf5
OK
Cheklar ro'yxati:
leofs-adm get-buckets
cluster id | bucket | owner | permissions | created at
-------------+----------+--------+------------------+---------------------------
leofs_1 | leofs | leofs | Me(full_control) | 2019-12-02 10:44:02 +0000
s3cmd sozlanmoqda
Dalada HTTP Proxy server name Gateway server IP-ni belgilang
s3cmd --configure
Enter new values or accept defaults in brackets with Enter.
Refer to user manual for detailed description of all options.
Access key and Secret key are your identifiers for Amazon S3. Leave them empty for using the env variables.
Access Key [9c2615f32e81e6a1caf5]:
Secret Key [8aaaa35c1ad78a2cbfa1a6cd49ba8aaeb3ba39eb]:
Default Region [US]:
Use "s3.amazonaws.com" for S3 Endpoint and not modify it to the target Amazon S3.
S3 Endpoint [s3.amazonaws.com]:
Use "%(bucket)s.s3.amazonaws.com" to the target Amazon S3. "%(bucket)s" and "%(location)s" vars can be used
if the target S3 system supports dns based buckets.
DNS-style bucket+hostname:port template for accessing a bucket [%(bucket)s.s3.amazonaws.com]: leofs
Encryption password is used to protect your files from reading
by unauthorized persons while in transfer to S3
Encryption password:
Path to GPG program [/usr/bin/gpg]:
When using secure HTTPS protocol all communication with Amazon S3
servers is protected from 3rd party eavesdropping. This method is
slower than plain HTTP, and can only be proxied with Python 2.7 or newer
Use HTTPS protocol [No]:
On some networks all internet access must go through a HTTP proxy.
Try setting it here if you can't connect to S3 directly
HTTP Proxy server name [172.26.9.180]:
HTTP Proxy server port [8080]:
New settings:
Access Key: 9c2615f32e81e6a1caf5
Secret Key: 8aaaa35c1ad78a2cbfa1a6cd49ba8aaeb3ba39eb
Default Region: US
S3 Endpoint: s3.amazonaws.com
DNS-style bucket+hostname:port template for accessing a bucket: leofs
Encryption password:
Path to GPG program: /usr/bin/gpg
Use HTTPS protocol: False
HTTP Proxy server name: 172.26.9.180
HTTP Proxy server port: 8080
Test access with supplied credentials? [Y/n] Y
Please wait, attempting to list all buckets...
Success. Your access key and secret key worked fine :-)
Now verifying that encryption works...
Not configured. Never mind.
Save settings? [y/N] y
Configuration saved to '/home/user/.s3cfg'
Agar siz xatoga duch kelsangiz ERROR: S3 xatosi: 403 (Access Denied): Kirish taqiqlangan:
s3cmd put test.py s3://leofs/
upload: 'test.py' -> 's3://leofs/test.py' [1 of 1]
382 of 382 100% in 0s 3.40 kB/s done
ERROR: S3 error: 403 (AccessDenied): Access Denied
Keyin s3cmd konfiguratsiyasida signature_v2 ni True ga o'zgartirishingiz kerak. Bunda tafsilotlar nashr.
Agar signature_v2 False bo'lsa, quyidagi kabi xatolik yuz beradi:
WARNING: Retrying failed request: /?delimiter=%2F (getaddrinfo() argument 2 must be integer or string)
WARNING: Waiting 3 sec...
WARNING: Retrying failed request: /?delimiter=%2F (getaddrinfo() argument 2 must be integer or string)
WARNING: Waiting 6 sec...
ERROR: Test failed: Request failed for: /?delimiter=%2F
Yuk sinovi
1 GB hajmli fayl yarating
fallocate -l 1GB 1gb
Uni Leofs-ga yuklang
time s3cmd put 1gb s3://leofs/
real 0m19.099s
user 0m7.855s
sys 0m1.620s
Π‘ΡΠ°ΡΠΈΡΡΠΈΠΊΠ°
leofs-adm du 1 tugun uchun:
leofs-adm du [email protected]
active number of objects: 156
total number of objects: 156
active size of objects: 602954495
total size of objects: 602954495
ratio of active size: 100.0%
last compaction start: ____-__-__ __:__:__
last compaction end: ____-__-__ __:__:__
Xulosa unchalik ma'lumotli emasligini ko'ramiz.
Keling, ushbu fayl qayerda joylashganligini ko'rib chiqaylik.
leofs-adm whereis leofs/1gb
Biz NFSni Leo Gateway 172.26.9.184 serverida faollashtiramiz.
Server va mijozga nfs-utils-ni o'rnating
sudo yum install nfs-utils
Ko'rsatmalarga muvofiq, biz konfiguratsiya faylini tuzatamiz /usr/local/leofs/current/leo_gateway/etc/leo_gateway.conf
protocol = nfs
172.26.9.184 serverida rpcbind va leofs-shlyuzni ishga tushiring
sudo service rpcbind start
sudo service leofs-gateway restart
leo_manager ishlayotgan serverda NFS uchun chelak yarating va NFS ga ulanish uchun kalit yarating.
leofs-adm add-bucket test 05236
leofs-adm gen-nfs-mnt-key test 05236 ip-Π°Π΄ΡΠ΅Ρ-nfs-ΠΊΠ»ΠΈΠ΅Π½ΡΠ°
NFS ga ulanish
sudo mkdir /mnt/leofs
## for Linux - "sudo mount -t nfs -o nolock <host>:/<bucket>/<token> <dir>"
sudo mount -t nfs -o nolock ip-Π°Π΄ΡΠ΅Ρ-nfs-ΡΠ΅ΡΠ²Π΅ΡΠ°-ΡΠ°ΠΌ-Π³Π΄Π΅-Ρ-Π²Π°Ρ-ΡΡΡΠ°Π½ΠΎΠ²Π»Π΅Π½-gateway:/bucket/access_key_id/ΠΊΠ»ΡΡ-ΠΏΠΎΠ»ΡΡΠ΅Π½Π½ΡΠΉ-ΠΎΡ-gen-nfs-mnt-key /mnt/leofs
sudo mount -t nfs -o nolock 172.26.9.184:/test/05236/bb5034f0c740148a346ed663ca0cf5157efb439f /mnt/leofs
NFS mijozi orqali disk maydonini ko'rish
Har bir saqlash tugunida 40 GB disk mavjudligini hisobga olgan holda disk maydoni (3 ishlaydigan tugun, 1 biriktirilgan tugun):
df -hP
Filesystem Size Used Avail Use% Mounted on
172.26.9.184:/test/05236/e7298032e78749149dd83a1e366afb328811c95b 60G 3.6G 57G 6% /mnt/leofs
6 ta saqlash tugunlari bilan LeoFSni o'rnatish.
Inventarizatsiya (quruvchisiz):
# Please check roles/common/vars/leofs_releases for available versions
[all:vars]
leofs_version=1.4.3
build_temp_path="/tmp/leofs_builder"
build_install_path="/tmp/"
build_branch="master"
source="package"
# nodename of leo_manager_0 and leo_manager_1 are set at group_vars/all
[leo_manager_0]
172.26.9.177
# nodename of leo_manager_0 and leo_manager_1 are set at group_vars/all
[leo_manager_1]
172.26.9.176
[leo_storage]
172.26.9.178 [email protected]
172.26.9.179 [email protected]
172.26.9.181 [email protected]
172.26.9.182 [email protected]
172.26.9.183 [email protected]
172.26.9.185 [email protected]
[leo_gateway]
172.26.9.180 [email protected]
172.26.9.184 [email protected]
[leofs_nodes:children]
leo_manager_0
leo_manager_1
leo_gateway
leo_storage
Chiqish leofs-adm holati
Chiqish leofs-adm holati
[System Confiuration]
-----------------------------------+----------
Item | Value
-----------------------------------+----------
Basic/Consistency level
-----------------------------------+----------
system version | 1.4.3
cluster Id | leofs_1
DC Id | dc_1
Total replicas | 2
number of successes of R | 1
number of successes of W | 1
number of successes of D | 1
number of rack-awareness replicas | 0
ring size | 2^128
-----------------------------------+----------
Multi DC replication settings
-----------------------------------+----------
[mdcr] max number of joinable DCs | 2
[mdcr] total replicas per a DC | 1
[mdcr] number of successes of R | 1
[mdcr] number of successes of W | 1
[mdcr] number of successes of D | 1
-----------------------------------+----------
Manager RING hash
-----------------------------------+----------
current ring-hash | d8ff465e
previous ring-hash | d8ff465e
-----------------------------------+----------
[State of Node(s)]
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
type | node | state | rack id | current ring | prev ring | updated at
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:29 +0000
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:29 +0000
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:30 +0000
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:29 +0000
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:29 +0000
S | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:29 +0000
G | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:31 +0000
G | [email protected] | running | | d8ff465e | d8ff465e | 2019-12-06 05:18:31 +0000
-------+----------------------+--------------+---------+----------------+----------------+----------------------------
Har bir saqlash tugunida 40 Gb disk mavjudligini hisobga olgan holda disk maydoni (6 ishlayotgan tugun):
df -hP
Filesystem Size Used Avail Use% Mounted on
172.26.9.184:/test/05236/e7298032e78749149dd83a1e366afb328811c95b 120G 3.6G 117G 3% /mnt/leofs