Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

Bo problem Dong. If you have any more questions, don’t be shy, just ask. BR, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, January 05, 2017 3:16 AM To: Weyl, Alexey (Nokia - IL) Cc: openstack-dev@lists.openstack.org Subject: 答复: RE: Re: [openstack-dev]

[openstack-dev] [Monasca] Monasca devstack installation is failing

*Hello,* *I am trying to install Monasca devstack using vagrant file given in monasca-ui repo.* *And its failing again and again with below error.* *Could you please help me, i will really appreciate your help.* ==> default: 2017-01-05 06:28:06.125 | ++ functions-common:start_service:2306

[openstack-dev] [nova] mutate config options on compute service

According to http://docs.openstack.org/newton/config-reference/mutable.html , seems this option is valid to compute service (as it says: Log onto the compute node. ) but from following test result seems it's not honored by compute service, is it a bug or wrong usage? this is a all in one

[openstack-dev] Fwd: [Openstack] The Forum: in more detail

Hi *dev, Post over on the general ML you might be interested in - please send replies there to avoid cross-posting pain ;) Regards, Tom Forwarded Message Subject: [Openstack] The Forum: in more detail Date: Thu, 5 Jan 2017 11:42:53 +0800 From: Tom Fifield

Re: [openstack-dev] [neutron][ml2] Mechanism drivers ! OpenvSwich or Linuxbridge or both of them?

Hi, Kevin. If I load openvswitch and linuxbridge mechanism drivers in neutron server, and running ovs-agent in compute nodes. What does openvsitch mechanism driver do? What does linuxbridge mechanism do? I think there must have some differences between the openvswitch and the linuxbridge mechanism

[openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

Hi Alexey, Sorry, I saw the configuration. Need to click the 'raw' button in github to see the whole layout.yaml file. Sorry to trouble you again and again. :-) BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：董文娟00101742 抄送人：＜openstack-dev@lists.openstack.org＞ 日 期

Re: [openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

It seems the file is truncated on Github preview. It stops at openstack/security-specs If you check the raw file[1], you will find entry of openstack/vitrage [1]: https://raw.githubusercontent.com/openstack-infra/project-config/master/zuul/layout.yaml [image: Screen Shot 2017-01-05 at 9.11.08

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Doug Hellmann wrote: Excerpts from Joshua Harlow's message of 2017-01-03 12:03:44 -0800: Hi Oslo folks (and others), Happy new year! After serving for about a year I think it's a good opportunity for myself to let another qualified individual run for Oslo PTL (seems common to only go for two

[openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

Hi, I know. Why only python-vitrageclient and puppet-vitrage register in the zuul/layout.yaml? They also register in the jeknins/jobs/projects.yaml. And other vitrage projects only register in the jeknins/jobs/projects.yaml. I'm confused if i want to add a new jenkins job, which file should

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Michal, Another option is 2 individuals from each core review team + PTL. That is lighter weight then 3 and 4, yet more constrained then 1 and 2 and would be my preferred choice (or alternatively 3 or 4). Adding a deliverable is serious business ☺ FWIW I don’t’ think we are at an impasse,

Re: [openstack-dev] [tc][kolla] Adding new deliverables

As the person purposing kolla-salt, I would like to weigh in. I like the idea of option 2, I certainly feel the PTL should always be involved in these things. I would also agree with the pre-1.0 as dev/experimental so as to not be tightly bound by rules for more stable and long term projects

[openstack-dev] [tc][kolla] Adding new deliverables

Hello, New deliverable to Kolla was proposed, and we found ourselves in a bit of an impasse regarding process of accepting new deliverables. Kolla community grew a lot since we were singular project, and now we have 3 deliverables already (kolla, kolla-ansible and kolla-kubernetes). 4th one was

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

Sorry for top post: thanks to Tim Burke, we are past this and a few other problems. Here's the latest work: Swift - Review from Tim : https://review.openstack.org/#/c/401397/ Swift - My review (WIP) : https://review.openstack.org/#/c/416084/ DevStack - My review :

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

Excerpts from John Dickinson's message of 2017-01-03 12:00:07 -0800: > > On 3 Jan 2017, at 10:38, Doug Hellmann wrote: > > > Excerpts from John Dickinson's message of 2017-01-03 09:02:19 -0800: > >> > >> On 2 Jan 2017, at 13:06, Davanum Srinivas wrote: > >> > >>> Folks, > >>> > >>> Short Story :

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Excerpts from Joshua Harlow's message of 2017-01-03 12:03:44 -0800: > Hi Oslo folks (and others), > > Happy new year! > > After serving for about a year I think it's a good opportunity for > myself to let another qualified individual run for Oslo PTL (seems > common to only go for two terms

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

On Wed, Jan 04, 2017 at 01:31:42PM -0500, Ian Cordasco wrote: > I believe you asked in another thread (that I cannot locate) if it was > acceptable to the Glance team to not have an 11.0.3 tarball on > openstack.org. With Brian on vacation, I'm hoping the other stable > maintenance cores will

Re: [openstack-dev] [Nova] python 3 tests hate my exception handling

Ok, I think at this point I'll propose a tweak to keystoneauth to make this easier, and then refactor my nova code around that. Thanks for the help everyone. Hugs and kisses, Michael On Wed, Jan 4, 2017 at 4:52 PM, Morgan Fainberg wrote: > > > On Jan 3, 2017

Re: [openstack-dev] [ironic] User survey question

Hi, Here are some questions I've thought of: TESTING / INTERESTED - What is your use case for ironic? - What, if anything, is preventing you from using ironic in a production environment? - What alternatives to ironic have you considered? USING - What new features would you like to see added

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

-Original Message- From: Tony Breeds Reply: OpenStack Development Mailing List (not for usage questions) , OpenStack Development Mailing List (not for usage questions) Date: December 14, 2016

Re: [openstack-dev] [Telemetry] Asking a question to our users

On 04/01/17 12:08 PM, Julien Danjou wrote: > I _think_ they ask for what "release of OpenStack" is being used, but > that might be it. i would probably do something similar to what Mehdi suggested then. i don't think we want feedback relating to ceilometer storage/api (because it's been dead

[openstack-dev] [keystone] documenting policy guidelines

We had another healthy discussion about policy today [0] and most of it revolved around documenting policy guidelines. The question of the day was where should these guidelines live? To answer that we highlighted the following criteria: - Guidelines should be proposed and reviewed in small

Re: [openstack-dev] [Telemetry] Asking a question to our users

On Wed, Jan 04 2017, gordon chung wrote: > is there a way to scope our question/responses? feedback is good but it > isn't the most useful when we get feedback based on Liberty. I _think_ they ask for what "release of OpenStack" is being used, but that might be it. -- Julien Danjou # Free

Re: [openstack-dev] [heat] project specific question for the next user survey

Dear Team Let's put some thoughts here[1] in next 24h. Any idea/suggestion to this heat adoption question are welcome. It will be great if we can get some really useful information from users by given the right question. [1] https://etherpad.openstack.org/p/ocata-heat-user-survey 2017-01-02

Re: [openstack-dev] [ironic] [nova] Ironic virt driver resources reporting

On Wed, Jan 4, 2017 at 5:45 PM, Vladyslav Drok wrote: > Thanks all for replies! > > On Tue, Jan 3, 2017 at 5:16 PM, Jay Faulkner wrote: > >> Hey Vdrok, some comments inline. >> >> > On Dec 30, 2016, at 8:40 AM, Vladyslav Drok wrote: >> > >>

Re: [openstack-dev] [Telemetry] Asking a question to our users

On 26/12/16 05:20 AM, Julien Danjou wrote: > Hi folks, > > The foundation is offering the opportunity to ask a question to users: > > "I wanted to offer you the opportunity to ask a question on the > upcoming User Survey, which launches on or before Feb. 1. Each PTL of > a project with

Re: [openstack-dev] [tripleo] [ci] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

On 01/04/2017 10:34 AM, Steven Hardy wrote: Hi Harry, On Tue, Jan 03, 2017 at 04:04:51PM -0500, Harry Rybacki wrote: Greetings All, Folks have been diligently working on the blueprint[1] to prepare TripleO-Quickstart (OOOQ)[2] and TripleO-Quickstart-Extras[3] for their transition into

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

Hi Team, Thanks for a great discussion at today's meeting, please find the minutes at https://wiki.openstack.org/wiki/Cyborg/MeetingLogs#2017-01-04 On Wed, Jan 4, 2017 at 10:40 PM, Miroslav Halas wrote: > Howard and team, > > > > I have usually conflict at this time, but I

Re: [openstack-dev] [tripleo] [ci] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

Greetings Steve On Wed, Jan 4, 2017 at 4:34 AM, Steven Hardy wrote: > Hi Harry, > > On Tue, Jan 03, 2017 at 04:04:51PM -0500, Harry Rybacki wrote: > > Greetings All, > > > > Folks have been diligently working on the blueprint[1] to prepare > > TripleO-Quickstart (OOOQ)[2] and

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

I quite like Boris' last suggestion, with a minor tweak: "In your opinion, what keystone feature(s) requires more attention (select all that apply): "federation", "performance", "policy", "scaling out", "backend support", "ldap"." Unless someone has another suggestion I'll stick to the above.

Re: [openstack-dev] [monasca]Monasca event handling capabilities

Hello, Monasca events handling is an early work in progress, see https://wiki.openstack.org/wiki/Monasca/Events for some information. Information on what metrics are available from each plugin can be found at https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md Custom checks

Re: [openstack-dev] [Performance] PTG?

Hi, Joe! It is not a mistake. After a talk with Dina B., we decided to extend Rally session for the wider audience and I requested "Rally & Performance team" session. On Wed, Jan 4, 2017 at 5:29 PM, Joe Talerico wrote: > When I signed up to attend the PTG, Performance was

[openstack-dev] [Trove] Trove Meeting on 4 Jan canceled

Hey folks: There's not much to discuss on the Agenda for this week [1] and most folks are still getting back from the Holidays, so let's cancel the Trove meeting for this week. We will have the Trove meeting next week on Wednesday, January 11th. Thanks, Nikhil [1]

Re: [openstack-dev] [ironic] [nova] Ironic virt driver resources reporting

Thanks all for replies! On Tue, Jan 3, 2017 at 5:16 PM, Jay Faulkner wrote: > Hey Vdrok, some comments inline. > > > On Dec 30, 2016, at 8:40 AM, Vladyslav Drok wrote: > > > > Hi all! > > > > There is a long standing problem of resources reporting in ironic

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On Mon, Dec 19, 2016 at 2:09 PM, Doug Hellmann wrote: > Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > >> 3) Choose Goals for Pike. >> Some of us already did, but we might want to start looking at what >> Goals we would like to achieve during Pike

Re: [openstack-dev] [Monasca]

Apologies for the delay in response, just returning from the holidays. >From the trace, it would appear the monasca API is unable to authenticate with >keystone. The API’s admin credentials may not be valid (either they do not >exist in keystone or are configured incorrectly for the API) which

[openstack-dev] [Performance] PTG?

When I signed up to attend the PTG, Performance was not listed as a option, however on the website it clearly shows Performance is Monday-Tuesday. Is this just a mistake in the event website? Joe __ OpenStack Development

Re: [openstack-dev] [nova] Outlook on Ocata blueprints

On 1/4/2017 12:07 AM, Shiina, Hironori wrote: Hi Matt, In Not started / blocked group in https://etherpad.openstack.org/p/nova-ocata-feature-freeze : https://blueprints.launchpad.net/nova/+spec/inject-nmi-ironic (Tang Chen) No Nova code changes yet, several Ironic patches outstanding, so

[openstack-dev] [ux] Future of the OpenStack UX team

Hi everyone, Piet recently reached out to me to explain that he won't be able to continue in his role as OpenStack UX team's PTL. Since he created the team and spent a lot of time coordinating its activities, that raises the question of the future of the OpenStack UX team. The situation was

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

Howard and team, I have usually conflict at this time, but I am trying to keep up with meeting logs and etherpads ☺. Either Scott or I will be at PTG representing Lenovo so we would be happy to participate. From last meeting I have added TODO to Nasca etherpard to link the design document

Re: [openstack-dev] [Telemetry] Asking a question to our users

I haven't answer before because that just one question, and I'm not sure about what is really interesting for us. But what about something like: Which backend/dispatcher/publusher their use ? Do their switch to Gnocchi ? On Wed, Jan 04, 2017 at 03:31:04PM +0100, Julien Danjou wrote: On Mon,

Re: [openstack-dev] [Telemetry] Asking a question to our users

On Mon, Dec 26 2016, Julien Danjou wrote: Nothing? :) > Hi folks, > > The foundation is offering the opportunity to ask a question to users: > > "I wanted to offer you the opportunity to ask a question on the > upcoming User Survey, which launches on or before Feb. 1. Each PTL of > a

Re: [openstack-dev] [ironic] User survey question

Hi, from my part, if it would be appropriate, I'd like to use this opportunity to estimate the iPXE adoption. So the question targeting those USING and TESTING ironic would be: - does the hardware you are managing with ironic support iPXE? - do you use ironic with iPXE enabled?

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

Happy New Year everyone. I won't be able participate in the IRC today due to a conflict, but I will try to connect and monitor. I will also put more comments in the etherpads that are linked On Wed, Jan 4, 2017 at 6:28 AM, Zhipeng Huang wrote: > Hi Team, > > Please find

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

++ to the suggestions Boris threw out. Answers to any of those would be valuable. In addition to that, I'd find any information about policy useful. Maybe something along the lines of "what changes to the policy files are you making, if any". This could be something that is asked OpenStack-wide

Re: [openstack-dev] [tripleo] quick reminder on review policy

On 01/03/2017 07:30 PM, Emilien Macchi wrote: > I've noticed some TripleO core reviewers self approving patch without > respecting our review policy, specially in tripleo-quickstart. > This is slightly misleading. To me, self-approving is +2/+A on your own patch. What has been going in

[openstack-dev] [horizon] Timeout issue

Hi, Maybe someone can help or give me some pointers. On horizon I am trying to attach a network interface to a router. When I do this I get the following error on horizon: “Danger: There was an error submitting the form. Please try again.” When I refresh the page I see that the operation has

Re: [openstack-dev] [tripleo] Atlanta PTG

I would like to bring this topic up on your inbox, so we can continue to make progress on the agenda. Feel free to follow existing examples in the etherpad and propose a design dession. Thanks, On Wed, Dec 21, 2016 at 9:06 AM, Emilien Macchi wrote: > General infos about PTG:

[openstack-dev] [ironic] User survey question

Hey all, We have an opportunity to ask a question on the upcoming User Survey, which will launch by February 1st. We can choose the audience to direct the question to, choosing from those USING, TESTING, or INTERESTED in Ironic (or some combination of these). The hope is that the Foundation

[openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.1.4 Agenda

Hi Team, Please find the agenda at https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda_for_next_meeting our IRC channel is #openstack-cyborg -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email:

Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

We do write code in the zuul/layout.yaml: - name: openstack/puppet-vitrage template: - name: merge-check - name: puppet-check-jobs - name: puppet-module-unit-jobs - name: puppet-beaker-jobs - name: puppet-beaker-jobs-xenial - name:

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

> > > OK - is there any way that I can assist? > > What about the challenges I discussed in my initial mail related to > long AIO build times etc..? > > I think there are some options, but the idea we're going with at the moment is to look into setting this up as a periodical - we're at about 1hr

Re: [openstack-dev] Planning for the Pike PTG

Matt Riedemann wrote: > I haven't been living under a rock but I'm not aware of any major > announcements regarding session planning for the PTG - has that happened > somewhere and I'm just in the dark? > > I'm mostly wondering about the Monday and Tuesday cross-project sessions > - are those

Re: [openstack-dev] [tripleo] Adding a LateServices ResourceChain

On Tue, Jan 03, 2017 at 03:20:37PM -0500, Lars Kellogg-Stedman wrote: > On Fri, Dec 23, 2016 at 02:21:00PM +, Steven Hardy wrote: > > I commented on the bug, I'm not sure about this as it seems to overlap with > > our service_config_settings interface, which IIRC landed slightly after > > your

Re: [openstack-dev] [tripleo] [ci] TripleO-Quickstart Transition to TripleO-CI Update and Invite:

Hi Harry, On Tue, Jan 03, 2017 at 04:04:51PM -0500, Harry Rybacki wrote: > Greetings All, > > Folks have been diligently working on the blueprint[1] to prepare > TripleO-Quickstart (OOOQ)[2] and TripleO-Quickstart-Extras[3] for > their transition into TripleO-CI. Presently, our aim is to begin

[openstack-dev] 答复: Re: [ALU] [Vitrage] vitrage tempest job config

Hi Alexey, As far as i know, every project needs to register in the zuul/layout.yaml[1], so zuul can submit the job to jenkins via gearman. So the jenkins knows which jobs need to run and then run the job which defined in the jenkins/jobs/XXX.yaml. Did i missing something? Or the job

[openstack-dev] [tricircle]weekly meeting of Jan.4

Hello, team, Welcome to the year 2017. Agenda of Jan.4 weekly meeting: 1. shadow_agent for VxLAN L2 networking/L3 DVR issue 2. db migration version 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting

Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

Hi Dong, All of that data is configured the openstack-infra/project-config in github. There you can find our changes by searching for vitrage. The main files that we have pushed our changes are: jenkins/jobs/vitrage.yaml gerrit/projects.yaml jenkins/jobs/projects.yaml BR, Alexey From:

Re: [openstack-dev] [Neutron][networking-*] Attention for upcoming refactoring

If you wanted one compatible with both you could have a line like this. session = ctx.session if isinstance(ctx, neutron.context.Context) else ctx On Tue, Jan 3, 2017 at 2:52 PM, Ian Wells wrote: > I see this changes a function's argument types without changing the >

Re: [openstack-dev] [neutron][ml2] Mechanism drivers ! OpenvSwich or Linuxbridge or both of them?

Note that with the openvswitch and linuxbridge mechanism drivers, it will be safe to have both loaded on the Neutron server at the same time since each driver will only bind a port if it has an agent of that type running on the host. On Fri, Dec 30, 2016 at 1:24 PM, Sławek Kapłoński

[openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

Hello, The aim of this mail is to ease the DPDK deployment with TripleO. I would like to see if the approach of deriving THT parameter based on introspection data, with a high level input would be feasible. Let me brief on the complexity of certain parameters, which are related to DPDK.