Language Selection

English French German Italian Portuguese Spanish

SUSE and Red Hat Leftovers

Filed under
Red Hat
SUSE
  • Skuba on SUSE CaaS Platform 4

    With SUSE CaaS Platform 4 we heard our customers feedback and decided to change what the lifecycle of the platform looks like.

    Previous versions of SUSE CaaS Platform included an administrator node that despite being useful for managing the whole platform, was another component to take care of, and an extra machine to take into account when deploying the platform.

    This administrator node used Salt to set up and maintain the Kubernetes cluster among the different nodes comprising your cluster.

    During this time, your feedback has been that a little more flexibility on the deployment was appreciated, so you could experiment with slightly different setups, even if they were for proof of concepts while you were fleshing out the details of production clusters.

  • Kubernetes Rolling Update Strategy in our production infra

    Kubernetes rolling update strategy means suppose we are running pod (containers) in our live infra and we want to update new changes into our running pod like build update, confrontational changes etc. While deployment new pod with new changes suppose our containers got stuck or failed due to any reason.

    So, we have to redeploy old pod with old changes again to avoid downtime of our application. This complete process is called rolling update strategy in Kubernetes.

    Kubernetes rolling update strategy

    Before moving to next we should aware about new pod deployment strategy of Kubernetes means how many new pods it will deploy at a time without taking downtime. Because high availability of our website is our first priority. So, while deploying new pod Kubernetes will deploy 25% or you can say one fourth of the total pod. Suppose we are running four pods first it will terminate 25% of total pod means one pod. Then it will launch 25% new pod and so on.

  • Tackle OpenStack networking woes with SUSE OpenStack Cloud Crowbar

    By far, the most difficult aspect of successfully deploying OpenStack is getting the networking right, a challenge that has caused many a well-intentioned IT team to throw up its hands and toss in the towel. Fortunately, SUSE OpenStack Cloud removes much of that pain by automating most of the network deployment and dramatically simplifying custom network set-ups.

  • Grow your virtualization environments without breaking the bank

    An IT director at a large financial services company shares the benefits and cost reductions they’ve experienced by switching to Red Hat Virtualization. In just three years, it’s paved the way for an efficient, stable and cost-effective virtualization environment.

  • How to Handle OpenShift Worker Nodes Resources in Overcommitted State

    One of the benefits in adopting a system like OpenShift is facilitating burstable and scalable workload. Horizontal application scaling involves adding or removing instances of an application to match demand. When OpenShift schedules a Pod, it’s important that the nodes have enough resources to actually run it. If a user schedules a large application (in the form of Pod) on a node with limited resources , it is possible for the node to run out of memory or CPU resources and for things to stop working!

    It’s also possible for applications to take up more resources than they should. This could be caused by a team spinning up more replicas than they need to artificially decrease latency or simply because of a configuration change that causes a program to go out of control and try to use 100% of the available CPU resources. Regardless of whether the issue is caused by a bad developer, bad code, or bad luck, what’s important is how a cluster administrator can manage and maintain control of the resources.

    In this blog, let’s take a look at how you can solve these problems using best practices.

  • How the new Quarkus extension for Visual Studio Code improves the development experience

    Earlier this year, we were introduced to Quarkus, the next-generation, container-first framework for Java applications. As expected, such new frameworks and technologies make way for new developer tools focused on making the development experience even better.

    The recent Quarkus extension for Visual Studio Code release aims to do just that, by bringing features specific to Quarkus project development within VS Code. The new VS Code extension is dependent on a couple of Java extensions for VS Code, so it is recommended that you have the Java Extension Pack installed. This article outlines what the Quarkus extension for VS Code has to offer: convenient features for an already convenient Java framework.

More in Tux Machines

Open source technology, enabling innovation

One of the most exciting projects to come out of the open source revolution is Kubernetes, a tool helping companies running their software on cloud services. It enables them to get the most out of the processing power they’re paying for by identifying machines that are being underutilised. So, if the software detects that a machine is not being optimised, it will load it up with another task so it’s working as hard as it can. Read more

Forbes Raves Upcoming Linux Desktop will enclose Windows 10 and macOS

Forbes senior employee Jason Evangelho dedicated an entire article to an upcoming update for a Sino-domestic Linux distribution: If you haven't paid attention to a bit of Linux desktop distribution called Deepin, it's time to put it on your radar. Remember that Huawei Deepin chose to ship on their MateBook laptop lineup. Remember that Deepin Cloud Sync (for system settings) is a great, progressive feature that every Linux distro must use. Remember that the retractable control center from the future looks like something sexy and sensible. But looking at 2020, Deepin is absolutely breathtaking. This is without a doubt the nicest desktop environment I have ever seen … For me, the UX is more intuitive and pleasant than macOS and Windows 10. And luckily a quick setting can also transform Deepin into the traditional Windows or macOS desktop paradigm's that you are already familiar with. Hell, even the installer is a relief. Read more Also: Differences between Windows and Linux operating systems. The fundamental differences that are worth knowing

[libre-riscv-dev] power pc

So as you know, the RISCV Foundation is seriously impeding progress. There
is huge momentum around RISCV itself, however as far as open *innovation*
is concerned, the sheer arrogance of the Foundation in failing to respect
the combination of Libre goals and business objectives has us completely
isolated from key critical resources such as the closed secret lists and
wiki.

We cannot even get access to documentation explaining how to propose new
extensions.

I have been considering for some time to reach out to MIPS and PowerPC.
Yesterday I wrote to the OpenPower Foundation and was really surprised and
delighted to hear back from Hugh Blemings, whom I worked with over 20 years
ago.

I outlined some conditions (no NDAs, open mailing lists, use of
Certification Marks and Compliance Suites) and he replied back that this
was pretty much along the lines of what they were planning.

I will have a chat with him some time, in the meantime I found the spec:

https://openpowerfoundation.org/?resource_lib=power-isa-version-3-0

It is eeenooormous, however Hugh reassures me that they want to break it
into sections.

Why would we even consider this?

The lesson from RISCV is really clear: if the ISA is set up as a cartel,
Libre innovation is not welcome.

If we had a goal to just *implement* a *pre existing* Extension, there
would be no problem.

It is the fact that we wish to implement entirely new extensions, for CPU
and GPU *and* VPU purposes, but not as a separate processor (which would be
classified as "custom") that is the "problem".

So starting at page 1146, we need to work out how to shoe horn a ton of
stuff into the ISA, as well as fit 16 bit compressed in as well.

L.
Read more Also: Libre RISC-V Open-Source Effort Now Looking At POWER Instead Of RISC-V

Calamares grabs onto things

I’ve been working on Calamares, the Universal Linux Installer, for a little over two years – following up in the role Teo started. It’s used by Neon (for the dev version, not the user version) and Manjaro and lots of other Linux distributions. I’ve typically called it an installer for boutique distro’s, as opposed to the Big Five. Well, Debian 11 has plans. And lubuntu uses it as well (and has for over six months). Those seem pretty big. Read more