)
Each release cycle, OpenStack project team leads (PTLs) introduce themselves, talk about upcoming features for the OpenStack projects they manage, plus how you can get involved and influence the roadmap.
Superuser will feature weekly summaries of the videos; you can also catch them on the OpenStack Foundation YouTube channel. This post covers Heat, Keystone and Kuryr.
Heat
What Heat
whose mission is to orchestrate composite cloud applications using a declarative template format through an OpenStack-native REST API.
Who Thomas Herve, PTL. Day job: principal software engineer, Red Hat.
Burning issues
“Convergence is a different way of working,” Herve says. “Right now we’re have a built-in approach and convergence is a bit more iterative. It allows us to do interesting things, for example you can recover failures…We’ve been working on it for almost two years and now it’s almost ready.”
What’s next
What matters in Newton
Herve also cited performance and improved template efficiency as goals for the coming cycle. “Performance is always something we can work on there are always things we need to improve at the template level so people can do more and be more efficient as they deploy.
Get involved!
“The main thing for us is to have feedback, it’s always interesting for us to hear from users,” he says. “Sometimes we’ll have an answer for them right away…and sometimes we won’t have an answer and it’s a way to improve the project.”
Use Ask OpenStack for general questions
For roadmap or development issues, subscribe to the OpenStack development mailing list, and use the tag [heat]
Meetings are held on IRC in #openstack-meeting on Freenode. See the Heat agenda page for times and details.
Keystone
What
Keystone is an OpenStack project that provides identity, token, catalog and policy services for use specifically by projects in the OpenStack family. It implements OpenStack’s Identity API.
Who Steve Martinelli, senior software developer at IBM and project team lead (PTL.)
*Burning issues**
“Our new V3 APIs have all the goodness in there, there’s a whole lot of awesome work being done and a lot of operators want to take advantage of it,” Martinelli says. “Trouble is, not all projects take advantage of V3, they sometimes make janky assumptions about V2..so we’re creating a cross-project initiative to make sure they are V3-ready.”
What’s next
What matters in Newton
Responding to the question by interviewer Carol Barrett about key priorities, Martinelli says “Given the fact that every project needs Keystone, it’s got to be fast to respond, it’s got to scale really well, and [it’s got to be stable] because there are some old deployments running Keystone. We can’t have any surprises for users.”
Get involved!
Use Ask OpenStack for general questions
For roadmap or development issues, subscribe to the OpenStack development mailing list, and use the tag [keystone]
Participate in the weekly meetings: held in #openstack-meeting, Tuesdays at 18:00 UTC.
Kuryr
What Kuryr
whose mission is to bridge between container framework networking and storage models to OpenStack networking and storage abstractions.
Who Antoni Segura Puimedon, PTL. Day job: Midokura.
Burning issues
“At the Austin summit, the biggest issue was satisfying use cases that operators have when they want to operate containers — because no one wants to run just Docker,” he says. “The focus was to provide the networking for Swarm, to design and stabilize the prototype that we have for Kubernetes and start to plan for Mesos integration and how to do all of that when containers run within virtual machines.”
What’s next
“If you use these APIs for all of your workloads, your operators can leverage the knowledge they have across the board,” he says.
What matters in Newton
“One of the first integrations will be Neutron, Magnum and Kuryr,” he says. “It may be a bit difficult but if it works, it’s going to provide a lot of value to OpenStack operators.”
Get involved!
Use Ask OpenStack for general questions
For roadmap or development issues, subscribe to the OpenStack development mailing list, and use the tag [kuryr]
Participate in the meetings:
Every two weeks (on even weeks) on Tuesday at 0300 UTC in #openstack-meeting-4 (IRC webclient)
Every two weeks (on odd weeks) on Monday at 1400 UTC in #openstack-meeting-4 (IRC webclient)
Cover Photo // CC BY NC
- Exploring the Open Infrastructure Blueprint: Huawei Dual Engine - September 25, 2024
- Open Infrastructure Blueprint: Atmosphere Deep Dive - September 18, 2024
- Datacomm’s Success Story: Launching A New Data Center Seamlessly With FishOS - September 12, 2024
