Social network integration for VyOS 2.0

There are still many design decisions we have to make for the next generation VyOS.

No project can become successful these days if it lacks social network integration. For this reason we started working on it right away.

When you install VyOS, you will be prompted to link it to at least one supported social network, Facebook or Twitter. If you choose to use Facebook, you will be prompted to join the official VyOS group and join or create a group for your network.

One of the functions of social networks is to connect like-minded people and let them tell one another about their interests. For this reason we are adding "likes" to the command line interface. You will be able to like a particular feature and see who else likes it.

We will be using the number of likes to prioritize features. Features that get the most likes will get the most attention, so make sure to like the features you use.

Knowing who else likes features you use will also help you find people to share experience or ask for help.

vyos@vyos# like protocols ospf

vyos@vyos# run show likes protocols ospf
dmbaturin likes OSPF
syncer likes OSPF
jrandomhacker likes OSPF

The other important function is to let other people know what you are up to. VyOS 2.0 will automatically post information about new commits, image upgrades, and other events to Facebook and Twitter. You can also choose to send all log messages to your Twitter account. While there is no mechanism in place for this, in the future VyOS may be able to post screenshots of error messages to Instagram.

And, it's a while off, but maybe at some point you will be able to control your routers through posts in social network groups. We call this concept SDN (Socially Defined Networking). Stay tuned!

phabricator maintenance

Hi everyone,

phabricator migration to new VM is now complete, but it experiences performances problems because it's still re-importing all the repositories and, given there's a kernel fork there, it takes a long time. It's borderline usable now, but sometimes it fails to load its CSS on first attempt, and sometimes it just takes a long time to respond. Sorry for the inconvenience!

One repository import is complete, we'll need to do some more maintenance on the network at that site, but it's not going to take as long. Then this will hopefully be over and things will get back to normal.

Maintenance notification: is going down for a few hours at most. The original VM we deployed from a template had a disk too small for what we need, so we setup a VM with a bigger disk and LVM instead ordinary partition so we can expand it more or less online in the future.

But now we need to move the data to it, and for this we need to take the old machine offline. Sorry for the inconvenience.

Sentrium? What Sentrium?

You may start wondering what's that mysterios Sentrium S.L. that appears in VyOS-related material sometimes.

It's pretty easy. Sentrium S.L. is the company that Daniil Baturin (one of VyOS maintainers) and his friend, Yuriy Andamasov who goes by syncer (a long time Vyatta and then VyOS user), and his friend Santiago Blanquet Bru De Sala setup for their IT consulting endeavors, and then thought that it can act as "the company behind VyOS" in cases when being a company makes things easier.

The company is registered in Spain and was funded completely out of our pockets, with no investors involved. Our source of income at the moment is a few consulting agreements with various companies.

To address some concerns it may raise, here are things that Sentrium S.L. may do:

  • Appear in the vendor/subject field in appliance catalogs, SSL certficiates, conference registrations and the like.
  • Provide support and consulting services specifically for VyOS (we are still wondering how to organize in a way that allows other maintainers and experienced community members to participate in it if they choose to).
  • Hire people and purchase services for VyOS (e.g. graphics design)
  • Take over the world.

What Sentrium S.L. will never do:

  • Assume copyrights to existing VyOS source code
  • Require VyOS contributors to transfer their copyright
  • Make a proprietary or freemium versions of VyOS
  • Wipe out the hackers forum
  • Sell VyOS to a FibreChannel switch manufacturer

In other words, for VyOS and its development process, it changes nothing. If we come up with any ideas for commercial support offerings for VyOS, we will tell, and if you have any ideas how to make it community-friendly, tell us!

VyOS infrastructure updates: new blog and new bugtracker/collaboration platform

Infrastructure changes always give people a mixed feeling. Nothing is exactly "the old thing but better", some long standing issues get fixed while some perfectly useful features become unavailable. I'm not an exception, and what I'm doing now also gives me a mixed feeling, but probably it's time to do it.

In any case, here's what we are up to. If you have any questions, or you spot any problems with any of new things we are going to use, please tell us.


The new blog will be on Posthaven ( aka
The new development portal will be
We need your feedback about both.

Blog migration

We've been using tumblr for our dev blog since the beginning. Not so many people complained, but there definitely are problems.

  • Twitter and facebook relay truncates posts at the first line instead of just posting the title and the link. This is annoying, and they are not going to fix it apparently.
  • There are multiple formatting issues, some of them didn't exist when we started. Lossless image formats are always converted to JPEG, sometimes the original file is not even preserved. Preformatted text eats some symbols, especially "<" and ">". Reblogging strips the post off its original formatting, if it had any.
  • Its content policy is, uhm, a bit too liberal. Not a bad thing per se, but it occasionally gets it blocked in workplace networks.

I looked into a number of options, including other services, traditional blog engines, and static blog generators. Posthaven costs $5/month if you want to host a blog there, but so far it's free of said problems and generally looks decent. 

The domain will be switched to here. The old blog will stay accessible at as long as Tumblr is alive.

Bugtracker migration

What's even more important is that we are going to trade Bugzilla for Phabricator (

When we started the fork, the development process was modelled after the old process used by Vyatta, complete with the same tools. That process, and Bugzilla itself is obviously showing its age, and it's time to rethink it.

One of the greatest concerns is lack of integration with... anything, really. We still post links to commits by hand because there is no easy way to make it automatically update bugs with those links when someone references the bug number in commit message. The need to register an account and oldschool UI, things I normally don't care about myself, are also a deterrent for a large number of people. A number of people also find Bugzilla workflow itself confusing.

I've been looking for a bandwagon to jump on for a while, and Phabricator looks like the best option so far. What also looks appealing is that there were high profile cases of migrating to it from Bugzilla, including Wikimedia Foundation migrating a decade worth of content and workflow to it; Blender and GHC also use it now.

It's a lot more than just a bugtracker and includes applications for bug tracking, code review, questions and answers, a simple wiki, and more. There is OAuth support so people can register through Github, Google, or Facebook if they don't want a local account. Git integration works nicely, and the Q&A app can potentially replace the forum even.

Other maintainers at least don't hate it so far, but we are still to get any feedback from end users. Please go to , look around, and tell us what you think so we can reconfigure things to make it easier to use. There's also a question of migrating Bugzilla data to it. It's possible, we've been looking into Wikimedia's way of migrating the data, but I wonder if we really should migrate all data indiscriminately.

To address some immediate concerns, old Bugzilla and the forum will not be removed. They will stay in read only mode for the foreseeable future if we replace them.

We also do not plan to move the code to Phabricator yet. Unless Github becomes evil, primary repositories will stay there, and the ones in Phabricator will be mirrors.