<div dir="ltr"><div><div><div><div><div><div>There are several fundamental problems in getting your feet wet in OpenStack.<br><br></div>First is that OpenStack is expecting to be installed into a rack of systems, not one system. While there are work arounds such as devstack, they fail to accurately produce a production environment or even a useful facsimile of one. One of the larger problems for many adopters of openstack at least initially is coming to grips with neutron and getting it plugged into their existing network environment. Devstack doesn't help you here much at all.<br><br></div>The other major problem is that there is something of a variety of flavors in terms of OpenStack, CFM, Networking, etc. OpenStack is flexible and supported by all the things. And as a result, there is no simple obvious path for deploying it. Some use puppet, some use chef, some ansible. Some use redhat, some ubuntu, some suse. Some use cisco, some arista, some bigswitch. The options go on and on. <br><br></div>I think there was a view early on that distributions of openstack would emerge. This has not been the case. The market has spoken and it has rebuked this idea. Others thought the future would be in appliances. Again the market spoke and rebuked this idea. There is an almost pathological hatred of appliances in the enterprise world after all.<br><br></div>So here we are. Facing a chicken and egg problem. For the established openstack user, you can use one of your greenfield environments to train up new employees, and many major deployers offer this training even to outside customers. The problem of course being you are being trained on their flavor of openstack, which may not be your own.<br><br></div>But, for the folks who are deploying for the very first time, they are entering into a sea of ideas, complex design patterns, and general distributed computing theory that is quite literally the subject of many masters and phd thesis today. It's not easy. And training up to a level of certitude in these murky waters is not easy.<br><br></div>I don't have an answer for you, in part because as I've been trying to spell out in detail, the scope is enormous. OpenStack sits upon a cross roads. And if you've not found it by following one of those pathes you may need to go back and begin the journey again at the beginning. <br><br>=/ <br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 30, 2014 at 7:36 AM, Ritesh Raj Sarraf <span dir="ltr"><<a href="mailto:rrs@researchut.com" target="_blank">rrs@researchut.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello James,<br>
<br>
On 12/30/2014 02:27 AM, James Dempsey wrote:<br>
> So, back to my original question:<br>
><br>
> What information do you give new users to help them be effective in the<br>
> cloud? What is your go-to demo for people who don't quite understand<br>
> what OpenStack is offering? How do you reach out to people in your<br>
> organizations who aren't OpenStack users yet, but probably should be?<br>
<br>
<br>
Like you, I'm fairly new to OpenStack, or even to the whole concept of<br>
Cloud in general.<br>
<br>
For what I have concluded so far, OpenStack (or Cloud computing in<br>
general), is a management interface for all your IT needs.<br>
<br>
Needs that comprise of Compute, Network and Storage.<br>
<br>
Cloud computing takes hundreds on physical nodes (comprising of compute,<br>
network and storage), makes a database of their abstracted interfaces<br>
(virtualization mostly) and provides a unified view.<br>
<br>
It allows you to spawn of virtual entities anywhere in that farm, thus<br>
making it a cloud.<br>
<br>
Management of this entire infrastructure, is the key component here.<br>
That's what OpenStack is.<br>
<br>
<br>
So far, the best start-up guide, for playing around is DevStack.<br>
<a href="https://github.com/openstack-dev/devstack" target="_blank">https://github.com/openstack-dev/devstack</a><br>
<br>
I don't find it very useful. One for because it is tightly tied to<br>
specific releases. And secondly because the entire process is very<br>
monolithic.<br>
<br>
<br>
Given the strong management stack that's been designed, for abstracted<br>
components, I'd have wished to see support for Linux Containers. That'd<br>
have allowed to prototype a 50 node setup on a single dev box.<br>
<br>
The only thing not covered, would have been the compute component, i.e.<br>
afaik Openstack Nova.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Given the large number of mailing lists I follow, I request you to CC me<br>
in replies for quicker response<br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</font></span></blockquote></div><br></div>