Burn1ngBull3t

joined 1 year ago
[–] [email protected] 0 points 2 months ago

I’d say Daft Punk too 😄

 

Hello !

We have been discussing at work about hosting (internally) some work related stories that we find funny.

I've been looking for tools to do that should be quite simple, and display one story at a time nothing fancy.

Couldn't find anything quite like that, was wodnering if you guys knew one ? If not, i might develop it then and share it.

Thanks !

 

Hello !

I recently 3dprinted a train whistle that usually works with a mouthpiece. It works by simply blowing air in it.

However, I would like to convert it to a whistle for my bike. For that I would need a system that could blow air in it, instead of myself, with the press of a button.

Any idea on what i could start with to build that ? It would be best if the circuitry was quite compact too.

Thanks !

[–] [email protected] 5 points 9 months ago* (last edited 9 months ago)

Hello @theit8514

You are actually spot on ^^

I did look in my exports file which was like so :/mnt/DiskArray 192.168.0.16(rw) 192.168.0.65(rw)

I added a localhost line in case: /mnt/DiskArray 127.0.0.1(rw) 192.168.0.16(rw) 192.168.0.65(rw)

It didn't solve the problem. I went to investigate with the mount command:

  • Will mount on 192.168.0.65: mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test

  • Will NOT mount on 192.168.0.55 (NAS): mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test

  • Will mount on 192.168.0.55 (NAS): mount -t nfs 127.0.0.1:/mnt/DiskArray/mystuff/ /tmp/test

The mount -t nfs 192.168.0.55 is the one that the cluster does actually. So i either need to find a way for it to use 127.0.0.1 on the NAS machine, or use a hostname that might be better to resolve

EDIT:

I was acutally WAY simpler.

I just added 192.168.0.55 to my /etc/exports file. It works fine now ^^

Thanks a lot for your help@[email protected] !

 

Hello !

I currently have a problem on my kubernetes cluster.

I have 3 nodes:

  • 192.168.0.16
  • 192.168.0.65
  • 192.168.0.55

I use a storage class nfs (sigs/nfs-subdir-external-provisioner) to use an NFS.

The NFS is actually set up on the 192.168.0.55 which is also a worker node then.

I noticed that i have problems mounting volumes when a pod is created on the 192.168.0.55 node. If its one of the other two, it mounts. (The error is actually a permission denied on the 192.168.0.55 node)

I would guess that something goes wrong when kube tries to mount to NFS since it’s on the same machine ?

Any idea on how i can fix this? Cheers !

[–] [email protected] 0 points 9 months ago

Hello ! You might find Sylius suitable. It’s an Open source framework based on Symfony.

Im pretty sure it has all your requirements. The thing is that it’s a headless framework, so a frontend needs to be built on top of that if you want some custom features.

Hope that helps !