<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Archana Kumari on Medium]]></title>
        <description><![CDATA[Stories by Archana Kumari on Medium]]></description>
        <link>https://medium.com/@archanaserver?source=rss-177b5962489------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5aF2XCch9uKmH8_LiFK3wg.jpeg</url>
            <title>Stories by Archana Kumari on Medium</title>
            <link>https://medium.com/@archanaserver?source=rss-177b5962489------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:46:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@archanaserver/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Career goals after Outreachy]]></title>
            <link>https://archanaserver.medium.com/career-goals-after-outreachy-3dca16c6b4af?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dca16c6b4af</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Wed, 18 Aug 2021 09:04:11 GMT</pubDate>
            <atom:updated>2021-08-18T09:04:11.694Z</atom:updated>
            <content:encoded><![CDATA[<h4>I will be sharing my career goals in this blog post.</h4><p>Hello world o/</p><p>As my <a href="http://outreachy.org/">Outreachy internship</a> has come to an end, only a few weeks are left for me to get the best out of it and perform much better on the tasks which I’m working on currently. I’ll be sharing my career goals in this blog post, as this is the prompt of weeks 9–10. Also, I’m not going to share in detail my goals yet it will be an overview of what would be my next step. So let’s start :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*UwEFGv1OSf7DZAjjNoPfsQ.png" /></figure><p>Okay, so it’s been more than 2 months for me to work as an Outreachy intern for OpenStack. I took this opportunity to get myself out of my comfort zone by working on completely different projects, with different skill sets and with different people(they are the best). When I started contributing to the OpenStack project I was almost on zero Level. I can say I wasn’t familiar with much of the stuff I worked on in the past few months even though I faced so many struggles setting up the whole project environment. Also in the beginning my skill set was not compatible with the OpenStack project, but somehow I managed to contribute to the first bugfix just by assigning myself for some low-hanging-fruit bugs and by looking into the initial codebase.</p><h4>What I have learned?</h4><p>So there are many new things I have learned and still getting introduced to new things daily, whether it is about a new module of python or about improving this blog post. I can’t stop myself from learning and I won’t stop myself from asking so many questions to anyone who has some good taste of it. Once this internship will end I hope I will be able to say that I’ve learned many new technologies, managing, mentoring and organizing skills for my career. Now I’ve become more of a person who will never stop contributing to Open Source projects, especially OpenStack projects(I LOVE OPENSTACK), even after the end of this internship.</p><p>During this internship, I started working on creating an OpenStack client (OSC) plugin within <a href="https://docs.openstack.org/python-manilaclient/latest/">python-manilaclient</a> to support OSC users , enhancing the usability of manila within an OpenStack cloud. This project skill descriptions are Python, GNU + Linux system administration and BASH. Till now I’ve contributed to a few bug fixes on manila client, adding waiter support on some commands like share group and share server commands. Right now I’m contributing to building two openstack shared command-line interfaces. The first one is a share group and the second one is a share group snapshot.</p><p>At the beginning of this project, I was unfamiliar with Python but I chose to learn it and work on it. The things which I’ve learned so far during the contribution are REST APIs, Shared file systems, good coding practice in Python and cloud computing paradigms. By working on problems at a cloud-scale, I got an opportunity to enhance my thinking and approach in terms of orchestration, asynchronous communication between microservices and performance.</p><h4>Here are some more questions, that I would like to highlight —</h4><p><strong>1. Are you looking for a job, internship, a grant, a volunteer position, or some type of other opportunity?</strong></p><p>Yes, I’m looking for a full-time job. Also, I’m comfortable with internship roles. One thing I want to mention here is that I love doing technical community work, so you can reach out to me for some volunteer work.</p><p><strong>2. What types of work would you like to contribute to?</strong></p><p>I’m looking to contribute to an open-source community project that operates in a globally distributed environment. Also if the skill set for the project matches with my current internship project that would be amazing. Apart from that, I would also love to explore and work on some other technical skills and make some contributions.</p><p><strong>3. What tools or skills do you have that would help you with that work?</strong></p><p>I have more than two years of learning experience in Web development and building projects using tools/skills like JavaScript, NodeJS, ReactJS and Firebase. Also, I have done Udacity Frontend certification with the help of Google Scholarship. You can find all my projects <a href="https://github.com/archanaserver">here at my GitHub profile</a>. I’m familiar with Python and Django too, as this was the required skill set for the OpenStack project. I believe all of these skill sets would help me with the work I’m looking for.</p><p><strong>4. What tools or skills would you like to learn?</strong></p><p>I would like to learn cloud computing concepts such as Kubernetes, Docker, DevOps and its tools, Containerization, Go programming language, Azure, AWS and more. This list will keep on increasing and would never stop.</p><p><strong>6. When are you available to start work?</strong></p><p>My internship will end on 7th September 2021 so I’m available to start after the end.</p><h4>8. Are you looking for a remote job?</h4><p>Yes, my first preference is remote work. I have experience working as a remote worker in two internships. But I’m open to relocating within India or internationally too.</p><p>That’s all I can share about my career goal, <strong>if my profile fits the type of candidate you are looking for please reach me out through email at ak31960466@gmail.com or you can DM me on LinkedIn/Twitter</strong>. I would love to have an informal chat with you. Also, if you want to help me out then please share this blog and my profile in your circle.</p><blockquote><strong>My profiles:</strong></blockquote><blockquote>See my OpenStack contributions on Gerrit: <a href="https://review.opendev.org/q/owner:ak31960466%2540gmail.com">https://review.opendev.org/q/owner:ak31960466%2540gmail.com</a></blockquote><blockquote>Twitter: <a href="https://twitter.com/archanaserver">https://twitter.com/archanaserver</a></blockquote><blockquote>LinkedIn: <a href="https://www.linkedin.com/in/archanaserver/">https://www.linkedin.com/in/archanaserver/</a></blockquote><blockquote>GitHub: <a href="https://github.com/archanaserver">https://github.com/archanaserver</a></blockquote><p>Thank you for reading it!🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dca16c6b4af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 9 & 10]]></title>
            <link>https://archanaserver.medium.com/outreachy-week-9-10-233aac81791b?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/233aac81791b</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[internship-experience]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Fri, 30 Jul 2021 18:11:56 GMT</pubDate>
            <atom:updated>2021-07-30T18:11:56.979Z</atom:updated>
            <content:encoded><![CDATA[<h4>The theme for this week is “Career opportunities”.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*umHiaygWVkHclL_NLurrVQ.png" /><figcaption>✨ week 9 &amp; 10 ✨</figcaption></figure><p>So my last two weeks, hmm? I’m still figuring out all the things I have done in the last two weeks. I’m being lazy here! I guess things are going pretty well here, but all I can say is my last two-week calendar was on calm mode. 🥤</p><p>There was not much that happened but I started my contribution towards OpenStack CLI support for Manila. I’m enjoying so much the whole process of contributing to this project.</p><h4>My Contribution 👩🏻‍💻</h4><p>So let’s talk a little bit about my project <strong>OpenStack Client Implementation for Manila</strong>. This project is all about creating an OpenStack Client(OSC) plugin within python-manilaclient so that it can support OSC users also enhances the usability of Manila within an OpenStack cloud.</p><p>Currently, I’m working on two patches i.e. adding share_group and share_group_snapshot commands, so that CLI support both the commands. This is fun and there is so much to learn at every step.</p><p>If I talk about share_group command implementation then there are more subcommands to implement under this command like share_group_create, share_group_delete, share_group_list, share_group_show, share_group_set and share_group_unset. Right now I have done implementing share_group_createcommand and I make Zuul happy today. 🥂</p><p>Now the share_group_snapshot command implementation, this one is still in work in progress mode and I’m actually reading some documentation for it. Here is about my last two weeks in short:</p><p><em>Week 9: all about reading so much documentation and having a good knowledge of the project I’m working on. 🤓</em></p><p><em>Week 10: coding, coding and more coding!!🙇🏻‍♀️</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSTLj8QUhg25pe%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSTLj8QUhg25pe%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FSTLj8QUhg25pe%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="195" frameborder="0" scrolling="no"><a href="https://medium.com/media/515243ee9256cdb8c6191734d173b574/href">https://medium.com/media/515243ee9256cdb8c6191734d173b574/href</a></iframe><p>I attended an amazing intern chat conversation on Zulip where everyone talks about the different career opportunities they are looking for and some amazing advice from past interns and mentors for our future.</p><p>The discussion was about everyone brainstorming different career paths in the technology industry(and free software) and brainstorming additional opportunities to work on free software.</p><p>Also, I have learned about Python debugging and writing good unit testing in the same. I guess I’m moving to become a good Python Developer 🙈</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FkrkrHAEodHgzP72rTI%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FkrkrHAEodHgzP72rTI%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FkrkrHAEodHgzP72rTI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/dbcc5cfbe8249c12e13ec54a32ce0db7/href">https://medium.com/media/dbcc5cfbe8249c12e13ec54a32ce0db7/href</a></iframe><p>🎧: <a href="https://www.google.com/search?q=One+Direction+-+Night+Changes&amp;oq=One+Direction+-+Night+Changes&amp;aqs=chrome..69i57.564j0j1&amp;sourceid=chrome&amp;ie=UTF-8">One Direction — Night Changes</a>, my current favourite 🎶 (done writing the blog with this song)</p><p>That’s all I have for now 🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=233aac81791b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Modifying Expectations: Progress Report]]></title>
            <link>https://archanaserver.medium.com/outreachy-modifying-expectations-progress-report-10011e99ba5c?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/10011e99ba5c</guid>
            <category><![CDATA[internship-experience]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Mon, 19 Jul 2021 21:11:44 GMT</pubDate>
            <atom:updated>2021-07-19T21:11:44.112Z</atom:updated>
            <content:encoded><![CDATA[<h4>Modification on your goals is perfectly fine!</h4><blockquote><em>This is the fourth blog in the series of Outreachy Internship blogs. As per the goal of the weeks I am publishing a blog every 2nd week, for the next 3 months. The prompt of this week is to </em>write a report about your progress on your project and what modifications happen in project goals.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dG1lzqSNOqzlKqWPfGvzhQ.jpeg" /><figcaption>Image Credit: Leon on <a href="https://unsplash.com/photos/vbxyFxlgpjM">Unsplash</a></figcaption></figure><p>In this blog, I’m going to talk about what I have accomplished so far, what goals took more time than expected and my modified goals for the second half of the internship.✨ Well, I am now half-way done with my Outreachy internship at OpenStack. Let me grab my cup of iced coffee and celebrate this with my laptop, because why not? huh! I’m on the second half of the internship 🎉💃🏻</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZdg7kl9bnyqXrPH2jq%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZdg7kl9bnyqXrPH2jq%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FZdg7kl9bnyqXrPH2jq%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/1fca048fc001beb6558987d67454337c/href">https://medium.com/media/1fca048fc001beb6558987d67454337c/href</a></iframe><p>I’ve been learning a lot about the OpenStack ecosystem from the starting of the project tasks and how I can complete the goals of the project. 🌺</p><blockquote>Before starting the blog I want to mention that my internship got two weeks extension, and now <strong>my end date of the internship is Sept. 7, 2021 :)</strong></blockquote><p>Previously my project task was to adding support to share type quotas in the Manila UI project. Manila has the option to define the quotas for a given share type. In setups with multiple share-types, per share type quota will allow resource providers to have better control over the provisioned resources. So my task was to implement this in the UI. But now due to some issues, there is some modification in my project task. I don’t want to share about the modifications here. You can keep reading to find :D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5H-gxrNKk4mfRR09IGKOg.png" /></figure><h4>What was your original internship project timeline?</h4><p>During the submission of the final application, we applicants are required to submit the project timeline that I’ll be working on for the next 3 months. This timeline covers everything about the project and the task.</p><p>As per the project, my timeline was something like this — get familiar with Manila UI code, contribute to small fixes, get familiar with share type quotas API, draft the mock of how the share type quotas visual component should look like, draft a basic layout of the visual components needed to work on the implementation, start coding to ready the base visual component up for review, continue coding…, include unit tests, work on documentation and done!</p><h4>What goals have you met?</h4><p>Okay so if I have to talk about my goals then I can say that there are many goals that I met and some of are below, because in those I faced many issue to complete it.</p><ul><li>OpenStack DevStack environment setup for the OpenStack project. It was very challenging for me due to some new issues hit every time when one got fixed.</li><li>Getting familiar with the code I’m currently contributing on projects like — python-manilaclient and manila-ui.</li><li>Getting familiar with the OpenStack ecosystem, now I know the flow — picking up the issue, assign it to myself, start making changes for that and submit it for review in the Gerrit.</li><li>Also making myself familiar with the Python syntax was a big task :/</li></ul><h4>What have you accomplished in the first half of your internship?</h4><p>My two patches got merged into OpenStack. Here are both:</p><ol><li>799997: Add — wait flag to the create share group operation | <a href="https://review.opendev.org/c/openstack/python-manilaclient/+/799997">https://review.opendev.org/c/openstack/python-manilaclient/+/799997</a></li><li>795990: Replace assertDictMatch with assertDictEqual method in tests | <a href="https://review.opendev.org/c/openstack/manila/+/795990">https://review.opendev.org/c/openstack/manila/+/795990</a></li></ol><p>Contributing to both the patches was very challenging for me, from not knowing anything about Python and unit testing to working on such patches with a huge codebase in Python. All I can say is I have learned a lot(i mean it!) when I worked on both the patches. Also, I am now more familiar with OpenStack ecosystem.</p><p>I am continuously working on the patches with are assigned by my mentor and learning too 🙋🏻‍♀️</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT5LMUt1dWrBQtacJG%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxT5LMUt1dWrBQtacJG%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxT5LMUt1dWrBQtacJG%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="331" frameborder="0" scrolling="no"><a href="https://medium.com/media/389c9288cec0941baf8d2a7725d9da07/href">https://medium.com/media/389c9288cec0941baf8d2a7725d9da07/href</a></iframe><h4>What project goals took longer than expected?</h4><p>Setting up the DevStack environment into my VirtualBox took a lot of time and ended up working on Vexxhost VM provided by mentor. Also, sometimes going through the reviews which are left by reviewer and making things clear before working on it took a lot of time too.</p><p>I believe these all took longer than expected due to the the resources I wasn’t able to find resources on time and I was afraid to ask question again and again to my mentor in the beginning of the internship. But now I ask many question multiple times in a day and make sure that I know things clearly before I start working on those.</p><h4>What is your new plan for the second half of the internship?</h4><p>So here comes the modification part, I learnt that<strong> modifying your project timeline to set more realistic goals is a skill all contributors need to learn. </strong>I had discussion with my mentor about my internship tasks about the second half of the internship — we ended up dropping the Manila UI part due to less reviewer for Manila UI projects and moving to the another Manila project which is <strong>OpenStack Manila — OSC Integration with python-manilaclient.</strong></p><p>This project is all about building OpenStack CLI(OSC) plugin within python-manilaclient to support OSC users enhances the usability of ‘manila’ within an OpenStack cloud. In this project I’ll be creating a CLI support for Manila.</p><p>I learned about this project and find it interesting to work on, though I love to work more on UI part but moving to something new and getting out of my comfort zone will surely shape me in something new :)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FTlsxMR9yIQI6tQJ1c0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FTlsxMR9yIQI6tQJ1c0%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FTlsxMR9yIQI6tQJ1c0%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="242" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7ead4bce55f4ed0f02c32ade41ee8bb/href">https://medium.com/media/c7ead4bce55f4ed0f02c32ade41ee8bb/href</a></iframe><p>That’s all folks! I think I’m done here. See you on the other side of the internship. I’m damn excited for the tasks I’ll working on for the upcoming weeks 🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10011e99ba5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 8]]></title>
            <link>https://archanaserver.medium.com/outreachy-week-8-7a048251c1f?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a048251c1f</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Sat, 17 Jul 2021 18:18:38 GMT</pubDate>
            <atom:updated>2021-07-17T18:18:38.549Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is the eighth weekly blog of my internship.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7Yafy9YGHTPAhh8s_MksFg.png" /></figure><p>This was a wonderful week in my internship🌻 Let’s take a look then:</p><h4>My first two patches get merged 🎉</h4><p>Starting with some great stuff i.e. yay! my two patches get merged into OpenStack and I can’t express my feeling how happy I feel during the whole week :) You can find both here if you wanna learn more about it:</p><ol><li>799997: Add — wait flag to the create share group operation | <a href="https://review.opendev.org/c/openstack/python-manilaclient/+/799997">https://review.opendev.org/c/openstack/python-manilaclient/+/799997</a></li><li>795990: Replace assertDictMatch with assertDictEqual method in tests | <a href="https://review.opendev.org/c/openstack/manila/+/795990">https://review.opendev.org/c/openstack/manila/+/795990</a></li></ol><p>Contributing to both the patches was very challenging for me, from not knowing anything about Python and unit testing to working on such patches with a huge codebase in Python. All I can say is I have learned a lot(i mean it!) when I worked on both the patches. Also, I am now more familiar with OpenStack stuff.</p><h4>GHC Open Source Day</h4><p>As I was mentoring for OpenStack project, it was an amazing experience for me because I got out of my comfort zone and delivered a presentation about <strong>Git and Gerrit</strong> and <strong>shared about Outreachy internship and my Outreachy Internship experience</strong>. The best part was when I heard from my mentor that I was awesome during the presentation :)</p><h4>Python course</h4><ul><li>I’m contributing to the OpenStack projects which are based on Python skillsets. I started improving those skills by looking into Python courses and blogs. I’m getting so much comfortable with Python code now.</li><li>I started building little projects and doing some challenges in Python just to explore something new daily in it.</li><li>In the upcoming week, I’m looking to learn about unit testing in Python.</li></ul><h4>Ongoing work and some updates</h4><ul><li>My internship has been extended for two more weeks and I’m happy because I’m enjoying my internship and building my skillsets :) Well, this is extended because things were slow in the starting weeks(due to some blockers) and we were not able to focus on the main project tasks. So outreachy organizers decided to give me two more weeks so that I can get full time to work on project tasks. ✨</li><li>Okay, so there is one more update which is that from now we are dropping manila ui stuff from my task list and moving forward to focus on contributing to another project i.e. OpenStack Manila — OSC Integration with python-manilaclient. (well more on this later)</li><li>Currently, I’m working on two patches from python-manilaclient project- in which the first one is all about adding — wait flag in delete share group operation. This will make the CLI wait for the operation to be completed before returning to the prompt. The second one is all about adding a “ — wait” option for managing/unmanaging a share server, this one is similar to the previous one.</li></ul><p>Yep! So that’s all I have for this week 🙋🏻‍♀️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a048251c1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 7]]></title>
            <link>https://archanaserver.medium.com/outreachy-week-7-c4aa606df119?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4aa606df119</guid>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[internship-experience]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Sun, 11 Jul 2021 19:52:10 GMT</pubDate>
            <atom:updated>2021-07-12T15:54:41.148Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is the seventh weekly blog of my internship.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*AtU3RUw5oVHevy1m1PdA5g.png" /><figcaption>✨ week 7 ✨</figcaption></figure><p>Hi there, so it’s the end of week 7 and all I can say is that it’s been a rollercoaster ride till now. 🎢 Some days were easy and some days were really difficult for me when I had no idea how to continue working on my task or what to do to move forward. Luckily I am under the guidance of amazing mentors who are helping me continuously to implementing my ideas efficiently into the project tasks.</p><p>Also, this week I did my past week reflection on my internship project tasks, my progress, my learning, important moments and some lessons I learned from the past few weeks. I usually get down sometimes and analyse everything — what went well, what could have been improved upon, and do I need to recreate my system to hit those goals. Along with this I also did my mid-year life audit check.</p><h3>˗ˏˋ archana ´ˎ˗ on Twitter: &quot;i just did my mid-year reset (goals and life audit check-in), my journal looks so good and fresh right now 🌺🌿so many things checked off from the list and many new things added 🌻 it&#39;s time to crush the rest of the stuff! / Twitter&quot;</h3><p>i just did my mid-year reset (goals and life audit check-in), my journal looks so good and fresh right now 🌺🌿so many things checked off from the list and many new things added 🌻 it&#39;s time to crush the rest of the stuff!</p><p>Okay, that’s enough talk! Let’s see about this week progress tasks and did I cross that off from the list. hmm!? 🤔</p><h4>What I have done this week?</h4><ul><li>So Monday starts with working on API microversion update patch <a href="https://review.opendev.org/c/openstack/manila-ui/+/798807"><em>798807: API v2.39, added share-type quotas</em></a>, this was about adding share type quotas into the initial patch and commit it for review. It gets reviewed by my mentor, I worked on their comments which showed ‘<strong>Build succeeded</strong>’ in green ;)</li><li>I did <strong><em>pair programming with Victoria(mentor)</em></strong>. I was quite scared at first when I heard about we are going to do a pair programming session. Because it was my first time though, but this ended up with a great and helpful session. I got to learn so many things like the workflow that I should follow when I get stuck somewhere and taking references from other codes is okay! :p</li><li>About the patch <a href="https://review.opendev.org/c/openstack/manila/+/795990"><em>795990: Replace assertDictMatch with assertDictEqual method in tests</em></a>. Well, this one is taking so much time because I didn&#39;t clearly understand all parts of this issue when I started working on this. This one is still in progress.</li><li>I‘m now working on a new task that is similar to this one(<a href="https://review.opendev.org/c/openstack/python-manilaclient/+/789018">789018: Add — wait flag to the delete share group operation</a>). But it’s about <a href="https://review.opendev.org/c/openstack/python-manilaclient/+/799997">799997: Add — wait flag to the create share group operation</a>. This one is similar to the adding delete option to share group operation but to submit my first patch for this one, I spend so much time reading all the codebase and understanding how can I work on this command. For now, I can see some reviews on this patch from my mentor, I’ll work on this in the next week. :)</li><li>I assigned myself some new tasks on python-manilaclients and manila-ui projects. <strong>I always make sure that for every task, I am getting myself out of my comfort zone so that I explored and experiment more</strong>. Here is the tasks list:</li></ul><p>→ <a href="https://bugs.launchpad.net/manila-ui/+bug/1516843">https://bugs.launchpad.net/manila-ui/+bug/1516843</a></p><p>→ <a href="https://bugs.launchpad.net/manila-ui/+bug/1599788">https://bugs.launchpad.net/manila-ui/+bug/1599788</a></p><p>→ <a href="https://bugs.launchpad.net/python-manilaclient/+bug/1898315">https://bugs.launchpad.net/python-manilaclient/+bug/1898315</a></p><ul><li>As usual, I had a 1:1 session with my mentor, we had some great discussions on next week tasks and our progress update.</li></ul><p>→ I received positive feedback and some suggestions for all my contributions. My mentor always making sure that I kept progressing into my contributions and sharing with me some external opportunities in which I can take part on.</p><p>→ We had a discussion about Python stuff in which I need to work on, so I started working on those by going through a Python course.</p><p>→ Also had a discussion about <a href="https://anitab-org.github.io/open-source-day/upcoming/">OSD Summer</a> mentor stuff. I’m excited for the next week because this is the first time I’m going to do mentorship for such a great program.</p><ul><li>Furthermore, I jumped on this issue → <a href="https://bugs.launchpad.net/manila-ui/+bug/1599788">Share Type Create and Update forms need separate fields for fixed parameters</a>. I started working on this issue by reading some documentation, looking into the ui side and figuring what I need to fix here by reading the bug description and all previous comments(whoever worked on this issue previously). I am quite excited to work on this issue because I am going to investigate some manila ui side work. Let’s go for this! ☁️</li></ul><p>That’s it about this week, I’m enjoying every day with new things to work on and I’m so proud of myself that I made this far along with my mentor 🌻</p><blockquote>I’m just so proud of myself right now✨</blockquote><p>Thanks for reading!</p><p>:wq till next week</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4aa606df119" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 6]]></title>
            <link>https://archanaserver.medium.com/outreachy-week-6-693ee6115eaa?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/693ee6115eaa</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[internship-activities]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 11:06:25 GMT</pubDate>
            <atom:updated>2021-07-06T11:10:43.157Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is the sixth weekly blog of my internship.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*eYqbjI3Ijr-sSTUNtq2mnA.png" /><figcaption>✨ week 6 ✨</figcaption></figure><p>Hi again :) This blog is going to be short and just the overview of what I have done.</p><h4>What I have done this week?</h4><ul><li>I started this week learning about API microversion updates, which we do when there are some changes in the API. I’m going to work on implementing share_type_quotasso I need to do this.</li><li>I submitted my initial patch in Manila UI after adding share_type_quotas it. You can find my patch here: <a href="https://review.opendev.org/c/openstack/manila-ui/+/798807">https://review.opendev.org/c/openstack/manila-ui/+/798807</a></li></ul><blockquote>If you want to look into share_type_quotas : <a href="https://specs.openstack.org/openstack/manila-specs/specs/pike/support-quotas-per-share-type.html">https://specs.openstack.org/openstack/manila-specs/specs/pike/support-quotas-per-share-type.html</a></blockquote><ul><li>My previous patch in python-manilaclient is reviewed and I guess it’s ready to be merged :) Here is the link: <a href="https://review.opendev.org/c/openstack/python-manilaclient/+/789018">https://review.opendev.org/c/openstack/python-manilaclient/+/789018</a></li></ul><blockquote><em>My contribution in this bug is to adding a waiter in the resource type </em><em>share_group for deletion and creation of it. The goal of this fix is to- when a user hits this command </em><em>$ manila share-group-create — name share-group-1 — wait, manilaclient shell waits on the share group to become available before providing group details. Similarly when a user hits this command </em><em>$ manila share-group-delete share-group-1 — wait manilaclient shell waits on the share group to be deleted before returning to the prompt.</em></blockquote><ul><li>This week session was on OpenStack testing and Zuul CI session. I got to learn so many new things. Thanks to my mentors!</li></ul><p>That’s it! See you next week 🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=693ee6115eaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 5]]></title>
            <link>https://archanaserver.medium.com/outreachy-week-5-cc19a82c5152?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc19a82c5152</guid>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[internship-activities]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 20:27:58 GMT</pubDate>
            <atom:updated>2021-06-29T20:32:58.080Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is the fifth weekly blog of my internship.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Ecfh_mjbtWzrri6cdOUz0Q.png" /><figcaption>✨ week 5 ✨</figcaption></figure><p>Hi there, This week was more of learning plus exploring things and less of implementing them. Since I have started working on the main tasks of the internship. So the week end with getting a more clear picture of my main task of this internship. Implement<strong> share type quotas in the Manila UI</strong> (more on this later). Let’s check on this weeks action items, what’s my progress and more.🥤</p><h4>Week 5 action items:</h4><ol><li>Complete Django girl workshop.</li><li>Outreachy blog post about “Everyone struggle”.</li><li>Working on the previous patch set.</li><li>Get familiar with Manila UI and Horizon code.</li></ol><h4>Tasks I have completed and more</h4><ul><li>I have completed <a href="https://tutorial.djangogirls.org/en/">Django girl workshop</a> and build my first Django project. I have done this course to get familiar with Python and Django stuff. But after completing the workshop I’m familiar with lots of Python stuff and its environment. In the end, I came up with building a simple web application: my own blog and putting it online(with Pythonanywhere). Here is <a href="https://github.com/archanaserver/my-first-blog">my Django application repo</a> and the <a href="http://archanaserver.pythonanywhere.com/">live site</a>.</li><li>About blog post — I have published a blog post on <a href="https://archanaserver.medium.com/how-to-contribute-to-openstack-5d9894ad09a1">How to Contribute to OpenStack</a>, this blog is a beginner-friendly guide for those who want to start with OpenStack open-source contributions.</li><li>Also, I have worked on <a href="https://review.opendev.org/c/openstack/manila/+/795990">my previous patch</a> on <a href="https://launchpad.net/manila">openstack/manila</a> project one which I picked up on during Manila Bug Squash Event. I have submitted my new patch set with some new changes, but it failed to run some of the test cases. I guess it needs more exploration and work from my side. Well, I’m on it! 🙋🏻‍♀️</li><li>Attended<strong> Week 5 Mentor &amp; Intern Chat — </strong>it was a discussion about free software and technical conferences.</li><li>Umm what else, okay! I have <strong>read so many documentations</strong> about Manila and Manila UI project get familiar with every aspect of it. Also, I have gone through the whole codebase and the rest of the project resources.</li></ul><blockquote>The day isn’t over yet if I haven’t read any documentation. :D</blockquote><ul><li>Also, I had my 1:1 meeting with Victoria(my project mentor). We talked about the status, goals and if any updates we have for the projects or anything else. We discussed the Microversion updates and share type quotas stuff which I’ll be going to start working on during week 6. We ended up setting up the next week task and goals. <strong>Ya, I’m on it too! 🚀</strong></li><li>Apart from this, I got selected to be one of the Open Source Day mentors for the OpenStack project. This event is organized by <a href="https://www.linkedin.com/company/anitab-org/">AnitaB.org</a> in association with Virtual Grace Hopper Celebration 2021! Here is the little about this event:</li></ul><blockquote>Open Source Day (OSD) is an all-day hackathon (including workshops), in which participants of all skill levels learn about Open Source while contributing to projects designed to solve real-world problems. <a href="https://www.linkedin.com/feed/hashtag/?keywords=opensourceday&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6813710048095727616">#OpenSourceDay</a>. These workshops are intended to help first-time contributors who are eager but have limited experience with open source projects get started. We’ll walk you through the steps and share some of our best practices that will make it easier for you to start.</blockquote><blockquote>You ca visit the event page to learn more about it! Open Source Day Summer 2021 agenda: <a href="https://opensourceday.anitab.org/agenda">https://opensourceday.anitab.org/agenda</a></blockquote><blockquote>Register for the event: <a href="https://anitab-org.github.io/open-source-day/">https://anitab-org.github.io/open-source-day/</a></blockquote><p>See you next week 🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc19a82c5152" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Contribute to OpenStack]]></title>
            <link>https://archanaserver.medium.com/how-to-contribute-to-openstack-5d9894ad09a1?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d9894ad09a1</guid>
            <category><![CDATA[contribution]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Wed, 23 Jun 2021 17:42:30 GMT</pubDate>
            <atom:updated>2021-06-26T04:24:10.395Z</atom:updated>
            <content:encoded><![CDATA[<h4>A blog for developers who wants to get started with contributing to OpenStack projects.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b2dvXQsYjFDnnqG4A3r_KQ.png" /></figure><blockquote>This is the second blog in the series of <strong>Outreachy Internship blogs</strong>. I’m publishing a new blog every 2nd week for the next 3 months.<strong> The prompt of this week is to write about some open source jargons where I struggled</strong>. (I know I’m publishing it late!)</blockquote><p>I remember when I was submitting my first patch, hmm it was not easy though! If you are starting a new journey, you will find that there is a lot to learn. The same happened with me too, I got introduced to many new open-source jargons every single day during the outreachy contribution period. Yup! I’m still figuring out new terms daily.</p><blockquote>I’m writing this blog just to put everything in one place for those who want to start contributing to OpenStack. This is basically a <strong>“Getting started guide for OpenStack contribution”</strong>. You might find so many links in there, which is going to be helpful for sure :) So, let’s start with learning a little about OpenStack.</blockquote><h3>What is OpenStack?</h3><p>OpenStack is a cloud operating system that controls large pools of computing, storage, and networking resources throughout a data centre, all managed and provisioned through APIs with common authentication mechanisms.</p><p>It’s a software package that provides a cloud platform for public and private cloud. They mainly focus on Iaas(Infrastructure as a Service). As a Cloud Administrator, you can use a command-line or web-based dashboard provision, control, and automate OpenStack resources.</p><p><em>OpenStack is on a mission to produce a ubiquitous and most secure Open Source Cloud Computing platform. Also, which is easy to use, simple to implement, interoperable between deployments, works well at all scales and meets the needs of users and operators of both public and private clouds. Read more about </em><a href="https://docs.openstack.org/contributors/common/introduction.html"><strong><em>OpenStack</em></strong></a><em> and </em><a href="https://governance.openstack.org/tc/reference/technical-vision.html"><strong><em>its vision</em></strong></a><em>.</em></p><blockquote><strong>OpenStack is open source &amp; recognized for its security</strong></blockquote><h4>OpenStack Services:</h4><p>OpenStack built from a set of microservices that combined into different setups based on actual needs. These services provide <em>REST APIs </em>for their users, to make usage of the APIs easier it is possible to use SDKs.</p><p>The following diagram provides a high-level overview of some OpenStack core services and their relationship with each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnIh9ncG6LkYTbBXLfFgZA.png" /><figcaption>Source: <a href="https://www.openstack.org/">https://www.openstack.org/</a></figcaption></figure><p>The list of <em>OpenStack components, Client tools </em>and<em> Development tools</em> is so long. If you want to read more details about their services, check the links below:</p><ul><li><a href="https://www.openstack.org/software/project-navigator/openstack-components#openstack-services"><strong>OpenStack components</strong></a></li><li><a href="https://www.openstack.org/software/project-navigator/sdks"><strong>Client tools</strong></a></li><li><a href="https://www.openstack.org/software/project-navigator/deployment-tools"><strong>Development tools</strong></a></li></ul><h3>How can you contribute?</h3><p>You can contribute in any form, whether you are interested in developing some new features in Openstack, in documentation, review code or in fixing Bugs. You are welcome!</p><blockquote><strong>Your contribution must be something that accomplishes OpenStack mission.</strong></blockquote><h3>Why should anyone contribute to Openstack?</h3><ul><li>To learn more about the OpenStack projects</li><li>Expand and learn more your skills</li><li>Build connections with amazing developers</li><li>Propose or fix anything which annoys you while researching on OpenStack :/</li></ul><h4>There are a few steps that every new contributor should follow to getting ready to contribute:</h4><ol><li>Join mailing lists</li><li>Get an IRC client</li><li>Configure accounts on Launchpad, Gerrit, and sign the ICLA.</li></ol><h3>Join mailing lists</h3><p>You can subscribe to public mailing lists from <a href="https://wiki.openstack.org/wiki/Mailing_Lists">here</a> to stay updated with all the OpenStack announcements, future development and community events details.</p><p><a href="https://wiki.openstack.org/wiki/Mailing_Lists">Mailing Lists - OpenStack</a></p><h3>Get an IRC Client and Join</h3><p>IRC (Internet Relay Chat) is one of the main communication channels for open source projects. You can freely join a channel that suits your interests if you are looking for help or interested in contributing.</p><p>To use IRC you need an IRC client. There are many client applications available that provide IRC functionality like <a href="http://hexchat.github.io/">HexChat</a>, <a href="https://kiwiirc.com/">KiwiIRC</a>, <a href="https://www.irccloud.com/">IRCCloud</a> and more. You just need to do some research as per your browser and system. Also,</p><ul><li>If you are got introduced to IRC first time, please check this <a href="https://docs.openstack.org/contributors/common/irc.html">https://docs.openstack.org/contributors/common/irc.html</a></li><li>If you are looking to join OpenStack IRC channels and meetings, you can check this <a href="https://wiki.openstack.org/wiki/IRC">https://wiki.openstack.org/wiki/IRC</a></li><li>If you want to learn more about Internet Relay Chat (IRC) application then I find this as a great resource <a href="https://www.geeksforgeeks.org/internet-relay-chat-irc/">https://www.geeksforgeeks.org/internet-relay-chat-irc/</a></li></ul><p><a href="https://wiki.openstack.org/wiki/IRC">IRC - OpenStack</a></p><h3>Getting ready to contribute:</h3><p>So you have decided to contribute to OpenStack project. You can go through the below steps to configure accounts and the rest of the project setups. You need to create an Ubuntu One Account account that you will use to authenticate for Launchpad and Gerrit accounts.</p><h4><strong>Become a team member</strong></h4><p>Here to setup your Open InfraStructure Foundation account, follow this link for step by step details. <a href="https://docs.openstack.org/contributors/common/accounts.html">https://docs.openstack.org/contributors/common/accounts.html</a></p><h4><strong>Setup and Learn Git</strong></h4><p>You can go through this link to learn more about git installation in your system and commit message structure. <a href="https://docs.openstack.org/contributors/common/git.html">https://docs.openstack.org/contributors/common/git.html</a></p><h4>Configuring Task Tracker Account</h4><p>OpenStack currently uses two task tracker platforms Launchpad and StoryBoard for different projects. They soon are moving from the bug tracking software Launchpad to StoryBoard.</p><p>You can go through the below link to setup an account on any one of those as per your project choice.</p><p><a href="https://docs.openstack.org/contributors/common/accounts.html#setup-your-task-tracker-account">Setup Your Task Tracker Account</a></p><h4><strong>Configuring Gerrit Code Review Account:</strong></h4><p>Before moving to the Gerrit account setup, a little about Gerrit- <em>Gerrit is a web-based code review tool integrated with Git and built on top of Git version control system (helps developers work together and maintain the history of their work). It allows merging changes to the Git repository when you are done with the code reviews.</em></p><p><strong>One thing I want to mention here is that Gerrit uses concepts of changes rather than pull requests. To learn about Gerrit workflow, you can </strong><a href="https://docs.opendev.org/opendev/infra-manual/latest/developers.html#quick-reference"><strong>check this link</strong></a><strong>.</strong></p><p>OpenStack community uses Gerrit to review codes, documentation, infrastructure changes and CI configurations. To sign up for it:</p><ol><li>Go to OpenStack’s Gerrit page <a href="https://review.opendev.org/">https://review.opendev.org/</a></li><li>Click sign in, you will be asked for a username. You can enter the same username here too.</li></ol><blockquote>Note: From here on out when you sign into Gerrit, you’ll be prompted to enter your Launchpad login info. This is because Gerrit uses it as an OpenID single sign on.</blockquote><p>Now the next step here is to <em>Sign the Openstack individual&#39;s contributor License Agreement</em>.</p><ol><li>Go to <a href="https://review.opendev.org/#/settings/agreements">Gerrit’s setting</a>.</li><li>Click the <strong>New Contributor Agreement</strong> link and sign the agreement.</li></ol><blockquote>You need to sign this to contribute code &amp; documentation. You will not be able to push patches to Gerrit without this.</blockquote><p>The last step here is, <em>setting the SSH Key</em>. To add the SSH Keys into your Gerrit account, you need to generate it first. <a href="https://docs.openstack.org/contributors/common/setup-gerrit.html"><strong>Follow this link</strong></a><strong> t</strong>o generate the ssh key. Now to import it into your Gerrit account:</p><ol><li>Go to <a href="https://review.opendev.org/#/settings/ssh-keys">Gerrit’s SSH Public Keys settings</a>.</li><li>Click the ‘Add Key’ button.</li><li>Paste the public key into the <strong>Add SSH Public Key</strong> text box and click <strong>Add</strong>.</li></ol><h4>Git review Installation</h4><p>You need to install git-review . Open your terminal and type: pip install git-review for macOS. Follow this for to check the command for different systems- <a href="https://docs.openstack.org/contributors/common/setup-gerrit.html#git-review">https://docs.openstack.org/contributors/common/setup-gerrit.html#git-review</a></p><p><strong>P.S. I would suggest using the same email and username for all account setup, that would be easy for you.</strong></p><p>That’s a lot of information. You can now prepare yourself for the next steps.🥤 So, let’s move :)</p><h3>To propose changes in the Git repository</h3><ol><li>Start by cloning the repo or setting up the development environment with DevStack</li><li>Remote update</li><li>Create branch</li><li>Running unit tests</li><li>Curate a commit on that branch</li><li>Do a git review</li></ol><h4>Start by cloning the repo or setting up DevStack</h4><p>You can start contributing to the OpenStack project just by cloning the repository into your system or you can use DevStack to bring up a complete OpenStack environment for development. However, it is advisable to only run DevStack on servers or virtual machines that are dedicated to this purpose. You can run DevStack on the virtual machine using VirtualBox with Ubuntu.</p><p>There are some projects(<a href="https://launchpad.net/python-manilaclient">python-manilaclient</a>, <a href="https://launchpad.net/manila">manila</a> and more) that don’t require setting up the whole environment, you can just clone the repo, add your changes, run tests on it and submit it for review. 🚀</p><p><strong>Cloning the repo:</strong></p><ol><li>To clone a project to your local machine, open the terminal and type git clone &lt;openstack-project-url&gt;.</li><li>Go to your installed project directory by cd &lt;openstack-project-url&gt;.</li><li>You need to do git review -d. This command sets up the necessary remote hosts and commits hooks to enable pushing changes to Gerrit. This basically checks if you can log in to Gerrit with your SSH keys.</li><li>Git review assumes the user you’re running it as is the same as your Gerrit username. If your git username is different from your Gerrit (review.openstack.org) username, you can tell it by setting this git config setting: git config --global gitreview.username &lt;username&gt; . Verify your username once again, using git config -list.</li><li>If you are hitting some error like “We don’t know where your gerrit is, please manually create a remote names ‘gerrit’ and try again. There you need to do git remote add gerrit &lt;your-repo-url&gt;. Here &lt;your-repo-url&gt; is the last link you got in the error message. (ssh://&lt;username&gt; . . .git)</li><li>Now do git review -d again. This should work now. Yay!</li></ol><p><strong>Setting up DevStack</strong></p><p>This is a whole different and a big topic. You can go through these links, to run devstack. You might hit some issues during this setup, in that case, make use of IRC channel.</p><ul><li><a href="https://docs.openstack.org/devstack/latest/">https://docs.openstack.org/devstack/latest/</a></li><li><a href="https://maari.ee/how-to-set-up-development-environment-for-openstack-with-devstack/">https://maari.ee/how-to-set-up-development-environment-for-openstack-with-devstack/</a></li><li><a href="https://osintern.net/how-to-setup-devstack/">https://osintern.net/how-to-setup-devstack/</a></li></ul><p>Once you are done with the above steps, which is to set up the project into your local machine. You can move on to the next step!</p><h4>Remote Update</h4><p>Once you cloned the repo, before creating any branches and making your changes, make sure to get the latest upstream changes with the following commands:</p><pre>git remote update<br>git checkout master<br>git pull --ff-only origin master</pre><h4>Create Branch</h4><p>To create your development branch into the repo. It’s good practice to create a new branch with a bug number for each patch than to work from master.</p><p>Let’s suppose you are working on bug number #1898318, you can create a new branch with the name “bug/1898318”. You need to run this command: git checkout -b bug/1898318</p><p>To check your branch, run this command: git branch</p><h4>Running unit tests</h4><p>This is the most important step. You need to run unit tests, to check if everything is working properly before submitting it for review.</p><p>To run the unit test you are going to run tox. So you need to install the tox package here: sudo pip install tox . You can<strong> </strong><a href="https://docs.openstack.org/manila/latest/contributor/development.environment.html#running-unit-tests"><strong>follow this</strong></a> to learn more about unit tests. Also, you can do sudo tox to run all the tests serially.</p><h4>Curate a commit</h4><p>You might be done with your fixes so you need to commit it. To commit your changes all you need to run is: git commit -a --amend</p><p>This will open up a nano editor, write your commit message and for the best practice add only 80 char per line. <a href="https://docs.openstack.org/contributors/common/git.html#commit-messages"><strong>Follow this guide</strong></a> for the commit message structure.</p><h4>Git Review</h4><p>Time to submit your changes for review: git review to push your changes for review.</p><p><em>git review is a command-line tool. This is a little bit different from what we use on GitHub with that PR. It is a specific tool that allows us to send some patches into OpenStack review system. Also, </em><em>git-review is a tool that helps to submit git branches to Gerrit for review.</em></p><p><strong><em>Note:</em></strong><em> When you are submitting the first patch into the project make sure to do </em><em>git review -d to initialize this into your project.</em></p><blockquote>Once you are done with it, all you need to do is be patient, don’t expect your first patch approval will be fast and do consider time zone difference.</blockquote><p>I have already added the important links for you, but here are some-</p><p>Main openstack contributor guide: <a href="https://docs.openstack.org/contributors/code-and-documentation/index.html">https://docs.openstack.org/contributors/code-and-documentation/index.html</a></p><p>Development workflow: <a href="https://docs.openstack.org/charm-guide/latest/making-a-change.html">https://docs.openstack.org/charm-guide/latest/making-a-change.html</a></p><p>That’s it. I hope that you find this helpful. See you next week :)</p><p>You can connect with me on <a href="https://twitter.com/archanaserver">Twitter</a>, <a href="https://www.instagram.com/archanaserver/">Instagram</a>, <a href="https://www.linkedin.com/in/archanaserver/">LinkedIn</a> and <a href="https://github.com/archanaserver">GitHub</a> 🌻✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d9894ad09a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy | Week 3 & 4]]></title>
            <link>https://archanaserver.medium.com/week-03-04-outreachy-internship-with-openstack-7491adf166c5?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/7491adf166c5</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Sun, 20 Jun 2021 16:57:30 GMT</pubDate>
            <atom:updated>2021-06-29T20:35:24.517Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>This is the third and the fourth weekly blog of my internship.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*gX0TL2RrF-OMJ3hmP0vmNQ.png" /></figure><p>Hi everyone, It’s been 4 weeks already! I was procrastinating since last week to write this blog. Finally, here I’m. 🙋🏻‍♀️ This blog post is going to be one of the special blog posts of my internship till date. Continue reading to know <em>why</em> part 😉 I have a lot to share and a lot to say, so many things happened in the last 2 weeks.</p><h3>What are the wins for the weeks?</h3><p>I spent time doing many amazing things, but there were few challenges I faced in the last weeks such as fixing bugs, setting up the development environment, or if it was about going through the whole codebase. When the whole codebase of OpenStack Manila is in Python(Django) and you have never worked on that before.</p><blockquote>I believe my biggest win for the week was not giving up! and continuing working :) I just love learning.</blockquote><h4>Let me share some of the wins for the weeks:</h4><ul><li>Participated in the Manila Bug Squash Event! Picked one Manila <a href="https://bugs.launchpad.net/manila/+bug/1646433">bug</a> to work on recommended by Victoria and I started my contribution to fixing this bug. <a href="https://review.opendev.org/c/openstack/manila/+/795990">Submitted the patch</a>, waiting for reviews from mentors. Also, this bug milestone change from none =&gt; <a href="https://launchpad.net/manila/+milestone/xena-2">Xena-2 </a>release.</li><li>Finished fixing some test cases in the openstack/python-manilaclient <a href="https://review.opendev.org/c/openstack/python-manilaclient/+/789018">patch</a> (though it needs some last reviews) which I was facing from the last 2 weeks. It was quite challenging, but I did it!</li><li>Got an opportunity to work with <a href="https://www.linkedin.com/in/helenaspease/">Helena Spease</a>(Marketing and Community @Open Infrastructure Foundation) on an article, which is all about <a href="https://superuser.openstack.org/articles/students-of-openinfra-archana-kumari-accurate-institute-of-management-and-technology/">How I got started working with the OpenStack Manila project as part of my Outreachy Internship Program</a>.</li><li>Something HUGE happened this time! I got the opportunity to talk about my contribution experience with OpenStack in <a href="http://openinfra.live/">OpenInfra Live</a>. I was excited and nervous at the same time as this was my first time being somewhere as a guest. That was really a wonderful session with a nice audience. You can find more details here:</li></ul><ol><li><a href="https://superuser.openstack.org/articles/how-to-start-contributing-upstream-to-openinfra-openinfra-live-recap/">How to Start Contributing Upstream to OpenInfra | OpenInfra Live Recap</a></li><li><a href="https://www.youtube.com/watch?v=4kGtM4J_hjM&amp;feature=youtu.be">How to Start Contributing Upstream to OpenInfra | YouTube Videos</a></li></ol><ul><li>Started my Python and Django journey 🏞</li><li>I have decided to write some more detailed blogs throughout my contribution period. I am learning so much new open-source jargon here and I can’t stop myself from writing articles on all those.</li><li>I started loving OPENSTACK ❤️</li></ul><h3>What’s not working?</h3><p>As I’m going to work on the Python codebases for the next couple of months. I need to focus more on the Python side. I have always worked on JavaScript and now switching to Python for the OpenStack Manila project is a bit challenging. But let’s do this!!</p><h3>What am I avoiding?</h3><ul><li>Blogging part is what I’m avoiding for the whole week. I don’t know why, I am not getting my flow, though I love writing. I thought of writing a few more blogs but ended up doing only a few.</li><li>I am trying to be more active!</li></ul><p>I have started working on my main task of the internship, which is all about implementing share type quotas in the Manila UI(I&#39;ll share more on this later).</p><p>That’s all for now!</p><p>See you next week 🌻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7491adf166c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 02 | Outreachy internship with OpenStack]]></title>
            <link>https://archanaserver.medium.com/week-02-outreachy-internship-with-openstack-e9ae3a743154?source=rss-177b5962489------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9ae3a743154</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Archana Kumari]]></dc:creator>
            <pubDate>Sun, 20 Jun 2021 16:53:01 GMT</pubDate>
            <atom:updated>2021-06-20T19:46:59.042Z</atom:updated>
            <content:encoded><![CDATA[<h3>Outreachy | Week 2</h3><h4><strong>This is the second weekly blog of my Outreachy internship with OpenStack.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_0sBwmUquvvDZiKUVZeTpA.png" /></figure><h4>Below are the top tasks of week 2:</h4><ul><li>Development environment Devstack setup</li><li>Work on fixing the patch I created during the contribution period.</li><li>Update introduction blog post</li><li>Attend a few meetings :)</li></ul><h3>Putting together my every day’s progress in brief:</h3><h4>Day 8</h4><ul><li>It was a Happy Monday! The first thing I did was to sync up with my mentor Victoria so that we can work on fixing that devstack environment issue.</li><li>We won’t be able to fix it by today. There were some issues with <a href="https://review.opendev.org/c/openstack/devstack/+/791282">OVN</a> that took so much time and we decided to continue fixing the devstack environment tomorrow.</li><li>I had a meeting today with Victoria and Kafilat(another Outreachy intern here) about the <strong>OpenStack big picture</strong>. I got to learn so much about OpenStack. It was an amazing day :D</li></ul><h4>Day 9</h4><ul><li>Ah! Finally, it was a productive day. We are done with setting up the devstack environment. <strong>KUDOS TO US!! 🥳</strong></li><li>We spent the whole day debugging all those previous issues with ovn and finally at the end of the day we sorted everything. We can now move on to the code part from tomorrow.</li><li>I can’t thank my mentors Victoria and Goutham enough. It was a frustrating process in the end but they helped me to fix all those issues. And yes we get it :)</li><li>Also, I read some reviewing changes to OpenStack documentation.</li><li>Some words from my mentor Victoria about code review:</li></ul><p>&gt; it’s a good way to start a contribution</p><p>&gt; it’s a great way to build knowledge</p><p>&gt; you can able to read other people code and review</p><p>&gt; this help you practise the best solution for the design and coding part</p><h4>Day 10</h4><ul><li>Hie again :) Thanks a lot for being here. So the day starts with facing another issue. The issue was yesterday’s devstack setup, due to so much resource installation in my virtual machine. My system started working slow.</li><li>My mentors helped me thereby setting up a virtual environment in <a href="https://vexxhost.com/">VEXXHOST</a> and connected with that environment through SSH. Here it’s sorted finally. Phew!</li><li>It’s time for <em>some task assignments</em> now. I got two tasks to work on today-</li><li><em>getting familiar with the OpenStack dashboard current UI status</em></li><li><em>work on that fix that I had submitted/contributed during the contribution period.</em></li><li>I picked off task one, started reading documentation about the OpenStack dashboard and played around there with some instances, network, volume and images stuff. Did some analysis, how all the components are connected there. Also, I spotted a bug. 😉</li><li>Time to start working on the next and the last task for today. So, during the contribution period, I contributed to this bug. This was under the project python-manilaclient. This fix was all about to work on the</li><li>When this task was assigned to me, I was a bit scared if I’ll be able to complete it or not. But damn! I’m so proud of myself, I did this 💃🏻</li><li><strong>Ah! Such relief 💜 I’m done with both the task :)</strong></li></ul><h4>Day 11</h4><ul><li>Okay so, I worked on my patch today also. I have gone through reviewer comments and tried to fix my issue.</li><li>Had my first one on one meeting with my mentor Victoria, she explained to me about running tests on the python manilaclient project and some discussion on commit messages. Also, we track our weekly status, goals and updates.</li><li>Attended the Manila Weekly meeting, got to know about the Manila Bug Squash Event(I’m so excited about this) and got assigned to some volunteer work there. Thanks to Victoria :)</li><li>The day ended by working on the patch fixes, submitting it again for review.</li></ul><blockquote>Today’s Affirm: I’m capable of everything I set my mind to 🌺</blockquote><h4>Day 12</h4><ul><li>I feel so tired today and lazy too. So in short, today I worked on fixing that patch. I’m facing some errors. Hopefully, I’ll work on this in the morning with a fresh mind.</li><li>Also published my Outreachy first blog prompt response. You can read about it here: Outreachy: Introduce Yourself.</li><li>Here is the end of week 2, it was a very productive week for me (though I still need to work on my patch fix)</li></ul><p>That’s all for now! Time to sleep zZ</p><p>See you next week :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9ae3a743154" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>