Nach der Ankündigung von Updates für die PostgreSQL-Datenbank haben wir Amazon RDS for PostgreSQL aktualisiert, um die PostgreSQL-Nebenversionen 11.6, 10.11, 9.6.16 und 9.5.20 zu unterstützen. Diese Version enthält Fehlerbehebungen und Verbesserungen durch die PostgreSQL-Community.
Quelle: aws.amazon.com
Ab heute unterstützt Amazon RDS for PostgreSQL die Größen 8xlarge und 16xlarge für die Instance-Klassen db.m5 und db.r5. Mit diesen neuen Instance-Größen steht Kunden, die derzeit entweder m4.10xlarge, m4.16xlarge, r4.8xlarge oder r4.16xlarge verwenden, eine unkomplizierte Upgrade-Möglichkeit auf die neueste Generation von Instances bereit.
Quelle: aws.amazon.com
One of the things we often assume with the Red Hat OpenShift platform, and with Kubernetes in general, is that our users have computing needs that always fit inside a standard cloud node. While this is definitely the case for most cloud-based applications, there are plenty of non-JavaScript-and-Redis style applications out there that still need to move into the cloud. Some enterprise applications were written before the cloud existed, and still others were created before JavaScript, C#, and Python even existed. Older systems written in languages, like PL/I and COBOL, can also benefit from the move to cloud, and from the use of containers, they just need a little extra attention to make the transition. Sometimes, they might need more specifically tailored environments than are available in the commodity-hardware-based clouds.
Or maybe, those systems need to also run extremely large, mission-critical databases, like IBM DB2. In order to unlock the true potential of a multi-cloud compute environment, that cloud software needs to run on a diverse array of hardware similar to what is already in place in some of the world’s largest enterprises and governments offices. Spreading cloud capabilities into these larger systems enables containers to exist in the same environment as the company’s central database, and to embrace and modernize those older applications that may still run the most the basic aspects of a business’ day-to-day operations.
To that end, IBM has announced that Red Hat OpenShift is now available to run on IBM Z and IBM LinuxONE systems. From their announcement:
The availability of OpenShift for Z and LinuxONE is a major milestone for both hybrid multicloud and for enterprise computing. OpenShift supports cloud-native applications being built once and deployed anywhere – and now extends this to on premises enterprise servers such as IBM Z and LinuxONE. This offering has been the result of the collaboration between the IBM and Red Hat development teams, and co-creation with early adopter clients. But this is just the beginning, as we are also bringing IBM Cloud Paks to IBM Z and LinuxONE, packaging containerized enterprise and open source software with Red Hat OpenShift.
OpenShift then brings together the core open source technologies of Linux, containers and Kubernetes, adds additional open source capabilities such developer tools and a registry, and hardens, tests and optimizes the software for enterprise production use.
Partnering with IBM Hybrid Cloud, we have also developed a robust roadmap for bringing the ecosystem of enterprise software to the OpenShift platform. IBM Cloud Paks containerize key IBM and open source software components to enable faster enterprise application development and delivery. Today we are also announcing that IBM Cloud Pak for Applications is available for IBM Z and LinuxONE – supporting modernization of existing apps and building new cloud-native apps. In the future, we intend to deliver additional Cloud Paks for IBM Z and LinuxONE.
There are a lot of moving parts inside to enable this integration. IBM and Red Hat have been working together to enable this usage model. This includes new capabilities for IBM’s Cloud Paks.
IBM z/OS Cloud Broker enables OpenShift applications to easily interact with data and applications on IBM Z. IBM z/OS Cloud Broker is the first software product to provide access to z/OS services by the broader development community.
Customers using OpenShift on IBM Z and LinuxONE can also use IBM Cloud Infrastructure Center to manage the underpinning cluster infrastructure. Cloud Infrastructure Center is an Infrastructure-as-a-Service offering which provides simplified infrastructure management in support of z/VM based Linux virtual machines on IBM Z and LinuxONE.
Here are some additional resources to get you up to speed on everything that’s happening between IBM Z and Red Hat OpenShift:
IBM’s page on Cloud Native Development.
IBM’s page on Linux Containers.
Two announcement webcasts, including speakers from IDC, Red Hat and IBM, on March 5 for IBM Z customers, and on March 17 for the wider Linux community.
A sponsored IDC white paper: Transforming a Corporate Datacenter into a Modern Environment: Kubernetes as a Foundation for Hybrid Cloud.
An IBM Systems Magazine article: Red Hat OpenShift, IBM Cloud Paks and more facilitate digital transformation.
The post IBM and Red Hat bring OpenShift to IBM Z and LinuxONE appeared first on Red Hat OpenShift Blog.
Quelle: OpenShift
Vodafone darf sein Mobilfunknetz in Australien doch mit dem Festnetzbetreiber TPG zusammenführen. TPG hatte nach dem dortigen Verbot von Huawei seinen 5G-Ausbau gestoppt. (Vodafone, Mobilfunk)
Quelle: Golem
Get ready to make the most of Google Cloud Next ‘20: our session guide is now available.At Google Cloud Next, our aim is to give you the tools you need to sharpen your technical skills, expand your network, and accelerate personal development. Across our hundreds of breakout sessions you’ll get the chance to connect and learn about all aspects of Google Cloud—from multi-cloud deployments, to application modernization, to next-level collaboration and productivity. Developers, practitioners, and operators from all over the world will come together at Next, and we hope you’ll join them.This year we’re going deep on the skills and knowledge enterprises need to be successful in the cloud. Our catalog of technical content keeps growing, and this year we’re offering more than 500 breakout sessions, panels, bootcamps, and hands-on labs. These sessions will give you in-depth knowledge in seven core areas: Infrastructure—Migrate and modernize applications and systems on premises and in the cloud.Application modernization—Develop, deploy, integrate, and manage both your existing apps and new cloud-native applications.Data management and analytics—Take advantage of highly available and scalable tools to store and manage your structured and unstructured data, then derive meaningful insights from that data.Cloud AI and machine learning—Leverage your data by applying artificial intelligence and machine learning to transform your business.Business application development—Reimagine app development by helping you innovate with no-code development, workflow automation, app integration, and API management. Cloud security—Keep your systems, apps, and users better protected with world-class security tools.Productivity and collaboration—Transform the ways teams grow, share, and work together.This means you can troubleshoot and debug microservices in Kubernetes, get a primer on big data and machine learning fundamentals, then finish up your day by learning to build, deploy, modernize and manage apps using Anthos. Or pick from hundreds of other topics. Want to learn which sessions you don’t want to miss? Beginning in March, we’ll be publishing guides to Next from Google experts. Keep an eye on our blog.
Quelle: Google Cloud Platform
Immer mehr Besitzer von Microsofts Surface Pro 7 ärgern sich über unerklärliche Shutdowns ihres teuren Gerätes. Auch ein Golem.de-Leser hat das Problem. Microsofts Ratschläge helfen nicht, deshalb arbeitet das Unternehmen jetzt intern an einer Lösung. (Surface, Microsoft)
Quelle: Golem
Today, we are announcing the limited preview of Azure Shared Disks, the industry’s first shared cloud block storage. Azure Shared Disks enables the next wave of block storage workloads migrating to the cloud including the most demanding enterprise applications, currently running on-premises on Storage Area Networks (SANs). These include clustered databases, parallel file systems, persistent containers, and machine learning applications. This unique capability enables customers to run latency-sensitive workloads, without compromising on well-known deployment patterns for fast failover and high availability. This includes applications built for Windows or Linux-based clustered filesystems like Global File System 2 (GFS2).
With Azure Shared Disks, customers now have the flexibility to migrate clustered environments running on Windows Server, including Windows Server 2008 (which has reached End-of-Support), to Azure. This capability is designed to support SQL Server Failover Cluster Instances (FCI), Scale-out File Servers (SoFS), Remote Desktop Servers (RDS), and SAP ASCS/SCS running on Windows Server.
We encourage you to get started and request access by filling out this form.
Leveraging Azure Shared Disks
Azure Shared Disks provides a consistent experience for applications running on clustered environments today. This means that any application that currently leverages SCSI Persistent Reservations (PR) can use this well-known set of commands to register nodes in the cluster to the disk. The application can then choose from a range of supported access modes for one or more nodes to read or write to the disk. These applications can deploy in highly available configurations while also leveraging Azure Disk durability guarantees.
The below diagram illustrates a sample two-node clustered database application orchestrating failover from one node to the other.
The flow is as follows:
The clustered application running on both Azure VM 1 and Azure VM 2 registers the intent to read or write to the disk.
The application instance on Azure VM 1 then takes an exclusive reservation to write to the disk.
This reservation is enforced on Azure Disk and the database can now exclusively write to the disk. Any writes from the application instance on Azure VM 2 will not succeed.
If the application instance on Azure VM 1 goes down, the instance on Azure VM 2 can now initiate a database failover and take-over of the disk.
This reservation is now enforced on the Azure Disk, and it will no longer accept writes from the application on Azure VM 1. It will now only accept writes from the application on Azure VM 2.
The clustered application can complete the database failover and serve requests from Azure VM 2.
The below diagram illustrates another common workload consists of multiple nodes reading data from the disk to run parallel jobs, for example, training of Machine Learning models.
The flow is as follows:
The application registers all Virtual Machines registers to the disk.
The application instance on Azure VM 1 then takes an exclusive reservation to write to the disk while opening up reads from other Virtual Machines.
This reservation is enforced on Azure Disk.
All nodes in the cluster can now read from the disk. Only one node writes results back to the disk on behalf of all the nodes in the cluster.
Disk types, sizes, and pricing
Azure Shared Disks are available on Premium SSDs and supports disk sizes including and greater than P15 (i.e. 256 GB). Support for Azure Ultra Disk will be available soon. Azure Shared Disks can be enabled as data disks only (not OS Disks). Each additional mount to an Azure Shared Disk (Premium SSDs) will be charged based on disk size. Please refer to the Azure Disks pricing page for details on limited preview pricing.
Azure Shared Disks vs Azure Files
Azure Shared Disks provides shared access to block storage which can be leveraged by multiple virtual machines. You will need to use a common Windows and Linux-based cluster manager like Windows Server Failover Cluster (WSFC), Pacemaker, or Corosync for node-to-node communication and to enable write locking. If you are looking for a fully-managed files service on Azure that can be accessed using Server Message Block (SMB) or Network File System (NFS) protocol, check out Azure Premium Files or Azure NetApp Files.
Getting started
You can create Azure Shared Disks using Azure Resource Manager templates. For details on how to get started and use Azure Shared Disks in preview, please refer to the documentation page. For updates on regional availability and Ultra Disk availability, please refer to the Azure Disks FAQ. Here is a video of Mark Russinovich from Microsoft Ignite 2019 covering Azure Shared Disks.
In the coming weeks, we will be enabling Portal and SDK support. Support for Azure Backup and Azure Site Recovery is currently not available. Refer to the Managed Disks documentation for detailed instructions on all disk operations.
If you are interested in participating in the preview, you can now get started by requesting access.
Quelle: Azure
Die Telekom sieht Sprint inzwischen als zu hoch bewertet an. Der US-Mobilfunkbetreiber soll nach dem Zusammengehen mit T-Mobile US weniger Anteile bekommen. Sprint gehört der japanischen Softbank Group, deren Chef Masayoshi Son Nachverhandlungen ablehnt. (Sprint, Telekom)
Quelle: Golem
Wer sich ansatzweise ambitioniert mit Pikachu und seinen Kumpels beschäftigt, kommt vermutlich schon bald nicht mehr ohne Pokémon Home aus. Die App ist nun für Nintendo Switch und mobile Endgeräte mit iOS und Android erhältlich. (Pokémon, Nintendo)
Quelle: Golem
Der Test von Xcloud geht weiter: Microsoft bringt den Dienst für Spielestreaming auch für iOS-Geräte heraus. Zunächst soll eine limitierte Anzahl an Testern zugelassen werden, die zudem erst einmal nur ein Spiel darauf spielen können. Die Nachfrage ist laut Microsoft trotzdem groß. (Microsoft, Server)
Quelle: Golem
