[Fuel-dev] Which kernel should we use in CentOS?

2014-03-28 Thread Dmitry Pyzhov
Guys, we have two kernels: default 2.6.32 and kernel-lt 3.10.30. And we have three types of CentOS nodes: master node, bootstrap, target node. Right now master node has 2.6 kernel, bootstrap has 3.10 and target node has an option in settings with 2.6 kernel as default. There is a suggestion

Re: [Fuel-dev] 4.1.1 bugfixes ready for review/merge

2014-04-03 Thread Dmitry Pyzhov
Exactly. Do not change Change-ID. It is our last resort. Without it we have no reliable method to check in which branches we merged a patchset. On Thu, Apr 3, 2014 at 12:49 PM, Evgeniy L e...@mirantis.com wrote: Hi Dmitry, This patches are same but they have different Change-Id:

[Fuel-dev] Closing all bugs for 5.0.x master node

2014-08-18 Thread Dmitry Pyzhov
FYI. 5.0.1 is the last official release on 5.0.x series. All future bugfixes for master node will be released in 6.0 and 5.1.1 versions. I'm closing following bugs as Won't fix for 5.0.x series: [neutron] Network verification failed on Neutron Vlan with Vlan tagging

Re: [Fuel-dev] Closing all bugs for 5.0.x master node

2014-08-18 Thread Dmitry Pyzhov
is fixed in 5.1, so it doesn't make sense for 5.0.2. All issues in 5.0.2 are relevant to OpenStack envs only (and puppet manifests to patch older envs up to 5.0.2), but are irrelevant to Fuel Master node. On Mon, Aug 18, 2014 at 3:08 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote: FYI. 5.0.1

[Fuel-dev] Let's close fuel-dev mailing list

2014-10-09 Thread Dmitry Pyzhov
Guys, Not everyone is subscribed to our outdated fuel-dev mailing list. If someone write to it, he/she does not reach the all of the developers. What is worth, it is hard to notice. We have migrated to openstack-dev with '[Fuel]' tag. It was surprise for me that old mailing list is still in use:

Re: [Fuel-dev] [Fuel build system] Documentation

2014-10-09 Thread Dmitry Pyzhov
Irina, thanks a lot. I think deprecated options should not be added to the documentation. We should do it in future for changes in documentation. But now we should discuss them and simply remove from our build system. What is more important for our build docs, we should find and document general

Re: [Fuel-dev] [Fuel] Detailed Fuel release version definition

2014-10-20 Thread Dmitry Pyzhov
I'm agree with Dmitry. We can change version text. Use '2014.2-6.0-pre' in openstack.yaml and '6.0-pre' in PRODUCT_VERSION. Yep, we need to test it first. Also think about sorting on ui and other places where we can compare versions. On Mon, Oct 20, 2014 at 2:36 PM, Aleksandra Fedorova