• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
OpenStack Contribution Process
 

OpenStack Contribution Process

on

  • 663 views

 

Statistics

Views

Total Views
663
Views on SlideShare
663
Embed Views
0

Actions

Likes
0
Downloads
11
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    OpenStack Contribution Process OpenStack Contribution Process Presentation Transcript

    • Lets Fix a Bug ...
    • Suppose You saw a bug like this one in the Code or DocsLine 55 and 57 are duplicate lines. Now you wish to fix it byremoving the duplicate line so what you need to do ?
    • STEP 1(A). Sign the CLA, Every developer needs to sign the Individual Contributor Licenseagreement.(B) Create a Launchpad Account( https://launchpad.net/) if you dont have one. Its amust.(C). Add yourself to the contributors wiki, On the Contributors page, include yourLaunchpad ID, your CLA Echosign Transaction Number and your CorporateAffiliation(if there is any). The information provided will be used by authorizedmembers to approve your request (see next step). Use your Launchpad ID as yourusername for the wiki.(D). Request membership in the openstack-cla group on Launchpad. Visithttps://launchpad.net/~openstack-cla/+join to join this group. Membership in thisgroup is required in order to submit code changes.
    • STEP 2: Setting Up the Environment We found the bug in the Tempest, So we need to get the source code of tempest project from the github repo but before we fix the bug we need to set up the environment.● Install git on your local machine. Ex: On ubuntu just type sudo apt-get install git-core● Configure Your user name and password: git config --global user.name "Firstname Lastname" git config --global user.email "your_email@youremail.com"● Install git-review tool On ubuntu: sudo apt-get install git-review On other unix like systems: pip install git-review
    • STEP 3: Getting the Code● To get a copy of any of the OpenStack projects, you can look at the Github OpenStack organization and browse, or you can directly clone the repository. Like here to fix our bug we need a clone of Tempest so we will clone the Tempest repository on our local machine like this: git clone git://github.com/openstack/tempest.git
    • STEP 4: Fix the Bug● Enter in to tempest directory and let git-review tool to configure your project. Make sure your gerrit/launchpad user name is the same as the current running user. $ cd tempest $ git review -s● Get the latest upstream changes: $ git remote update $ git checkout master $ git pull origin master● Create a TOPIC branch i.e. Create a branch with a name which tells something about your changes. Like here we will use duplicate_line_in_base.py $ git checkout -b duplicate_line_in_base.py● Open the base.py file in your favourite text editor, Remove the duplicate line and save it.● Now commit your change with a commit message. You can read more about commit messages on http://wiki.openstack.org/GitCommitMessages. $git commit -am “Removed the duplicate line from base.py. It will fix this bug #1234”● Finally send the code for review. $ git review
    • What happens after you submit a changeAny Openstack developer may propose or comment on a change (includingvoting +1/0/-1 on it). Openstack projects have a policy requiring two positivereviews from core reviewers.When a review has two +2 reviews and one of the core team believes it isready to be merged, he or she should leave a +1 vote in the "Approved"category. You may do so by clicking the "Review" button again, with orwithout changing your code review vote and optionally leaving a comment.When a +1 Approved review is received, Jenkins will run tests on thechange, and if they pass, it will be merged.
    • Few links to understand the process more thoroughlyGerrit Workflowhttp://wiki.openstack.org/GerritWorkflowGerrit, Jenkins, and GitHubhttp://wiki.openstack.org/GerritJenkinsGithubHow To Contributehttp://wiki.openstack.org/HowToContribute