OpenStack

Hear from experts at Verizon, China Mobile, Intel, NTT and more. The post Inside telecom and NFV: Must-see sessions at the Berlin Summit appeared first on Superuser.

Do you know who Lew Tucker is? Of course you do. He’s the VP and CTO of Cloud Computing at Cisco, but that’s probably not why you know him. You...

OpenStack provides an ideal environment to implement efficient NVMe-based storage model for high throughput says Calsoft's Sagar Nangare. The post How to get high performance for network connected solid-state drives with NMVe over fabrics appeared first on Superuser.

With two days of AnsibleFest instead of one this time around, we had 100% more time to talk about Ansible things ! I got to attend great sessions, learn a bunch of things, chat and exchange war stories about Ansible, ARA, Zuul, Tower and many other ... [More] things. It was awesome and I wanted to take the time to share a bit about some of the great Ansible community projects that were featured during the event. [Less]

For this third episode, here are some thoughts on how upgrades from Docker to Podman could work for us in OpenStack TripleO. Don’t miss the first and second episodes where we learnt how to deploy and operate Podman containers. Edit: the upstream code ... [More] merged and we finally decided we wouldn’t remove the container during the migration from Docker to Podman. We would only stop it, and then remove containers at the end of the upgrade process. The principles remain the same and the demo is still valid at this point. I spent some time this week to investigate how we could upgrade the OpenStack Undercloud that is running Docker containers to run Podman containers, without manual intervention nor service disruption. The way I see it as this time (the discussion is still ongoing), is we could remove the Docker containers in Paunch, just before starting the Podman containers and service in Systemd. It would be done per container, in serial. for container in containers: docker rm container podman run container create systemd unit file && enable service In the follow demo, you can see the output of openstack undercloud upgrade with a work in progress prototype. You can observe the HAproxy running in Docker, and during the Step 1 of containers deployment, the container is stopped (top right) and immediately started in Podman (bottom right). You might think “that’s it?”. Of course not. There are still some problems that we want to figure out: Migrate containers not managed by Paunch (Neutron containers, Pacemaker-managed containers, etc).Whether or not we want to remove the Docker container or just stop (in the demo the containers are removed from Docker).Stopping Docker daemon at the end of the upgrade (will probably be done by upgrade_tasks in Docker service from TripleO Heat Templates). The demo is a bit long as it shows the whole upgrade output. However if you want to see when HAproxy is stopped from Docker and started in Podman, go to 7 minutes. Also don’t miss the last minute of the video where we see the results (podman containers, no more docker containers managed by Paunch, and SystemD services). Thanks for following this series of OpenStack / Podman related posts. Stay in touch for the next one! By the way, did you know you could follow our backlog here? Any feedback on these efforts are warmly welcome! [Less]

For this third episode, here are some thoughts on how upgrades from Docker to Podman could work for us in OpenStack TripleO. Don’t miss the first and second episodes where we learnt how to deploy and operate Podman containers. I spent some time this ... [More] week to investigate how we could upgrade the OpenStack Undercloud that is running Docker containers to run Podman containers, without manual intervention nor service disruption. The way I see it as this time (the discussion is still ongoing), is we could remove the Docker containers in Paunch, just before starting the Podman containers and service in Systemd. It would be done per container, in serial. for container in containers: docker rm container podman run container create systemd unit file && enable service In the follow demo, you can see the output of openstack undercloud upgrade with a work in progress prototype. You can observe the HAproxy running in Docker, and during the Step 1 of containers deployment, the container is stopped (top right) and immediately started in Podman (bottom right). You might think “that’s it?”. Of course not. There are still some problems that we want to figure out: Migrate containers not managed by Paunch (Neutron containers, Pacemaker-managed containers, etc). Whether or not we want to remove the Docker container or just stop (in the demo the containers are removed from Docker). Stopping Docker daemon at the end of the upgrade (will probably be done by upgrade_tasks in Docker service from TripleO Heat Templates). The demo is a bit long as it shows the whole upgrade output. However if you want to see when HAproxy is stopped from Docker and started in Podman, go to 7 minutes. Also don’t miss the last minute of the video where we see the results (podman containers, no more docker containers managed by Paunch, and SystemD services). Thanks for following this series of OpenStack / Podman related posts. Stay in touch for the next one! By the way, did you know you could follow our backlog here? Any feedback on these efforts are warmly welcome! [Less]

The post OpenKilda – Distributed is the Future appeared first on Aptira.

In my last post, about cultural norms in OpenStack, I said that ease of development was a self inflicted issue. This was somewhat contentious 🙂 I’ve had some interested expressed a deeper dive. In that post I articulated three cultural problems and ... [More] two technical ones. What does success for developers look like? I think independent … Continue reading OpenStack and ease of development [Less]

Author Mina Andrawos offers this overview in a the second part of the series. The post Modern cloud native architectures: Microservices, Containers and Serverless – Part 2 appeared first on Superuser.