1 |
On Wed, Dec 02, 2015 at 10:20:33PM -0800, Zac Medico wrote: |
2 |
> On 12/02/2015 03:49 PM, William Hubbs wrote: |
3 |
> > On Tue, Dec 01, 2015 at 03:28:44PM -0600, William Hubbs wrote: |
4 |
> > Here is where my thoughts are on this now. There will be a |
5 |
> > "-containers" keyword, which will expand to list all of the containers |
6 |
> > we can detect on the operating system OpenRC is running on -- for |
7 |
> > example, on Linux it might be: |
8 |
> > |
9 |
> > "-docker -lxc -openvz -rkt -systemd-nspawn -vserver" |
10 |
> > |
11 |
> > So any time you list -containers as a keyword it would expand |
12 |
> > appropriately. |
13 |
> |
14 |
> Sounds good. |
15 |
> |
16 |
> >> OpenRC currently doesn't do any detection of virtual machines, so maybe |
17 |
> >> that could be another expansion of this -- add a keyword "vm" and |
18 |
> >> keywords for the virtual machines. |
19 |
> > |
20 |
> > VM's will be a separate project that I will look at later. |
21 |
> > |
22 |
> > Thoughts? |
23 |
> |
24 |
> How about a bare-metal keyword? |
25 |
|
26 |
In OpenRC, the keywords block services from running in the listed |
27 |
environments, so once I get the containers and vms implemented, bare |
28 |
metal would be something like: |
29 |
|
30 |
keyword -containers -vms |
31 |
|
32 |
the idea being that if it isn't a container or vm that I know how to |
33 |
detect, it is bare metal. |
34 |
|
35 |
William |