Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SPDK submodule. #1

Merged
merged 1 commit into from
May 4, 2021
Merged

Add SPDK submodule. #1

merged 1 commit into from
May 4, 2021

Conversation

sdpeters
Copy link
Contributor

@sdpeters sdpeters commented May 3, 2021

Uses a fork of the SPDK github repo, so we're free to commit branches as

needed, as in this repo. The default branch in the SPDK fork repo will be wip-ceph-nvmeof.

Signed-off-by: Scott Peterson scott.d.peterson@intel.com

@idryomov
Copy link
Contributor

idryomov commented May 4, 2021

Should this be targeted at devel instead of wip-skeleton?

@sdpeters
Copy link
Contributor Author

sdpeters commented May 4, 2021

Should this be targeted at devel instead of wip-skeleton?

That makes sense. We probably need a PR for this wip-skeleton branch then, because the devel branch seems to be empty so far.

@sdpeters sdpeters changed the base branch from wip-skeleton to devel May 4, 2021 16:30
@idryomov
Copy link
Contributor

idryomov commented May 4, 2021

Do you want to own the spdk fork? We already have one in the ceph organization which we could start using: https://github.com/ceph/spdk. Going forward we would probably want to set up some CI on the ceph side, so it might be easier to have everything in one place.

@sdpeters
Copy link
Contributor Author

sdpeters commented May 4, 2021

Do you want to own the spdk fork? We already have one in the ceph organization which we could start using: https://github.com/ceph/spdk. Going forward we would probably want to set up some CI on the ceph side, so it might be easier to have everything in one place.

We can go either way. Who's the approver for PRs to https://github.com/ceph/spdk? Can that fork repo accommodate our branches without disrupting other work?

.gitmodules Outdated Show resolved Hide resolved
@idryomov
Copy link
Contributor

idryomov commented May 4, 2021

We can go either way. Who's the approver for PRs to https://github.com/ceph/spdk? Can that fork repo accommodate our branches without disrupting other work?

I can approve and also add others as needed.

The fork hasn't been used in years so we won't disrupt anything.

@sdpeters
Copy link
Contributor Author

sdpeters commented May 4, 2021

We can go either way. Who's the approver for PRs to https://github.com/ceph/spdk? Can that fork repo accommodate our branches without disrupting other work?

I can approve and also add others as needed.

The fork hasn't been used in years so we won't disrupt anything.

OK, let me revise this patch to point to https://github.com/ceph/spdk. I'll submit a PR for https://github.com/ceph/spdk to add the wip-ceph-nvmeof branch.

@idryomov
Copy link
Contributor

idryomov commented May 4, 2021

I'd call it ceph-nvmeof, without the wip prefix, to distinguish the submodule branch from other truly WIP branches.

@sdpeters
Copy link
Contributor Author

sdpeters commented May 4, 2021

I'd call it ceph-nvmeof, without the wip prefix, to distinguish the submodule branch from other truly WIP branches.

Will do

@idryomov
Copy link
Contributor

idryomov commented May 4, 2021

I went ahead and created ceph-nvmeof branch in ceph/spdk.git so you have something to target your PR at. It is based on 20.07 as discussed.

The default branch in the SPDK fork repo will be ceph-nvmeof.

Signed-off-by: Scott Peterson <scott.d.peterson@intel.com>
@sdpeters
Copy link
Contributor Author

sdpeters commented May 4, 2021

This now refers to the ceph-nvmeof branch of the Ceph SPDK fork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants