简体繁体 English

将修改从Devstack复制到Openstack（生产）

[英]replicate modification from Devstack to Openstack (production)

原文 2012-11-29 10:28:24 2 1 python/ openstack

I installed openstack through DevStack because I had to modify some files. 我通过DevStack安装了openstack，因为必须修改一些文件。 When I install DevStack, I have all the files under /opt/stack. 安装DevStack时，所有文件都在/ opt / stack下。 There I have services folders (glance, keystone...) and libraries folders (python-glanceclient, python-keystoneclient). 那里有服务文件夹（glance，keystone ...）和库文件夹（python-glanceclient，python-keystoneclient）。 If I modify those files, how can I replicate modification on a already deployed Openstack? 如果修改这些文件，如何在已部署的Openstack上复制修改？ Installing openstack without devstack builds a different structure of folder. 不使用devstack安装openstack会构建不同的文件夹结构。

I mean, where the python-'service'client folders are in a fresh openstack installation? 我的意思是，全新安装的python-'service'client文件夹在哪里？

Thank you 谢谢

1 个解决方案

devstack pulls it's openstack software stack from github. devstack从github提取了openstack软件堆栈。 the git repot's it installs from are located in /opt/stack. 安装的git仓库位于/ opt / stack中。

What you may want to do is fork openstack as well as the repot of the openstack projects you wish to modify, then make your devstack deployment deploy not from the openstack repot, but your own forked repot. 您可能想要做的是派生openstack以及您要修改的openstack项目的仓库，然后使devstack部署不是从openstack仓库而是从您自己的派生仓库部署。

you can do this by modifying the stack.sh script ( I believe ). 您可以通过修改stack.sh脚本（我相信）来做到这一点。 devstack.org has a line by line explanation of the entire script on their site and that can point you in the right direction. devstack.org在网站上逐行解释了整个脚本，可以为您指明正确的方向。

http://devstack.org/stack.sh.html read this. http://devstack.org/stack.sh.html阅读此内容。

once you've deployed using your own git repository you can of course edit and commit back to it. 使用自己的git存储库进行部署后，您当然可以对其进行编辑并将其提交回来。 even push to it. 甚至推动它。

then any other devstack deployment you have can also be setup to pull from your repository instead of the public openstack repos. 那么您也可以将任何其他devstack部署设置为从存储库中提取，而不是从公共openstack仓库中提取。

of course rebasing later against openstack will be increasingly difficult as openstack developement moves at a fairly brisk pace. 当然，随着openstack的发展以相当快的速度发展，在以后针对openstack进行基础调整将变得越来越困难。

If the modification you are making is one you want to commit back to the open source project check out this site: 如果您要进行的修改是要提交给开源项目的修改，请访问以下站点：

http://wiki.openstack.org/HowToContribute http://wiki.openstack.org/HowToContribute

Basically openstack has a commit review and continuous integration environment that is based off of gerrit and jenkins. 基本上，openstack具有基于gerrit和jenkins的提交审核和持续集成环境。 This is the method by which commits back to the open source repository are gate tested and manually reviewed by other developers before being merged. 这是对合并到开放源代码存储库中的提交进行门测试并在合并之前由其他开发人员手动检查的方法。

If you are intending to deploy this for production use, I recommend against deploying from devstack. 如果打算将其部署供生产使用，则建议不要从devstack进行部署。 This is not the proper way to do that. 这不是正确的方法。