r/openstack • u/[deleted] • Nov 15 '22
STOP using packstack or devstack installation if you’re not a developer.
Pretty much everything is on the title, don’t use all in one solution and especially those two one when looking to « try Openstack ».
Many of you don’t get enough knowledge on Openstack but even lower linux/network/database/hypervisor/messaging queue or even just micro services concepts.
You’re basically shouting yourself in the foot and because you’ll probably fail install it as they’re not aimed to be used by beginners, you’ll end up being frustrated of Openstack.
Your first move should 100% time be manual installation step by step.
FWIW I’m an Openstack and kolla/kolla-ansible developer and professional architect on it since the first public 2010 releases and I’ve seen too much people failing to learn Openstack because they want to take the short path and focused on all in one installation.
3
u/nafsten Nov 16 '22
I get the idea in principle but I would never do a manual install of Openstack. I’ve been using Openstack since Mikata or so, and deployed by hand, with Fuel, Packstack, TripleO, but today I would old use Kolla-Ansible or Kayobe.
I get that building by hand let’s you learn, but are you ever going to use that in production?
1
Nov 16 '22
Oh no no no, don’t get me wrong, I’m specifically aiming to stop beginners using those tools and start learning the basics and inners of Openstack and infrastructure, not people who already know what they’re doing xD
I should probably have been more explicit about that.
Thanks for your kolla/kayobe usage :-) Great to read that.
1
u/nafsten Nov 16 '22
I don’t I’d agree it’s where beginners should start either. My advice to someone who wants to learn Openstack would be to do an all in one Kolla-Ansible install. That way with a little effort you would have a running install that you can kick the tyres on to see how it all works together.
All off the config files are in one place under /etc/kolla so you can easily go poke at them. If you want to see what a config does you can change it then eg docker restart nova_compute.
I wasted so much time on battling bits of Openstack that a good opinionated deployment tool (like Kolla) just deals with. Early concepts like “what sort of networking deployment do you want” - when I was a noob, I had no idea at all! It was only after I started actually using it did these things start to make sense
1
Nov 17 '22
I’m seeing an increasing number of beginners trying to install and work on Openstack, in a sense, it’s a benefit as it spread the word, but it’s also a curse as new comers are too many times students that don’t even gets the basics of I.T such as Networking, systems, database, communication channels etc.
There university sending them on such wide territories without proper basics learning is a waste of time and the bad side effect of that is people being traumatized by Openstack and so spreading bad opinion on it.
I mean, it’s like, I know nothing about boat but then in a suddent someone told me to drive a gigantic tanker that wasn’t maintained since a while on a storming ocean, that would be nuts and I would me too tell everyone how bad the experience was and how tankers should be much more simpler to operate.
2
1
u/vforvalerio87 Nov 17 '22
I'm looking to do a manual, step-by-step installation of all the OpenStack components, I have previous experience with Hyper-V and Xen (if that helps).
I don't have physical servers to try the steps on at the moment. I am under the assumption that you want a controller node, and the other server you chop for parts to vend stuff like volumes or VMs.
Is there a way I could set this up using two dedicated servers on any given hosting provider, if they are in the same local network?
If so, can anybody suggest a specific hosting provider, and possibly a hardware configuration that I need? (Like, multiple network interfaces per box or something).
I am open to helpful comments, links, blog posts, articles or whatever. Or if somebody is willing to put in some hours of tutoring I can just pay for that: how much time would be needed to set the whole thing up?
Thanks
2
Nov 18 '22
Alright, the bare minimum to be at ease and peace of mind while still being able to match 80/90% of real case production grade infrastructure is 4 physical nodes.
1x Control plane. 3x Hyperconverged nodes (Storage+Compute).
You either can perform that using regular VMs, or physical baremetal servers.
If you really want to do it with 2 servers you’ll end up having to choose services you’ll use and definitely have to use native cinder mode aka iscsi backend.
If you want to find help, just join us in here: https://discord.gg/vMfuUXaW
I’ll help you there as the reddit format isn’t appropriate for that.
3
u/Responsible-Dealer48 Jan 02 '23 edited Jan 02 '23
The documentation will make any beginner run up a tree. So many fragmented, outdated chunks of information strewn across the net makes it near impossible to start from scratch. If any technology sorely needs a "Start" button it's Openstack. That said, once it's cooking it's an incredible piece of engineering.
1
u/crono782 Nov 16 '22
Besides teaching the ins and outs of how openstack components actually work and fit together, I think manual installs are more fun and rewarding. Definitely my preferred method.
0
Nov 16 '22
The more you know about how each Openstack service is build and how it link/communicate with others, the more you understand Openstack itself and starting with a manual method is by default the best way to see that. All packstack/devstack/microstack solution are hidding away complexities and inners that for a beginner needs to be learned.
1
u/xmenkeyman Nov 17 '22
Start with Red Hat OpenStack and get experience with hard-way and promote yourself in which IT position are you working on 😊
1
u/LeadCreepy Nov 29 '23
hey, i'm a total beginner when talking about openstack and i have an academic project this time where i'm gonna have to use openstack and most of it's services , also docker it's a great project but i feel like i'm totally lost right now , like i don't get how each services communicate with each other , i even went to openstack doc but yet i feel lost , so if you do know any great video or any tips that could help i would be really gratefull and thanks !
16
u/firestorm_v1 Nov 15 '22
I regret that I do not have any awards but can only give you an upvote.
The absolutely best way to get familiarity with the Openstack infrastructure is to build it yourself from scratch. You only need twoservers for a proof of concept installation (three if you want to play with migration of instances between hypervisors)! You need one controller node and one (or two) hypervisor nodes. It doesn't require the most bleeding edge machines, no stupidly high amounts of RAM, no ridiculously huge disks, etc. You can do this with a couple of i5's and 16GB per node if that's all you got.
I built my first cluster out of spare parts, I had four decommissioned machines from a previous job, they were core 2 quads, 2GHz, 8GB RAM per box with a 2TB drive in each. I built out one controller and three hypervisors and it worked perfectly until I decommissioned it due to space constraints.
My second iteration was a bit more bougie, it is a Dell R610, 12 cores with 128GB RAM and 4T disk and I was able to spin up a controller node and four hypervisors on a single physical chassis using nested virtualization. It's not ideal (Openstack prefers physical hardware), but it will be more than adequate for learning and as a proof of concept.
Don't use any kind of orchestration or automation to build it out. Learn how the various components connect to each other, where their log files are, what the services are called, and what they provide. Learn about VM lifecycle management, learn about the networking and how IP addresses are allocated and released. Get to know how to use migration tools, play with NFS and iSCSI (you can use FreeNAS for this!). Break it and learn how to diagnose and fix it. That's the whole point of building an Openstack lab is to learn.
Professionally, I picked up the Openstack cluster at work when no one else on my sysadmin team wanted to learn it and maintain it. There's a lot to learn! I built the cluster over the weekend and when I started working user issues the following week, I was already more prepared and took on the work easily.