[openstack-dev] [kolla][osic] Ubuntu scale testing completed - now need CentOS deployed

Britt, Paul, and Michal, We are in need of centos deployed on the osic cluster (but not the deployment node). I'm not sure if we have time to get through all of the scenarios we have but I'd like to have data on centos as well. When you wake up, if you could sort out getting centos deployed

Re: [openstack-dev] [heat][yaql] Deep merge map of lists?

On Sun, Aug 28, 2016 at 11:58 PM, Steven Hardy wrote: > Hi all, > > I have a need to merge a list of maps of lists: > > heat_template_version: 2016-10-14 > > outputs: > debug: > value: > yaql: > # dict(vms=>dict($.vms.select([$.name, $]))) >

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Hello, Bin, Understand your expectation. In Tricircle big-tent application: https://review.openstack.org/#/c/338796/, a proposal was also given to add plugin mechnism in Nova/Cinder API layer, just like Neutron support plugin mechanism in API layer, that boosts innovation for different backend

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

Thanks for replying. See my comments inline. On Sun, Aug 28, 2016 at 8:02 PM Afek, Ifat (Nokia - IL) wrote: > Hi Yujun, > > Regarding the validation – I agree that we should implement it in another > way, but as a first stage I think you can just remove it. > OK > If you

Re: [openstack-dev] [kolla][oisc] scenario #8 running - need help deploying centos next

Scenario #8 was running about 12 hours (mitaka rally and tempest testing) and was only half way done. Inspection of the control machines showed out of disk space errors on the control nodes (which only have a 50gb total partition for where /var/lib/docker was stored). Elasticsearch produces

[openstack-dev] [heat][yaql] Deep merge map of lists?

Hi all, I have a need to merge a list of maps of lists: heat_template_version: 2016-10-14 outputs: debug: value: yaql: # dict(vms=>dict($.vms.select([$.name, $]))) expression: dict($.data.l.select([$.keys().toList()[0], $.values().toList()[0]])) data:

Re: [openstack-dev] [OpenStack-docs] [cinder] [api] [doc] API status report

On Sat, Aug 27, 2016 at 07:46:48PM +0200, Andreas Jaeger wrote: > On 08/26/2016 11:33 PM, Anne Gentle wrote: > > Hi cinder block storage peeps: > > > > I haven't heard from you on your comfort level with publishing so I went > > ahead and made the publishing job myself with this review: > > > >

[openstack-dev] [kolla][ironic][bifrost][osic] future of bifrost & Ironic for Kolla

Hey Stackers & Sean :), I just wanted to provide a quick update on where we think Kolla will be when ironic and bare metal config are fully fleshed out (landing in Newton). 3 controller, 20 storage, 100 compute with ceph+ovs+cinder+enable_central_logging on OSIC 130 node cluster Currently

[openstack-dev] [kolla] NOTICE: Deadline of 31st for milestone #3 - PLEASE UPDATE BLUEPRINT STATUS

Please take heed of the subject line. It would be immensely helpful if people working on the 35 blueprints would get them into he correct state (good progress or NEEDS REVIEW) so we can best select which features land in Newton. Ping any of the cores on #openstack-kolla if you don’t have

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] relationship_type in static_datasources

Hi Yujun, Regarding the validation – I agree that we should implement it in another way, but as a first stage I think you can just remove it. If you have some thoughts regarding the way to implement it, we will be happy to hear them. We thought about a yaml file per datasource, but didn’t

Re: [openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey on irc)

This vote has passed unanimously prior to August 30th, therefore, closing voting early. Welcome to the core reviewer team Dave! If you have any questions, feel free to ask any core reviewer or myself. I have made the necessary changes in gerrit. Regards -steve From: Steven Dake

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

Hi Yujun, In order for the static_physical to work for different datasources without the restrictions, you need to do the following changes: Go to the static_physical transformer: 1. Remove the methods: _register_relations_direction, _find_relation_direction_source. 2. Add to the