- Community - lists.openinfra.dev

[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

[openstack-community] OpenStack Weekly Community Newsletter (Oct. 3 – Oct. 9)
by Jay Fankhauser 09 Oct '15

09 Oct '15

What you need to know about Astara <http://superuser.openstack.org/articles/what-you-need-to-know-about-astara> Henrik Rosendahl, CEO of Akanda, introduces OpenStack's newest project, an open-source network orchestration platform built by OpenStack operators for OpenStack clouds. An OpenStack security primer <http://superuser.openstack.org/articles/an-openstack-security-primer> Meet the troubleshooters and firefighters of the OpenStack Security project and how you can get involved. 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…>! <http://superuser.openstack.org/articles/coming-soon-superuser-tv> 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 Liberty Release Oct., 15, 2015 <https://wiki.openstack.org/wiki/Liberty_Release_Schedule> 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 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 Superuser Awards: your vote counts <http://superuser.openstack.org/articles/superuser-awards-your-vote-counts> (voting closes on 10/12 at 11:59 pm PT) Vote for one of the four finalists: FICO <http://superuser.openstack.org/articles/tokyo-superuser-awards-finalist-fico>, GoDaddy <http://superuser.openstack.org/articles/tokyo-superuser-awards-finalist-god…>, Lithium Technologies <http://superuser.openstack.org/articles/tokyo-superuser-awards-finalist-lit…>, or NTT <http://superuser.openstack.org/articles/tokyo-superuser-awards-finalist-ntt…>. The winner will be announced at the Tokyo Summit. (Vote here <https://www.surveymonkey.com/r/SuperuserAwards>) Security Advisories and Notices [openstack-announce] [OSSA 2015-021] Nova network security group changes are not applied to running instances (CVE-2015-7713) <http://lists.openstack.org/pipermail/openstack-announce/2015-October/000683…> Tips ‘n Tricks By Belmiro Moreira: Scheduling and disabling Cells <http://openstack-in-production.blogspot.com/2015/10/scheduling-and-disablin…> Upcoming Events <https://www.openstack.org/community/events> Oct 10, 2015 OpenStack India Meetup, Pune Pune, IN <http://www.meetup.com/Indian-OpenStack-User-Group/events/225039190/> Oct 12, 2015 OpenStack Cinder deep dive Stockholm, SE <http://www.meetup.com/Indian-OpenStack-User-Group/events/225039190/> Oct 13, 2015 Pub Gathering Manchester, GB <http://www.meetup.com/Manchester-OpenStack-Meetup/events/224421141/> Oct 14 - 15, 2015 Monolithic to Cloud-Native Apps: Lessons Learned by HP/ Neutron with Akanda <http://www.meetup.com/OpenStack-New-York-Meetup/events/225737696/> Oct 14, 2015 3. Istanbul Meetup: OpenStack'de Ceph Storage kullanimi Istanbul, TR <http://www.meetup.com/Turkey-OpenStack-Meetup/events/225916298/> Oct 14, 2015 教你玩東京~~東京高峰會介紹Taipei, TW <http://www.meetup.com/OpenStack-Taiwan-User-Group/events/225859043/> Oct 15, 2015 OpenStack Howto part 7 - Data Processing Prague, CZ <http://www.meetup.com/OpenStack-Czech-User-Group-Meetup/events/222955596/> What you need to know from the developer's list (WIP) Success Bot Says <https://wiki.openstack.org/wiki/Successes> harlowja: The OpenStack Universe [1] krotscheck: OpenStack CI posted first package to NPM [2] markvan: OpenStack Chef Cookbook team recently put in place all the pieces to allow for a running a full (devstack like) CI test against all the cookbook projects commits. proton driver running with Kerberos for encryption and authentication Tell us yours via IRC with a message "#success [insert success] Proposed Design Summit allocation <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076000.html> Track layout is on the official schedule [3]. PTLs or liaisons can start pushing up schedule details. The wiki [4] explains how. Reach out to ttx or thingee on IRC if there are any issues. Devstack extras.d support going away M-1 <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076310.html> Sean Dague mentions extras.d is devstack plugins, and has existed for 10 months. Projects should prioritize getting to the real plugin architecture. Sean compiled a list of the top 25 jobs (by volume) that giving warnings of breaking [5]. Naming N and O Release Now <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076327.html> Sean Dague suggests since we already have the locations for N and O summits, we should start the name polls now. Carol Barrett mentions that the current release naming process only allows the release to be named is announced and no sooner than the opening of development of the previous release [6]. Consensus is made to have this changed. Monty mentions this option was discussed in the past, but it was changed because we wanted to keep a sense of ownership by the people who actually worked on the release. Sean will propose this to the next group of TC members. Requests + urllib3 + distro packages <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076518.html> Problems: Requests python library has very very specific versions of urllib3 it works with. So specific that they aren't always released. Linux vendors often unbundle urllib3 from requests and then apply what patches were needed to their urllib3 while not updating their requests package dependencies. We use urllib3 and requests in some places, but don't mix them up. If we have a distro-alterted requests + pip installed urllib3, request usually breaks. Lots of places the last problem can happen; they all depend on us having a dependency on requests that is compatible with the version installed by the distro, but a urllib3 dependency that triggers an upgrade of just urllib3. When constraints are in use, the requests version has to match the distro requests version exactly, but that will happen from time to time. Examples include: DVSM test jobs where the base image already has python-requests installed. Virtualenvs where the system-site-packages are enabled. Solutions: Make sure none of our testing environments include distro requests packages. Monty notes we're working hard to make this happen. Make our requirements be tightly matched to what requests needed to deal with unbundling. In progress by Matt Riedemann [7]. Teach pip how to identify and avoid this situation by always upgrading requests. Get the distros to stop un-vendoring urllib3. [1] - https://gist.github.com/harlowja/e5838f65edb0d3a9ff8a [2] - https://www.npmjs.com/package/eslint-config-openstack [3] - https://mitakadesignsummit.sched.org/ [4] - https://wiki.openstack.org/wiki/Design_Summit/SchedulingForPTLs [5] - http://lists.openstack.org/pipermail/openstack-dev/2015-October/076559.html [6] - http://governance.openstack.org/reference/release-naming.html [7] - https://review.openstack.org/#/c/213310/

1 0

[openstack-community] OpenStack Community Weekly Newsletter (September 28 - October 2)
by Allison Price 02 Oct '15

02 Oct '15

53 things that are new in OpenStack Liberty <https://www.mirantis.com/blog/53-things-new-openstack-liberty/> Another autumn, another OpenStack release. OpenStack’s 12th release, Liberty, is due on October 15, and release candidates are already being made available. But what can we expect from the last six months of development? App Developers: First App on OpenStack Tutorial Needs You <http://superuser.openstack.org/articles/app-developers-first-app-on-opensta…> The tutorial that guides new developers to deploy their first application on OpenStack is complete for Apache Libcloud and needs help for new languages and SDKs. The Road to Tokyo The OpenStack Summit Tokyo will sell out! Register NOW! <https://openstacksummitoctober2015tokyo.eventbrite.com/> The deadline to request transfers and refunds is October 12. Please email summitreg(a)openstack.org <mailto:summitreg@openstack.org> with any requests or questions. The schedule and mobile app for the OpenStack Summit in Tokyo are now available <https://www.openstack.org/summit/tokyo-2015/schedule/> Speakers, sponsors, and ATC registration codes must be redeemed by October 19 at 11:59 p.m. PT, so register now! 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 Liberty Release Oct., 15, 2015 <https://wiki.openstack.org/wiki/Liberty_Release_Schedule> Security Advisories and Notices [openstack-announce] [OSSA 2015-020] Glance storage overrun (CVE-2015-5286) <http://lists.openstack.org/pipermail/openstack-announce/2015-September/0006…> Tips ‘n Tricks By Augustina Ragwitz <http://hackhackblog.blogspot.com/2015/09/my-first-openstack-infra-patch.html>: Hack hack hack the way to your first OpenStack patch <http://superuser.openstack.org/articles/hack-hack-hack-the-way-to-your-firs…> By Scott Lowe: Using Docker Machine with OpenStack <http://superuser.openstack.org/articles/using-docker-machine-with-openstack> Upcoming Events <https://www.openstack.org/community/events> Oct 04 – 08, 2015 Gartner SymposiumITxpo Orlando, FL, US <http://www.gartner.com/events/na/orlando-symposium> Oct 06, 2015 October Sydney Meetup <http://www.meetup.com/Australian-OpenStack-User-Group/events/220202327/> Oct 07, 2015 Houston OpenStack Meetup Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/?eventId=2248…> Oct 07 – 08, 2015 OpenStack Liberty Release Richardson, TX, US <http://www.meetup.com/OpenStack-DFW/events/225014699/> Oct 07 – 08, 2015 OpenStack 101 Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/> Oct 08, 2015 7. Meetup, Konu : Murano - OpenStack App Catalog Ankara, TR <http://www.meetup.com/Turkey-OpenStack-Meetup/events/225419496/> Oct 08 - 09, 2015 Neutron apollozza! New date! New Location! Austin, TX, US <http://www.meetup.com/OpenStack-Austin/events/225479349/> Oct 10, 2015 OpenStack India Meetup, Pune, IN <http://www.meetup.com/Indian-OpenStack-User-Group/events/225039190/> Oct 12, 2015 OpenStack Cinder deep dive Stockholm, SE <http://www.meetup.com/OpenStack-User-Group-Nordics/events/225365322/> What you need to know from the developer’s list PTL election results are in! https://wiki.openstack.org/wiki/PTL_Elections_September_2015#Results <https://wiki.openstack.org/wiki/PTL_Elections_September_2015#Results> Proposed Design Summit track/room/time allocation <http://lists.openstack.org/pipermail/openstack-dev/2015-October/076000.html> http://tinyurl.com/mitaka-design-summit <http://tinyurl.com/mitaka-design-summit> If anyone sees any glaring issues, they should reach out to Thierry Carrez.

1 0

[openstack-community] September 29 Price Increase - OpenStack Summit Tokyo
by Kendall Waters 28 Sep '15

28 Sep '15

Hi everyone, Just a reminder that the registration price for the Tokyo Summit will INCREASE to $1,000 USD next Tuesday, September 29th at 11:59pm (PT). Register HERE <https://openstacksummitoctober2015tokyo.eventbrite.com/> before the price increases! Also, all discount registration codes will expire on October 19, 2015 at 11:59pm (PT) (This applies to speakers, ATCs, sponsors, etc.) Cheers, Kendall VISA INFORMATION: If you require a visa to travel to Japan, please carefully read the instructions HERE <https://www.openstack.org/summit/tokyo-2015/tokyo-and-travel/#visa>. The entire visa process can take up to 5 weeks to complete so APPLY NOW 1. First, you will need to have booked your flights, hotel accommodation, and Summit registration BEFORE applying for visa invitation support 2. Then complete the visa request form on the Summit Tokyo and Travel Page HERE <https://openstack.formstack.com/forms/visa_request_form> 3. Receive a hardcopy of your visa invitation documents in the mail and apply for a visa at your local Japanese embassy or consulate 4. Wait for your visa to be issued, which may take up to 10 business days and pick it up from the embassy All visa requests must be made before October 1.

1 1

[openstack-community] OpenStack Weekly Community Newsletter (Sept.,19 – 25)
by Jay Fankhauser 25 Sep '15

25 Sep '15

Register for OpenStack Summit Tokyo 2015 <https://www.eventbrite.com/e/openstack-summit-october-2015-tokyo-tickets-17…> Full access registration prices increase on 9/29 at 11:59pm PT This trove of user stories highlights what people want in OpenStack <http://superuser.openstack.org/articles/this-trove-of-user-stories-highligh…> The Product Working Group recently launched a Git repository to collect requirements ranging from encrypted storage to rolling upgrades. How storage works in containers <http://superuser.openstack.org/articles/how-storage-works-in-containers> Nick Gerasimatos, senior director of cloud services engineering at FICO, dives into the lack of persistent storage with containers and how Docker volumes and data containers provide a fix. The Road to Tokyo Get your OpenStack Summit Tokyo visa in five steps: Deadline for Visa invitation requests is 10/1 <http://superuser.openstack.org/articles/get-your-openstack-summit-tokyo-vis…> The schedule and mobile app for the OpenStack Summit in Tokyo are now available <https://www.openstack.org/summit/tokyo-2015/schedule/> 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 Heats Up Silicon Valley <https://developer.ibm.com/opentech/2015/09/20/openstack-heats-up-silicon-va…> OpenStack Day Benelux 2015 <http://superuser.openstack.org/articles/openstack-day-benelux-2015> Deadlines and Contributors Notifications Liberty Release Oct., 15, 2015 <https://wiki.openstack.org/wiki/Liberty_Release_Schedule> Security Advisories and Notices [openstack-announce] [OSSA 2015-019] Glance image status manipulation (CVE-2015-5251) <http://lists.openstack.org/pipermail/openstack-announce/2015-September/0006…> Tips ‘n Tricks By Swapnil Kulkarni <http://blog.coolsvap.net/>: [OpenStack][RDO] Liberty Test-Day <http://blog.coolsvap.net/2015/09/24/openstackrdo-test-day-liberty/> Upcoming Events <https://www.openstack.org/community/events> Sep 28, 2015 – Jan 3, 2016 Presenting At PyCon (call for papers) Portland,OR, US <https://us.pycon.org/2016/speaking/> Sep 29 – 30, 2015 Cloud Storage in OpenStack <https://groups.openstack.org/groups/frederick-md/cloud-storage-openstack> Oct 01, 2015 OpenStack Meetup Cluj Cluj-Napoc, Cluj, RO <http://www.meetup.com/OpenStackRomania/events/222910344/> Oct 01, 2015 South Bay OpenStack Meetup, Beginner track San Francisco, CA, US <http://www.meetup.com/openstack/events/221806052/> Oct 01 – 02, 2015 October OpenStack Meetup – SDN and Containers Chicago, IL, US <http://www.meetup.com/meetup-group-NjZdcegA/events/225081881/> Oct 04 – 08, 2015 Gartner SymposiumITxpo Orlando, FL, US <http://www.gartner.com/events/na/orlando-symposium> Oct 06, 2015 October Sydney Meetup <http://www.meetup.com/Australian-OpenStack-User-Group/events/220202327/> Oct 07, 2015 Houston OpenStack Meetup Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/?eventId=2248…> Oct 07 – 08, 2015 OpenStack Liberty Release Richardson, TX, US <http://www.meetup.com/OpenStack-DFW/events/225014699/> Oct 07 – 08, 2015 OpenStack 101 Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/>What you need to know from the developer’s list Handling Projects with no PTL candidates <http://lists.openstack.org/pipermail/openstack-dev/2015-September/075227.ht…> The technical committee will appoint a PTL [1] if there is no identified eligible candidate. Appointed PTLs: Robert Clark nominated security PTL Serg Melikyan nominated Murano PTL Douglas Mendizabal nominated Barbican PTL Election for Magnum PTL between Adrian Otto and Hongbin Lu MagnetoDB being abandoned, not PTL was chosen. Instead, it will be fast tracked for removal [2] from the official list of OpenStack projects. Release help needed - we are incompatible with ourselves <http://lists.openstack.org/pipermail/openstack-dev/2015-September/075075.ht…> Robert Collins raises that while the constraints system in place for how we recognize incompatible components in our release is working, the release team needs help from the community to fix the incompatibility that exists so we can cut the full Liberty release. Issues that exist: OpenStack client not able to create an image. Fix is merged [3]. Semver and dependency changes <http://lists.openstack.org/pipermail/openstack-dev/2015-September/075107.ht…> Robert Collins says currently we don’t provide guidance on what happens when the only changes in a project are dependency changes and a release is made. Today the release team treats dependency changes as a “feature” rather than a bug fix. (e.g. if the previous release 1.2.3, requirement sync happens, the next version is 1.3.0.) Reasons behind this are complex, some guidance is needed to answer the questions: Is this requirements change an API break? Is this requirements change feature work? Is this requirements change a bug fix? All of these questions can be true. Some examples: If library X exposes library Y as part of its API, and library Y’s dependency changes from Y>=1 to Y>=2. X does this because it needs a feature from Y==2. Library Y is not exposed in library X’s API, however, a change in Y’s dependencies for X will impact users who independently use Y. (ignoring intricacies surrounding PIP here.) Proposal: nothing -> a requirement -> major version change 1.x.y -> 2.0.0 -> major version change 1.2.y -> 1.3.0 -> minor version change 1.2.3. -> 1.2.4 -> patch version change Thierry Carrez is ok with the last two proposals. Defaulting to a major version bump sounds a bit overkill. Doug Hellmann reminds that we can’t assume the dependency is using semver itself. We would need something other than the version number to determine from the outside whether the API is in fact breaking. Due this problem being so complicated, Doug would rather over-simplify the analysis of requirements updates until we’re better at identifying our own API breaking changes and differentiating between features and bug fixes. This will allow us to be consistent, if not 100% correct. Criteria for applying vulnerability:managed tag <http://lists.openstack.org/pipermail/openstack-dev/2015-September/073435.ht…> The vulnerability management processes were brought to the big tent a couple of months ago [4]. Initially we listed what repos the Vulnerability Manage Team (VMT) tracks for vulnerabilities. TC decided to change this from repos to deliverables as per-repo tags were decided against. Jeremy Stanley provides transparency for how deliverables can qualify for this tag: All repos in a given deliverable must qualify. If one repo doesn’t, they all don’t in a given deliverable. Points of contact: Deliverable must have a dedicated point of contact. The VMT will engage with this contact to triage reports. A group of core reviewers should be part of the <project>-corsec team and will: Confirm whether a bug is accurate/applicable. Provide pre-approval of patches attached to reports. The PTLs for the deliverable should agree to act as (or delegate) a vulnerability management liaison to escalate for the VMT. The bug tracker for the repos within a deliverable should have a bug tracker configured to initially provide access to privately reported vulnerabilities initially to the VMT. The VMT will determine if the vulnerability is reported against the correct deliverable and redirect when possible. The deliverable repos should undergo a third-party review/audit looking for obvious signs of insecure design or risky implementation. This aims to keep the VMT’s workload down. It has not been identified who will perform this review. Maybe the OpenStack Security project team? Review of this proposal is posted [5]. Consistent support for SSL termination proxies across all APIs <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074871.ht…> While a bug [6] was being debugged, an issue was identified where an API sitting behind a proxy performing SSL termination would not generate the right redirection (http instead of https). A review [7] has been given to have a config option ‘secure_proxy_ssl_header’ which allows the API service to detect ssl termination based on the header X-Forwarded-Proto. Another bug back in 2014 was open with the same issue [8]. Several projects applied patches to fix this issue, but are inconsistent: Glance added public_endpoint config Cinder added public_endpoint config Heat added secure_proxy_ssl_header config (through heat.api.openstack:sslmiddleware_filter) Nova added secure_proxy_ssl_header config Manila added secure_proxy_ssl_header config (through oslo_middleware.ssl:SSLMiddleware.factory) Ironic added public_endpoint config Keystone added secure_proxy_ssl_header config Ben Nemec comments that solving this at the service level is the wrong place, due to this requiring changes in a bunch of different API services. Instead it should be fixed in the proxy that’s converting the traffic to http. Sean Dague notes that this should be done in the service catalog. Service discovery is a base thing that all services should use in talking to each other. There’s an OpenStack spec [9] in an attempt to get a handle on this Mathieu Gagné notes that this won’t work. There is a “split view” in the service catalog where internal management nodes have a specific catalog and public nodes (for users) have a different one. Suggestion to use oslo middleware SSL for supporting the ‘secure_proxy_ssl_header’ config to fix the problem with little code. Sean agrees the split view needs to be considered, however, another layer of work shouldn’t decide if the service catalog is a good way to keep track of what our service urls are. We shouldn’t push a model where Keystone is optional. Sean notes that while the ‘secure_proxy_ssl_header’ config solution supports the cases where there’s a 1 HA proxy with SSL termination to 1 API service, it may not work in the cases where there’s a 1 API service to N HA Proxies for: Clients needing to understand the “Location:” headers correctly. Libraries like request/phatomjs can follow the links provided in REST documents, and they’re correct. The minority of services that “operate without keystone” as an option are able to function. ZZelle mentions this solution does not work in the cases when the service itself acts as a proxy (e.g. nova image-list). Would this solution work in the HA Proxy case where there is one terminating address for multiple backend servers? Yes, by honoring the headers X-Forwarded-Host and X-Forwarded-Port which are set by HTTP proxies, making WSGI applications unaware of the fact that there is a request in front of them. Jamie Lennox says this same topic came up as a block in a Devstack patch to get TLS testing in the gate with HA Proxy. Longer term solution, transition services to use relative links. This is a pretty serious change. We’ve been returning absolute URLs forever, so assuming that all client code out there would with relative code is a big assumption. That’s a major version for sure. Sean agrees that we have enough pieces to get something better with proxy headers for Mitaka. We can do the remaining edge cases if clean up the service catalog use. [1] - http://governance.openstack.org/resolutions/20141128-elections-process-for-… <http://governance.openstack.org/resolutions/20141128-elections-process-for-…> [2] - https://review.openstack.org/#/c/224743/ <https://review.openstack.org/#/c/224743/> [3] - https://review.openstack.org/#/c/225443/ <https://review.openstack.org/#/c/225443/> [4] - http://governance.openstack.org/reference/tags/vulnerability_managed.html <http://governance.openstack.org/reference/tags/vulnerability_managed.html> [5] - https://review.openstack.org/#/c/226869/ <https://review.openstack.org/#/c/226869/> [6] - https://bugs.launchpad.net/python-novaclient/+bug/1491579 <https://bugs.launchpad.net/python-novaclient/+bug/1491579> [7] - https://review.openstack.org/#/c/206479/ <https://review.openstack.org/#/c/206479/> [8] - https://bugs.launchpad.net/glance/+bug/1384379 <https://bugs.launchpad.net/glance/+bug/1384379> [9] - https://review.openstack.org/#/c/181393/ <https://review.openstack.org/#/c/181393/> The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world._______________________________________________ Community mailing list Community(a)lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community <http://lists.openstack.org/cgi-bin/mailman/listinfo/community>

1 0

[openstack-community] User Survey - Deadline Sept 25th
by Tom Fifield 22 Sep '15

22 Sep '15

Hi all, If you run OpenStack, build apps on it, or have customers with OpenStack deployments, please take a few minutes to respond to the latest User Survey or pass it along to your friends. Since 2013, the user survey has provided significant insight into what people are deploying and how they're using OpenStack. You can see the most recent results in these SuperUser Articles: [1][2][3]. Please follow the link and instructions below to complete the User Survey by ***April 8, 2015 at 23:00 UTC***. If you already completed the survey, there's no need to start over. You can simply log back in to update your Deployment Profile, as well as take the opportunity to provide additional input. You need to do this to keep your past survey responses active, but we hope you'll do it because we've made the survey shorter and with more interesting questions ;) Take the Survey ( http://www.openstack.org/user-survey ) All of the information you provide is confidential to the Foundation and User Committee and will be aggregated anonymously unless you clearly indicate we can publish your organization’s profile. Remember you can hear directly from users and see the aggregate survey findings by attending the next OpenStack Summit, October 27-30 in Tokyo (http://www.openstack.org/summit) Thank you again for your support. -Tom [1] http://superuser.openstack.org/articles/user-survey-identifies-leading-indu… [2] http://superuser.openstack.org/articles/openstack-users-share-how-their-dep… [3] http://superuser.openstack.org/articles/openstack-application-developers-sh…

1 2

[openstack-community] [upstream] Upstream Training prep, live assistance, and mentoring
by Tim Freund 21 Sep '15

21 Sep '15

Hi Everyone - We'll open registration for the Tokyo Upstream training soon, and we're doing something a little different this time: we are pairing students with mentors right away and allowing them to work through some of the technical details of OpenStack contribution before class begins. To do that, we need to fill our roster of Upstream mentors! We need people who are willing to mentor students via IRC and email before and after the class that occurs on October 25th and 26th, and we also need people who can be with us in Tokyo to help students complete hands on exercises. Please fill out the following form if you can help in either role: http://goo.gl/forms/fczq3NZ16g Our students will be looking for bugs tagged as low-hanging-fruit, so you can also help by tagging such bugs appropriately in Launchpad. If you're unfamiliar with Upstream training, and you'd like to learn more, we have basic course information and a complete training schedule on the wiki[1]. You can read about our Vancouver training session in Superuser[2]. [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Training [2] http://superuser.openstack.org/articles/what-building-legos-can-teach-you-a… Please direct additional questions or comments to the community(a)lists.openstack.org list with the [upstream] tag. You can also reach out to me directly. Thanks for your help! Tim -- Tim Freund 913-207-0983 | @timfreund http://tim.freunds.net

3 3

[openstack-community] OpenStack Community Weekly Newsletter (Sept., 12 – 18)
by Jay Fankhauser 18 Sep '15

18 Sep '15

Running OpenStack? You have the power to influence the roadmap <https://www.openstack.org/surveys/landing?BackURL=/surveys/current> Complete the User Survey by September 25 Call for Outreachy Mentors <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074399.ht…> If you are a full-time contributor, please consider sharing your time, knowledge and experience to make our community more diverse and you’ll have the opportunity to meet new talents. Ask for further directions in OpenStack-opw on Freenode. A starter guide to DefCore, OpenStack’s interoperability project <http://superuser.openstack.org/articles/a-starter-guide-to-defcore-openstac…> Rob Hirschfeld, co-chair of the DefCore committee, shares more on DefCore, which defines capabilities, code and must-pass tests, creating the minimum standards for products labeled OpenStack The Road to Tokyo Register now: full access registration prices increase on 9/29 at 11:59pm PT <https://www.eventbrite.com/e/openstack-summit-october-2015-tokyo-tickets-17…> Discounted registration for nonprofit/government/students deadline is 9/25 <https://openstack.formstack.com/forms/openstack_summit_tokyo_discounted_reg…> Get your OpenStack Summit Tokyo visa in five steps: Deadline for Visa invitation requests is 10/1 <http://superuser.openstack.org/articles/get-your-openstack-summit-tokyo-vis…> The schedule and mobile app for the OpenStack Summit in Tokyo are now available <https://www.openstack.org/summit/tokyo-2015/schedule/> Reports from Previous Events None this week Deadlines and Contributors Notifications Liberty Release Oct., 15, 2015 <https://wiki.openstack.org/wiki/Liberty_Release_Schedule> Security Advisories and Notices None this week Tips ‘n Tricks By Nicole Martinelli <https://www.linkedin.com/in/nicolemartinelli>: Confused about the OpenStack release cycle? Check out this handy chart <http://superuser.openstack.org/articles/confused-about-the-openstack-releas…> By Superuser: How to migrate from VMware and Hyper-V to OpenStack <http://superuser.openstack.org/articles/how-to-migrate-from-vmware-and-hype…> By Madhu Kashyap: Bringing NFV into OpenStack with Tacker <http://superuser.openstack.org/articles/bringing-nfv-into-openstack-with-ta…> By Nicholas Cammorato: Building an OpenStack lab from scratch with PackStack on AWS and Google Cloud – Installing OpenStack via Packstack <https://www.ravellosystems.com/blog/openstack-packstack-installation-on-aws/> By Miguel Grinberg <https://developer.rackspace.com/blog/authors/miguel-grinberg/>: Keystone-to-Keystone Federation with the OpenStack-Ansible Project <https://developer.rackspace.com/blog/keystone-to-keystone-federation-with-o…> Upcoming Events <https://www.openstack.org/community/events> Sep 21 – 24, 2015 Storage Developer Conference Santa Clara, CA, US <http://www.snia.org/events/storage-developer> Sep 29 – 30, 2015 Cloud Storage in OpenStack <https://groups.openstack.org/groups/frederick-md/cloud-storage-openstack> Oct 01, 2015 OpenStack Meetup Cluj Cluj-Napoc, Cluj, RO <http://www.meetup.com/OpenStackRomania/events/222910344/> Oct 01, 2015 South Bay OpenStack Meetup, Beginner track San Francisco, CA, US <http://www.meetup.com/openstack/events/221806052/> Oct 01 – 02, 2015 October OpenStack Meetup – SDN and Containers Chicago, IL, US <http://www.meetup.com/meetup-group-NjZdcegA/events/225081881/> Oct 04 – 08, 2015 Gartner SymposiumITxpo Orlando, FL, US <http://www.gartner.com/events/na/orlando-symposium> Oct 06, 2015 October Sydney Meetup <http://www.meetup.com/Australian-OpenStack-User-Group/events/220202327/> Oct 07, 2015 Houston OpenStack Meetup Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/?eventId=2248…> Oct 07 – 08, 2015 OpenStack Liberty Release Richardson, TX, US <http://www.meetup.com/OpenStack-DFW/events/225014699/> Oct 07 – 08, 2015 OpenStack 101 Houston, TX, US <http://www.meetup.com/openstackhoustonmeetup/events/224870393/> Oct 10, 2015 OpenStack India Meetup, Pune Pune, IN <http://www.meetup.com/Indian-OpenStack-User-Group/events/225039190/> Oct 12, 2015 OpenStack Cinder deep dive Stockholm, SE <http://www.meetup.com/OpenStack-User-Group-Nordics/events/225365322/> Oct 13, 2015 Pub Gathering Manchester, GB <http://www.meetup.com/Manchester-OpenStack-Meetup/events/224421141/> Oct 15, 2015 OpenStack Howto part 7 – Data Processing Prague, CZ <http://www.meetup.com/OpenStack-Czech-User-Group-Meetup/events/222955596/> Oct 15 – 16, 2015 Coming event, stay tuned Washington D.C., DC, US <http://www.meetup.com/OpenStackDC/events/224954116/> Oct 16, 2015 OpenStack PDX Meetup <http://www.meetup.com/openstack-pdx/events/fsnsglytnbtb/> Oct 16, 2015 SFBay OpenStack Hackathon #OSSFO <http://www.meetup.com/openstack/events/223988220/>What you need to know from the developer’s list PTL Nominations Are Over, Lets Start Elections! <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074765.ht…> Five projects don’t have candidates. According to OpenStack governance, the TC will appoint the new PTL [1]. Barbican MagnetoDB Magnum Murano Security Seven projects will have an election: Cinder Glance Ironic Keystone Mistral Neutron Oslo There was confusion in UTC and how to submit nominations through Gerrit, but the TC will work with those candidates in Magnum, Barbican, Murano, Security. Doug Hellmann says MagnetoDB will be discussed for removal due to inactivity. [1] Proposed Priorities For Glance <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074360.ht…> From conversations at the Ops Midcycle meetup and email threads with regards to Glance issues, Doug Hellmann put together a list of proposed priorities for the Glance team: Focus attention on DefCore: DefCore goals: Ensure all OpenStack deployments are interoperable at REST level (users can write software for one OpenStack cloud and move to another without changes to the code). Provide a well documented API with arguments that don’t change based on deployment choices. Integration tests in Tempest that test Glance’s API directly, in addition to the the current tests that proxy through Nova and Cinder. Once incorporated into DefCore, the APIs need to remain stable for an extended period of time, and follow deprecation timelines defined by complete V2 adoption in Nova and Cinder. In Nova, some specs didn’t land in Liberty. Both teams need to work together. In Cinder, the work is more complete, but needs to be reviewed that the API is used correctly. Security audits and bug fixes 5 out of the 18 recent security reports were related to Glance [2] Two ways to upload images to Glance V2: 1) POST image bits to Glance API server. a) Not widely deployed. Potential DOS vector. 2) Task API, to have Glance download it asynchronously. a) Not widely deployed. b) Assumes you know what task “types” are supported by which cloud, and the expected arguments (i.e. JSON blob). (e.g. Glance docs give a url for a source, but Rackspace gives a Swift location as a source) New Proposed ‘default’ network model <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074527.ht…> Monty hates floating IPs. Observed with 5 public clouds, requiring you to use a floating IP to get an outbound address. Others directly attach you to the public network. Some allow you to create a private network and attach virtual machines to it, create a router with a gateway. Monty wants an easier way to have a virtual machine on the external facing network of a cloud. Users shouldn't have to learn about how to make that work with floating tips. This should be consistent behavior across public clouds. There is an effort set for Mitaka to work on Monty's request [3]. This will be done for 'nova boot' and work with multiple networks. If you have a more complicated network setup, this spec isn't for you. Base Feature Deprecation Policy <http://lists.openstack.org/pipermail/openstack-dev/2015-September/073576.ht…> Thierry proposes a standard way to communicate and perform removal of user-visible behaviors and capabilities. We sort of have something today, but not written of “to remove a feature, you mark it deprecated for n releases, then remove it”. Tag proposed [4]. We need to survey existing projects to see what their deprecation policy is. Proposed options for deprecation period: n+2 for features and capabilities, n+1 for config options n+1 for everything n+2 for everything Ben Swartzlander thinks this discussion also needs to cover long term support (LTS). Fungi thinks this is premature. Icehouse stable branch made it to 14 months before it was dropped due to not enough effort was given to keep it working. It was agreed “config options and features will have to be marked deprecated for a minimum of one stable release branch and a minimum of 3 months”. team:danger-not-diverse tag <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074264.ht…> Josh Harlow is concerned that most projects start off small and not diverse, and this tag [5] would create negative connotations for those projects. Thierry raises it’s important to see the intent of the tag, rather by it’s name. The tag system is there to help our ecosystem navigate the big tent by providing bits of information. Example of information: how risky is it to invest on a given project? Some projects are dependent on a single company and can disappear in one day by the CEO’s decision. For this reason, Thierry supports describing project teams that are *extremely* fragile. As a result, the big tent is more inclusive. On the flip side, we need to inform our ecosystem that some project are less mature. Otherwise, you’re hiding this information. [1] - http://lists.openstack.org/pipermail/openstack-dev/2015-September/074837.ht… <http://lists.openstack.org/pipermail/openstack-dev/2015-September/074837.ht…> [2] - https://security.openstack.org/search.html?q=glance&check_keywords=yes&area… <https://security.openstack.org/search.html?q=glance&check_keywords=yes&area…> [3] - https://blueprints.launchpad.net/neutron/+spec/get-me-a-network <https://blueprints.launchpad.net/neutron/+spec/get-me-a-network> [4] - https://review.openstack.org/#/c/207467/ <https://review.openstack.org/#/c/207467/> [5] - https://review.openstack.org/#/c/218725/ <https://review.openstack.org/#/c/218725/> Other News Tracking the OpenStack revolution <http://superuser.openstack.org/articles/tracking-the-openstack-revolution> Python 3 Status in OpenStack Liberty <http://techs.enovance.com/7807/python-3-status-openstack-liberty> The weekly newsletter is a way for the community to learn about all the various activities in the OpenStack world._______________________________________________ Community mailing list Community(a)lists.openstack.org <mailto:Community@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/community <http://lists.openstack.org/cgi-bin/mailman/listinfo/community>

1 0

Re: [openstack-community] Community Digest, Vol 38, Issue 8
by Thiago Donizetti Corredor 16 Sep '15

16 Sep '15

Good morning all, Do we have a date for Brazil Summit? Thiago Donizetti Corredor da Silva ITIL® 2011 and CobiT® V4.1 Foundation Certificate Find me on: Skype: thiago_corredor(a)live.com Linkedin:http://www.linkedin.com/in/thiagocorredor > On 16/09/2015, at 09:01, community-request(a)lists.openstack.org wrote: > > Send Community mailing list submissions to > community(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > or, via email, send a message with subject or body 'help' to > community-request(a)lists.openstack.org > > You can reach the person managing the list at > community-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Community digest..." > > > Today's Topics: > > 1. Re: Schedule Live - Tokyo OpenStack Summit (Kendall Waters) > 2. User Survey - Deadline Sept 25th (Tom Fifield) > 3. Re: User Survey - Deadline Sept 25th (Tom Fifield) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Sep 2015 14:42:03 -0500 > From: Kendall Waters <kendall(a)openstack.org> > To: openstack(a)lists.openstack.org, Community(a)lists.openstack.org, > summitsponsors(a)lists.openstack.org, marketing(a)lists.openstack.org > Subject: Re: [openstack-community] Schedule Live - Tokyo OpenStack > Summit > Message-ID: <387952FD-2C64-4CA8-B229-B095F3F1327A(a)openstack.org> > Content-Type: text/plain; charset="utf-8" > > Hi everyone, > > The mobile apps for the Tokyo Summit are now available for download! If you attended the Vancouver Summit, then you can simply update the same mobile app to use for the Tokyo Summit. > > For Apple devices, click HERE <https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=98721629…> to download. > For Android devices, click HERE <https://play.google.com/store/apps/details?id=org.sched.openstacksummitmay2…> to download. > > See you in Tokyo! > > Cheers, > Kendall > >> On Aug 26, 2015, at 1:25 PM, Kendall Waters <kendall(a)openstack.org> wrote: >> >> Hi everyone, >> >> The schedule for the upcoming OpenStack Summit in Tokyo <https://www.openstack.org/summit/tokyo-2015/> is now available! >> >> SCHEDULE: https://www.openstack.org/summit/tokyo-2015/schedule/ <https://www.openstack.org/summit/tokyo-2015/schedule/> >> >> There are two views for the Summit schedule. The Main Conference view is what the vast majority of attendees should use. Active Technical Contributors and operators who contribute to the Mitaka release cycle should use the Design Summit + Main Conference view of the Summit schedule. >> >> MOBILE APP >> In the coming weeks the schedule mobile app will also be available for download. We will notify the community at that time. If you attended the Vancouver Summit then you can simply update the same mobile app to use for the Tokyo Summit. >> >> SPEAKER NOTIFICATIONS >> If you submitted a talk - check your email. Everyone who submitted a speaking proposal for the Summit will soon receive an email notification to let them know whether or not their talk is accepted. The email sent to selected speakers contains next steps and a Summit speaker registration code. Each speaker is responsible for registering themselves to attend the Summit. Please make sure your colleagues read the email and complete this step. >> >> Contact summit(a)openstack.org <mailto:summit@openstack.org> with any questions. >> >> We?ll see you in Tokyo in two months. >> >> Cheers, >> Kendall > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstack.org/pipermail/community/attachments/20150915/7536932…> > > ------------------------------ > > Message: 2 > Date: Wed, 16 Sep 2015 11:40:30 +0800 > From: Tom Fifield <tom(a)openstack.org> > To: openstack(a)lists.openstack.org, OpenStack Operators > <openstack-operators(a)lists.openstack.org>, > "community(a)lists.openstack.org" <community(a)lists.openstack.org> > Subject: [openstack-community] User Survey - Deadline Sept 25th > Message-ID: <55F8E4AE.7060607(a)openstack.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi all, > > If you run OpenStack, build apps on it, or have customers with OpenStack > deployments, please take a few minutes to respond to the latest User > Survey or pass it along to your friends. > > Since 2013, the user survey has provided significant insight into what > people are deploying and how they're using OpenStack. You can see the > most recent results in these SuperUser Articles: [1][2][3]. > > Please follow the link and instructions below to complete the User > Survey by ***April 8, 2015 at 23:00 UTC***. If you already completed the > survey, there's no need to start over. You can simply log back in to > update your Deployment Profile, as well as take the opportunity to > provide additional input. You need to do this to keep your past survey > responses active, but we hope you'll do it because we've made the survey > shorter and with more interesting questions ;) > > > > Take the Survey ( http://www.openstack.org/user-survey ) > > > All of the information you provide is confidential to the Foundation and > User Committee and will be aggregated anonymously unless you clearly > indicate we can publish your organization?s profile. > > Remember you can hear directly from users and see the aggregate survey > findings by attending the next OpenStack Summit, October 27-30 in Tokyo > (http://www.openstack.org/summit) > > Thank you again for your support. > > > -Tom > > > [1] > http://superuser.openstack.org/articles/user-survey-identifies-leading-indu… > [2] > http://superuser.openstack.org/articles/openstack-users-share-how-their-dep… > [3] > http://superuser.openstack.org/articles/openstack-application-developers-sh… > > > > ------------------------------ > > Message: 3 > Date: Wed, 16 Sep 2015 11:52:51 +0800 > From: Tom Fifield <tom(a)openstack.org> > To: openstack(a)lists.openstack.org, OpenStack Operators > <openstack-operators(a)lists.openstack.org>, > "community(a)lists.openstack.org" <community(a)lists.openstack.org> > Subject: Re: [openstack-community] User Survey - Deadline Sept 25th > Message-ID: <55F8E793.1080204(a)openstack.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Copy and Paste Error Strikes Again! > > The deadline is (as the subject says): ***September 25 at 23:59 UTC***. > That is next Friday - get on it :) > > http://www.openstack.org/user-survey > > > Regards, > > Tom > >> On 16/09/15 11:40, Tom Fifield wrote: >> Hi all, >> >> If you run OpenStack, build apps on it, or have customers with OpenStack >> deployments, please take a few minutes to respond to the latest User >> Survey or pass it along to your friends. >> >> Since 2013, the user survey has provided significant insight into what >> people are deploying and how they're using OpenStack. You can see the >> most recent results in these SuperUser Articles: [1][2][3]. >> >> Please follow the link and instructions below to complete the User >> Survey by ***Sep 25, 2015 at 23:00 UTC***. If you already completed the >> survey, there's no need to start over. You can simply log back in to >> update your Deployment Profile, as well as take the opportunity to >> provide additional input. You need to do this to keep your past survey >> responses active, but we hope you'll do it because we've made the survey >> shorter and with more interesting questions ;) >> >> >> >> Take the Survey ( http://www.openstack.org/user-survey ) >> >> >> All of the information you provide is confidential to the Foundation and >> User Committee and will be aggregated anonymously unless you clearly >> indicate we can publish your organization?s profile. >> >> Remember you can hear directly from users and see the aggregate survey >> findings by attending the next OpenStack Summit, October 27-30 in Tokyo >> (http://www.openstack.org/summit) >> >> Thank you again for your support. >> >> >> -Tom >> >> >> [1] >> http://superuser.openstack.org/articles/user-survey-identifies-leading-indu… >> >> [2] >> http://superuser.openstack.org/articles/openstack-users-share-how-their-dep… >> >> [3] >> http://superuser.openstack.org/articles/openstack-application-developers-sh… > > > > > ------------------------------ > > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > > > End of Community Digest, Vol 38, Issue 8 > ****************************************

1 0

Re: [openstack-community] Schedule Live - Tokyo OpenStack Summit
by Kendall Waters 15 Sep '15

15 Sep '15

Hi everyone, The mobile apps for the Tokyo Summit are now available for download! If you attended the Vancouver Summit, then you can simply update the same mobile app to use for the Tokyo Summit. For Apple devices, click HERE <https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=98721629…> to download. For Android devices, click HERE <https://play.google.com/store/apps/details?id=org.sched.openstacksummitmay2…> to download. See you in Tokyo! Cheers, Kendall > On Aug 26, 2015, at 1:25 PM, Kendall Waters <kendall(a)openstack.org> wrote: > > Hi everyone, > > The schedule for the upcoming OpenStack Summit in Tokyo <https://www.openstack.org/summit/tokyo-2015/> is now available! > > SCHEDULE: https://www.openstack.org/summit/tokyo-2015/schedule/ <https://www.openstack.org/summit/tokyo-2015/schedule/> > > There are two views for the Summit schedule. The Main Conference view is what the vast majority of attendees should use. Active Technical Contributors and operators who contribute to the Mitaka release cycle should use the Design Summit + Main Conference view of the Summit schedule. > > MOBILE APP > In the coming weeks the schedule mobile app will also be available for download. We will notify the community at that time. If you attended the Vancouver Summit then you can simply update the same mobile app to use for the Tokyo Summit. > > SPEAKER NOTIFICATIONS > If you submitted a talk - check your email. Everyone who submitted a speaking proposal for the Summit will soon receive an email notification to let them know whether or not their talk is accepted. The email sent to selected speakers contains next steps and a Summit speaker registration code. Each speaker is responsible for registering themselves to attend the Summit. Please make sure your colleagues read the email and complete this step. > > Contact summit(a)openstack.org <mailto:summit@openstack.org> with any questions. > > We’ll see you in Tokyo in two months. > > Cheers, > Kendall >

1 0