restive fog
https://4.nabox.org/downloads/
If you guys feel adventurous, you can test today the future of NAbox 😄
v4 is the path forward and no features will be delivered in 3, as far as I know, v4 has feature parity with 3 at this point (and some more)
Migration from 3 to 4 is available if you installed a recent version of 3.5.2 (yes, there has been a couple of iteration for that version number)
spare wyvern
awesome.
Will go through the process of installing a new deployment this week and let you know how everything goes
icy pollen
Will try this!!
zinc sedge
Hi @restive fog which port is needed for the migration? Since we use microsegmentation this would help a lot
restive fog
Https only
low prairie
I wanted to test this out. We have nabox 3.5.2 deployed. When I ssh to the nabox VM, the "migrate" command is not found. From the root, running a find I only get:
nabox:/# find . -name "migrate"
./sys/kernel/debug/tracing/events/migrate
Any tips on this? Thanks.
restive fog
You need a recent 3.5.2, when did you install it ?
restive fog
In case you need it there is also the manual option : https://4.nabox.org/faq/#migrating-from-older-versions
zinc sedge
Hi @restive fog just out of curiosity, can you give some insight about the reason from changing alpin linux to FLatcar and from Prometheus to VictoriaMetrics? Since we heavily use Prometheus and some want to use Cortex it would be interesting 🙂
restive fog
Alpine became impossible to maintain, every package based distribution on the long run is difficult to keep the package dependencies consistent as lots of packages are split, renamed, etc. Flatcar on the other end is a single block to update, and atomic pieces of filesystems for addons like nabox.
Regarding Victoria metrics the main driver was the long term retention that is not recommended even by Prometheus. Victoria metrics is more forgiving and has better management for long term retention, plus if you wanted to purchase a license you could even prune metrics to keep less samples for older data a little bit like graphite. Also VM takes much less space on disk
low prairie
You need a recent 3.5.2, when did you install it ?
I'd only upgraded to 3.5.2 a couple of days earlier. I'll check out the manual option. Thanks.
zinc sedge
Will the custom harvest files also be migrated or only the data + clusters?
low prairie
I found my issue. I was running NAbox 3.5.2 (2024-03-27). I downloaded the 3.5.2 update again and applied, and its now 3.5.2 (2024-04-02), but now has the migrate command. Seems I upgraded to 3.5.2 just before the re-release with the migrate utility.
restive fog
Will the custom harvest files also be migrated or only the data + clusters?
No customization will be migrated. And no way to customize easily yet, will be part of b2. So only data + systems
restive fog
I found my issue. I was running NAbox 3.5.2 (2024-03-27). I downloaded the 3.5.2...
Yeah sorry about that it has been a bit messy. I’m considering moving migrate tool to nabox 4 and have a script to execute on nabox 3 that fetches and install migrate