BSDFan

[gyptazy @gyptazy]

#ProxLB v2.3.0 for your #Proxmox VE clusters is out now!

Just released v2.3.0 of ProxLB which squashes some smaller bugs and adds smaller features. Like always, you can simply upgrade to the newer version by the usual ways.

[BSDFan @BSDFanFBSD]

He’s adding the next awesome things for a better Proxmox usage. Looking for Microsegmentation for years now

[gyptazy @gyptazy]

#Microsegmentation with East-West traffic management in #Proxmox?

Today, I had some further chats with customers and microsegmentation always comes up again when switching to Proxmox. While North-South traffic management isn't a big deal, East-West traffic management can be a bit more complicated.

In the past, I already made exactly for this reason #ProxWall (https://t.co/LvHDXKR1CM) which adds the major requirements of such solutions. But ProxWall is once again another dedicated tool and it might make more sense to integrate this into #PegaProx.

This approach adds east-west traffic management for l3 traffic into the centralized management interface of PegaProx. While you can already utilize this in Proxmox, it can be challenging to understand the ways of SDN, VNETs and Firewalls, including the default policies of forward traffic and rule management. This gets easier this way. However, unlike ProxWall this is not yet for L2 traffic...

Just sharing a first draft...

[gyptazy @gyptazy]

#Microsegmentation with East-West traffic management in #Proxmox?

Today, I had some further chats with customers and microsegmentation always comes up again when switching to Proxmox. While North-South traffic management isn't a big deal, East-West traffic management can be a bit more complicated.

In the past, I already made exactly for this reason #ProxWall (https://t.co/LvHDXKR1CM) which adds the major requirements of such solutions. But ProxWall is once again another dedicated tool and it might make more sense to integrate this into #PegaProx.

This approach adds east-west traffic management for l3 traffic into the centralized management interface of PegaProx. While you can already utilize this in Proxmox, it can be challenging to understand the ways of SDN, VNETs and Firewalls, including the default policies of forward traffic and rule management. This gets easier this way. However, unlike ProxWall this is not yet for L2 traffic...

Just sharing a first draft...

[BSDFan @BSDFanFBSD]

@gyptazy Sylve wäre vielleicht auch cool gewesen. Vielleicht ja auch der EuroBSDCon 😬

[gyptazy @gyptazy]

Quick reminder: Tomorrow you can listen to my talk about #PegaProx for #Proxmox at the #FrOSCon conference. It'll be at 10 AM in room HS8.

More: https://t.co/yR7Mv7fauY

[BSDFan @BSDFanFBSD]

@apparentorder @gyptazy The last time I did was when I was 15. This was when I had AMD k6… lol

[BSDFan @BSDFanFBSD]

@gyptazy When you’re doing this for Boxy, it’s ok I guess 😏🙃

[BSDFan @BSDFanFBSD]

@BoxyBSD @gyptazy It’s for Boxy? Then it’s fine 🙃

[gyptazy @gyptazy]

The last night I spent time into adding #ARM64 support for #PegaProx!

As #Proxmox now also fully supports arm64, PegaProx should do the same and here we go... The last night I spent some time into re-creating the dependency packages for arm64, adjusting the pipeline for cross-builds and testing. It's not yet merged, as I still need to adjust the dependency package pipelines to push into the repository, as the current pipeline simply takes the statically crafted packages from the CDN.

If someone is already interested into testing PegaProx on arm64, you might give the following things a try. Please report any issues to the issue tracker at Github.

Links:
PR: https://t.co/EHYNJl3hP0 (note @AustriaYt cherry-picked and fast-forwarded it directly)
Dev-Build Artifacts: https://t.co/vDh0HQhums
PegaProx ARM64 LXC: https://t.co/HV9TOiHX7Q
PegaProx ARM64 VM: https://t.co/HV9TOiHX7Q

[gyptazy @gyptazy]

I am currently working on a new storage integration of #NetApp for #PegaProx where it gets #Ontap storage snapshots with #Proxmox VE for faster snapshots across NFS, iSCSI, Fibre Channel and NVMe over Fabrics.

https://t.co/cmr5l8RJAf

[BSDFan @BSDFanFBSD]

@gyptazy Thanks for your modules

[BSDFan @BSDFanFBSD]

@gyptazy Sylve is really cool

[BSDFan @BSDFanFBSD]

@SuperbPhoenix @gyptazy Does it? Go ahead!

[BSDFan @BSDFanFBSD]

@Tigersharke @gyptazy Indeed, but he also wrote module for this part

[BSDFan @BSDFanFBSD]

Works even on Apple Mac M1!!!!

[gyptazy @gyptazy]

#Proxmox VE finally supports #ARM64 hardware architecture, now!

It was a long journey and several ones complained about a missing ARM64 hardware support for the native hypervisor.

https://t.co/QOsTU4cejQ

[gyptazy @gyptazy]

@minWi @BoxyBSD It’s currently tested by some people from the Discord channel before pushing upstream, but you can already find it right here: https://t.co/mzq12vc5iF

[BSDFan @BSDFanFBSD]

RaspberryPI users will be happy but who else???

[gyptazy @gyptazy]

#Proxmox VE finally supports #ARM64 hardware architecture, now!

It was a long journey and several ones complained about a missing ARM64 hardware support for the native hypervisor.

https://t.co/QOsTU4cejQ

[BSDFan @BSDFanFBSD]

@gyptazy Nice!

[gyptazy @gyptazy]

#Proxmox 9 running on #ARM64 / #aarch64

[gyptazy @gyptazy]

#Proxmox VE finally supports #ARM64 hardware architecture, now!

It was a long journey and several ones complained about a missing ARM64 hardware support for the native hypervisor.

https://t.co/QOsTU4cejQ