Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

The status is as follows: 1) Fuel-main [1] and fuel-library [2] patches can deploy the master node w/o docker containers 2) I've not built experimental ISO yet (have been testing and debugging manually) 3) There are still some flaws (need better formatting, etc.) 4) Plan for tomorrow is to build

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

Hi, I am working on the TOSCA CSAR plugin for murano and so far am able to successfully import an application definition archive of my CSAR example to murano. However, when I try to add the imported application to an environment I get this error from Murano Dashboard:

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

On Tue, Nov 24, 2015 at 11:35:34AM +0100, Thierry Carrez wrote: > Tony Breeds wrote: > > [...] > > I understand that we want to keep the number of parallel meetings to a > > minimum, > > but is it time to add #openstack-meeting-5? > > Some slots are taken by groups that have not been holding

Re: [openstack-dev] [networking-ovs-dpdk]

FYI, bug 1513367 is opened for this apparmor problem to track when booting vms failed with ovs-dpdk enabled. https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367 On Tue, Nov 24, 2015 at 9:49 PM, Mooney, Sean K wrote: > Out of interest > > Have you removed

[openstack-dev] [all] Thoughts on python-future?

Hi all, I¹ve been using the python-future library for Python 3 porting and want to see what people think of it. http://python-future.org/overview.html#features The end result is standard Python3 code made compatible with Python2 through library imports. The great thing is that Python 3

Re: [openstack-dev] [all] Thoughts on python-future?

Which bit in particular do you like? Some of the stuff - like past.translation - is likely to be deeply fragile, other bits are fine, but not really any different to six. On 25 November 2015 at 15:33, Eric Kao wrote: > Hi all, > > I’ve been using the python-future

[openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Hi, Neutron has now various subprojects and some of them would like to implement Horizon supports. Most of them are additional features. I would like to start the discussion where we should have horizon support. [Background] Horizon team introduced a plugin mechanism and we can add horizon

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 24/11/15 19:20, Dolph Mathews wrote: Scenarios I've been personally involved with where the "distrustful" model either did help or would have helped: - Employee is reprimanded by management for not positively reviewing & approving a coworkers patch. - A team of employees is pressured to

Re: [openstack-dev] [networking-ovs-dpdk]

Thank you so much Sean, It helped a lot and that I have VMs active running :) That's so kind of you to spend your time. It would be nice if this apparmor thing is mentioned somewhere in the documentation, will help newbies like me. @Hui - Thank you for the info and the config file :) Thanks,

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Hi Akihiro, Great initiative. On Wed, Nov 25, 2015 at 10:46 AM, Akihiro Motoki wrote: > Hi, > > Neutron has now various subprojects and some of them would like to > implement Horizon supports. Most of them are additional features. > I would like to start the discussion where

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

On Wed, Nov 25, 2015 at 12:51:54PM +1100, Tony Breeds wrote: > There is lots of hygiene stuff to do in the repo :) I'll see what I can come > up > with but at the very least it's going to require a bunch of people to +1 a > review to drop their meeting ;P Okay it wasn't too bad. Of the

Re: [openstack-dev] Rally as A Service?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/15 1:35 PM, Munoz, Obed N wrote: > Is there any plan or work-in-progress for RaaS (Rally as a > Service)? I saw it mentioned on > https://wiki.openstack.org/wiki/Rally I think we've talked about something like this at the Operators

Re: [openstack-dev] Rally as A Service?

-- Obed N Munoz Cloud Engineer @ ClearLinux Project Open Source Technology Center On 11/24/15, 4:11 PM, "JJ Asghar" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >On 11/24/15 1:35 PM, Munoz, Obed N wrote: >> Is there any plan or work-in-progress for RaaS

Re: [openstack-dev] [magnum-ui][magnum] Suggestions for Features/Improvements

Thanks Brad, just added a new item of "Enable end user create container objects via magnum-ui, such as creating pod, rc, service etc", it would be great if we can enable end user create some container applications via magnum UI, comments? Thanks! On Wed, Nov 25, 2015 at 1:15 AM, Bradley Jones

Re: [openstack-dev] Rally as A Service?

Obed, We are refactoring Rally to make it possible to run it as a deamon. There is plenty amount of work that should be done, including this spec: https://review.openstack.org/#/c/182245/ Best regards, Boris Pavlovic On Tue, Nov 24, 2015 at 2:20 PM, Munoz, Obed N wrote:

[openstack-dev] [all][glance][api][infra][defcore] last call for feedback on image import (again)

Thanks to all the OpenStackers who have participated so far. A major revision is now available for your reading pleasure. https://review.openstack.org/#/c/232371/ I realize a USA holiday is coming up very soon this week ... the Glance community would be thankful to get some comments before

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Hi Doug! Thanks for taking the time to gather opinions before going ahead. On 11/23/2015 10:58 PM, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches

Re: [openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

On Tue, Nov 24, 2015 at 7:39 AM, Jim Rollenhagen wrote: > On Mon, Nov 23, 2015 at 03:35:58PM -0800, Shraddha Pandhe wrote: > > Hi, > > > > I would like to know how everyone is using maintenance mode and what is > > expected from admins about nodes in maintenance. The

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

On Nov 24, 2015, at 4:35 AM, Thierry Carrez wrote: > I'd rather standardize and rename -alt to -2 (i.e. redirect -alt to -2 > on IRC, and bulk-change all meetings YAML from -alt to -2). +1. 'alt' is confusing. -- Ed Leafe signature.asc Description: Message signed

Re: [openstack-dev] [neutron][sfc]

Hi Oguz, I will forward you the email on the steps of using DevStack to set up SFC. As you mentioned, the DevStack support patch for networking-sfc is being worked on and under review. The codes that support this feature including unit test codes have been developed and uploaded for review.

[openstack-dev] [puppet] Puppet 4 and Beaker testing

Today we do unit testing against all kinds of puppet versions but beaker's acceptance testing is currently limited to the 3.8.x series. The is because we install "latest" Puppet from Puppet Labs repositories but do so using the old packaging style which relied on dependency packages being

[openstack-dev] [searchlight] Weekly IRC meeting cancelled

We will not be holding our weekly IRC meeting this week due to the US Thanksgiving holiday. Our regular meeting will resume Thursday, December 3rd. As always, you can find the meeting schedule and agenda here: http://eavesdrop.openstack.org/#Searchlight_Team_Meeting Thanks, Travis

[openstack-dev] [cinder][nova]Move encryptors to os-brick

> the cinder admin and the nova admin are ALWAYS the same people There is interest in hybrid clouds where the Nova and Cinder services are managed by different providers. The customer would place higher trust in Nova because you must trust the compute service, and the customer would place less

[openstack-dev] [networking-ovn] Supporting multiple routes per router interface

Hi, The https://review.openstack.org/#/c/237820/ patch added the support for adding router interfaces in OVN NB. This patch only provides support for a single route per interface. Neutron supports multiple routes per router interface. While attempting to model this in OVN Northbound DB, I ran

Re: [openstack-dev] [Openstack-i18n] DocImpact Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Akihiro, Judging by most of the bugs we see in the openstack-manuals queue, the bugs that will be raised in projects' own queues will usually be against their own developer documentation. In the rare instance that that isn't the case, and it

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

this is the history Brant provided: http://lists.openstack.org/pipermail/openstack-dev/2014-May/036427.html it's apparently on his todo list... or until he finds the person he needs to defer it to[1] [1]

[openstack-dev] [Magnum] Why set DEFAULT_DOCKER_TIMEOUT = 10 in docker client?

hi all In Magnum code, we hardcode it as DEFAULT_DOCKER_TIMEOUT = 10 This bring troubles in some bad networking environment (or bad performance swarm master) At least it doesn't work on our gate. Here is the test patch on gate https://review.openstack.org/249522 , I set it as 180 to make sure

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On 24 November 2015 at 21:46, Akihiro Motoki wrote: > Hi, > > Neutron has now various subprojects and some of them would like to > implement Horizon supports. Most of them are additional features. > I would like to start the discussion where we should have horizon support. > >

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On Wed, Nov 25, 2015 at 12:06 PM, Armando M. wrote: > > > On 24 November 2015 at 21:46, Akihiro Motoki wrote: > >> Hi, >> >> Neutron has now various subprojects and some of them would like to >> implement Horizon supports. Most of them are additional

[openstack-dev] [Neutron][TaaS] Query regarding TaaS API

Dear Members of Neutron-TaaS community, I have a few queries related to the TaaS API, and would like to know a bit more details about them. a) Currently Tap Service and Tap flow Endpoints are listed under /v2_0/taas/ For example: http://111.000.222.115:9696/v2.0/taas/tap-services.json

Re: [openstack-dev] [Magnum] Why set DEFAULT_DOCKER_TIMEOUT = 10 in docker client?

Li Yong, At any rate, this should not be hardcoded. I agree that the default value should match the RPC timeout. Adrian > On Nov 24, 2015, at 11:23 PM, Qiao,Liyong wrote: > > hi all > In Magnum code, we hardcode it as DEFAULT_DOCKER_TIMEOUT = 10 > This bring troubles

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Gord, Hi Ryota, Thanks for your detailed responses. Hope you don't mind that I'm sending one reply to both of your emails. I think it would be easier to have one thread for this discussion. Let me explain our use case in more details. Here is an example of how we would like to integrate

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Gord, Hi Ryota, (I sent the same mail again in a more readable format) Thanks for your detailed responses. Hope you don't mind that I'm sending one reply to both of your emails. I think it would be easier to have one thread for this discussion. Let me explain our use case in more details.

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/24/2015 8:35 AM, Andrew Laski wrote: On 11/24/15 at 10:26am, Balázs Gibizer wrote: I think see your point, and it seems like a good way forward. Let's turn the black list to a white list. Now I'm thinking about creating a new Field type something like WhiteListedObjectField which

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

> keystonemiddleware 1.5.3: Middleware for OpenStack Identity periodic-ceilometer-python27-kilo started failing after this release First bad: http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-kilo/40c5453/testr_results.html.gz test_acl_scenarios failing with 401 Unauthorized

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Tue, Nov 24, 2015 at 6:44 AM, Lance Bragstad wrote: > I think one of the benefits of the current model was touched on earlier by > dstanek. If someone is working on something for their organization, they > typically bounce ideas of others they work with closely. This

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/24/15 at 11:19am, Ryan Rossiter wrote: On 11/24/2015 8:35 AM, Andrew Laski wrote: On 11/24/15 at 10:26am, Balázs Gibizer wrote: I think see your point, and it seems like a good way forward. Let's turn the black list to a white list. Now I'm thinking about creating a new Field

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Folks, I have updated a spec, please review: https://review.openstack.org/#/c/243340 On Fri, Nov 20, 2015 at 4:50 PM, Dmitry Nikishov wrote: > Stanislaw, > > proposing patches could be a viable option long-term, however, by the time > these patches will make it upstream,

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

On Mon, Nov 23, 2015 at 08:34:46PM EST, John Belamaric wrote: > It currently only supports greenfield deployments. See [1] - we plan to build > a migration in the Mitaka time frame. A DevStack stack.sh run is about as greenfield as it's going to get. So, this leaves me wondering: how are we

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

Ignore me, I'm not able to read and comprehend today. Sorry. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

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

On 11/23/2015 01:20 AM, Juan Antonio Osorio wrote: > > > On Sat, Nov 21, 2015 at 2:05 AM, Ben Nemec > wrote: > > Thinking about this some more makes me wonder if we need a sample config > generator like oslo.config. It would work

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

On 11/23/2015 06:03 AM, Daniel P. Berrange wrote: On Fri, Nov 20, 2015 at 02:44:17PM -0500, Ben Swartzlander wrote: On 11/20/2015 01:19 PM, Daniel P. Berrange wrote: On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote: Brick does not have to take over the decisions in order to be a

[openstack-dev] [nova]Please see request for input on review

Sean Please can you look at cancel live migration nova spec, I'd like to progress this spec ASAP. Last Thursday, Jay Commented @sdague @edleafe: Please see the long conversation about the RESTful-ness of the API on the pause live migration spec:

Re: [openstack-dev] [nova] Nova meeting this Thursday

+1 On Tue, Nov 24, 2015 at 11:51 PM, John Garbutt wrote: > Hi, > > I just wanted to share my plan for Thursday's meeting. > > As it is thanksgiving in the US, I am assuming no US based people will > attend. > > Given there are lots of non-US people around, and it is our

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 25 November 2015 at 05:26, Thierry Carrez wrote: ... > So it would be a shame to restrict task tracking possibilities to two > projects per bug just to preserve accurate change tracking in Launchpad, > while the plan is to focus Launchpad usage solely on task tracking :)

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Robert Collins wrote: > [...] > So, if folk do want bugs to sit in fix-committed, we can address the > timeouts really very easily: one (or two tops) projects per bug. We > should do that anyway because adding a comment to a bug is also able > to timeout, so our code is still going to suffer the

[openstack-dev] Cross-Project Meeting SKIPPED, Tue Nov 24th, 21:00 UTC

Hi all! As discussed in one of cross-project meetings [1], we will be skipping meetings if there are no agenda items to discuss. There are no items to discuss this time around, but someone can still call for a meeting by adding an agenda item for December 1st [2]. We also have a new meeting

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: John Garbutt [mailto:j...@johngarbutt.com] > Sent: November 24, 2015 16:09 > On 24 November 2015 at 15:00, Balázs Gibizer > wrote: > >> From: Andrew Laski [mailto:and...@lascii.com] > >> Sent: November 24, 2015 15:35 > >> On 11/24/15 at 10:26am, Balázs Gibizer

[openstack-dev] [magnum-ui][magnum] Suggestions for Features/Improvements

We have started to compile a list of possible features/improvements for Magnum-UI. If you have any suggestions about what you would like to see in the plugin please leave them in the etherpad so we can prioritise what we are going to work on.

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

On 11/23/2015 4:50 PM, Alan Pevec wrote: 2015-11-23 17:31 GMT+01:00 Matt Riedemann : Or do you also suggest juno-eol != 2014.2.4? I'd prefer to just remove the version tag in setup.cfg entirely so we switch to post-versioning, then we can EOL the thing. That's

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Lance makes some very good points below. I agree fully with them. Thanks, Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Lance Bragstad To: "OpenStack

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

Hi Lisa, In regards to your comment about the duplication of key management code in Cinder and Nova, there was a long-term plan to replace that code with a shared library when the encryption feature was implemented. The key manager code has been moved to its own library, Castellan [1]. The

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

On 11/24/2015 10:42 AM, Matt Riedemann wrote: On 11/23/2015 4:50 PM, Alan Pevec wrote: 2015-11-23 17:31 GMT+01:00 Matt Riedemann : Or do you also suggest juno-eol != 2014.2.4? I'd prefer to just remove the version tag in setup.cfg entirely so we switch to

Re: [openstack-dev] [Neutron] Call for review focus

On 24 November 2015 at 04:13, Rossella Sblendido wrote: > > > On 11/23/2015 06:38 PM, Armando M. wrote: > >> >> >> On 23 November 2015 at 04:02, Rossella Sblendido > > wrote: >> >> >> >> On 11/20/2015 03:54 AM, Armando M.

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

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 tables, to not expose soft deleted resources in the REST API in new ways, and to

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

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 actively used in our CI system. Regarding this topic, I'm aware that quite some effort has been done in the past [2] and I

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

mriedem and myself resolved this with keystone folks earlier today[1]. should be all better now [2] [1] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2015-11-24.log.html#t2015-11-24T14:38:39 [2] https://review.openstack.org/#/c/249268/ On 24/11/15 12:33 PM, Alan

Re: [openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

Another use cases for maintenance node are: * HW component replacement, e.g. NIC, or disk * FW upgrade/downgrade - we should be able to use ironic FW management API/CLI for it. * HW configuration change. Like re-provision server, like changing RAID configuration.

[openstack-dev] Rally as A Service?

Hi folks, Is there any plan or work-in-progress for RaaS (Rally as a Service)? I saw it mentioned on https://wiki.openstack.org/wiki/Rally I’d like to know if there’s an ongoing effort and if we can join that in order to make it a reality. -- Obed N Munoz Cloud Engineer @ ClearLinux

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

Would it be possible to get a bit more detail in (especially if other projects are mocking like this) what is being done so that I [or anothe rKeystone dev] can work towards a real mock/test module in keystonemiddleware so this doesn't occur again due to internal-interface mocking? On Tue, Nov

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Ifat, Thank you for starting discussion how AODH can be integrated with Vitrage that would be a good example of AODH integration with other OpenStack components. The key role of creating alarm definition is to set endpoint (alarm_actins) which can be receive alarm notification from AODH.

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

Vitaly, That's great news. I agree that we need to run fuelclient against every change in nailgun, but on the other hand - I think we should stick to the protocol that Igor proposed: * Announce this change in openstack-dev ML. * Wait 1 week before approving it, so anyone can prepare. * Change

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

Le lundi 23 novembre 2015, à 14:00 +0100, Ihar Hrachyshka a écrit : > Vincent Untz wrote: > > >Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit : > >>Vincent Untz wrote: > >> > >>>Hi, > >>> > >>>I know 2014.2.4 is (in theory) the last juno

[openstack-dev] [vitrage] Next vitrage meeting

Hi, Vitrage weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress from last week * Review action items * Next steps * Open Discussion You are welcome to join. Vitrage meetings page:

Re: [openstack-dev] Fwd: [Senlin]Support more complicated scalingscenario

> After debugging, I found that former result is not overridden by > another policy. > http://git.openstack.org/cgit/openstack/senlin/tree/senlin/engine/actions/base.py#n441 I think you are not referring to a correct location in the source code. That line was only about checking whether there

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

+1 On Thu, Nov 19, 2015 at 11:08 AM, Michael Johnson wrote: > +1 > > On Thu, Nov 19, 2015 at 9:35 AM, Eichberger, German > wrote: > > All, > > > > > > > > As I said in a previous e-mail I am really excited about the deep talent > in the Octavia

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Good, wide ranging discussion. From my point of view, this isn’t about trusting cores, rather (as was pointed out by others) ensuring people with different customer perspectives be part of the approval. Of course, you could argue they could have -1’d it anyway, but I think ensuring

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Steve Martinelli wrote: > So it's only for this time around (Mitaka-1) that I'll have to tag bugs > as fix-released, because the release automation will just leave a comment? We'll likely turn all FixCommitted bugs to FixReleased (one last time) as part of the transition, so you don't really need

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Tony Breeds wrote: > [...] > I understand that we want to keep the number of parallel meetings to a > minimum, > but is it time to add #openstack-meeting-5? Some slots are taken by groups that have not been holding meetings for quite a long time. For good hygiene, I'd like us to clean those up

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean, Thanks for you kind help. I did the following. # apt-get install ubuntu-cloud-keyring # echo "deb http://ubuntu-cloud.archive.canonical.com/ubuntu " \

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Clint Byrum wrote: > Excerpts from Brad Topol's message of 2015-11-23 13:38:34 -0800: >> So to avoid the perception of a single company owning a piece of code, at >> IBM our policy for major projects like Cinder, Nova and currently many >> parts of Keystone (except pycadf) is to make sure we do

[openstack-dev] [puppet] Puppet OpenStack Mid-Cycle (Mitaka)

Hello, If you're involved in Puppet OpenStack or if you want to be involved, please look at this poll: http://goo.gl/forms/lsBf55Ru8L Thanks a lot for your time, -- Emilien Macchi signature.asc Description: OpenPGP digital signature

Re: [openstack-dev] [Congress] tempest tests in gate not running

Tim, Previous failure on gate is fixed with this patch https://review.openstack.org/#/c/247314/ Now congress tempest tests are running, so our tempest plugin worked :) http://logs.openstack.org/10/237510/5/check/gate-congress-dsvm-api/0bdbb53/console.html Current gate failures report a different

Re: [openstack-dev] [nova] FKs in the DB

On Mon, Nov 23 2015, Jordan Pittier wrote: > Is the DB the limiting factor of openstack performance ? De we have hard > evidence of this ? We need numbers before acting otherwise it will be an > endless discussion. > > When I look at the number of race conditions we had/have in OpenStack, it >

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Mon, Nov 23 2015, Morgan Fainberg wrote: > What I would like us to do is to move to a trustful policy. I can > confidently say that company affiliation means very little to me when I was > PTL and nominating someone for core. We should explore making a change to a > trustful model, and allow

[openstack-dev] [cloudkitty] Remove inactive contributors from cloudkitty-core

Hi, Some people in the cloudkitty-core group are not active anymore. They haven't produced a single contribution during the last cycle. Here is the list of the two people: - Adrian Turjak - François Magimel I think we should remove them from the group. We've got new faces in the project, let's

[openstack-dev] [neutron][sfc]

Hi, Is there any working Devstack configuration for sfc testing? I just saw one commit that is waiting review. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] Migration progress

Hi Paul, Comments inline: 2015-11-23 16:36 GMT+08:00 Paul Carlton : > John > > At the live migration sub team meeting I undertook to look at the issue > of progress reporting. > > The use cases I'm envisaging are... > > As a user I want to know how much longer my instance

Re: [openstack-dev] [Neutron] Security Groups OVS conntrack support

Thanks! I got it now: OpenStack already allows all "related" connections, and you need connection tracking for that. This was not very clear to me from the documentation... -Tapio On Mon, Nov 23, 2015 at 10:14 PM Russell Bryant wrote: > On 11/23/2015 02:16 PM, Kevin Benton

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > Sent: November 23, 2015 22:33 > On 11/23/2015 2:23 PM, Andrew Laski wrote: > > On 11/23/15 at 04:43pm, Balázs Gibizer wrote: > >>> From: Andrew Laski [mailto:and...@lascii.com] > >>> Sent: November 23, 2015 17:03 > >>> > >>> On 11/23/15

Re: [openstack-dev] [devstack]Question about using Devstack

@Bob Ball My goal is that I want to reboot devstack DomU without reinstall devstack. Thanks to @ALL I finally reboot devstack successfully without reinstalling.in my case by this way. First I add `exit 0` before the first line of stack.sh to stop openstack running. Then i use these commands

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

Hi would you be able to attach the n-cpu log form the computenode and the n-sch and q-svc logs for the controller so we can see if there is a stack trace relating to the vm boot. Also can you confirm ovs-dpdk is running correctly on the compute node by running sudo service ovs-dpdk status

[openstack-dev] [ceph] DevStack plugin for Ceph required for Mitaka-1 and beyond?

Hi, I was trying to figure out the state of DevStack plugin for Ceph, but couldn't find its source code and ran into the following doubt. At Mitaka 1, i.e. next week, wouldn't Ceph related Jenkins gates (e.g. Cinder's gate-tempest-dsvm-full-ceph) that still use extras.d's hook script instead of a

Re: [openstack-dev] [Heat] how to start heat through devstack

Hi, P. Ramanjaneya Reddy. Please read Heat documentation page: http://docs.openstack.org/developer/heat/getting_started/on_devstack.html#configure-devstack-to-enable-heat In your case it looks like you use localrc for new version of devstack, so you need use local.conf file instead. If it will

Re: [openstack-dev] [release] process change for closing bugs when patches merge

Excerpts from Armando M.'s message of 2015-11-23 17:37:47 -0800: > On 23 November 2015 at 13:58, Doug Hellmann wrote: > > > As part of completing the release automation work and deprecating our > > use of Launchpad for release content tracking, we also want make some > >

Re: [openstack-dev] [openstack-ansible] Random ssh errors in gate check jobs

On 11/23/2015 06:32 AM, Jesse Pretorius wrote: > Thanks for digging into this Major. It is a royal pain and will likely be > resolved with the release of Ansible 2, but for now we're stuck with having > to work around the issue with what we have. > > I wonder, is there a difference in results

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/24/15 at 10:26am, Balázs Gibizer wrote: From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] Sent: November 23, 2015 22:33 On 11/23/2015 2:23 PM, Andrew Laski wrote: > On 11/23/15 at 04:43pm, Balázs Gibizer wrote: >>> From: Andrew Laski [mailto:and...@lascii.com] >>> Sent: November 23,

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

I think one of the benefits of the current model was touched on earlier by dstanek. If someone is working on something for their organization, they typically bounce ideas of others they work with closely. This tends to be people within the same organization. The groups developing the feature might

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 24, 2015 15:35 > On 11/24/15 at 10:26am, Balázs Gibizer wrote: > >> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > >> Sent: November 23, 2015 22:33 > >> On 11/23/2015 2:23 PM, Andrew Laski wrote: > >> > On 11/23/15 at

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 24 November 2015 at 15:00, Balázs Gibizer wrote: >> From: Andrew Laski [mailto:and...@lascii.com] >> Sent: November 24, 2015 15:35 >> On 11/24/15 at 10:26am, Balázs Gibizer wrote: >> >> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] >> >> Sent: November

Re: [openstack-dev] [ceph] DevStack plugin for Ceph required for Mitaka-1 and beyond?

Hi Ramana, I’ll resurrect the infra patch and put the project under the right namespace. There is no plugin at the moment. I’ve figured out that this is quite urgent and we need to solve this asap since devstack-ceph is used by the gate as well :-/ I don’t think there is much changes to do on

[openstack-dev] [nova][infra][bugs] Grafana Dashboard for Bugs

Background == We have "grafana" for data visualization [1] and I'd like to introduce a dashboard which shows data from our bug tracker Launchpad. Based on ttx's code [2] for the "bugsquashing day stats" [3] I created a PoC (screenshot at [4]). The code which collects the data from

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

Please have a look at your neutron server log and neutron agent log and provide this information if you have troubles interpreting the messages. Probably you'll find the reason there! -- Andreas (IRC: scheuran) On Di, 2015-11-24 at 12:17 +0100, Praveen MANKARA RADHAKRISHNAN wrote: > Hi, >

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

In fact, we (I and Dmitry) are on the same page of how to merge these two features (Centos7 and Docker removal). We agreed that Dmitry's feature is much more complicated and of higher priority. So, Centos 7 should be merged first and then I'll rebase my patches (mostly supervisor -> systemd).

[openstack-dev] [all][oslo] qpidd driver has been removed from oslo.messaging. RIP qpidd driver

Greetings, The qpidd driver had been marked as deprecated in Liberty[0] and the planned removed has now been done[1]. This change removes the *qpidd* driver, which is different from the amqp1 one, which depends on `python-qpid-proton`. If there are questions, please, don't hesitate to ask.

Re: [openstack-dev] [hyper-v] oslo.privsep vs Windows

Hello, Thanks Dims for raising the concern and Angus for reaching out. :) Most of the time, python development on Windows is not too far off from Linux. But the two systems are quite different, which imply different modules (fcntl, pwd, grp modules do not exist in Windows) or different

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

Hi, Am trying to set up an open stack (kilo) installation using ovs-dpdk through devstack installation. I have followed the " https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst " documentation. I used the same versions as in documentation (fedora21, with

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 24 November 2015 at 06:21, Adam Young wrote: > > So, having been one of the initial architects of said policy, I'd like to > reiterate what I felt at the time. The policy is in place as much to > protect the individual contributors as the project. If I was put in a >

[openstack-dev] [Heat] how to start heat through devstack

Hi, How to start heat using devstack, i've added below services in localrc but throwing an error localrc: ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng IMAGE_URLS+=",

Re: [openstack-dev] [Neutron] Call for review focus

On 11/23/2015 06:42 PM, Armando M. wrote: On 23 November 2015 at 09:22, Carl Baldwin > wrote: On Mon, Nov 23, 2015 at 5:02 AM, Rossella Sblendido > wrote: > To cross-reference we can

  1   2   >