Loading…

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Magnum [clear filter]
Wednesday, October 28
 

11:15am

Magnum: Work session
Heat Template Refactoring

Talk to Steve Hardy and TripleO team to learn from their experience in refactoring, managing templates. Magnum has recently merged code to use a master Jinja2 template that generates individual HOT files if they don't already exist. These HOT files are used for bay creation in Magnum.

https://bugs.launchpad.net/magnum/+bug/1501045

Wednesday October 28, 2015 11:15am - 11:55am
Kinkei Room
  • format json

12:05pm

Magnum: Work session
Magnum Scalability

If Magnum were scaled to support hundreds of thousands... or millions... of bays/containers, what challenges will we face, and how can we plan to address them?

Wednesday October 28, 2015 12:05pm - 12:45pm
Kinkei Room
  • format json

2:00pm

Magnum: Work session
Magnum Security

In Liberty, we added support for TLS using an implementation that is completely within Magnum. Our intent was to implement this using Barbican, but we were unable to make that work this time around. What enhancements can we reasonably plan to make for secure operation of Magnum? What other security enhancements could we add to make Magnum more appealing to cloud operators?

Wednesday October 28, 2015 2:00pm - 2:40pm
Jako room
  • format json
 
Thursday, October 29
 

9:00am

Magnum: Storage Features
OpenStack already has a variety of storage capabilities offered through Cinder, and Manila. In the Mitaka release, we plan to embark on an adventure to add new storage integration features into Magnum to allow these resources to be utilized from your containerized applications. Come to this session to affirm our current priorities for adding storage features. For example, we would like to add support for cinder volumes with filesystems automatically created by Heat/Magnum that are added to the host, and shared with the container by using "-e" hints in Docker that can be used in combination with "-v" flags with Docker to conenct a new/existing volume to a particular container. We would also like to leverage Manila to expose a given filesystem to multiple containers so they can have a consistent filesystem view across multiple containers on multiple hosts.

Thursday October 29, 2015 9:00am - 9:40am
Ohka room
  • format json

9:50am

Magnum: Netwoking: Past, Present, and Future
The first networking solution for Magnum used a simple flannel overlay network with our Kubernetes bay. Since then, Magnum and Neutron contributors ahve been working together to design Kuryr, which acts as a libnetwork driver for Docker that connects docker containers to your Neutron networks. This way it can work with your existing SDN. Magnum Also has a new networking specification for that is designed to work with exising Bay types, as well as new ones that are not based on Docker containers. In this session we will outline Magnums goals and non-goals for networking, and explain our point-of-view for how OpenStack cloud resources, including Magnum bays, should be able to share common networks easily.

Thursday October 29, 2015 9:50am - 10:30am
Ohka room
  • format json

11:00am

Magnum: Work session
Magnum Auto-scaling

How should Magnum tackle auto-scaling? Bring your proposals, and let's select an approach based on a set of design principles that we all agree on together.

Thursday October 29, 2015 11:00am - 11:40am
Kinkei Room
  • format json

11:50am

Magnum: Work session
Functional Testing

Our functional testing needs to be expanded, and must be redesigned so that tests on different Magnum COE types can be executed in parallel. Tests must be consistently completed in under 120 minutes. Let's take a challenge to get that time down to 30 minutes on average.

Thursday October 29, 2015 11:50am - 12:30pm
Kinkei Room
  • format json

1:50pm

Magnum: Bare Metal Bays
Magnum is designed to offer a choice of compute instance types to run bays, including Virtual Machines, Bare Metal, and even Containers from libvirt/lxc. Our main templates create VM instances, and we have templates that are designed to work with ironic bare metal instances as well. there are some challenges with bare metal instances that make it more difficult for them to securely join Neutron networks and use Cinder storage volumes. This is because working with these services requires that the control plane can be accessed by the host, which it normally can not be. In this session we will highlight these differences and explain which issues are unique to irnoic, and which are challenges for Magnum.

Thursday October 29, 2015 1:50pm - 2:30pm
Ohka room
  • format json

2:40pm

Magnum: Getting Started for Developers and Sysadmins
Overview for developers and system administrators/engineers planning to begin with Magnum for the first time. In this session, we will identify all the useful resources for you about where to find documentation and guides, video sessions about Magnum, where to find the developemnt team to interact with them, how to join our community, where to file bugs, and and how to contribute new features and improvements. We will also poll the audience for your input on ways that we could make Magnum easier to work with, and more friendly for newcomers.

Thursday October 29, 2015 2:40pm - 3:20pm
Ohka room
  • format json

3:30pm

Magnum: Scope of Magnum
Today Magnum serves as an integration point to allow OpenStack cloud operators to offer a containers-as-a-service solution to their cloud users. It allows the creation of Bays, which are groupings of Nova instances that run a container orchestration engine (COE) such as Docker Swarm, Kubernetes, or Apache Mesos. This gives users a choice of what type of container environment to start up. We have intentionally avoided the creation of new container technology, such as container formats, runtime environments, or the creation of elaborate openstack-specific tools for interacting with containers, holding a strong preference for allowing the use of native APIs and tools. Let's discuss our current point of view, and true that up with your expectations from OpenStack. Should our scope be expanded? If so, what should that new scope include, and why?

Thursday October 29, 2015 3:30pm - 4:10pm
Ohka room
  • format json
 
Friday, October 30
 

9:00am

Magnum contributors meetup
The Magnum contributors meetup is a informal gathering of the project contributors, with an open agenda.

Click here for details on the meetup agenda.

Friday October 30, 2015 9:00am - 12:30pm
Nadeshiko room
  • format json

2:00pm

Magnum contributors meetup
The Magnum contributors meetup is a informal gathering of the project contributors, with an open agenda.

Click here for details on the meetup agenda.

Friday October 30, 2015 2:00pm - 5:30pm
Nadeshiko room
  • format json