<font size=2 face="sans-serif">Steve,</font>
<br>
<br><font size=2 face="sans-serif">I agree with you on that Kolla can use
</font><font size=2 face="Calibri">EPEL</font><font size=2 face="sans-serif">,
because Kolla is not a function part of OpenStack but a deployment tool.
In the same vein, is that means Kolla do not need to catch up with the
global requirements of OpenStack? For example, instead of using oslo required
by OpenStack, can Kolla be more open to be compatible with an old oslo?
This is a big deal because if installers such as daisycloud-core want to
use Kolla as underlying deployment tool, they should keep the same requirements
updating cadence as kolla, but sometimes that is not necessary for OpenStack
installers. <br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">发件人:
</font><font size=1 face="sans-serif">"Steven
Dake (stdake)" <stdake@cisco.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">收件人:
</font><font size=1 face="sans-serif">"OpenStack
Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">日期:
</font><font size=1 face="sans-serif">2016-07-06
02:03</font>
<br><font size=1 color=#5f5f5f face="sans-serif">主题:
</font><font size=1 face="sans-serif">[probably forge
email可能是仿冒邮件]Re: [openstack-dev] [daisycloud-core] [kolla]
Kolla Mitakarequirementssupported by CentOS</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Hu,</font>
<br>
<br><font size=2 face="Calibri">I am open to not using EPEL in the containers
themselves. I didn't even know all the dependencies were available
without EPEL. I am on vacation at present, but I'll try a build without
EPEL and see if it actually builds correctly. This does raise the
question were ansible, docker, and git tools come from. I am not
keen to pull them from COPRs because I want them distributed via the CDN
for HA purposes.</font>
<br>
<br><font size=2 face="Calibri">Are you planning to pull ansible, docker,
and the git tools into delorean-deps? One thing I am not keen on
doing is yum install with an URL.</font>
<br>
<br><font size=2 face="Calibri">Also for source builds we absolutely require
EPEL because we need gcc and other development tools.</font>
<br>
<br>
<br>
<br><font size=2 face="Calibri">As for the deployment host, we do require
EPEL which is perfectly normal. </font>
<br>
<br><font size=2 face="Calibri"><b>From: </b>"</font><a href=mailto:hu.zhijiang@zte.com.cn><font size=2 color=blue face="Calibri"><u>hu.zhijiang@zte.com.cn</u></font></a><font size=2 face="Calibri">"
<</font><a href=mailto:hu.zhijiang@zte.com.cn><font size=2 color=blue face="Calibri"><u>hu.zhijiang@zte.com.cn</u></font></a><font size=2 face="Calibri">><b><br>
Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)"
<</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Date: </b>Monday, July 4, 2016 at 1:02 AM<b><br>
To: </b>"OpenStack Development Mailing List (not for usage questions)"
<</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Subject: </b>Re: [openstack-dev] [daisycloud-core] [kolla] Kolla Mitaka
requirementssupported by CentOS</font>
<br>
<br><font size=2 face="Calibri">> As one of RDO maintainer, I strongly
invite kolla, not to use EPEL.<br>
> It's proven very hard to prevent EPEL pushing broken updates, or push<br>
> updates to fit OpenStack requirements.<br>
<br>
> Actually, all the dependency above but ansible, docker and git python<br>
> modules are in CentOS Cloud SIG repositories.<br>
> If you are interested to work w/ CentOS Cloud SIG, we can add missing<br>
> dependencies in our repositories.</font><font size=2 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
I added [kolla] key word in the mail subject. Hope can get response from
Kolla team about how to choose repos.</font><font size=2 face="Calibri"><br>
<br>
</font><font size=2 face="sans-serif"><br>
Thanks,</font><font size=2 face="Calibri"> </font><font size=2 face="sans-serif"><br>
Zhijiang</font><font size=2 face="Calibri"> <br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
发件人: </font><font size=1 face="sans-serif">Haïkel
<</font><a href=mailto:hguemar@fedoraproject.org><font size=1 color=blue face="sans-serif"><u>hguemar@fedoraproject.org</u></font></a><font size=1 face="sans-serif">></font><font size=1 color=#5f5f5f face="sans-serif"><br>
收件人: </font><font size=1 face="sans-serif">"OpenStack
Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=1 color=blue face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size=1 face="sans-serif">>,
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
日期: </font><font size=1 face="sans-serif">2016-07-03
05:18</font><font size=1 color=#5f5f5f face="sans-serif"><br>
主题: </font><font size=1 face="sans-serif">[probably
forge email可能是仿冒邮件]Re: [openstack-dev] [daisycloud-core]
Kolla Mitaka requirementssupported by CentOS</font><font size=2 face="Calibri"><br>
</font>
<hr noshade><font size=2 face="Calibri"><br>
<br>
</font><font size=2 face="Calibri"><br>
2016-07-02 20:42 GMT+02:00 jason <</font><a href=mailto:huzhijiang@gmail.com><font size=2 color=blue face="Calibri"><u>huzhijiang@gmail.com</u></font></a><font size=2 face="Calibri">>:<br>
> Pip Package Name Supported By Centos CentOS Name
Repo Name<br>
> ======================================================================================================================<br>
> ansible
yes<br>
> ansible1.9.noarch
epel<br>
> docker-py yes<br>
> python-docker-py.noarch extras<br>
> gitdb
yes<br>
> python-gitdb.x86_64 epel<br>
> GitPython yes<br>
> GitPython.noarch
epel<br>
> oslo.config yes<br>
> python2-oslo-config.noarch centos-openstack-mitaka<br>
> pbr
yes<br>
> python-pbr.noarch
epel<br>
> setuptools yes<br>
> python-setuptools.noarch base<br>
> six
yes<br>
> python-six.noarch
base<br>
> pycrypto yes<br>
> python2-crypto
epel<br>
> graphviz no<br>
> Jinja2
no (Note: Jinja2 2.7.2 will be installed as<br>
> dependency by ansible)<br>
><br>
<br>
As one of RDO maintainer, I strongly invite kolla, not to use EPEL.<br>
It's proven very hard to prevent EPEL pushing broken updates, or push<br>
updates to fit OpenStack requirements.<br>
<br>
Actually, all the dependency above but ansible, docker and git python<br>
modules are in CentOS Cloud SIG repositories.<br>
If you are interested to work w/ CentOS Cloud SIG, we can add missing<br>
dependencies in our repositories.<br>
<br>
<br>
><br>
> As above table shows, only two (graphviz and Jinja2) are not supported<br>
> by centos currently. As those not supported packages are definitly
not<br>
> used by OpenStack as well as Daisy. So basicaly we can use pip to<br>
> install them after installing other packages by yum. But note that<br>
> Jinja2 2.7.2 will be installed as dependency while yum install<br>
> ansible, so we need to using pip to install jinja2 2.8 after that
to<br>
> overide the old one. Also note that we must make sure pip is ONLY
used<br>
> for installing those two not supported packages.<br>
><br>
> But before you trying to use pip, please consider these:<br>
><br>
> 1) graphviz is just for saving image depend graph text file and is
not<br>
> used by default and only used in build process if it is configured
to<br>
> be used.<br>
><br>
> 2) Jinja2 rpm can be found at<br>
> </font><a href="http://koji.fedoraproject.org/koji/packageinfo?packageID=6506"><font size=2 color=blue face="Calibri"><u>http://koji.fedoraproject.org/koji/packageinfo?packageID=6506</u></font></a><font size=2 face="Calibri">,
which I<br>
> think is suitable for CentOS. I have tested it.<br>
><br>
> So, as far as Kolla deploy process concerned, there is no need to
use<br>
> pip to install graphviz and Jinja2. Further more, if we do not install<br>
> Kolla either then we can get ride of pip totally!<br>
><br>
> I encourage all of you to think about not using pip any more for<br>
> Daisy+Kolla, because pip hase a lot of overlaps between yum/rpm, files<br>
> may be overide back and force if not using them carefully. So not<br>
> using pip will make things easier and make jump server more cleaner.<br>
> Any ideas?<br>
><br>
><br>
> Thanks,<br>
> Zhijiang<br>
><br>
> --<br>
> Yours,<br>
> Jason<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>OpenStack-dev-request@lists.openstack.org</u></font></a><font size=2 face="Calibri">?subject:unsubscribe<br>
> </font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size=2 color=blue face="Calibri"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size=2 face="Calibri"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>OpenStack-dev-request@lists.openstack.org</u></font></a><font size=2 face="Calibri">?subject:unsubscribe</font><font size=2 color=blue face="Calibri"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size=2 color=blue face="Calibri"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size=2 face="Calibri"><br>
<br>
</font>
<br><font size=2 color=blue face="Calibri"><br>
--------------------------------------------------------<br>
ZTE Information Security Notice: The information contained in this mail
(and any attachment transmitted herewith) is privileged and confidential
and is intended for the exclusive use of the addressee(s). If you
are not an intended recipient, any disclosure, reproduction, distribution
or other dissemination or use of the information contained is strictly
prohibited. If you have received this mail in error, please delete
it and notify us immediately.<br>
<br>
</font>
<br><tt><font size=2>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><pre><font color="blue">
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
</font></pre><br>