VyOS development news in August and September
Most importantly: all but one blockers for the 1.2.0 release candidate are now resolved. Quite obviously, for the release candidate, we want all features that w...
Category: VyOS Platform Blog | development (2)
VyOS 1.2.0 development news in July
Despite the slow news season and the RAID incident that luckily slowed us down only for a couple of days, I think we've made good progress in July. First, Kim H...
On "run reset vrrp master"
I've just exorcised a ghost of the old VRRP CLI implementation — the "reset vrrp master" command. I thought it would go away with the vyatta-vrrp package, but i...
New VRRP CLI is here (with IPv6 support)
Ever since I started with Vyatta, I've had a problem with commands for features unrelated to interfaces being defined inside interfaces. I'm sure the person who...
Making first boot scripts just got easier (but building vyos-1x got a bit harder)
As you probably know already, we are working on integrating cloud-init into VyOS, which will allow us to support multiple cloud platforms, and get rid of the cu...
Building VyOS images with custom packages just got simpler
While the new build scripts first introduced when we migrated the development branch to jessie made things much simpler for developers and for people who just w...
Writing migration scripts (and manipulating VyOS config files outside VyOS) just got easier
Long story short VyOS 1.2.0-rolling (starting with the next nightly build) includes a library for parsing and manipulating config files without loading them int...
Things the new style configuration mode definitions intentionally do not support
I've made three important changes to the design of the configuration command definitions, and later I realized that I never wrote down a complete explanation of...
VyOS 1.2.0 status update
While VyOS 1.2.0 nightly builds have been fairly usable for a while already, there are still some things to be done because we can make a named release candidat...
Naming of the nightly builds
Historically, we used to use "999.$timestamp" version numbers for development builds, including nightly builds. In our build scripts termninology, a development...
