#longhorn — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #longhorn, aggregated by home.social.
-
Собачий корм, фичекрип и несостоявшаяся революция — Windows Longhorn
Многие из нас до сих пор нежно хранят в своем сердце воспоминания о Windows XP. И есть за что. Дружелюбная к пользователю, надежная (особенно после 98-ой и «линолеума»), да и просто ставшая для многих проводником в мир компьютеров — именно такой и была эта ОС. А вот пришедшую ей на смену Vista ругают до сих пор. В первую очередь, из-за низкой стабильности, которая бросалась в глаза после отточенной сервис-паками XP. Однако между XP и Vista есть еще кое-что. Проект, который не стал успешным релизом, но который на десятилетия определил устройство Windows. И имя ему — Longhorn. Почему эта задумывавшаяся революционной ОС так и не вышла, как амбиции столкнулись с реальностью и какие идеи из той эпохи до сих пор живут в «винде» — разбираемся в этой статье.
https://habr.com/ru/companies/ispsystem/articles/1033042/
#windows #longhorn #vista #ос #операционные_системы #microsoft
-
Собачий корм, фичекрип и несостоявшаяся революция — Windows Longhorn
Многие из нас до сих пор нежно хранят в своем сердце воспоминания о Windows XP. И есть за что. Дружелюбная к пользователю, надежная (особенно после 98-ой и «линолеума»), да и просто ставшая для многих проводником в мир компьютеров — именно такой и была эта ОС. А вот пришедшую ей на смену Vista ругают до сих пор. В первую очередь, из-за низкой стабильности, которая бросалась в глаза после отточенной сервис-паками XP. Однако между XP и Vista есть еще кое-что. Проект, который не стал успешным релизом, но который на десятилетия определил устройство Windows. И имя ему — Longhorn. Почему эта задумывавшаяся революционной ОС так и не вышла, как амбиции столкнулись с реальностью и какие идеи из той эпохи до сих пор живут в «винде» — разбираемся в этой статье.
https://habr.com/ru/companies/ispsystem/articles/1033042/
#windows #longhorn #vista #ос #операционные_системы #microsoft
-
Собачий корм, фичекрип и несостоявшаяся революция — Windows Longhorn
Многие из нас до сих пор нежно хранят в своем сердце воспоминания о Windows XP. И есть за что. Дружелюбная к пользователю, надежная (особенно после 98-ой и «линолеума»), да и просто ставшая для многих проводником в мир компьютеров — именно такой и была эта ОС. А вот пришедшую ей на смену Vista ругают до сих пор. В первую очередь, из-за низкой стабильности, которая бросалась в глаза после отточенной сервис-паками XP. Однако между XP и Vista есть еще кое-что. Проект, который не стал успешным релизом, но который на десятилетия определил устройство Windows. И имя ему — Longhorn. Почему эта задумывавшаяся революционной ОС так и не вышла, как амбиции столкнулись с реальностью и какие идеи из той эпохи до сих пор живут в «винде» — разбираемся в этой статье.
https://habr.com/ru/companies/ispsystem/articles/1033042/
#windows #longhorn #vista #ос #операционные_системы #microsoft
-
Собачий корм, фичекрип и несостоявшаяся революция — Windows Longhorn
Многие из нас до сих пор нежно хранят в своем сердце воспоминания о Windows XP. И есть за что. Дружелюбная к пользователю, надежная (особенно после 98-ой и «линолеума»), да и просто ставшая для многих проводником в мир компьютеров — именно такой и была эта ОС. А вот пришедшую ей на смену Vista ругают до сих пор. В первую очередь, из-за низкой стабильности, которая бросалась в глаза после отточенной сервис-паками XP. Однако между XP и Vista есть еще кое-что. Проект, который не стал успешным релизом, но который на десятилетия определил устройство Windows. И имя ему — Longhorn. Почему эта задумывавшаяся революционной ОС так и не вышла, как амбиции столкнулись с реальностью и какие идеи из той эпохи до сих пор живут в «винде» — разбираемся в этой статье.
https://habr.com/ru/companies/ispsystem/articles/1033042/
#windows #longhorn #vista #ос #операционные_системы #microsoft
-
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
@[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/
-
@[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/
-
@[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/
-
@[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/
-
@[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/
-
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
I already use #Borg/#Borgmatic for my #Docker backups and dat was easy to setup. Then I tried doing the same thing for my #Kubernetes cluster, then realised it may not be that simple to backup the volumes - the databases, that was easy since Borgmatic supports that super easily. The PVCs tho, which uses #Longhorn underneath... I'm not too sure how to back them up - esp the
RWOones. One option I've found seems to be to set up backups, possible for Longhorn, to some #S3 storage location but ofc #MinIO is like, not an option now. Idk if finding a diff S3 option (#Garage? #RustFS?) is a good idea or, really, how do others back up data on their #K8s cluster in their #homelab/workplace? -
Unpopular opinion: I have fought with ZFS under Talos for months, but in reality what I needed was Longhorn.
Yeah, yeah, I now, different things. But that's just to say that ZFS is not the silver bullet that some people try to convince you of.
-
Unpopular opinion: I have fought with ZFS under Talos for months, but in reality what I needed was Longhorn.
Yeah, yeah, I now, different things. But that's just to say that ZFS is not the silver bullet that some people try to convince you of.
-
Unpopular opinion: I have fought with ZFS under Talos for months, but in reality what I needed was Longhorn.
Yeah, yeah, I now, different things. But that's just to say that ZFS is not the silver bullet that some people try to convince you of.
-
Unpopular opinion: I have fought with ZFS under Talos for months, but in reality what I needed was Longhorn.
Yeah, yeah, I now, different things. But that's just to say that ZFS is not the silver bullet that some people try to convince you of.
-
Unpopular opinion: I have fought with ZFS under Talos for months, but in reality what I needed was Longhorn.
Yeah, yeah, I now, different things. But that's just to say that ZFS is not the silver bullet that some people try to convince you of.
-
Yeah, I'm plenty aware that using networked volumes with Kubernetes is the better way to go, but I gotta hand it to Longhorn: the distributed replicas make it a breeze to move stuff around and do physical maintenance in the nodes. 👏
-
Yeah, I'm plenty aware that using networked volumes with Kubernetes is the better way to go, but I gotta hand it to Longhorn: the distributed replicas make it a breeze to move stuff around and do physical maintenance in the nodes. 👏
-
Yeah, I'm plenty aware that using networked volumes with Kubernetes is the better way to go, but I gotta hand it to Longhorn: the distributed replicas make it a breeze to move stuff around and do physical maintenance in the nodes. 👏
-
Yeah, I'm plenty aware that using networked volumes with Kubernetes is the better way to go, but I gotta hand it to Longhorn: the distributed replicas make it a breeze to move stuff around and do physical maintenance in the nodes. 👏
-
Yeah, I'm plenty aware that using networked volumes with Kubernetes is the better way to go, but I gotta hand it to Longhorn: the distributed replicas make it a breeze to move stuff around and do physical maintenance in the nodes. 👏
-
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
Updated my #homelab to #k3s 1.35, deployed #vaultwarden, #pihole with #unbound and #forgejo with #woodpecker. All the web guis have #letsencryt certificates. Storage redundancy is achieved by #longhorn which maintains redundant copies of pvcs across the nodes. The nodes are vms controlled by #incus, so that I can shut down the whole k8s thingy with a simple incus stop command when I’m done playing.
k3s is really nice and easy to deploy and well documented, getting things to run in k8s though is mainly pasting yaml from the internet and hoping for the best. -
So it appears like, for the last ~months, my MTU configuration was REALLY wrong
Hinted by the immich longhorn replica not rebuilding, but I also didn't know, the extreme slowness of any service using a db cluster where the master node wasn't in the same region
I had put the slowness on the shoulders of packets hopping a lot between regions, but it turns out, it was just db requests maxing past the configured MTU value, silently dropping
Now that BOTH the wireguard and flannel MTU values are set properly, everything is so damn snappy
This feels like new skin
#homelab #selfhosted #selfhosting #wireguard #mtu #vpn #mesh #longhorn #immich #flannel #devops #linux #opensource #networking
-
So it appears like, for the last ~months, my MTU configuration was REALLY wrong
Hinted by the immich longhorn replica not rebuilding, but I also didn't know, the extreme slowness of any service using a db cluster where the master node wasn't in the same region
I had put the slowness on the shoulders of packets hopping a lot between regions, but it turns out, it was just db requests maxing past the configured MTU value, silently dropping
Now that BOTH the wireguard and flannel MTU values are set properly, everything is so damn snappy
This feels like new skin
#homelab #selfhosted #selfhosting #wireguard #mtu #vpn #mesh #longhorn #immich #flannel #devops #linux #opensource #networking
-
So it appears like, for the last ~months, my MTU configuration was REALLY wrong
Hinted by the immich longhorn replica not rebuilding, but I also didn't know, the extreme slowness of any service using a db cluster where the master node wasn't in the same region
I had put the slowness on the shoulders of packets hopping a lot between regions, but it turns out, it was just db requests maxing past the configured MTU value, silently dropping
Now that BOTH the wireguard and flannel MTU values are set properly, everything is so damn snappy
This feels like new skin
#homelab #selfhosted #selfhosting #wireguard #mtu #vpn #mesh #longhorn #immich #flannel #devops #linux #opensource #networking
-
So it appears like, for the last ~months, my MTU configuration was REALLY wrong
Hinted by the immich longhorn replica not rebuilding, but I also didn't know, the extreme slowness of any service using a db cluster where the master node wasn't in the same region
I had put the slowness on the shoulders of packets hopping a lot between regions, but it turns out, it was just db requests maxing past the configured MTU value, silently dropping
Now that BOTH the wireguard and flannel MTU values are set properly, everything is so damn snappy
This feels like new skin
#homelab #selfhosted #selfhosting #wireguard #mtu #vpn #mesh #longhorn #immich #flannel #devops #linux #opensource #networking
-
For the last ~6 months, my immich Longhorn PVC wouldn't rebuild replicas across regions, and timeout instead
Today, I figured I had misplaced my MTU configuration for the Wireguard network under k3s...
So some packets were getting dropped silently...
Woops
#kubernetes #k3s #longhorn #network #networking #wireguard #wg #mesh #homelab #selfhosted #selfhosting #mtu
-
For the last ~6 months, my immich Longhorn PVC wouldn't rebuild replicas across regions, and timeout instead
Today, I figured I had misplaced my MTU configuration for the Wireguard network under k3s...
So some packets were getting dropped silently...
Woops
#kubernetes #k3s #longhorn #network #networking #wireguard #wg #mesh #homelab #selfhosted #selfhosting #mtu
