Open Stack

Good, thanks everyone for your feedback. As suggested, let's merge 
pb_num calculation as a bugfix (no exception needed). With regards to UI 
part, I do agree that it's just nice to have feature and I don't see the 
review with GUI part amongst of those nominated for exception. So - 
let's put it to the next release.

-- 
EugeneB

> Vitaly Kramskikh <mailto:vkramskikh at mirantis.com>
> 27 июля 2015 г., 13:57
> +1 to Stanislav's proposal.
>
>
>
>
> -- 
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> Stanislav Makar <mailto:smakar at mirantis.com>
> 27 июля 2015 г., 3:05
>
> Hello
> I went through LP-1464656 and I see that it covers two things:
> 1. Bad pg num calculation algorithm.
> 2. Add the possibility to set pg num via GUI.
>
> First is the most important and a BUG by itself, second is nice to 
> have feature and no more.
> Hence we should split it into a bug and a feature.
>
> As the main part is a bug it does not impact FF at all.
>
> My +1 to close bad pg num calculation algorithm as a bug and postpone 
> specifying pg_num via GUI to the next release.
>
> /All the best
> Stanislav Makar
>
> +1 for FFE
> Given how borken pg_num calculations are now, this is essential to the 
> ceph story and there is no point in testing ceph at scale with out it.
>
> The only work-around for not having this is to delete all of the pools 
> by hand after deployment and calculate the values by hand, and 
> re-create the pools by hand. The story from that alone makes it high 
> on the UX scale, which means we might as well fix it as a bug.
>
> The scope of impact is limited to only ceph, the testing plan needs 
> more detail, and we are still comming to turns with some of the data 
> format to process between nailgun calculating and puppet consuming.
>
> We would need about 1.2 week to get these landed.
>
> -- 
>
> --
>
> Andrew Woodward
>
> Mirantis
>
> Fuel Community Ambassador
>
> Ceph Community
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe 
> <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> Andrew Woodward <mailto:xarses at gmail.com>
> 25 июля 2015 г., 1:58
> +1 for FFE
> Given how borken pg_num calculations are now, this is essential to the 
> ceph story and there is no point in testing ceph at scale with out it.
>
> The only work-around for not having this is to delete all of the pools 
> by hand after deployment and calculate the values by hand, and 
> re-create the pools by hand. The story from that alone makes it high 
> on the UX scale, which means we might as well fix it as a bug.
>
> The scope of impact is limited to only ceph, the testing plan needs 
> more detail, and we are still comming to turns with some of the data 
> format to process between nailgun calculating and puppet consuming.
>
> We would need about 1.2 week to get these landed.
>
> -- 
>
> --
>
> Andrew Woodward
>
> Mirantis
>
> Fuel Community Ambassador
>
> Ceph Community
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> Konstantin Danilov <mailto:kdanilov at mirantis.com>
> 24 июля 2015 г., 13:46
> Team,
>
> I would like to request an exception from the Feature Freeze for [1]
> fix. It requires changes in
> fuel-web [2], fuel-library [3] and in UI. [2] and [3] are already
> tested, I'm fixing UT now.
> BP - [4]
>
> Code has backward-compatibility mode. I need one more week to finish 
> it. Also
> I'm asking someone to be an assigned code-reviewer for this ticket to 
> speed-up
> review process.
>
> Thanks
>
> [1] https://bugs.launchpad.net/fuel/+bug/1464656
> [2] https://review.openstack.org/#/c/204814
> [3] https://review.openstack.org/#/c/204811
> [4] https://review.openstack.org/#/c/203062
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150727/787878d8/attachment.html>