0xF2

Red Hat Ceph Storage and ODF continue. The same team will continue to develop newer releases, now with dual IBM and RHT corporate access.

Open Source commitment, upstream first, and foundation continue as before.

I am a member of the team, and while we are certainly adjusting to the news, we are also pretty excited. Red Hat has been generous to Ceph, but it could not take Ceph beyond platform storage for OpenStack and Kubernetes — we want to reach for the full “Linux of Storage” original vision.

A brief discussion of the talk at Open Source Summit: How Many Ways Can You Fail? A Taxonomy of Corporate (in)Decision.

(Podcast)

Help improve Cephadm by submitting feedback upstream or to Red Hat!

Yay. Thank you.

Yes, two billion in a single bucket is a bit much, index sharding only goes to ~700M if I remember correctly.

We support multiple versions in parallel. Currently Jewel (which has just received the 5-year extension) and Luminous, with Nautilus set for release later this year.

Beast is pretty cool. Full performance analysis coming in September!

CephFS finally reached supported status -- and many other additions in this summary of Red Hat's new storage system.

The designer in the software team gets to decide what is available. Software that has no design has in itself been designed, but the choices were made by a developer instead.

There is nothing inappropriate about one vendor making choices. to continue the Apple example, they make 8 of the reasonably complete smartphones you could choose to buy. If you were forced to buy Apple's phone, that would be another matter, but you get to choose.

I believe I have seen this work in Leopard through Lion, particularly Snow Leopard. I remember re-making the addressing of my home network once I changed jobs and the internal subnets were no longer different. More recently, I no longer print with the same machine at both sites, I will check it out.

This is not an explicit option, such as a default setting for printer for a named network. What I noticed back then was that printers located on the unreacheable networks were never the default offering, provided the routing could be used to distinguish where I was. So, if both home and work networks were using 10.0.0/24, it would not work.

It may be possible that binding to the name of access points is a more clever way to do it today.

The sea of printers at the office. How do you simplify when "you see the whole network" as you put it?

I like it better than reading different signs in every office I visit.

In the US the problem however is that recycling collection is not standardized. Each city does it differently, which gets in the way of the standardization you propose. We would need a Federal standard (or at least an agreement by the relevant industry association) to help there.

Why would one-bin be impossible? We have ways to differentiate commingled glass, plastic, and metal automatically (and mechanically). We can get fancier with AI if we need to.

Always use the word impossible with the greatest care. Everything is always impossible right up to the moment it is done.

Care to offer us a design that solves the problem?

Fascinating. Thanks for sharing, I thin this is probably one extreme of the scale of effort taking care of garbage... and with good reason given the delicate ecosystem.

The things you learn talking about design ;-)

That is actually a better point for recycling UX than saving a user's time, as most people do not throw away trash so many times a day to make UX matter. But the system does not work if it defeats the user's willingness to cooperate, as the escalating documentation shows.

Thanks! I shall add it to the article.

Author here. The point here is not the trash, I go by those bins twice a day and can affor to think a few more seconds if I am carrying something unusual. Plus it makes you feel like you are part of a bigger cause to put near-zero effort to help save the planet.

The point is software. There I should not spend a fraction of a second thinking, because that does not happen twice a day. It happens every 15 minutes if we are talking about me looking at my phone. UX thinking there makes a real, tangible difference.

Apple does not get away with it because of force, or because of Steve Jobs' style. Apple can actually provide two different experiences, one via the UNIX cli (with a lot of knobs) and one in the Mac OS X UI (with high UX). Browsers do the same with chrome:// and about:config.

In a properly modular design, you often do not need to choose whether to upset the expert user or to make the naïve ones happy.

Sebastien Han is showing how to install 1.3 (and other versions too) using Ansible here:

https://www.youtube.com/watch?v=dv_PEp9qAqg&feature=youtu.be