This post originally appeared under the title “Inside Speedinvest: Why I Joined the Deep Tech Team” on February, 23rd 2020 as a guest post at speedinvest.com.
I am stoked to report that I have joined the SpeedinvestDeep Tech team as a principal to cover Germany.
Since Speedinvest is highly distributed with teams in Vienna, Munich, Berlin, London and San Francisco, and I will be remote for the most part, it seems only fitting to introduce myself via the blog — so here it goes:
I started programming as a kid and pretty much stayed in tech ever since. Even though I’d always introduce myself as a software developer, on paper I am a lawyer, but I’ll spare you the details on this little detour. During my law studies, it pulled me back into software development and I co-founded fruux, a German software company behind the sabre/dav open source technology, powering sync functionality in products, such as atmail, Box, Nextcloud, Posteo, ownCloud and many others.
After running a SaaS company for many years, I’ve spent time working on digital projects and taking care of technology investments & acquisitions with a member of the executive board at C.H.BECK, one of the major legal publishers in the DACH region. Before joining Speedinvest, I was also a member of the investment team at Target Partners, a leading early-stage tech VC.
The diverse and highly distributed team at Speedinvest allows me to stay on course with my thematic interests, and ‘go even earlier’ as investor. Not to mention, as a founder and software developer, the Speedinvest Deep Tech team is the perfect platform to find and support Europe’s most exciting tech companies. It’s a win-win!
Tech I like?
I am interested in everything from enterprise software, tools that help developers & ‘NoCoders’ build, test, deploy, secure and monitor software, all the way down to (mostly software-defined) infrastructure, as well as everything related to distributed & remote work.
To all the founders out there: If you are working on exciting tech, I’d love to talk. Just shoot me an email, find me on LinkedIn or hit me up on Twitter.
Older Ansible Tower versions don’t have cleanup tasks scheduled by default, which may lead to a very slow or even unusable Tower instance with lots of historic data. At that point it may not even be possible to schedule cleanup task and even if they are set up with lots of patience they may be so slow that they timeout. Luckily there’s a command line tool called awx-manage, but in my case even that failed as the cleanup tasks also timed out.
At that point the only remedy is to manually delete data in Tower. I managed to unstuck a Ansible Tower 2.1.4 instance as follows:
Run the Tower shell via awx-manage (ideally in a screen session, this may take a while):
Paste the following code into the shell to cleanup objects in the database:
This iterates through all Job objects up to record_id=200000 and deletes them. You may have a lot less or a lot more objects in your Tower database, so you might have to adjust the 200000 to something else. I also had to delete the UnifiedJob objects, so you also might have to run this:
This took several hours in my case, your mileage may vary. After this manual deletion went through the following awx-manage cleanup commands started working again for me:
Finally I restarted Ansible Tower and the webinterface was reasonably fast again. Hope it works for you, too!