Skip to content
This repository has been archived by the owner on Apr 20, 2020. It is now read-only.

[READ IF YOU USE THIS] This repository may get archived #64

Closed
phoracek opened this issue Dec 12, 2019 · 7 comments
Closed

[READ IF YOU USE THIS] This repository may get archived #64

phoracek opened this issue Dec 12, 2019 · 7 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@phoracek
Copy link
Member

Hello,

in KubeVirt we used to use kubernetes-device-plugins [1] to experiment
with device plugins to:

  • connect pod's to linux bridges
  • pass PCI devices to containers
  • expose kvm device to containers

The reality is that this repo was not touched (except for some small
adjustments) in the last 2 years. It was used only to host device plugins
used within kubevirt. Is there any reason not to make this
repository read-only? Anybody using it on this forum? If nobody votes
against it in the next two weeks, I will archive the repo (note that it won't
be deleted, just set to read-only and marked as discontinued).

Note that I don't want to archive the device-plugin-manager [1] which
seems to be vendored by folks.

Regards,
Petr

[1] https://github.com/kubevirt/device-plugin-manager

@maiqueb
Copy link

maiqueb commented Dec 31, 2019

Hi,

We're looking into this project to set the cgroups for the character device used by macvtap.

@phoracek
Copy link
Member Author

phoracek commented Jan 2, 2020

Hello @maiqueb. That means you'd need to extend this project with a new DP (I was more afraid somebody is using existing plugins).

I would advice you to create a new repository and use https://github.com/kubevirt/device-plugin-manager as your framework. All this repo adds on top of that is outdated (Go 1.9, Kubernetes 1.10) development infrastructure and some directory structure.

I'd be happy to help you set up your own repo (rather than continue maintaining this old one). Please let me know if that sounds reasonable to you.

@halkeye
Copy link

halkeye commented Jan 20, 2020

I was planning on using it for like octoprint to be able to run the host that had the 3d printer installed.

I can just fork it though if need be.

@phoracek
Copy link
Member Author

Hey @halkeye! I'd recommend you the same as to Miguel. This project is not bringing any real benefits, just maintenance burden. I'd recommend you creating your own blank new repo and using the https://github.com/kubevirt/device-plugin-manager. With that you would get minimal up-to-date project, using all the bells and whistles of the device-plugin-manager.

3D printer in Kubernetes? That's so cool! Please lemme know when you have it published ;) BTW, I'd be happy to assist you using the device-plugin-manager, just open issues on the repo.

@kubevirt-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 19, 2020
@maiqueb
Copy link

maiqueb commented Apr 20, 2020

@phoracek I think you can archive the repo, and close the issue.

@phoracek
Copy link
Member Author

Goodbye repo.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants