[openstack-dev] [cross-project] The Future of Meetings

Hey all, When we first discussed the future of cross-project meetings at the Tokyo summit, we walked out with the idea of beginning to have ad-hoc meetings instead of one big meeting with all big tent projects. Now that we have some process in place [1] (unfortunately still under review), we can

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

​hi hui,​ On Mon, May 9, 2016 at 12:41 AM, Hui Kang wrote: > Then the precheck should check for backend overlay fs on Ubuntu > trusty, rather than the kernel version. > ​i do not have more info about this in pre-check. just copy from the doc. Maybe we need re-consider

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

On Sat, May 07, 2016 at 11:02:23AM -0400, Davanum Srinivas wrote: > Dirk, Haïkel, Igor, Alan, Tony, Ghe, > > Please see brain dump here - > https://etherpad.openstack.org/p/requirements-tasks Looks good to me. > Looking at time overlap, it seems that most of you are in one time > range and

[openstack-dev] [vitrage] the section of vitrage.transformers in setup.cfg is not used

Hi folks, I notice that in the setup.cfg file there is the `vitrage.transformers` section. It seems not be used. May I propose a bug to delete it? Thank you~ vitrage.transformers = nova.instance = vitrage.entity_graph.transformer.nova_transformer.instance_transformer.InstanceTransformer

Re: [openstack-dev] [vitrage] the section of vitrage.transformers in setup.cfg is not used

Hi, You are right, it is an old configuration that we should delete. Thanks for reporting this bug, and you are welcome to contact us again with any questions or suggestions you might have :) Best regards, Ifat. From: EXT dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday,

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/07/2016 01:00 AM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Hello, Sébastien, There is OPNFV summit in Berlin Jun 20~23, 2016, as currently Kingbird is still a part of OPNFV multisite project, how about to have a design summit there, to discuss the features and design needed, and also discuss whether to move Kingbird to OpenStack community thread?

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

DIms, I would like to see how I can get involved. Looking forward to the meeting. Best Regards, Swapnil Kulkarni irc : coolsvap On Sat, May 7, 2016 at 8:32 PM, Davanum Srinivas wrote: > Dirk, Haïkel, Igor, Alan, Tony, Ghe, > > Please see brain dump here - >

Re: [openstack-dev] [all] cross-project deployment tool meeting

Hi, I have created a doodle so we can find a slot for our first meeting. Please respond until this Friday so I can try an secure a spot in the cross project irc room. https://doodle.com/poll/7wrmtpc4ffcwi428 Cheers, Jan Sent from my mobile > On 06 May 2016, at 22:13, Emilien Macchi

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

On 07/05/16 17:02, Davanum Srinivas wrote: Dirk, Haïkel, Igor, Alan, Tony, Ghe, Please see brain dump here - https://etherpad.openstack.org/p/requirements-tasks Nice starting point. Reading through all of it right now. Looking at time overlap, it seems that most of you are in one time range

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Thanks for the clarification :). Not sure if I'll be in OSCON but who knows :). Take care. On Monday, 9 May 2016, Zhipeng Huang wrote: > Hi Sebastien, > > Totally understand your reasoning here, however there are some > misunderstanding :P I'm not familiar with Smaug,

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

I've replied on the etherpad. -Rob On 8 May 2016 at 03:02, Davanum Srinivas wrote: > Dirk, Haïkel, Igor, Alan, Tony, Ghe, > > Please see brain dump here - > https://etherpad.openstack.org/p/requirements-tasks > > Looking at time overlap, it seems that most of you are in one

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

The reason Kolla works in the gate is it is using the btrfs graph driver. The AUFS graph driver in the 14.04 kernel is busted. This is what the precheck is meant to check. Apparently it needs to also check the graph driver type in use. Regards -steve From: Jeffrey Zhang

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

Fox, Kevin M wrote: I think part of the problem with the whole Swift situation is that it does something most other OpenStack projects don't do. Its both a control plane and a data plane. [...] Yes, it is certainly part of the Go rationale (I wouldn't say "problem"). Swift implementing a

Re: [openstack-dev] [tc] License for specs repo

Ben Swartzlander wrote: On 05/05/2016 04:01 PM, Davanum Srinivas wrote: Ben, Have you seen this yet? http://lists.openstack.org/pipermail/legal-discuss/2014-March/000201.html

Re: [openstack-dev] [tc] supporting Go

On 05/08/2016 03:37 PM, Rayson Ho wrote: > On Sun, May 8, 2016 at 5:16 AM, Thomas Goirand > wrote: >> I've heard that upstream for >> Golang was working on implementing shared libs, but I have no idea what >> the status is. Does anyone know? > > > In

[openstack-dev] [HA] About next HA Team meeting (VoIP)

Hi All, In today's ( 9th May 2016) meeting we agree to skip the next IRC meeting (which is 16th May 2016) in favour of a gotomeeting VoIP on 18th May 2016 (Wednesday). Today's meeting logs and summary can be found here. http://eavesdrop.openstack.org/meetings/ha/2016/ha.2016-05-09-08.04.html

[openstack-dev] [ironic] it's official: ironic-discoverd is EOL now

Hey, you didn't know it wasn't EOL all this time? ;) Well, now it is. The last PyPI release was ironic-discoverd 1.1.1 (it's not tagged in git due to technical reasons), and with Kilo going EOL we will have no more releases. Both stable/1.0 and stable/1.1 branches are gone now as well. I

Re: [openstack-dev] [kolla] deploy kolla on ppc64

This is fixed on master branch. please try and test it.[0][1] [0] https://git.openstack.org/cgit/openstack/kolla/commit/?id=070bf258357c85a7b4411dc97f75df7d19e9792c [1] https://bugs.launchpad.net/kolla/+bug/1573544 On Fri, Apr 22, 2016 at 7:15 PM, Jeffrey Zhang wrote:

[openstack-dev] [vitrage] Vitrage IRC meetings - notice the change of time

Hi, Vitrage meeting this week will be SKIPPED, as many Vitrage developers won't be able to attend. Starting from next week, the meeting time and channel will be changed to: Wednesday at 8:00 UTC, #openstack-meeting-4 See you next Week, Ifat.

Re: [openstack-dev] [tc] supporting Go

On 08/05/2016 10:21, Thomas Goirand wrote: > On 05/04/2016 01:29 AM, Hayes, Graham wrote: >> On 03/05/2016 17:03, John Dickinson wrote: >>> TC, >>> >>> In reference to >>> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and >>> Thierry's reply, I'm currently drafting a TC

Re: [openstack-dev] [all][i18n] [config] translation import: No more pot files in git trees

We had a group presentation in the upstream development track on Monday where we talked about the new work in Oslo. My section where I talked about the config generator and other documentation tools is at the end, starting around 39:00. https://www.openstack.org/videos/video/live-from-oslo

Re: [openstack-dev] [HA] About next HA Team meeting (VoIP)

Sam P wrote: > Hi All, > > In today's ( 9th May 2016) meeting we agree to skip the next IRC > meeting (which is 16th May 2016) in favour of a gotomeeting VoIP on > 18th May 2016 (Wednesday). > Today's meeting logs and summary can be found here. >

[openstack-dev] [nova] api-ref sprint today & wed

There is a lot of work to be done to get the api-ref into a final state. Review / fix existing patches - https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open shows patches not yet merged. Please review them, and if there are issues feel free to fix them. Help create

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [vitrage] the section of vitrage.transformersin setup.cfg is not used

Hi, OK, i will fix it. Thank you for your response. :) BR, dwj "Afek, Ifat (Nokia - IL)" 2016-05-09 14:47 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for

[openstack-dev] [TripleO] supporting OVS-DPDK and SRIOV

Hello Folks, We have been working on Triple-O and NFV client for some time now. We would like to work and get this feature (ovs-dpdk and sr-iov) rolled out into tripleo installer. We look for support and suggestions for the spec files - ovs-dpdk - https://review.openstack.org/313871 sr-iov -

[openstack-dev] [horizon] Feature Freeze one week earlier in Newton.

Hi all, As requested we’ll be moving our feature freeze in Newton to R-6 (http://releases.openstack.org/newton/schedule.html). This is one week earlier than in previous cycles, to give plugins a chance to finalise their own features for Newton without risk of breaking changes. The FFE process

[openstack-dev] [Heat] Summit recap

Hi all, Here are some of my thoughts on the Austin summit sessions. Don't hesitate to ask questions or fix my misunderstanding. I'll try to keep it short, please also refer to the etherpads for more details (sometimes :)): https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Heat

Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016 at 4:57 AM, Thomas Goirand wrote: > > Do you know if that's already in use in some distros? Since the Go toolchain is pretty self-contained, most people just follow the official instructions to get it installed... by a one-step: # tar -C /usr/local -xzf

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

Hi, Tomorrow, we'll have our weekly meeting, I added a few topics: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160510 Feel free to add more and also submit any outstanding bug or patch. Thanks, On Tue, May 3, 2016 at 7:58 AM, Emilien Macchi wrote: >

Re: [openstack-dev] [Heat] Summit recap

On Mon, May 09 2016, Thomas Herve wrote: […] > Using DLM > > > We managed to not talk about ZooKeeper too much :). We want to remove > the database locks that we have and use tooz instead. The key is to > provide a nice upgrade path, so starting with the locks use for >

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

Yeah, the data plane api is much more complicated then the control plane. I agree the control api would be a pretty thin api. But just because its thin doesnt mean its not increadibly useful. :) Also, just because the community isnt screaming yet doesnt mean its not really broken. We tend to

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Hi Amrith, We've had a lot of 'new' tests enabled for py34 in the last week - from your results you can see it's running 6x the number of tests (although it's taking 8.5x as long). It looks like python3 isn't as fast as python2.7? If so, we may have to do something wrt the 'dangling-mock'

[openstack-dev] [release][oslo] oslo.versionedobjects 1.9.0 release (newton)

We are gleeful to announce the release of: oslo.versionedobjects 1.9.0: Oslo Versioned Objects library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.versionedobjects With package available at:

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

So I'm able to run the py34 tests in about 10s if I run the dangling mock detector with a depth of 0 or 1. I'd also like to figure out how we can get the py34 tests to show progress like py27 does. If a test fails, it is much harder to debug as it is now ... -amrith From: Peter Stachowski

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

On 5/8/16, 7:55 AM, "Monty Taylor" wrote: >On 05/08/2016 03:45 AM, Steve Kowalik wrote: >> On 08/05/16 08:11, lương hữu tuấn wrote: >>> Hi, >>> >>> @Robert: I was successful to update the kernel without change the >>>image. >> >> But that was Robert's point entirely.

[openstack-dev] Ansible inventory - Would you need another inventory system for your openstack cloud and how would you like it to be?

Hello everyone, I am using ansible for some time now, and I think the current default Ansible inventory system is lacking a few features, at least when working on an OpenStack cloud - whether it's for its deployment, its support or its usage. I'm thinking of developing a new inventory, based on

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

On Sun, 8 May 2016 at 15:58 Monty Taylor wrote: > On 05/08/2016 03:45 AM, Steve Kowalik wrote: > > On 08/05/16 08:11, lương hữu tuấn wrote: > >> Hi, > >> > >> @Robert: I was successful to update the kernel without change the image. > > > > But that was Robert's point

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

FYI, I filed a bug about this issue https://bugs.launchpad.net/kolla/+bug/1579583 - Hui On Mon, May 9, 2016 at 10:42 AM, Steven Dake (stdake) wrote: > > > On 5/8/16, 7:55 AM, "Monty Taylor" wrote: > >>On 05/08/2016 03:45 AM, Steve Kowalik wrote: >>> On

[openstack-dev] [api] API-WG summit session recap

hello all, We had a great session for the API working group in Austin, and I wanted to give a brief recap and extend a thank you to all who attended. There were about 20-30 people in attendance for the double session fishbowl that took place on monday. This turnout was one of the larger we

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Tim, I agree – creating a datasource from Vitrage to Congress is the first step, and we should have some concrete use case in mind to help guide this process. The most straightforward use case I would suggest is when there is a problem on an instance that is caused by some problem on the

[openstack-dev] [Neutron] FYI: Changed my irc nick to andreas_s (formerly scheuran)

-- - Andreas (IRC: andreas_s) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [release][oslo] futurist 0.14.0 release (newton)

We are eager to announce the release of: futurist 0.14.0: Useful additions to futures, from the future. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/futurist With package available at:

[openstack-dev] [release][oslo] mox3 0.15.0 release (newton)

We are chuffed to announce the release of: mox3 0.15.0: Mock object framework for Python This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/mox3 With package available at: https://pypi.python.org/pypi/mox3 Please

[openstack-dev] [release][oslo] oslo.concurrency 3.8.0 release (newton)

We are chuffed to announce the release of: oslo.concurrency 3.8.0: Oslo Concurrency library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency With package available at:

[openstack-dev] [release][oslo] oslo.context 2.3.0 release (newton)

We are gleeful to announce the release of: oslo.context 2.3.0: Oslo Context library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.context With package available at: https://pypi.python.org/pypi/oslo.context

[openstack-dev] [release][oslo] oslo.log 3.6.0 release (newton)

We are pleased to announce the release of: oslo.log 3.6.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report

[openstack-dev] [release][oslo] oslo.cache 1.7.0 release (newton)

We are tickled pink to announce the release of: oslo.cache 1.7.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at:

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Cathy, Cathy Zhang: I will tentatively set the meeting time to UTC 1700 ~ UTC 1800 Tuesday. Hope this time is good for all people who have interest and like to contribute to this work. We plan to start the first meeting on May 17. I would be happy to participate, but I'm unlikely to be

Re: [openstack-dev] Ansible inventory - Would you need another inventory system for your openstack cloud and how would you like it to be?

On 05/09/2016 09:27 AM, Jean-Philippe Evrard wrote: Hello everyone, I am using ansible for some time now, and I think the current default Ansible inventory system is lacking a few features, at least when working on an OpenStack cloud - whether it's for its deployment, its support or its usage.

[openstack-dev] [release][oslo] debtcollector 1.4.0 release (newton)

We are delighted to announce the release of: debtcollector 1.4.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. This release is part of the newton release series. With source available at:

[openstack-dev] [release][oslo] oslo.policy 1.7.0 release (newton)

We are glad to announce the release of: oslo.policy 1.7.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy Please

[openstack-dev] [release][oslo] oslo.middleware 3.9.0 release (newton)

We are thrilled to announce the release of: oslo.middleware 3.9.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at:

[openstack-dev] [release][oslo] oslo.privsep 1.6.0 release (newton)

We are jubilant to announce the release of: oslo.privsep 1.6.0: OpenStack library for privilege separation This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.privsep With package available at:

[openstack-dev] [release][oslo] oslo.rootwrap 4.2.0 release (newton)

We are delighted to announce the release of: oslo.rootwrap 4.2.0: Oslo Rootwrap This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.rootwrap With package available at: https://pypi.python.org/pypi/oslo.rootwrap

[openstack-dev] [release][oslo] oslotest 2.5.0 release (newton)

We are satisfied to announce the release of: oslotest 2.5.0: Oslo test framework This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslotest With package available at: https://pypi.python.org/pypi/oslotest Please

[openstack-dev] [release][oslo] oslo.utils 3.9.0 release (newton)

We are glad to announce the release of: oslo.utils 3.9.0: Oslo Utility library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.utils With package available at: https://pypi.python.org/pypi/oslo.utils Please

[openstack-dev] [release][oslo] stevedore 1.13.0 release (newton)

We are delighted to announce the release of: stevedore 1.13.0: Manage dynamic plugins for Python applications This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/stevedore With package available at:

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Thanks - let me try and get the code cleaned up and rebased. One area that I could use your insight on is the interface to networking-ovn and how it should look. Regards John From: Ryan Moats > Date: Sunday, May 8, 2016 at 8:32 PM To: John

[openstack-dev] [release][oslo] oslo.reports 1.8.0 release (newton)

We are eager to announce the release of: oslo.reports 1.8.0: oslo.reports library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.reports With package available at: https://pypi.python.org/pypi/oslo.reports

[openstack-dev] [release][oslo] tooz 1.35.0 release (newton)

We are eager to announce the release of: tooz 1.35.0: Coordination library for distributed systems. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/tooz With package available at: https://pypi.python.org/pypi/tooz

[openstack-dev] [release][oslo] oslo.vmware 2.6.0 release (newton)

We are happy to announce the release of: oslo.vmware 2.6.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware Please

[openstack-dev] [release][oslo] oslo.service 1.9.0 release (newton)

We are pleased to announce the release of: oslo.service 1.9.0: oslo.service library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.service With package available at: https://pypi.python.org/pypi/oslo.service

Re: [openstack-dev] [tc] supporting Go

On Mon, 9 May 2016 09:06:02 -0400 Rayson Ho wrote: > Since the Go toolchain is pretty self-contained, most people just follow > the official instructions to get it installed... by a one-step: > > # tar -C /usr/local -xzf go$VERSION.$OS-$ARCH.tar.gz I'm pretty certain the

[openstack-dev] [release][oslo] oslo.messaging 5.0.0 release (newton)

We are delighted to announce the release of: oslo.messaging 5.0.0: Oslo Messaging API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging With package available at:

Re: [openstack-dev] [api] API-WG summit session recap

> On May 9, 2016, at 10:12 AM, michael mccune wrote: > > Promoting the guidelines > > > The heart of the API-WG has always been the guidelines that are produced, we > had a nice discussion about how we can increase the awareness and usage of > the

[openstack-dev] [release][oslo] taskflow 1.31.0 release (newton)

We are chuffed to announce the release of: taskflow 1.31.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Dmitry Tantsur wrote: On 05/07/2016 01:00 AM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help

[openstack-dev] config options: current state (R-21)

We're close to have all options moved to "nova/conf/". At the bottom is a list of the remaining options and their open reviews. The documentation of the options in "nova/conf/" is done for ~ 150 options. Which means ~ 450 are missing. This means there are still around 80 changes necessary to

[openstack-dev] [kolla] OpenPower support

all, We have a Mitaka/Kolla control plane deployed on x86 in our lab with an OpenPower (Habanero system from Tyan) compute node attached to it and it works like a charm :-). Under SoftLayer we also have a Mitaka/Kolla control plane deployed on x86 and we are trying to attach a Power8 system

Re: [openstack-dev] [kolla] OpenPower support

Franck, It's coming from Nova: http://codesearch.openstack.org/?q=ServiceTooOld=nope==nova Check the nova configuration files for a rpc version mismatch -- Dims On Mon, May 9, 2016 at 12:17 PM, Franck Barillaud wrote: > all, > > We have a Mitaka/Kolla control plane

Re: [openstack-dev] [heat]Provides different stack quota to tenant

Excerpts from Sylvernass Arthas's message of 2016-05-08 05:33:13 -0700: > Hi, guys > > Now, all tenant share the public config "max_stacks_per_tenant" which > decides maximum number of stacks any one tenant may have active at one time, > the default value is 1000. > Should heat provides

[openstack-dev] [TripleO][CI] Elastic recheck bugs

Hi, all I'd like to enable elastic recheck on TripleO CI and have submitted patches for refreshing the tracked logs [1] (please review) and for timeout case [2]. But according to Derek's comment behind the timeout issue could be multiple issues and bugs, so I'd like to clarify - what are criteria

Re: [openstack-dev] [kolla] CentOS binary and source gate failed due to the rabbitmq

The ubuntu gate deploy failed too; that is awkward. http://logs.openstack.org/05/314205/1/check/gate-kolla-dsvm-deploy-ubuntu-source/766ee43/console.html#_2016-05-09_16_58_39_411 - Hui On Mon, May 9, 2016 at 1:48 AM, Jeffrey Zhang wrote: > I deploy the Kolla by using

Re: [openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

Assaf, thanks for driving this session. As a newbie to the design sessions, I think presenting a brief "context" up-front is helpful. IMO the key word here is "brief" (5 min or less for example) and furthermore should not open the floor for digression given the short time-frame we have per

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

Hi neutrinos, Just a reminder that from this week, we'll resume the usual schedule for the weekly team meeting. Many thanks, Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

On Sun, May 08, 2016 at 09:55:58AM -0500, Monty Taylor wrote: > On 05/08/2016 03:45 AM, Steve Kowalik wrote: > >On 08/05/16 08:11, lương hữu tuấn wrote: > >>Hi, > >> > >>@Robert: I was successful to update the kernel without change the image. > > > >But that was Robert's point entirely. Installing

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

Paul, There is no request from the Kolla community to churn the images. I don't see that as adding any value. We can just document the reality of the situation, which is only BTRFS works well as a graph driver with 14.04. Regards -steve On 5/9/16, 10:48 AM, "Paul Belanger"

Re: [openstack-dev] [tc] supporting Go

I think you'll find that being able to embed a higher performance language inside python will be much easier to do for optimizing a function or two rather then deal with having a separate server have to be created, authentication be added between the two, and marshalling/unmarshalling the data

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Hi If we choose to use bifrost to deploy ironic standalone I think combining kevins previous suggestion of modifying the bifrost install playbook with Steve Dake's suggestion of creating a series of supervisord configs for running each of the service is a reasonable approch. I am currently

Re: [openstack-dev] [tc] supporting Go

On 09/05/2016 19:09, Fox, Kevin M wrote: > I think you'll find that being able to embed a higher performance language > inside python will be much easier to do for optimizing a function or two > rather then deal with having a separate server have to be created, > authentication be added between

Re: [openstack-dev] [tc] supporting Go

Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > On Mon, 9 May 2016 09:06:02 -0400 > Rayson Ho wrote: > > > Since the Go toolchain is pretty self-contained, most people just follow > > the official instructions to get it installed... by a one-step: > >

Re: [openstack-dev] [TripleO][CI] Elastic recheck bugs

Sorry, missed the mentioned patches: [1] Refresh log files for tripleo project: https://review.openstack.org/#/c/312985/ [2] Add bug for TripleO timeouts: https://review.openstack.org/#/c/313038/ On Mon, May 9, 2016 at 8:22 PM, Sagi Shnaidman wrote: > Hi, all > > I'd like

[openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

I just read http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html and, unless I missed something, it seems to be describing something that is not multi-tenant. I am focused on FQDNs for Neutron Ports. For those, only the "hostname" part (the first label, in official DNS

Re: [openstack-dev] [tc] supporting Go

On 9 May 2016, at 11:14, Hayes, Graham wrote: > On 09/05/2016 19:09, Fox, Kevin M wrote: >> I think you'll find that being able to embed a higher performance language >> inside python will be much easier to do for optimizing a function or two >> rather then deal with having a separate server

Re: [openstack-dev] [ironic] API docs now publishing from our tree

Works for me. The api-ref stuff is much easier to maintain, review, and the resulting docs are infinitely more usable for developers. I'm already working on getting api-ref up to date; the current docs there are sorely out of date and wrong. I'd like to land these patches quickly and iterate on

Re: [openstack-dev] [tc] supporting Go

Ah. ok. Yeah, using Go for that use case wouldn't be too bad then. Thanks, Kevin From: Hayes, Graham [graham.ha...@hpe.com] Sent: Monday, May 09, 2016 11:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 01:15 PM, Clint Byrum wrote: > Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: >> On Mon, 9 May 2016 09:06:02 -0400 >> Rayson Ho wrote: >> >>> Since the Go toolchain is pretty self-contained, most people just follow >>> the official

Re: [openstack-dev] [tc] supporting Go

On 05/09/2016 02:15 PM, Clint Byrum wrote: Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: On Mon, 9 May 2016 09:06:02 -0400 Rayson Ho wrote: Since the Go toolchain is pretty self-contained, most people just follow the official instructions to get it

Re: [openstack-dev] [tc] supporting Go

On 09/05/2016 19:39, Ben Swartzlander wrote: > On 05/09/2016 02:15 PM, Clint Byrum wrote: >> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: >>> On Mon, 9 May 2016 09:06:02 -0400 >>> Rayson Ho wrote: >>> Since the Go toolchain is pretty

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 09/05/2016 19:21, Mike Spreitzer wrote: > I just read > http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.htmland, > unless > I missed something, it seems to be describing something that is not > multi-tenant. I am focused on FQDNs for Neutron Ports. For those, only > the

Re: [openstack-dev] Ansible inventory - Would you need another inventory system for your openstack cloud and how would you like it to be?

On 9 May 2016 at 15:27, Jean-Philippe Evrard wrote: > I am using ansible for some time now, and I think the current default > Ansible inventory system is lacking a few features, at least when working > on an OpenStack cloud - whether it's for its deployment, its support

[openstack-dev] [Tacker][NFV] Tacker - Weekly IRC Meeting - new time

Tackers, We are resuming Tacker IRC weekly meeting at a new time slot (an hour earlier) and at a new channel. When: Tuesday 1600 UTC Where: #openstack-meeting Duration: 1hr Here is the agenda for tomorrow's meeting,

Re: [openstack-dev] [tc] supporting Go

Excerpts from Tim Simmons's message of 2016-05-09 18:29:30 +: > > The point here though, is that the versions of Python that OpenStack > > has traditionally supported have been directly tied to what the Linux > > distributions carry in their repositories (case in point, Python 2.6 > > was

Re: [openstack-dev] [tc] supporting Go

On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > This is not a "Go seems cool - lets go try that" decision from us - we > know we have a performance problem with one of our components, and we > have come to the conclusion that Go (or something like it) is the > solution.

[openstack-dev] [designate] Summit Recap

I started writing this on a plane on the way home from Austin, TX where we just finished up the Newton design summit for OpenStack, and finished it a few days later - please excuse any weirdness in syntax or flow :) 6 Months On: Where are we = One of the things I did

[openstack-dev] [release][stable][winstackers] os-win 0.4.2 release (mitaka)

We are overjoyed to announce the release of: os-win 0.4.2: Windows / Hyper-V library for OpenStack projects. This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/os-win With package available at:

Re: [openstack-dev] [tc] supporting Go

Go static linking/portability is something of a misnomer too. Last I looked Go only statically linked Go code, so any system libraries used still were dynamic. So it gets you somewhat to the use case of container level portability but not all the way unless you can do literally everything in

Re: [openstack-dev] [TripleO][CI] Elastic recheck bugs

On Mon, May 9, 2016, at 10:22 AM, Sagi Shnaidman wrote: > Hi, all > > I'd like to enable elastic recheck on TripleO CI and have submitted > patches > for refreshing the tracked logs [1] (please review) and for timeout case > [2]. > But according to Derek's comment behind the timeout issue could

[openstack-dev] [release][sahara] sahara-tests 0.2.0 release

We are glad to announce the release of: sahara-tests 0.2.0: Sahara tests With source available at: https://git.openstack.org/cgit/openstack/sahara-tests For more details, please see below. 0.2.0 ^ Discovery of data sources with relative paths is now fixed. Fix default resource

  1   2   >