-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintainer for vyos appliance wanted #816
Comments
Could something like these simple build steps https://docs.vyos.io/en/latest/contributing/build-vyos.html#build-iso |
Well I followed the basic instructions for building a new iso and it worked as expected. The same 6 bash commands could easily be used to create the .iso for VyOS v1.2, v1.3, or v1.4 |
I have some reservations about providing my own images, but that shouldn't stop you.
|
This is totally irrelevant. GNS3/SolarWinds doesn't offer "Support" for any of the Appliances provided by this registry, This is not a Hill I'm willing to die on, I was just offering an option to get an updated VyOS |
Just noticed, that the access to the legacy releases has changed (again). Now you have to open https://vyos.net/get/ and fill out a form to get the links to the old releases. That is an absolutely reasonable way to handle that. But for me the vyos project is changing the download procedure too often, to keep up with them. Furthermore I have no access to the current release 1.3.x, therefore the releases in the appliance are getting old. In their blog post https://blog.vyos.io/community-contributors-userbase-and-lts-builds they tell us, why they don't accept distributing self made images with the name "vyos". Mainly they fear, that non-working images will have a negative impact on their brand. While I can fully understand it, that means that there is no way getting the vyos images except paying a lot of money. So for these reasons I think, that the vyos appliance has to go. As no other maintainer has shown up, I will create a PR removing vyos. |
I did it and they only give access to the legacy 1.2.9-S1 version :(
Let me try if we can get a subscription as a non-profit organization before we decide removing VyOS. |
Even then, we only get the information to update the appliance, but not the right to redistribute the images. As the images are quite costly, almost all users won't have access to the images and therefore won't be able to use the appliance. So the vyos appliance will be of very limited use. |
I just tried it. They give a long URL, that redirects to another long URL, that redirects to But I have no idea how long the vyos folks will keep this scheme. |
It's very simple to build the 1.3.3 ISO using docker. |
I have contacted the VyOS team and they offered us a partnership, part of it is they would maintain the VyOS appliance on the GNS3 marketplace. Hopefully this should be finalized soon. |
@grossmj the VyOS project has a very good documentation on how to build the ISO: I can publish my basic and simple scripts that builds VyOS regularilly. |
@elico I started using the rolling version since it's stable enough for general usage. |
The VyOS appliance was recently updated by the VyOS Inc.: #911 |
As I have no longer access to the vyos LTS versions, I can no longer update the vyos appliance. It already shows, as the latest version 1.3.3 is missing.
For keeping the vyos appliance up-to-date someone with access to the LTS versions is needed.
The text was updated successfully, but these errors were encountered: