Re: [openstack-dev] [designate] Non Candidacy for PTL - Pike
Graham, We've been lucky to have you leading the project over the last few cycles. You've done really great work. I'll always appreciate you fighting for what you believed in and trying to make things better for everyone. I'll miss your heavy involvement on a professional and personal level. You are an awesome person and I've greatly enjoyed working and...not working with you at all the events we've attended over the last few years. <3 Tim Simmons From: Hayes, Graham <graham.ha...@hpe.com> Sent: Monday, January 9, 2017 4:30 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [designate] Non Candidacy for PTL - Pike Happy new year! As you may have guessed from the subject, I have decided that the time has come to step aside as PTL for the upcoming cycle. It is unfortunate, but my work has pivoted in a different direction over the last year (containers all the way down man - but hey, I got part of my wish to write Golang, just not on the project I envisaged :) ). As a result, I have been trying to PTL out of hours for the last cycle and a half. Unfortunatly, this has had a bad impact on this cycle, and I don't think we should repeat the pattern. We have done some great work over the last year or so - Worker Model, the s/Domain/Zone work, the new dashboard, being one of the first projects to have an external tempest plugin and getting lost in the west of Ireland in the aftermath of the flooding. I can honestly say, I have enjoyed my entire time with this team, from our first meeting in Austin, back in the beginning of 2014, the whole way through to today. We have always been a small team, but when I think back to what we have produced over the last few years, I am incredibly proud. Change is healthy, and I have been in a leadership position in Designate longer than most, and no project should rely on a person or persons to continue to exist. I will stick around on IRC, and still remain a member of the core review team, as a lot of the roadmap is still in the heads of myself and 2 or 3 others, but my main aim will be to document the roadmap in a single place, and not just in thousands of etherpads. It has been a fun journey - I have gotten to work with some great people, see some amazing places, work on really interesting problems and contribute to a project that was close to my heart. This is not an easy thing to do, but I think the time is right for the project and me to let someone else make their stamp on the project, and bring it to the next level. Nominations close soon [0] so please start thinking about if you would like to run or not. If anyone has any questions about the role, please drop me an email or ping me [1] on IRC [2] Thank you for this opportunity to serve the community for so long, it is not something I will forget. - Graham 0 - https://governance.openstack.org/election/ 1 - mugsie 2 - #openstack-dns __ 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
Re: [openstack-dev] [designate] Meeting this week
Sounds good to me. Enjoy your meeting :) Tim Simmons From: Hayes, Graham <graham.ha...@hpe.com> Sent: Wednesday, November 30, 2016 10:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [designate] Meeting this week Hi All, There is an unexpected internal meeting today that conflicts with the IRC meeting. As a result, I will not be available to chair, and I think that the other HPE team members will also be unavailable. I suggest that we postpone for this week? Thanks, Graham __ 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
Re: [openstack-dev] [designate] The designate API service is stopped
Jaime, Usually that's the error you see if you're trying to start up multiple API processes. They all try and bind to port 9001, so that error is saying the API can't bind. So something else (I suspect another designate-api process, or some other type of API) is already listening on that port. Hope that helps, Tim Simmons From: Jaime Fernández jjja...@gmail.com Sent: Monday, July 20, 2015 8:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [designate] The designate API service is stopped I've followed instructions to install Designate in Dev environment: http://docs.openstack.org/developer/designate/install/ubuntu-dev.html I've made some slight modifications to use qpid (instead of rabbitmq) and to integrate with Infoblox. What I've seen is that designate-api process dies (the other processes are running correctly). I'm not sure if the problem could be a network issue between designate-api and qpid. Here it is the output for last traces of designate-api process: 2015-07-20 14:43:37.728 727 DEBUG qpid.messaging.io.raw [-] READ[3f383f8]: '\x0f\x00\x00\x10\x00\x00\x00\x00\x00\x00\x00\x00\x01\n\x00\x00' readable /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/qpid/messaging/driver.py:411 2015-07-20 14:43:37.729 727 DEBUG qpid.messaging.io.ops [-] RCVD[3f383f8]: ConnectionHeartbeat() write /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/qpid/messaging/driver.py:651 2015-07-20 14:43:37.729 727 DEBUG qpid.messaging.io.ops [-] SENT[3f383f8]: ConnectionHeartbeat() write_op /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/qpid/messaging/driver.py:683 2015-07-20 14:43:37.730 727 DEBUG qpid.messaging.io.raw [-] SENT[3f383f8]: '\x0f\x00\x00\x10\x00\x00\x00\x00\x00\x00\x00\x00\x01\n\x00\x00' writeable /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/qpid/messaging/driver.py:475 Traceback (most recent call last): File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/hubs/hub.py, line 457, in fire_timers timer() File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/hubs/timer.py, line 58, in __call__ cb(*args, **kw) File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/greenthread.py, line 214, in main result = function(*args, **kwargs) File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/oslo.service-0.4.0-py2.7.egg/oslo_service/service.py, line 623, in run_service service.start() File /home/sysadmin/openstack/designate/designate/service.py, line 173, in start socket = self._wsgi_get_socket() File /home/sysadmin/openstack/designate/designate/service.py, line 209, in _wsgi_get_socket 'port': self._service_config.api_port}) RuntimeError: Could not bind to 0.0.0.0:9001http://0.0.0.0:9001 after trying for 30 seconds 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup [-] Could not bind to 0.0.0.0:9001http://0.0.0.0:9001 after trying for 30 seconds 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup Traceback (most recent call last): 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/oslo.service-0.4.0-py2.7.egg/oslo_service/threadgroup.py, line 154, in wait 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup x.wait() 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/oslo.service-0.4.0-py2.7.egg/oslo_service/threadgroup.py, line 51, in wait 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup return self.thread.wait() 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/greenthread.py, line 175, in wait 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup return self._exit_event.wait() 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/event.py, line 121, in wait 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup return hubs.get_hub().switch() 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site-packages/eventlet-0.17.4-py2.7.egg/eventlet/hubs/hub.py, line 294, in switch 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup return self.greenlet.switch() 2015-07-20 14:43:55.221 727 ERROR oslo_service.threadgroup File /home/sysadmin/openstack/designate/.venv/local/lib/python2.7/site
Re: [openstack-dev] Error starting designate (DNSaaS)
All, The updated documentation for Designate is here: http://docs.openstack.org/developer/designate/ The readthedocs version was abandoned a while ago, it was taken down by the Designate maintainers but appears to have returned. Refer to http://docs.openstack.org/developer/designate/install/ubuntu-dev.html for the most up-to-date dev environment guide. Feel free to join us in #openstack-dns if you run into issues. Thanks, Tim Simmons From: Jaime Fernández jjja...@gmail.com Sent: Wednesday, July 1, 2015 12:24 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Error starting designate (DNSaaS) Just to test designate, as a first step, I installed everything in a single virtual machine. The config file is exactly the same one than provided by http://designate.readthedocs.org/en/latest/getting-started.html#development-environment (except for property state_path with value /var/lib/designate). It looks like this file configures a sqlite database. Perhaps tomorrow I will try with MySQL instead of sqlite, but I also tried other official guideline that was using bind and mysql and it also failed in the same step. So, I'm not sure if it is some type of conflict with RHEL6.5, or the latest sql scripts have some bug. __ 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] [Designate] Core reviewer update
Thanks all, I’m honored :) —Tim On Feb 12, 2015, at 10:31 AM, Kiall Mac Innes ki...@macinnes.iemailto:ki...@macinnes.ie wrote: Changes have been applied, welcome Tim :) On 12/02/15 16:18, Rich Megginson wrote: On 02/12/2015 08:51 AM, Hayes, Graham wrote: On 12/02/15 15:50, Kiall Mac Innes wrote: +1 - Tim has been giving good reviews over the last few months and will make a good addition.. Thanks, Kiall On 12/02/15 15:40, Vinod Mangalpally wrote: Hello Designate folks, Betsy Luzader (betsy) resigned from her core reviewer position on Designate. In order to keep the momentum of reviews in Designate going, I'd like to propose adding Tim Simmons (timsim) to designate-core. For context on Designate reviews and who has been active, please see http://stackalytics.com/report/contribution/designate-group/30 Designate members, please reply with your vote on the proposed change. Thanks vinod +1 - I think Tim will make a great addition :) +1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.orgmailto: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.orgmailto: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.orgmailto: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.orgmailto: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
