kubevirt / community Goto Github PK
View Code? Open in Web Editor NEWCommunity content
Home Page: https://kubevirt.io
Community content
Home Page: https://kubevirt.io
CNCF event for KubeVirt Weekly meeting is off by 1 hr ... https://www.cncf.io/calendar/
Please contact Amye Scavarda Perrin [email protected] and cc Cloud Native Computing Foundation [email protected] to have the event updated.
/kind enhancement
What happened:
Current standard of this repos main branch name master
is not respectful to some contributors and/or users of KubeVirt
What you expected to happen:
Please adjust the main branch name to main
.
Anything else we need to know?:
Currently the KubeVirt Twitter account has primary ownership set to @fabiand 's Google account within Red Hat.
We need to move primary ownership to the [email protected] Google account without losing content.
The [email protected] is managed by CNCF IT. Josh Berkus RH OSPO and myself have access to that account. Maintainers should have the ability to tweet also.
Currently the KubeVirt branded YouTube channel has primary ownership set to @fabiand 's Google account within Red Hat.
We need to move primary ownership to the [email protected] Google account without losing content.
The [email protected] is managed by CNCF IT. Josh Berkus RH OSPO and myself have access to that account.
In https://github.com/kubevirt/community/blame/master/membership_policy.md#L43
Link goes to https://github.com/kubevirt/project-infra/blob/master/github/ci/prow/files/orgs.yaml#L21
But should be https://github.com/kubevirt/project-infra/blob/main/github/ci/prow-deploy/files/orgs.yaml
Not sure if we want to keep the line number reference here. It may change infrequently, but the current line number is out of date (should be 22)
Per email to kubevirt-devel from [email protected]
Lately we've been thinking about the diversity of our project maintainers. It's easy to notice that a lot of emails come from one domain. When our project was in its infancy, that was understandable and sort of made sense. However, I'd like to think we've grown past that. We are starting to see more names on our community calls, and an ever growing number of followers on various platforms such as GitHub, Twitter or Slack. With that in mind, a topic I'd like to discuss during tomorrow's community meeting is the establishment of a documented process by which community members can get involved and become maintainers or co-owners of the KubeVirt project.
As a follow on to that, it's worth also discussing the different ways people interested in the project might be able to get involved. Some areas of responsibility might include:
* Moderating a public GitHub issue scrub
* Building the Community Meeting weekly agenda
* Slack presence -- to answer questions of other community members
* Leading or contributing towards our effort to get KubeVirt to V1
If you have any other ideas, please feel free to bring them up on this email thread or during the call!
Here's a draft proposal for what our maintainership procedures could look like:
https://docs.google.com/document/d/1sviYdFC5gXIRhc8M1nFOb1aDzyS-fmao9JjzSzdORTQ/edit#
https://docs.google.com/document/d/1N9SflndMOh9H7POvEMR__KWV--fi0e7OoTO76YcqAFs/edit
CFP: link
Status: Submitted, waiting on review
Presenter: @rthallisey
Presenter: @davidvossel
General Topic Idea Ryan and I want to present the journey of how we measured and improved KubeVirt's performance at scale. This will include details into how we approached scale testing along with how we profiled the distributed system to evaluate and improve performance.
Title: 1000s of VMs and beyond: KubeVirt performance and scale
Abstract:
Our goal is to scale KubeVirt to new levels and measure its performance and efficiency; here’s our journey to 1000s of VMs:
In this session we will uncover the tools and methodologies we used to visualize, measure, and identify KubeVirt performance bottlenecks and improve them. We'll outline how we collected baseline performance metrics under load and how changing certain code paths impacted baseline performance. From our learnings, we hope you’ll come away with an understanding of what patterns can help improve performance in your own Kubernetes controllers as well as an understanding of how to approach profiling a distributed control plane.
CPF: link
Status: Submitted
Presenter: @marceloamaral
Presenter: @rthallisey
General Topic Idea Ryan and I want to present the journey in the SIG Scalability of how we analyzed and improved KubeVirt's performance at scale, including the testing tools we have developed.
How KubeVirt Bootstrapped Our Own Performance Infrastructure
Kubernetes has extensive performance and scale testing infrastructure, but how many other cloud native projects do? Performance testing is not widely adopted because of its infrastructure, metric definition, and tooling complexity. This often leads to bad experiences for users.
KubeVirt certainly didn't have anything when we launched the project, so we formed the Performance and Scale SIG and built our own. Today, that framework allows us to verify expected system behaviors under various load conditions and prevent unexpected regressions.
This talk will share our journey in KubeVirt through our performance testing framework, defining key metrics, creating performance tests, and deeply analyzing the results. We will discuss the challenges we face using Prometheus, and finally, we will conclude the talk with a guideline on how to bootstrap your own performance infrastructure for your project.
[@kwiesmueller ] Discuss featureGates (and deprecation)
Create issue for deprecation policy
13 listed in featuregates.go… not all may be used
Please create policy in this repo. We can then link to it.
CNCF KubeVirt account currently cannot create Google groups
Please work with CNCF to enable Google groups creation for KubeVirt account
Mark DeNeve has reqs web statistics for his blog post.
He would also like a brief statement from the project to help with a promotion
We have many repos with different versions of welcome, contributing, and style guides. I would like for all of the these pages to be moved this following hierarchy to follow suit with CNCF/Kubernetes ....
kubevirt/community:
- contributors:
- README.md: https://github.com/kubernetes/community/tree/master/contributors/devel/README.md
- CONTRIBUTING.md
- example_subproject: https://github.com/kubernetes/community/tree/master/contributors/devel/sig-api-machinery
RELEASES.md
STLYE_GUIDE.md
etc
- guides: https://github.com/kubernetes/community/tree/master/contributors/guide
- automation.md: https://github.com/kubernetes/community/blob/master/contributors/devel/automation.md
- first_contribution.md: https://github.com/kubernetes/community/blob/master/contributors/guide/first-contribution.md
- owners.md: https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md
The repo page gets a stub page (example: kubernetes/apimachinary/CONTRIBUTING.md )
A secondary object is to sync these pages to the user-guide appendix
Some contents in kubevirt this repository would get more visibility if stored in the 'community' section of the main website instead of this repo.
Some things that may require community visibility outside of regular website could be kept here, but others like:
Could make better use and visibility on the website
It is with both sadness and excitement that I have to inform the community that I have resigned my position with IBM/Red Hat and with that my position as KubeVirt community organizer. My last day with IBM/Red Hat will be Nov 29. I have accepted a position at NASA Goddard Space Agency to assist in building and maintaining climate research supercomputers.
This is a great opportunity to get involved with the project. I thought the position was fun. I got to do some coding and got to do a lot of talking to people both publicly and through back channels. See pull/154 for a list of responsibilities. It is unclear if Red Hat is going to fund another position.
CFP: https://events.linuxfoundation.org/kvm-forum/
Status:
Presenter: @alicefr
Title: Introduction to KubeVirt demo plus virtual machine migration
KubeVirt Code of Conduct hasn't been reviewed since 2017.
Let's do a deep review and side-by-side comparison to CNCF/Kubernetes's CoC document. Link is here.
Datetime: 2021/10/14: 1:30-2:00pm PST
Slack super thread: https://kubernetes.slack.com/archives/C8ED7RKFE/p1631813761150900
/kind bug
Please update sigs.yaml @rthallisey
Create task list for comm mgr turnover / onboarding
Sometimes, i.e. for twitter or for the youtube channel - a generic background image is needed as a header or footer.
https://www.youtube.com/channel/UC2FH36TbZizw25pVT1P3C3g/
https://twitter.com/kubevirt
it would be nice to have a simple themed background image which can be used here and there.
Hi,
as discussed in the community meeting yesterday, I'm opening an issue here to discuss if we want to host the work I did in KubeVirt org.
The repository kubevirt-test-vm is a small golang program that helps the users to create test VMs and containers for running fio tests. The repository is self-contained, so it already has a containerdisk based on Fedora with all the needed tooling. The fio tests are containerized, and we deploy the same image directly in a container on the cluster or inside the VM.
I'd like to move the repository under KubeVirt org to have a better visibility and have the chance to use KubeVirt CI.
I have already raised the questions in kubevirt-devel and you can see there more details.
Bug scrub is starting to take 15-30 mins out of community calls. It is time to split out to a separate call with a person in charge of bug management.
Reqs for this should be easy
Review repo for offensive langauge
git grep -I -E 'master|slave|whitelist|blacklist' -- ':!vendor' ':!cluster-up' ':!cluster-sync' ':!*generated*'
Currently the cal shared on the community page (link) is a cal owned by the Red Hat org. This is going to harm incubation due diligence and so it needs to be migrated to the correct account.
Events need to be migrated to the CNCF account
The CNCF account calendar needs to be made publically viewable
The kubevirt.io/community page needs to be updated to link to the correct cal
PR #5 is concerned about adding PV based disk to VMs.
There are two issues:
The problem with 1 is that libvirtd and qemu expect the same path in their namespace. But their mount namespace is different than the pods mount namespace.
A possible solution is to expose the pod informations in the virt-handler
to allow it to share enough informations about it to allow libvirt/qemu to use the attached volumes.
Currently Red Hat KubeVirt account owns the kubevirt-devel mailing list
Move kubevirt-devel ownership to CNCF KubeVirt acount
Ensure group history IS NOT LOST
https://github.com/kubevirt/community/blob/main/design-proposals/nic-hotplug/nic-hotplug.md
I see the nic-hotplug proposal,but do not find the feature in kubevirt. How about the plan of nic-hotplug.
What: https://devconf.cz
When: Jan 28-29, 2022
Where: Brno, Czech Republic
CFP: https://cfp.devconf.info/login
/kind enhancement
Per Josh Berckus in Red Hat OSPO (Open Source Program Office) it is time to begin the process to get project KubeVirt promoted to an incubating project under the CNCF.
CNCF Technical Oversight Committee (TOC) Due Diligence doc is here
Most of these should be covered in the project proposal document. The due diligence exercise involves validating any claims made there, verifying adequate coverage of the topics, and possibly summarizing the detail where necessary.
Technical
The key high-level questions that the voting TOC members will be looking to have answered are (from the graduation criteria):
Some details that might inform the above include:
Besides the core team, how active is the surrounding community? Bug reports? Assistance to newcomers? Blog posts etc.
http://youtube.com/saiyam911 ([email protected])
KubeVirt CONTRIBUTING guides are scattered and haven't been reviewed in quiet a while.
Let's do a deep review and side-by-side comparison to CNCF/Kubernetes's CONTRIBUTING document. Link is here.
Please follow their established hierarchy when organizing the pages.
Existing documents can be deprecated with community approval
ATO Call for Papers - link
ATO Talk Topics - link
TIPS for getting proposal accepted - https://opensource.com/article/20/5/tips-conference-proposals
Organizer: @mazzystr
Presenter: @stu-gott
Use Raspberry Pi 4 hardware to build Kubernetes / Rancher K3S multinode cluster with KubeVirt layered on. Apply mixed workloads to the cluster.
Demonstrate running mixed workloads.
Topic: All Things Open 2021
Time: Apr 29, 2021 07:00 Pacific Time (US and Canada)
Join Zoom Meeting
https://zoom.us/j/3205945033
Federico Gimenez provided a video describing KubeVirt CI infrastructure. Please upload to KubeVirt YouTube channel
Title: KubeVirt CI Infrastrcture Overview
Description: Brief overview of the infrastructure we use to run KubeVirt CI jobs, how it has changed over the last few months and the short/medium term improvements we are working on. Includes a small demo about our usage of Bazel gitops rules to manage components on CI/CD pipelines
Need CNCF event for KubeVirt SIG Performance & Scale Weekly meeting ... https://www.cncf.io/calendar/
Please contact Amye Scavarda Perrin [email protected] and cc Cloud Native Computing Foundation [email protected] to have the event added.
What: https://devconf.cz
When: Jan 28-29, 2022
Where: Brno, Czech Republic
CFP: https://cfp.devconf.info/login
Migrate KubeVirt related docs from Red Hat gdrive to CNCF / gdrive
These documents should not be isolated under the Red Hat umbrella. They need to be community accessible.
Showing how all the components are intended to play together.
Pobox has invoiced on July 3. They're ready to be paid.
The KubeVirt community would like to create a survey for users to get a better gauge on various aspects of the project.
Develop survey here
Project page: https://bestpractices.coreinfrastructure.org/en/projects/2805
The Linux Foundation (LF) Core Infrastructure Initiative (CII) Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices. Projects can voluntarily self-certify, at no cost, by using this web application to explain how they follow each best practice. The CII Best Practices Badge is inspired by the many badges available to projects on GitHub. Consumers of the badge can quickly assess which FLOSS projects are following best practices and as a result are more likely to produce higher-quality secure software.
More details at ... https://bestpractices.coreinfrastructure.org/en
KubeVirt has stagnated on it's trek toward a gold medal. Let's get things moving again.
Template is here
Community will need to approve
/kind enhancement
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.