Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool
Ramy, Anita, I am in the process of adding an OpenStack project [1] for CI Watch. For the time being adding it to the big-tent is out of the scope of the project. I look forward to discussing CI monitoring solutions during next Tuesday's meeting. Can we make a list of all similar efforts and collect links to where we can find out more about them? Patrick East has scoreboard [2]. Bob Ball linked to a running instance of scoreboard [3], but the link is not working for me. Is it running somewhere else or is is not available at the moment? I do not know of other similar projects or where to find information about them. I am interested to see what others are doing. Regards, Skyler [1] https://review.openstack.org/#/c/216840/ [2] https://github.com/stackforge/third-party-ci-tools/tree/master/monitoring/scoreboard [3] http://zuul.openstack.xenproject.org/scoreboard/ The 08/25/2015 14:45, Asselin, Ramy wrote: HI Skyler, Very nice tool! When do you plan to open source it? Are you considering adding it to the OpenStack big-tent [1]? There are a few tools being worked on that provide different information [2][3][4]. It would be nice to consolidate and invest collective effort into one tool. It would be great to meet and discuss in the third party meeting [5], as Anita suggested. Are you available next Monday or Tuesday? Thanks! Ramy [1] http://docs.openstack.org/infra/manual/creators.html [2] http://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/monitoring/lastcomment-scoreboard [3] http://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/monitoring/scoreboard [4] http://git.openstack.org/cgit/stackforge/radar/tree/ [5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Monday, August 24, 2015 5:44 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool On 08/24/2015 07:59 PM, Skyler Berg wrote: Hi all, I am pleased to announce CI Watch [1], a CI monitoring tool developed at Tintri. For each OpenStack project with third-party CI's, CI Watch shows the status of all CI systems for all recent patch sets on a single dashboard. CI maintainers can use this tool to pinpoint when errors began and to find other CI's affected by the similar issues. Core team members can find which vendor CI systems are failing and determine when breaking changes hit their projects. The project dashboards provide access to all relevant logs and reviews, simplifying the process of investigating failures. CI Watch should also create more transparency within the third-party CI ecosystem. The health of all CI's is now visible to everyone in the community. We hope that by giving everyone this visibility we will make it easier for anyone to find and address issues on CI systems. Any feedback would be appreciated. We plan to open source this project soon and welcome contributions from anyone interested. For the moment, any bugs, concerns, or ideas can be sent to openstack-...@tintri.com. [1] ci-watch.tintri.com Best, Skyler Berg __ 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 Hi Skyler: Thanks for your interest in participating in the third party segment of the openstack community. We have a number of people working on dashboards for ci systems. We are working on having infra host one: https://review.openstack.org/#/c/194437/ which is a tool currently hosted by one of our ci operators, Patrick East, which is open source. Can I suggest you attend a third party meeting and perhaps meet some of the other operators and collaborate with them? We don't have any lack of people starting tools what we lack is a tool which will be maintained. Thanks for your interest Skyler, Anita. __ 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 Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org
[openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool
Hi all, I am pleased to announce CI Watch [1], a CI monitoring tool developed at Tintri. For each OpenStack project with third-party CI's, CI Watch shows the status of all CI systems for all recent patch sets on a single dashboard. CI maintainers can use this tool to pinpoint when errors began and to find other CI's affected by the similar issues. Core team members can find which vendor CI systems are failing and determine when breaking changes hit their projects. The project dashboards provide access to all relevant logs and reviews, simplifying the process of investigating failures. CI Watch should also create more transparency within the third-party CI ecosystem. The health of all CI's is now visible to everyone in the community. We hope that by giving everyone this visibility we will make it easier for anyone to find and address issues on CI systems. Any feedback would be appreciated. We plan to open source this project soon and welcome contributions from anyone interested. For the moment, any bugs, concerns, or ideas can be sent to openstack-...@tintri.com. [1] ci-watch.tintri.com Best, Skyler Berg __ 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] [cinder][nova][ci] Tintri Cinder CI failures after Nova change
As Matt found, it the problem was with out of date requirements. Going forward I would advise any third party CI that is not spinning up a new VM for every job to purge all python packages after each run. This will make devstack reinstall everything, avoid this type of problem. Though the problem was with global requirements, only our CI was failing because everyone else was getting the newest version of each package each time. We are still failing on one test (test_ec2_instance_run.InstanceRunTest) and we are not sure what the cause is. Here is a log from a recent run: http://openstack-ci.tintri.com/tintri/refs-changes-88-210588-1/ Here is the failing test: ft1.280: setUpClass (tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest)_StringException: Traceback (most recent call last): File tempest/test.py, line 272, in setUpClass six.reraise(etype, value, trace) File tempest/test.py, line 265, in setUpClass cls.resource_setup() File tempest/thirdparty/boto/test_ec2_instance_run.py, line 91, in resource_setup state = wait.state_wait(_state, available) File tempest/thirdparty/boto/utils/wait.py, line 51, in state_wait (dtime, final_set, status)) AssertionError: State change timeout exceeded!(196s) While waitingfor set(['available']) at failed From n-crt log: 2015-08-07 15:21:58.237 ERROR oslo_messaging.rpc.dispatcher [req-d4ce0001-0754-461f-8fdc-57908baf88f7 tempest-InstanceRunTest-1110235717 tempest-InstanceRunTest-357311946] Exception during message handling: 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py, line 142, in _dispatch_and_reply 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher executor_callback)) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py, line 186, in _dispatch 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher executor_callback) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py, line 129, in _do_dispatch 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/cert/manager.py, line 70, in decrypt_text 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher return crypto.decrypt_text(project_id, base64.b64decode(text)) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/crypto.py, line 200, in decrypt_text 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher return priv_key.decrypt(text, padding.PKCS1v15()) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/cryptography/hazmat/backends/openssl/rsa.py, line 536, in decrypt 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher return _enc_dec_rsa(self._backend, self, ciphertext, padding) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/cryptography/hazmat/backends/openssl/rsa.py, line 76, in _enc_dec_rsa 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher return _enc_dec_rsa_pkey_ctx(backend, key, data, padding_enum) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/cryptography/hazmat/backends/openssl/rsa.py, line 105, in _enc_dec_rsa_pkey_ctx 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher _handle_rsa_enc_dec_error(backend, key) 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher File /usr/lib/python2.7/site-packages/cryptography/hazmat/backends/openssl/rsa.py, line 145, in _handle_rsa_enc_dec_error 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher assert errors[0].reason in decoding_errors 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher AssertionError 2015-08-07 15:21:58.237 32745 ERROR oslo_messaging.rpc.dispatcher 2 The 08/07/2015 09:01, Matt Riedemann wrote: On 8/7/2015 8:38 AM, Matt Riedemann wrote: On 8/6/2015 3:30 PM, Skyler Berg wrote: After the change cleanup NovaObjectDictCompat from virtual_interface [1] was merged into Nova on the morning of August 5th, Tintri's CI for Cinder started failing 13 test cases that involve a volume being attached to an instance [2]. I have verified that the tests fail with the above mentioned change and pass when running against the previous commit. If anyone knows why this patch is causing an issue or is experiencing similar problems, please let me know. In the meantime, expect Tintri's CI to be either down or reporting failures until a solution is found. [1] https
[openstack-dev] [cinder][nova][ci] Tintri Cinder CI failures after Nova change
After the change cleanup NovaObjectDictCompat from virtual_interface [1] was merged into Nova on the morning of August 5th, Tintri's CI for Cinder started failing 13 test cases that involve a volume being attached to an instance [2]. I have verified that the tests fail with the above mentioned change and pass when running against the previous commit. If anyone knows why this patch is causing an issue or is experiencing similar problems, please let me know. In the meantime, expect Tintri's CI to be either down or reporting failures until a solution is found. [1] https://review.openstack.org/#/c/200823/ [2] http://openstack-ci.tintri.com/tintri/refs-changes-06-201406-35/ -- __ 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] devstack installation problem
I just ran into this issue because I was installing a package that was bringing in keystonemiddleware 1.5.x which was downgrading pbr to 1.0. I fixed this problem by upgrading keystonemiddleware to 2.x.x with: pip install -U keystonemiddleware After that, devstack worked fine again. This break happened after the RDO packages used in devstack were changed from Juno to Kilo. Skyler Berg The 07/11/2015 18:18, Jeremy Stanley wrote: On 2015-07-11 18:09:26 + (+), Jeremy Stanley wrote: On 2015-07-11 22:49:27 +0530 (+0530), Venkateswarlu P wrote: After running ./stack.sh I am getting the following error. 015-07-11 17:01:02.188 | error in setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers; Expected ',' or end-of-list in python-ldap=2.4;python_version=='2.7' at ;python_version=='2.7' [...] That's an indication something's dragging in an older PBR release that didn't know not to copy environment markers into tests_require. Without more of the logs indicating what installed which versions of PBR and why, it's hard to tell you any more than that. Are you running from the DevStack master branch or a stable/something branch? Oh, I also meant to add that if you're re-running stack.sh on a machine where you've already run it before, this is a known issue. See https://launchpad.net/bugs/1468808 for a detailed explanation and current workaround. -- Jeremy Stanley __ 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] [horizon] Modifying existing dashboards with plugins
I am considering making a plugin for Horizon which will add additional information to existing dashboards. For example, the plugin may add a new column to a table in a table in the instances dashboard. I have not found a standard method for plugins to do this. The plugin support I have found only allows for adding new dashboards and panels [1] as far as I can tell. There is currently a way to change any part of openstack_dashboard with a customization module [2]. However, this does not appear to be designed for plugins. Since only one customization module can be specified, it is not a good fit for plugin developers, because users would be limited to one plugin that uses this mechanism. I am wondering if there is a way to have plugins modify existing dashboards currently that I am overlooking. If not, should there be? [1] http://docs.openstack.org/developer/horizon/topics/settings.html#pluggable-settings-label [2] http://docs.openstack.org/developer/horizon/topics/customizing.html#modifying-existing-dashboards-and-panels __ 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
