I am busy changing the world

At the end of the Rocky development cycle of OpenStack, the Technical Committee intended to remove Searchlight [1] and some other projects (e.g. Freezer) from the Governance (OpenStack official projects). The reasons for that are because Searchlight has missed several milestones and lacked communication of the PTLs (Project Technical Lead). I couldn't stand the fact that a pretty cool project would be abandoned so I nominated to be the PTL of Searchlight for the Stein cycle. I hope that I can do something to revive it. Why should Searchlight be revived?  That is the question I tried to answer when decided to take the lead. It's harder and harder for cloud operators to get the information about the resources of other services (e.g Nova Compute, Swift, Cinder etc.) because they evolve very fast and there are more and more resources and APIs are made (Do you hear about the placement API of Nova?). Searchlight is pretty cool in this case because It centralizes all of that inf...

As you may already know, OpenStack is a big software project that running on stacks of servers so you cannot just folk it to your computer and run. Fortunately, the OpenStack community had built a minimal version of the OpenStack called devstack that help you have a developing environment without using a lot of resources. But, devstack still eats lots of CPU and memory of your computer so in my opinion, it's better to have a dedicated machine for running devstack (mine is a computer with 16GB). So the last things you need to do to start working on your patches are: 1. SSH to the devstack server 2. Make sure that the service outputs logs to some files (such as /opt/stack/logs/tacker.log) For Tacker or services that have settings file under /etc/<service name>/<service name>.conf, you can change the parameter to output logs to file 3. Using tmux or byobu to have multiple ssh console screens that you can easily switch to and for 4. Use VI or NANO to ma...

I'm using the djangosaml2 app to add the Single Sign On functionality using  SAML2 to my Django projects. I followed the official manual at  https://bitbucket.org/lgs/djangosaml2/overview  to make my project work with a SimpleSAMLphp instance as an IdP but I got this error: cannot serialize IdpUnspecified('No IdP to send to given the premises',) (type IdpUnspecified) I have no idea why this error showed up?! I have a very little knowledge about SAML2 and the PySAML2 module. The only thing I can think about is to enable logging for the djangosaml2 app. So, I added these following lines in the settings.py of my project: import logging logging.basicConfig() I reloaded the website and a logging message appeared in the console: ERROR:djangosaml2:Unable to know which IdP to use Yessss, that is the problem!