We always run through the whole internal testing process, so those packages are quite stable.
pve-no-subscription =~ pvetest
I use pvetest a lots and it's stable.
I understand the new update policy.
Hope PVE be better.
We always run through the whole internal testing process, so those packages are quite stable.
We always run through the whole internal testing process, so those packages are quite stable.
sorry, but oVirt is another half past dead project (my personal opinion). You should start from getting all these proxmox stuff together by yourself. It is not that hard, when you know what to do. The hardest part will be the new web-interface
But calm down, it was just a big misunderstanding. Seems we are fine to run our current and maybe future projects with no-subscription repository. Just check the forum for some new light about new repos (just added).
Hi Guys,
just read this
http://forum.proxmox.com/threads/15742-Details-about-the-new-pve-no-subscripton-repository
old repos = new repos
pvetest = don't exist anymore
stable = pve-no-subscription
/ = pve-enterprise (more tested than old stable repos)
So that's change nothing about quality, just improve quality for subscribers users with more tested packages.
Yes, it does change something, it's exactly what has been said in this thread. They're making the default repo the test repo and the "subscription" repo the real stable repo. That means everyone without a subscription will just be testing package so they can be added to the subscription repo. Basically, they've just changed the names of the repositories and they're telling us that "stable no subscription" isn't actually "pvetest".
I'm all agree.I'm not interested in using anything from Proxmox VE in the new project. I don't want to help these people who've taken open source code to put it behind a paywall. Paying for tech support is one thing, paying for binaries and to have a nag screen removed is another.
Again, this is not true.
old pvetest was really a test, with packages pulled regulary from git repo with some little little tests, more for developpers than final users.
the new pve-no-subscription package will be a lot more tested.
The only difference is the nag screen at logon on gui.
(But maybe keeping the old pvetest could be better for understanding. I don't known if proxmox team have time to manage 3 differents repos)
The "only difference" is that you're basically doing the testing for the people who are paying for a "subscription". That means everyone who doesn't have a subscription is far more likely to run into bugs and new things which can break features than those people who are paying for a subscription. You're also more likely to have some kind of mysterious crash or run into one of those 100% CPU usage bugs.
Ok, so I'll take ovirt as example to compare
With ovirt, you don't have a test version, so ovirt stable release are tested internally by ovirt devs.
So ovirt stable release = proxmox pve-no-subscription repo
Now, redhat RHEV is the entreprise commercial version of ovirt, with support and licenses
So RHEV users benefinit from users of ovirt.
rhev = proxmox pve-enterprise repo
Than doesn't mean than ovirt is bugged right ?
same thing for fedora/rhel
The "only difference" is that you're basically doing the testing for the people who are paying for a "subscription". That means everyone who doesn't have a subscription is far more likely to run into bugs and new things which can break features than those people who are paying for a subscription. You're also more likely to have some kind of mysterious crash or run into one of those 100% CPU usage bugs.
If you did not pre-tested in the test running as a product, you tend to look for an alternative solution.
Hi everyone!
We're a non-profit organization, and is affordable is not an annual release of thousands of euro a stable release. No more thousands of euros a penny is affordable. But I do not really like to just update my version of the test systems. But is it possible that just the name scares me to "test version" and in fact, these packages have been somewhat tested in advance? If this is you propose to run as a community edition, it's really scary to the test name. If you did not pre-tested in the test running as a product, you tend to look for an alternative solution.
sorry my bad english