Open-source News

Yesterday I delivered my initial arsenal of AMD Ryzen 7 PRO 6850U Linux benchmarks against various other AMD Ryzen and Intel Core notebooks. That ongoing Ryzen 7 PRO 6850U is happening from a Lenovo ThinkPad X13 Gen 3 AMD notebook and this new "Rembrandt" device continues looking good under Linux. But prior to installing Linux, I did run some benchmarks of Lenovo's Windows 11 Pro on there for seeing how the Linux vs. Windows performance is looking for this Zen 3+ SoC.

Buy Managed Malaysia VPS Server with Linux SSD Hosting - Onlive Server  EIN News

Just shy of two weeks since fwupd 1.8.2 was released with supporting more hardware for system and peripheral firmware updating under Linux, Fwupd 1.8.3 has now arrived as the newest version...

Just shy of two weeks since fwupd 1.8.2 was released with supporting more hardware for system and peripheral firmware updating under Linux, Fwupd 1.8.3 has now arrived as the newest version...

Toshiba's Visconti SoC provides an optimized image recognition processor and geared for advanced driver assistance system (ADAS) solutions for automobiles and similar modern use-cases. Toshiba engineers are now publishing patches for their DNN image processing accelerator driver with hopes of getting the code upstreamed into the mainline Linux kernel...

Toshiba Looks To Upstream DNN Image Processing Accelerator Driver For Their Visconti SoC  Phoronix

Toshiba's Visconti SoC provides an optimized image recognition processor and geared for advanced driver assistance system (ADAS) solutions for automobiles and similar modern use-cases. Toshiba engineers are now publishing patches for their DNN image processing accelerator driver with hopes of getting the code upstreamed into the mainline Linux kernel...

Since last year Microsoft has been working on Direct3D 12 video acceleration for Mesa so that Windows Subsystem for Linux can run common applications targeting the VA-API video acceleration API and ultimately enjoy GPU-based video acceleration by way of Direct3D 12. After the initial video encode/decode support for D3D12 was merged to Mesa earlier this year, the latest Microsoft contribution is now handling of video engine based effects...

Since last year Microsoft has been working on Direct3D 12 video acceleration for Mesa so that Windows Subsystem for Linux can run common applications targeting the VA-API video acceleration API and ultimately enjoy GPU-based video acceleration by way of Direct3D 12. After the initial video encode/decode support for D3D12 was merged to Mesa earlier this year, the latest Microsoft contribution is now handling of video engine based effects...

Released last month was AMD ROCm 5.2 for the company's open-source Linux GPU compute stack while out today is the v5.2.1 point release...

Released last month was AMD ROCm 5.2 for the company's open-source Linux GPU compute stack while out today is the v5.2.1 point release...

2 Ways to install AnyDesk on Oracle Linux 8  Linux Shout

When it comes to compressing textures using the Adaptive Scalable Texture Compression (ASTC) format that is supported by the OpenGL / OpenGL ES / Vulkan APIs, Arm's ASTC Encoder has long reigned supreme. Out today is ASTC-Encoder 4.0 as the latest performance-boosting update to this open-source compressor...

When it comes to compressing textures using the Adaptive Scalable Texture Compression (ASTC) format that is supported by the OpenGL / OpenGL ES / Vulkan APIs, Arm's ASTC Encoder has long reigned supreme. Out today is ASTC-Encoder 4.0 as the latest performance-boosting update to this open-source compressor...

How movie posters inspire engagement on our open source team Stefan Mattejiet Fri, 07/22/2022 - 03:00 Register or Login to like Register or Login to like

For the past several years, Design Thinking has been providing a way to enhance problem solving within teams, to ensure learning goals are met, and to increase team engagement. In our previous article, we discussed the problem with processes. In this article, we're going to describe how we made work more engaging.

The problem with engagement

We reached a point in our planning that we were able to articulate information about the upcoming pieces of work our team could take on. We solicited feedback from various stakeholders that represented different viewpoints, but we had no way to converse about the work properly to one another. It was all a one-way information exchange, with presentations and slides being spoken to a group of people, but not with a group of people. Worse still, it took hours to convey information.

The whole scenario felt forced and devoid of personality. Why would anyone want to take part, let alone enjoy, any aspect of our project? It was just another meeting in a cascade of meetings, during which most people probably did something else, while being talked at.

Something had to change, so we turned to Design Thinking to drum up some thoughts on how we could improve our process.

Design Thinking and Agile practices often advertise themselves as wonderful team and relationship building concepts. They can be, but as a team we had concentrated on the mechanics of Agile, and ended up with stiff, formal events that certainly got the job done, but curtailed any chance of creativity and natural conversation. After two quarterly planning cycles operating under our version of the "letter of the Agile Law" we knew there was a problem, and we wanted to fix it. Our next challenge was finding the right "fit".

We began by looking at our quarterly planning call itself. We asked ourselves whether this was really the best experience we could offer attendees of our quarterly planning events? These calls relied on participation and engagement from all parties to really make them a valuable tool to guide decisions. First and foremost, we wanted to get that without having to explain a massive shift in our way of doing things, or drowning people with explanations on our new methods. We decided to look through the lens of Design Thinking by putting the needs of our end users (the attendees of our calls) first. We asked ourselves: Were we in their position, would we come away from those calls feeling like we were involved in the decision making, or even that we enjoyed attending them? In short, the answer was no, we didn't believe we would.

[ Related read: 7 tips for giving and receiving better feedback ]

It was time to ask our attendees for some feedback on what they felt about how the sessions were being delivered, what value they derived from them. As is often the case when you ask questions like that, we didn't always get a great amount of feedback, or the feedback that we did get was vague. So we decided to make small incremental changes to our planning calls in an effort to increase engagement and to enable meaningful discussions. We would then garner feedback on these tweaks, and gauge the appetite for larger changes from our attendees as we progressed.

More great content Free online course: RHEL technical overview Learn advanced Linux commands Download cheat sheets Find an open source alternative Explore open source resources Incremental changes

First, we decided to change how we were demonstrating resourcing limitations per project to our stakeholders by reminding them that these projects all required real people, and weren't just numbers. Now we really did keep it simple here. In fact, all we did was add in some stick figures (dabbing, of course) that represented each team member so that people on the planning call could see exactly how many people each project needed. It was an instant hit.

Our stakeholders quickly appreciated something a little different to look at and it generated friendly, light conversation between participants. People were trying to guess which stick figure looked like who on the team (spoiler: they were all the same). After seeing how something so simple could instantly spark conversation, and even add a little fun into our calls, we knew we were on the right track. Time to make some real changes.

A picture is worth a thousand words, and at this point all we'd used were some stick figures. However, you can see how making a couple of small, simple changes can generate a positive impact.

Image by:

(Leigh Griffin, CC BY-SA 4.0)

You take a functional, but also kind of dull spreadsheet, add a bit of color, graphics, and a sprinkle of actual human language, and you end up with the kind of meeting that stands out amongst all of the others in people's calendars. This one is a little special. This one has a little bit more to it. Like the latest blockbuster movie that has people talking about it for days, this meeting ensures it has your full attention, and has you looking forward to seeing what happens in the sequels!

Image by:

(Leigh Griffin, CC BY-SA 4.0)

Movie posters

So the stick figures worked, uncomplicated language worked, the visuals worked. How could we build on this for an even better experience? The answer was closer at hand than we'd expected. One of our team members had some success using techniques and practices from the fantastic resource that is the Open Practice Library. We mentioned this free, community-built online resource in our first article. It was here we found the concept of a News Headlines, also known as Cover Stories, in which a project is broken down into key points, and is written in the style of a newspaper or magazine.

In one of the many brainstorming sessions we had reviewing the feedback, we landed on the idea of using movie posters for our cover stories. OK, truth be told we might have also been talking about the Oscars at the time, but it was a lightbulb moment and it instantly felt right. The creativity started flowing, and we began forming our project's movie posters for their upcoming "premiere" in the next quarterly planning call. The result? Uma Thurman in Kill Bill Vol. 2 capturing all you needed to know about upgrading two applications that run services based on status messages sent through other applications hooked into a larger database, critical for troubleshooting outages and performance issues. Obviously!

Image by:

(Leigh Griffin, CC BY-SA 4.0)

Here was a way to be creative in how our potential projects could be discussed and shared with our stakeholders, while still capturing all the key pieces of information. They still got the details about the work they would need to do, so they could form an opinion and reach a decision on what work holds the most value, and what deserves their time and resources. However, we wanted our team to have its own version of these cover stories, something that might resonate more with the people in our team.

In our next article, we'll talk about all the lessons we learned along the way.

Using Design Thinking, be creative in how potential projects can be discussed and shared with stakeholders, while still capturing all the key pieces of information.

Image by:

Image by Mapbox Uncharted ERG, CC-BY 3.0 US

Community management Careers Agile What to read next Put Design Thinking into practice with the Open Practice Library Build Design Thinking into your team processes This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. 91 points Waterford, Ireland

Product Owner on the Community Platform Engineering team at Red Hat from Waterford, Ireland and in my spare time I'm a retired showjumper but full time 'groom' for my son who has followed in my hoof-prints - ah, foot-prints!

| Follow aoifemoloney4 Open Enthusiast Author Contributor Club 489 points Waterford, Ireland

Leigh is an Engineering Manager and passionate about process improvement and researching new ways to approach problems. He is an accredited ICF Coach and has led several Agile transformations within Red Hat.

| Follow leighgriffin Open Minded Author Contributor Club Register or Login to post a comment.

Create conditional pipelines with CEL Camilla Conte Fri, 07/22/2022 - 03:00 Register or Login to like Register or Login to like

You just followed a guide to start your Tekton pipeline (or task) when a merge request is created or updated on your GitLab project. So you configured GitLab to send merge request events as webhooks. And you deployed some Tekton components:

• EventListener: receives webhooks from GitLab
• Trigger: starts your Pipeline every time the EventListener receives a new webhook from GitLab
• Pipeline: fetches the source code from GitLab and builds it

Then you notice that any event in your merge request (a new comment, a tag change) triggers the pipeline. That's not the behavior you desire. You don't need to build a comment or a tag, after all. You only want the pipeline to run when there is actual new code to build. Here's how I use Tekton's CEL Interceptor to create conditionals for my pipelines.

Have your trigger ready

I expect you have a trigger already defined. It's probably something similar to the snippet below.

The trigger's interceptor rejects anything that's not coming from a merge request. Still, the interceptor is not able to differentiate between code and non-code updates (like new comments).

apiVersion: triggers.tekton.dev/v1beta1
kind: Trigger
metadata:
  name: webhook-listener-trigger
spec:
  interceptors:
   # reject any payload that's not a merge request webhook
    - name: "filter-event-types"
      ref:
        name: "gitlab"
        kind: ClusterInterceptor
      params:
        - name: eventTypes
          value:
           - "Merge Request Hook"
  bindings:
    - ref: binding
  template:
    ref: templateAdd a CEL interceptor

Here comes the cel interceptor. This interceptor filters the webhook payload using the CEL expression language. If the filter expression evaluates to true, the pipeline starts.

Here I'm checking for the object_attributes.oldrev field to exist in the JSON body of the webhook payload. If object_attributes.oldrev exists, then that means this event is about a code change. If there wasn't a code change, there's no previous revision (oldrev) to refer to.

spec:
  interceptors:
    - name: "allow-code-changes-only"
      ref:
        name: cel
        kind: ClusterInterceptor
      params:
        - name: filter
          value: >
           has(body.object_attributes.oldrev)

Add the new interceptor to your trigger. Now your trigger looks like this:

apiVersion: triggers.tekton.dev/v1beta1
kind: Trigger
metadata:
  name: gitlab-listener-trigger
spec:
  interceptors:
    - name: "verify-gitlab-payload"
      ref:
        name: "gitlab"
        kind: ClusterInterceptor
      params:
        - name: eventTypes
          value:
           - "Merge Request Hook"
    - name: "allow-code-changes-only"
      ref:
        name: "cel"
        kind: ClusterInterceptor
      params:
        - name: filter
          value: >
           has(body.object_attributes.oldrev)
  bindings:
    - ref: binding
  template:
    ref: template

Deploy this new version of the trigger and enjoy the powers of automation. From now on, your pipeline only starts if there is some new code to build.

More on Kubernetes What is Kubernetes? Free online course: Containers, Kubernetes and Red Hat OpenShift technical over… eBook: Storage Patterns for Kubernetes Test drive OpenShift hands-on An introduction to enterprise Kubernetes How to explain Kubernetes in plain terms eBook: Running Kubernetes on your Raspberry Pi homelab Kubernetes cheat sheet eBook: A guide to Kubernetes for SREs and sysadmins Latest Kubernetes articles Tips

There are no limits to the conditions you can set in a CEL filter.

You may check that the merge request is currently open:

body.object_attributes.state in ['opened']

You can make sure the contributor finished their work on the code:

body.object_attributes.work_in_progress == false

You just have to concatenate multiple conditions correctly:

- name: filter
  value: >
   has(body.object_attributes.oldrev) &&
    body.object_attributes.state in ['opened'] &&
    body.object_attributes.work_in_progress == false

Check out the merge request events documentation to get inspired to write your own conditions.

You may need the CEL language definition to know how to translate your thoughts into code.

To evaluate types other than strings, you want to know the mapping between JSON and CEL types.

Control when automated builds happen in Tekton with CEL.

Kubernetes CI/CD What to read next This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.

The post Monit – A Open Source Tool for Managing and Monitoring Linux System first appeared on Tecmint: Linux Howtos, Tutorials & Guides .

Monit is a free open source and very useful tool that automatically monitors and manages processes, files, directories, checksums, permissions, filesystems, and services like Apache, Nginx, MySQL, FTP, SSH, SMTP, and so on in

The post Monit – A Open Source Tool for Managing and Monitoring Linux System first appeared on Tecmint: Linux Howtos, Tutorials & Guides.

The post How to Configure a CA SSL Certificate in HAProxy first appeared on Tecmint: Linux Howtos, Tutorials & Guides .

The HAProxy is a widely-used, reliable, high-performance reverse proxy, that offers high-availability and load balancing capabilities for TCP and HTTP applications. By default, it is compiled with OpenSSL, thus supporting SSL termination, enabling your

The post How to Configure a CA SSL Certificate in HAProxy first appeared on Tecmint: Linux Howtos, Tutorials & Guides.

Linux Distro Reviews: Desktop Environment Toolkits  WebProNews

In the previous articles we discussed how to assess, from a high level, whether a modernization effort made sense in your enterprise. We also covered the attributes a successful modernization team should have, and some team characteristics that might cause problems. At this point you might be thinking that starting a modernization project is a no-brainer.