Dmitry, Aleksandra,
thank you for help and support!
Regards,
Igor Marnat
On Fri, Mar 4, 2016 at 1:20 AM, Aleksandra Fedorova
wrote:
> As we agreed, we have switched ISO builds to latest CentOS 7.2 snapshots.
>
> You can see now that each ISO build (see for ex. [1]) produces several
> *_id.txt a
As we agreed, we have switched ISO builds to latest CentOS 7.2 snapshots.
You can see now that each ISO build (see for ex. [1]) produces several
*_id.txt artifacts.
Note that centos_mirror_id.txt points to CentOS snapshot at
http://mirror.fuel-infra.org/pkgs/
BVT test is stable, see [2], and nigh
Thanks for the detailed explanation, very helpful!
Considering that this change is atomic and easily revertable, lets
proceed with the change, the sooner we do that the more time we'll have
to confirm that there is no impact and revert if necessary.
--
Dmitry Borodaenko
On Thu, Mar 03, 2016 at
Hi,
let me add some details about the change:
1) There are two repositories used to build Fuel ISO: base OS
repository [1], and mos repository [2], where we put Fuel dependencies
and packages we rebuild due to certain version requirements.
The CentOS 7.2 feature is related to the upstream repo o
It is not just about BVT. I'd suggest to monitor situation overall,
including failures of system tests [1]. If we see regressions there, or
some test cases will start flapping (what is even worse), then we'd have to
revert back to CentOS 7.1.
[1] https://github.com/openstack/fuel-qa
On Wed, Mar 2
I agree with Mike's concerns, and propose to make these limitations (4
weeks before FF for OS upgrades, 2 weeks for upgrades of key
dependencies -- RabbitMQ, MCollective, Puppet, MySQL, PostgreSQL,
anything else?) official for 10.0/Newton.
For 9.0/Mitaka, it is too late to impose them, so we just
Formally, we can merge it today. Historically, every update of OS caused us
instability for some time: from days to a couple of month.
Taking this into account and number of other exceptions requested, overall
stability of code, my opinion would be to postpone this to 10.0.
Also, I'd suggest to ch
Igor,
couple of points from my side.
CentOS 7.2 will be getting updates for several more months, and we have
snapshots and all the mechanics in place to switch to the next version when
needed.
Speaking of getting this update into 9.0, we actually don't need FFE, we
can merge remaining staff today
Igor,
Your statement about updates for 7.2 isn't correct - it will receive
updates, because it's the latest release ATM. There is *no* pinning inside
ISO, and the only place where it was 8.0 were docker containers just
because we had to workaround some issues. But there are no docker
containers i
Dmitry, Igor,
> Very important thing is that CentOS 7.1 which master node is based now
> don't get updates any longer.
If you are using "fixed" release you must be ready that you won't get
any updates. So with CentOS 7.2 the problem still the same.
However, let's wait for Fuel PTL decision. I on
Igor,
please note that this is pretty much not like update of master node which
we had in 8.0. This is minor _update_ of CentOS from 7.1 to 7.2 which team
tested for more than 2 months already.
We don't expect it to require any additional efforts from core or qa team.
Very important thing is that
Hi Igor,
Postponing this till Fuel 10 means we have to elaborate a plan to do such
upgrade for Fuel 9 after the release - the underlying system will not get
updated on it's own, and the security issues will not close themselves. The
problem here is that such upgrade of deployed master node require
Hey Dmitry,
No offence, but I rather against that exception. We have too many
things to do in Mitaka, and moving to CentOS 7.2 means
* extra effort from core team
* extra effort from qa team
Moreover, it might block development by introducing unpredictable
regressions. Remember 8.0? So I think i
I'd like to ask for a feature freeze exception for switching to CentOS-7.2
feature [0].
CentOS-7.2 ISO's have been tested periodically since the beginning of the
year, and all major issues were addressed / fixed at the moment. During the
last weekend I've made 70 BVT runs to verify that the solut
14 matches
Mail list logo
