csuttles (⌐■_■)

Memento Mori

Neutron Pain Points Kevin Benton https://www.openstack.org/summit/boston-2017/summit-schedule/events/18801/neutron-pain-points https://etherpad.openstack.org/p/neutron-boston-painpoints https://etherpad.openstack.org/p/pike-neutron-making-it-easy Octavia LBaaS People were looking for an update on status, but noone was there to speak on it Main contributor moved on, but project is still maintained, even though it was not represented in this session FWaaS v2 L3 supported since Newton L2 was targeted for Ocata, now targeted for Pike

Oslo Developer/Operator Feedback ChangBo Guo https://www.openstack.org/summit/boston-2017/summit-schedule/events/18762/oslo-developeroperator-feedback https://etherpad.openstack.org/p/BOS-Oslo-brainstorming This was a brainstorming dev/user session for the oslo middleware that unifies communications between OpenStack components. Topics included testing against PyPy, configs in etc.d (or potentially consul), messaging and potential changes to rootwrap and privsep. A suggestion to better support alternatives to RabbitMQ for AMQP messaging in this forum bore fruit in the next oslo forum and are detailed in this etherpad: https://etherpad.

Containers Networking Using Kuryr: A Hands-On Lab Sudhir Kethamakka Amol Chobe https://www.openstack.org/summit/boston-2017/summit-schedule/events/18385/containers-networking-using-kuryr-a-hands-on-lab Kuryr is a part of the OpenStack Big Tent Kuryr is a bridge between container frameworks and Neutron Supports CNI and CNM Docker Kubernetes Rkt CoreOS The lab focused on the CNM model. Both CNM and CNI support are plugins in Kuryr, so it's possoble to extend Kuryr to support other network models by writing a plugin at this layer.

Learn about Keystone to Keystone federation and see it work with Horizon for Ocata Elvin Tubillara Nithya Renganathan https://www.openstack.org/videos/boston-2017/learn-about-keystone-to-keystone-federation-and-see-it-work-with-horizon-for-ocata The crux of this lightning talk was: Keystone instance "A" is source of identity Keystone instance "B" uses Keystone "A" as source ov identity via Shibboleth/SAML2.0 Mappings are created for B->A. This only gets you identity, not ssh-keys or other Keystone components For this to be successful, users must fully qualify their names, like user@VagrantServiceProvider

Home of Open {Composable} Infrastructure Mark Collier https://www.openstack.org/videos/boston-2017/home-of-open-composable-infrastructure Mark talked about hacking on Apple IIs and cutting class to play Doom, and how computing has evolved to become the foundation for important human achievements like science, industry, going to mars, or curing disease. He talked about the using open source first for solving technical problems, and the importance of AI, and machine learning. Some of the open source platforms he talked about included:

Consuming Multiple OpenStack Clouds with Ease Monty Taylor https://www.openstack.org/videos/boston-2017/consuming-multiple-openstack-clouds-with-ease Shade - what is it? Task oriented lib Multi-Cloud Scalable (used on 20k servers a day in managing OpenStack CI) Logic design is borrowed heavily from nodepool lib in Python and Ansible https://github.com/openstack-infra/shade #openstack-shade on freenode Side note: presentation was made using https://pypi.python.org/pypi/presentty We got a walkthrough of the module, and a demo where a server was created and destroyed in 3 different clouds, located in 3 different providers (with different credentials)

GEIX / GE Healthcare They shared their success stories with OpenStack, which included reducing the time required for some medical imaging from over 1 day to minutes. This was in partnership with a research endeavor they sponsor. Taking OpenStack to the Network Edge (Verizon) Verizon previewed their OpenStack in a box CPE, which was 1U, LTE capable with four antennas, and runs OpenStack in containers. It's part of their globally, massively distributed OpenStack footprint.

Upstream Institute Sunday, I attended this session, and met some great people. I sat with two Swift core contributors, two Cinder contributors, and a Manilla contributor who also previously contributed to Horizon and Trove. The class was an intro to contributing to OpenStack, so I was lucky to end up at a table full of seasoned folks. I made connections with almost everyone at the table, and I really enjoyed speaking with them and learning from them.