[ Gluster FS 9 ] Manage Gluster Storage with Heketi REST API

Поделиться
HTML-код
  • Опубликовано: 2 ноя 2024

Комментарии • 42

  • @mmlmahesh
    @mmlmahesh 4 года назад +2

    Of the the best RUclips channel which focuses on practical real-time industrial work.I’ve referred to many of your videos to work on my current project.You are really awesome sir.

    • @justmeandopensource
      @justmeandopensource  4 года назад +1

      Hi Mahesh, that is very kind of you. Much appreciated. Thanks for watching.

  • @HosseinOjvar
    @HosseinOjvar 2 года назад +1

    Very clear and straightforward tutorial
    ;)

  • @angelogoncalvesdias4504
    @angelogoncalvesdias4504 3 года назад +1

    Excellent video. Quick and clear.Excellent content.

  • @mohammednawaz7501
    @mohammednawaz7501 4 года назад +2

    Very well done with the flow of the video. Learned from your videoas alot!! Thank you

  • @taharbounsiar137
    @taharbounsiar137 4 года назад +1

    Hello Venkat, you are doing great job with your videos, waining for next one, configuring k8s + heketi + gluster on dynamic provision

    • @justmeandopensource
      @justmeandopensource  4 года назад +1

      Hi Tahar, thanks for watching. Thats next in my list. I should have done it on Monday Nov 9th but was so busy this week. I will try and get it done soon. Cheers.

  • @snapp_r
    @snapp_r 2 года назад

    hey, first of all.. thanks for sharing all this tutorial~
    it really helps.. and I appreciate it!
    I wanna ask something tho..
    with this setup or the one for kubernetes, the heketi service will be a single point of failure right?
    how can we make a fail-over for it? is there any backup/db for the cluster?

  • @vishalkarki89
    @vishalkarki89 4 года назад +3

    Hey Venkat,
    Thank you for putting out such quality content. A quick question, do you have any plans to make videos on Ceph Storage?

    • @justmeandopensource
      @justmeandopensource  4 года назад +3

      Hi Vishal, thanks for watching. Rook/Ceph is in my list. I will do a video at some point. Cheers.

    • @jaganyalla
      @jaganyalla 3 года назад +1

      @@justmeandopensource Thanks Venkat.

    • @justmeandopensource
      @justmeandopensource  3 года назад +1

      You are welcome.

  • @rajip81
    @rajip81 3 года назад

    Thank you for all the videos. Flow is perfect. I've learnt allot from all your videos. COuld you please let me know to use this storage as a data domain in Ovirt node

  • @kmute90
    @kmute90 3 года назад

    Do you have any idea why does it say "Error: New Node doesn't have glusterd running" when trying to add new node to heketi cluster?

  • @corwaincyrus6840
    @corwaincyrus6840 4 года назад +1

    Just came here to add a view and a like 😅

  • @hrishekessaraghueeti1258
    @hrishekessaraghueeti1258 4 года назад +1

    Hi, could you please upload video of integrating heketi with kubernetes cluster, I am having issue where my pvc is always in pending status not going to bound... Eagerly waiting for your next upload

    • @justmeandopensource
      @justmeandopensource  4 года назад +2

      Just done with the recording and scheduled for release tomorrow at 7:30 GMT. Hope it will be of some help.

  • @ardyjaroensuk5452
    @ardyjaroensuk5452 4 года назад +1

    when i add device from glusterfs node show this error " Initializing device /dev/vdc failed (already initialized or contains data?): /bin/bash: /usr/sbin/lvm: No such file or directory " but this device not contains data

    • @justmeandopensource
      @justmeandopensource  4 года назад +1

      Hi Ardy, thanks for watching. Please try this command and then add the device.
      wipefs -a /dev/vdb

    • @umitakin9523
      @umitakin9523 3 года назад

      @@justmeandopensource I did that but still same problem? how can add device ?
      gluster-version 7.9
      heketi-cli version 10.2
      I run that too;
      dd if=/dev/zero of=/dev/sda bs=512 count=1
      and this;
      heketi-cli device add --destroy-existing-data --name /dev/sda --node 73d5df5b44d3419b92574612d70ca7c3

  • @SK-wf1oh
    @SK-wf1oh Год назад

    DO You know how we can deploy heketi server on docker container?

  • @SK-wf1oh
    @SK-wf1oh Год назад

    so how can I create storage class for kubernetes cluster by heketi?

  • @vahaggn
    @vahaggn 2 года назад

    Hi how to expand the pvc is it possible?

  • @zaheerhussain5311
    @zaheerhussain5311 Год назад

    Hi
    I am facing this error while running
    heketi-cli node add --zone 1 --cluster d421c1cd1883ff0ffbf243f67c222155 --management-host-name server-1 --storage-host-name server-1
    Unable to create node: New Node doesn't have glusterd running
    even though
    in "Enable JWT authorization. Please enable for deployment",
    "use_auth": true
    Please suggest.
    Regards
    Zaheer

  • @lazydevops90
    @lazydevops90 4 года назад +1

    Bro please give suggestions on how to do auto snapshot glusterfs

    • @justmeandopensource
      @justmeandopensource  4 года назад +1

      Hi Vinu, I haven't played with Glusterfs snapshot. Looks straight forward from the below documentation.
      docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Snapshots/
      And for scheduling automatic snapshots, take a look at below documentation from Red Hat.
      access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.1/html/administration_guide/ch16s12

  • @hrishekessaraghueeti1258
    @hrishekessaraghueeti1258 3 года назад +1

    Is there an alternative for heketi that is not deprecated

    • @justmeandopensource
      @justmeandopensource  3 года назад +1

      Where do you that heketi is deprecated?

    • @AravindaVK
      @AravindaVK 3 года назад

      @@justmeandopensource mentioned in the README github.com/heketi/heketi#important-notice

    • @AravindaVK
      @AravindaVK 3 года назад +1

      We are working on the GlusterFS based K8s storage solution kadalu.io for quite some time. Let us know if it is useful for you. Github: github.com/kadalu/kadalu

  • @monaminor3342
    @monaminor3342 3 года назад +1

    device add nahi ho rhi.
    Error: Initializing device /dev/sdd failed (already initialized or contains data?): /bin/bash: /usr/sbin/lvm: No such file or directory

    • @justmeandopensource
      @justmeandopensource  3 года назад +1

      Hi, thanks for watching. If you get that error, possibly there is some data already in that disk/partition.
      Try wiping it with this command.
      sudo wipefs -a /dev/sdd

    • @monaminor3342
      @monaminor3342 3 года назад +1

      Done that as well.
      Wiped.
      And added new disk as well.
      Tried adding new device it giving only the same error.
      Please help in this

    • @foxipub3629
      @foxipub3629 3 года назад

      @@justmeandopensource Hi V! Same problem is here. Its only working if executor "mock" - i am still unable resolve it ...

    • @foxipub3629
      @foxipub3629 3 года назад

      Update: Unresolved on Ubuntu 18.04.5 LTS. Recreate on Centos 7.8 - Just works fine.

  • @lazydevops90
    @lazydevops90 4 года назад +1

    Then why copy files to mount folder taking more time. ?

    • @justmeandopensource
      @justmeandopensource  4 года назад +1

      Hi Vinu, thanks for watching. I just explained the process. I haven't used it much. This needs some troubleshooting. Various things could be the cause of slow copy.

  • @SK-wf1oh
    @SK-wf1oh Год назад

    sorry but I've met a problem on ALMA OS
    systemctl status heketi
    ● heketi.service - Heketi Server
    Loaded: loaded (/etc/systemd/system/heketi.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Thu 2023-01-05 14:12:06 CET; 4s ago
    Process: 3736046 ExecStart=/usr/local/bin/heketi --config=/etc/heketi/heketi.json (code=exited, status=203/EXEC)
    Main PID: 3736046 (code=exited, status=203/EXEC)
    Jan 05 14:12:06 alma_os_server systemd[1]: heketi.service: Service RestartSec=100ms expired, scheduling restart.
    Jan 05 14:12:06 alma_os_server systemd[1]: heketi.service: Scheduled restart job, restart counter is at 5.
    Jan 05 14:12:06 alma_os_server systemd[1]: Stopped Heketi Server.
    Jan 05 14:12:06 alma_os_server systemd[1]: heketi.service: Start request repeated too quickly.
    Jan 05 14:12:06 alma_os_server systemd[1]: heketi.service: Failed with result 'exit-code'.
    Jan 05 14:12:06 alma_os_server systemd[1]: Failed to start Heketi Server.