|
Erin,
Which public mailing list are you referring to?
Thanks,
Matt
On Wed, Mar 11, 2020, at 12:06 PM, Erin Boyd wrote:
Kris/Matt,
Can we please move all these discussions to the public mailing list and/or a PR for sandbox? Now that the repo has been made public, let's invite the other interested parties that aren't necessarily subscribed to the TOC mailing list to participate.
Thanks,
Erin
On Wed, Mar 11, 2020 at 10:03 AM Kris Nova < kris.nova@...> wrote: Matt - yes that is the point of the Monday call at 9am Pacific
Would you or anyone else care to join?
On Wed, Mar 11, 2020 at 8:14 AM Matt Farina < matt@...> wrote:
Kris,
Did the Falco and OPA folks want to talk about this together prior to coming to a CNCF call? Possibly to prepare for the CNCF call.
- Matt
On Wed, Mar 11, 2020, at 10:55 AM, Kris Nova wrote:
So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!
On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote:
Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
--
Kris Nova
Chief Open Source Advocate
85 2nd Street
San Francisco, CA 94105
--
Kris Nova
Chief Open Source Advocate
85 2nd Street
San Francisco, CA 94105
|
|
|
Kris/Matt, Can we please move all these discussions to the public mailing list and/or a PR for sandbox? Now that the repo has been made public, let's invite the other interested parties that aren't necessarily subscribed to the TOC mailing list to participate. Thanks, Erin
On Wed, Mar 11, 2020 at 10:03 AM Kris Nova < kris.nova@...> wrote: Matt - yes that is the point of the Monday call at 9am Pacific
Would you or anyone else care to join?
On Wed, Mar 11, 2020 at 8:14 AM Matt Farina < matt@...> wrote: Kris,
Did the Falco and OPA folks want to talk about this together prior to coming to a CNCF call? Possibly to prepare for the CNCF call.
- Matt
On Wed, Mar 11, 2020, at 10:55 AM, Kris Nova wrote:
So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!
On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote:
Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
--
Kris Nova
Chief Open Source Advocate
85 2nd Street
San Francisco, CA 94105
--
Kris Nova Chief Open Source Advocate
85 2nd Street San Francisco, CA 94105
|
|
|
Kris Nova <kris.nova@...>
Matt - yes that is the point of the Monday call at 9am Pacific
Would you or anyone else care to join?
On Wed, Mar 11, 2020 at 8:14 AM Matt Farina < matt@...> wrote: Kris,
Did the Falco and OPA folks want to talk about this together prior to coming to a CNCF call? Possibly to prepare for the CNCF call.
- Matt
On Wed, Mar 11, 2020, at 10:55 AM, Kris Nova wrote:
So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!
On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote:
Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
--
Kris Nova
Chief Open Source Advocate
85 2nd Street
San Francisco, CA 94105
-- Kris Nova Chief Open Source Advocate
85 2nd Street San Francisco, CA 94105
|
|
|
Kris,
Did the Falco and OPA folks want to talk about this together prior to coming to a CNCF call? Possibly to prepare for the CNCF call.
- Matt
On Wed, Mar 11, 2020, at 10:55 AM, Kris Nova wrote:
So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!
On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote:
Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
--
Kris Nova
Chief Open Source Advocate
85 2nd Street
San Francisco, CA 94105
|
|
|
I'm available then and also during the TOC meeting. If you decide to expand Monday's meeting (or would like me to attend even if it's not expanded), I'd love an invite!
On Wed, Mar 11, 2020 at 10:57 AM Kris Nova < kris.nova@...> wrote: So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
Excited to see this. The sandbox criteria ( https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon! On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote: Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
--
Kris Nova Chief Open Source Advocate
85 2nd Street San Francisco, CA 94105
|
|
|
Kris Nova <kris.nova@...>
So we set up a call next Monday morning with Falco + OPA to discuss this. Looks like a lot of this has been happening without our communities involved. Should we all join forces for a CNCF wide call here?
Right now we are scheduled for Monday the 16th at 9am Pacific
On Wed, Mar 11, 2020 at 7:26 AM Jeyappragash Jeyakeerthi < jj@...> wrote:
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
Excited to see this. The sandbox criteria ( https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon! On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote: Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
-- Kris Nova Chief Open Source Advocate
85 2nd Street San Francisco, CA 94105
|
|
|
toggle quoted messageShow quoted text
On Wed, Mar 11, 2020, 7:48 PM Liz Rice < liz@...> wrote: Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
Excited to see this. The sandbox criteria ( https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon! On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote: Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
|
|
|
Thanks Dan & Matt for getting this public!
We had a brief discussion on this in the closed TOC call yesterday, and it’s clear that many TOC members have questions and ideas around this. We are suggesting a public call with Dan, Matt, Gerred and whoever else are the interested parties (possibly in next week’s TOC meeting slot). The strategy behind the distribution and discovery of artifacts is extremely important for the whole community.
On 11 Mar 2020, at 13:05, Gerred Dillon < hello@...> wrote:
Excited to see this. The sandbox criteria ( https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon! On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote: Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. For example, this could include Helm charts, Falco configurations, and Open Policy Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The CNCF Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io, is currently in development in a pre-alpha state. Support for Helm charts is in development with plans to support more projects to follow. Pull requests, especially those to support other CNCF projects, are welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
|
|
|
Excited to see this. The sandbox criteria ( https://www.cncf.io/sandbox-projects/) (point 3 specifically) states:
3. Projects commissioned or sanctioned by the CNCF, including initial code for CNCF WG collaborations, and “experimental” projects
Following this, I would suggest to the TOC we would proceed with moving this through the SIG process as a Sandbox project. Where I would like to understand is what is the graduation pathway for this - does it graduate to being a CNCF Service? An incubating project like any other? Furthermore, if it's a CNCF service, does it follow different requirements to leave sandbox?
I look forward to getting involved in the development and governance of this project. Thanks Dan, Matt, Cynthia, Sergio, and the Operator Framework / Helm teams for the discussion back at KubeCon!
On Tue, Mar 10, 2020 at 3:35 PM Matt Farina < matt@...> wrote: Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and
publishing packages and configurations for CNCF projects. For example,
this could include Helm charts, Falco configurations, and Open Policy
Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If
every CNCF project that needs to share artifacts creates its own Hub
this creates a fair amount of repeat work for each project and a
fractured experience for those trying to find the artifacts to consume.
The CNCF Hub attempts to solve that by providing a single experience for
consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io,
is currently in development in a pre-alpha state. Support for Helm
charts is in development with plans to support more projects to follow.
Pull requests, especially those to support other CNCF projects, are
welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
|
|
|
Hello folks, I want to share that the CNCF Hub which was alluded to in the last TOC call is now public. You can find the source at https://github.com/cncf/hub. From the README:
Hub is a web-based application that enables finding, installing, and
publishing packages and configurations for CNCF projects. For example,
this could include Helm charts, Falco configurations, and Open Policy
Agent (OPA) policies.
Discovering artifacts to use with CNCF projects can be difficult. If
every CNCF project that needs to share artifacts creates its own Hub
this creates a fair amount of repeat work for each project and a
fractured experience for those trying to find the artifacts to consume.
The CNCF Hub attempts to solve that by providing a single experience for
consumers that any CNCF project can leverage.
The project, accessible at https://hub.cncf.io,
is currently in development in a pre-alpha state. Support for Helm
charts is in development with plans to support more projects to follow.
Pull requests, especially those to support other CNCF projects, are
welcome.
I look forward to some healthy discussion over the technical bits along with how to proceed positionally with the project. For example, is this something that should be a sandbox project or a service from the CNCF? Or, something else?
For those interested in some more history and context...
At KubeCon/CloudNativeCon SD, last November, a group of us got together. That include Dan Kohn along with representatives from the Operator Framewok, KUDO, and Helm. Note, both the Operator Framework and KUDO are projects that were and are proposed for the CNCF.
After that meeting I was asked to write an initial specification to kick things off. You can read there here. The specification was started to be turned into reality by Dan through Cynthia and Sergio.
For those who might wonder why this was not more public sooner... the plan was to do so but the virus impact on operations, like the movement of conferences, has impacted the schedule.
I want to thank Dan for bringing people together around this topic and working to make the idea a reality.
I'm happy to try to answer any questions. But, as I have only been involved during parts of this process (and often to a limited extent outside of the spec and initial meeting) I may have to defer to others for answers.
Regards,
Matt Farina
|
|
|
Re: CNCF TOC Survey 2020 H1 is now open, was March 6 close, now March 20
To clarify, we're now keeping the TOC survey open through March 20. I've changed the subject line to reflect.
Thank you!
On Sat, Mar 7, 2020 at 5:01 PM Vinod NA < vinod@...> wrote: Thank you, Chris, really appreciate it
I can understand the situation, thank you all for your great work through these difficult times.
Regards,
Vinod
On Sun, Mar 8, 2020 at 12:52 AM Chris Aniszczyk < caniszczyk@...> wrote: We will extend the survey another two weeks, it's been a crazy week for the organization with the postponement and cancellation of events.
On Sat, Mar 7, 2020 at 3:56 PM Vinod NA < vinod@...> wrote: Hi Amye,
I haven't received any reminders about this survey? Was the reminder sent out to everyone? If not could you please extend the survey for a week?
Thanks!
Vinod
On Mon, Feb 24, 2020 at 4:00 PM Amye Scavarda Perrin < ascavarda@...> wrote: Hi all, We're opening our TOC survey for the first half of 2020. https://www.surveymonkey.com/r/TOC-2020-H1 We'd appreciate your feedback, I'll send another reminder before this survey closes on March 6. Thanks! - amye
-- Amye Scavarda Perrin | Program Manager | amye@...
--
Chris Aniszczyk (@cra) | +1-512-961-6719
-- Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
Re: Kubernetes Event-driven Autoscaling (KEDA) is looking for TOC sponsors for its Sandbox donation
Tom Kerkhove
We already have two sponsors and looking for our last sponsor!
If you are interested or want to learn more, don't hesitate to ask me questions!
Great to hear, thank you so much Liz!
Tom Kerkhove
Azure Architect at Codit, Microsoft Azure MVP
From: Liz Rice <liz@...>
Sent: Monday, March 2, 2020 6:33:17 PM
To: Tom Kerkhove <kerkhove.tom@...>
Cc: cncf-toc@... <cncf-toc@...>
Subject: Re: [cncf-toc] Kubernetes Event-driven Autoscaling (KEDA) is looking for TOC sponsors for its Sandbox donation
I’m happy to sponsor, and have updated the PR to say so.
As a comment on the process - personally speaking, the recommendation from SIG Runtime was super-helpful and fwiw I found it helpful to watch
the SIG presentation recording. Thanks to everyone involved!
Hi,
Kubernetes Event-driven Autoscaling (KEDA) is in process of being donated as a Sandbox project to CNCF and is being recommended by SIG-Runtime.
We are actively seeking TOC sponsors so that KEDA can be accepeted - If you are interested, feel free to reach out to me or head over to our proposal on https://github.com/cncf/toc/issues/335
Thank you for your time,
Tom Kerkhove
KEDA Maintainer.
|
|
|
Re: CNCF TOC Survey 2020 H1 is now open, closes March 6
Thank you, Chris, really appreciate it
I can understand the situation, thank you all for your great work through these difficult times.
Regards,
Vinod
On Sun, Mar 8, 2020 at 12:52 AM Chris Aniszczyk < caniszczyk@...> wrote: We will extend the survey another two weeks, it's been a crazy week for the organization with the postponement and cancellation of events.
On Sat, Mar 7, 2020 at 3:56 PM Vinod NA < vinod@...> wrote: Hi Amye,
I haven't received any reminders about this survey? Was the reminder sent out to everyone? If not could you please extend the survey for a week?
Thanks!
Vinod
On Mon, Feb 24, 2020 at 4:00 PM Amye Scavarda Perrin < ascavarda@...> wrote: Hi all, We're opening our TOC survey for the first half of 2020. https://www.surveymonkey.com/r/TOC-2020-H1 We'd appreciate your feedback, I'll send another reminder before this survey closes on March 6. Thanks! - amye
-- Amye Scavarda Perrin | Program Manager | amye@...
--
Chris Aniszczyk (@cra) | +1-512-961-6719
|
|
|
Re: CNCF TOC Survey 2020 H1 is now open, closes March 6
Chris Aniszczyk
We will extend the survey another two weeks, it's been a crazy week for the organization with the postponement and cancellation of events.
On Sat, Mar 7, 2020 at 3:56 PM Vinod NA < vinod@...> wrote: Hi Amye,
I haven't received any reminders about this survey? Was the reminder sent out to everyone? If not could you please extend the survey for a week?
Thanks!
Vinod
On Mon, Feb 24, 2020 at 4:00 PM Amye Scavarda Perrin < ascavarda@...> wrote: Hi all, We're opening our TOC survey for the first half of 2020. https://www.surveymonkey.com/r/TOC-2020-H1 We'd appreciate your feedback, I'll send another reminder before this survey closes on March 6. Thanks! - amye
-- Amye Scavarda Perrin | Program Manager | amye@...
-- Chris Aniszczyk (@cra) | +1-512-961-6719
|
|
|
Re: CNCF TOC Survey 2020 H1 is now open, closes March 6
Hi Amye,
I haven't received any reminders about this survey? Was the reminder sent out to everyone? If not could you please extend the survey for a week?
Thanks!
Vinod
On Mon, Feb 24, 2020 at 4:00 PM Amye Scavarda Perrin < ascavarda@...> wrote: Hi all, We're opening our TOC survey for the first half of 2020. https://www.surveymonkey.com/r/TOC-2020-H1 We'd appreciate your feedback, I'll send another reminder before this survey closes on March 6. Thanks! - amye
-- Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
Re: Postponing KubeCon + CloudNativeCon Amsterdam
I second the ideas from Puja, Kevin and Dan. Let's see if we can
have some community events in China either online or offline.
Henry
-----------------------------
Creator and maintainer of Harbor
https://github.com/goharbor/harbor
@zhanghaining
toggle quoted messageShow quoted text
On 3/6/20 7:53 PM, Dan Kohn wrote:
Big
+1.
I and a few community members are also discussing on
organizing virtual summit for the China (or probably APAC)
Community.
Most chinese contributors would not be able to attend KubeCon
EU nor KubeCon NA, I believe people would be happy to join
even it's a virtual one.
Let's have a talk how to collaborate.
Thanks,
Kevin Wang
On Fri, Mar 6, 2020 at 05:40 PM, Puja Abbassi wrote:
We are thinking of at least organizing a virtual
Contributor Summit for China now. It's not decided, yet, but
it was proposed and we will discuss what we can do.
Puja
|
|
|
Re: Postponing KubeCon + CloudNativeCon Amsterdam
Both sounds like great suggestions :) Look forward to more input from APAC developers
On Fri, Mar 6, 2020 at 7:54 PM Dan Kohn < dan@...> wrote:
Big +1.
I and a few community members are also discussing on organizing virtual summit for the China (or probably APAC) Community.
Most chinese contributors would not be able to attend KubeCon EU nor KubeCon NA, I believe people would be happy to join even it's a virtual one.
Let's have a talk how to collaborate.
Thanks,
Kevin Wang
On Fri, Mar 6, 2020 at 05:40 PM, Puja Abbassi wrote:
We are thinking of at least organizing a virtual Contributor Summit for China now. It's not decided, yet, but it was proposed and we will discuss what we can do.
Puja
-- Zhipeng (Howard) Huang
Principle Engineer OpenStack, Kubernetes, CNCF, LF Edge, ONNX, Kubeflow, OpenSDS, Open Service Broker API, OCP, Hyperledger, ETSI, SNIA, DMTF, W3C
|
|
|
Re: Postponing KubeCon + CloudNativeCon Amsterdam
toggle quoted messageShow quoted text
Big +1.
I and a few community members are also discussing on organizing virtual summit for the China (or probably APAC) Community.
Most chinese contributors would not be able to attend KubeCon EU nor KubeCon NA, I believe people would be happy to join even it's a virtual one.
Let's have a talk how to collaborate.
Thanks,
Kevin Wang
On Fri, Mar 6, 2020 at 05:40 PM, Puja Abbassi wrote:
We are thinking of at least organizing a virtual Contributor Summit for China now. It's not decided, yet, but it was proposed and we will discuss what we can do.
Puja
|
|
|
Re: Postponing KubeCon + CloudNativeCon Amsterdam
Big +1.
I and a few community members are also discussing on organizing virtual summit for the China (or probably APAC) Community.
Most chinese contributors would not be able to attend KubeCon EU nor KubeCon NA, I believe people would be happy to join even it's a virtual one.
Let's have a talk how to collaborate.
Thanks,
Kevin Wang
toggle quoted messageShow quoted text
On Fri, Mar 6, 2020 at 05:40 PM, Puja Abbassi wrote:
We are thinking of at least organizing a virtual Contributor Summit for China now. It's not decided, yet, but it was proposed and we will discuss what we can do.
Puja
|
|
|
Re: Postponing KubeCon + CloudNativeCon Amsterdam
We are thinking of at least organizing a virtual Contributor Summit for China now. It's not decided, yet, but it was proposed and we will discuss what we can do.
Puja
|
|
|
