On Jun 28, 2019, at 3:38 AM, Daniel Comnea wrote:
On Fri, Jun 28, 2019 at 4:58 AM Clayton Coleman wrote:
> > On Jun 26, 2019, at 1:08 PM, Colin Walters wrote:
> >
> >
> >
> > On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote:
> >
> >
> >> Because the operating system integration is so
On Fri, Jun 28, 2019 at 4:58 AM Clayton Coleman wrote:
> > On Jun 26, 2019, at 1:08 PM, Colin Walters wrote:
> >
> >
> >
> > On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote:
> >
> >
> >> Because the operating system integration is so critical, we need to
> >> make sure that the major
Sorry for missing out the mailer by mistake, not intentional.
PSB in blue.
On Wed, Jun 26, 2019 at 10:14 PM Daniel Comnea
wrote:
>
>
> On Wed, Jun 26, 2019 at 6:09 PM Colin Walters wrote:
>
>>
>>
>> On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote:
>>
>>
>> > Because the operating
In Fedora Atomic, it was trivial to build a custom ostree image. I
would hope the same is available for the FCOS model as well.
On Wed, Jun 26, 2019 at 1:36 PM Colin Walters wrote:
>
>
>
> On Wed, Jun 26, 2019, at 1:10 PM, Colin Walters wrote:
>
> > The tricky thing here is...if we want this to
On Wed, Jun 26, 2019, at 1:10 PM, Colin Walters wrote:
> The tricky thing here is...if we want this to work the same as OpenShift 4/OCP
> with RHEL CoreOS, then what we're really talking about here is a *derivative*
> of FCOS that for example embeds the kubelet from OKD. And short term
> it
On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote:
> Because the operating system integration is so critical, we need to
> make sure that the major components (ostree, ignition, and the kubelet)
> are tied together in a CoreOS distribution that can be quickly
> refreshed with OKD -
TL:DR - I can’t even summarize this, but it’s worth it to read!
First, I’ll start this off with an apology - I intended to draft an OKD 4
proposal many months ago, but I kept pushing it back to fix “just one more
bug”, and as a result there’s been a real gap in regular summarization
across the
