Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Thanks Stan for the pointer. I removed the line that referred to the 'name' property and now my application is added to the environment without any errors. However, what I see in ui.yaml still doesn't look like YAML. I'm attaching samples again. Even for HOT packages the content is not YAML.

Re: [openstack-dev] how do we get the migration status details info from nova

I agree we should have both(notification/API). Watcher will consume notifications, not the API, API would be helpful for operator. The notification way should be addressed in separate BP. BR, YunTongJin 2015-11-26 22:37 GMT+08:00 少合冯 : > Agree. Why not both. and will

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

Sorry for wrong numbers. The bug-fix for issue with counters is merged. Correct numbers(latest result from rally's gate[1]): - total number of executed tests: 1689 - success: 1155 - skipped: 534 (neutron,heat,sahara,ceilometer are disabled. [2] should enable them) - failed: 0 [1] -

Re: [openstack-dev] [puppet] [release] Puppet OpenStack 7.0.0 Liberty (_independent)

Fantastic to hear, good work guys. On Thu, Nov 26, 2015, 3:01 PM David Moreau Simard wrote: > Awesome ! > > Congratulations to everyone involved in the release of the most > popular deloyment method [1] :) > The new acceptance and integration tests make this rock solid, too ! >

Re: [openstack-dev] [puppet] [release] Puppet OpenStack 7.0.0 Liberty (_independent)

Awesome ! Congratulations to everyone involved in the release of the most popular deloyment method [1] :) The new acceptance and integration tests make this rock solid, too ! [1]: http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up David Moreau Simard

Re: [openstack-dev] [magnum] Using docker container to run COE daemons

One of the benefit of running daemons in docker container is that the cluster can upgrade more easily. Take mesos as an example, if I can make mesos running in container, then when update mesos slave with some hot fixes, I can upgrade the mesos slave to a new version in an gray upgrade， i.e.

Re: [openstack-dev] [oslo] fake driver doesn't work with multi topics

Thanks Flavio. I'll report it in launchpad. best regard, Masahito On 2015/11/27 3:00, Flavio Percoco wrote: On 26/11/15 10:40 +0900, Masahito MUROI wrote: Hi oslo.message folks, We are trying to use oslo_message's fake driver [1] for our testing. However, the driver doesn't seem to work with

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

2015-11-27 15:40 GMT+09:00 Daniel Mellado : > I still do think that even if there are some issues addressed to the > feature, such as skipping tests in the gate, the feature itself it's still > good -we just won't use it for the gates- > Instead it'd be used as a

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

I still do think that even if there are some issues addressed to the feature, such as skipping tests in the gate, the feature itself it's still good -we just won't use it for the gates- Instead it'd be used as a wrapper for a user who would be interested on trying it against a real/reals clouds.

Re: [openstack-dev] [magnum]storage for docker-bootstrap

Hi Hongbin, The docker in master node stores data in /dev/mapper/atomicos-docker--data and metadata in /dev/mapper/atomicos-docker--meta. /dev/mapper/atomicos-docker--data and /dev/mapper/atomicos-docker--meta are logic volumes. The docker in minion node store data in the cinder volume, but

Re: [openstack-dev] [murano] Is it possible to use Murano RESTful API to create and deploy an application

Hi Tony, We have already implemented commands which allow user to configure and deploy environments via CLI. Please, take a look to this article: http://docs.openstack.org/developer/murano/draft/enduser-guide/deploying_using_cli.html On Thu, Nov 26, 2015 at 9:18 AM, WANG, Ming Hao (Tony T) <

Re: [openstack-dev] [nova]New Quota Subteam on Nova

Raildo Mascena wrote on 11/20/2015 05:13:18 PM: > From: Raildo Mascena > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 11/20/2015 05:15 PM > Subject: [openstack-dev] [nova]New Quota Subteam

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/25/2015 10:43 PM, Ben Nemec wrote: On 11/23/2015 06:50 AM, Dmitry Tantsur wrote: On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote: On 10 November 2015 at 15:08, Tzu-Mainn Chen

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

Doug Hellmann wrote: > Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500: >> >>> On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote: >>> >>> OK, reserving bugs for new contributors does reduce the number of >>> people contending for them, but it doesn't eliminate

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Hi, One thing i observed is there is no packets coming to the dpdk interface (data network). I have verified it with the tcpdump using mirror interface. and if i assign ip address and ping each other the data network bridges that is also not working. could this be a possible cause for the nova

Re: [openstack-dev] [murano] Is it possible to use Murano RESTful API to create and deploy an application

Hi Anastasia, Thanks for your information. “environment-apps-edit” can be used as “environment-apps-create”, I got it. ☺ Thanks, Tony From: Anastasia Kuznetsova [mailto:akuznets...@mirantis.com] Sent: Thursday, November 26, 2015 4:35 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] New [puppet] module for Magnum project

On 11/25/2015 05:08 PM, Ricardo Rocha wrote: > Hi. > > We've started implementing a similar module here, i just pushed it to: > https://github.com/cernops/puppet-magnum > > It already does a working magnum-api/conductor, and we'll add > configuration for additional conf options this week - to

Re: [openstack-dev] [Fuel] CentOS-7 Transition Plan

Hi all, Part of those change requests may be merged shortly (today). They are compatible with Centos6. List of change requests ready to merge (compatible with Centos6): Fuel-library - https://review.openstack.org/#/c/247066/ - https://review.openstack.org/#/c/248781/ -

[openstack-dev] [neutron][fwaas]

Hi, I am trying to fork vArmour FWaaS driver and didn't find how and when https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/agents/varmour/varmour_router.py#L276 function is called. I put pdb traces but starting neutron-l3-agent never fall in to a debug

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

I have submitted patch for DVR Grenade multinode job: https://review.openstack.org/#/c/250215 Without DVR upgrade - we won't be able to tell if L3 upgrade is working. What is left to be done, it is the DVR support in Grenade. DVR has the multinode job, but I do not see DVR in grenade - creation

[openstack-dev] how do we get the migration status details info from nova

Now, we are agree on getting more migration status details info are useful. But How do we get them? By REST API or Notification? IF by API, does the "time_elapsed" is needed? For there is a "created_at" field. But IMO, it is base on the time of the conductor server? The time_elapsed can get

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

Hello Kevin, I've added some pictures that illustrates how it works with HW switch and with VMs on devstack. On Wed, Nov 25, 2015 at 10:53 PM, Kevin Benton wrote: > This is cool. I didn't know you were working on an OVS driver for testing > in CI as well. :) > > Does this

Re: [openstack-dev] [stable] Post-release bump after 2014.2.4?

> I've confirmed that the juno side of kilo grenade is not blowing up [1], but > I'm not sure why it's not blowing up. Trying to figure that out. It would blow up if something were merged after 2014.2.4 tag which won't happen before version in setup.cfg is either bumped or removed so we're safe

Re: [openstack-dev] how do we get the migration status details info from nova

On 26/11/15 10:48, 少合冯 wrote: Now, we are agree on getting more migration status details info are useful. But How do we get them? By REST API or Notification? IF by API, does the "time_elapsed"is needed? For there is a "created_at" field. But IMO, it is base on the time ofthe conductor

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Am when you say dpdk interface do you mean dpdk physical interface is not reciving any packets or a vhost-user interface. Can you provide the output of ovs-vsctl show. And sudo /opt/stack/DPDK-v2.1.0/tools/dpdk_nic_bind.py –status You should see an output similar to this. Network devices using

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

On 11/26/2015 10:40 AM, Thierry Carrez wrote: Doug Hellmann wrote: Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500: On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote: OK, reserving bugs for new contributors does reduce the number of people contending

Re: [openstack-dev] Encouraging first-time contributors through bug tags/reviews

> On Nov 26, 2015, at 4:19 PM, Rossella Sblendido wrote: > > I'd like to help. Neutron could be one of the pilot project. I will mention > that in the next Neutron team meeting :) Thank you! If one, or more, projects pilot this concept... We could share the results at

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

Hi Sukhdev, I didn't have a change to be present on previous meeting due to personal reasons, but I will be on next meeting. It is important to keep CI testing as much possible closer to real Ironic use-case scenario. At the moment we don't have any test-case that covers ironic/neutron

[openstack-dev] [nova][ironic] do we really need websockify with numpy speedups?

Hi all, I was long puzzled why devstack is installing numpy. Being a fantastic package itself, it has the drawback of taking about 4 minutes to compile its C extensions when installing on our gates (e.g. [0]). I finally took time to research and here is what I've found: it is used only by

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

Hi Daniel, Thanks for pointing this up. 2015-11-25 1:40 GMT+09:00 Daniel Mellado : > Hi All, > > As you might already know, within Red Hat's tempest fork, we do have one > tempest configuration script which was built in the past by David Kranz [1] > and that's been

Re: [openstack-dev] [QA] Meeting Thursday November 26th at 9:00 UTC

Hi, On today QA meeting, the log bot seemed down. So I'd like to send a mail for summarizing the log and the situation instead: #action gmann will ask mtreinish and johnthetubaguy for reviewing the microversion test patches - We are discussing this already on IRC after the meeting and that

Re: [openstack-dev] [nova] How were we going to remove soft delete again?

On 24 November 2015 at 16:36, Matt Riedemann wrote: > I know in Vancouver we talked about no more soft delete and in Mitaka lxsli > decoupled the nova models from the SoftDeleteMixin [1]. > > From what I remember, the idea is to not add the deleted column to new >

Re: [openstack-dev] [nova] How were we going to remove soft delete again?

On 26 November 2015 at 12:10, John Garbutt wrote: > On 24 November 2015 at 16:36, Matt Riedemann > wrote: >> I know in Vancouver we talked about no more soft delete and in Mitaka lxsli >> decoupled the nova models from the SoftDeleteMixin [1].

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Hi Sean, its the dpdk physical interface. dpdk interface is correctly added to the bridge. please find the below ovs-stats. controller -- [stack@localhost devstack]$ sudo ovs-vsctl show c74e8e55-8f4e-4e49-9547-4319803a85f9 Bridge "br-ens5f1" Port "br-ens5f1"

Re: [openstack-dev] [openstack-announce] [release][stable][keystone][ironic] keystonemiddleware release 1.5.3 (kilo)

I suspect it could break ironic stable/kilo in the same way as 2.0.0 release. Still investigating, checking if https://review.openstack.org/#/c/250341/ will also fix it. Example of failing patch: https://review.openstack.org/#/c/248365/ On 11/23/2015 08:54 PM, d...@doughellmann.com wrote: We

[openstack-dev] TripleO client answers file.

We are proposing to have an "answers file" for the tripleoclient so that you don't have to have a ling line of openstack overcloud deploy --templates /home/stack/mytemplates --environment superduper.yaml --environment loadsofstuff.yaml --envirnoment custom.yaml But instead can just do

Re: [openstack-dev] [nova][ironic] do we really need websockify with numpy speedups?

Hi again, I've went on and created a proper pull request to websockify [0], comment there if you think we need it :) I also realized that there is another option, which is to include python-numpy to files/debs/ironic and files/debs/nova (strangely it is already present in rpms/ for nova, noVNC

Re: [openstack-dev] TripleO client answers file.

+1. That would be really helpful. What about passing other deployment parameters via answers.yaml ? For example, compute-flavor, control-flavor etc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

Hi! Boris P. and I tried to push a spec[1] for automation tempest config generator, but we did not succeed to merge it. Imo, qa-team doesn't want to have such tool:( >However, there is a big concern: >If the script contain a bug and creates the configuration which makes >most tests skipped, we

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Vahid, I see what is the problem. You are generating UI form that looks like this: Forms: - group0: fields: [] Application: name: $.group0.name ?: type: "io.murano.apps.generated.CsarHelloWorld" Version: 2.2 The problem in in "name: $.group0.name". Previously

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in the default environment, but via a "noop"

[openstack-dev] [telemetry] upcoming Mitaka-1 release

hi, just a quick note, i'll be tagging the Mitaka-1 release early next week for Ceilometer and Aodh. if you want to get something in for M-1, now is the time. please let us know so we can track it. Gnocchi will not have a release -- it will continue to be released independently as features

Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

Hello everyone, Yes, I am working on this now. We have some success already, but there is a lot of work to do. Of course, some things don't work ideally. For example, in [2] from the previous letter we have not 24 skipped tests, actually much more. So we have a bug somewhere :) Regards, Yaroslav

Re: [openstack-dev] [stable] Stable team PTL nominations are open

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Monday, November 23, 2015 5:11 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [stable] Stable team PTL nominations are open > > Hi everyone, > > We discussed setting up a standalone

Re: [openstack-dev] how do we get the migration status details info from nova

> -Original Message- > From: Paul Carlton [mailto:paul.carlt...@hpe.com] > Sent: November 26, 2015 12:11 > On 26/11/15 10:48, 少合冯 wrote: > > > Now, we are agree on getting more migration status details > info are useful. > > But How do we get them? > By REST API or

Re: [openstack-dev] TripleO client answers file.

On Thu, Nov 26, 2015 at 01:37:16PM +0100, Lennart Regebro wrote: > We are proposing to have an "answers file" for the tripleoclient so > that you don't have to have a ling line of > >openstack overcloud deploy --templates /home/stack/mytemplates > --environment superduper.yaml --environment

Re: [openstack-dev] [Ironic][Neutron] Testing of Ironic/Neutron integration on devstack

Hi All, Just want to notify that I've created tempest bug [0] to verify Ironic multitenancy and going to work on it. Please let me know if you have any comments/suggestions regarding the test scenario described there. [0] https://bugs.launchpad.net/tempest/+bug/1520230 Best regards, Yuriy

Re: [openstack-dev] TripleO client answers file.

On Thu, Nov 26, 2015 at 06:01:31PM +0500, Qasim Sarfraz wrote: >+1. That would be really helpful.  >What about passing other deployment parameters via answers.yaml ?  For >example, compute-flavor, control-flavor etc So, I think the main reason to avoid this, is that long term it

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Praveen, there are many error in your q-svc log. It says: InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use with host %(host)s', {'ip': u'10.81.1.150', 'host': u'localhost.localdomain'}).\n"] Did you maybe specify duplicated ips in your controllers and compute nodes neutron

Re: [openstack-dev] [nova][ironic] do we really need websockify with numpy speedups?

Hi Pavlo, Can we just use a wheel package for numpy instead? Thanks, Roman On Thu, Nov 26, 2015 at 3:00 PM, Pavlo Shchelokovskyy wrote: > Hi again, > > I've went on and created a proper pull request to websockify [0], comment > there if you think we need it :) > >

Re: [openstack-dev] TripleO client answers file.

On 11/26/2015 02:34 PM, Steven Hardy wrote: On Thu, Nov 26, 2015 at 01:37:16PM +0100, Lennart Regebro wrote: We are proposing to have an "answers file" for the tripleoclient so that you don't have to have a ling line of openstack overcloud deploy --templates /home/stack/mytemplates

Re: [openstack-dev] TripleO client answers file.

Thanks Steve. Makes sense to avoid passing deployment parameters with answer file interface Lennart proposed. On Thu, Nov 26, 2015 at 6:42 PM, Steven Hardy wrote: > On Thu, Nov 26, 2015 at 06:01:31PM +0500, Qasim Sarfraz wrote: > >+1. That would be really helpful. > >

[openstack-dev] [puppet] [release] Puppet OpenStack 7.0.0 Liberty (_independent)

Puppet OpenStack community is very proud to announce the release of 22 modules: puppet-aodh 7.0.0 puppet-ceilometer 7.0.0 puppet-cinder 7.0.0 puppet-designate 7.0.0 puppet-glance 7.0.0 puppet-gnocchi 7.0.0 puppet-heat 7.0.0 puppet-horizon 7.0.0 puppet-ironic 7.0.0 puppet-keystone 7.0.0

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On 26.11.2015 14:12, Jiří Stránský wrote: My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in

Re: [openstack-dev] [TripleO] RFC: profile matching

On 11/09/2015 03:51 PM, Dmitry Tantsur wrote: Hi folks! I spent some time thinking about bringing profile matching back in, so I'd like to get your comments on the following near-future plan. First, the scope of the problem. What we do is essentially kind of capability discovery. We'll help

Re: [openstack-dev] how do we get the migration status details info from nova

Useful information. Thank you Gibi. BR Shaohe Feng.. 2015-11-26 21:29 GMT+08:00 Balázs Gibizer : > > -Original Message- > > From: Paul Carlton [mailto:paul.carlt...@hpe.com] > > Sent: November 26, 2015 12:11 > > On 26/11/15 10:48, 少合冯 wrote: > > > > > >

Re: [openstack-dev] how do we get the migration status details info from nova

Agree. Why not both. and will use created_at to work out how long the migration has been running. Paul, thank you very much for the suggestion. BR. Shaohe Feng 2015-11-26 19:10 GMT+08:00 Paul Carlton : > On 26/11/15 10:48, 少合冯 wrote: > > Now, we are agree on getting

[openstack-dev] More and more circular build dependencies: what can we do to stop this?

Hi, As a package maintainer, I'm seeing more and more circular build-dependency. The latest of them is between oslotest and oslo.config in Mitaka. There's been some added between unittest2, linecache2 and traceback2 too, which are now really broadly used. The only way I can work around this

[openstack-dev] [Oslo][TaskFlow] Non-DAG Flows, Timers and External Events

Hello list, I've been busy investigating how to best introduce HA to Ironic Inspector and I got referred to TaskFlow. With Ironic Inspector, besides handling other issues, each Node being introspected undergoes couple of steps with side-effects. This can be described using a finite automaton[1].

Re: [openstack-dev] [openstack-announce] [release][stable][keystone][ironic] keystonemiddleware release 1.5.3 (kilo)

Here is the first pass at a fixture to handle the case that ceilometer is doing with the hacked-up memcache interface. This will be something supported by keystonemiddleware so it should not break randomly in the future: https://review.openstack.org/#/c/249794/ On Thu, Nov 26, 2015 at 7:27 AM,

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

Hi Julien, You'll find attached to this mail two dump files. gnocchi_resource.txt is an example of resource requests and responses from gnocchi. gnocchi_measure.txt an example of a timeframe request. Metric (vcpus) measure == Data stored by ceilometer with default

Re: [openstack-dev] [ironic] Releases and things

On 25 November 2015 at 18:02, Jim Rollenhagen wrote: > Hi all, > > We're approaching OpenStack's M-1 milestone, and as we have lots of good > stuff in the master branch, and no Mitaka release yet, I'd like to make > a release next Thursday, December 3. > > First, I've

Re: [openstack-dev] [ironic] [inspector] Releases and things

FYI the same thing applies to both inspector and (very soon) inspector-client. On 11/26/2015 04:30 PM, Ruby Loo wrote: On 25 November 2015 at 18:02, Jim Rollenhagen > wrote: Hi all, We're approaching OpenStack's M-1 milestone,

[openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

Hi all, We want to support xbzrle compress for live migration. Now there are 3 options, 1. add the enable flag in nova.conf. such as a dedicated 'live_migration_compression=on|off" parameter in nova.conf. And nova simply enable it. seems not good. 2. add a parameters in live

Re: [openstack-dev] [magnum] Using docker container to run COE daemons

Jay, Agree and disagree. Containerize some COE daemons will facilitate the version upgrade and maintenance. However, I don’t think it is correct to blindly containerize everything unless there is an investigation performed to understand the benefits and costs of doing that. Quoted from Egor,

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Thu, Nov 26 2015, Stéphane Albert wrote: Here a first reply about resource handling. > Resource data > = > Duplicated resource informations from ceilometer, only revision timestamps > changing. So I guess that's a bug in Gnocchi, we should not create new revision if there is 0

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Thu, Nov 26 2015, Stéphane Albert wrote: Now about measures. > We don't get any data, but there is data with a bigger granularity. We don't > have a way to know that but request the archive policy and parse it. Oh I see. I think we can consider that as being a bug in the API, that should be

Re: [openstack-dev] More and more circular build dependencies: what can we do to stop this?

Thomas Goirand wrote: > What can we do so that it doesn't constantly happen again and again? > It's a huge pain for downstream package maintainers and distros. The only way to avoid it constantly happening again and again is to test against it in check/gate. "If it's not tested, it's broken" --

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Thu, Nov 26, 2015 at 05:04:02PM +0100, Julien Danjou wrote: > On Thu, Nov 26 2015, Stéphane Albert wrote: > > Here a first reply about resource handling. > > > Resource data > > = > > Duplicated resource informations from ceilometer, only revision timestamps > > changing. > > So

Re: [openstack-dev] More and more circular build dependencies: what can we do to stop this?

On 27 November 2015 at 03:50, Thomas Goirand wrote: > Hi, > > As a package maintainer, I'm seeing more and more circular > build-dependency. The latest of them is between oslotest and oslo.config > in Mitaka. > > There's been some added between unittest2, linecache2 and

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Thu, Nov 26 2015, Stéphane Albert wrote: > I'll open a bug with a full history dump, sometime it's due to the host > changing (flapping) from name to hash, this might be due to > ceilometer. This would be a Ceilometer (or above) bug indeed. I think I saw something recently. It's possible the

Re: [openstack-dev] [nova]New Quota Subteam on Nova

Hi Markus, I totally agree with you, we'll add some effort to close bugs related to quotas, but there is some bugs like "Quotas can be exceeded by making highly parallel requests" that will not be easy to fix on the current quota design. For now,

Re: [openstack-dev] [gnocchi][rating] Issues regarding gnocchi support in CloudKitty

On Thu, Nov 26, 2015 at 05:31:38PM +0100, Julien Danjou wrote: > On Thu, Nov 26 2015, Stéphane Albert wrote: > > > I'll open a bug with a full history dump, sometime it's due to the host > > changing (flapping) from name to hash, this might be due to > > ceilometer. > > This would be a

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Openstack uses the hostname as a primary key in many of the project. Nova and neutron both do this. If you had two nodes with the same host name then it would cause undefined behavior. Based on the error Andreas highlighted are you currently trying to configure ovs-dpdk with vxlan/gre? I

[openstack-dev] [neutron][tap-as-a-service] Tap-as-a-service API

Folks, Any plan to revive this [1] so we can discuss and finalize the use cases and APIs. [1] https://review.openstack.org/#/c/96149/ Thanks, Fawad Khaliq __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On 26 November 2015 at 15:55, 少合冯 wrote: > Hi all, > We want to support xbzrle compress for live migration. > > Now there are 3 options, > 1. add the enable flag in nova.conf. > such as a dedicated 'live_migration_compression=on|off" parameter in > nova.conf. > And

[openstack-dev] [group-based-policy] Meeting today

Hi GBP team, Is the meeting today not going to happen due to US Thanksgiving? Best regards, Igor Duarte Cardoso - Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263

Re: [openstack-dev] [nova]New Quota Subteam on Nova

On 26 November 2015 at 16:46, Raildo Mascena wrote: > Hi Markus, > > I totally agree with you, we'll add some effort to close bugs related to > quotas, but there is some bugs like "Quotas can be exceeded by making highly > parallel requests" that will not be easy to fix on the

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: > Hi all, > We want to support xbzrle compress for live migration. > > Now there are 3 options, > 1. add the enable flag in nova.conf. > such as a dedicated 'live_migration_compression=on|off" parameter in > nova.conf. > And nova simply

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On 26 November 2015 at 17:39, Daniel P. Berrange wrote: > On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: >> Hi all, >> We want to support xbzrle compress for live migration. >> >> Now there are 3 options, >> 1. add the enable flag in nova.conf. >> such as a

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On 26/11/15 15:55, 少合冯 wrote: Hi all, We want to support xbzrle compress for live migration. Now there are 3 options, 1. add the enable flag in nova.conf. such asa dedicated 'live_migration_compression=on|off" parameter in nova.conf. And nova simply enable it. seems not good. 2.

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On Thu, Nov 26, 2015 at 05:49:50PM +, Paul Carlton wrote: > Seems to me the prevailing view is that we should get live migration to > figure out the best setting for > itself where possible. There was discussion of being able have a default > policy setting that will allow > the operator to

Re: [openstack-dev] [oslo] fake driver doesn't work with multi topics

On 26/11/15 10:40 +0900, Masahito MUROI wrote: Hi oslo.message folks, We are trying to use oslo_message's fake driver [1] for our testing. However, the driver doesn't seem to work with multi topics. Is this behavior expected or a bug? mmh, I'd say it's not. It's very likely this fake driver

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

On Thu, Nov 26, 2015 at 05:39:04PM +, Daniel P. Berrange wrote: > On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: > > 3. dynamically choose when to activate xbzrle compress for live migration. > > This is the best. > > xbzrle really wants to be used if the network is not able

Re: [openstack-dev] [group-based-policy] Meeting today

Hi Igor, Yes, no meeting today. We discussed in last week’s IRC. Happy Thanksgiving! ;-) Best, ~Sumit. On Thu, Nov 26, 2015 at 9:31 AM, Duarte Cardoso, Igor wrote: > Hi GBP team, > > > > Is the meeting today not going to happen due to US Thanksgiving? > > > > Best