A Better Way to Discover Blogs and Get Inspired

WordPress is home to millions of sites across countless topics. It’s a big and beautiful world, and we want to make it easier for you to discover new voices. Over the past few months, the mobile team has been working hard to improve the experience of your WordPress Reader on the mobile app. In particular, we’ve been exploring different ways for you to discover new blogs and find inspiration.

The new Discover tab on your Reader will recommend blogs and posts based on topics you follow. These changes give you more control over what you see, making it easier for you to find interesting voices, while also giving you and your site the opportunity to find a bigger audience. 

How it works

Add appropriate tags and categories when drafting your blog posts — this helps us recommend your posts to the right audience. 

The topics you now see in your improved Reader are a combination of tags and categories. If you want to find interesting blogs, follow topics you care about. The Discover tab will then show you recommended blogs and posts based on those topics.

Each post on the Discover tab has a list of topics on top. If you want to go deeper into a topic, tap on it to see a feed of blog posts from that specific topic.

If you’d like to see more posts from a particular topic on your Discover feed, tap the Follow button from that topic feed.

Soon we’ll be rolling out improvements to posts on the Reader as well. To give blog posts more room to shine, the featured image will be more prominent. 

If you’d like to try the new Discover tab, make sure you update your WordPress app to the latest version. If you don’t have the app yet, you can download it for free, on both Android and iOS. We’d love to hear your thoughts on the new experience. For specific feedback on the updates, reach out to us from within the app by going to My Site, tapping your photo on the top right, tapping Help & Support → and then selecting Contact Support.
Quelle: RedHat Stack

Toward zero: Reducing and offsetting our data center power emissions

Following the massive Australian bushfires earlier this year, I was motivated to act within my role as a data scientist at Automattic to help fight anthropogenic climate change. Together with colleagues from across the company, we formed an employee resource group focused on sustainability. We are pleased to announce that as a result of our efforts, Automattic now offsets data center power emissions produced from non-renewable sources. This means that the servers running WordPress.com, WordPress VIP, Tumblr, and other Automattic services contribute net zero carbon emissions to our shared atmosphere.

Measuring and offsetting emissions is not a trivial task. In the interest of transparency, this post provides more details on the decisions we made and answers questions that readers may have on the topic. We hope that this will benefit other organizations that are in a similar position to Automattic. We welcome feedback and are happy to answer any other questions you may have.

The decision: For 2020, we decided to purchase offsets from Simoshi via the United Nations’ offset platform. These offsets are produced by improving the efficiency of cooking stoves in Ugandan schools. Emission reductions are achieved by using less wood to cook the same amount of food. This project also has third-party certification from the Gold Standard, and it contributes to nine of the United Nations’ Sustainable Development Goals, including No Poverty, Quality Education, and Gender Equality. See the project page and the following video for more details:

Why did we choose this project? Anyone who’s tried to purchase offsets knows that it can be complicated. We don’t have in-house sustainability experts, so we relied on publicly-available information to better understand the topic. Resources we found useful include: Carbon Offset Guide, atmosfair, and Greenhouse Gas Protocol. As the price of offsets varies widely, we chose to follow Microsoft’s approach and set our own internal price of $15 per metric tonne of CO2e. Simoshi’s project stood out because it matches our budget, has a clear emission reduction mechanism, is certified by the United Nations and the Gold Standard, and has many benefits beyond emission reductions, which align with our company’s values.

What emissions do our offsets cover? Automattic has servers in many data centers around the world, operated by different providers. As we don’t control the data center providers’ choice of energy utilities, we treat the emissions from data center power use as being in Scope 3, i.e., as indirect emissions from our value chain. For each data center, we used publicly-available information from our providers to determine whether they’re powered by renewable resources. This led us to conclude that approximately half of our data center energy use is covered by renewables paid for by the data center providers. For the other data centers, we used our servers’ power consumption logs to get the estimated power used over a period of one year. We then multiplied these figures by 1.5 to obtain a conservative estimate that accounts for power usage effectiveness. Using a variety of resources on grid carbon intensity, such as those published by the American Environmental Protection Agency and the European Environment Agency, we converted these power use estimates to emission estimates. This gave us an overall figure of 1,850 tonnes of CO2e for 2020.

Why offset rather than reduce emissions? We are aware that offsetting is an imperfect solution. Ideally, we would source all our energy from renewables. In a perfect world, it wouldn’t even be possible to buy energy generated by burning fossil fuels. However, given the current reality, setting our own price on carbon and offsetting non-renewable data center emissions is a good temporary solution. This also gives us a financial incentive to work with providers and shift toward greener data centers. In fact, this sort of shift happened last year when we changed our main European data center to a provider that operates on 100% renewables. We hope to continue making such changes in coming years, i.e., reducing emissions where feasible and offsetting the rest.

Why aren’t we doing more? From watching the climate action space, it seems like every announcement is greeted with demands to do more. This is a positive thing — society should hold companies accountable for their actions. As a company, we believe that we can always do better: The opening sentence of our creed is “I will never stop learning”, and we know that we are “in a marathon, not a sprint.” It is our hope that as we learn more about the space and our impact, we will be able to take stronger climate action.

What are we planning to do next? Automattic is a fully-distributed company. This means that our employees aren’t required to commute to central offices, which leads to significant savings in carbon emissions. However, we historically relied on flying to in-person meetups a few times a year to foster collaboration and bonding. Since March 2020, all business travel has been suspended, and it is still unclear what travel will look like in the post-pandemic world. In any case, as an employee resource group, we are planning on quantifying our travel emissions, and advocating for reducing avoidable trips and offsetting emissions from trips that are deemed essential. One change that is already taking place is aligning more teams around fewer time zones. In addition to helping with synchronous collaboration and decreasing isolation, this will reduce the distance traveled per person once meetups resume. We will share more on other actions we take in the future — watch this space! We also welcome feedback from our customers, so please comment on this post or contact us to share your thoughts.
Quelle: RedHat Stack

Expert Advice: Stay On Top of Your Business with Jetpack CRM

Customers are the heart of your business, and the best way to maintain your vital relationships with them is with a world-class CRM (customer relationship management) system.

Join us at our next free webinar on Thursday, September 17th, to learn how you can turn leads into customers, track business metrics, leverage data, and monitor activity profiles to better serve your customers—all by using Jetpack CRM.

Date: Thursday, September 17, 2020Time: 8:00 am PT | 10:00 am CT | 11:00 am ET | 15:00 UTCRegistration link: https://zoom.us/webinar/register/8015988855022/WN_ZMyGfL7dRsm_4yzwivSnzwWho’s invited: All are welcome, but this webinar is designed especially for small business owners, freelancers, consultants, and anyone else interested in learning how they can improve their sales process.

Jetpack CRM was built specifically for WordPress, so that you can manage your leads as they navigate your sales funnel, all on your WordPress dashboard. Mike Stott and Woody Hayday, the founding developers and lead engineers behind Jetpack CRM, will be co-presenting in the webinar, which will include a 15-minute live Q&A at the end of the 45-minute presentation.

Don’t worry if you can’t make it to the live webinar, though! A recording will be available on our YouTube channel a few days after the event.

Live attendance is limited, so be sure to register early. We look forward to seeing you!
Quelle: RedHat Stack

Start Taking Donations, Tips, and Contributions for Your Creative and Professional Pursuits

With our growing suite of payment features, we want to make it easier for you to earn money on WordPress.com. With the Donations block, you can now accept credit and debit card payments for all types of donations, earning revenue and growing your base of supporters. Collect donations, tips, and contributions on your website to fuel your creative and professional projects or to support and grow your business or organization.

Donations block example for an arts organization

What can you accept donations for?

You can collect financial contributions on your website for just about anything — the sky really is the limit. Here are examples of things people support through donations:

Creative pursuits for musicians, artists, designers, writers, and moreConcrete creations like podcasts, video games, music clips, and photographyBloggers and content creators of all shapes and sizesEveryday passions like news summaries and mindfulness exercisesProfessional endeavors including civic engagement and professional developmentNonprofits and community, religious, and political organizations

Donations block examples for a musician and radio station

Continue to build your community by engaging with your supporters in a unique and authentic way. People can opt to support you through one-time, monthly, or yearly contributions, and the Donations block lets you engage with each level for a more custom experience. For example, you might send your monthly supporters additional content and information on top of what you send your one-time supporters.

As you ask for support, we’ll handle the rest — the credit and debit card payment processing, sending receipts, reporting, and more.

Ask for your first donation

Above all, the first step in earning money on your website is to ask for it. You can add a Donations block to your website in a matter of minutes; watch this short video to learn how. Alternatively, a step-by-step guide follows below.

How to use Donations block to earn money on your WordPress.com website

To use the Donations block, you’ll need a WordPress.com website with any paid plan — Personal, Premium, Business, or eCommerce.On any page or post, add the Donations block.

To set up your first donation request, create a Stripe account if you don’t have one already. Stripe is the company we’ve partnered with to process credit and debit card payments in a safe, secure, and speedy way.After you’ve connected to Stripe, configure the block’s settings, like how often you’re asking for donations. It can be any combination of single (one-time), monthly recurring, or yearly recurring donations.

Set three donation amounts that you’d like visitors to choose from for any of the payment intervals. These are fully customizable. Be sure to set your currency as well.

You can also allow visitors to donate what they want — essentially a blank box for them to fill out how much money they would like to give.

Review all of the text in your Donations block — you can edit every single letter, so be sure to provide enough information for your visitors about their donation, why you’re asking for it, etc.

Publish your block!You can manage your supporters, see earnings, and keep an eye on other metrics in the Earn dashboard.

Last but not least, tell others about what you’re doing! Share on social media, email, and however you best communicate with people who might donate to your cause.

A suite of payment features to fit your needs

Looking to accept payments for something else? There are several other payment features on WordPress.com to suit your needs and help you make money with your website. In addition to the new Donations block, here are other features:

Payments block: Accept one-time or recurring payments on your website for physical items, digital downloads, services, memberships, subscriptions, and more.Premium Content block: Create one-time, monthly, or yearly subscription options to share select content with those who pay for it — text, images, videos, or any kind of content. Exclusive content can be sent to email inboxes or viewed on your website.Paid newsletters: Using the Premium Content block, you can share your site’s latest premium content via email newsletters in a fully automated way.eCommerce Store: Turn your website into an eCommerce store and sell products and services seamlessly.

If you’re interested in setting up a membership- or subscription-based website, learn more about getting started with memberships and subscriptions.

Add the Donations block and start earning money with your website today!
Quelle: RedHat Stack

Lens 3.6 Released — Kubeconfig Files as References, Additional Smart Terminal Options and More!

The post Lens 3.6 Released — Kubeconfig Files as References, Additional Smart Terminal Options and More! appeared first on Mirantis | Pure Play Open Cloud.
We’re excited to announce Lens — the Kubernetes IDE — version 3.6 is now available. This is the first release since Mirantis took over the lead in the project. The biggest new features are related to the way Lens manages Kubernetes cluster access using kubeconfig files and additional smart terminal configuration options. These features will greatly improve the overall user experience, enhance support for various Open ID providers and make it possible to use Lens in restricted enterprise environments. While working on these features, we also completed massive refactoring to unify the underlying frontend framework to support an extensions API in the future plus a lot of smaller fixes. See the entire changelog at the end of this post.

I’d like to thank all contributors to the 3.6 release: @aleksfront, @nevalla, @jakolehm, @ocdi, @ixrock, @jim-docker, @timurista, @Nox-404, @rand0me, @Nokel81, @jnummelin, @dan-slinky-ckpd

See below for more details about the new features and improvements.
Use Kubeconfig Files as References
One of the key features of Lens 3.6 is the ability to use kubeconfig files directly as cluster references instead of copy-pasting the contents of those files. Simply choose the file from your filesystem.

Previously, this information was stored internally and it was working fine as long there was no need to update the kubeconfig file contents. However, many Lens users are using third party tools from managed Kubernetes service providers to generate their kubeconfig files. These tools not only generate those files but might also update them on the fly. This behaviour has caused a lot of confusion (even sadness) among our users and we are happy to say those days are now gone. Lens will automatically use the fresh data available from the kubeconfig files!
Additional Smart Terminal Options
The users of Lens have been able to enjoy the built-in Smart Terminal for quite some time. The Smart Terminal comes with kubectl and some other tools necessary to work with Kubernetes clusters. The terminal is smart because it will automatically switch the version of kubectl to match the currently selected cluster API version. It will also automatically switch the context to match that selected cluster.

While Smart Terminal is great and improves the quality of life for many of our users, users working in restricted enterprise environments have found it impossible to use due to restricted directory access where Smart Terminal bundled binaries may be executed and/or downloaded. You can now define the directory used with Smart Terminal

Docker Enterprise Container Cloud: Continuously updated, multi-cloud Kubernetes

The post Docker Enterprise Container Cloud: Continuously updated, multi-cloud Kubernetes appeared first on Mirantis | Pure Play Open Cloud.
Kubernetes is complicated. Leveraging multiple cloud platforms, providers, technology stacks, and flavors of Kubernetes is even more complex, demanding, risky, and expensive. 
That’s why today we are pleased to announce the release of Docker Enterprise Container Cloud, designed to help you ship code faster by providing choice, simplicity, and security.
Docker Enterprise Container Cloud is a multi-cloud management solution that gives you one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal. What’s more, they are continuously updated by Mirantis, with zero downtime.   
OK, that’s a lot, so let’s look at what it actually means.
Multi-cloud management
At the base of Mirantis offerings has always been freedom from vendor lock-in. In this case it means the ability to spin up Kubernetes clusters on a variety of different providers. For example, you might have some clusters on-prem, on your OpenStack cloud, and others on Amazon Web Services. You can even deploy on bare metal!
It works like this:

Deploy the management cluster.
The management cluster deploys regional clusters. 
Regional clusters deploy and manage child clusters.

For example, you might deploy a regional cluster (Cluster1) on the AWS us-east-1a region, and a second (Cluster2) on your internal OpenStack cloud. Each manages Docker Enterprise Kubernetes clusters in its own region. So Cluster2 would create and manage Kubernetes clusters that run on your local OpenStack resources, while Cluster1 manages Kubernetes clusters running on EC2 servers in the us-east-1a region.
The importance of a standard API
At first it may seem silly to even worry about this; after all, can’t you just use services like Amazon’s Kubernetes Service to create clusters?  Sure you can, but once you’ve done that, you’re locking yourself into the AWS management API, AWS deployment tooling, and thus the AWS cloud (and AWS bills).
By providing a common management API, Docker Enterprise Container Cloud provides a number of advantages:

Freedom to move among different providers as price, capability, and geography dictate
Freedom to stop maintaining multiple provisioning stacks, unique to each infrastructure or provider
The ability to see what’s going on overall from a single pane of management glass
The ability to see aggregated statistics using Stacklight, Mirantis’ Logging, Monitoring, and Alerting framework

This release also brings a few more advantages.
Automated upgrades and other release highlights
Docker Enterprise Container Cloud is a complete lifecycle management system, periodically checking for updates and applying them without disrupting user workloads. It also integrates with ActiveDirectory and other IAM management systems, enabling you to provide your users a public cloud experience right in your own environment.
And of course underlying all clusters, Docker Enterprise Kubernetes is hardened for enterprise production use, and its Docker Engine – Enterprise container runtime features content trust, STIG, OSCAL, FIPS 140-2 encryption, and other technologies required by Gov/Mil and regulated industries.
We also have three new service offerings:

LabCare includes business day support for non-production clusters, hardened software packages with regular maintenance updates and critical fixes, as well as remote incident resolution.
ProdCare includes 24x7x365 support for production, with enhanced SLA and escalation management.
OpsCare includes fully managed remote operations with up to 99.99% SLA, 15 minute initial response time, lifecycle and alert management, and customer advocacy and roadmap planning.

There’s also more for your developers this time around.
Developers, Container Cloud, and Lens
Most of the time, Docker Enterprise releases are all about operators, but not this time; in addition to our goal of providing the equivalent of the public cloud experience on your own infrastructure, we want to help you ship code faster by enabling you to deploy a cluster without having to think about it — or worse, get permission!
And don’t forget about Lens, the world’s most popular Kubernetes IDE, which enables you to work with any Kubernetes cluster, as long as you have the KUBECONFIG. Manage multiple clusters without losing your context, group clusters into workspaces to ease the pain of managing dozens or hundreds (or thousands!) of clusters.
So go ahead and try out both Docker Enterprise Container Cloud and Lens, and join us at Launchpad2020 for more information about both!
The post Docker Enterprise Container Cloud: Continuously updated, multi-cloud Kubernetes appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

The Forrester Multi-Cloud Container Development Platforms Wave Report, Reimagined With Docker Enterprise Container Cloud

The post The Forrester Multi-Cloud Container Development Platforms Wave Report, Reimagined With Docker Enterprise Container Cloud appeared first on Mirantis | Pure Play Open Cloud.
It’s difficult to create a report defining the “state of the industry” for an industry that moves as fast as cloud computing.  For example, Forrester recently published its Multi-Cloud Container Development Platforms Wave Report, covering nine leading vendors in the category, and in order to make the report “fair”, every company was represented by the state of its offerings as of April 1, 2020.
Unfortunately, if you’re a company whose new product offering didn’t become generally available until, say April 2, 2020, those new offerings weren’t considered in the report.  For example, if this latest report were based on Mirantis’ current products, support offerings, and services, as well as the Mirantis strategy/vision Mirantis would clearly have been ranked a Leader — just as it was in the previous Forrester Wave Report.
Instead, because Forrester was (understandably) hamstrung by its rules it had to work with what was available on that date.
What the Forrester Wave report left out
For Mirantis, this means the report couldn’t take into account the following:

The Docker Enterprise Container Cloud release that will be available this coming week. Instead, it was based on Docker Enterprise 3.0, shipped back in 2019. Docker Enterprise Container Cloud key capabilities:

Multi-Cluster Management
Multi-Cloud: Public, Private, BM
Self-Service Clusters
Automated Full-Stack LCM
Centralized Observability
Add Existing Docker Enterprise Clusters to Fleet
Lens Kubernetes IDE

Our most recent support offerings ProdCare, a 24×7 follow-the-sun support offering, and OpsCare, a managed service offering with a 99.99% SLA and a cloud, tooling, and ops team 100% focused on the success of your organization.
Our acquisition and strategic integration of Lens, the world’s most popular Kubernetes IDE, one of the top 30 Kubernetes-related projects on GitHub, with over 8,200 stargazers, 52,000 users, and 600,000 downloads.

Why Mirantis Is a Leader
Obviously we can’t guarantee what the results would have been had the report been written today, but given our past experience, we’re fairly certain that we would have maintained our position as a Leader.  Inclusion of Docker Enterprise Container Cloud in the Mirantis profile would have significantly changed the score for each of the following Forrester Wave evaluation criteria:

Platform Operations

Docker Enterprise Container Cloud introduces groundbreaking multi-cluster, multi-cloud lifecycle operations capabilities. Operators and developers can easily create Kubernetes clusters via GUI or API, and the Container Cloud will automatically provision the underlying infrastructure, operating system, and cloud-native Kubernetes stack across public/private clouds and bare metal.
Container Cloud keeps its management clusters and associated child clusters up to date with full-stack continuous updates. Every cluster is automatically updated using Kubernetes rolling updates, ensuring that workloads remain operational. With a single click, child cluster owners can decide when to apply available updates.
Control plane configuration is managed by the Container Cloud. The management cluster is deployed via a bootstrap node and a YAML configuration file with details about the other management cluster nodes. Container Cloud takes care of the remaining deployment steps, with full-stack lifecycle management of the infrastructure, the operating system, and the cloud-native Kubernetes stack.
Container Cloud includes cloud-native logging and monitoring across the entire fleet of clusters. Child cluster owners can observe and monitor real-time Prometheus metrics, review logs, receive alerts, and more. Centralized IT Operations can view data for any cluster as well as aggregated data for the entire fleet.
Through built-in security features and policies, Container Cloud supports RBAC, IAM, LDAP and Active Directory. Container Cloud respects multi-tenancy policies and security permissions of underlying infrastructure when deploying child clusters. Container Cloud builds on industry-leading security features in Docker Enterprise, including FIPS 140-2 Validation and a DISA STIG, and built-in image scanning and signing in Docker Trusted Registry.

Platform Infrastructure

The distributed multi-cluster management capabilities in Docker Enterprise Container Cloud enable robust edge computing support. With a centralized management plane and centralized observability, coupled with automated full-stack lifecycle management and continuous updates, organizations can ensure their entire fleet of Kubernetes clusters are always consistent, available, and up to date, from the data center to the edge.
Based on the underlying infrastructure, Container Cloud automatically provisions container storage resources for each of its child clusters. Users don’t need to hassle with the complexity of attaching storage volumes to their VMs, leveraging a centralized Ceph cluster, or using mounted volumes on bare metal nodes.

Platform Experience

Docker Enterprise Container Cloud and Lens provide a developer experience that’s unparalleled in its ease of use and efficiency. By using an intuitive GUI to create and update self-service Kubernetes clusters, developers can deploy, observe and manage their applications without getting slowed down by complex infrastructure. 
By simply importing their clusters’ kubeconfig files into Lens, developers can easily navigate Kubernetes primitives such as deployments, pods, and nodes, with complete situational awareness and control. With a single click. developers can inspect logs, modify YAML files, or open a terminal to use kubectl.
Container Cloud, Docker Enterprise, and Lens also provide a consistent operator experience for platform operations across clouds, with automated full-stack lifecycle management and continuous updates, a centralized management plane, centralized observability, self-service clusters, and a secure software supply chain.
With the intuitive GUI included in Container Cloud, operators can manage an entire fleet of Kubernetes clusters across public and private clouds, as well as bare metal. A centralized cloud-native LMA toolchain provides observability for each cluster, and aggregated data for the entire fleet.
Mirantis is the only leading container platform vendor to offer real enterprise choice at every layer of the stack, from the infrastructure layer to the operating system to the cloud-native Kubernetes ecosystem. Enterprises no longer need to lock themselves into a single virtualization/cloud platform or operating system – with Mirantis they are free to choose the infrastructure and tools that best suit their needs.

Cloud-Native Application Development

With robust open standards-based integration support for RBAC and IAM platforms, DevOps toolchains, Kubernetes-native tooling, and more, Container Cloud enables development environments that are fully integrated across the entire software development lifecycle. Every open standards-based Kubernetes cluster in its fleet can be managed by its intuitive GUI or rich Kubernetes and Cluster APIs, unlocking application and DevOps portability across clouds. 
Container Cloud also provides enterprise-grade SSO, AD/LDAP integration, RBAC, multitenancy, DevOps integration, and policy customization features that integrate with Docker Docker Enterprise, Docker Trusted Registry, and 3rd-party systems, to create a unified and secure software supply chain.

Container Runtime and Registries

Docker Enterprise Container Cloud provides robust image and application lifecycle management features for comprehensive container image support. With Docker Trusted Registry, a private image registry with built-in image scanning and signing that’s included with Docker Enterprise, developers and operators can count on a secure software supply chain that integrates with their preferred CI/CD tooling. 
Container Cloud deploys Kubernetes clusters in HA configuration by default, so that applications can be updated or scaled without downtime. Using its intuitive GUI or through CI/CD automation leveraging the Kubernetes Cluster API, developers and operators can add or remove worker nodes to tune their clusters for application scaling and performance.

Market-Leading Innovation
With the launch of Docker Enterprise Container Cloud, enterprises can benefit from innovative new capabilities for automated full-stack lifecycle management with continuous updates, centralized management & observability, and an industry-leading secure software supply chain. Best of all, it’s free to download and use – give it a try today.
The post The Forrester Multi-Cloud Container Development Platforms Wave Report, Reimagined With Docker Enterprise Container Cloud appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Docker Enterprise Container Cloud Helps Kubernetes Developers Ship Code Faster on Public and Private Clouds

The post Docker Enterprise Container Cloud Helps Kubernetes Developers Ship Code Faster on Public and Private Clouds appeared first on Mirantis | Pure Play Open Cloud.
Mirantis reduces cloud complexity with real choice, simplicity, and security
MIRANTIS LAUNCHPAD VIRTUAL EVENT, (Campbell, CA) — September 16, 2020 — Announced at the inaugural Mirantis Launchpad 2020 virtual conference, Docker Enterprise Container Cloud offers enterprises unprecedented speed to ship code faster on public clouds and on premise infrastructure. It simplifies Kubernetes with one consistent cloud experience for developers and operators across public and private clouds, with complete app and devops portability.
“Docker Enterprise Container Cloud and Lens will enable businesses to streamline delivery of hundreds of daily deployments across thousands of apps, overcoming the complexity of Kubernetes development at enterprise scale,” said Mirantis customer Don Bauer, Docker Captain and VP Technology Services / DevOps Manager.
Docker Enterprise Container Cloud is available free of charge for up to 3 clusters totaling 15 nodes, without any limitations in functionality.
The launch follows the introduction of Docker Enterprise 3.1 and new 24×7 and managed operations support offerings, which launched in May 2020. The release builds on the Mirantis Kubernetes vision to deliver Your Cloud Everywhere and the recent announcement of Lens, the world’s most popular Kubernetes IDE. Lens greatly simplifies app development by consolidating more than a dozen Kubernetes tools into a single integrated development environment that provides dev and ops teams with situational awareness in their context. 
With Lens and Docker Enterprise Container Cloud, Mirantis empowers a new breed of Kubernetes developers by removing infrastructure and operations complexity through automated full-stack lifecycle management and continuous updates, and providing tools for insights and management that support cloud-native software development.
“Docker Enterprise Container Cloud breaks the mold with real choice at every layer of the stack,” said Adrian Ionel, CEO and co-founder, Mirantis. “Unlike lock-in solutions like IBM/Red Hat and VMware that force you to deploy their rigid stack, Container Cloud empowers you to deploy your own multi cloud everywhere, unlocking speed with freedom of choice, simplicity, and industry-leading security.”
New capabilities in Docker Enterprise Container Cloud include:

Multi-Cloud: Public, Private, and Bare Metal
Multi-Cluster Management
Self-Service Clusters On-Demand
Automated Full-Stack Lifecycle Management with Continuous Updates
Centralized Insights and Management

Container Cloud is the only independent container platform that provides a choice of operating system and virtualization software. Developers can benefit from a frictionless “managed Kubernetes” experience of self-service cluster provisioning across any infrastructure, while enterprise IT can ensure compliance with regulations and corporate policies. Developers can easily deploy and manage clusters via API, CLI, or UI, and can approve automated zero-downtime updates to their clusters as they become available from Mirantis.
Docker Enterprise Container Cloud enables companies to ship code faster with these key capabilities:
Cloud Choice – Provides choice at every level of the stack, from the virtualization layer to the OS to Kubernetes, so that organizations can build on open standards and use their favorite tools and frameworks to ship code faster that runs on any private, public, or hybrid cloud.
Cloud Simplicity – Simplifies Kubernetes for developers and operators with one cohesive cloud experience, built in security, a single pane of glass, and full lifecycle management.  
Cloud Speed – Increases developer velocity with a modern software supply chain for getting secured code to production faster and continuously. Container Cloud provides developers self-service access to Kubernetes clusters, complete app and devops portability, and built-in industry leading security.
Cloud Secured – Enhances the security of your Kubernetes clusters and modern apps through a secure supply chain that integrates security into every stage of the application lifecycle. Container Cloud provides the industry’s most secure container engine with FIPS 140-2 validation along with built-in image scanning and signing.
Cloud Scale – Enables organizations to achieve massive scale from the desktop to the data center, delivering consistent clusters everywhere. Operators benefit from complete observability and management across a fleet of automatically updated Kubernetes clusters.
Pricing and availabilityDocker Enterprise Container Cloud is available for download free HERE, without any limitations in functionality, for up to 3 clusters totaling 15 nodes. For larger-scale deployments requiring enterprise support, Mirantis provides annual subscriptions for LabCare 8×5 support, ProdCare 24×7 support and OpsCare 24×7 managed operations.
To learn more about Docker Enterprise Container Cloud, visit: https://www.mirantis.com/software/docker/docker-enterprise-container-cloud/.
About Mirantis
Mirantis helps organizations ship code faster on public and private clouds. The company provides a public cloud experience on any infrastructure to the data center to the edge. With Lens and Docker Enterprise Container Cloud, Mirantis empowers a new breed of Kubernetes developers by removing infrastructure and operations complexity and providing one cohesive cloud experience for complete app and devops portability, a single pane of glass, and automated full-stack lifecycle management with continuous updates.
Mirantis serves many of the world’s leading enterprises, including Adobe, DocuSign, Liberty Mutual, Nationwide Insurance, PayPal, Reliance Jio, Splunk, and STC. Learn more at www.mirantis.com.
Media Contact
Joseph Eckert for Mirantis
The post Docker Enterprise Container Cloud Helps Kubernetes Developers Ship Code Faster on Public and Private Clouds appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis

Seedlet: A New, Sophisticated Theme Fully Powered By the Block Editor

Is your WordPress.com site ready for a refresh? Today, we’re unveiling Seedlet, a new theme that’s simple yet stylish.

Designed by Kjell Reigstad, Seedlet is a great option for professionals and creatives seeking a sophisticated vibe. Classically elegant typography creates a refined site that gives your writing and images space to breathe — and shine. 

Seedlet was built to be the perfect partner to the block editor, and supports all the latest blocks. Writing, audio, illustrations, photography, video — use Seedlet to engage and direct visitors’ eyes, without the theme getting in the way. And the responsive design shifts naturally between desktop and mobile devices.

Learn more about setting up Seedlet, and explore the demo site to see it in action. 

Our team is hard at work developing new block-powered themes. Watch this space for updates!
Quelle: RedHat Stack

How to Create a Unified Container Strategy When Your Developers Have Gone Rogue

The post How to Create a Unified Container Strategy When Your Developers Have Gone Rogue appeared first on Mirantis | Pure Play Open Cloud.
If you’ve paid any attention to press releases or marketing from any major cloud vendor in the last year, you’ve noticed a major focus on multi-cloud capabilities. This is a significant new focus because modern enterprises leveraging container orchestration often have applications running in a number of different environments, and enterprises not yet at this stage often have a number of different infrastructure types to manage. Fortunately, there are options for IT teams to bring rogue developer teams under one umbrella in a way that’s both convenient and increases productivity. 
No VP, CIO or leader of an IT organization wants to invest in technology to make developer’s lives easier only to have them ignore it. So it’s critical to ensure your approach makes things easy for developers across business units. A lot of solutions offer some type of container orchestration, and depending on the maturity and diversity of an organization, you may have several different solutions which fit your needs. 
Organizations looking at implementing enterprise-wide Kubernetes typically have a few requirements:

Flexibility: It is common for different business units to use different tooling for various aspects of their CI/CD pipeline. Enterprises should seek a platform that integrates seamlessly with most available tools for code creation, packaging, security and release. PaaS solutions seem convenient, but can be too opinionated, and force too much of an overhaul across diverse business units. 
Portability: Working with some PaaS or IaaS solutions can create a lock-in scenario where, although easy to manage in the near-term, an enterprise faces great costs should they change direction. Solutions like this can also box in individual business units who want to try different approaches. 
Ease of management: It is, of course, possible to leverage open-source technology to create an enterprise-wide pipeline that accomplishes flexibility and portability, but the complexity of management can create an expensive and time-consuming process to get systems up and running. 
Scalability: How easy is it to spin up multiple clusters across different teams? As you grow your presence within the cloud, this will absolutely be a necessity. 
Security: How secure is the platform, and how well does it facilitate compliance and demonstrability during audits?

With these points in mind, enterprises typically have a choice between an on-prem based solution such as Docker Enterprise or a home-baked solution, or a managed Kubernetes service. 
A few options for accomplishing a unified cloud strategy include Public Cloud, PaaS, DIY Open Source, and Open Source Container Management. Each has its advantages and disadvantages with regard to the five requirements:

Public Cloud: Public Cloud can be a great way to ensure your developers have a consistent platform experience, especially given the number of services and offerings available from each of the Big 3 public cloud providers. Developers are likely to find anything they could possibly need or want within a public cloud platform. So should you find that AWS, for example, has services which meet ALL of the developer, financial and regulatory requirements for your enterprise, this could be the way to go. Having said this, leveraging public clouds also creates some limitations, specifically in terms of giving your developers access to the best tooling for various use cases. It’s entirely possible, for example, that AWS might release better tooling for AI use cases one year, and Azure might have better tooling for Edge in the same year. If an adventurous developer uses her own credit card to purchase another platform for a specific service, it can be both expensive and time consuming to recreate infrastructure that was already available on the platform owned by central IT. This can also lead to unpleasant bills for application owners who receive unexpected (sometimes massive) expenses. Because of this, implementing strict cost controls is a requirement for budget-conscious enterprises on Public Clouds. 
Public cloud scores high on Ease of Management and Security, but lower on Flexibility and Portability, and while it’s highly Scalable, this comes at a significant cost.
PaaS: For infrastructure teams trying to limit the amount that developer teams go off the grid, PaaS may seem on the surface like the best option, and for some use cases, it is. The advantage of using a PaaS solution revolves around the fact that developers are limited in terms of freedom of choice, and developer workflows can be tightly controlled by central IT.Problems arise with PaaS when you go beyond those convenient use cases, so it can be disadvantageous to limit flexibility of developer teams. A good example of this situation would be Edge use cases, which are very popular in the Telecommunications industry. It’s not typically possible to deploy platforms like Red Hat OpenShift on every edge cluster, and this can introduce inconsistencies between the platform and clusters. PaaS, like Public Cloud, scores highly on Ease of Management and Security, but will poorly on Portability and Flexibility. 
DIY Open-source: Kubernetes is an extremely flexible framework, and by now, more than 6 years after it’s inception, we have the advantage that it’s extremely hardened and reliable. Some enterprises opt for building and managing kubernetes in house, but this comes with inherent challenges as well. The Kubernetes ecosystem contains enough integrated tooling that enterprises need to have a devoted team, or experts on open-source, in order to stitch it all together. Even the simple process of provisioning a Kubernetes cluster for a specific development team can require significant experience on behalf of central IT. On the plus side, home-built Kubernetes gives you virtually unlimited flexibility and zero lock in, as long as you have expertise in house. Unlike the first two options, DIY Open-Source does not score so well on Ease of Management, but the Flexibility and Portability are virtually limitless. Security and Scalability depend on the set up you choose, and the capability of your in-house team.
Open-source Container Management: If enterprises lean toward DIY open source options, it’s normally for cost reasons. Perhaps they already have capable IT teams in house with all (or most) of the skills they need, and the bandwidth to build and run an open-source platform.For enterprises who need to have a platform up and running quickly, or who don’t have the experience/bandwidth to stand up a platform themselves, leveraging a commercially provided framework provides all of the advantages of home-built, without the stress of building and managing a platform. Mirantis, as one example, has a K8s platform that is flexible and enables automated cluster deployment across AWS and Azure, OpenStack and Bare Metal, but in addition to this platform, also has a wide range of services, so that enterprises can choose how much control they would like to have for themselves.One common approach with enterprises leveraging such a framework is to have the platform managed by the provider for the first year or two, and as your internal capabilities increase, open-source platforms offer the advantage of easy management transfer to the customer.

It goes without saying that at Mirantis, we’re a little biased toward the final option. It gives maximum flexibility to your developers, and does not require an all-in approach. In other words, our preference would be for a commercial open source container management system that does NOT require you to forgo Azure, AWS or VMWare for certain use cases. For example, our solution is designed to fit on top of Public Clouds, Openstack and Bare Metal, all while giving you a single pane of glass for unified development.
We hope this has helped. Please get in touch with our team if you have more questions. 
The post How to Create a Unified Container Strategy When Your Developers Have Gone Rogue appeared first on Mirantis | Pure Play Open Cloud.
Quelle: Mirantis