Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to obtain and download the source code for OpenStack development. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

OpenStack is an infrastructure as a service (IaaS) cloud computing project.

Resources are managed through a dashboard that provides control to administrators and gives users the right to configure resources through a Web interface. This article describes how to set up your account, set up your development environment, and start contributing to OpenStack.

Step 1: set up the account through online registration and key configuration

Set up your Launchpad account. Launchpad is the location that OpenStack uses to host all its projects. Please visit the Launchpad login page, register with your email address, and choose a memorable Launchpad ID for yourself. Then access https://launchpad.net/~LaunchpadID, set your OpenPGP key, and use the instructions on this page to upload your SSH public key. For example, my Launchpad id is houshengbo, so I will access https://launchpad.net/~houshengbo, as shown in figure 1.

Figure 1. Set OpenPGP key

Set up your SSH account for Gerrit. OpenStack applies a code review process to ensure code quality. Please visit the OpenStack code review page and log in using your Launchpad account. Then access https://review.openstack.org/#/settings/ssh-keys and upload your SSH public key.

Figure 2. Upload SSH public key

Step 2: sign the CLA agreement

Please join OpenStack Foundation if you have not already joined. Use the email address that you plan to use to contribute the code. The primary email address in foundation profile needs to match the preferred email that you set later in the Gerrit contact information.

Please visit the Code Review page. Click the Sign In link located in the upper-right corner of the page. Log in to Launchpad using your Launchpad ID.

Unless you are a U.S. Government employee (see below), please agree to Individual Contributor License Agreement and provide contact information. All your names and email addresses are public. If necessary, you can update this contact information later, but make sure that the primary email address always matches the email address set for your OpenStack Foundation membership.

Join the OpenStack Contributors group. Code changes need to be submitted as a member.

If you are working as an individual contributor, then performing the above steps is sufficient. If you work on behalf of the company or the U.S. Government, you may need to focus on other internal approval processes that vary from company to company. For more information, see Contributor license Agreement.

Step 3: set up the local development environment

Set up the Eclipse environment:

On the Eclipse window, click Help > Install New Software.

In the Work with field, enter http://download.eclipse.org/egit/updates and click Add.

Select the Eclipse EGit under Eclipse Git Team Provider.

Click Next until you find the Review Licences window. Accept the license terms and click Finish.

On the Eclipse window, click Help > Install New Software.

Configure python interpreter for Eclipse. In the Work with field, enter http://pydev.org/updates and click Add.

Check PyDev.

Click Next until you find the Review Licences window. Accept the license terms and click Finish.

Install Ubuntu 11.10 or 11.10 + with python.

Install git:sudo apt-get install git.

Install Eclipse.

Install the PyDev plug-in for Eclipse.

Install the EGit plug-in for Eclipse.

Set up the code base.

Open a terminal, change to the target directory (for example, / opt/stack) and run the following command to get the keystone code:

Git clone https://github.com/openstack/keystone.git

Import the project into Eclipse: run Eclipse and set the workspace to the directory where all projects (/ opt/stack) are saved.

Create the PyDev project: click File > New > PyDev project. Make its name the same as the project, such as keystone, and then click Finish.

Synchronize the project with Egit: in Eclipse, right-click the project (keystone), click Team > Share project, and then click Next and Finish.

After completing the above steps, you should see [keystone master] after your project name in Eclipse.

Open a terminal, change to the target directory, and run the following command to get the devstack code:

Git clone git://github.com/openstack-dev/devstack.git

Create a file called localrc in the devstack directory you just created. You can find information on how to configure localrc on the DevStack website.

Run. / stack.sh. The default working directory is / opt/stack, which can be changed manually. When you successfully run devstack for the first time, you can find all the code under / opt/stack.

Use devstack:

Another way is to download specific projects instead of cloning all of them. Take the Keystone project as an example:

Run the unit test

Run all unit tests on a project:

Open a terminal and go to the project directory, such as keystone.

Run the. / run_tests.sh command. When asked if you want to create a virtual environment, select Y or N.

Test an example:

Open a terminal and go to the project directory, such as keystone.

Run the. / run_tests.sh command, for example. / run_tests.sh / opt/stack/keystone/tests/test_backend.py.

Test an example:

Open a terminal and go to the project directory, such as keystone.

Run the. / run_tests.sh: command, such as. / run_tests.sh / opt/stack/keystone/tests/test_backend.py:CommonHelperTests.

Test a method:

Open a terminal and go to the project directory, such as keystone.

Run. / run_tests.sh:. Commands, such as. / run_tests.sh / opt/stack/keystone/tests / test_backend.py:CommonHelperTests.test_format_helper_raises_malformed_on_incomplete_format.

Run the OpenStack service

All services running Devstack:

Open a terminal and change to the devstack directory.

Run the. / stack.sh command. In localrc, specify the service to run, such as ENABLED_SERVICES=key,c-api,c-vol,c-sch,mysql,rabbit.

Run. / unstack.sh to shut down all services.

After the first successful run of. / stack.sh, you can also run. / rejoin-stack.sh to run all specified services.

Run the service in Eclipse. Take Keystone as an example:

Set the debug configuration of keystone in Eclipse. Right-click everything under the script keystone-bin, and then click Debug as > Debug Configurations, as shown in figure 3.

Figure 3. Debug configuration

Set the debug configuration. Click the Arguments tab, select Other as the working directory, and enter ${workspace_loc:keystone}, as shown in figures 4 and 5.

Figure 4. Main tab configuration

Figure 5. Arguments tab configuration

Start Keystone: click the Debug button on the Debug Configuration window, or run it from the Debug/Run drop-down toolbar button, as shown in figure 6.

Figure 6. Start the Keystone service

Step 4: set up the local computer configuration

Set up the git global configuration:

Open a terminal.

Run the git config-- global user.name "Firstname Lastname" command.

Run the git config-- global user.email "your_email@youremail.com" command.

Install the git-review tool:

For Ubuntu 12.04 or later, run the sudo apt-get install git-review command on a terminal.

For versions prior to Ubunu 12.04, run the sudo pip install git-review command.

Configure your project to learn about Gerrit:

Open a terminal and go to the project directory, such as keystone.

Run the git review-s command. You will be asked to enter your gerrit user name. Please type your Launchpad id and press Enter.

Step 5: OpenStack Workflow demonstration

If you find an OpenStack problem, please register it as a bug. If you want to add a new feature, register it as a blueprint. The changes you are about to add should be in the branch version, not the major version. In addition, do not mix multiple bug fixes or blueprints in a branch version. The following workflow shows an example of bug repair in Keystone.

Submit the bug of Keystone:

Figure 7. Submit the bug of Keystone

Visit https://launchpad.net/keystone.

Click Report a bug, and then enter the profile and the required information.

Click the Submit bug report button. This bug has a link: https://bugs.launchpad.net/keystone/+bug/1087674 and a bug number: 1087674.

Assign this bug to yourself in the Assigned to column.

Create a branch (branch name Bug1087674) in keystone for this bug:

Open a terminal and change to the keystone directory.

Make sure that keystone is in the major version through git checkout master.

Run the git checkout-b Bug1087674 command.

Modify the keystone code in the branch Bug1087674.

Submit the code to Gerrit:

Open a terminal and change to the keystone directory.

Run the git commit-a command.

Enter some comments. The first paragraph should be an introduction to a sentence; the second paragraph can be a detailed description (optional); if the branch fixes a bug or a blueprint, add Fixes Bug1087674 or Blueprint XXXX as the last paragraph.

Run the ctrl+o command, press Enter, and then run ctrl+x.

Run git review.

Check for submitted patches:

Figure 8. The Review page of the submitted patch

Go to https://review.openstack.org and log in using your Launchpad account.

From the top horizontal navigator, click My > Changes, and then you can find the patch you have submitted.

In this demonstration, the link is https://review.openstack.org/#/c/17673/. Any user can view this patch. Any developer can give comments.

Typically, this is the process of submitting a patch. But what if some developers add comments and you decide to change the branch? Here is an option:

Open a terminal and change to the keystone directory.

Go to the branch Bug1087674 via git checkout Bug1087674.

Make further modifications to this branch.

Change to the keystone directory.

Run the git commit-a-amend command. Do not run git commit-a, or multiple comments will be submitted to Gerrit, which is not recommended. )

Please modify the notes if possible.

Run the ctrl+o command, then press Enter and run ctrl+x.

Run git review.

After the patch is submitted for the second time, there are two patch sets in the linked https://review.openstack.org/#/c/17673/, as shown in figure 9.

Figure 9. History of patch sets

In addition, what if the primary branch changes when you use the branch Bug1087674? Here are what you can do:

Open a terminal and go to the main branch via git checkout master.

Update the code with git pull origin master.

Switch back to this branch via git checkout Bug1087674.

The code is refactored through git rebase-I master.

If there are no conflicts, run the git commit-a-amend command and run git review.

If a conflict occurs, the terminal will display the file with the conflict.

You can also look for conflicts in Eclipse because conflicting files are marked in red.

Fix these conflicts manually.

Continue refactoring, git rebase-continue.

After the refactoring is successful, run the git commit-a-amend command and git review.

On the OpenStack development source code how to obtain and download to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.