Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On 30 November 2015 at 18:19, Derek Higgins wrote: > Hi All, > > A few months tripleo switch from its devtest based CI to one that was > based on instack. Before doing this we anticipated disruption in the ci > jobs and removed them from non tripleo projects. > > We'd like to investigate

[openstack-dev] Install Openstack-Ansible

Hi All, I have been following the below link for Openstack-Ansible : http://docs.rackspace.com/rpc/api/v11/bk-rpc-installation/content/ch-playbooks-openstack.html#sec-utility-container-overview . The ansible playbooks are running as of now and as per my understanding, it is only installing the

Re: [openstack-dev] [murano]How to use Murano to transmit files to Mistral and execute scripts on Mistral

On Mon, Nov 30, 2015 at 5:07 AM, WANG, Ming Hao (Tony T) < tony.a.w...@alcatel-lucent.com> wrote: > For the object storage support, does Murano have any plan to support the > auto-uploading function? Murano has plans to support everything applications may need. It is just a matter of priorities/

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov to core reviewers of fuel-mirror

-1 I personally know Dmitry and respect his contributions into our package management and CI systems around it. Thanks to Dmitry, a lot of bad things were prevented and many things developed which work very well. However, I don't particularly understand this proposal, and I'd like to get some clar

Re: [openstack-dev] [ironic] Install Time Too Long Ironic in devstack

Hi Zhi, it seems that Ironic is building a new deploy ramdisk for you with diskimage-builder. You can skip it if you state IRONIC_BUILD_DEPLOY_RAMDISK=False in your local.conf, then the bootstrap image will be downloaded from tarballs.o.o. If you are interested here is a sample ironic setting f

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks _

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

Hi Sean, I noticed that above talking using openstack with dpdk only in devstack. I already have kilo environment and want it to support dpdk. Could reinstalling ovs with dpdk will be work? Thanks. Yu 在 2015/11/27 20:38, Mooney, Sean K 写道: For kilo we provided a single node all in o

Re: [openstack-dev] [Magnum] Liberty RPMs for RDO

Hello Mathieu, On Mon, Nov 30, 2015 at 4:48 PM, Alan Pevec wrote: > Hi Mathieu, > > 2015-11-30 10:54 GMT+01:00 Mathieu Velten : > > Hi, > > > > Let me first introduce myself : I am currently working at CERN to help > > evaluate and deploy Magnum. > > > > In this regard Ricardo recently sends an

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

On 30.11.2015 14:28, Bogdan Dobrelya wrote: > Hello. > Please let's make this change [0] happen to the Oslo messaging. > This is reasonable, straightforward and backwards compatible change. And > it is required for OpenStack applications - see [1] - to implement a > sane HA. The only thing left is

Re: [openstack-dev] [Fuel] Feature Freeze is soon

Mike I think, it is rather good idea. I guess we can have a couple of requests still - although everyone is shy, we might get a little storm of FFE's. BTW, I will file at least one. On Tue, Dec 1, 2015 at 10:28 AM, Mike Scherbakov wrote: > Hi Fuelers, > we are couple of days away from FF [1]. I

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

sean roberts wrote: > Being successful at your first patch for most people means that their > first effort is different than an a regular patch. > > Identifying abandoned work more quickly is good. It doesn't help the > first timer. > > Tagging low hanging fruit for first timers I like. I'm rec

Re: [openstack-dev] [cross-project] Cross-project Liaisons

Mike Perez wrote: > [...] > I would like to propose cross-project liaisons which would have the following > duties: > > * Watching the cross-project spec repo [1]. > - Comment on specs that involve your project. +1 to carry forward for TC > approval. > -- If you're not able to provide t

[openstack-dev] [swift] [oslo.messaging] [fuel] [ha] Is Swift going to support oslo.messaging?

Hello folks, The issue I want to raise is related to Swift and Oslo.messaging. Currently Swift doesn't support oslo.messaging middleware. There is no possible to setup RabbitMQ HA setup in swift configuration, so we faced the problem [1] in Fuel. If we want to use Ceilometer notifications for Swif

[openstack-dev] [Magnum] 'fixed_network' actually means 'fixed_subnet'. Which way is better to fix this?

Hi All, I'm working on API related enhancement and encountered the following issue: bay-creation return 400 Bad Request with a valid fixed-network in baymodel( https://bugs.launchpad.net/magnum/+bug/1519748 ) The 'fixed_network' actually means 'fixed_network_cidr', or more precisely 'fixed_subnet

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

The nomination deadline is passed, we have two candidates! I'll be setting up the election shortly (with Jeremy's help to generate election rolls). Cheers, -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not

[openstack-dev] [midonet] IRC: ditch #midonet-dev?

Hi, Our IRC channels have been neglected for a long time, and as a result we lost ownership of #midonet-dev, which is now owner by freenode-staff. In theory, it should be very easy to get ownership back, particularly since we still own #midonet. But in reality, it seems like none of the freenode s

Re: [openstack-dev] [midonet] IRC: ditch #midonet-dev?

+1 for #2 On Tue, Dec 1, 2015 at 10:57 AM, Sandro Mathys wrote: > Hi, > > Our IRC channels have been neglected for a long time, and as a result > we lost ownership of #midonet-dev, which is now owner by > freenode-staff. In theory, it should be very easy to get ownership > back, particularly sinc

Re: [openstack-dev] [midonet] IRC: ditch #midonet-dev?

On Tue, Dec 1, 2015 at 10:59 AM, Ivan Kelly wrote: > +1 for #2 > PS: Beware of the top-posting! It makes vote counting harder ;-) > > On Tue, Dec 1, 2015 at 10:57 AM, Sandro Mathys > wrote: > > Hi, > > > > Our IRC channels have been neglected for a long time, and as a result > > we lost owner

Re: [openstack-dev] [midonet] IRC: ditch #midonet-dev?

On Tue, Dec 1, 2015 at 7:08 PM, Antoni Segura Puimedon wrote: > > > On Tue, Dec 1, 2015 at 10:59 AM, Ivan Kelly wrote: >> >> +1 for #2 > > > PS: Beware of the top-posting! It makes vote counting harder ;-) > >> >> >> On Tue, Dec 1, 2015 at 10:57 AM, Sandro Mathys >> wrote: >> > Hi, >> > >> > Our

Re: [openstack-dev] [ironic] Install Time Too Long Ironic indevstack

Thanks for your reply. But now, I meet a new problem. My console display: 2015-12-01 10:06:20.591 | ++ timeout 15 sh -c 'while ! ssh -p 22 -o StrictHostKeyChecking=no -i /opt/stack/data/ironic/ssh_keys/ironic_key stack@10.250.11.127 echo success; do sleep 1; done' 2015-12-01 10:06:35.598 | ++ di

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov to core reviewers of fuel-mirror

On 12/01/2015 09:25 AM, Mike Scherbakov wrote: > 4. I don't quite understand how repo is organized. I see a lot of > Python code regarding to fuel-mirror itself and packetary, which is > used as fuel-mirrors core and being written and maintained mostly by > Bulat [5]. There are seem to

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

On 30.11.2015 13:03, Bogdan Dobrelya wrote: > On 20.11.2015 17:41, Bogdan Dobrelya wrote: >>> Hi, >>> >>> let me try to rephrase this a bit and Bogdan will correct me if I'm wrong >>> or missing something. >>> >>> We have a set of top-scope manifests (called Fuel puppet tasks) that we use >>> for O

Re: [openstack-dev] [Magnum] 'fixed_network' actually means 'fixed_subnet'. Which way is better to fix this?

Hi HouMing, I checked the heat templates again, and check with heat developers. For heat stack creation now, it can not directly use existed network when create new stack. which means, it need create a new net and subnet. So for fixed_network, the name is still need. just like when you create netw

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

Hi, > pregenerated catalogs for the Noop tests to become the very first > committed state in the data regression process has to be put in the > *separate repo* +1 to that, we can put this new repo into .fixtures.yml > note, we could as well move the tests/noop/astute.yaml/ there +1 here too, as

[openstack-dev] [all][oslo] On Python 3, request_id must by Unicode, not bytes

Hi, The next oslo.context release including the following change (still under review) might break the voting Python 3 gate of your project: https://review.openstack.org/#/c/250731/ Please try to run Python 3 tests of your project with this change. I already ran the tests on Python 3 of th

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 01/12/15 04:13, Russell Bryant wrote: > On 11/30/2015 07:56 PM, Armando M. wrote: >> As a result, there is quite an effort imposed on the PTL, the various >> liaisons (release, infra, docs, testing, etc) and the core team to >> help manage the existing relationships and to ensure that the pictur

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

It can be selected but we have no tests for deployment which are run on periodical basis. So, we do not have any recent status. Also, serializer in Nailgun for Nova-Network is now not in use (it is not tested how serialization will work in 8.0). Aleksey Kasatkin On Tue, Dec 1, 2015 at 9:36 AM,

Re: [openstack-dev] [Neutron] Evolving the stadium concept

Armando M. wrote: > [...] > So my question is: would revisiting/clarifying the concept be due after > some time we have seen it in action? I would like to think so. I also think it's time to revisit this experience now that it's been around for some time. On one hand the Neutron stadium allowed to

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 01/12/15 05:16, Doug Wiegley wrote: > Part of the issue is that in a year, we added all the repos above. And > all of said repos were all heading over to infra with the same newbie > questions/mistakes. Not a bad thing in and of itself, but the sheer > volume was causing a lot of infra load. So

[openstack-dev] [kolla] ValueError: No JSON object could be decoded

Link: https://openstack.nimeyo.com/67158/?show=67158#q67158 From: kunciil TASK: [ceph | Fetching Ceph keyrings] * fatal: [gridppcl11 -> gridppcl13] => Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ansible/runner/init.py", lin

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On Mon, Nov 30, 2015 at 06:07:44PM -0500, Zane Bitter wrote: > On 30/11/15 12:51, Ruby Loo wrote: > > > > > >On 30 November 2015 at 10:19, Derek Higgins >> wrote: > > > >Hi All, > > > > A few months tripleo switch from its devtest based CI to one > >that w

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 01/12/15 10:42, Thierry Carrez wrote: > Armando M. wrote: >> [...] >> So my question is: would revisiting/clarifying the concept be due after >> some time we have seen it in action? I would like to think so. > I also think it's time to revisit this experience now that it's been > around for some

[openstack-dev] [kolla] Using existing ceph pools

Link: https://openstack.nimeyo.com/67172/?show=67172#q67172 From: kunciil I am planning to use an existing Ceph pool, the question is how to avoid [storage] group creating new Ceph pool with 'enableceph: "yes"' and how to pass existing Ceph values (rbduser,libvirtimagesrbd_pool etc...) to Nova,

[openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

Hi All I have the below sql query which - "lists routers connected to given internal and external networks" select DISTINCT routerports.router_id from routerports inner join ports as ports1 on (ports1.id=routerports.port_id and ports1.network_id=internal_network_id) inner join ports as ports

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

Hi, I'm porting OpenStack code to Python 3 for two years. I'm happy with six. It has been adopted by all OpenStack projects which are being ported to (or have been ported to) Python 3. It was discussed to use python-future in Swift, but Swift is now using six too. I wrote a tool to port an O

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

All informations on Python 3 are on the wiki: https://wiki.openstack.org/wiki/Python3 You may also join the IRC channel on Freenode: #openstack-python3 Victor Le 25/11/2015 03:33, Eric Kao a écrit : Hi all, I’ve been using the python-future library for Python 3 porting and want to see what pe

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

On 11/30/2015 01:28 PM, Bogdan Dobrelya wrote: > Hello. > Please let's make this change [0] happen to the Oslo messaging. > This is reasonable, straightforward and backwards compatible change. And > it is required for OpenStack applications - see [1] - to implement a > sane HA. The only thing left

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On Mon, Nov 30, 2015 at 03:35:13PM -0800, Devananda van der Veen wrote: >On Mon, Nov 30, 2015 at 3:07 PM, Zane Bitter wrote: > > On 30/11/15 12:51, Ruby Loo wrote: > >On 30 November 2015 at 10:19, Derek Higgins > wrote: > >    Hi All,

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

Bogdan, Which service would use this flag to start with? and how would the code change to provide "app side is fully responsible for duplicates handling"? Thanks, Dims On Tue, Dec 1, 2015 at 4:27 AM, Bogdan Dobrelya wrote: > On 30.11.2015 14:28, Bogdan Dobrelya wrote: >> Hello. >> Please let's

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 05:25 PM, Clint Byrum wrote: > Excerpts from Ben Nemec's message of 2015-11-30 13:22:23 -0800: >> On 11/30/2015 02:15 PM, Sean Dague wrote: >>> On 11/30/2015 03:01 PM, Robert Collins wrote: On 1 December 2015 at 08:37, Ben Nemec wrote: > On 11/30/2015 12:42 PM, Joshua Harlow

[openstack-dev] [neutron][neutron-*] Notice! pylint breakage

I found a problem yesterday running pep8 locally in neutron-lbaas. After discussing with LBaaS team, we identified that there is a problem with pylint. The same issues were seen, when hecking in neutron and neutron-vpnaas repos (need to check neutron-fwaas). There are two issues seen. First, the

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On 12/01/2015 01:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. >From an interop perspective, this concerns me a bit. My un

[openstack-dev] [neutron] Purpose and documentation of the API

Sometimes when I'm discussing or reviewing proposed specs, I feel as though I may have incorrect assumptions about what the Neutron API is _for_. And certainly I feel that we lack good unified documentation of it - or at least, that I haven't yet found that documentation, if it exists. So I'd lik

[openstack-dev] [QA][Infra] Continuous OpenStack quality monitoring and quality improvement plan

Dear OpenStack QA and Dev Team, A small group at the Software Engineering Department of the University of Szeged, Hungary is working on the quality improvements of OpenStack modules in collaboration with Ericsson Hungary. We created a WIKI page describing our goals and motivation doing this: https

[openstack-dev] [Fuel] Patch size limit

Hi, I recently noticed the influx of big patches hitting Gerrit (especially in fuel-web, but I also heard that there was a couple of big ones in library). I think that patches that have 1000 LOC are simply too big to review thoroughly and reliably. I would argue that there should be a limit to pa

Re: [openstack-dev] [QA][Infra] Continuous OpenStack quality monitoring and quality improvement plan

On 2015-12-01 13:30, Péter Hegedűs wrote: Dear OpenStack QA and Dev Team, A small group at the Software Engineering Department of the University of Szeged, Hungary is working on the quality improvements of OpenStack modules in collaboration with Ericsson Hungary. We created a WIKI page describin

Re: [openstack-dev] [Fuel] Patch size limit

On 01/12/15 12:45, Maciej Kwiek wrote: > Hi, > > I recently noticed the influx of big patches hitting Gerrit > (especially in fuel-web, but I also heard that there was a couple of > big ones in library). I think that patches that have 1000 LOC are > simply too big to review thoroughly and reliably.

Re: [openstack-dev] [neutron][L3][DVR][arp]

Some one posted a bug [1] for vlan arp responder and vlan l2population, which use the merged patch [2] for supporting the same thing in the ofagent So for DVR for vlan, I think we can continue with the bug fix above. From: huangdenghui [hdh_1...@163.com] Sent:

Re: [openstack-dev] [QA][Infra] Continuous OpenStack quality monitoring and quality improvement plan

2015.12.01. 13:45 keltezéssel, Andreas Jaeger írta: > On 2015-12-01 13:30, Péter Hegedűs wrote: >> Dear OpenStack QA and Dev Team, >> >> A small group at the Software Engineering Department of the University >> of Szeged, Hungary is working on the quality improvements of OpenStack >> modules in col

Re: [openstack-dev] Install Openstack-Ansible

On Tue, 2015-12-01 at 13:41 +0530, Sharma Swati6 wrote: > The ansible playbooks are running as of now and as per my > understanding, it is only installing the basic (main) openstack > components. > > How to install other Openstack components like Designate, Ironic, > etc. Please let me know the st

Re: [openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

Consult the API: http://docs.sqlalchemy.org/en/latest/orm/query.html#sqlalchemy.orm.query.Query.join In fact, there is already one join happening a couple lines above your change: https://github.com/openstack/neutron/blob/stable/liberty/neutron/db/l3_db.py#L800 Most likely, you will also need t

Re: [openstack-dev] [neutron][L3][DVR][arp]

Some one posted a bug [1] for vlan arp responder and vlan l2population, which use the merged patch [2] for supporting the same thing in the ofagent So for DVR for vlan, I think we can continue with the bug fix above. [1] https://bugs.launchpad.net/neutron/+bug/1413056 [2] https://review

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 1 December 2015 at 13:40, Sean Dague wrote: > > The current approach means locks block on their own, are processed in > the order they come in, but deletes aren't possible. The busy lock would > mean deletes were normal. Some extra cpu spent on waiting, and lock > order processing would be non

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

Hi, After some further discussions with Vitrage team, let me go one step back and ask a more basic question: In Vitrage, we would like to evaluate and correlate different kinds of alarms: AODH threshold alarms, event alarms, Nagios alarms, Ganglia alarms, Zabbix alarms, etc. This includes alar

Re: [openstack-dev] [swift] [oslo.messaging] [fuel] [ha] Is Swift going to support oslo.messaging?

?Is it possible to write the functionality you desire in your own middleware for Swift that lives outside of the Swift code? I would favor that approach for the following reasons: * You would have more control over code/changes so your middleware could stabilize and mature faster (don't have

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

On Tue, Dec 01 2015, AFEK, Ifat (Ifat) wrote: > In Vitrage, we would like to evaluate and correlate different kinds of alarms: > AODH threshold alarms, event alarms, Nagios alarms, Ganglia alarms, Zabbix > alarms, etc. This includes alarms on physical resources that are not part of > OpenStack, li

Re: [openstack-dev] [neutron] Purpose and documentation of the API

On Tue, Dec 01, 2015 at 07:16:00AM EST, Neil Jerram wrote: > _What is important: the API, or documented use cases?_ Both are important - however I think I understand what you are trying to tease out. > > Being theoretically inclined, I tend to assume that if an API exists, it > is the primary th

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

> -Original Message- > From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 30, 2015 20:32 > On 11/30/15 at 07:32am, Sean Dague wrote: > >On 11/24/2015 10:09 AM, John Garbutt wrote: > >> On 24 November 2015 at 15:00, Balázs Gibizer > >> wrote: > From: Andrew Laski [mailto:an

Re: [openstack-dev] [all] [glance] Proposal to add Abhishek to Glance core team

> -Original Message- > From: Nikhil Komawar [mailto:nik.koma...@gmail.com] > Sent: Tuesday, December 01, 2015 6:21 AM > To: OpenStack Development Mailing List (not for usage questions); Kekane, > Abhishek > Subject: [openstack-dev] [all] [glance] Proposal to add Abhishek to Glance > core te

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

Thanks for the quick reply. We have a few more questions, for clarification: 1. Does AODH currently support raising alarms on resources not modeled in OpenStack? For example, raising an alarm on a Switch? Or does each alarm have to relate to a resource ID (or IDs)( 2. What we feel is missing i

[openstack-dev] [nova] [ironic] Hardware composition

Hi list! There is an idea of making use of hardware composition (e.g. http://www.intel.com/content/www/us/en/architecture-and-technology/rack-scale-architecture/intel-rack-scale-architecture-resources.html) to create nodes for ironic. The current proposal is: 1. To create hardware-compositor ser

Re: [openstack-dev] [cross-project] Cross-project Liaisons

As someone who's surprised more than one team with a patch that apparently came from left field (until I pointed out the x-project spec), I'm totally for this. Michael On Tue, Dec 1, 2015 at 1:45 AM Thierry Carrez wrote: > Mike Perez wrote: > > [...] > > I would like to propose cross-project li

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On 30/11/15 22:18, Steven Hardy wrote: On Mon, Nov 30, 2015 at 12:51:53PM -0500, Ruby Loo wrote: On 30 November 2015 at 10:19, Derek Higgins wrote: Hi All, Â Â A few months tripleo switch from its devtest based CI to one that was based on instack. Before doing this w

Re: [openstack-dev] [TripleO/heat] openstack debug command

On Tue, Dec 1, 2015 at 3:39 AM, Steve Baker wrote: > I mean _here_ > > https://review.openstack.org/#/c/251587/ OK, that's great! If you want any help implementing it, I can try. //Lennart __ OpenStack Development Mailing L

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov to core reviewers of fuel-mirror

Thomas, You are right about two independent modules in the repo. That is because the former intention was to get rid of fuel-mirror (and fuel-createmirror) and perestroika and leave only packetary there. Packetary is to be developed so it is able to build not only repositories but packages as wel

Re: [openstack-dev] [Fuel] Patch size limit

Neil, just to clarify: moved/renamed files are marked as "R" so I think there may be some way to ignore such files when counting LOC. Maciej, I completely agree with you. It's pretty hard to review such big change,and takes a lot of time which could be saved by submitting smaller patches. +1 On

Re: [openstack-dev] [cross-project] Cross-project Liaisons

Excerpts from Mike Perez's message of 2015-11-30 17:30:52 -0800: > Hello all, > > Currently for cross-project specs, the author of the spec spends the time to > explain why a certain feature makes sense to be across multiple projects. This > also includes giving technical solutions for it working

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Tue, Dec 1, 2015 at 6:05 AM, Sean Dague wrote: > On 12/01/2015 01:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > > constrained by Apach

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

We do support Neutron for vCenter, but – as I mentioned a few months ago – we do not yet have a fully vetted way to deploy the multi-hypervisor use case with both KVM/QEMU and vCenter. This depends on our ability to select multiple networking options and align them to the correct hypervisors. P

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Some additional info... astroid upstream folks are going to try to push for pylint 1.4.5 that pins to astroid 1.3.8. If that happens, we could just pin pylint at 1.4.5. Ref: https://bitbucket.org/logilab/astroid/issues/275/140-and-141-fail-to-work-with-pylint-144 It sounds like we don't need to p

[openstack-dev] [Fuel] CentOS7 Merging Plan

Hello, We're almost got green BVT on custom CentOS7 ISO and it seems that it's the time to discuss the plan how this feature could be merged. This is not the only one feature that is in a queue. Unfortunately, almost any other feature will be broken if merged after CentOS7, so it was decided to m

Re: [openstack-dev] [nova][libvirt] Native AIO mode - RFC

Hello! Bumping up this thread as there've been some updates in the specs discussion [1] regarding native AIO stability & performance. Seems there's also movement in the related qemu development (see inline comments). Best regards Silvan [1] https://review.openstack.org/#/c/232514/7/specs/mitaka/ap

Re: [openstack-dev] Install Openstack-Ansible

Hi Major, Thanks for your prompt response. I will plan to create a spec for Designate. However, I just want to know if I have to implement this in openstack-ansible, or for that matter, I want to add any new component to it, are there any steps or guidelines to be followed. For example, first

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

Fox, this is one of the reasons. There are others listed in my original letter. Guys, I have prepared two patches [1] and [2] that can properly deploy the master node. I still have not got any positive feedback on the spec [3]. My intention was to wait until Centos 7 feature is merged and then to

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Hi, On Tue, Dec 1, 2015 at 3:58 PM, Dmitry Teselkin wrote: > Hello, > > We're almost got green BVT on custom CentOS7 ISO and it seems that it's > the time to discuss the plan how this feature could be merged. > > This is not the only one feature that is in a queue. Unfortunately, > almost any ot

[openstack-dev] [nova] Milestone 13.0.0.0b1 (aka. Mitaka-1) to be cut tomorrow

Hi, As you probably know, the Mitaka Release schedule for Nova defines a first milestone between Dec 1-3 [1] We had an hard dependency for translations and reno changes [2] but now everything is landed in tree. As a consequence, the release patch is provided for cutting the milestone right

Re: [openstack-dev] [puppet] weekly meeting #61

On 11/29/2015 03:35 PM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, Tuesday at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151201 We did our (short) meeting, you ca

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Tuesday 01 December 2015 08:50:14 Lance Bragstad wrote: > On Tue, Dec 1, 2015 at 6:05 AM, Sean Dague wrote: > > > > From an interop perspective, this concerns me a bit. My > > understanding is that Apache is specifically needed for > > Federation. Federation is the norm that we want for enviro

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Should we not be updating this in the requirements project? From: Paul Michali mailto:p...@michali.net>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, December 1, 2015 at 4:50 PM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [open

Re: [openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

Thanks Sean. I will check that. Meanwhile I tried this and it is working port1 = orm.aliased(models_v2.Port, name="port1") port2 = orm.aliased(models_v2.Port, name="port2") router_intf_qry = context.session.query(RouterPort.router_id).join((port1, port1.id==RouterPort.p

Re: [openstack-dev] [kolla] ValueError: No JSON object could be decoded

Hello, First of all, this is not a mailing list for debugging, I invite you sir/madam to join us on #kolla and ask questions there. Second, this doesn't help whole lot, we can get to the source of problem, but we need your help with that, so let me invite you again to our #kolla channel. Third, it

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Hi, in your plan you need to have an item about updating ISO on fuel-library CI gates. Regards, Alex On Tue, Dec 1, 2015 at 4:11 PM, Sergii Golovatiuk wrote: > Hi, > > On Tue, Dec 1, 2015 at 3:58 PM, Dmitry Teselkin > wrote: > >> Hello, >> >> We're almost got green BVT on custom CentOS7 ISO a

Re: [openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

On Tue, Dec 01, 2015 at 10:22:41AM EST, Venkata Anil wrote: > Thanks Sean. I will check that. > > Meanwhile I tried this and it is working > > port1 = orm.aliased(models_v2.Port, name="port1") > port2 = orm.aliased(models_v2.Port, name="port2") > router_intf_qry = > contex

[openstack-dev] [Fuel] Configuration management for Fuel 7.0

Hello, folks. We need any kind of CM for Fuel 7.0. Otherwise new project with 800+ nodes will be near impossible to support. Customer always wants to change something. In our opinion, there are two major approaches for CM: #1 Independent CM (Puppet master, Chef, Ansible, whatever) #2 Fuel-based

Re: [openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

On 12/01/2015 09:06 PM, Sean M. Collins wrote: On Tue, Dec 01, 2015 at 10:22:41AM EST, Venkata Anil wrote: Thanks Sean. I will check that. Meanwhile I tried this and it is working port1 = orm.aliased(models_v2.Port, name="port1") port2 = orm.aliased(models_v2.Port, name="po

[openstack-dev] [Fuel] Nominating Roman Prykhodchenko to python-fuelclient cores

Guys, I propose to promote Roman Prykhodchenko to python-fuelclient cores. He is the main contributor and maintainer of this repo. And he did a great job making changes toward OpenStack recommendations. Cores, please reply with your +1/-1. signature.asc Description: Message signed with OpenPGP

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Infra did not want to update requirements for master. I found a solution for VPN on master, namely pinning pylint and astroid in tox.ini (we already have a dependency for pylint in tox.ini). I'm thinking that for VPN on Kilo, we could cherry pick that change, rather than employ https://review.ope

Re: [openstack-dev] [cross-project] Cross-project Liaisons

On 11/30/2015 08:30 PM, Mike Perez wrote: Hello all, Currently for cross-project specs, the author of the spec spends the time to explain why a certain feature makes sense to be across multiple projects. This also includes giving technical solutions for it working with a variety of services and

Re: [openstack-dev] [Fuel] Patch size limit

Hi Maciej, thank you for bringing this up, +1, but we should discuss the limit, personally for me it's ok to review 400loc patches, if the patch covers only one bug-fix/feature implementation. So if everybody is agree, we should: 1. update contribution guide 2. create a task for *non-voting* gate

Re: [openstack-dev] [swift] [oslo.messaging] [fuel] [ha] Is Swift going to support oslo.messaging?

On 12/01/2015 08:17 AM, Richard Hawkins wrote: ​Is it possible to write the functionality you desire in your own middleware for Swift that lives outside of the Swift code? I would favor that approach for the following reasons: * You would have more control over code/changes so your middleware c

Re: [openstack-dev] [Fuel] Patch size limit

TL/DR: I think you're trying to solve the problem the wrong way. If you're trying to reduce the burden of large patches, I feel the project in question should distribute the burden of reviewing the big ones so one person's not stuck doing them all. That also means you can keep that patch in mental

Re: [openstack-dev] [cross-project] Cross-project Liaisons

On 09:29 Dec 01, Doug Hellmann wrote: > Excerpts from Mike Perez's message of 2015-11-30 17:30:52 -0800: > > Hello all, > > > > Currently for cross-project specs, the author of the spec spends the time to > > explain why a certain feature makes sense to be across multiple projects. > > This > > a

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

So my takeaway is we need each project to have something like: https://gist.github.com/harlowja/b4f0ddadbda1f92cc1e2 That could possibly exist in oslo (I just threw it together) but the idea is that a thread/greenthread would run that 'run_forever' method in that code and it would periodically

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

Hi, we have plugins for neutron (DVS and NSX). We'll finish the work on component registry . You could safely remove nova-network altogether. On Tue, Dec 1, 2015 at 5:49 PM, Sheena Gregson wrote: > We do support Neutron for vCenter, but – as I mentioned

Re: [openstack-dev] [Fuel] Nominating Roman Prykhodchenko to python-fuelclient cores

+1. No doubts. ) Aleksey Kasatkin On Tue, Dec 1, 2015 at 5:49 PM, Dmitry Pyzhov wrote: > Guys, > > I propose to promote Roman Prykhodchenko to python-fuelclient cores. He is > the main contributor and maintainer of this repo. And he did a great job > making changes toward OpenStack recommenda

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 12/01/2015 08:08 AM, Duncan Thomas wrote: > > > On 1 December 2015 at 13:40, Sean Dague > wrote: > > > The current approach means locks block on their own, are processed in > the order they come in, but deletes aren't possible. The busy lock would > mean d

Re: [openstack-dev] [cross-project] Cross-project Liaisons

Excerpts from Mike Perez's message of 2015-12-01 08:45:30 -0800: > On 09:29 Dec 01, Doug Hellmann wrote: > > Excerpts from Mike Perez's message of 2015-11-30 17:30:52 -0800: > > > Hello all, > > > > > > Currently for cross-project specs, the author of the spec spends the time > > > to > > > expla

Re: [openstack-dev] [swift] [oslo.messaging] [fuel] [ha] Is Swift going to support oslo.messaging?

> > Denis, I actually don't think that Swift needs to use oslo.messaging at > all. The middleware loads the rabbit configuration for the Notifier class > from the CONF object here: > > https://github.com/openstack/ceilometermiddleware/blob/master/ceilometermiddleware/swift.py#L112 > and that conf o

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Sean Dague wrote: On 12/01/2015 08:08 AM, Duncan Thomas wrote: On 1 December 2015 at 13:40, Sean Daguemailto:s...@dague.net>> wrote: The current approach means locks block on their own, are processed in the order they come in, but deletes aren't possible. The busy lock would m

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov to core reviewers of fuel-mirror

Vladimir, if you've been behind of this, could you please share further plans in separate email thread or (better) provide plans in README in the repo, so everyone can be aware of planned changes and can review them too? If you or someone else propose a change, please post a link here... Thanks,

  1   2   >