Language Selection

English French German Italian Portuguese Spanish

SUSE

SUSE/OpenSUSE leftovers

Filed under
SUSE
  • Wrapping Up a Decade of Synergistic Technology

    What a decade! Thinking back to 2009, it?s obvious that so much has changed ? and so fast! Not surprisingly, technology is at the forefront of everything. But it?s not confined to just one branch or field of advancement. The 2010s can rightly be characterized as a decade of technological synergy. An era of overlapping and interdependent technologies where the combined effect and impact is greater than the sum of the individual elements.

    [...]

    As we finish one decade and start on a new one, it’s natural to speculate about what’s coming next. But as always, the future is difficult to predict. Sometimes, we don’t become aware of paradigm shifts or radical changes until they are in progress, or maybe even for a while after they have happened.

    Even so, one thing is beyond doubt. All the dominant industry trends involve interconnected, converging and synergistic technologies. In such a collaborative environment, the open source model is an indispensable and crucial element. It has become the “secret source” driving so much of the technological advancement and progress around us.

  • openSUSE Heroes: Piwik -> Matomo

    You might know that Piwik was renamed into Matomo more than a year ago. While everything is still compatible and even the scripts and other (internal) data is still named piwik, the rename is affecting more and more areas. Upstream is working hard to finalize their rename - while trying not to break too much on the other side. But even the file names will be renamed in some future version.

    Time - for us - to do some maintenance and start following upstream with the rename. Luckily, our famous distribution already has matomo packages in the main repository (which currently still miss Apparmor profiles, but hey: we can and will help here). So the main thing left (to do) is a database migration and the adjustments of all the small bits and bytes here and there, where we still use the old name.

  • How the Internet of Things (IoT) will drive adoption of Software Defined Storage

    Real world IoT use cases are everywhere. There are those we are familiar with as consumers: the app-controlled central heating system that sends household fuel consumption data to gas and electricity providers; the telemetry devices in the cars of inexperienced drivers, which report speed, location and journey duration data to the insurer; and the smart watch that records our sleep patterns, exercise workouts and our heart rate. Then there are those we are becoming familiar with as employees: the cameras that count us in and out of the workplace, manage security in retail outlets, or examine and optimise our journeys around a warehouse, and check ‘real’ stock levels vs the ERP count.

Red Hat, IBM and Fedora's Kernel

Filed under
Red Hat
SUSE
  • CodeReady Workspaces devfile, demystified

    With the exciting advent of CodeReady Workspaces (CRW) 2.0 comes some important changes. Based on the upstream project Eclipse Che 7, CRW brings even more of the “Infrastructure as Code” idea to fruition. Workspaces mimic the environment of a PC, an operating system, programming language support, the tools needed, and an editor. The real power comes by defining a workspace using a YAML file—a text file that can be stored and versioned in a source control system such as Git. This file, called devfile.yaml, is powerful and complex. This article will attempt to demystify the devfile.

  • Building freely distributed containers with Podman and Red Hat UBI

    DevNation tech talks are hosted by the Red Hat technologists who create our products. These sessions include real solutions and code and sample projects to help you get started. In this talk, you’ll learn about building containers with Podman and Red Hat Universal Base Image (UBI) from Scott McCarty and Burr Sutter.

    We will cover how to build and run containers based on UBI using just your regular user account—no daemon, no root, no fuss. Finally, we will order the de-resolution of all of our containers with a really cool command. After this talk, you will have new tools at the ready to help you find, run, build, and share container images.

  • Backfitting SLES 12 for IBM z15 – It’s in Our DNA

    For 20 years, SUSE has partnered with IBM to advance Linux on Z. From the early days of the IBM Linux Tech Center to an elaborate open source ecosystem, you might say that supporting IBM Z is part of our DNA.
    Several months ago, SUSE included support for the newly announced IBM z15 and IBM LinuxONE III systems as part of SLES 15. Now, with SUSE Linux Enterprise Server for IBM Z and LinuxONE 12 SP5, we are backfitting all the latest IBM Z support for pervasive encryption and more.
    The latest IBM z15 system is designed to support your mission-critical initiatives and allow you to be innovative as you design and scale your environment. Combined with SUSE Linux Enterprise Server for IBM Z and LinuxONE, these state-of-the-art systems provide an ultra-secure data serving platform to support the global economic growth we are seeing today.

  • Contribute at the Fedora Test Week for Kernel 5.4

    The kernel team is working on final integration for kernel 5.4. This version was just recently released, and will arrive soon in Fedora. This version has many security fixes included. As a result, the Fedora kernel and QA teams have organized a test week from Monday, December 09, 2019 through Monday, December 16, 2019. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.

Leftovers: Fedora, SUSE and Programming

Filed under
Development
SUSE
Misc
  • Updated NeuroFedora Computational Neuroscience ISO image available

    We've been working on making more software available in NeuroFedora. Neuron is now built with IV support, so models from ModelDB that use these should now be runnable using NeuroFedora.

    The Computational Neuroscience ISO image has been updated to include these improvements. After receiving some feedback, we've also added Julia and R to the image. The new version, 20191201, is available for download here. The checksum file is also provided. So please test your download for correctness before you proceed to use it.

  • Time needed to dist-upgrade Fedora

    Every couple of months I upgrade my main home computer to the latest Fedora. As this process is not instantaneous, this means some time without internet, wifi, smart home controls etc. This time I decided to measure how long it takes exactly.

    Hardware is mid-range home server: Core i5 CPU, 16GiB of RAM, storage is 2x HDD in btrfs raid1, over LUKS, bcached on NVMe drive.

  • SUSE Revives Patches For Exposing /proc/cpuinfo Data Over Sysf

    Back in 2017 were patches for exposing /proc/cpuinfo data via sysfs for more easily parsing selected bits of information from the CPU information output. That work never made it into the mainline kernel but now SUSE's Thomas Renninger is taking over and trying to get revised patches into the kernel.

    Renninger sent out revised versions of the "sysfs-based cpuinfo" on Friday that within /sys/devices/system/cpu/cpuX/info/ would expose nodes to easily parse pieces of cpuinfo like bogomips, cpu_family, flags, model, model_name, stepping, vendor_id, and more. Reading the information via sysfs with a single-value-per-file makes it much easier for parsing compared to having to parse the entire /proc/cpuinfo output and complements other CPU information already accessible via the very convenient sysfs.

  • Do's and Don'ts of implementing a hamburger menu

    The infamous hamburger menu is one of the examples where I see bad practice very often. Surf the web one day using a screen reader or using only your keyboard and you will most likely experience some of the problems as well. Let's have a look at the most common errors and how to avoid them.

  • The GCC Git Conversion Heats Up With Hopes Of Converting Over The Holidays

    Decided back at the GNU Tools Cauldron was a timeline to aim converting from Subversion as their default revision control system to Git over the New Year's holiday. For that to happen, by the middle of December they wanted to decide what conversion system to use for bringing all their SVN commits to Git. As such, now it's heating up ahead of that decision.

    Eric S Raymond announced the conversion work in progress. Right now he's been working on addressing the remaining problems with Reposurgeon in being able to convert the GCC SVN repository to Git. Following those lingering issues being resolved, he's seeking broader review of the Reposurgeon "recipe" and then "the conversion progress starts to become desirable."

  • PyGotham 2019 Speaker Coaching Recap

    I’m one of the organizers for PyGotham, the yearly Python programming conference in New York City. This year thirteen PyGotham speakers received training from opera singer and speaking coach Melissa Collom, paid for by the conference and free for the speakers. Eight of the speakers were new to the conference scene; Melissa helped them focus on delivering value to their audience, structuring their talks clearly, and speaking with conviction. All the speakers who responded to a survey said they felt more confident and they were more likely to propose conference talks again.

    Here’s what some of our speakers said:

    “Melissa helped me pick out the areas I needed to improve, that I could work on for maximum impact in the limited time that I had before the conference. More importantly, she told me what she thought were my strengths and it helped me immensely to know what I had working for me.”

    “It was fun and Melissa made me feel comfortable to be myself! She brought out the best in me. The positive and constructive feedback was helpful and provided in a supportive way.”

  • Marco Zehe: The myth of getting rich through ads

    In addition, the web hosting was expensive, but not really performant. And they often let essential software get out of date. My WordPress at some point had started complaining because my PHP version was too old. Turned out that the defaults for shared hosts were not upgraded to a newer version by default by the hoster, and one had to go into an obnoxious backend to fiddle with some setting somewhere to use a newer version of PHP.

    I then decided to try something completely new. I exported the contents of my three blogs and set up blogs at WordPress.com, the hosted WordPress offering from the makers themselves: Automattic. I looked at their plans, and the Premium plan, which cost me 8€ per month, per blog felt suitable. I also took the opportunity to pull both German language blogs together into one. I just added two categories that those who just want to see my tecnical stuff, or the private stuff, could still do so.

    With that move, I got a good set of features that I would normally use on a self-hosted blog as well, so I set up some widgets, some theme that comes with the plan, and imported all my content including comments and such. I lost my statistics from the custom plugins, but hey, I had lost years of statistics from before that when I decided to no longer use JetPack on my self-hosted blogs, too, so what.

    And I did two more things. I added a “Buy me a coffee” button so people could show their appreciation for my content if they wanted to. And I opted into the Word Ads program, that would display some advertisement on the blog’s main page and below each individual post. I simply wanted to see if my content would be viable enough to generate any significant enough income.

    [...]

    When I compare my experience to that of my wife, who runs both a guide and a forum for the popular Sims FreePlay game in Germany, it is clear that even she with her thousands of visitors to both the guide and forum does not always generate enough traffic to get the minimum Google Adsense payout threshold per month. And that is just enough to cover her monthly domain and server costs, because the traffic is so heavy that shared hosting cannot cope. So she has to run a dedicated v server for those, which are way more expensive than shared hosting.

    So, ads on the web are really not a sustainable model for many. Yes, there may be some very popular and widespread 8content-wise) blogs or publication sites that do generate enough revenue through ads. But the more niche your topic gets, if you don’t generate thousands of visitors per month, ads sometimes may cover the costs of a service like WordPress to run your blog, but only if you are on one of the lower plans with less control over what your blog can do or the ads that are being displayed.

    I believe that a more engaged interaction with the actual audience is a better way to generate revenue, although that, of course, also depends on readers loyalty and your own dedication. I think that initiatives like Grant For The Web are the future of monetisation of content on the web, and I may start supporting that once my move back to self-hosting is complete. I’ll keep you posted.

OpenSUSE: New Local Build Environment Features and Highlights of YaST Development Sprint

Filed under
SUSE
  • New Local Build Environment Features

    We have just created osc 0.167 release which focuses on the local build functionality. It is way easier now to deal with VM builds (eg. inside of KVM) and also building for foreign hardware architecture becomes way easier now.

  • Highlights of YaST Development Sprint 90

    As usual, during this sprint we have been working on a wide range of topics. The release of the next (open)SUSE versions is approaching and we need to pay attention to important changes like the new installation media or the /usr/etc and /etc split.

SUSE/OpenSUSE: SUSE Doc Day at SUSECON 2020, OpenSUSE Board Election and More

Filed under
SUSE
  • Yes We Do it Again: SUSE Doc Day at SUSECON 2020

    A Doc Day is a time when a group of people gathers to collaborate on writing documentation on one or more given topics. The main premise for our Doc Day is to get a group of interested people – YOU – in a room together and have you work towards shared goals. To help you feel more comfortable, we will give a short overview of our documentation, how we usually work, and how you can contribute.
    Of course, you cannot write entire manuals or guides in one single day. But you can help us to improve existing documentation by reviewing, editing and updating it. In addition, we will use the Doc Day to kick-off the creation of new guides and papers for topics that you think are not yet covered (well enough).

  • openSUSE Board election 2019-2020 – Call for Nominations, Applications

    Two seats are open for election on the openSUSE Board. Gertjan Lettink completed his second term. Simon Lees completed his first term and thus he is eligible to run as a Board candidate again should he wish to do so.

  • status.opensuse.org updated

    Our infrastructure status page at https://status.opensue.org/ is using Cachet under the hood. While the latest update brought a couple of bugfixes it also deprecated the RSS and Atom feeds, that could be used to integrate the information easily in other applications.

    While we are somehow sad to see such a feature go, we also have to admit that the decision of the developers is not really bad - as the generation of those feeds had some problems (bugs) in the old Cachet versions. Instead of fixing them, the developers decided to move on and focus on other areas. So it's understandable that they cut off something, which is not in their focus, to save resources.

  • SSL cipher updates

    Sometimes it's a good idea to follow best practices. This is what we did by following the recommendations for "general-purpose servers with a variety of clients, recommended for almost all systems" from https://ssl-config.mozilla.org/.

Tumbleweed Snapshots Rate Top-Notch, Get Krita, QEMU, Mesa Updates

Filed under
SUSE

Closing out the month, there were two snapshots with version upgrades and one snapshot (20191127) that produced some minor changes to a couple Advanced Linux Sound Architecture (ALSA) packages.

The first Tumbleweed snapshot for December arrived with the 20191202 snapshot. Updated were also made to ALSA with the update of the 1.2.1.1 versions of alsa-plugins, alsa-utils and asla, which dropped 25 patches and fixed regressions for the UCM parser. GNOME had several package updates for gedit, evolution and more. The 3.34.2 version of gnome-software fixed a potential threading crash when using flatpak and had an upstream fix for fwupd. An updated version of ModemManager 1.12.0, which is a DBus-activated daemon that controls mobile broadband devices and connections, had a large amount of improvements and changes to include adding support for Mobile Station Based Assisted-GPS in addition to Mobile Station Assisted Assisted-GPS. Revision control tool mercurial 5.2 made some backwards compatibility changes and added some new feature extensions with its quarterly release. The update of perl 5.30.1 triggered an issue recorded on the snapshot reviewer because the newer version and patch that came in it is problematic for embedded Perl usage. Several other packages were updated in the snapshot to include qemu 4.1.93, re2 20191101, xen and xorg-x11-server. The one major version change in the snapshot was an update to terminal multiplexer tmux 3.0a; the major release that allows its users to easily switch between several programs in one terminal offers new features like added support for the SD (scroll down) escape sequence and for underscore colors.

Read more

More OpenSUSE: Etherpad updated

News About Servers (SUSE, Ubuntu, Red Hat and More)

Filed under
Server
SUSE
  • What is Cloud Native?

    Cloud native is more than just a buzzword, though. It's an approach used by some of the largest organizations on the planet, including Walmart, Visa, JP Morgan Chase, China Mobile, Verizon and Target, among others. Cloud native is an approach that enable developers and organization to be more agile, providing workload portability and scalability.

  • What is Kata Containers and why should I care?

    Kata Containers can significantly improve the security and isolation of your container workloads. It combines the benefits of using a hypervisor, such as enhanced security, and container orchestration capabilities provided by Kubernetes.

    Together with Eric Erns from Intel, we have recently performed a webinar in which we presented the benefits of using Kata Containers in a Charmed Kubernetes environment. In this blog, we aim to highlight the key outcomes from this webinar.

  • An idiot's guide to Kubernetes, low-code developers, and other industry trends

    As part of my role as a senior product marketing manager at an enterprise software company with an open source development model, I publish a regular update about open source community, market, and industry trends for product marketers, managers, and other influencers. Here are five of my and their favorite articles from that update.

  • A blueprint for OpenStack and bare metal

    The bare metal cloud is an abstraction layer for the pools of dedicated servers with different capabilities (processing, networking or storage) that can be provisioned and consumed with cloud-like ease and speed. It embraces the orchestration and automation of the cloud and applies them to bare metal workload use cases.

    The benefit to end users is that they get access to the direct hardware processing power of individual servers and are able to provision workloads without the overhead of the virtualization layer—providing the ability to provision environments in an Infrastructure-as-code methodology with separation of tenants and projects.

  • Software Development, Microservices & Container Management – Part III – Why Kubernetes? A Deep Dive into Kubernetes world

    Together with my colleague Bettina Bassermann and SUSE partners, we will be running a series of blogs and webinars from SUSE (Software Development, Microservices & Container Management, a SUSE webinar series on modern Application Development), and try to address the former questions and doubts about K8s and Cloud Native development and how it is not compromising quality and control.

  • Epic Performance with New Tuning Guide – SUSE Linux Enterprise Server on AMD EPYC* 7002 Series Processors

    EPYC is AMD’s flagship mainstream server microprocessors and supports 1-way and 2-way multiprocessing. The first generation was originally announced back in May 2017 and replaced the previous Opteron server family with the introduction of the Zen microarchitecture for the mainstream market.

  • Content Lifecycle Management in SUSE Manager

    Content Lifecycle management is managing how patches flows through your infra in a staged manner. In ideal infra, latest patches will always be applied on development servers. If everything is good there then those patches will be applied to QA servers and lastly to production servers. This enables sysadmins to catch issues if any and hence preventing patching of prod system which may create downtime of live environments.

    SUSE Manager gives you this control via content lifecycle. In this, you create custom channels in SUSE Manager for example dev, qa and prod. Then you register your systems to those channels according to their criticality. Now whenever channels gets the new patches it will be available to respective systems (registered to those channels) to install. So if you control channels you control the patch availability to systems.

    In content lifecycle management, suse manager enables you to push patches to channels manually. Like on first deploy all latest patches will be available to dev channels and hence dev systems. At this stage, if you run update commands (zypper up, yum update) they will show latest patches only on dev servers. QA and prod servers wont show any new patches.

  • The Early History of Usenet, Part VII: Usenet Growth and B-News

    For quite a while, it looked like my prediction — one to two articles per day — was overly optimistic. By summer, there were only four new sites: Reed College, University of Oklahoma (at least, I think that that's what uucp node uok is), vax135, another Bell Labs machine — and, cruciallyy, U.C. Berkeley, which had a uucp connection to Bell Labs Research and was on the ARPANET.

    In principle, even a slow rate of exponential growth can eventually take over the world. But that assumes that there are no "deaths" that will drive the growth rate negative. That isn't a reasaonable assumption, though. If nothing else, Jim Ellis, Tom Truscott, Steve Daniel, and I all planned to graduate. (We all succeeded in that goal.) If Usenet hadn't shown its worth to our successors by then, they'd have let it wither. For that matter, university faculty or Bell Labs management could have pulled the plug, too. Usenet could easily have died aborning. But the right person at Berkeley did the right thing.

    Mary Horton was then a PhD student there. (After she graduated, she joined Bell Labs; she and I were two of the primary people who brought TCP/IP to the Labs, where it was sometimes known as the "datagram heresy". The phone network was, of course, circuit-switched…) Known to her but unknown to us, there were two non-technical ARPANET mailing lists that would be of great interest to many potential Usenet users, HUMAN-NETS and SF-LOVERS. She set up a gateway that relayed these mailing lists into Usenet groups; these were at some point moved to the fa ("From ARPANET") hierarchy. (For a more detailed telling of this part of the story, see Ronda Hauben's writings.) With an actual traffic source, it was easy to sell folks on the benefits of Usenet. People would have preferred a real ARPANET connection but that was rarely feasible and never something that a student could set up: ARPANET connections were restricted to places that had research contracts with DARPA. The gateway at Berkeley was, eventually, bidirectional for both Usenet and email; this enabled Usenet-style communication between the networks.

openSUSE Leap 15.0 Reached End of Life, Upgrade to openSUSE Leap 15.1 Now

Filed under
SUSE

The openSUSE Leap 15.0 operating system release has reached end of life on November 30th, 2019, which was the last day when it received software updates and security patches.
openSUSE Leap 15.0 was released 18 months ago, on May 25th, 2018, and it was based on the SUSE Enterprise Linux 15 operating system series. It was the first OpenSuSE Leap release to adopt a new versioning scheme that's in sync with upstream SUSE Enterprise Linux (SLE) releases.

As of November 30th, 2019, openSUSE Leap 15.0 will no longer receive software updates and security patches for its core components or apps. Therefore, users are encouraged upgrade their computers as soon as possible to the latest version, openSUSE Leap 15.1, which will be supported with software updates and security patches until November 2020.

"openSUSE Leap 15.0 will receive no further maintenance or security updates after that date. It is recommended for openSUSE Leap users to upgrade to the current release openSUSE Leap 15.1. The next release, openSUSE Leap 15.2, is planned for May 2020." said Marcus Meissner, SUSE Security and openSUSE Maintenance.

Read more

Red Hat, IBM and SUSE

Filed under
Red Hat
SUSE
  • Raytheon Leans on Red Hat to Advance DevSecOps

    Jon Check, senior director for cyber protection solutions for Raytheon Intelligence, Information and Services, said Raytheon has developed a set of DevSecOps practices for organizations building applications deployed in highly secure environments, involving government contracts.

    Raytheon and these customers have been challenged by a chronic shortage of IT professionals with the appropriate level of clearance to work on these classified projects. To overcome that issue, Check said Raytheon developed what it describes as a “code low, deploy high” approach to DevSecOps. Developers who lack security clearances can still build applications; however, those applications can only be deployed by IT professionals having the appropriate security clearance.

    In addition, Check said Raytheon has developed integrations between its DevSecOps framework and various IT tools based on the ITIL framework, which so many IT operations teams depend on to foster collaboration across the application development and deployment process. For example, he said, whenever code gets checked into a repository, an alert can be sent to an IT service management application from ServiceNow.

  •                    

  • [Older] IBM: ‘Mac users are happier and more productive’ [iophk: duh]

                         

                           

    IBM CIO Fletcher Previn talked up fresh IBM findings that show those of its employees who use Macs are more likely to stay with IBM and exceed performance expectations compared to [Windows] users.

  •                    

  • [Older] IBM: Mac users perform better at work and close larger high-value sales compared to [Windows] users

                         

                           

    Today, IBM announced some major news showing the benefits of using a Mac over a [Windows machine] at work. According to IBM research, there are 22% more macOS users who exceed expectations in performance reviews compared to Windows users. High-value sales deals also tend to be 16% higher for Mac users compared to [Windows] users.

  •                    

  • [Older] IBM: Our Mac-Using Employees Outperform Windows Users in Every Way

                         

                           

    According to IBM, one staff member can support 5,400 Mac users, while the company needed one staff member per 242 [Windows] users. Only 5 percent of Mac users called the help desk for assistance, compared with 40 percent of [Windows] users. This Mac-IBM love affair has been ongoing for a few years, and the same IBM PR points out that in 2016, IBM CIO Fletcher Previn declared that IBM saves anywhere from $273 to $543 when its end users choose Mac over [Windows].

  • Centiq receives highest SUSE Solution Partner certification to bolster best-in-class enterprise cloud application migration and implementation expertise for SAP projects
  • Noop now named none

    Lately more and more people approached me with saptune warnings regarding ‘noop’ being an invalid scheduler.
    With new Servie Packs we see a transition from non-multiqueue schedulers (noop, cfq, deadline) to multiqueue schedulers (none, mq-deadline, bfq, kyber).
    This transition will be finished with kernel 5.x (SLES 15 SP2). Only multiqueue schedulers will remain.
    Even if you do not have upgraded lately, new hardware like NVMe’s can come with multiqueue support only.

SUSE/OpenSUSE Development Report

Filed under
SUSE
  • openSUSE Tumbleweed – Review of the week 2019/47

    Another week, in which openQA did block some of the snapshots – and some issues it was unfortunately not able to see. Anyway, during the week 2019/47 we have released three snapshot into the wild (1116, 1118 and 1119), containing those changes:

    Mesa 19.2.4: fixes critical rendering issues from earlier Mesa 19.2.3. As this rendering issue did not happen on all graphics adapters, openQA had no chance of spotting it
    Linux kernel 5.3.11
    KDE Plasma 5.17.3
    Subversion 1.13.0
    binutils 2.33.1

  • YaST Team: Highlights of YaST Development Sprints 88 and 89

    A few weeks ago, we wrote about the new ItemSelector widget that is finding its way into YaST user interfaces. It turned out that just a simple on/off status is not enough in some cases, so we had to extend that concept. For example, software modules may have dependencies, and we want to show the difference between one that was explicitly selected by the user and one that was auto-selected because some other software module requires it.

    This kind of shook the foundations of the underlying classes; all of a sudden a bit is no longer just a bit, but it needs to be broken down into even smaller pieces. Well, we cheated; we now use integer values instead. Most of the class hierarchy still only uses 0 and 1, but the new YCustomStatusItemSelector also supports using higher numbers for application-defined purposes.

    For each possible status value, the application defines the name of the icon to be displayed (for graphical UIs like the Qt UI), the text equivalent (for text mode / the NCurses UI), and an optional nextStatus which tells the widget what status to cycle to when the user changes the status of an item with a mouse click or with the keyboard. A value of -1 lets the application handle this.

    So this is not a one-trick-pony that is useful only for that one use case (the software modules), but a generic tool that might find good uses in other places all over YaST as well.

Syndicate content

More in Tux Machines