DEV Community: ccokeke0023

Enhancing Manila UI: Adding Metadata Support to Share Snapshot Creation and Editing

ccokeke0023 — Mon, 22 Jul 2024 20:24:13 +0000

To enhance the Manila UI by adding metadata support to the "Create Share Snapshot" dialog and allow for metadata editing, you need to understand and utilize the API microversions correctly. According to the REST API Version History, metadata for share snapshots was introduced in microversion 2.73. This blog post explain few steps to update the Manila UI and ensure you are using the correct microversion.

Step 1: Ensure API Microversion Compatibility
Before you start adding metadata fields to your forms, you need to make sure your code is set to use the correct API microversion (2.73 or later).

In the Horizon settings or where you configure the Manila client, ensure that you are using microversion 2.73 or higher. Typically, this is done in a configuration file or directly in the API client initialization.

Step 2: Adding the Metadata Textbox to the Create Snapshot Dialog
I Updated the form used for creating share snapshots to include a metadata textbox. This form is defined in manila_ui/dashboards/project/share_snapshots/forms.py.

Step 3: Connecting the API for Snapshot Creation
To connect the API for creating snapshots with the new metadata field, ensure the handle method in the form processes the metadata correctly.

Step 4: Implementing Metadata Editing for Share Snapshots
To allow editing metadata for existing share snapshots, update the form and view for editing share snapshots.

Key Git Commands: Descriptions and Uses
During the course of working on the task of enhancing the Manila UI, I had the opportunity to learn and use several Git commands. Below is a brief description of each command and its purpose:

git rebase git rebase is used to reapply commits on top of another base tip.I learnt this when I mistakenly used git commit --amend instead of using git commit then the commit message. It is often used to keep a feature branch up to date with the latest changes in the main branch.

Uses:

Integrate changes from the main branch into a feature branch.
Clean up commit history by creating a linear sequence of commits.
git rebase --continue
After resolving conflicts during a rebase, git rebase --continue is used to resume the rebase process. It indicates that the conflicts have been resolved, and Git can continue applying the remaining commits.

Use:Continue the rebase process after resolving conflicts.

git rm -rm The command should be git rm (without the -rm). It is used to remove files from the working directory and the index (staging area). The -r option allows recursive removal, i.e., it can remove directories and their contents.

Use:Remove files or directories from the repository.

git diff git diff shows the differences between changes in the working directory and the index (staging area), or between different commits. It is useful for reviewing changes before committing them.

Uses:

View changes made to files.
Compare different versions of files.

Conclusion**

By following these steps, you can enhance the Manila UI to include metadata support for creating and editing share snapshots. Ensure that your code uses API microversion 2.73 or later to take advantage of the metadata functionality introduced in this version. This allows users to provide and manage additional information in the form of metadata, improving the organization and management of share snapshots.

Add Filter choices to resources

ccokeke0023 — Mon, 01 Jul 2024 19:17:38 +0000

I worked on the project Add Filter Choices to Resources as my first task, focusing on implementing filterable actions for both users and administrators. This enhancement ensures a user-friendly interface for managing Share Networks by utilizing filters and workflows.

The ShareNetworksView class is central to this functionality, displaying a list of share networks using a table. It retrieves detailed data from the Manila API and applies user-defined filters to refine the results. The get_filters method enables filtering based on criteria such as name or description, making it easier to manage large sets of data.

For updating share networks, the Update class provides a guided workflow that sets the necessary initial data and context for the process. Similarly, the Create class streamlines the creation of new share networks, defining the required forms and URLs.

The Detail class offers an in-depth view of a specific share network, showcasing its properties and related information. It gathers additional details from the Neutron API, offering a comprehensive overview of the network’s subnets and availability zones. The get_data method further enriches the share network data with security services and share server information.

Overall, this project enhances the functionality of the Horizon dashboard, making it more intuitive and efficient for managing Share Networks.

The image attached here is the sample of the test.

Embracing Struggles: My Journey Through the Outreachy Internship

ccokeke0023 — Mon, 17 Jun 2024 07:34:41 +0000

Everybody struggles in life every now and then. Struggling is a part of life. It doesn’t matter what other people think or say; it all depends on our perspectives. Our personal struggles are shaped by our unique experiences and challenges. Often, we might feel lazy or unmotivated, but struggles indicate that we need to push beyond our current limits. However, it's crucial to channel our efforts correctly because doing more of the wrong activities can lead to even greater challenges. Always remember, the struggle you face today is paving the way for a brighter tomorrow.

To God be the glory, this is the third week of my internship period. When I first contributed to my project, I was incredibly nervous. I didn't have the confidence to believe I could succeed, and being a beginner only heightened my anxiety. Initially, I struggled to understand the concept of Share and Resources in Manila. Despite my nerves, one of my core values, dedication, kept me going. I refused to give up and dedicated myself to studying the project documentation and learning how everything worked. My perseverance paid off, and I found my contribution period to be fruitful. By the end of this period, I gained a lot of confidence and learned valuable skills, such as effective Googling and seeking help from my mentors and the community.

During the internship, I had my first video call meeting with my mentors,Ashley, Carlos, and Goutham. It was a wonderful experience to connect with them beyond email or chat. With their proper guidance, I successfully completed my tasks. They provided a thorough demo of the entire project and explained the concepts of Share and Resources in Manila in detail. Thanks to their support, I was able to quickly get started on my first task.

Looking back, I see how my initial struggles were essential for my growth. They taught me resilience, the importance of dedication, and the value of seeking help when needed. Struggles are a universal experience; everyone faces them at different points in their lives. What matters is how we respond to them. By embracing the challenges and persevering, we can achieve great things.

An OpenSource term I just learnt about

ccokeke0023 — Tue, 11 Jun 2024 14:54:24 +0000

Vocabulary Term: Linting

Introduction

Before embarking on my journey with Outreachy, I came across a multitude of terms and concepts related to open source software development. One of the intriguing terms that stood out to me was "linting." Although it might not be entirely rare in the broader programming community, it was new to me and has proven to be essential in the world of open source development.

What is Linting?

Linting refers to the process of running a program that analyzes code for potential errors, bugs, stylistic errors, and other problematic patterns. This automated tool, known as a linter, reviews the source code to ensure that it adheres to certain coding standards and best practices. The primary goal of linting is to improve code quality and maintainability.

Origin of the Term

The term "linting" originates from a Unix utility called lint, which was created in 1978 to detect suspicious constructs in C language source code. The name "lint" was inspired by the small, often overlooked bits of fluff or fiber found in clothing, which can be seen as an analogy for the small, often overlooked errors in code.

Importance of Linting in Open Source

Consistency: In open source projects, where multiple contributors work on the same codebase, consistency is crucial. Linting ensures that all contributors follow the same coding standards, making the code more readable and uniform.
Early Error Detection: Linters can catch errors and potential bugs early in the development process, reducing the time spent on debugging later.
Code Quality: By enforcing best practices and coding standards, linting improves the overall quality of the code, making it more robust and easier to maintain.
Learning Tool: For new contributors, especially those unfamiliar with the project's coding standards, linters serve as an educational tool, guiding them to write better code.

Common Linting Tools

Different programming languages have their own linting tools. Some popular ones include:

ESLint: A widely used linter for JavaScript.
Pylint: A linter for Python code that checks for errors and enforces a coding standard.
Rubocop: A Ruby linter that enforces the Ruby style guide.
ShellCheck: A linter for shell scripts that detects syntax and semantic errors.

Applying Linting in My Internship

During my Outreachy internship, I encountered linting as an integral part of the development workflow. Initially, it felt like an additional step, but I soon realized its value in maintaining high code standards. Using linters helped me write cleaner code and avoid common pitfalls, making my contributions more reliable and aligned with the project's guidelines.

Conclusion

Linting may not be the most glamorous term in the open source vocabulary, but it plays a pivotal role in ensuring code quality and consistency. Learning about linting and incorporating it into my development process has been a valuable experience during my Outreachy internship. It has taught me the importance of adhering to coding standards and the benefits of automated tools in maintaining a healthy codebase.

Outreachy Blog 1 - Introducing myself

ccokeke0023 — Tue, 04 Jun 2024 10:21:17 +0000

Hello Everyone!

Thanks in advance for your interest to read about me. Today, I would be telling you a little bit about myself and how I got selected for the Outreachy'24 Internship cohort.

My name is Christian Chima Okeke, an Outreachy Intern with OpenStack Manila. I am a degree holder with B.Eng Electronic Engineering and strongly making a career switch to become a Software Engineer.I am also a trained Network Engineer.My interest are on Product Design, Frontend and Backend Development, as well as making contributions to OpenSource Projects.

I got to know about Outreachy sometime last year and joined the OpenStack Manila Project. Though, I was not selected in my first and second attempt but I never stopped contributing to Manila. So, in this cohort, I am accepted to intern with OpenStack on the Project "Implement new features in the OpenStack Manila Dashboard". My mentor(s) are Goutham Pacha Ravi and Carlos da Silva and Ashley Rodriguez.

What is Outreachy

Outreachy provides paid 3-month internships for OpenSource and OpenScience for the under-represented in the community. Within these 3-month internship period, interns are paid a stipend of $7,000 and work on select projects according to their skillsets. Outreachy internships run twice in the year between May to August or December to March.

How did I apply to Outreachy

Last year, I applied to Outreachy but unfortunately I was not accepted. I did not relent though but kept connected to the Community which I have come to Love. I decided that the idea is to get involved and committed for a long-term to OpenSource so I used the period to hone my skills further. I also, was following the progress of interns on the twitter and community channels and by the next application, I was more prepared to apply again. Coincidentally, OpenStack Manila was selected to participate again in this cohort and I immediately jumped right in because this is the community I have come to identify with. Finally, on 3rd May, 2024, I received the good news that I have been selected to participate in this cohort. I could not contain my join and I immediately reached out to my Mentors, Goutham and Carlos da Silva who have been providing me all guides throughout the contribution phase. Indeed, I am very grateful to them both.

A short brief about OpenStack Manila

The OpenStack Shared File Systems service (manila) provides coordinated access to shared or distributed file systems. The method in which the share is provisioned and consumed is determined by the Shared File Systems driver, or drivers in the case of a multi-backend configuration. There are a variety of drivers that support NFS, CIFS, HDFS, GlusterFS, CEPHFS, MAPRFS and other protocols as well.

The Shared File Systems API and scheduler services typically run on the controller nodes. Depending upon the drivers used, the share service can run on controllers, compute nodes, or storage nodes.

My core values

Dedication - I was able to succeed as a result of my doggedness and dedication to whatever goal I set to achieve.

Curiosity - I value curiosity, the desire to learn or know about what interests me drives me to achieve my goal.

Growth - I think investing a considerable amount of time and energy in one's personal development is needed for one's growth.

Compassion - I value compassion, it drives our commitment to serve others with empathy and respect.

Thanks for reading