GNU bug report logs -
#28128
[PATCH] scripts: system: Add support for container network sharing.
Previous Next
Reported by: Christopher Baines <mail <at> cbaines.net>
Date: Thu, 17 Aug 2017 19:14:01 UTC
Severity: normal
Tags: patch
Done: Arun Isaac <arunisaac <at> systemreboot.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
>> +(define shared-network-service-type
>> + (service-type (name 'shared-network)
>> + (extensions (list (service-extension etc-service-type identity)))
>> + (compose concatenate)
>> + (extend append)
>> + (default-value '())))
>
> I’d encourage you to add a ‘description’ field as well. :-)
Sure, will do.
> 1. ‘service-type-name’ exists for debugging purposes, and I think we
> shouldn’t rely on it at all in our code. Instead, we should
> compare service types by identity, as in:
>
> (eq? (service-kind service) foo-service-type)
Sure, will do.
> 2. The notion of “shared network” is very much a container (or VM)
> thing, so somehow it still doesn’t feel right to me that (gnu
> system) has to be aware of these special cases.
>
> I think the ‘host-database-service-type’ wouldn’t have this problem, but
> maybe it has other issues. I guess this needs more experimentation,
> sorry for not coming up with clearer ideas!
If these services (the shared-network service, the hosts-database
service or indeed any other service) had access to the operating-system
object `os', then they would be able to operate independently without
having to be extended by `essential-services'. Is this possible somehow?
Is it a good idea to give services access to the os fields?
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 6 years and 104 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.