-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update reference architecture #90
Comments
Improvements here are needed. I wonder if we're not on a path to convergence between the landscape and the reference architecture. I'd like to assist in iterating on the reference arch. |
Please let me know your interest in contributing to this work group. Slide 13 and 14 along with the landscape document are our start point. https://docs.google.com/presentation/d/1BthkP9OftIICEn1h9ML1F0TKXhaUxXILlcDpuz3Sjzg/edit#slide=id.g31fcaed9a5_0_12 |
I'd like to help out as well. |
The landscape was always designed to take it's groupings from the reference
architecture. That's still the plan going forward.
…--
Dan Kohn <dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Tue, Feb 20, 2018 at 1:03 PM, John Belamaric ***@***.***> wrote:
I'd like to help out as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AC8MBhz68308d0USu8b4S7h0f2fsK_gZks5tWwjmgaJpZM4SMQzI>
.
|
What's the goal of providing a reference architecture? Is this going to call out specific products? Would that go against the "no king makers" moto? |
@rothgar, correct. No specific products will be named in the reference architecture. Those that are in the two slides are placed there as examples to quickly convey by example what is meant by the newly proposed layers / architecture. |
The TOC approved this document as the reference architecture in November 2016: https://docs.google.com/presentation/d/1uMw2wkK0ubmc3khxqIuxK_rLK_wN89tNCnK7gDmTGR8/edit#slide=id.g15843037bc_2_6 |
Thanks for the additional context Lee and Dan |
@kenowens12 Do you want to do a call to kick off this review? |
Lets get a meeting scheduled for the next week. Please respond if your available on: please rate these options with most preferable first. |
If anyone is still working on this I would be happy to contribute. We've been looking at app dev and ops tools for awhile (on k8s) and I may have some insight or useful info to help. |
@kenowens12 I could make the Monday time at 10am PT. The other two I can't commit to but could try. |
monday at 10 |
|
So...I got slammed with P1 outages over the weekend and Monday (large change weekends suck!) How is Tuesday, May 1st at 9:30am, 10am, or 1pm PDT. |
Many of us will be at KubeCon then. Could we try the following week, please?
…--
Dan Kohn <dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Tue, Apr 24, 2018 at 1:20 PM, Ken Owens ***@***.***> wrote:
So...I got slammed with P1 outages over the weekend and Monday (large
change weekends suck!)
How is Tuesday, May 1st at 9:30am, 10am, or 1pm PDT.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AC8MBnyvOPtbJ1D_xbVgbuECOXFdcBrOks5tr17AgaJpZM4SMQzI>
.
|
I knew that @dankohn :-) I'm OOF this week so looking at the week of 5/14. Please let me know availability for the following options: 5/14 - Monday PDT |
I'm good for
…--
Dan Kohn <dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Mon, May 7, 2018 at 7:08 PM, Ken Owens ***@***.***> wrote:
I knew that @dankohn <https://github.com/dankohn> :-)
I'm OOF this week so looking at the week of 5/14.
Please let me know availability for the following options:
5/14 - Monday PDT
9:30am
10:00 am
12:00 pm
2:30 pm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AC8MBjBhkEUcx1DLd03HjCCQ0YY-PxLJks5twNPrgaJpZM4SMQzI>
.
|
Sorry, I'm good for 10, 12, and 14:30 on Monday, 5/14. Once we pin down a
time, I'll send out a meeting invite.
…--
Dan Kohn <dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Tue, May 8, 2018 at 12:03 AM, Dan Kohn ***@***.***> wrote:
I'm good for
--
Dan Kohn ***@***.***>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
On Mon, May 7, 2018 at 7:08 PM, Ken Owens ***@***.***>
wrote:
> I knew that @dankohn <https://github.com/dankohn> :-)
>
> I'm OOF this week so looking at the week of 5/14.
>
> Please let me know availability for the following options:
>
> 5/14 - Monday PDT
> 9:30am
> 10:00 am
> 12:00 pm
> 2:30 pm
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#90 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AC8MBjBhkEUcx1DLd03HjCCQ0YY-PxLJks5twNPrgaJpZM4SMQzI>
> .
>
|
I would be happy to contribute as well. |
@taylorwaggoner Could you please kick off a Doodle Poll here with several slots for this week and next? We'd like to find a recurring slot where we can do an architecture call, such as the 2nd and 4th Friday of the month. |
I like this idea the best! Thanks Dan. |
Here is the Doodle Poll: https://doodle.com/poll/6nik8mc8r56s3wu3 We also have set up a mailing list: https://lists.cncf.io/g/cncf-reference-architecture Please feel free to join, and let's please move discussion there. |
old issue, close out |
From today's TOC call there's been a desire to update the reference architecture. @kenowens12 from the @cncf/toc will be leading this effort.
The text was updated successfully, but these errors were encountered: