BUGS of OPENSTACK: broken dependency of version of openstack-novaclient in tarballs of horizon-9.1.2
WRONG!!!
1 2 3 | (.venv) [homitaka@tayn1 horizon]$ egrep novaclient requirements.txt python-novaclient!=2.33.0,>=2.29.0 # Apache-2.0 (.venv) [homitaka@tayn1 horizon]$ |
pip – to show all versions of package
(.venv) [[email protected] ~]$ pip install python-novaclient== Collecting python-novaclient== Could not find a version that satisfies the requirement python-novaclient== (from versions: 2.6.0, 2.6.0.1, 2.6.10, 2.7.0, 2.8.0, 2.9.0, 2.10.0, 2.11.0, 2.11.1, 2.12.0, 2.13.0, 2.14.0, 2.14.1, 2.15.0, 2.16.0, 2.17.0, 2.18.0, 2.18.1, 2.19.0, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.23.1, 2.23.2, 2.23.3, 2.24.0, 2.24.1, 2.25.0, 2.26.0, 2.27.0, 2.28.0, 2.28.1, 2.29.0, 2.30.0, 2.30.1, 2.30.2, 2.30.3, 2.31.0, 2.32.0, 2.33.0, 2.34.0, 2.35.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0, 3.3.1, 3.3.2, 3.4.0, 4.0.0, 4.1.0, 5.0.0, 5.1.0, 6.0.0, 6.0.1, 7.0.0, 7.1.0, 7.1.1, 8.0.0) No matching distribution found for python-novaclient== (.venv) [[email protected] ~]$
Deploy Horizon (any releases) from tarballs with Apache for isolated user in virtual environment.
If your company use OpenStack clouds without ‘Horizon Dashboard’ interface, you may wish to deploy your own horizon instance. Or you can use this method for permanent deploy any version of Horizont in your clouds.
However, your concern is that http might be insecure… especially if hosted on a VM or machine accessible from the Internet. So you want an SSL connection. It is will be in next parts of articles
ref: https://docs.openstack.org/developer/horizon/topics/install.html
5 – five-minute introduction to the module logging Python
The use of pirnt is suitable for those programmers who have enough time. But it’s better to use logging. In addition, learn to use the Python debugger for debugging errors and Pylint to prevent errors and to make the code more readable.
In order to display the log messages on the screen, use the following code:
Flush Expired Openstack Keystone Tokens
After a while of running Openstack and performing a lot of testing (especially Tempest) you may find that your database seems to get pretty full … and this is partly down to expired keystone token’s that remain in the DB table.
To resolve this simply setup a periodic Cron job to execute
1 | # /usr/bin/keystone-manage token_flush |
This will remove all expired tokens to help clean-up the DB a bit
Of course, this action better to insert as cron task:
1 2 3 4 | # cat keystone_token_flush #!/bin/bash 10 * * * * root /usr/bin/keystone-manage token_flush |
Own installation Ganeti Web Manager + own Python environment + localization (by desire).
Актуально для текущей-последней версии GWM (в репозитории pip), для Python 2.17.13 (собственная оригинальная инсталляция в /opt).
Apache 2.4, Ganeti 2.15.2 on CentOS7.
Protected: Apache 2.4 and compilation mod_wsgi for alternative python version.
Additional version of Python 2.7.* from source code, local pip and mod_wsgi on Apache2.4
Python – bunch of difficult sets of scripts on 80%. It is have own pros and cons. Very often – it is problems of difficult dependencies of application, when in OS we see old version of Python interpretator.
Building own version from source is the most appropriate variant of solving if need to use it only for local application in environment of some user or web servers.
Here is sample of commands of shell for getting copy of installation of Python in special directory – /opt.
OpenStack : Glance 11.0.1 on OpenSuse 13.2 – ‘cannot import name _uuid_generate_random’
Если вы получили этот питоньячий костыль при попытке запуска glance
ERROR: Unable to load glance-api-keystone from configuration file /etc/glance/glance-api-paste.ini.
Got: ImportError('cannot import name _uuid_generate_random',)
OpenStack : по следам костыльного сообщения – No handlers could be found for logger “oslo_config.cfg”
Отслеживания питоньячего кода привело к удивительном открытию. В процессы установки glance чуда по мануалам мы получили, в частности два питоньячих модуля в основной системе: