Many people, including me, are interested in learning Open Source technologies, including Openshift. Despite there are few documents in the Internet about creating a single-node Openshift cluster, I haven't been able to build a working lab based on that guides after a month of trying. I think it would be great if there were a one-hour workshop or lab guide which actually works at the end. So many people have access to an ESXi server so if they are able to build a small lab for themselves, They can begin to play with it at home. I can attempt to the meeting on any time, including upcoming March, 2nd. Thanks.

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

Thanks!

Regards,
Michal

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

Please add JaimeMagiera. Many thanks.

It seems the link to the okd-wg google group in https://github.com/openshift/community/projects points to the operator-framework group rather than the okd-wg ?

Invite the MetalKube team to upcoming mtg Oct 15 - Clayton/Diane - ask Russell Bryant

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

In the previous OKD WG meetings, we've discussed Packit and how we'd like to use it to make integrating OKD code into Fedora a lot smoother.

There seems to be some confusion about Packit's current state of affairs as well as its goals.

@TomasTomecek, could you comment on this (and perhaps come to an OKD WG meeting to discuss this?)

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

The OpenShift Github org will enforce use of 2FA starting Thursday Sept 12th at 19:00 UTC (15:00 ET). The following collaborators must enable 2FA or Github will automatically remove them from the organization. See: https://help.github.com/en/articles/securing-your-account-with-two-factor-authentication-2fa

@git001
@klenkes74

The card still shows details for the January meeting.

https://github.com/openshift/community/projects/1#column-6779348

Could we automate this to negate the need for manual updates?

At the last OKD WG mtg, the OKD Working Group Meeting time was set to 17:00 UTC on Tuesdays on a Bi-weekly cadence on Tuesdays.

However, the group wanted to open a discussion on the optimal time for the call.

If you have feedback on the 17:00 UTC time that we've settled on, please add a comment.

If you are okay with the 17:00 UTC time, give the issue a thumbs up in the reaction option.

Given that users are now explicitly being told to move from 3.x, does the Working Group think we should remove references to it from the OKD website and the various repo pages? The links could be replaced with a note along the lines of "OKD v.3 is no longer receiving updates. Please consider moving to OKD 4."

Accept

@BryanHepworth is your name Bryan Hepworth ?

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

Christian Glombek to present update on OKD Road Map CfA
Oct 15 2020 OKD WG Meeting

Hi, according to https://github.com/openshift/community/blob/master/CHARTER.md#role-of-sub-working-groups each sub group must have a chair, I'm applying for it. Not sure how the process is, so opening this issue.

my github uid is @runcom :)

S3 based dynamic Storage Class need to add in future release for Block and NAS.

OKD-WG Mtg: Oct 29h 17:00 UTC
Suggested Speaker: @cgruver Charro Gruver

If you look at these two repos:
Code Ready Containers: https://github.com/code-ready/crc
Single Node Cluster: https://github.com/code-ready/snc
You can get a feel for what we'll need to do to make it work with OKD4. It really should not be too big a deal. I've been playing with building crc from source and using snc to build a bundle that crc can consume. I use an openshift-installer built from the 4.1 branch with Libvirt support enabled.
There's still some rough edges, and it's currently dependent on pulling RHCOS from the official redhat registry and OCP images from either quay.io or the redhat registry.
But, there's definitely a path for us to modify it to pull FCOS qcows images for the OS and to take an OKD image from a local or public registry.

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through

requested for Oct 15th 17:00 UTC meeting
suggested speaker to request: Sam Batschelet @hexfusion

Sam, if you are available for the next OKD-WG, we'd like to have you come and present on this topic for 10-15 max at Clayton's suggestion. Could you confirm if you are available?

@LorbusChris and i realized after the charter was out that firing a PR process will cause this issue however we didn't want to pull and change the charter. We'll follow up after it gets merged.

What we should have done was to ask folks to create a github issue in this repo and either @LorbusChris or i would have created the PR and merge it to avoid asking you to rebase, sorry for inconvenience ... we are learning as we go and will try to adjust/ imrpove the process

As such for tracking purpose i'll create the request here as a github issue and then i'll personally open a PR and deal with the rebase rather than asking you to fix our own problem.

Sorry for the inconvenience and support as we learning through