Hi everyone,
We're pleased to announce that the next Cephalocon will be March 3-5 in
Seoul, South Korea!
https://ceph.com/cephalocon/seoul-2020/
The CFP for the conference is now open:
https://linuxfoundation.smapply.io/prog/cephalocon_2020
Main conference: March 4-5
Developer summit: March 3
Mark your calendars, and get your talk proposals in! The CFP will close
in early December in order to get a final schedule published in early
January.
In addition to the two day conference, we will also have a developer
summit on March 3 to take advantage of having so many developers in the
same place at the same time. The developer sessions will include video
conferencing so that remote developers will also be able to participate.
A sponsorship prospectus will be available Real Soon Now.
We hope you can join us!
FOSDEM is a free software event that offers open source communities a place to
meet, share ideas and collaborate. It is renown for being highly developer-
oriented and brings together 8000+ participants from all over the world. It
is held in the city of Brussels (Belgium).
FOSDEM 2020 will take place during the weekend of February 1st-2nd 2020. More
details about the event can be found at http://fosdem.org/
** Call For Participation
The Software Defined Storage devroom will go into it's fourth round for
talks around Open Source Software Defined Storage projects, management tools
and real world deployments.
Presentation topics could include but are not limited too:
- Your work on a SDS project like Ceph, Gluster, OpenEBS or LizardFS
- Your work on or with SDS related projects like SWIFT or Container Storage
Interface
- Management tools for SDS deployments
- Monitoring tools for SDS clusters
** Important dates:
- Nov 24th 2019: submission deadline for talk proposals
- Dec 15th 2019: announcement of the final schedule
- Feb 2nd 2020: Software Defined Storage dev room
Talk proposals will be reviewed by a steering committee:
- Niels de Vos (OpenShift Container Storage Developer - Red Hat)
- Jan Fajerski (Ceph Developer - SUSE)
- Kai Wagner (SUSE)
- Mike Perez (Ceph Community Manager, Red Hat)
Use the FOSDEM 'pentabarf' tool to submit your proposal:
https://penta.fosdem.org/submission/FOSDEM20
- If necessary, create a Pentabarf account and activate it.
Please reuse your account from previous years if you have
already created it.
https://penta.fosdem.org/user/new_account/FOSDEM20
- In the "Person" section, provide First name, Last name
(in the "General" tab), Email (in the "Contact" tab)
and Bio ("Abstract" field in the "Description" tab).
- Submit a proposal by clicking on "Create event".
- Important! Select the "Software Defined Storage devroom" track
(on the "General" tab).
- Provide the title of your talk ("Event title" in the "General" tab).
- Provide a description of the subject of the talk and the
intended audience (in the "Abstract" field of the "Description" tab)
- Provide a rough outline of the talk or goals of the session (a short
list of bullet points covering topics that will be discussed) in the
"Full description" field in the "Description" tab
- Provide an expected length of your talk in the "Duration" field. Please
consider at least 5 minutes of discussion into your proposal plus allow
5 minutes for the handover to the next presenter.
Suggested talk length would be 20+5+5 and 45+10+5 minutes. Note that
short talks have a preference so that more topics can be presented during
the day.
** Recording of talks
The FOSDEM organizers plan to have live streaming and recording fully working,
both for remote/later viewing of talks, and so that people can watch streams
in the hallways when rooms are full. This requires speakers to consent to
being recorded and streamed. If you plan to be a speaker, please understand
that by doing so you implicitly give consent for your talk to be recorded and
streamed. The recordings will be published under the same license as all
FOSDEM content (CC-BY).
Hope to hear from you soon! And please forward this announcement.
If you have any further questions, please write to the mailinglist at
storage-devroom(a)lists.fosdem.org and we will try to answer as soon as
possible.
Thanks!
Hi Haomai,
I read your below presentation:
Topic: CEPH RDMA UPDATE
Link: https://www.openfabrics.org/images/eventpresos/2017presentations/103_Ceph_H…
I want to talk about the items on page 17:
I. Work in Progress:
1. RDMA-CM for control path
[Changcheng]:
Do you also prefer that we need use RDMA-CM for connection management?
1) Support multiple devices
[Changcheng]:
Do you mean seperate public & cluster network and use both RDMA on public & cluster network?
Currently, Ceph could work under RDMA with below solution:
a. Make no difference between public & cluster network, both use the same RDMA device port for RDMA messenger.
OR
b. Public network is based on TCP posix and cluster network is running on RDMA.
2) Enable unified ceph.conf for all ceph nodes
[Changcheng]:
Do you mean that in some node, ceph need set different RDMA device port to be used?
2. Ceph replication Zero-copy
1) Reduce number of memcpy by half by re-using data buffers on primary OSD
[Changcheng]:
What does it mean? Any technical sharing about this iteam?
3. Tx zero-copy
Avoid copy out by using reged memory
[Changcheng]:
I've read the code, the function:tx_copy_chunk will copy data to segmented chunk to be sent. How do you solve the zero-copy problem?
II. ToDo:
1. Use RDMA Read/Write for better memory utilization
[Changcheng]:
Any plan to implement RDMA Read/Write? How to solve the compatiblity problem since the previous implementation is based on RC-Send/RC-Recv?
2. ODP - On demand paging
[Changcheng]:
Do you mean that "the registered Memory Region is pinned to physical page and can't be swapped out" problem?
3. Erasure-coding using HW offload.
[Changcheng]:
Is this related with RDMA NIC?
B.R.
Changcheng
recently I installed Hadoop and other frameworks such as
Hive/TPCDS/TeraGen/SPARK into container, and configure it to work with S3.
thus, its possible to access the same S3-data via all of those utilities.
the container resides on docker-hub (in order to download it, all it needs
is to run-it)
attached document describing the container content and how to use it.
https://docs.google.com/document/d/1v5jiarEK6CEU0cstBjpyQ8T5ucTF7LWSwHe-Fct…
will appreciate your comments.
Gal.
On Mon, 18 Nov 2019, Rui Chang (Arm Technology China) wrote:
> Hi,
>
> When I use following command to show osd status in json format, it seems it does not give the result in json format. Is it a bug? This blocks the osd creation using ceph-deploy which checks the output.
>
> root@ceph_deploy_test_3:/etc/ceph# /usr/bin/ceph --cluster=ceph osd stat --format=json
>
> 61110
>
> The OS I use is Ubuntu 18.04, and the ceph is 15.xxx built from ceph master branch.
Yeah. This was just fixed and the backport is merged.. it should be in
the next nautilus release.
https://github.com/ceph/ceph/pull/31399
>
> Regards,
> Rui
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
- ceph-maintainer
On Mon, Nov 18, 2019 at 5:28 PM Rui Chang (Arm Technology China)
<Rui.Chang(a)arm.com> wrote:
>
> Hi,
>
>
>
> When I use following command to show osd status in json format, it seems it does not give the result in json format. Is it a bug? This blocks the osd creation using ceph-deploy which checks the output.
>
>
>
> root@ceph_deploy_test_3:/etc/ceph# /usr/bin/ceph --cluster=ceph osd stat --format=json
>
this issue was already addressed by https://github.com/ceph/ceph/pull/31399.
>
>
> 61110
>
>
>
> The OS I use is Ubuntu 18.04, and the ceph is 15.xxx built from ceph master branch.
>
>
>
> Regards,
>
> Rui
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> _______________________________________________
> Dev mailing list -- dev(a)ceph.io
> To unsubscribe send an email to dev-leave(a)ceph.io
--
Regards
Kefu Chai
Hi,
When I use following command to show osd status in json format, it seems it does not give the result in json format. Is it a bug? This blocks the osd creation using ceph-deploy which checks the output.
root@ceph_deploy_test_3:/etc/ceph# /usr/bin/ceph --cluster=ceph osd stat --format=json
61110
The OS I use is Ubuntu 18.04, and the ceph is 15.xxx built from ceph master branch.
Regards,
Rui
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
