[openstack-dev] 答复: [tripleo] Blueprints for Rocky
Hi all, I proposed a BP about the integration with Vitrage: https://blueprints.launchpad.net/tripleo/+spec/tripleo-vitrage-integration And I posted a spec patch to the gerrit: https://review.openstack.org/#/c/552425/ Please help to review, any comments are welcome. Thanks~ BR, dwj 原始邮件 发件人：AlexSchultz 收件人：OpenStack Development Mailing List (not for usage questions) 日 期 ：2018年03月13日 22:02 主 题 ：[openstack-dev] [tripleo] Blueprints for Rocky Hey everyone, So we currently have 63 blueprints for currently targeted for Rocky[0]. Please make sure that any blueprints you are interested in delivering have an assignee set and have been approved. I would like to have the ones we plan on delivering for Rocky to be updated by April 3, 2018. Any blueprints that have not been updated will be moved out to the next cycle after this date. Thanks, -Alex [0] https://blueprints.launchpad.net/tripleo/rocky __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: [tripleo][vitrage] Draft schedule for PTG
Hi EmilienMacchi, I added a topic about 'support Vitrage(Root Cause Analysis project) service' in the etherpad for PTG. Can you please help to schedule a time slot? Maybe after the topic of 'Upgrades and Updates', half an hour is enough. We want to support the feature in the TripleO roadmap for Rocky. Thanks~ BR, dwj 原始邮件 发件人： ; 收件人： ; 日 期 ：2018年02月20日 00:38 主 题 ：[openstack-dev] [tripleo] Draft schedule for PTG __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Alex and I have been working on the agenda for next week, based on what people proposed in topics. The draft calendar is visible here: https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7kge5oqertje78%40group.calendar.google.com&ctz=Europe%2FDublin Also you can import the ICS from: https://calendar.google.com/calendar/ical/tgpb5tv12mlu7kge5oqertje78%40group.calendar.google.com/public/basic.ics Note this is a draft - we would love your feedback about the proposal. Some sessions might be too short or too long? You to tell us. (Please look at event details for descriptions). Also, for each session we need a "driver", please tell us if you volunteer to do it. Please let us know here and we'll make adjustment, we have plenty of room for it. Thanks! -- Emilien Macchi__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] send notification when update vertex
Hi dan, I use Vitrage master branch to test 'host_down' scenario.. When scenario_evaluator match the ''host_down_alarm_on_host" scenario and Do 'mark_down' action, Process update the vertex in entity graph and then should send the notification. But currently, it didn't send the notification. I trace the log but didn't find the reason. Can you help me to have a look at? Thanks~ The vitrage-graph log and config file are in attachment. From i post the 'computer.host.down' event to finish the evaluator. Use the 'host_down' template in Vitrage repo: etc/vitrage/templates.sample/host_down_scenarios.yaml BR, dwj vitrage.conf Description: Binary data vitrage_graph_for_host_down.txt Description: Binary data __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: RE: [vitrage] some error in Aodh datasource
Hi Idan,
Sorry, maybe it's the issue of my OpenStack env. I'll check it later. Thanks~
BR,
dwj
原始邮件
发件人：董文娟00101742
收件人： ;
抄送人： ;
日 期 ：2017年10月30日 08:59
主 题 ：答复: RE: [openstack-dev][vitrage] some error in Aodh datasource
Hi Idan,
Yes, it happens when Vitrage receives the Aodh alarm(event alarm) state change
notification.
But for the event alarm and threshold alarms, they don't combine type dict and
type Unicode.
So only gnocchi threshold alarm needs to encode.
I think gnocchi threshold alarm need to handle the state change notification
separately,
otherwise the event alarm and threshold alarm will raise exception as shown in
the log below.
What do you think?
BR,
dwj
发件人： ;
收件人：董文娟00101742;
抄送人： ;
日 期 ：2017年10月29日 17:04
主 题 ：RE: [openstack-dev][vitrage] some error in Aodh datasource
Hi dwj,
In this patch I added support for gnocchi threshold alarm.
This kind of alarm combine type dict and type Unicode. This occurs when
receiving notification about state transition from insufficient data to alarm.
In order not to make a major change in the code structure this type of error
should occur in event alarm (because it entirely type dict). It is caught in
_convert_alarm_state_transition_event.
In the upcoming changes in Aodh datasource (because of Ceilometer’s API is
being removed) we might need to insert some changes so
_convert_alarm_state_transition_event will receive also the alarm type (event,
gnocchi..).
Let me know if I can be of any help.
Thanks.
BR
Idan kinory
From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Friday, October 27, 2017 10:51 AM
To: Kinory, Idan (Nokia - IL/Kfar Sava)
Cc: Afek, Ifat (Nokia - IL/Kfar Sava) ;
openstack-dev@lists.openstack.org
Subject: [openstack-dev][vitrage] some error in Aodh datasource
Hi Idan Kinory,
I deploy Vitrage with devstack using master branch.
Currently I found a error in Aodh datasource when I change the Aodh alarm
state(alarm_state_transition notification).
The error log is as follows:
Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:30:50.429
9880 DEBUG vitrage.datasources.listener_service [-] EVENT ENQUEUED:
Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: {'description': u'Alarm
when * event occurred.', 'resource_id': None, 'vitrage_entity_type': 'aodh',
'timestamp': u'2017-10-26T06:37:41.353447', 'state_timestamp':
u'2017-10-27T07:09:06.636137', 'name': u'dwj', 'vitrage_datasource_action':
'update', 'severity': u'low', 'vitrage_sample_date': '2017-10-27
07:30:50.382730+00:00', 'vitrage_event_type': u'alarm.deletion', 'enabled':
True, 'alarm_id': u'9578d0eb-5d09-49a2-80e9-fb1a6c7ce7e9', 'state': u'alarm',
'repeat_actions': False, 'event_type': (u'*',), 'project_id':
u'378f268c64fc42c28226704dd71f37fe', 'type': u'event'} _enqueue_events
/opt/stack/vitrage/vitrage/datasources/listener_service.py:106
Oct 27 07:31:02 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:02.327
10104 DEBUG vitrage.datasources.services [-] start get changes _get_changes
/opt/stack/vitrage/vitrage/datasources/services.py:119
Oct 27 07:31:02 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:02.331
10104 DEBUG vitrage.datasources.services [-] end get changes _get_changes
/opt/stack/vitrage/vitrage/datasources/services.py:126
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver [-] Failed to Convert alarm state
transition event - 'dict' object has no attribute 'encode': AttributeError:
'dict' object has no attribute 'encode'
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver Traceback (most recent call last):
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver File
"/opt/stack/vitrage/vitrage/datasources/aodh/driver.py", line 352, in
_convert_alarm_state_transition_event
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver unicode_to_str =
state.encode("ascii")
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver AttributeError: 'dict' object has no
attribute 'encode'
I noticed that you fix the code in this patch(Line 352-368):
https://review.openstack.org/#/c/501701/4/vitrage/datasources/aodh/driver.py
Can you please explain why? Thanks.
BR,
dwj__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] some error in Aodh datasource
Hi Idan Kinory,
I deploy Vitrage with devstack using master branch.
Currently I found a error in Aodh datasource when I change the Aodh alarm
state(alarm_state_transition notification).
The error log is as follows:
Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:30:50.429
9880 DEBUG vitrage.datasources.listener_service [-] EVENT ENQUEUED:
Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: {'description': u'Alarm
when * event occurred.', 'resource_id': None, 'vitrage_entity_type': 'aodh',
'timestamp': u'2017-10-26T06:37:41.353447', 'state_timestamp':
u'2017-10-27T07:09:06.636137', 'name': u'dwj', 'vitrage_datasource_action':
'update', 'severity': u'low', 'vitrage_sample_date': '2017-10-27
07:30:50.382730+00:00', 'vitrage_event_type': u'alarm.deletion', 'enabled':
True, 'alarm_id': u'9578d0eb-5d09-49a2-80e9-fb1a6c7ce7e9', 'state': u'alarm',
'repeat_actions': False, 'event_type': (u'*',), 'project_id':
u'378f268c64fc42c28226704dd71f37fe', 'type': u'event'} _enqueue_events
/opt/stack/vitrage/vitrage/datasources/listener_service.py:106
Oct 27 07:31:02 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:02.327
10104 DEBUG vitrage.datasources.services [-] start get changes _get_changes
/opt/stack/vitrage/vitrage/datasources/services.py:119
Oct 27 07:31:02 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:02.331
10104 DEBUG vitrage.datasources.services [-] end get changes _get_changes
/opt/stack/vitrage/vitrage/datasources/services.py:126
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver [-] Failed to Convert alarm state
transition event - 'dict' object has no attribute 'encode': AttributeError:
'dict' object has no attribute 'encode'
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver Traceback (most recent call last):
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver File
"/opt/stack/vitrage/vitrage/datasources/aodh/driver.py", line 352, in
_convert_alarm_state_transition_event
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver unicode_to_str =
state.encode("ascii")
Oct 27 07:31:12 dwj-vitrage vitrage-collector[9880]: 2017-10-27 07:31:12.087
9880 ERROR vitrage.datasources.aodh.driver AttributeError: 'dict' object has no
attribute 'encode'
I noticed that you fix the code in this patch(Line 352-368):
https://review.openstack.org/#/c/501701/4/vitrage/datasources/aodh/driver.py
Can you please explain why? Thanks.
BR,
dwj__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Vitrage] Integration with doctor
Hi, For the integration Vitrage with doctor, I have some issues which need to be confirmed~ :) 1. Notification strategies: conservative (nova->Aodh) @Ifat In the host_down_scenarios.yaml[1], we only set the host state as error. But in doctor current use case, we need to call nova API 'nova reset-state' to set instance state as error to trigger the event alarm and notify the consumer. Is it needed to be fix? We need to add 'Aodh' and 'Nova' notifier plugins in Vitrage config file for doctor integration, right? 2. Notification strategies: shortcut (inspector->Aodh) @Ryota Do we have any plans to change to shortcut notification? @Ifat If we use the shortcut notification, in the Aodh notifier plugin, maybe we need to create aodh alarm with 'alarm_actions'. Correct me if I miss something. [1]. https://github.com/openstack/vitrage/blob/master/etc/vitrage/templates.sample/host_down_scenarios.yaml BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about "is_admin" in ctx
Hi Alexey, Currently we use 'is_admin' as 'is_admin_project'[1], right? I think the 'is_admin_project' represent the tenant , not be related to user. So why 'is_admin_project' alaways return 'True' with all of the user and tenants is the issue. What about a user which is not ＇admin' but have the 'admin' role? Should the user with 'admin' role see all all-tenants? [1] https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94 Ｔｈａｎｋｓ~ BR, dwj Original Mail Sender: ＜alexey.w...@nokia.com＞ To: ＜openstack-dev@lists.openstack.org＞ Date: 2017/05/15 22:49 Subject: Re: [openstack-dev]Suspected SPAM - Re: [vitrage] about "is_admin" in ctx Hi Wenjuan, Sorry it took me so long to answer due to the Boston Summit. After making some more checks in order to make it sure, the results are the following: 1. The context that we use has 2 properties regarding admin (is_admin, is_admin_project). 2. The is_admin property regards whether the user that has done the inquiry is the admin or not. So the only way it is True is if the user is admin. 3. The is_admin_project I thought will represent the tenant of the user, but from all of the user and tenants that I have used, it laways returned me True. 4. Due to that I have decided to use the is_admin property in the context to indicate whether the user can see all-tenants or not. 5. This is not a perfect solution because also users such as nova/cinder/all project names seems to be able to see the admin tab. In our case what will happen is that although in the UI we have the admin tab for those users, the data we will show in the vitrage tab is not of all the tenants but this specific tenant. Alexey From: Weyl, Alexey (Nokia - IL/Kfar Sava) [mailto:alexey.w...@nokia.com] Sent: Tuesday, April 25, 2017 3:10 PM To: OpenStack Development Mailing List (not for usage questions) ＜openstack-dev@lists.openstack.org＞ Subject: Suspected SPAM - Re: [openstack-dev] [vitrage] about "is_admin" in ctx Hi Wenjuan, This is a good question, I need to check it a bit more thoroughly. It’s just that at the moment we are preparing for the Boston Openstack Summit and thus it will take me a bit more time to answer that. Sorry for the delay. Alexey J From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Friday, April 21, 2017 11:08 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] about "is_admin" in ctx Hi all, I'm a little confused about the "is_amdin" in ctx. From the hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73), "is_admin" means admin user,. But we define the macro as "admin project"( https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94 ). But in my opinion, it should be the admin role. Correct me if i'm wrong :). BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [vitrage] about "is_admin" in ctx
Hi Alexey, Sorry for reply with a delay. I just saw this mail. It's OK, not a emergency issue. :) BR, dwj Original Mail Sender: ＜alexey.w...@nokia.com＞ To: ＜openstack-dev@lists.openstack.org＞ Date: 2017/04/25 21:09 Subject: Re: [openstack-dev] [vitrage] about "is_admin" in ctx Hi Wenjuan, This is a good question, I need to check it a bit more thoroughly. It’s just that at the moment we are preparing for the Boston Openstack Summit and thus it will take me a bit more time to answer that. Sorry for the delay. Alexey J From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Friday, April 21, 2017 11:08 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] about "is_admin" in ctx Hi all, I'm a little confused about the "is_amdin" in ctx. From the hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73), "is_admin" means admin user,. But we define the macro as "admin project"( https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94 ). But in my opinion, it should be the admin role. Correct me if i'm wrong :). BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] about "is_admin" in ctx
Hi all, I'm a little confused about the "is_amdin" in ctx. From the hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73), "is_admin" means admin user,. But we define the macro as "admin project"( https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94 ). But in my opinion, it should be the admin role. Correct me if i'm wrong :). BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ALU] Re: [vitrage] vitrage Resource API
Hi Alexey, Thanks for letting me know. I'll continue to implement the API if there is nobody works on it. :) BR, dwj Original Mail Sender: ＜alexey.w...@nokia.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜trinath.soman...@nxp.com＞ Date: 2017/03/21 14:17 Subject: Re: [openstack-dev] [ALU] Re: [vitrage] vitrage Resource API Hi Dong, At the beginning that API was a mock, and then when the Vitrage started to work, we haven’t implemented the API and thus we can’t show an API in the client that doesn’t work. In order to implement that API it also needs to support Multi tenancy. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Tuesday, March 21, 2017 2:46 AM To: trinath.soman...@nxp.com Cc: openstack-dev@lists.openstack.org Subject: [ALU] Re: [openstack-dev] [vitrage] vitrage Resource API No, in the implemention of these APIs． see https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/resource.py#L47 Original Mail Sender: ＜trinath.soman...@nxp.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜openstack-dev@lists.openstack.org＞ Date: 2017/03/21 00:50 Subject: Re: [openstack-dev] [vitrage] vitrage Resource API Outlook for iOS From: dong.wenj...@zte.com.cn ＜dong.wenj...@zte.com.cn＞ Sent: Monday, March 20, 2017 2:49:57 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] vitrage Resource API Hi All, I noticed that the APIs of `resource list` and `resource show` were mocked. Is there any backgroud for the mock or the API is not necessary? BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [vitrage] vitrage Resource API
No, in the implemention of these APIs． see https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/resource.py#L47 Original Mail Sender: ＜trinath.soman...@nxp.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜openstack-dev@lists.openstack.org＞ Date: 2017/03/21 00:50 Subject: Re: [openstack-dev] [vitrage] vitrage Resource API In tests? Get Outlook for iOS From: dong.wenj...@zte.com.cn ＜dong.wenj...@zte.com.cn＞ Sent: Monday, March 20, 2017 2:49:57 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] vitrage Resource API Hi All, I noticed that the APIs of `resource list` and `resource show` were mocked. Is there any backgroud for the mock or the API is not necessary? BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] vitrage Resource API
Hi All, I noticed that the APIs of `resource list` and `resource show` were mocked. Is there any backgroud for the mock or the API is not necessary? BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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＞ 日 期 ：2017年01月04日 19:13 主 题 ：RE: 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: puppet-branch-tarball-jobs - name: openstack-server-release-jobs - name: release-notes-jobs - name: openstack/python-vitrageclient template: - name: merge-check - name: python-jobs - name: python35-jobs - name: check-requirements - name: publish-to-pypi - name: osc-plugin-jobs Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 10:59 AM To: Weyl, Alexey (Nokia - IL) Cc: openstack-dev@lists.openstack.org Subject: 答复: Re: [openstack-dev] [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 registeration moved from zuul/layout.yaml to jenkins/jobs/projects.yaml? If yes, how can zuul know which jobs need to submit to jenkins?Thanks~ [1]https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：OpenStack Development Mailing List (not for usage questions) 日 期 ：2017年01月04日 16:30 主 题 ：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: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 9:49 AM To: openstack-dev@lists.openstack.org Subject: [ALU] [openstack-dev] [Vitrage] vitrage tempest job config Hi all, I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml. Where does all the jobs configed?Thanks~ BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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 i register in? BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：董文娟00101742 抄送人：＜openstack-dev@lists.openstack.org＞ 日 期 ：2017年01月04日 19:13 主 题 ：RE: 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: puppet-branch-tarball-jobs - name: openstack-server-release-jobs - name: release-notes-jobs - name: openstack/python-vitrageclient template: - name: merge-check - name: python-jobs - name: python35-jobs - name: check-requirements - name: publish-to-pypi - name: osc-plugin-jobs Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 10:59 AM To: Weyl, Alexey (Nokia - IL) Cc: openstack-dev@lists.openstack.org Subject: 答复: Re: [openstack-dev] [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 registeration moved from zuul/layout.yaml to jenkins/jobs/projects.yaml? If yes, how can zuul know which jobs need to submit to jenkins?Thanks~ [1]https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：OpenStack Development Mailing List (not for usage questions) 日 期 ：2017年01月04日 16:30 主 题 ：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: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 9:49 AM To: openstack-dev@lists.openstack.org Subject: [ALU] [openstack-dev] [Vitrage] vitrage tempest job config Hi all, I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml. Where does all the jobs configed?Thanks~ BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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 registeration moved from zuul/layout.yaml to jenkins/jobs/projects.yaml? If yes, how can zuul know which jobs need to submit to jenkins?Thanks~ [1]https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：OpenStack Development Mailing List (not for usage questions) 日 期 ：2017年01月04日 16:30 主 题 ：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: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 9:49 AM To: openstack-dev@lists.openstack.org Subject: [ALU] [openstack-dev] [Vitrage] vitrage tempest job config Hi all, I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml. Where does all the jobs configed?Thanks~ BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Vitrage] vitrage tempest job config
Hi all, I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml. Where does all the jobs configed?Thanks~ BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
