- Community - lists.openinfra.dev

[openstack-community] Regarding Designate-Virtualenv Issues
by Sharma Swati6 13 Nov '15

13 Nov '15

Hi Folks, I am trying to use Designate using Virtualenv approach from the link : http://docs.openstack.org/developer/designate/install/ubuntu-kilo.html#exer… I was able to get the different Designate services started successfully. I have certain environment variables in the virtualenv also- export OS_USERNAME=openstack export OS_PASSWORD=password export OS_TENANT_NAME=myproject export OS_TENANT_ID=123456789 export OS_AUTH_URL=https://127.0.0.1:9001/v2.0/ I then began exercising the API calls. When I am trying to fire this : http://IP.Address:9001/api_version/command , I am doubtful about what IP Address it should be. It did not work with https://127.0.0.1:9001/v2.0/ I also tried 'curl -s checkip.dyndns.org | sed -e 's/.*Current IP Address: //' -e 's/<.*$//' to find out the IP Address but it gives null result for the server address. Can anyone please let me know where does the problem lie? Am I mentioning the IP Address wrong somewhere? Thanks & Regards Swati Sharma System Engineer Tata Consultancy Services Cell:- +91-9717238784 Mailto: sharma.swati6(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1

[openstack-community] Regarding Designate Issues
by Sharma Swati6 10 Nov '15

10 Nov '15

Hi All, I am trying to install Designate using Devstack-Kilo but facing the following issues while starting its services- WARNING keystone.common.wsgi [-] Could not find service: dns WARNING keystone.common.wsgi [-] Could not find project: service DEBUG keystone.middleware.core [-] Auth token not in the request header. Will not build auth context. process_request /opt/stack/keystone/keystone/middleware/core.py:223 I guess all the dependencies are installed for this now (oslo.service, Babel, etc) and PowerDNS is starting properly, but the designate services are still not starting. My query is the same as has been posted here - https://ask.openstack.org/en/question/82412/configuring-designate-in-devsta… Please help me out with the next steps. Thanks & Regards Swati Sharma System Engineer Tata Consultancy Services Ground to 8th Floors, Building No. 1 & 2, Skyview Corporate Park, Sector 74A,NH 8 Gurgaon - 122 004,Haryana India Cell:- +91-9717238784 Mailto: sharma.swati6(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[openstack-community] OpenStack Weekly Community Newsletter (Oct., 31 - Nov., 6)
by Jay Fankhauser 06 Nov '15

06 Nov '15

Superuser TV <http://superuser.openstack.org/articles/section/superuser-tv> Introduced at the Tokyo Summit, Superuser TV offers community and industry insights, plus educational topics to support the OpenStack community. With content ranging from deployments to diversity, from emerging technologies to cloud strategy, Superuser TV is aiming to provide the community with access to a variety of perspectives and knowledge October 2015 user survey highlights increasing maturity of OpenStack deployments <http://superuser.openstack.org/articles/october-2015-user-survey-highlights…> 60 percent of deployments in production and high rates of adoption of OpenStack’s core services are key findings from the report released by the User Committee. The full report can be downloaded here: openstack.org/user-survey <https://www.openstack.org/surveys/landing?BackURL=%2Fsurveys%2Fcurrent> Eliminating “Not-Invented-Here” Syndrome <http://superuser.openstack.org/articles/eliminating-not-invented-here-syndr…> Why embracing this notion is the key to unlock an open data center infrastructure, according to Boris Renski, the co-founder and CMO of Mirantis. Community feedback OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the OpenStack Weekly Community Newsletter or have ideas on how to present content please get in touch: community(a)openstack.org <mailto:community@openstack.org>. Reports from Previous Events OpenStack Summit Tokyo – Final Summary <http://redhatstackblog.redhat.com/2015/11/05/openstack-summit-tokyo-final-s…> Why OpenStack Neutron just grabbed center stage <http://superuser.openstack.org/articles/why-openstack-neutron-just-grabbed-…> Finding your way around OpenStack: professional certification and the project navigator <http://superuser.openstack.org/articles/finding-your-way-around-openstack-p…> Your OpenStack questions answered, a block storage battle and mobile eats the world <http://superuser.openstack.org/articles/your-openstack-questions-answered-a…> Domo arigato Japan! <https://www.blueboxcloud.com/insight/blog-article/domo-arigato-japan> Deadlines and Contributors Notifications Call for papers: OSCON <http://conferences.oreilly.com/oscon/open-source/public/cfp/423> 2016 deadline: November 24, 2015 Continuous Lifecycle London <http://continuouslifecycle.london/call-for-papers/> Deadline: December 1, 2015 PyCon 2016 <https://us.pycon.org/2016/speaking/> deadline: Jan 3, 2016 USENIX Annual Technical Conference 2016 <https://www.usenix.org/conference/atc16/call-for-papers> deadline: February 1, 2016 Security Advisories and Notices None this week Tips ‘n Tricks By Russell Bryant <https://twitter.com/russellbryant>: Open Virtual Network tutorial <http://superuser.openstack.org/articles/open-virtual-network-tutorial> By Gal Sagie: What you need to know about Dragonflow for the OpenStack Liberty release <http://superuser.openstack.org/articles/what-you-need-to-know-about-dragonf…> Upcoming Events <https://www.openstack.org/community/events> Nov 07, 2015 OSATH – FOSSCOMM 2015 Aigaleo, GR <http://www.meetup.com/Athens-OpenStack-User-Group/events/226479917/> Nov 11, 2015 whereis instance_ha + OpenStack Tokyo Summit Recap <http://www.meetup.com/Australian-OpenStack-User-Group/events/220202353/> Nov 12, 2015 8. Meetup, Konu: OpenStack Plugin Development 101 Ankara, TR <http://www.meetup.com/Turkey-OpenStack-Meetup/events/225419513/> What you need to know from the developer’s list Success Bot Says <https://wiki.openstack.org/wiki/Successes> calebb: Shade now supports volume snapshots pleia2: Launched code search [1]. sdague: grenade-multinode live upgrade tests now running on nova non voting AJaeger: Contributors guide is published [2]. Tell us yours via IRC with a message “#success [insert success]” Upgrading Elastic Search Cluster Monday <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078314.html> November 9th 1700UTC Requires a cluster restart, in which people won’t be able to do searches during that time. New features from upgrade: Aggregations Rolling upgrades within a major release Should improve performance Release Team Communication Changes <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078277.html> IRC channel change from #openstack-relmgr-office to #openstack-release “Office hours” are being dropped. Just drop by the channel or on the dev list with subject containing “[release]” anytime you need something. Deprecation for Untagged Code <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078336.html> Ironic tries to keep master backwards compatible. There are deployers doing continuous deployments of Ironic off of master. Based on the deprecation tag policy [3], it only covers released and tagged code, but not unreleased code or features introduced in an intermediate release. A proposal [4] by Jim: Three month deprecation period is needed for features that were never released. A feature that was introduced in a intermediate release needs to be deprecated in the next intermediate release or coordinated release, and supported until the next release and 3 months. Outcome of Distributed Lock Manager Discussion @ the Summit <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078214.html> There was a two part session at the summit [5] Previously, there was an unwritten policy that DLMs should be optional, which led to writing poor DLM-like things backed by databases. Continuing our existing pattern of usage like databases and message-queues, we’ll use an oslo abstraction layer: tooz [6]. Current OpenStack project requirements that surfaced in discussion for DLMs, it’s likely that Consul, Etcd and Zoo Keeper will be fine to use via Tooz. No project required a fair locking implementation in the DLM. We want to avoid the situation of unmaintained drivers. We adopted a similar requirement from oslo.messaging driver requirements [7]: Two developers responsible for it Gating functional tests that use dsvm Test drivers in-tree need to be clearly referenced as a test driver in the module name. Davanum brings in Devstack ZooKeeper support [8]. An etcd driver is in review for Tooz [9]. A Consul driver in Tooz is also planned [10]. Concerns raised about the default DLM driver being ZooKeeper: It’s a new platform for operators to understand We don’t know how well ZooKeeper will work with openjvm as oppose to Oracle’s JVM. Troubleshooting Cross-Project Communication <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078138.html> Evolve the current cross-project meeting to an “as needed” rotation, held at any time on Tuesdays or Wednesdays. Based on feedback [11] it’s difficult to have meetings at different times on Tuesday and Wednesdays. There was consensus that the meeting can be “as needed” on Tuesday, and that most announcements will happen in the mailing list, and sometimes show up in this weekly Dev List Summary. API For Getting Only Status of Resources <http://lists.openstack.org/pipermail/openstack-dev/2015-November/078318.html> Projects like Heat,Tempest, Rally, and other projects that work with resources are polling for updates on asynchronous operations. Boris proposes having API’s expose the ability to just get the status by UUID, instead of fetching all data on a resource. Clint suggests instead of optimizing for polling, we should revisit the proposal for a pub/sub model, so users can subscribe to updates for resources. Sean suggests near term work around is to actually use Searchlight, which today monitors the notification bus for Nova. Searchlight is hitting the Nova API more than ideal, but at least it’s one service. Longer term we need a dedicated event service in OpenStack. Everyone wants web sockets, but anticipating 10,000+ open web sockets, this isn’t just a bit of python code, but a highly optimized server underneath. [1] – http://codesearch.openstack.org/ <http://codesearch.openstack.org/> [2] – http://docs.openstack.org/contributor-guide <http://docs.openstack.org/contributor-guide> [3] – https://review.openstack.org/#/c/242117/1 <https://review.openstack.org/#/c/242117/1> [4] – https://review.openstack.org/#/c/242117/1 <https://review.openstack.org/#/c/242117/1> [5] – https://etherpad.openstack.org/p/mitaka-cross-project-dlm <https://etherpad.openstack.org/p/mitaka-cross-project-dlm> [6] – https://pypi.python.org/pypi/tooz <https://pypi.python.org/pypi/tooz> [7] – https://review.openstack.org/#/c/240645/ <https://review.openstack.org/#/c/240645/> [8] – https://review.openstack.org/#/c/241040/ <https://review.openstack.org/#/c/241040/> [9] – https://review.openstack.org/#/c/151463/ <https://review.openstack.org/#/c/151463/> [10] – https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver <https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver> [11] – http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015… <http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015…>

1 0

[openstack-community] YUM server question
by Wilson Kwok 05 Nov '15

05 Nov '15

Hello all, We're testing RDO in our school lab, but the network have QoS, when 30 students downloading RDO caused network connection lost. We're thinking to download RDO to our YUM server, and then students download RDO from this YUM server to avoid this issue. Can someone tell me how to do with YUM server ? thanks.

3 2

[openstack-community] Houston OpenStack Meetup: Deploying OpenStack with OSA
by OpenStack Texas 04 Nov '15

04 Nov '15

Hello everyone, If you know of anyone in Houston, TX or will be in Houston on or around the 17th of November, join us for a talk with Walter Bentley on using Ansible to deploy your OpenStack cluster. More details available here: http://www.meetup.com/openstackhoustonmeetup/events/226009298/ Kind regards, OpenStack Houston Meetup

1 0

[openstack-community] Tokyo Session for User Group & OpenStack Days Leaders
by Lauren Sell 23 Oct '15

23 Oct '15

Hi everyone, I wanted to give you a heads up that we have a working group session planned Wednesday at 3:40 pm, and would like to get as much participation and feedback from User Group leaders and OpenStack Day organizers as possible. http://sched.co/4Nyj <https://www.openstack.org/summit/tokyo-2015/schedule/main-conference> More than a year ago, Tom Fifield and others in the community kicked off a process to help identify and define “official" user groups in an effort to encourage high quality, sustainable and community-driven groups around the world. We have since created the user groups portal (groups.openstack.org <http://groups.openstack.org/>) and began on boarding dozens of groups, but have yet to pull the trigger on the “official” user group designation. One thing that has been missing is an official user group logo, which is an important part of the recognition and signal to community members. In April, we developed several options for official User Group and OpenStack Days logos and solicited feedback via a community survey. The logo options had the OpenStack colors and word mark, but not the traditional OpenStack “O” icon. The feedback was pretty neutral on the logos produced, with the primary request being to incorporate the “O” icon. After receiving the feedback, we stalled out due to bandwidth around the Vancouver Summit, but now have a proposed user group logo with the “O” icon and are ready to move the program forward. Please join us Wednesday afternoon in Tokyo to voice your opinion and learn how to participate. The primary goal for this session is to dust off the official user group process and make sure everyone is on board, so we can begin recognizing official user groups with the new proposed branding as soon as possible. We would also like to discuss how the OpenStack Days programs and branding will evolve alongside it (openstack.org/event-policy) Finally, we would like to brainstorm other programs or funding opportunities that the Foundation can offer to help support official user groups — so please come with ideas for what would make the biggest impact in your local community. We’ll of course be sharing notes after the fact via the community mailing list. Thanks, Lauren

2 1

[openstack-community] #WeAreOpenStack
by Allison Price 22 Oct '15

22 Oct '15

Hi everyone, At the OpenStack Summit Tokyo, we are kicking off a social media initiative to promote diversity and inclusivity within the OpenStack community. This idea was developed by the Women of OpenStack, and we encourage everyone in the community, even if you aren’t able to attend the Summit, to join in! To participate, use the hashtag #WeAreOpenStack on Twitter, Facebook or Instagram to show what the OpenStack community means to you. Posts can include pictures of you with fellow community members or your perspective of being a part of the community. The OpenStack Summit Tokyo is simply going to be the launch of this hashtag, but after the Summit, continue to use the hashtag at different OpenStack events, including OpenStack Days, meetups and even day-to-day activities with your fellow Stackers. Cheers, Allison

1 0

[openstack-community] OpenStack Community Open Space at the Tokyo Summit
by Sharone Zitzman 20 Oct '15

20 Oct '15

Hi Everyone, I'm very excited to be making my way to my first OpenStack Summit, despite organizing the OpenStack Israel community for a number of years now (annual event, meetup, and web presence). I think this is an excellent opportunity to leverage the diversity of community leaders from around the globe all being in the same place and I wanted to attempt to organize an on the ground "open space" meeting - i.e. an ad hoc, informal, brainstorming session - where we can all learn from each other about what we're doing on the ground, and from each other's experience. I have created a global OpenStack community Facebook group, so we can all have a place to collaborate: https://www.facebook.com/groups/637144716425889/ And have scheduled an on the ground event for Wednesday October 28th at 10:00 AM - which is between other conference community sessions at the summit. https://www.facebook.com/events/933499416688213/ You are all invited to join both the group and the meetup. Looking forward to meeting you all there. Warm Regards, Sharone Zitzman @shar1z <http://www.twitter.com/shar1z> -- [image: photo] <http://getcloudify.org/?utm_source=EML-SIG&utm_medium=EML&utm_term=SIG-CFY&…> *Sharone Zitzman* Community & Growth Lead - Cloudify, GigaSpaces +972-54- <+972-54-22-66-463>559-9104 | sharoner(a)gigaspaces.com | http://getcloudify.org <http://getcloudify.org/?utm_source=EML-SIG&utm_medium=EML&utm_term=SIG-CFY&…> <https://il.linkedin.com/in/sharonez> <http://twitter.com/shar1z> <https://github.com/shar1z> <http://getcloudify.org/authors/sharone-zitzman/?utm_source=EML-SIG&utm_medi…> -- [image: photo] <http://getcloudify.org/?utm_source=EML-SIG&utm_medium=EML&utm_term=SIG-CFY&…> *Sharone Zitzman* Community & Growth Lead - Cloudify, GigaSpaces +972-54- <+972-54-22-66-463>559-9104 | sharoner(a)gigaspaces.com | http://getcloudify.org <http://getcloudify.org/?utm_source=EML-SIG&utm_medium=EML&utm_term=SIG-CFY&…> <https://il.linkedin.com/in/sharonez> <http://twitter.com/shar1z> <https://github.com/shar1z> <http://getcloudify.org/authors/sharone-zitzman/?utm_source=EML-SIG&utm_medi…>

1 0

[openstack-community] OpenStack Weekly Community Newsletter (Oct., 10-16)
by Jay Fankhauser 16 Oct '15

16 Oct '15

Liberty, the 12th release of OpenStack, came out yesterday <https://www.openstack.org/software/liberty/> With 1,933 individual contributors and 164 organizations contributing to the release, Liberty offers finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies such as containers in production environments: Learn what’s new <http://superuser.openstack.org/articles/openstack-liberty-a-primer-on-what-…> Break down those silos, OpenStack <http://superuser.openstack.org/articles/break-down-those-silos-openstack> “The projects need to come together to develop consistent formats, approaches and messaging,” says Rochelle Grober, senior software architect at Huawei Technologies and active member of the OpenStack community. The Road to Tokyo The OpenStack Summit Tokyo will sell out! Register NOW! <https://www.eventbrite.com/e/openstack-summit-october-2015-tokyo-tickets-17…> The schedule and mobile app for the OpenStack Summit in Tokyo are now available <https://www.openstack.org/summit/tokyo-2015/schedule/> If you have already downloaded an OpenStack Summit mobile app before, no need to do it again! Just refresh your existing app. OpenStack training sessions available in Tokyo <https://www.openstack.org/blog/2015/10/openstack-training-sessions-availabl…> Several ecosystem companies are offering training in Tokyo during the week of the Summit. Check out the sessions available and plan your travel accordingly The Summit maps are now available online <https://www.openstack.org/summit/tokyo-2015/campus-maps> Speakers, sponsors, and ATC registration codes deactivate 10/19, so register now <https://www.eventbrite.com/e/openstack-summit-october-2015-tokyo-tickets-17…>! If the OpenStack Summit Tokyo is going to be your first summit, check out these helpful tips and info: https://www.openstack.org/summit/tokyo-2015/new-to-the-summit/ <https://www.openstack.org/summit/tokyo-2015/new-to-the-summit/> We have created videos and PDF downloads <https://www.openstack.org/summit/tokyo-2015/tokyo-and-travel/#hotels> to help you navigate from either of the Tokyo airports to the Summit venue. Community feedback OpenStack is always interested in feedback and community contributions, if you would like to see a new section in the OpenStack Weekly Community Newsletter or have ideas on how to present content please get in touch: community(a)openstack.org <mailto:community@openstack.org>. Reports from Previous Events None this week Deadlines and Contributors Notifications Outreachy Mentorship Application deadline: Nov., 02, 2015, 07:00 pm UTC <https://www.gnome.org/outreachy/> Call for papers: FOSDEM’16 <https://fosdem.org/2016/news/2015-09-24-call-for-participation/> deadline: October 30, 2015 OSCON <http://conferences.oreilly.com/oscon/open-source/public/cfp/423> 2016 deadline: November 24, 2015 Continuous Lifecycle London <http://continuouslifecycle.london/call-for-papers/> Deadline: December 1, 2015 PyCon 2016 <https://us.pycon.org/2016/speaking/> deadline: Jan 3, 2016 USENIX Annual Technical Conference 2016 <https://www.usenix.org/conference/atc16/call-for-papers> deadline: February 1, 2016 Security Advisories and Notices None this week Tips ‘n Tricks By Nir Yechiel and Jiri Benc: Troubleshooting Networking with RHEL OpenStack Platform: meet ‘plotnetcfg’ <http://redhatstackblog.redhat.com/2015/10/15/troubleshooting-networking-wit…> Upcoming Events <https://www.openstack.org/community/events> Oct 17, 2015 OpenStack中的SaaS Beijing, CN <http://www.meetup.com/China-OpenStack-User-Group/events/225801881/> Oct 19 – 20, 2015 OpenStack Octoberfest! Minneapolis, MN, US <http://www.meetup.com/Minnesota-OpenStack-Meetup/events/224638648/> Oct 19 – 20, 2015 OpenStack BoF at All Things Open! Raleigh, NC, US <http://www.meetup.com/Triangle-OpenStack-Meetup/events/226055043/> Oct 20, 2015 Easy OpenStack: SolidFire+Platform9 Sunnyvale, California, US <http://www.meetup.com/Triangle-OpenStack-Meetup/events/226055043/> Oct 20, 2015 Stateless OS: From an OpenStack Perspective & Creacion de Plugins para Tempest Guadalajara, MX <http://www.meetup.com/OpenStack-GDL/events/225875446/> Oct 21, 2015 OpenStack 2015 October <http://www.meetup.com/OpenStack-Hungary-Meetup-Group/events/225260922/> Oct 21 – 22, 2015 Bi-modal IT & OpenStack (#26) Washington D.C., DC, US <http://www.meetup.com/OpenStackDC/events/224954102/> Oct 22 – 23, 2015 October monthly meetup Chesterfield, MO, US <http://www.meetup.com/OpenStack-STL/events/225819101/> What You Need to Know From the Developer’s List Success Bot Says <https://wiki.openstack.org/wiki/Successes> ttx: Another OpenStack Release! With help of jesusaurus, the infra team has deployed Kibana 3. First steps in upgrading elastic search cluster. shamail: Product Working Group wiki fully updated [1] tristanC: 6 new TC members have been elected[2] AJaegar: OpenStack API Quick Start converted to RST [3], and translated to German [4] and Japanese [5]. reed: section 2 and 3 of the OpenStack Shade tutorial merged. Now work on section [6]. sirushti: Heat just announced support for Python 3.4 [7]. AJaegar: All Documentation manuals have been updated with content for Liberty [8]. Upgrade to Gerrit 2.11 <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076962.html> The OpenStack Infra team would like to upgrade from Gerrit 2.8 to 2.11. Proposing to do the upgrade shortly after the Mitaka summit. Motivation: Take advantage of some of the new REST API, ssh commands, and stream events features. There is a big UI change in 2.11, in which 2.8 includes both the old and new style. Preview 2.11 [9]. If you don’t like Gerrit 2.11, give Gertty [10] a try. Service Catalog: The Next Generation (Cont.) <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076592.html> Continuing from last week summary… <http://www.openstack.org/blog/2015/10/openstack-weekly-community-newsletter…> Sean Dague realizes that while people want to go in much more radical directions here, we should be careful. This is not a blank slate, as there are enough users using it that we must do careful shifts that enable a new thing similar to the old thing. Moving away from REST is too much, at least in the next 6 to 12 months. Getting a service catalog over REST without auth, or tenant IDs gets us somewhere to figure out a DNS representation. Establishing Release Liaisons for Mitaka <http://lists.openstack.org/pipermail/openstack-dev/2015-October/077033.html> Doug Hellmann writes that the release management team relies on liaisons from each project to be available for coordination for work across all teams. Responsibilities of release liaisons [11]. Signup [12]. Release Communication During Mitaka <http://lists.openstack.org/pipermail/openstack-dev/2015-October/077033.html> Doug Hellmann begins one of many emails describing difference in the way we handle release management for the Mitaka cycle. In the past, we’ve had communication issues where project team leads didn’t see or pay attention to release related announcements. This email was sent to the list and individual project team leads, to improve the odds that all will see it. “[release]” topic tag on the openstack-dev mailing list will be used. All project team leads and release liaison should configuring their email client to ensure the messages are visible. Requests + urllib3 + distro package (cont.) <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076518.html> Continuing discussions from last week… <http://www.openstack.org/blog/2015/10/openstack-weekly-community-newsletter…> Robert Collins comments a trivial workaround is to always use virtualenvs and not system-site-packages. Has OpenStack infra team considered using system-site-packages? Yes, but we take advantage of the python ecosystem uploading new releases to PyPI. We can then pretty instantly test compatibility of our software with new releases of dependencies. A way forward is: Get distros to fix their requests python dependencies Ubuntu [13] Fedora [14][15][16] Fix existing known bugs in pip where such dependencies are violated by some operations. Stop using vendorized version of requests and fork the project to use dependencies it should from the start. Convince upstream to stop vendorizing urllib3. Always use distro packages of requests, never from virtual environments. Scheduler Proposal (cont.) <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076373.html> Continuing from last week’s summary… <http://www.openstack.org/blog/2015/10/openstack-weekly-community-newsletter…> Ed notes that Josh Harlow’s solution isn’t too different than the current design of hosts sending their state to the scheduler. The reason for Cassandra proposal was to eliminate the duplication and have resources being scheduler and the scheduler itself all working with the same data. This is the intent of the current design. The data can never be perfect, so work with what you have and hope the rest of the system deals with your mistakes and gracefully retry. (e.g. scheduled compute node no longer has resources to accommodate a request.) To make this solution possible for downstream distributions and/or OpenStack users) you have to solve: Cassandra developers upstream should start caring about OpenJDK. Or Oracle should make its JVM free software. Clint notes that Cassandra does not recommend OpenJDK [17]. Thomas adds: Upstream does not test against OpenJDK. They close bugs without fixing them when it only affects OpenJDK. Thierry is generally negative about Java solutions as this being one of the reasons [18]. The free software JVM is not on par with the non-free JVM. We then indirectly force our users to use a non-free dependency. When the java solution is the only solution for a problem space, that might still be a good trade-off versus reinventing the wheel. However, for distributed locks and sharing state, there are some other good options out there. Clint mentions that Zookeeper is different from Cassandra. He has had success with OpenJDK. It’s also available on Debian/Ubuntu making access for developers much easier. [1] – https://wiki.openstack.org/wiki/ProductTeam <https://wiki.openstack.org/wiki/ProductTeam> [2] – https://wiki.openstack.org/wiki/TC_Elections_September/October_2015#Results <https://wiki.openstack.org/wiki/TC_Elections_September/October_2015#Results> [3] – http://developer.openstack.org/api-guide/quick-start/ <http://developer.openstack.org/api-guide/quick-start/> [4] – http://developer.openstack.org/de/api-guide/quick-start/ <http://developer.openstack.org/de/api-guide/quick-start/> [5] – http://developer.openstack.org/api-guide/quick-start/ <http://developer.openstack.org/api-guide/quick-start/>[6] – https://review.openstack.org/#/c/232810/ <https://review.openstack.org/#/c/232810/> [7] – https://review.openstack.org/231557 <https://review.openstack.org/231557> [8] – http://docs.openstack.org/liberty/ <http://docs.openstack.org/liberty/> [9] – http://review-dev.openstack.org <http://review-dev.openstack.org/> [10] – https://pypi.python.org/pypi/gertty <https://pypi.python.org/pypi/gertty> [11] – http://docs.openstack.org/project-team-guide/release-management.html#releas… <http://docs.openstack.org/project-team-guide/release-management.html#releas…> [12] – https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management <https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management> [13] – https://bugs.launchpad.net/ubuntu/+source/python-requests/+bug/1505038 <https://bugs.launchpad.net/ubuntu/+source/python-requests/+bug/1505038> [14] – https://bodhi.fedoraproject.org/updates/FEDORA-2015-20de3774f4 <https://bodhi.fedoraproject.org/updates/FEDORA-2015-20de3774f4> [15] – https://bodhi.fedoraproject.org/updates/FEDORA-2015-1f580ccfa4 <https://bodhi.fedoraproject.org/updates/FEDORA-2015-1f580ccfa4> [16] – https://bodhi.fedoraproject.org/updates/FEDORA-2015-d7c710a812 <https://bodhi.fedoraproject.org/updates/FEDORA-2015-d7c710a812> [17] –https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StartupChecks.java#L153-L155 <https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandr…> [18] – https://twitter.com/mipsytipsy/status/596697501991702528 <https://twitter.com/mipsytipsy/status/596697501991702528>

1 0

[openstack-community] Outreachy: Call for Funding, Mentors
by Lauren Sell 12 Oct '15

12 Oct '15

Hi everyone, Quick update on the Outreachy <https://www.gnome.org/outreachy/> program, including a request for funding and volunteer mentors. For those of you who are not aware, Outreachy helps people from groups underrepresented in free and open source software get involved by matching interns with established mentors in the upstream community. There have been a record 30 intern applicants and 11 volunteer mentors for OpenStack this next cycle, which will take place Dec 7, 2015 - March 7, 2016. The OpenStack program coordinators could use a few more volunteer mentors, and there has been specific interest in Ceilometer, Cinder, Horizon, Murano, Neutron, Nova, Sahara and Zaqar. You can learn more about what is expected from mentors and how to apply here: https://wiki.openstack.org/wiki/Outreachy/Mentors <https://wiki.openstack.org/wiki/Outreachy/Mentors> Additionally, the Foundation agreed to sponsor five interns, but we could use some additional sponsors to help support the large increase in OpenStack applicants. The sponsorship cost is 6,500 USD per intern, which provide them a stipend for the three-month program. You can learn more about sponsorship here: https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs#Action <https://wiki.gnome.org/Outreachy/Admin/InfoForOrgs#Action> I personally believe Outreachy is one of the most important and effective diversity efforts we’ve invested in to date. We’ve had some amazing graduates become long-term contributors to our community. I cannot give enough praise and thanks to the program coordinators (Victoria Martinez de la Cruz and Mahati Chamarthy for OpenStack), volunteer mentors, and sponsors for making it possible. Please help spread the word. If you are interested in becoming a mentor or sponsoring an intern, please contact Victoria (victoria(a)vmartinezdelacruz.com <mailto:victoria@vmartinezdelacruz.com>) or me (lauren(a)openstack.org <mailto:lauren@openstack.org>). Thanks, Lauren

5 5