Thanks a lot Ben, it's a really good Openstack 101 talks ! To help with video navigation : 00:03 - Introduction 03:03 - Why Cloud 09:41 - What is Cloud 19:49 - What is OpenStack 25:46 - Why Use It 29:22 - The Community 31:43 - Using OpenStack 36:37 - Architecture 48:22 - Distributions 49:22 - Managed OpenStack 50:28 - Q & A
This is very valuable information about open stack..thanks ben for your explanation about open stack.. before ,i was very inferior about what is openstack..but now after saw this vdo, I'm pretty much acquainted ..🤘
Thanks for sharing your time, knowledge, and experience; its greatly appreciated! This was a great introduction to OpenStack, very informative and a great place to start learning about the platform.
I was making a reference to Sun's early offering of zones. Containers have been around for a long time, lots of history there. Just using one implementation as an example. Remember this was 6 years ago :)
I still don't get it. Say I've got 100TiB in hard drives, 1TiB in RAM, 20 cores of CPU, etc., what do I need to do to turn them into a cloud? Do I need a computer running openstack specifically? Does the message queue need its own computer?
@@bens6697 Thank you for taking two years to craft the most perfectly unhelpful answer possible. Your dedication to being a nuisance is impressive enough that I'm not even annoyed.
Please stop using codewords for your components. Don't call it nova, call it compute. Or OpenCompute if you want to link it to your project. The documentation is because of that so hard to read that I just went back to doing it manually/scripting.
I don't think they are codewords, they are simply names that the developers use to differentiate the project. Similar to why we have Twitter, Google, Facebook and not "WhatYouAreDoingin140charsOrLess", "SearchForStuff", and "HeresAPictureOfMyLunch".
@@bens6697 github.com/openstack/nova Look at the branches. Look at the "I will not use a number because that dehumanizes my codebase". No, this is actually a problem. I contrast this with the smartos releases which contains an UTC timestamp. When I saw that I felt the suffering the programmer had. I too suffered the daylight saving problem.
@@BspVfxzVraPQ The branches are named for the releases. If you know the release you want to branch, I don't see the problem. Using a UTC timestamp for the branches would actually confuse matters IMHO.
I came here without any knowledge about OpenStack. After this video, I'm totally clear what it is and what is its purpose. Awesome introduction.
Glad to know it helped.
Thanks a lot Ben, it's a really good Openstack 101 talks !
To help with video navigation :
00:03 - Introduction
03:03 - Why Cloud
09:41 - What is Cloud
19:49 - What is OpenStack
25:46 - Why Use It
29:22 - The Community
31:43 - Using OpenStack
36:37 - Architecture
48:22 - Distributions
49:22 - Managed OpenStack
50:28 - Q & A
No prob, you're welcome!
This was the exactly the video I needed for an intro to OpenStack. Thank you for the clear explanation!
You're welcome!
The explaination is totally spot on! The best intro to cloud/openstack I've came across till now...
Thank you for your feedback, I really appreciate it!
This is very valuable information about open stack..thanks ben for your explanation about open stack.. before ,i was very inferior about what is openstack..but now after saw this vdo, I'm pretty much acquainted ..🤘
I've been looking for a video like this and Ben delivered this in a very clear and good paced way, thanks a lot!
No problem, you're welcome
This was the exactly the video I needed for an intro to OpenStack . thank you Ben
You're very welcome
Thanks for sharing your time, knowledge, and experience; its greatly appreciated! This was a great introduction to OpenStack, very informative and a great place to start learning about the platform.
You are very welcome!
The presentation was really useful as it gives a good insight into openstack for beginners.
Thanks !
Thanks for the review!
Thank you for the video. Nice introduction to OpenStack.
You are welcome.
What a great presentation! Should have appeared in my watch list two years ago. I love your style Ben. Thanks a lot!
Thank you!
Thank you very much for this video. I learned a lot as a beginner
You're welcome.
Thanks Ben!
You're welcome
16:49 IaaS , PaaS, SaaS
19:43 What is OpenStack
43:10 - A view of how OpenStack services work(a generic model for all services OpenStack)
@комиссар полиции обвиняет play it in 2X!
good job, thanks
you are welcome
Thanks!
you are welcome
i guys should give the slide link to download, please?
see below
Anyone have the slide deck?
You can try reaching out to Ben on Twitter: @bensilverm
Christopher Moriarty you can get them here www.slideshare.net/mobile/secret/mzSXGmlE9nwVCW
When was this held? Year?
2017, Sydney Australia
@@bens6697 thanks much
Where can we get the slides ?
www.slideshare.net/secret/mzSXGmlE9nwVCW
@@bens6697 thank you sir
@@Alain9-1 you are welcome!
Excellent talk. WaaS Weight Loss as a service...giggle. Did you say containers were mostly living in Sun? Or did I misunderstand?
I was making a reference to Sun's early offering of zones. Containers have been around for a long time, lots of history there. Just using one implementation as an example. Remember this was 6 years ago :)
21:20 not only sun.. cgroups, chroot, namespaces have been a thing for a long time :P
That is true, wasn't trying to slight those communities, just an unintended oversight.
To contact the presenter, check me out on Twitter @bensilverm or LinkedIn at www.linkedin.com/in/benjsilverman/
You
14:40 my cup says: there is no cloud it is just someone else computer.
I thought Google designed the modern data center, self provisioning, sdn using and I am pretty sure Amazon copied Google data center architecture
I still don't get it. Say I've got 100TiB in hard drives, 1TiB in RAM, 20 cores of CPU, etc., what do I need to do to turn them into a cloud? Do I need a computer running openstack specifically? Does the message queue need its own computer?
You need a cloud platform software, one of which is OpenStack.
@@bens6697 Thank you for taking two years to craft the most perfectly unhelpful answer possible. Your dedication to being a nuisance is impressive enough that I'm not even annoyed.
@@Asdayasman You're welcome. Please check out all of my other videos for maximum enjoyment.
bluemix? really? xD
What is cloud? Somebody else's problem.
Please stop using codewords for your components. Don't call it nova, call it compute. Or OpenCompute if you want to link it to your project. The documentation is because of that so hard to read that I just went back to doing it manually/scripting.
I don't think they are codewords, they are simply names that the developers use to differentiate the project. Similar to why we have Twitter, Google, Facebook and not "WhatYouAreDoingin140charsOrLess", "SearchForStuff", and "HeresAPictureOfMyLunch".
@@bens6697 github.com/openstack/nova
Look at the branches. Look at the "I will not use a number because that dehumanizes my codebase". No, this is actually a problem.
I contrast this with the smartos releases which contains an UTC timestamp. When I saw that I felt the suffering the programmer had. I too suffered the daylight saving problem.
@@BspVfxzVraPQ The branches are named for the releases. If you know the release you want to branch, I don't see the problem. Using a UTC timestamp for the branches would actually confuse matters IMHO.
13 minutes of nothing so far