[sles-beta] Discussion point,

[Darren Thompson]

Olaf

A very simple use case is using this in conjunction with containers such
that a "stateless" template is used to provision other containers which
actually provide applications. e.g. a "factory reset" container is
initially run-up and then "statefull" changes are made to the container
after that.

e.g. rather than running apache on the server OS itself, a container is
provisioned, which runs apache/web sites etc. In that way a "cleaner" host
OS is maintained and greater isolation between the "required" OS and the
"provided" application is possible.

As said, this is just a thought bubble for discussion at this time...

Darren




On 18 June 2014 16:57, Olaf Kirch <okir at suse.de> wrote:

> Hi Darren,
>
> Reading quickly through this, these ideas seem to be primarily geared
> towards client type systems. These could inherently be stateless in the
> sense that for many things, automated configuration and useful defaults go
> a long way. Anything that provides a service is inherently stateful.
> Anything that needs to trust an authentication service (such as a
> directory) needs to be stateful.
>
> The other thing that sticks out a little is this: automated provisioning
> is a continuing research topic in the communities. Puppet, chef, autoyast,
> younameit. None of this stuff is trivial. This makes me wonder what
> scenarios Lennart plans to support, specifically. Compared to the
> contenders in the provisioning area, his is either a very restricted use
> case, or he's underestimating the complexity a little.
>
> Either way, it sounds like this is really way off in the future. Maybe
> material for SLE13, but definitely not for SLE12 :-)
>
> Regards
> Olaf
>
> Am 18.06.2014 um 05:02 schrieb "Darren Thompson" <darrent at akurit.com.au>:
>
> Team
>
> I have just been reading Lennart Poettering's systemd blog and it got me
> thinking.
>
> Factory Reset, Stateless Systems, Reproducible Systems & Verifiable Systems
> http://0pointer.de/blog
> Is it worth delaying the release of SLES12 and incorporating this
> functionality as it would be a compelling reason to update or switch to
> SLES12.
>
> What are your thoughts?
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *<image003.jpg>*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
>


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140618/c3ba2362/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140618/c3ba2362/attachment.jpg>