On Mon, Jul 22, 2019 at 4:02 PM Justin Cook wrote:
> On 22 Jul 2019, 12:24 +0100, Daniel Comnea , wrote:
>
> I totally agree with that but let's do a quick reality check taking
> example some IRC channels, shall we?
>
>- ansible IRC channel doesn't log the conversation - does the comments
>
I tried FCoS prior to the release by using the assembler on github.
Too much secret sauce in how to actually construct an image. I
thought atomic was much more polished, not really sure what the
value-add of ignition is in this usecase. Just give me a way to build
simple image pipelines and I
On Wed, Jul 24, 2019 at 10:40 AM Michael Gugino wrote:
> I tried FCoS prior to the release by using the assembler on github.
> Too much secret sauce in how to actually construct an image. I
> thought atomic was much more polished, not really sure what the
> value-add of ignition is in this
On 24 Jul 2019, 04:57 -0500, Daniel Comnea , wrote:
> > > > >
> > > > >
> > > > > All i'm trying to say with the above is:
> > > > >
> > > > > Should we go with IRC as a form of communication we should then be
> > > > > ready to have bodies lined up to:
> > > > >
> > > > > • look after and admin
On Wed, Jul 24, 2019 at 12:18 PM Fox, Kevin M wrote:
> So, last I heard OpenShift was starting to modularize, so it could load
> the OpenShift parts as extensions to the kube-apiserver? Has this been
> completed? Maybe the idea below of being able to deploy vanilla k8s is
> workable as the
On Wed, Jul 24, 2019 at 12:45 PM Fox, Kevin M wrote:
> Ah, this raises an interesting discussion I've been wanting to have for a
> while.
>
> There are potentially lots of things you could call a distro.
>
> Most linux distro's are made up of several layers:
> 1. boot loader - components to get
All,
Could you take a minute and do this short survey for the OKD Working Group
(mtg logistics, communication channels, interest levels, feedback)
Survey link here: https://forms.gle/abEFZ6oey79jxGjJ7
We'll be holding the OKD Working Group kick-off meeting next week on July
31st at 9:00 am
Hi Diane.
Am 24.07.2019 um 19:39 schrieb Diane Mueller-Klingspor:
> All,
>
> Could you take a minute and do this short survey for the OKD Working Group
> (mtg
> logistics, communication channels, interest levels, feedback)
>
> Survey link here: https://forms.gle/abEFZ6oey79jxGjJ7
I have
> On Jul 24, 2019, at 9:14 PM, Michael Gugino wrote:
>
> I think what I'm looking for is more 'modular' rather than DIY. CVO
> would need to be adapted to separate container payload from host
> software (or use something else), and maintaining cross-distro
> machine-configs might prove tedious,
I think what I'm looking for is more 'modular' rather than DIY. CVO
would need to be adapted to separate container payload from host
software (or use something else), and maintaining cross-distro
machine-configs might prove tedious, but for the most part, rest of
everything from the k8s bins up,
I think FCoS could be a mutable detail. To start with, support for
plain-old-fedora would be helpful to make the platform more portable,
particularly the MCO and machine-api. If I had to state a goal, it
would be "Bring OKD to the largest possible range of linux distros to
become the defacto
11 matches
Mail list logo
