Language Selection

English French German Italian Portuguese Spanish

SUSE/OpenSUSE: Name Change, YaST, MicroOS and More

Filed under
SUSE
  • openSUSE project: vote on name change

    The openSUSE project informed it's members by mail to vote for a potential name change. The vote ends on 07.11.2019 at 23:59 UTC. In a Wiki article the openSUSE Board and Election Committee have gathered the most important arguments for and against a name change for all members.

  • Highlights of YaST Development Sprint 87

    As you may know, we have recently extended YaST to support additional encryption mechanisms like volatile encryption for swap devices or pervasive encryption for data volumes. You can find more details in our blog post titled "Advanced Encryption Options Land in the YaST Partitioner".

    Those encryption mechanisms offer the possibility of adjusting the sector size of the encryption layer according to the sector size of the disk. That can result in a performance boost with storage devices based on 4k blocks. To get the best of your systems, we have instructed YaST to set the sector size to 4096 bytes whenever is possible, which should improve the performance of the encrypted devices created with the recently implemented methods.

    Additionally, we took the time to improve the codebase related to encryption, based on the lessons we learned while implementing volatile and pervasive encryption. We also performed some additional tests and we found a problem that we are already fixing in the sprint that has just started.

  • toolbox - bring your own (debugging) utilities with you

    Our Container Host OS openSUSE MicroOS and our Kubernetes platform openSUSE Kubic are both using transactionl-update to apply patches to the system. This implies that a read-only root filesystem is used. While this has big advantages, like it allows to update a cluster automatically in a safe way, this has one drawback: you need to reboot to activate new installed packages. But what if you want to debug a problem and the utility you need is not installed? Who says, that the problem is still debuggable after a reboot?

  • Why software-defined storage is right for the hybrid cloud

    Beyond being an intermediate step, hybrid cloud isn’t particularly well defined. If you took a random selection of three CIOs, they’d each likely explain it differently. It’s a bit like asking three people to imagine a farmyard animal: one thinks “pig”, one thinks “hen” and the other thinks “cow”. All three are right, but all three are imagining something very different. The National Institute of Standards and Technology (NIST) have given us an official hybrid cloud definition but not everyone agrees that this is that helpful. Lauren Nelson, principle analyst at Forrester, described this definition as “far from reality”. We’re at the top of the hype cycle and Nelson was making a fair point: NIST’s definition calls for active bursting from one environment into another, and while most enterprises would see themselves as hybrid, cross environment bursting is in practice nearly as rare as real unicorns.

  • A “Silly Season Blog” – Have Fun with Sapstartsrv and Pacemaker

    This blog is about a funny integration of a plain Linux service into the SAP start framework sapstartsrv and SUSEs High Availability solution based on pacemaker. This solution is not intended to run in productive environments but should demonstrate how to integrate special services.

openSUSE community votes on name change – but not to what….

  • openSUSE community votes on name change – but not to what….

    The openSUSE project is in the midst of asking stakeholders to vote on a name change – though what the new name might be is not clear.

    The openSUSE community has recently been pondering whether to reconstitute itself as a new legal entity such as a foundation. This has prompted discussion over the status of the openSUSE name and trademarks – unsurprisingly given that SUSE and the SUSE logo are trademarks of SUSE LLC, the commercial company that champions the project and its open source operating system.

    The page detailing the vote gives a comprehensive list of reasons to keep the current name. These include the potential loss of brand recognition earned over years, and contributors’ attachment to the current name – and branding.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Server Leftovers

  • Knative at 1: New Changes, New Opportunities

    This summer marked the one-year anniversary of Knative, an open-source project that provides the fundamental building blocks for serverless workloads in Kubernetes. In its relatively short life (so far), Knative is already delivering on its promise to boost organizations’ ability to leverage serverless and FaaS (functions as a service). Knative isn’t the only serverless offering for Kubernetes, but it has become a de-facto standard because it arguably has a richer set of features and can be integrated more smoothly than the competition. And the Knative project continues to evolve to address businesses’ changing needs. In the last year alone, the platform has seen many improvements, giving organizations looking to expand their use of Kubernetes through serverless new choices, new considerations and new opportunities.

  • Redis Labs Leverages Kubernetes to Automate Database Recovery

    Redis Labs today announced it has enhanced the Operator software for deploying its database on Kubernetes clusters to include an automatic cluster recovery that enables customers to manage a stateful service as if it were stateless. Announced at Redis Day, the latest version of Kubernetes Operator for Redis Enterprise makes it possible to spin up a new instance of a Redis database in minutes. Howard Ting, chief marketing officer for Redis Labs, says as Kubernetes has continued to gain traction, it became apparent that IT organizations need tools to provision Redis Enterprise for Kubernetes clusters. That requirement led Redis Labs to embrace Operator software for Kubernetes developed by CoreOS, which has since been acquired by Red Hat. IT teams can either opt to recover databases manually using Kubernetes Operator or configure the tool to recover databases automatically anytime a database goes offline. In either case, he says, all datasets are loaded and balanced across the cluster without any need for manual workflows.

  • Dare to Transform IT with SUSE Global Services

Audiocasts/Shows: FLOSS Weekly and Linux Headlines

  • FLOSS Weekly 555: Emissions API

    Emissions API is easy to access satellite-based emission data for everyone. The project strives to create an application interface that lowers the barrier to use the data for visualization and/or analysis.

  • 2019-11-13 | Linux Headlines

    It’s time to update your kernel again as yet more Intel security issues come to light, good news for container management and self-hosted collaboration, and Brave is finally ready for production.

Bill Wear, Developer Advocate for MAAS: foo.c

I remember my first foo. It was September, 1974, on a PDP-11/40, in the second-floor lab at the local community college. It was an amazing experience for a fourteen-year-old, admitted at 12 to audit night classes because his dad was a part-time instructor and full-time polymath. I should warn you, I’m not the genius in the room. I maintained a B average in math and electrical engineering, but A+ averages in English, languages, programming, and organic chemistry (yeah, about that….). The genius was my Dad, the math wizard, the US Navy CIC Officer. More on him in a later blog — he’s relevant to what MAAS does in a big way. Okay, so I’m more of a language (and logic) guy. But isn’t code where math meets language and logic? Research Unix Fifth edition UNIX had just been licensed to educational institutions at no cost, and since this college was situated squarely in the middle of the military-industrial complex, scoring a Hulking Giant was easy. Finding good code to run it? That was another issue, until Bell Labs offered up a freebie. It was amazing! Getting the computer to do things on its own — via ASM and FORTRAN — was not new to me. What was new was the simplicity of the whole thing. Mathematically, UNIX and C were incredibly complex, incorporating all kinds of network theory and topology and numerical methods that (frankly) haven’t always been my favorite cup of tea. I’m not even sure if Computer Science was a thing yet. But the amazing part? Here was an OS which took all that complexity and translated it to simple logic: everything is a file; small is beautiful; do one thing well. Didn’t matter that it was cranky and buggy and sometimes dumped your perfectly-okay program in the bit bucket. It was a thrill to be able to do something without having to obsess over the math underneath. Read more Also: How to upgrade to Ubuntu 20.04 Daily Builds from Ubuntu 19.10

Intel is Openwashing With 'OpenVINO'