Live data from Hacker News

Viewing profile — samnco

samnco

HN member
Joined
Wed, Apr 19, 2017, 6:35 AM UTC
HN karma
7
Public activity
17 items

About samnco

Kubernetes & GPUs, what else?

Recent public activity

  1. story
  2. story
  3. comment
    Comment #14155584

    Hello, OK I gave it a try and you are absolutely right. For the nvidia-smi, I could run it the /dev/nvidia0, which is cool. I was also able to run it unprivileged. I guess my mista…

  4. comment
    Comment #14149155

    Aaah that is interesting. Let me dive into this later today and test my charts without that. It would actually make my life way easier for charting. I got that from a very early st…

  5. comment
    Comment #14148158

    privileged containers are required for the GPU to be shared with the containers. By default, the bundle come with a "auto" tag, which will activate privileged containers just when …

  6. comment
    Comment #14148142

    I have not, but it is technically possible. the PSU is the double 1100W with the GPU enablement kit. Up to 4x PCI-x 16x full speed. Also up to 1.5TB RAM, and 8x 3.5" HDD or 16x 2.5…

  7. comment
    Comment #14147927

    Here you go :) https://drive.google.com/file/d/0B1CCk51NQ4koSmkxSmxWb1E5Y0E... Replicating is not very hard. You need a lightweight x86 machine for MAAS, which takes ~20min to inst…

  8. comment
    Comment #14147474

    Yes, each GPUs has a 4x -> 16x and a 4x-4x extender, in addition to the m.2 -> PCI-e 4x adapter. So many potential failure points in there. The sole use case is CUDA. Essentially I…

  9. comment
    Comment #14147256

    I don't know. Maybe the make of the extenders isn't very good, I saw other people with similar issues. The PSU is the Corsair AX1500i (1500W), with 10x lines for GPUs. It's robust …

  10. comment
    Comment #14147061

    Actually, it was a fun DIY project I did a while ago. You can read about it here: https://hackernoon.com/installing-a-diy-bare-metal-gpu-clust... It works, but the GPUs aren't very…

  11. comment
    Comment #14147052

    Typically, you would have a set of "helm charts" (packages) for your application(s). So deploying, without data, would be something like a sequence of "helm install app-appId --val…

  12. comment
    Comment #14147008

    Ah you are right, I forgot about glusterfs. My bad. Canonical at this stage only supports Ceph commercially, but it doesn't mean GlusterFS is not a good option. I haven't tried it …

  13. comment
    Comment #14146627

    You have several options for this. If it is non HA, then you can pin a RC to a specific node, and use hostpath storage. if the container fails, it will always respawn on the same n…

  14. comment
    Comment #14146402

    You have several options: * Run Ceph in separate nodes and connect it to the cluster. With Juju, you can do that from the bundle, as Ceph is also a supported workloads. This gives …

  15. comment
    Comment #14146000

    Ahah, good point. Really the ETH stuff was "because I can". But in the same charts repository you will find a Tensorflow chart. My previous series of blogs [0] was about exactly th…

  16. comment
    Comment #14145973

    There are a few killer features that you would benefit at any size and that I really love * self healing: when you create a deployment/replica set. it will be maintained at all cos…

  17. comment
    Comment #14145937

    Canonical will officially support GPUs when they lands GA upstream. The flag is beta as of now in the Canonical Distribution of Kubernetes. Paying customers either for the managed …