Becoming Native to
OpenStack
Musings from Our
(not Yet Completed) Journey
Uri Cohen
Head of Product @ GigaSpaces
@uri1803
...
Some
Background
First Leap:
From Closed
to Open
Source
Some
Insights We
Gained, One
Year into It
Some
Insights We
Gained, One
Year into It
Some
Insights We
Gained, One
Year into It
100s of servers
1000s of servers
Then Came
OpenStack
We Needed
a New
Architecture!
Best of
Breed
vs.
Homegrown
Python All
(Well, Most
of) the Way
From
Windows First
to
Linux First
From Dev
Only Team to
Dev+Ops
Becoming
Devops
Oriented
What It
Means for Us
to Be
OpenStack
Native
• Primary target cloud
• Tight integration with
most APIs (Nova,
Neutron, Cind...
Key
Takeaways
• It takes time… and
it’s never a one-
off
• Never be religious
about a language
/ tool / technology
Thank You!
https://github.com/cloudify-cosmo/cloudify-nodecellar-openstack
getcloudify.org
Upcoming SlideShare
Loading in …5
×

Becoming Native to OpenStack, Uri Cohen & Barak Merimovich

363 views

Published on

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.

Published in: Technology, Art & Photos
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
363
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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 
  • Becoming Native to OpenStack, Uri Cohen & Barak Merimovich

    1. 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
    2. 2. Some Background
    3. 3. First Leap: From Closed to Open Source
    4. 4. Some Insights We Gained, One Year into It
    5. 5. Some Insights We Gained, One Year into It
    6. 6. Some Insights We Gained, One Year into It 100s of servers 1000s of servers
    7. 7. Then Came OpenStack
    8. 8. We Needed a New Architecture!
    9. 9. Best of Breed vs. Homegrown
    10. 10. Python All (Well, Most of) the Way
    11. 11. From Windows First to Linux First
    12. 12. From Dev Only Team to Dev+Ops
    13. 13. Becoming Devops Oriented
    14. 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. 15. Key Takeaways • It takes time… and it’s never a one- off • Never be religious about a language / tool / technology
    16. 16. Thank You! https://github.com/cloudify-cosmo/cloudify-nodecellar-openstack getcloudify.org

    ×