Re: [openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

2016-02-01 Thread Armando M.
On 1 February 2016 at 16:59, Carl Baldwin wrote: > I almost missed this because [Neutron] was missing from the subject. > I'm replying now to add it in case someone else missed it. > > Ah...so there are people who indeed read these emails! Thanks for spotting this, I totally

Re: [openstack-dev] [oslo][all] Announcing our new Olso Project

2016-02-01 Thread Davanum Srinivas
yay Ronald :) On Mon, Feb 1, 2016 at 11:50 AM, Ronald Bradford wrote: > The Olso team is proud to announce the release of Oslo Bingo. In Oslo > we like to spice up our release notes using meaningful random > adjectives [1]. > > Each month the Oslo team will select an

[openstack-dev] [Fuel][QA] added fuel-devops branch 'release/2.9'

2016-02-01 Thread Dennis Dmitriev
Hi all, New branch 'release/2.9' was added to the repository 'fuel-devops' last week. This branch was created to keep supporting 2.9.x code while fuel-devops 3.0.0 will be merged to the 'master' branch. Please create all fixes for fuel-devops v2.9.x directly into 'release/2.9' branch instead of

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-02-01 Thread Vitaly Kramskikh
Folks, That's true, Nailgun is still using Role entity - in DB, API, plugins can provide new roles, etc., and it's not going away, at least in 9.0. I'm fine with proposed set of role groups, except the "controller" group. We don't have anything else but "controller" role in this group in the

Re: [openstack-dev] [puppet] Midcycle Sprint Summary

2016-02-01 Thread Cody Herriges
Emilien Macchi wrote: > Last week, we had our midcycle sprint. > Our group did a great job and here is a summary of what we worked on: > My attention at the office was stolen quite a few times by finishing up work for our production cloud deployment but I worked on the pupept-cinder Mitaka

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

2016-02-01 Thread Roman Prykhodchenko
This is basically why I proposed to allow users to set per cluster priority for every enabled plugin. That would allow users to select results they need. Putting too many logic into checks whether two plugins are incompatible is error-prone and won’t stop anyone from shooting their feet. > 29

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

2016-02-01 Thread Thierry Carrez
Fausto Marzi wrote: [...] That said, what we are trying to do, with Sam (that is showing an open attitude and constructive approach), is to understand if the solution make sense itself, if we can work together as a Team and if it make sense to include it in Freezer. If not, it is crystal clear,

<    1   2