Fedora and Red Hat Leftovers
-
Thessaloniki Fedora 37 Release Party aftermath | iBlog Efstathios Iosifidis
We, at Open Source UoM, organized a Fedora 37 Release Party. These kind of events are organized around the world after the new version of Fedora is released. It is likely that it was the world’s first post-pandemic in-person Fedora 37 Release Party. There was an online Release Party, that showed us the way.
Being an organizer once again, I felt the joy of organizing an event, meet friends and discuss about my favourite topic. The party was attended by Open Source UoM members and students of the University of Macedonia. Fortunately, every promo material I was sent, arrived on time and I gave it as a present to the party animals.
-
What's new in Ansible Automation Platform 2.3
We are thrilled to announce the general availability of Red Hat Ansible Automation Platform 2.3. If you didn’t get the opportunity to attend AnsibleFest 2022 in Chicago, or get time to watch the keynotes on the AnsibleFest content hub, I am the lucky Ansiblite (or is it Ansi-Bull) who will walk you through all the new, cool and exciting features coming with our new release. Ansible Automation Platform 2.3 introduces a number of new features and capabilities that deliver simpler, security-focused automation at scale. Ansible Automation Platform 2.3 is compatible with the Developer Preview of Event-Driven Ansible, a new set of capabilities that empower true end-to-end automation.
-
Understanding the Confidential Containers Attestation Flow
Attestation is a confidential computing keystone. With attestation, workload owners can fully assert the trustworthiness of the hardware and software environment their workload is running in, regardless of the security posture of the underlying infrastructure provider.
This article describes the hardware-based attestation flows and processes that the Confidential Containers project is built upon. With hardware-based attestation, a confidential computing processor generates cryptographic evidence for a workload-running environment. Provided that the workload owner trusts that piece of hardware, they can then remotely verify that evidence and decide if the workload’s execution environment is trustworthy or not. If it is, the owner can then provision it with a set of secrets ( e.g. container image encryption keys), effectively permitting it to run the workload.
-
Event-driven automation: How to build an event-driven automation architecture
Event-driven automation is at the core of automating your emergency response, reducing reaction times to as close to real-time as possible. It’s also at the center of a Self-Healing Infrastructure, enabling consistency and efficiency in lifecycle, content and compliance management across a hybrid cloud infrastructure.
In the first article in this series, we outlined the difference between basic automation and event-driven automation. Following up in our second article, we then defined what the common architectural components consist of, and how we can use a combination of different technologies to create a solution such as this. Now, we will take a deeper look into an example architecture that could be used in your industry, and further outline how to construct this solution within your organization.
-
Red Hat Lowers Barriers to Hybrid Cloud Adoption with Expanded Public Offerings in AWS Marketplace
-
Code Comments - Season 1, Episode 3: Amazon Web Services and Open Principles
It’s one thing to talk about your open source principles. It’s another entirely to build them into your workflows. How does a large company like Amazon Web Services actually make it work? David Duncan, Sr Manager Partner Solutions Architect at AWS, explains that being open with partners and customers throughout the development process is key. He talks about ensuring there are no one-way doors, and how collaboration helps to produce a better experience for OpenShift on AWS as well as combining the power of the Cloud Control API with Ansible automation.