Transforming your product to be OpenStack Native: OpenStack is an open source cloud infrastructure, unlike typical cloud environment it was built to allow deeper integration with the underlying infrastructure services such as security, metering, networking etc. In this talk i wanted to share the experience of what it takes to transform an existing enterprise product into OpenStack and why we have chosen to take a native OpenStack approach which include integration with the networking, security etc.
How Red Hat Uses FDO in Device Lifecycle _ Costin and Vitaliy at Red Hat.pdf
Becoming Native to OpenStack, Uri Cohen & Barak Merimovich
1. Becoming Native to
OpenStack
Musings from Our
(not Yet Completed) Journey
Uri Cohen
Head of Product @ GigaSpaces
@uri1803
Barak Merimovich
Cloudify Group Leader
@barakme
#openstackil
14. What It
Means for Us
to Be
OpenStack
Native
• Primary target cloud
• Tight integration with
most APIs (Nova,
Neutron, Cinder,
Keystone, soon also Heat
and Ceilometer)
• Community Involvement
15. Key
Takeaways
• It takes time… and
it’s never a one-
off
• Never be religious
about a language
/ tool / technology
Goals:
Why Workflows are critical part of automation of applications on the cloud
Clarify the need for something like OpsWorks
Why do we think this OpsWorks is needed in addition to other projects
XAP, Why Cloudify, Java infra, geared for high perf, short detection times -->scales up to a few hundred of nodes legacy protocols
devops - larger scales, dynamic languages, a lot of choices
devops - larger scales, dynamic languages, a lot of choices
devops - larger scales, dynamic languages, a lot of choices
OpenStack is here to stay, that’s why we’re all here. Most of the orgs we talked with have an openstack initiative, we wanted to be aligned with it
python as a foundation - much more suitable for devops workloads, native integration with OpenStack (new releases), available OOTB unlike Java / Ruby / others. Talk about the transition
Move from windows mostly to linux mostly, eat our own dog food and use what are users will be using
devops - larger scales, dynamic languages, a lot of choices