If we could answer that question with a simple "yes" or "no," this would not be much of a story. Reality is a little more nuanced, though. An accurate answer begins with one of "Yes, but…" or "No, but…"—and the answer depends on who you ask, among other important variables, including industry, company size, and so forth.

On the "yes" front, IT job descriptions don’t typically buck the "degree required" assumption, sysadmin roles included. This fact is perhaps especially true in the corporate business world across a wide range of sectors, and it isn’t limited to large companies, either. Consider a recent opening posted on the jobs site Indeed.com for an IT system administrator position at Crest Foods, a 650-person food manufacturing company in Ashton, Ill. The description includes plenty of familiar requirements for a sysadmin. The first bullet point under "Desired Education & Experience" reads: "Bachelor’s degree in computer science, networking, IT, or relevant field."

"Generally, systems administrators will have [degrees] from four-year universities," says Jim Johnson, district president at the recruiting firm Robert Half Technology. While some employers don’t specify a particular degree field, Johnson notes the bachelor’s in computer information systems (CIS) as a good fit for the sysadmin field and overlapping IT roles.

That said, Johnson also points out that there are other options out there for people that don’t pursue a traditional degree path. That’s especially true given the growth of online education and training, as well as in-person opportunities such as technical schools.

"There are [sysadmins] with computer systems professional or computer operator certificates from technical or online schools," Johnson says.

Moreover, a potential employer’s "desired" educational background can be just that: An ideal scenario, but not a dealbreaker. This fact can be true even if a degree is listed as "required," perhaps especially in markets with a tight supply of qualified candidates. If you’ve got the technical chops, a degree might become much more optional than a job description might lead you to believe.

In addition to this, there are some “special” moments, such as Thanksgiving and the nearby days that, by now, have become a widespread event even beyond the countries where they used to be celebrated. Probably, in the data-centers in areas where those festivities are celebrated (or at least where the capitalistic part of the celebration is celebrated), the load reaches the annual peak, due to the e-commerce websites.

To make the situation even worst, many Cloud customers are rewriting and improving their applications, making them more cloud-native. Now, you’ll wonder how cloud-native applications can make things worse? The reason is very simple: the cloud-native applications scale. This means that during the off-peak season the applications will drastically reduce their footprint, creating the false feeling of resource abundancy.

This situation creates some problems, in my opinion.

First of all, since it’s very hard for the Public Cloud provider to estimate the load - and in the future, it will be even harder - we will have to live with frequent resource exhaustion in public clouds, which will make a single-cloud single-region application fragile. This will be true, not even considering the economic aspect of the problem. There will be situations where it will not be economically convenient for the Cloud Provider to provision enough resources to manage the peaks since the additional provisioning cost would not be repaid during the short periods those resources will be used.

Our legacy Linode Manager will be decommissioned on January 31, 2020. After that time, you will be automatically redirected to the Cloud Manager when logging in to manage your infrastructure on Linode.

David Egts, chief technologist of Red Hat's (NYSE: RHT) North American public sector business, has said that open-source procedures can help organizations meet digital transformation goals while promoting mobility and addressing a skills gap.

In a Fedscoop interview posted Monday, Egts noted that Red Hat’s Open Innovation Labs works with government customers to help them reduce workload processing time through new software development methods.

Red Hat invests heavily in open source communities, offering our employees' time and skills in many upstreams to advance the pace of innovation and support our customers' interests. And when Red Hat purchases a company, it ensures that any proprietary software becomes available as open source. For instance, just this month, Red Hat shared Quay, the formerly proprietary container registry and security scanner software, as an open source upstream available to all.

[...]

Awareness of open source in the Middle East is growing in many sectors, particularly in the telecommunications sphere. As operators seek to evolve from physical to digital players, open source ecosystems and solutions are being implemented to optimise and simplify operations, reduce costs, and facilitate digital transformation agendas. From Egypt, Saudi Arabia, and the UAE, to everywhere in between, open source solutions are being unlocked as cost-effective, flexible, reliable, secure, and alternative foundational systems to drive innovation and digital transformation. For telecommunications organisations, open source will enable improved delivery of digital services, the ability to introduce new digital services faster, and the capabilities to leverage insights from data to create new revenue streams.

The film, produced by IBM and directed by Austin Peck, centers on the increasing incidents of the devastation of natural disasters, and a cadre of coders who've dedicated their attentions and tech talent to help facilitate and expedite the responders' response to natural disasters. The social-activist developers serve as a frontline defense against some of the society-at-large greatest dangers.

The Kubernetes with OpenShift World Tour is a series of in-person workshops around the globe that help you build the skills you need to quickly modernize your applications. This World Tour provides a hands-on experience and teaches the basics of working with the hybrid-cloud, enterprise container platform Red Hat® OpenShift® on IBM Cloud™. You learn coding skills in the world of containerized, cloud-native development with expert developer advocates, who have deep technical experience building cloud microservices and applications with Red Hat OpenShift.

Moore and his team of open source developers work with open source communities such as the Apache Software Foundation, Linux Foundation, eClipse, OSGi, OpenStack, Cloud Foundry, Docker, JS, Node.js and more.

Next to this, Linux based servers have proved to be stable and capable of handling numerous requests at the time. Because no one wants a site that crashes when visitors are trying to get to it. It can be very annoying and bad for business. Linux has a very dedicated community and on the various forums, you can find useful information in dealing with a certain problem that you may encounter.

If Amazon's numbers are accurate, Graviton2 should deliver a big performance boost for Amazon's ARM Linux cloud potential. Graviton2 processors are 7nm designs making use of Arm Neoverse cores. Amazon says they can deliver up to seven times the performance of current A1 instances, twice the FP performance, and support more memory channels as well as doubling the per-core cache.

AWS has been working with operating system vendors and independent software vendors to help them release software that runs on ARM. ARM-based EC2 instances support Amazon Linux 2, Ubuntu, Red Hat, SUSE, Fedora, Debian and FreeBSD. It also works with multiple container services (Docker, Amazon ECS, and Amazon Elastic Kubernetes Service).

We launched the first generation (A1) of Arm-based, Graviton-powered EC2 instances at re:Invent 2018. Since that launch, thousands of our customers have used them to run many different types of scale-out workloads including containerized microservices, web servers, and data/log processing.

Last year Amazon introduced their first 64-bit Arm-based ECS2 “A1” instances which were found to deliver up to 45% cost savings over x86 Instances for the right workloads.

With Braket, developers can get started on building quantum algorithms and basic applications and then test them in simulations on AWS, as well as the quantum hardware from its partners. That’s a smart move on AWS’s part, as it’s hedging its bets without incurring the cost of trying to build a quantum computer itself. And for its partners, AWS provides them with the kind of reach that would be hard to achieve otherwise. Developers and researchers, on the other hand, get access to all of these tools through a single interface, making it easier for them to figure out what works best for them.

The official release of version 3.0 of the Helm package manager for Kubernetes is designed to make it easier for IT organizations to discover and securely deploy software on Kubernetes clusters more easily.

Taylor Thomas, a core contributor to Helm who is also a software developer for Nike, says for the last year the committee that oversees the development of Helm under the auspices of the Cloud Native Computing Foundation (CNCF) has been structuring the package manager to rely more on the application programming interfaces (APIs) that Kubernetes exposes to store records of installation. Helm Charts, which are collections of YAML files describing a related set of Kubernetes resources, now can be rendered on the client, eliminating the need for the Tiller resource management tool resident in the previous release of Helm that ran on the Kubernetes cluster.

In addition to providing a more secure way to render Helm Charts, Thomas says this approach provides a more streamlined mechanism for packaging software using Helm. Helm 3.0 also updates Helm Charts and associated libraries.
Additionally, a revamped Helm Go software development kit (SDK) is designed to make Helm more accessible, with the aim of sharing and reusing code the Helm community has open-sourced with the broader Go community, says Thomas.

Last year, we introduced Gardener in the Kubernetes Community Meeting and in a post on the Kubernetes Blog. At SAP, we have been running Gardener for more than two years, and are successfully managing thousands of conformant clusters in various versions on all major hyperscalers as well as in numerous infrastructures and private clouds that typically join an enterprise via acquisitions.

We are often asked why a handful of dynamically scalable clusters would not suffice. We also started our journey into Kubernetes with a similar mindset. But we realized that applying the architecture and principles of Kubernetes to productive scenarios, our internal and external customers very quickly required the rational separation of concerns and ownership, which in most circumstances led to the use of multiple clusters. Therefore, a scalable and managed Kubernetes as a service solution is often also the basis for adoption. Particularly, when a larger organization runs multiple products on different providers and in different regions, the number of clusters will quickly rise to the hundreds or even thousands.

Today, we want to give an update on what we have implemented in the past year regarding extensibility and customizability, and what we plan to work on for our next milestone.