Updating files in k/community/contributors/devel that SIG Architecture owns

12 views
Skip to first unread message

Eduar Tua

unread,
Jan 17, 2019, 4:55:13 PM1/17/19
to kubernetes-sig-architecture
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

Brian Grant

unread,
Jan 17, 2019, 5:41:14 PM1/17/19
to Eduar Tua, kubernetes-sig-architecture
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To post to this group, send email to kubernetes-si...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/c6040971-8d6d-4f7e-9be5-6dbff9f002f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Eduar Tua

unread,
Jan 18, 2019, 2:03:23 PM1/18/19
to Brian Grant, kubernetes-sig-architecture
Thank you. I'll update the issue and move files you mentioned.
--

Eduar Tua

Eduar Tua

unread,
Jan 21, 2019, 12:28:16 PM1/21/19
to kubernetes-sig-architecture
I just updated the issue and moved files. PR


On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

Eduar Tua

unread,
Jan 21, 2019, 1:35:48 PM1/21/19
to kubernetes-sig-architecture
Hi Brian, someone wrote this 
  1. mesos-style.md - is this even still valid? We moved mesos out a long time ago
Should we delete it?

On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

David Oppenheimer

unread,
Jan 21, 2019, 4:23:57 PM1/21/19
to Eduar Tua, kubernetes-sig-architecture
On Mon, Jan 21, 2019 at 10:35 AM Eduar Tua <edua...@gmail.com> wrote:
Hi Brian, someone wrote this 
  1. mesos-style.md - is this even still valid? We moved mesos out a long time ago
Should we delete it?

I wrote this doc, very early in the project's history. (Unfortunately I put neither my name nor a date on it; sigh.)

It is unrelated to, and pre-dated, the work to integrate Mesos with Kubernetes. It was describing how you could use a combination of a custom controller, (optionally) a custom scheduler, and what I called an "API server plugin" (which appears to be very roughly equivalent to today's aggregated/extension API server) to build the functional equivalent of a Mesos framework in Kubernetes. In a sense it foreshadowed the "operator model," though much more heavyweight, more about running the application than managing the application, and much less practical since it pre-dated TPRs/CRDs.

I'm fine with deleting it. It was interesting in an era when people were writing tons of blog posts about why the decentralized Mesos scheduling/application orchestration approach was better than Kubernetes; the point was that actually you can use Kubernetes to build the Mesos model. If I ever were to get some free time, I would just write an updated version as a blog post or something like that.
 

On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.

To post to this group, send email to kubernetes-si...@googlegroups.com.

Eduar Tua

unread,
Jan 21, 2019, 4:45:09 PM1/21/19
to kubernetes-sig-architecture
Thank you David. I think this document has valuable information for developers coming from Mesos. If you think we can move it somewhere else let me know.


On Monday, January 21, 2019 at 3:23:57 PM UTC-6, David Oppenheimer wrote:
On Mon, Jan 21, 2019 at 10:35 AM Eduar Tua <edua...@gmail.com> wrote:
Hi Brian, someone wrote this 
  1. mesos-style.md - is this even still valid? We moved mesos out a long time ago
Should we delete it?

I wrote this doc, very early in the project's history. (Unfortunately I put neither my name nor a date on it; sigh.)

It is unrelated to, and pre-dated, the work to integrate Mesos with Kubernetes. It was describing how you could use a combination of a custom controller, (optionally) a custom scheduler, and what I called an "API server plugin" (which appears to be very roughly equivalent to today's aggregated/extension API server) to build the functional equivalent of a Mesos framework in Kubernetes. In a sense it foreshadowed the "operator model," though much more heavyweight, more about running the application than managing the application, and much less practical since it pre-dated TPRs/CRDs.

I'm fine with deleting it. It was interesting in an era when people were writing tons of blog posts about why the decentralized Mesos scheduling/application orchestration approach was better than Kubernetes; the point was that actually you can use Kubernetes to build the Mesos model. If I ever were to get some free time, I would just write an updated version as a blog post or something like that.
 

On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

David Oppenheimer

unread,
Jan 21, 2019, 4:50:04 PM1/21/19
to Eduar Tua, kubernetes-sig-architecture
On Mon, Jan 21, 2019 at 1:45 PM Eduar Tua <edua...@gmail.com> wrote:
Thank you David. I think this document has valuable information for developers coming from Mesos. If you think we can move it somewhere else let me know.

In the current form it will probably do more harm than good since it refers to a non-existant concept ("API server plugin"). I'm fine with deleting it, and I can write an updated version some time when I get a chance. If you prefer to move it, feel free, but I'm not very familiar with the layout of the documentation and proposal related repos these days so can't concretely suggest where to move it.
 

On Monday, January 21, 2019 at 3:23:57 PM UTC-6, David Oppenheimer wrote:
On Mon, Jan 21, 2019 at 10:35 AM Eduar Tua <edua...@gmail.com> wrote:
Hi Brian, someone wrote this 
  1. mesos-style.md - is this even still valid? We moved mesos out a long time ago
Should we delete it?

I wrote this doc, very early in the project's history. (Unfortunately I put neither my name nor a date on it; sigh.)

It is unrelated to, and pre-dated, the work to integrate Mesos with Kubernetes. It was describing how you could use a combination of a custom controller, (optionally) a custom scheduler, and what I called an "API server plugin" (which appears to be very roughly equivalent to today's aggregated/extension API server) to build the functional equivalent of a Mesos framework in Kubernetes. In a sense it foreshadowed the "operator model," though much more heavyweight, more about running the application than managing the application, and much less practical since it pre-dated TPRs/CRDs.

I'm fine with deleting it. It was interesting in an era when people were writing tons of blog posts about why the decentralized Mesos scheduling/application orchestration approach was better than Kubernetes; the point was that actually you can use Kubernetes to build the Mesos model. If I ever were to get some free time, I would just write an updated version as a blog post or something like that.
 

On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.

To post to this group, send email to kubernetes-si...@googlegroups.com.

Eduar Tua

unread,
Jan 21, 2019, 4:52:27 PM1/21/19
to kubernetes-sig-architecture
I will delete it.

Thank you.


On Monday, January 21, 2019 at 3:50:04 PM UTC-6, David Oppenheimer wrote:
On Mon, Jan 21, 2019 at 1:45 PM Eduar Tua <edua...@gmail.com> wrote:
Thank you David. I think this document has valuable information for developers coming from Mesos. If you think we can move it somewhere else let me know.

In the current form it will probably do more harm than good since it refers to a non-existant concept ("API server plugin"). I'm fine with deleting it, and I can write an updated version some time when I get a chance. If you prefer to move it, feel free, but I'm not very familiar with the layout of the documentation and proposal related repos these days so can't concretely suggest where to move it.
 

On Monday, January 21, 2019 at 3:23:57 PM UTC-6, David Oppenheimer wrote:
On Mon, Jan 21, 2019 at 10:35 AM Eduar Tua <edua...@gmail.com> wrote:
Hi Brian, someone wrote this 
  1. mesos-style.md - is this even still valid? We moved mesos out a long time ago
Should we delete it?

I wrote this doc, very early in the project's history. (Unfortunately I put neither my name nor a date on it; sigh.)

It is unrelated to, and pre-dated, the work to integrate Mesos with Kubernetes. It was describing how you could use a combination of a custom controller, (optionally) a custom scheduler, and what I called an "API server plugin" (which appears to be very roughly equivalent to today's aggregated/extension API server) to build the functional equivalent of a Mesos framework in Kubernetes. In a sense it foreshadowed the "operator model," though much more heavyweight, more about running the application than managing the application, and much less practical since it pre-dated TPRs/CRDs.

I'm fine with deleting it. It was interesting in an era when people were writing tons of blog posts about why the decentralized Mesos scheduling/application orchestration approach was better than Kubernetes; the point was that actually you can use Kubernetes to build the Mesos model. If I ever were to get some free time, I would just write an updated version as a blog post or something like that.
 

On Thursday, January 17, 2019 at 4:41:14 PM UTC-6, Brian Grant wrote:
Thanks. Most of the SIG Arch ones are correct. I suggested some SIG changes for specific files, including at least one that wasn't in the list.

On Thu, Jan 17, 2019 at 1:55 PM Eduar Tua <edua...@gmail.com> wrote:
I filed this issue where you can see files grouped by SIGs.
Some files owned by kubernetes-sig-architecture have to be reviewed or updated. Is there anyone who wants to help in the review process? Maybe file owners.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-architecture+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages