I think, Vladimir means, that we need to improve our scheduling of the CI
jobs over available CI resources. As I know, now we have a dedicated server
groups for separate tests and we cannot use free resources of other server
groups in case of overbalanced load.
On Thu, Jun 5, 2014 at 6:52 PM,
Hi, fuelers
We had a meeting today to discuss how we gonna meet all the requirements
for OpenStack patching (
https://blueprints.launchpad.net/fuel/+spec/patch-openstack) and FUEL
Upgrade blueprints.
These are the main points:
1. We need strict EOS and EOL rules to decide how many maintenance
On 5 June 2014 16:27, Vladimir Kuklin vkuk...@mirantis.com wrote:
1. We need strict EOS and EOL rules to decide how many maintenance
releases there will be for each series or our QA team and infrastructure
will not ever be available to digest it.
Agreed. Would it not be prudent to keep with
