Re: next steps on "opening up the cluster"


Zachary Smith
 

All,

Sorry I wasn't on the call today, traveling in Japan now (sorry I missed you here Chris!).

I think an issue to highlight here is that we're running into very typical service provider things around effectuating access, managing capacity, good accounting/oversight, etc.  Most of these issues (especially with a wider audience) creep up after the initial access and could become a burden for the CNCF or create a negative experience for the users if not handled properly.  Given what we do at Packet, I'm intimate with some of the challenges here.

A few questions I have:

-Does the CNCF have the ability and resources to act as a service provider to its members for this?  Grant access, reset access, respond to questions of a wider audience and their users, etc? 
-Is self service an important part of the access that end user projects (and their users, developers, etc) need in order to make successful use of the resources?
-Can Packet throw its hat in the ring as a consumer of some of the resources that we would then offer out via our platform to users / organizations that CNCF approves?

At Packet we have several dozen related projects (some CNCF members, some not) that we sponsor with free on-demand bare metal infrastructure for similar goals as the CNCF, e.g. to perform scale testing, setup non VM-based workloads, to test raw networking and related stacks, etc.  So my selfish ask would be that some of this could actually end up on the CNCF cluster vs our own capacity, but only if that is deemed useful to the CNCF and it's membership goals.  The non-selfish ask is that we'd love to add some value around this granting of access, provisioning and ongoing accounting/resource management if that is of use.

I'd love to have a further chat on this subject if there is interest.

thanks!
-Zac


July 21, 2016 at 2:44 AM
I think it's important to ensure that we don't end up with projects scattered across multiple locations.

The objective should always be to put all projects on the cluster.  In my opinion, it's one of our strengths as an organization.

We currently have a multi-tenant cloud environment for provisioning VMs and a section where dedicated hardware can be leveraged.

We have contemplated the idea that we should provide $0/timed access to the multi-tenant space "the CNCF cloud" to all members.  In essence, you get a login and off you go and all dedicated hardware projects would follow the process Chris outlined.

Are we deviating from that approach?  Our we missing some execution steps to opening it up?  Does the cluster committee need to assemble to discuss how we might do this?

I've been out for a couple of weeks so I may be out of the loop.  If any of this is redundant, apologies from the clueless guy.

Jason M.
702.333.6570


On Jul 20, 2016, at 12:23 PM, NASSAUR, DOUGLAS C via cncf-toc <cncf-toc@...> wrote:

I've proposed a "reference architecture" environment people could experience by "renting" time (at $0) to illustrate cloud native vs traditional virtualization approaches like openstack. Several of us have created and would donate the illustrative solution. 

Regards, Doug

On Jul 20, 2016, at 11:24 AM, Solomon Hykes via cncf-toc <cncf-toc@...> wrote:

This would be very useful for the Docker developers as well! They would love to have access too, would that be ok?

On Wednesday, July 20, 2016, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

yes it could


On Wed, 20 Jul 2016, 17:04 Diane Mueller-Klingspor, <dmueller@...> wrote:
All,

The Fedora team has been asking for access to the cncf cluster for some testing of their Fedora cloud projects. Could this "opening" up include them as a potential guest on the cluster? 

Diane Mueller 
Director, Community Development
Red Hat OpenShift
@openshiftcommon
(604) 765 3635


On Wed, Jul 20, 2016 at 8:54 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
Have the folks apply for cluster access here by creating an issue and filling out the template:

On Wed, Jul 20, 2016 at 10:52 AM, Alexis Richardson <alexis@...> wrote:
Hi all,

Thanks for supporting Camille's idea on widening the availability of
the CNCF Cluster to more open source projects!

Towards NEXT STEPS:

1) Camille please let ZK team know the answer is Yes.  What is needed next?

2) Dan & Chris --- what does CNCF need to do, in order to open this
up?  Do we want to publish info on our website for example?

3) Please could TOC people who want to help or "get involved" speak up
on this thread.

a



--
Chris Aniszczyk (@cra) | +1-512-961-6719

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc




--
Kind Regards,

Diane Mueller
Director, Community Development
Red Hat OpenShift
@openshiftcommons

We have more in Common than you know, learn more at http://commons.openshift.org

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
CONFIDENTIAL INFORMATION

This email message, its chain, and any attachments: (a) may include proprietary information, trade secrets, confidential information and/or other protected information ("Confidential Information") which are hereby labeled as Confidential for protection purposes, (b) is sent to you in confidence with a reasonable expectation of privacy, (c) may be protected by confidentiality agreements requiring this notice and/or identification, and (d) is not intended for transmission to, or receipt by unauthorized persons. If you are not the intended recipient, please notify the sender immediately by telephone or by replying to this message. Please then delete this message, any attachments, chains, copies or portions from your system(s). Thank you.

CONFIDENTIAL INFORMATION

This email message, its chain, and any attachments: (a) may include proprietary information, trade secrets, confidential information and/or other protected information ("Confidential Information") which are hereby labeled as Confidential for protection purposes, (b) is sent to you in confidence with a reasonable expectation of privacy, (c) may be protected by confidentiality agreements requiring this notice and/or identification, and (d) is not intended for transmission to, or receipt by unauthorized persons. If you are not the intended recipient, please notify the sender immediately by telephone or by replying to this message. Please then delete this message, any attachments, chains, copies or portions from your system(s). Thank you.

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
July 21, 2016 at 12:54 AM
Have the folks apply for cluster access here by creating an issue and filling out the template:




--
Chris Aniszczyk (@cra) | +1-512-961-6719
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
July 21, 2016 at 12:52 AM
Hi all,

Thanks for supporting Camille's idea on widening the availability of
the CNCF Cluster to more open source projects!

Towards NEXT STEPS:

1) Camille please let ZK team know the answer is Yes. What is needed next?

2) Dan & Chris --- what does CNCF need to do, in order to open this
up? Do we want to publish info on our website for example?

3) Please could TOC people who want to help or "get involved" speak up
on this thread.

a
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

--
Zachary Smith, CEO at Packet
+1 212.812.4178

Join cncf-toc@lists.cncf.io to automatically receive all group messages.