[openstack-dev] [daisycloud-core] Kolla Mitaka requirements supported by CentOS
jason
huzhijiang at gmail.com
Sat Jul 2 18:42:24 UTC 2016
Pip Package Name Supported By Centos CentOS Name Repo Name
======================================================================================================================
ansible yes
ansible1.9.noarch epel
docker-py yes
python-docker-py.noarch extras
gitdb yes
python-gitdb.x86_64 epel
GitPython yes
GitPython.noarch epel
oslo.config yes
python2-oslo-config.noarch centos-openstack-mitaka
pbr yes
python-pbr.noarch epel
setuptools yes
python-setuptools.noarch base
six yes
python-six.noarch base
pycrypto yes
python2-crypto epel
graphviz no
Jinja2 no (Note: Jinja2 2.7.2 will be installed as
dependency by ansible)
As above table shows, only two (graphviz and Jinja2) are not supported
by centos currently. As those not supported packages are definitly not
used by OpenStack as well as Daisy. So basicaly we can use pip to
install them after installing other packages by yum. But note that
Jinja2 2.7.2 will be installed as dependency while yum install
ansible, so we need to using pip to install jinja2 2.8 after that to
overide the old one. Also note that we must make sure pip is ONLY used
for installing those two not supported packages.
But before you trying to use pip, please consider these:
1) graphviz is just for saving image depend graph text file and is not
used by default and only used in build process if it is configured to
be used.
2) Jinja2 rpm can be found at
http://koji.fedoraproject.org/koji/packageinfo?packageID=6506, which I
think is suitable for CentOS. I have tested it.
So, as far as Kolla deploy process concerned, there is no need to use
pip to install graphviz and Jinja2. Further more, if we do not install
Kolla either then we can get ride of pip totally!
I encourage all of you to think about not using pip any more for
Daisy+Kolla, because pip hase a lot of overlaps between yum/rpm, files
may be overide back and force if not using them carefully. So not
using pip will make things easier and make jump server more cleaner.
Any ideas?
Thanks,
Zhijiang
--
Yours,
Jason
More information about the OpenStack-dev
mailing list