Working from feedback on the existing implementation, we have now introduced a central metadata object to represent the lifecycle and pin the resources required to implement what people today know as containers. This includes the runtime specification and the root filesystem snapshots. We also allow arbitrary labeling of the container. Such provisions will bring the containerd definition of container closer to what is expected by users. The objects that encompass today's ContainerService, centered around the runtime, will be known as tasks. These tasks take on the existing lifecycle behavior of containerd's containers, which means that they are deleted when they exit. Largely, there are no other changes except for naming. The `Container` object will operate purely as a metadata object. No runtime state will be held on `Container`. It only informs the execution service on what is required for creating tasks and the resources in use by that container. The resources referenced by that container will be deleted when the container is deleted, if not in use. In this sense, users can create, list, label and delete containers in a similar way as they do with docker today, without the complexity of runtime locks that plagues current implementations. Signed-off-by: Stephen J Day <stephen.day@docker.com>
		
			
				
	
	
		
			81 lines
		
	
	
		
			1.5 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			81 lines
		
	
	
		
			1.5 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
package plugin
 | 
						|
 | 
						|
import (
 | 
						|
	"fmt"
 | 
						|
	"sync"
 | 
						|
 | 
						|
	"github.com/boltdb/bolt"
 | 
						|
	"github.com/containerd/containerd/content"
 | 
						|
	"github.com/containerd/containerd/snapshot"
 | 
						|
 | 
						|
	"golang.org/x/net/context"
 | 
						|
	"google.golang.org/grpc"
 | 
						|
)
 | 
						|
 | 
						|
type PluginType int
 | 
						|
 | 
						|
const (
 | 
						|
	RuntimePlugin PluginType = iota + 1
 | 
						|
	GRPCPlugin
 | 
						|
	SnapshotPlugin
 | 
						|
	TaskMonitorPlugin
 | 
						|
)
 | 
						|
 | 
						|
type Registration struct {
 | 
						|
	Type   PluginType
 | 
						|
	Config interface{}
 | 
						|
	Init   func(*InitContext) (interface{}, error)
 | 
						|
}
 | 
						|
 | 
						|
// TODO(@crosbymichael): how to we keep this struct from growing but support dependency injection for loaded plugins?
 | 
						|
type InitContext struct {
 | 
						|
	Root        string
 | 
						|
	State       string
 | 
						|
	Runtimes    map[string]Runtime
 | 
						|
	Content     content.Store
 | 
						|
	Meta        *bolt.DB
 | 
						|
	Snapshotter snapshot.Snapshotter
 | 
						|
	Config      interface{}
 | 
						|
	Context     context.Context
 | 
						|
	Monitor     TaskMonitor
 | 
						|
}
 | 
						|
 | 
						|
type Service interface {
 | 
						|
	Register(*grpc.Server) error
 | 
						|
}
 | 
						|
 | 
						|
var register = struct {
 | 
						|
	sync.Mutex
 | 
						|
	r map[string]*Registration
 | 
						|
}{
 | 
						|
	r: make(map[string]*Registration),
 | 
						|
}
 | 
						|
 | 
						|
// Load loads all plugins at the provided path into containerd
 | 
						|
func Load(path string) (err error) {
 | 
						|
	defer func() {
 | 
						|
		if v := recover(); v != nil {
 | 
						|
			rerr, ok := v.(error)
 | 
						|
			if !ok {
 | 
						|
				rerr = fmt.Errorf("%s", v)
 | 
						|
			}
 | 
						|
			err = rerr
 | 
						|
		}
 | 
						|
	}()
 | 
						|
	return loadPlugins(path)
 | 
						|
}
 | 
						|
 | 
						|
func Register(name string, r *Registration) error {
 | 
						|
	register.Lock()
 | 
						|
	defer register.Unlock()
 | 
						|
	if _, ok := register.r[name]; ok {
 | 
						|
		return fmt.Errorf("plugin already registered as %q", name)
 | 
						|
	}
 | 
						|
	register.r[name] = r
 | 
						|
	return nil
 | 
						|
}
 | 
						|
 | 
						|
func Registrations() map[string]*Registration {
 | 
						|
	return register.r
 | 
						|
}
 |