Aspiring to be an openstack developer

asked 2017-04-27 02:06:07 -0500

DarkKnight gravatar image

updated 2017-04-27 02:08:09 -0500

I work as a openstack administrator. While i have thoroughly enjoyed the learning here, I have noticed a behavioral pattern when i attempt any issue.

I usually start by executing certain commands to know the status, deending upon the o/p, i go ahead and check the relevant logs. I excitingly search for errors inside the logs and try to understand that if it has anything to do with some configuration changes, only a few handful i manage this way. Next, i laboriously copy the error and fall back on the google search and then on the openstack forum. Most of the time, I am served. But some of the times, either the error is so uncommon or doesn't attract the community attention, I mostly get stuck.

While, I have tried to see the traceback and jump to the last python file (along with the line number) in the traceback and logged some variable values, this approach is not helping me beyond a limit.

Hence from all the experienced openstack developers and enthusiasts i want to ask if there is a step-by-step approach here.I would appreciate if the answer also lists down some prerequisites to get started with openstack debugging and further development such as Python, or some other important sub-topics within Python, devstack, code review and test cases.

PS: I have a beginner level programming experience with Python and OOPS.

edit retag flag offensive close merge delete


Hi, take a look at this summit talk about troubleshooting and python.

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2017-04-27 05:16:03 -0500 )edit

Thanks for the suggestion, but actually i am looking for the next level to this video.

DarkKnight gravatar imageDarkKnight ( 2017-04-27 23:25:57 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2018-04-16 19:51:03 -0500

mattoliverau gravatar image

Well your able to read python so that's a great start! The next level would be understanding the project in question's structure and logic. And you've obviously realised OpenStack is a _big_ project :)

The best way I've found to help is getting involved. If your a little unsure, go help code review patches.. Where you can go ask questions inline or jump on the projects IRC channel. Each project will have their own idiosyncrasies. So first pick the one you know most about (administering) or even the area of tech you have a passion about, and jump in their channel. If your seeing some stack traces in logs, you could see if there is already a bug for it, or raise one.. or if your feeling confident try an either tackle it or go find a bug marked as low-hanging fruit, to get you started. Sometimes the only way to learn is to get your hands dirty.

In any case, there is a new SIG (special interest group) who have formed to help new contributors (experienced or beginners) get started with OpenStack, we're called the First Contact SIG. And have contacts/liasons with all the OpenStack projects (or can at least introduce you to projects) and will be there to get you onboarded and to answer any quetions.

Another great source of information is the OpenStack community portal and the contributor guide, both we are actively continually building up and improving.

There is also the Openstack Upstream Institute (OUI) who put on new contributor trainings, usually on the weekend before a summit. Where you'll meet a bunch of people and mentors from different projects and help start building your network :)

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-04-27 02:06:07 -0500

Seen: 153 times

Last updated: Apr 16 '18