Mageia in cloud professionnal environment
Posted: Apr 14th, '14, 15:08Hello,
I'm starting to think about using mageia to perform a Proof of Concept in my company about upgrading our server automaticly.
We are currently using redhat and manual updates, which doesn't works well.
We have different objectives :
- we must be able to install the distribution on cloud env, openwatt and vcloud. It means also to be able to use the tools from the administration planel(vmtools for vcloud solution)
- we would need to make a copy of the repository everyday, or to access to such snapshots to be able to update our server depending on different decision. Some project would love to be updated with 0 day security update, while other would prefer a 1 or 3 month latency to prevent any disagreement or regression.
- A good way to priorize the update in our fleet would be welcome.
Do you have any idea on how and if we can do that easily with mageia ?
Another question would be also, can we keep old version of software. I'm thinking of PHP for example, some project want to upgrade from 5.3 to 5.4, and then to 5.5, but other would prefer to receive only the security update from 5.3. Do we have this granularity in mageia ? I tried to install 5.3 on my personnal laptop, but the package was unfound. I know it exist for some software, but what is the general rules about that.
Best regards,
Pierre
I'm starting to think about using mageia to perform a Proof of Concept in my company about upgrading our server automaticly.
We are currently using redhat and manual updates, which doesn't works well.
We have different objectives :
- we must be able to install the distribution on cloud env, openwatt and vcloud. It means also to be able to use the tools from the administration planel(vmtools for vcloud solution)
- we would need to make a copy of the repository everyday, or to access to such snapshots to be able to update our server depending on different decision. Some project would love to be updated with 0 day security update, while other would prefer a 1 or 3 month latency to prevent any disagreement or regression.
- A good way to priorize the update in our fleet would be welcome.
Do you have any idea on how and if we can do that easily with mageia ?
Another question would be also, can we keep old version of software. I'm thinking of PHP for example, some project want to upgrade from 5.3 to 5.4, and then to 5.5, but other would prefer to receive only the security update from 5.3. Do we have this granularity in mageia ? I tried to install 5.3 on my personnal laptop, but the package was unfound. I know it exist for some software, but what is the general rules about that.
Best regards,
Pierre