Re: [openstack-dev] [oslo][mistral] Mistral expressions package

Hi, I’m not too happy about the idea of creating one more subproject within Mistral. I don’t even see now what else this new library project managed by Mistral team will contain besides this expression utils module. I’m also not sure about its name. We already have mistral-lib which was

Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

Dougal, I forgot to mention that explicitly but, yes, #1 is needed only not to break the sequence of migrations. We can manually fix the migration number in #2 just for stable/pike but I somewhat don’t like the idea of having different migration numbers in different branches. It’s a good news

Re: [openstack-dev] [telemetry] ceilometer-notification restart with no consumers on ceilometer-pipe

Hi, tianqing I saw your pipline.yaml and found the configurations I think you should remove the excluded symbol because it would filter all cpu*, disk*, memeory*, network* sources. Cheers, Hanxi Liu irc(lhx_) On Wed, Oct 18, 2017 at 11:17 AM, 李田清 wrote: > Hello, >

Re: [openstack-dev] Unified Limits work stalled - next steps, need for new leadership

HI Sean, I think that we(Lance and I) from Huawei are willing to take over and continue this feature. I hope that we can get some information and suggestion from you. Such as: what’s the progress now? What should I do now? IMHO, the main work now is to update and polish these two specs[1],

[openstack-dev] [telemetry] ceilometer-notification restart with no consumers on ceilometer-pipe

Hello, I am testing ceilometer workload partition. And find that if we restart agent notification, the ceilometer-pip* queue will not have consumers any more. Does anyone know this? The pipeline.yaml is here http://paste.openstack.org/show/623909/ And i also find the

[openstack-dev] [acceleration] Cancellation of Cyborg Team Meeting this week

Hi team, Since I'm traveling to OpenStack Day Nordic, I would have to cancel our team meeting this week, but if you have any items to discuss plz feel free to put them on our irc channel #openstack-cyborg __ OpenStack

Re: [openstack-dev] [oslo][blazar][heat] Remove oslotest.mockpatch

Zane, Thanks for the update, we can clean up this module from Oslo side. 2017-10-18 2:10 GMT+08:00 Zane Bitter : > On 16/10/17 09:53, ChangBo Guo wrote: > >> The oslotest.mockpatch has been deprecated in favor of native fixtures in >> [1] , need remove its usage in

[openstack-dev] OpenStack Dev Digest is Open to Volunteers!

Hey all, The OpenStack Dev Digest has been receiving great feedback from various members of our community as being a good resource to get important summaries of threads they might be interested in responding back to and/or being informed on. Currently the Dev Digest gets posted by me on the

Re: [openstack-dev] IBM z/VM CI asks for reporting permission to Nova changes

Hi Andreas Exactly, we found the issue yesterday and will fix it soon, really appreciate your info and help~ Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82451493 Address:

Re: [openstack-dev] [nova][out-of-tree drivers] Breaking change to ComputeDriver.spawn and friends

Thanks for sharing this info, I already keep an eye on this change and understand the reason, so if I understand this correctly, out of tree driver only need 'allocations' to be added for spawn and rebuild function and up to the driver to use it, correct? Best Regards! Kevin (Chen) Ji 纪 晨

Re: [openstack-dev] [masakari]oslo.context 2.19.1 is currently blocked

Hello Ben, On 2017/10/18 0:05, Ben Nemec wrote: Can you add masakari to https://bugs.launchpad.net/oslo.context/+bug/1721432 so we don't miss it in the process of fixing this problem?  At some point we will be releasing a new oslo.context and we need to make sure we get all the broken

[openstack-dev] [all][docs][contributor-guide] Onboarding Contributor Content Help Wanted

Hey all, tldr; There's an effort to collect general documentation for new OpenStack contributors. The content that qualifies as general so far is Git, IRC, account setup. We are looking for help to write new content at the git repo openstack/contributor-guide. No that subject tag is not a

Re: [openstack-dev] [forum] Schedule Is Available

On 16:43 Oct 16, Mike Perez wrote: > Hey all, > > Thanks to Jimmy McArthur for getting the schedule posted so quickly! Here's > the > schedule posted on the Summit site filtering by forum related sessions: > >

[openstack-dev] [nova][out-of-tree drivers] Breaking change to ComputeDriver.spawn and friends

Out-of-tree virt driver maintainers, please keep an eye on [1], which will force you to update the signature of your spawn and rebuild overrides. See the commit message for the whys and wherefores, and let me know if you have any questions. [1] https://review.openstack.org/511879 Thanks, Eric

Re: [openstack-dev] [qa][infra][devstack] Changes to devstack-core for zuul v3 migration

On Tue, Oct 10, 2017 at 04:34:29PM -0400, Sean Dague wrote: > On 10/10/2017 04:22 PM, Dean Troyer wrote: > > On Tue, Oct 10, 2017 at 1:15 PM, Andrea Frittoli > > wrote: > >> - we will treat +1 from infra-core members on devstack changes in the > >> ansible bits as +2 >

[openstack-dev] [designate] Skipping this weeks meeting

Hi, I have a conflict this week with a different meeting. I would suggest we skip this week unless there is someone who can chair it in my absence? Thanks, Graham signature.asc Description: OpenPGP digital signature __

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Excerpts from Zane Bitter's message of 2017-10-16 18:10:20 -0400: > On 14/10/17 11:47, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2017-10-13 15:21:14 -0400: > >> Replying to myself here, to avoid singling anyone in particular out. I > >> want to rephrase the question, because

[openstack-dev] [tc] [all] TC Report 42

( with clicky things: https://anticdent.org/tc-report-42.html ) we can't always hold the belief which we believe 5 years ago After [last week's report](https://anticdent.org/tc-report-41.html) I got into an [interesting

Re: [openstack-dev] [oslo][blazar][heat] Remove oslotest.mockpatch

On 16/10/17 09:53, ChangBo Guo wrote: The oslotest.mockpatch has been deprecated in favor of native fixtures in [1] , need remove its usage in python-heatclient, python-blazarclient [2][3], Heat/Blazar team please help review, then we'll merge [4] [1]https://review.openstack.org/#/c/245199/

Re: [openstack-dev] [docs][ptls][all] documentation retention policy changes

On Thu, 28 Sep 2017 12:51:18 -0400 Doug Hellmann wrote: > At the Queens PTG in Denver the documentation team members present > discussed a new retention policy for content published to > docs.openstack.org. I have a spec up for review to document that > policy and the

Re: [openstack-dev] [ironic] ironic and traits

Hi! Answering to both Eric and John inline. On 10/16/2017 07:26 PM, John Garbutt wrote: > On 16 October 2017 at 17:55, Eric Fried > wrote: > > * Adding references to the specs: ironic side [1]; nova side [2] (which > just merged). > >

[openstack-dev] [release][ptl] Releases repo frozen

Just a heads up that the releases repo is frozen while we work through some zuul v3 migration issues. Jobs are passing, but some of the important post-release processing that needs to happen will require a little more tinkering to get right. Feel free to propose release patches, but just know

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

So, my $0.02. A supported/recent version of a tool to install an unsupported version of a software is not a bad thing. OpenStack has a bad reputation (somewhat deservedly) for being hard to upgrade. This has mostly gotten better over time but there are still a large number of older,

Re: [openstack-dev] [docs] Evidence of Success

Thanks for your feedback, everybody. I made some more edits to the document and tried to address the remaining comments left in the etherpad. I think the current revision of the doc provides enough details on the metrics and goals, so it should be ready to be added to

Re: [openstack-dev] [forum] Schedule Is Available

Amrith Kumar wrote: Mike, Thanks for sending this out. Long lines in descriptions of many events are not being wrapped, take Rochelle's session "Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop"at 3:30pm on Wednesday. Any chance the descriptions could be wrapped? This is now

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-17 at 11:46 +, milanisko k wrote: > > How about the shared container? Wouldn't it be better not have to > rely on t-h-t especially if we're "scheduling" (and probably > configuring) the services as a single logical entity? The containers architecture for Pike and Queens is

Re: [openstack-dev] [masakari]oslo.context 2.19.1 is currently blocked

Can you add masakari to https://bugs.launchpad.net/oslo.context/+bug/1721432 so we don't miss it in the process of fixing this problem? At some point we will be releasing a new oslo.context and we need to make sure we get all the broken projects fixed before then. Thanks. -Ben On

[openstack-dev] [kolla-kubernetes] example of containerize neutron ML2 drivers

Hi, At PTG, there were discussion around prototyping per-vendor neutron drivers (for example ML2 drivers) within containerized neutron service. Is there any design decision made? If so, please kindly share it as a guideline for implementing vender-specific neutron drivers.Thanks a lot! Regards,

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

To be as cool as nova, we'll find nicknames until then. We can probably start with Kevin "Destroy of Clouds" Carter. On 17 October 2017 at 15:28, Jean-Philippe Evrard wrote: > Hello, > > I'd be happy to have a room for OpenStack-Ansible. > > I'll be there, and probably

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Neutron - Miguel Lavalle - mig...@mlavalle.com On Mon, Oct 16, 2017 at 9:39 PM, Jeffrey Zhang wrote: > I am the speaker. Michal couldn't be Sydney this summit. > > On Tue, Oct 17, 2017 at 1:05 AM, Kendall Nelson > wrote: > >> Added Kolla to my

Re: [openstack-dev] [ptls] Sydney Forum Project Onboarding Rooms

Hello, I'd be happy to have a room for OpenStack-Ansible. I'll be there, and probably more ppl, like Kevin Carter(cloudnull) and Amy Marrich(spotz). Thanks! On 17 October 2017 at 03:39, Jeffrey Zhang wrote: > I am the speaker. Michal couldn't be Sydney this summit. >

Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

On 17 October 2017 at 09:19, Renat Akhmerov wrote: > Hi, > > We have two patches in Mistral that we need to back port to stable/pike. > However, they are against of stable branch management policy because they > slightly change the DB schema. The patches are the

Re: [openstack-dev] IBM z/VM CI asks for reporting permission to Nova changes

Hi Laurene, at the moment the z/VM CI is posting a +1 even though the job failed. That’s because in zuul layout.yaml the job is probably set to "voting: false.” You can easily fix this by setting it to “true”. For example see https://review.openstack.org/#/c/512190/ Regards, --- Andreas

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

út 17. 10. 2017 v 13:06 odesílatel Dan Prince napsal: > On Tue, 2017-10-17 at 10:06 +, milanisko k wrote: > > > > Does it mean dnsmasq was run from a stand-alone container? > > Yes. There are separate containers for the ironic-inspector and > dnsmasq. > > > > > Could you

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-17 at 10:06 +, milanisko k wrote: > > Does it mean dnsmasq was run from a stand-alone container? Yes. There are separate containers for the ironic-inspector and dnsmasq. > > Could you please point me (in the patch probably) to the spot where > we configure inspector

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Hi Julia Yes, you are right on your assumptions here. The missing feature here, is the ability of Ironic to provide a mechanism to append standard kernel arguments, when not netbooting. Having a way to append default parameters to bootloader would be very useful and avoid the need of manual hacks,

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

Hi Dan! thanks for the testing! I've got couple of questions... po 16. 10. 2017 v 20:04 odesílatel Dan Prince napsal: > On Wed, 2017-10-04 at 15:10 +0200, Dmitry Tantsur wrote: > > (top-posting, as it is not a direct response to a specific line) > > > > This is your

[openstack-dev] [neutron][classifier] CCF Meeting

Hi everyone. Reminder that the Common Classification Framework meeting is at 14:00 UTC. The Agenda can be found here: https://wiki.openstack.org/wiki/Neutron/CommonClassificationFramework#All_Meetings.27_Agendas Regards. David.

[openstack-dev] [masakari]oslo.context 2.19.1 is currently blocked

Hello Masakari contributors, I submitted a patch which fixes masakari UT codes according to oslo.context 2.19.1.[1] Because oslo.context 2.19.1 adds 'project' key in context's to_dict function.[2] But, I realized that the latest global-requirement blocks oslo.context 2.19.1.[3] So I abandoned

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On 10/17/17 12:50 AM, Michał Jastrzębski wrote: > So my 0.02$ > > Problem with handling Newton goes beyond deployment tools. Yes, it's > popular to use, but if our dependencies (openstack services > themselves) are unmaintained, so should we. If we say "we support > Newton" in deployment tools,

[openstack-dev] [stable][mistral] Asking for stable branch policy exception

Hi, We have two patches in Mistral that we need to back port to stable/pike. However, they are against of stable branch management policy because they slightly change the DB schema. The patches are the following: 1. https://review.openstack.org/#/c/512528/ 2.

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Emilien Macchi wrote: > > Thierry, when I read your comment on Gerrit I understand you prefer to > amend the existing policy and just make a note for installers (which > is I think the option #2 that I proposed). Can you please confirm > that? > So far I see option #1 has large consensus here,

[openstack-dev] Project Meteos - Machine Learning as a Service in OpenStack

Hello Everyone, Meteos is a Machine Learning as a Service in OpenStack. Meteos allows users to analyze huge amount of data and predict a value by data mining and machine learning algorithms. Meteos create a workspace of Machine Learning via sahara spark plugin and manage some resources and jobs

Re: [openstack-dev] The CI issue: “cp: cannot create regular file '/opt/stack/new/bin/etcd': Text file busy

On Tue, 17 Oct 2017, at 14:15, linziw...@itri.org.tw wrote: > and in the /%24LOG_PATH/logs/devstack-early.txt file, > it shows > 2017-10-17 02:49:21.324 | + lib/etcd3:install_etcd3:109: sudo cp > /opt/stack/new/devstack/files/etcd-v3.1.10-linux-amd64/etcd > /opt/stack/new/bin/etcd > 2017-10-17