October 2020 - Dev - lists.ceph.io

10/15/2020 perf meeting is on at 8AM PST!

by Mark Nelson

Hi Folks, The weekly performance meeting will be starting in about 2 hours! This week we will discuss Adam's work rebasing the onode cache deduplication work on top of column family sharding, Mark's rebase of the priority cache age-binning code, and Gabi's work on PGLog refactor. Please feel free to add your own topic to the etherpad as well. Hope to see you there! Etherpad: https://pad.ceph.com/p/performance_weekly Bluejeans: https://bluejeans.com/908675367 Thanks, Mark

3 years, 6 months

1
0
0 0

Questions about ISA-L Crypto built into Ceph

by Song, Shijin

Hi all, I'm focusing on the ISA-L encryption in the Ceph master. But when I read the 'CMakelists.txt' in Ceph, I found the default usage of crypto lib is 'openssl' rather than 'isa-l' or others. So I just wonder whether the isa-l crypto has been built in Ceph and how the isa-l crypto usage method in Ceph currently. Hope you may help and reply. Thanks. Best wishes, Shijin

3 years, 6 months

2
1
0 0

DocuBetter Meeting 14 Oct 2020 -- 24 hours from the time of this email.

by John Zachary Dover

There is a general documentation meeting called the "DocuBetter Meeting", and it is held every two weeks. The next DocuBetter Meeting will be on 14 Oct 2020 at 1630 UTC, and will run for thirty minutes. Everyone with a documentation-related request or complaint is invited. The meeting will be held here: https://bluejeans.com/908675367 Send documentation-related requests and complaints to me by replying to this email and CCing me at zac.dover(a)gmail.com. The next DocuBetter meeting is scheduled for: 14 Oct 2020 1630 UTC Etherpad: https://pad.ceph.com/p/Ceph_Documentation Zac's docs whiteboard: https://pad.ceph.com/p/docs_whiteboard Report Documentation Bugs: https://pad.ceph.com/p/Report_Documentation_Bugs Meeting: https://bluejeans.com/908675367

3 years, 6 months

1
0
0 0

Announcing go-ceph v0.6.0

by John Mulligan

I'm happy to announce the another release of the go-ceph API bindings. This is a regular release following our every-two-months release cadence. https://github.com/ceph/go-ceph/releases/tag/v0.6.0 Changes in the release are detailed in the link above. The bindings aim to play a similar role to the "pybind" python bindings in the ceph tree but for the Go language. These API bindings require the use of cgo. There are already a few consumers of this library in the wild, including the ceph-csi project. Specific questions, comments, bugs etc are best directed at our github issues tracker. -- John Mulligan phlogistonjohn(a)asynchrono.us jmulligan(a)redhat.com

3 years, 6 months

1
0
0 0

Building packages with Shaman

by Wido den Hollander

Hi, I have access to github.com/ceph/ceph and I've pushed a branch: https://github.com/ceph/ceph/tree/wip-rgw-placement-rule-empty I expected this to be build by Shaman, but so far it hasn't happened. Can I trigger this somehow so that I can see if my patch(es) work? Wido

3 years, 6 months

2
1
0 0

nautilus repo is locked ...

by Yuri Weinstein

And we will start QE validation soon. Thx YuriW

3 years, 6 months

1
0
0 0

10/08/2020 perf meeting is canceled

by Mark Nelson

Hi Folks, Meeting canceled this week since I'm on PTO and haven't prepped anything. :) See you next week guys! Thanks, Mark

3 years, 6 months

1
0
0 0

Re: Rook orchestrator module

by Patrick Donnelly

Adding in dev(a)ceph.io. ceph-devel is now for kernel development but I'm keeping it in the cc list because a lot of discussion already happened there. Also for those interested, there's a recording of a meeting we had on this topic here: https://www.youtube.com/watch?v=1OSQySElojg On Tue, Sep 29, 2020 at 12:32 PM Travis Nielsen <tnielsen(a)redhat.com> wrote: > > Sebastian and fellow orchestrators, > > Some questions have come up recently about issues in the Rook > orchestrator module and its state of disrepair. Patrick, Varsha, and I > have been discussing these recently as Varsha has been working on the > module. Before we fix all the issues that are being found, I want to > start a higher level conversation. I’ll join the leads meeting > tomorrow to discuss, and would be good to include in the Monday > orchestrator agenda as well, which unfortunately I haven’t been able > to attend recently... > > First, Rook is driven by the K8s APIs, including CRDs, an operator, > the CSI driver, etc. When the admin needs to configure the Ceph > cluster, they create the CRDs and other resources directly with the > K8s tools such as kubectl. Rook does everything with K8s patterns so > that the admin doesn’t need to leave their standard administration > sandbox in order to configure Rook or Ceph. If any Ceph-specific > command needs to be run, the rook toolbox can be used. However, we > prefer to avoid the toolbox for common scenarios that should have CRDs > for declaring desired state. We're at a crossroads here. Ceph is increasingly learning to manage itself with a primary goal of increasing user friendliness. Awareness of the deployment technology is key to that. > The fundamental question then is, **what scenarios require the Rook > orchestrator mgr module**? The module is not enabled by default in > Rook clusters and I am not aware of upstream users consuming it. > > The purpose of the orchestrator module was originally to provide a > common entry point either for Ceph CLI tools or the dashboard. This > would provide the constant interface to work with both Rook or cephadm > clusters. Patrick pointed out that the dashboard isn’t really a > scenario anymore for the orchestrator module. As Lenz pointed out in another reply, my understanding was wrong here. Dashboard has been using the orchestrator for displaying information from the orchestrator. > If so, the only > remaining usage is for CLI tools. And if we only have the CLI > scenario, this means that the CLI commands would be run from the > toolbox. But we are trying to avoid the toolbox. We should be putting > our effort into the CRDs, CSI driver, etc. I think we need to be careful about looking at the CLI as the sole entry point for the orchestrator. The mgr modules (including the dashboard) are increasingly using the orchestrator to do tasks. As we discussed in the orchestrator meeting (youtube linked earlier in this mail) CephFS is planning these scenarios for Pacific: - mds_autoscaler plugin deploys MDS in response to file system degradation (increased max_mds, insufficient standby). Future work [1] will look at deploying MDS with more memory in response to load on the file system. (Think lots of small file systems with small MDS to start.) - volumes plugin deploys NFS clusters configured via the `ceph nfs ...` command suite. - cephfs-mirror daemons deployed to geo-replicate CephFS file systems. - (Still TBD:) volumes plugin to use an rsync container to copy data between two CephFS subvolumes (encrypted or not). Probably include RBD mounted images as source or destination, at some point. > If the orchestrator module is creating CRs, we are likely doing > something wrong. We expect the cluster admin to create CRs. > > Thus, I’d like to understand the scenarios where the rook orchestrator > module is needed. If there isn’t a need anymore since dashboard > requirements have changed, I’d propose the module can be removed. Outside of this thread I think we already decided not to do this but I'm still interested to hear everyone's thoughts. Hopefully broader exposure on dev(a)ceph.io will get us more voices. [1] https://tracker.ceph.com/issues/46680 -- Patrick Donnelly, Ph.D. He / Him / His Principal Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D

3 years, 6 months

1
0
0 0

Ceph Developer Monthly next week

by Josh Durgin

Next week CDM is on October 7, at 11am ET (3pm UTC): https://bluejeans.com/908675367/ We've got 3 topics on the agenda so far [0]: * Deploying NFS Gateway clusters with volume/nfs plugin - Varsha * Adaptive Distributed NVMe-oF Namespaces (ADNN) for Ceph and other distributed block storage systems - Scott Peterson [1] * High performance tracing - Gabi BenHanokh Feel free to add more! Josh [0] https://tracker.ceph.com/projects/ceph/wiki/CDM_07-OCT-2020 [1] https://review.spdk.io/gerrit/c/spdk/spdk/+/4325/5/module/bdev/redirector/R…

3 years, 6 months

2
1
0 0

10/01/2020 perf meeting is on at 8AM PST!

by Mark Nelson

Hi Folks, The weekly performance meeting will be starting in 30 minutes! This week we will discuss ideas for changing how pglog stores data and updated test results looking at Gabi's key recycling prototype, disabling pglog omap, and disabling pglog entirely. Hope to see you there! Etherpad: https://pad.ceph.com/p/performance_weekly Bluejeans: https://bluejeans.com/908675367 Thanks, Mark

3 years, 6 months

2
1
0 0

2024

2023

2022

2021

2020

2019

Dev October 2020