<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Haikel,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Apparently we are doing it wrong (according to apevec). We should be using a different iscsi package. So until we make the change, I guess epel will have to stay in our repos.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">-steve<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Haïkel <hguemar@fedoraproject.org></span><span style="font-family:PMingLiU;color:black"><br>
</span><b><span style="font-family:Calibri;color:black">Reply-To: </span></b><span style="font-family:Calibri;color:black">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Friday, October 14, 2016 at 2:33 PM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [daisycloud-core] Kolla Mitaka requirements supported by CentOS<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Le 12 oct. 2016 6:01 AM, "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>> a écrit :<span style="font-family:PMingLiU"><br>
</span>><span style="font-family:PMingLiU"><br>
</span>> Haikel,<span style="font-family:PMingLiU"><br>
</span>><span style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>><span style="font-family:PMingLiU"><br>
</span>> We attempted removing EPEL from our repo lists. We got build errors on cinder-volume. We have iscsi integration because vendors require it to work with their third party plugins. The package iscsi-target-utils is not in the newton repos for RDO.<br>
><br>
> <br>
><br>
> The package that fails can be seen here:<br>
><br>
> <a href="http://logs.openstack.org/04/385104/1/check/gate-kolla-dsvm-build-centos-source-centos-7-nv/f6cc1d8/console.html#_2016-10-11_19_34_40_662928">
http://logs.openstack.org/04/385104/1/check/gate-kolla-dsvm-build-centos-source-centos-7-nv/f6cc1d8/console.html#_2016-10-11_19_34_40_662928</a><br>
><br>
> <br>
><br>
> If you could fix that up, it would be grand J<br>
><br>
> <o:p></o:p></p>
<p>Sorry for the delay, it got in the wrong folder, I'll look into adding this package.<o:p></o:p></p>
<p>H.<br>
><br>
> Thanks<br>
><br>
> -steve<br>
><br>
> <br>
><br>
> <br>
>><br>
>> From: Haïkel <<a href="mailto:hguemar@fedoraproject.org">hguemar@fedoraproject.org</a>><br>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
>> Date: Saturday, July 2, 2016 at 2:14 PM<br>
>><br>
>> To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
>> Subject: Re: [openstack-dev] [daisycloud-core] Kolla Mitaka requirements supported by CentOS<br>
>><br>
>> <br>
>><br>
>> 2016-07-02 20:42 GMT+02:00 jason <<a href="mailto:huzhijiang@gmail.com">huzhijiang@gmail.com</a>>:<br>
>>><br>
>>> Pip Package Name Supported By Centos CentOS Name Repo Name<br>
>>><br>
>>> ======================================================================================================================<br>
>>><br>
>>> ansible yes<br>
>>><br>
>>> ansible1.9.noarch epel<br>
>>><br>
>>> docker-py yes<br>
>>><br>
>>> python-docker-py.noarch extras<br>
>>><br>
>>> gitdb yes<br>
>>><br>
>>> python-gitdb.x86_64 epel<br>
>>><br>
>>> GitPython yes<br>
>>><br>
>>> GitPython.noarch epel<br>
>>><br>
>>> oslo.config yes<br>
>>><br>
>>> python2-oslo-config.noarch centos-openstack-mitaka<br>
>>><br>
>>> pbr yes<br>
>>><br>
>>> python-pbr.noarch epel<br>
>>><br>
>>> setuptools yes<br>
>>><br>
>>> python-setuptools.noarch base<br>
>>><br>
>>> six yes<br>
>>><br>
>>> python-six.noarch base<br>
>>><br>
>>> pycrypto yes<br>
>>><br>
>>> python2-crypto epel<br>
>>><br>
>>> graphviz no<br>
>>><br>
>>> Jinja2 no (Note: Jinja2 2.7.2 will be installed as<br>
>>><br>
>>> dependency by ansible)<br>
>>><br>
>>> <br>
>><br>
>> <br>
>><br>
>> As one of RDO maintainer, I strongly invite kolla, not to use EPEL.<br>
>><br>
>> It's proven very hard to prevent EPEL pushing broken updates, or push<br>
>><br>
>> updates to fit OpenStack requirements.<br>
>><br>
>> <br>
>><br>
>> Actually, all the dependency above but ansible, docker and git python<br>
>><br>
>> modules are in CentOS Cloud SIG repositories.<br>
>><br>
>> If you are interested to work w/ CentOS Cloud SIG, we can add missing<br>
>><br>
>> dependencies in our repositories.<br>
>><br>
>> <br>
>><br>
>> <br>
>>><br>
>>> <br>
>>><br>
>>> As above table shows, only two (graphviz and Jinja2) are not supported<br>
>>><br>
>>> by centos currently. As those not supported packages are definitly not<br>
>>><br>
>>> used by OpenStack as well as Daisy. So basicaly we can use pip to<br>
>>><br>
>>> install them after installing other packages by yum. But note that<br>
>>><br>
>>> Jinja2 2.7.2 will be installed as dependency while yum install<br>
>>><br>
>>> ansible, so we need to using pip to install jinja2 2.8 after that to<br>
>>><br>
>>> overide the old one. Also note that we must make sure pip is ONLY used<br>
>>><br>
>>> for installing those two not supported packages.<br>
>>><br>
>>> <br>
>>><br>
>>> But before you trying to use pip, please consider these:<br>
>>><br>
>>> <br>
>>><br>
>>> 1) graphviz is just for saving image depend graph text file and is not<br>
>>><br>
>>> used by default and only used in build process if it is configured to<br>
>>><br>
>>> be used.<br>
>>><br>
>>> <br>
>>><br>
>>> 2) Jinja2 rpm can be found at<br>
>>><br>
>>> <a href="http://koji.fedoraproject.org/koji/packageinfo?packageID=6506">http://koji.fedoraproject.org/koji/packageinfo?packageID=6506</a>, which I<br>
>>><br>
>>> think is suitable for CentOS. I have tested it.<br>
>>><br>
>>> <br>
>>><br>
>>> So, as far as Kolla deploy process concerned, there is no need to use<br>
>>><br>
>>> pip to install graphviz and Jinja2. Further more, if we do not install<br>
>>><br>
>>> Kolla either then we can get ride of pip totally!<br>
>>><br>
>>> <br>
>>><br>
>>> I encourage all of you to think about not using pip any more for<br>
>>><br>
>>> Daisy+Kolla, because pip hase a lot of overlaps between yum/rpm, files<br>
>>><br>
>>> may be overide back and force if not using them carefully. So not<br>
>>><br>
>>> using pip will make things easier and make jump server more cleaner.<br>
>>><br>
>>> Any ideas?<br>
>>><br>
>>> <br>
>>><br>
>>> <br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> Zhijiang<br>
>>><br>
>>> <br>
>>><br>
>>> --<br>
>>><br>
>>> Yours,<br>
>>><br>
>>> Jason<br>
>>><br>
>>> <br>
>>><br>
>>> __________________________________________________________________________<br>
>>><br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>><br>
>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>> <br>
>><br>
>> __________________________________________________________________________<br>
>><br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>><br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>> <br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><o:p></o:p></p>
</blockquote>
</div>
</body>
</html>