Thank you Outreachy!


This week was my last week in the Outreachy internship and, now that it’s over, I would like to share with you what I have to say about my whole experience.

Even if I had worked before in the OpenStack Zaqar project, during this internship I could get more deeply into it and understand it better. I have to say that at first, it was kinda hard to totally understand everything, and sometimes I felt like a fish out of the water, but the more I went on and the more I was able to get more familiar with everything. (more…)

Implementing missing endpoints

Hello people!

I’d like to share with you my weekly internship experience. This week I had the opportunity to finally start digging into the code! So at first, I had to understand how was the API organized. Once I understood that, I started working on the code by adding the features that were missing, which were:  ‘pool_update’, ‘pool_list’, ‘flavor_update’ and a ‘flavor_list’. There were other methods that had a similar functionality, so I could use those to implement something like that in the missing endpoints I was working on.

After writing code for these features, I started working on unit tests; as some of the methods I could look at in order to implement the missing endpoints, there were also some tests that I could use as examples to write my tests, even though I had some trouble understanding how to implement the flavor_update test. Flavors and pools usually have a similar implementation, but they are different from each other: you can think about pools like containers, or more precisely, like containers of data containers; while flavors basically have the main task of exposing pools.


Dealing with specs

Hello everyone!

So, as I said before, I got accepted to Outreachy and my whole task during my internship  is to work for OpenStack on python-zaqarclient adding support for Zaqar API v1.1. This week, I had to work on a specification that explained what features are missing in the client side of Zaqar, and which are the things that need to be done in order to add those features.

The thing about specs is that they have to be written with the markup language, which is a system for annotating a document in a way that is syntactically distinguishable from the text. Python uses a type of markup language for documentation, called reStructuredText, which is a component of Docutils.

When writing a spec you have to be very careful to the syntax, because writing something syntactically wrong, changes completely the output, and you’ll have to fix it in order to see your spec like it should be seen. Here’s a link to the reStructuredText, if you want to know more about it:

Anyway, working on specs was my first weakly internship experience, and I found out that you need to be very precise and be careful to the way you write them, but people is always open to help you understand what is wrong or what you could improve. It was also great to know that my mentor was always available and ready to help me if I had any kind of question.

So, that’s it! Be ready for my next posts because they’ll become more interesting every week!

Got accepted to Outreachy!

As I mentioned in my previous post, I got accepted to the Outreachy program, which is an internship for women and people from other underrepresented groups that can work, for a period of three months, on free and open source software while learning and improving  their abilities.

The internship will start on May 25 and I’ll be working for OpenStack on the zaqar-pythonclient, adding support for Zaqar API v1.1.

The internship will finish on August 25. So during all that time I’ll be writing about my experience in Outreachy, and about the task in which I’ll be working on during these three months.

I hope that my following posts about my learning process could be useful for you, and that my experience could help you to get more  enthusiastic about OpenStack, if you’re not already into it. So, let’s get started!

Stop being your own limitation

There’s a very famous quote from Gandhi that says: “be the change that you want to see in the world“, and I could change it a little bit and say “be the change that you want to see in your life“. Sometimes we just look for a turn in our life to happen, but then the fear overcomes and we decide to not change anything because, after all, our life isn’t that bad.

I’ll share with you something in which I’m working on; there are so many things, positive ones, that are happening to me right now: I got accepted to the Outreachy internship, which is fantastic, I’m now working on two projects that involve opening a chapter of two different and famous groups in my country, which is awesome! But the thing is that, shy and insicure as I am, sometimes fear overcomes and what I think is: “Will I be able to do this?”, “I’m only 20 years old, what am I doing?”.

Those are the kind of questions that come into my mind because, as well as so many people, I fear failure. But should I or we keep thinking that way? Those questions are the ones that can really, in my opinion, lead to the failure we all fear, because we are just putting limits to ourselves, we are not opening our minds to positive changes and opportunities.

The fact is that every time we have to take a decision, or an opportunity, small or big that it could be, we have to take that risk in order to that change to happen, and what I’ve understood is that there is no success without failures and risks being taken.

So what I can say is that when fear overcomes, we just need to stop thinking about the possible failure that the risk you are going to take could lead to, but try thinking, instead, about the positive changes that will happen in your life if you DO take that decision, about the accomplished you will feel after you take that risk and beat that fear you were having before.

Stop thinking about your limitations, because the thing is that those limitations are just in your mind, you can do anything you want, you can be that change you want to see in your life.