How to submit code to OpenStack

Reprint: http://blog.csdn.net/ffb/article/details/9625011

The best way to contribute to OpenStack is to help the Community complete blueprint or bugfix. The code submission needs to follow some of the community's basic requirements, and the following is a summary of last year's participation in the OpenStack community.

Original address: http://blog.csdn.net/ffb/article/details/9625011

ProcessRegister an OpenID application for a personal CLA certificate
Apply for the company's CLA certificate (individuals do not need to do this) to update the contributors list, the company column is written on the name of the company joined the OpenStack Contributors Group (must) and the OpenStack group Https://launchpad.net/~openstac K-cla/+join (must) set SSH Keys (copy Local ~/.ssh/id_rsa.pub content) to claim a blueprint/bug (this step can skip) git clone code to local, configure User.Name and US The registration of Er.email and OpenID is modified within the term, and all tests are passed (no test will be refused). One of the basic requirements of the code is to conform to the PEP8 specification. |__ If the deadline is exceeded, click on the "Restored" button on the interface to submit the audit wait review results according to the review requirements to modify the code, with Git commit .....-amend commit to modify Git again review until successful
Test Requirements
[Plain]The name of the view plain copy import library needs to be sorted alphabetically Pep8 detection: sudo apt-get install PEP8 ~/nova$ pep8.      Nosetest:sudo pip install nose ~/nova$ nosetests. Novatest: ~/nova$ sudo./run_tests.sh [api/xxx/xxxx.py] For example:./run_tests.sh Test_db_api TEMPEST-DEVSTACK:CD Devs Tack Source Exerciserc;./exercise.sh

Comment Requirements
The format is divided into three parts, the first line is a description of the local modification, followed by an empty line after the detailed description of the modification, followed by an empty line to modify the corresponding BugID or bpid, and then write Changeid. The system will judge according to the Change-id in the note that this commit belongs to the BP, Fixbug and implement blueprint to write in front of the Changeid line.

[Plain]View plain copy Implement bp:efficient-limiting. 1.add limit param to Db.instance_get_all_by_filters () 2.execute limit before Sqlarchmy Get_all () fixes:bug #100337 3 Implements:blueprint xxxxxxxxxxx Change-id:iea3eeb7b51194b6017d624506aafc6469d7338e4

Reference Document: Summary_of_git_commit_message_structure | Information_in_commit_messages

Update Requirements
Before executing git review, you should make sure that review is up to date and update the current code to the latest version using the following command:

[plain] view plain copy Git fetch origin master git rebase fetch_head git Add. git commit--amend git review

If a conflict occurs when rebase, you should manually resolve the conflict after you execute git rebase--continue

F.A.Q.

[Q] The code test failed after committing review due to the server's cause.
[A]
Execute review on this patch, if it is smokestack, enter reverify, and if it is Jenkins, enter recheck to test it again

[Q] How to continue to modify at home
[A]
after the company submitted patches to review, continue to make changes at home, you can
1. Local execution
     git-review-d Review_number
    such as, git-review-d 12859
    This step will verify the Ssh-key

or
2. Merge the changes on the jekins to local.
    There's a button near the review button.