Request #3997
opennebula linux packages repository
Status: | Closed | Start date: | 09/23/2015 | |
---|---|---|---|---|
Priority: | Low | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Pull request: |
Description
Hello! Thanks a lot for super-awesome product.
One thing still better tbd.
http://downloads.opennebula.org/repo/ splits releases to folders, making upgrade a pain.
Can you please devide all stuff to stable/unstable ? Making separate folder for each new release is a mess.
Thanks a lot in advance!
History
#1 Updated by Daniel Dehennin almost 6 years ago
emik0 emik0 wrote:
Hello,
http://downloads.opennebula.org/repo/ splits releases to folders, making upgrade a pain.
Can you please devide all stuff to stable/unstable ? Making separate folder for each new release is a mess.
I disagree.
You ask what we had before, a single repository per distribution (like http://downloads.opennebula.org/repo/Debian/7/)
I ask to split the repositories to avoid automatic upgrades since ONE requires a manual step, the upgrade of the database.
Your request introduce a second problem: it takes time to validate a new version, we are using the API to automatically generate things and a new version requires adaptation to our infrastructure.
During the test of the new version, we need to be able to deploy new servers with a previous one.
As a solution to your request, your can achieve modify your repository sources simply by running sed
with pssh or dish.
Your can manager your sources with any configuration management system (SaltStack, Puppet, ansible, ...), but this requires a little bit more work.
Regards.
#2 Updated by emik0 emik0 almost 6 years ago
Thanks for the answer, probably you're right and automation via ansible/puppet is a proper way to go. After hearing a reason behind repo change, i close ticket.
Thanks again!