2018-10-06 03:32:43 +00:00
|
|
|
package docklog
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
Use init to handle plugin invocation
Currently, nomad "plugin" processes (e.g. executor, logmon, docker_logger) are started as CLI
commands to be handled by command CLI framework. Plugin launchers use
`discover.NomadBinary()` to identify the binary and start it.
This has few downsides: The trivial one is that when running tests, one
must re-compile the nomad binary as the tests need to invoke the nomad
executable to start plugin. This is frequently overlooked, resulting in
puzzlement.
The more significant issue with `executor` in particular is in relation
to external driver:
* Plugin must identify the path of invoking nomad binary, which is not
trivial; `discvoer.NomadBinary()` now returns the path to the plugin
rather than to nomad, preventing external drivers from launching
executors.
* The external driver may get a different version of executor than it
expects (specially if we make a binary incompatible change in future).
This commit addresses both downside by having the plugin invocation
handling through an `init()` call, similar to how libcontainer init
handler is done in [1] and recommened by libcontainer [2]. `init()`
will be invoked and handled properly in tests and external drivers.
For external drivers, this change will cause external drivers to launch
the executor that's compiled against.
There a are a couple of downsides to this approach:
* These specific packages (i.e executor, logmon, and dockerlog) need to
be careful in use of `init()`, package initializers. Must avoid having
command execution rely on any other init in the package. I prefixed
files with `z_` (golang processes files in lexical order), but ensured
we don't depend on order.
* The command handling is spread in multiple packages making it a bit
less obvious how plugin starts are handled.
[1] drivers/shared/executor/libcontainer_nsenter_linux.go
[2] https://github.com/opencontainers/runc/tree/eb4aeed24ffbf8e2d740fafea39d91faa0ee84d0/libcontainer#using-libcontainer
2019-05-13 15:59:52 +00:00
|
|
|
"os"
|
2018-10-06 03:32:43 +00:00
|
|
|
"os/exec"
|
|
|
|
|
|
|
|
hclog "github.com/hashicorp/go-hclog"
|
|
|
|
plugin "github.com/hashicorp/go-plugin"
|
|
|
|
"github.com/hashicorp/nomad/drivers/docker/docklog/proto"
|
|
|
|
"github.com/hashicorp/nomad/plugins/base"
|
|
|
|
"google.golang.org/grpc"
|
|
|
|
)
|
|
|
|
|
2018-11-06 05:39:00 +00:00
|
|
|
const PluginName = "docker_logger"
|
2018-10-16 17:49:50 +00:00
|
|
|
|
|
|
|
// LaunchDockerLogger launches an instance of DockerLogger
|
|
|
|
func LaunchDockerLogger(logger hclog.Logger) (DockerLogger, *plugin.Client, error) {
|
2018-11-06 05:39:00 +00:00
|
|
|
logger = logger.Named(PluginName)
|
Use init to handle plugin invocation
Currently, nomad "plugin" processes (e.g. executor, logmon, docker_logger) are started as CLI
commands to be handled by command CLI framework. Plugin launchers use
`discover.NomadBinary()` to identify the binary and start it.
This has few downsides: The trivial one is that when running tests, one
must re-compile the nomad binary as the tests need to invoke the nomad
executable to start plugin. This is frequently overlooked, resulting in
puzzlement.
The more significant issue with `executor` in particular is in relation
to external driver:
* Plugin must identify the path of invoking nomad binary, which is not
trivial; `discvoer.NomadBinary()` now returns the path to the plugin
rather than to nomad, preventing external drivers from launching
executors.
* The external driver may get a different version of executor than it
expects (specially if we make a binary incompatible change in future).
This commit addresses both downside by having the plugin invocation
handling through an `init()` call, similar to how libcontainer init
handler is done in [1] and recommened by libcontainer [2]. `init()`
will be invoked and handled properly in tests and external drivers.
For external drivers, this change will cause external drivers to launch
the executor that's compiled against.
There a are a couple of downsides to this approach:
* These specific packages (i.e executor, logmon, and dockerlog) need to
be careful in use of `init()`, package initializers. Must avoid having
command execution rely on any other init in the package. I prefixed
files with `z_` (golang processes files in lexical order), but ensured
we don't depend on order.
* The command handling is spread in multiple packages making it a bit
less obvious how plugin starts are handled.
[1] drivers/shared/executor/libcontainer_nsenter_linux.go
[2] https://github.com/opencontainers/runc/tree/eb4aeed24ffbf8e2d740fafea39d91faa0ee84d0/libcontainer#using-libcontainer
2019-05-13 15:59:52 +00:00
|
|
|
bin, err := os.Executable()
|
2018-10-06 03:32:43 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
client := plugin.NewClient(&plugin.ClientConfig{
|
|
|
|
HandshakeConfig: base.Handshake,
|
|
|
|
Plugins: map[string]plugin.Plugin{
|
2018-11-12 18:51:53 +00:00
|
|
|
PluginName: &Plugin{impl: NewDockerLogger(logger)},
|
2018-10-06 03:32:43 +00:00
|
|
|
},
|
2018-11-06 05:39:00 +00:00
|
|
|
Cmd: exec.Command(bin, PluginName),
|
2018-10-06 03:32:43 +00:00
|
|
|
AllowedProtocols: []plugin.Protocol{
|
|
|
|
plugin.ProtocolGRPC,
|
|
|
|
},
|
2019-01-09 23:06:58 +00:00
|
|
|
Logger: logger,
|
2018-10-06 03:32:43 +00:00
|
|
|
})
|
|
|
|
|
|
|
|
rpcClient, err := client.Client()
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
2018-11-06 05:39:00 +00:00
|
|
|
raw, err := rpcClient.Dispense(PluginName)
|
2018-10-06 03:32:43 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
2018-10-16 17:49:50 +00:00
|
|
|
l := raw.(DockerLogger)
|
2018-10-06 03:32:43 +00:00
|
|
|
return l, client, nil
|
|
|
|
|
|
|
|
}
|
|
|
|
|
2018-11-12 18:51:53 +00:00
|
|
|
func ReattachDockerLogger(reattachCfg *plugin.ReattachConfig) (DockerLogger, *plugin.Client, error) {
|
|
|
|
client := plugin.NewClient(&plugin.ClientConfig{
|
|
|
|
HandshakeConfig: base.Handshake,
|
|
|
|
Plugins: map[string]plugin.Plugin{
|
|
|
|
PluginName: &Plugin{impl: NewDockerLogger(hclog.L().Named(PluginName))},
|
|
|
|
},
|
|
|
|
Reattach: reattachCfg,
|
|
|
|
AllowedProtocols: []plugin.Protocol{
|
|
|
|
plugin.ProtocolGRPC,
|
|
|
|
},
|
|
|
|
})
|
|
|
|
|
|
|
|
rpcClient, err := client.Client()
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
raw, err := rpcClient.Dispense(PluginName)
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
l := raw.(DockerLogger)
|
|
|
|
return l, client, nil
|
|
|
|
}
|
|
|
|
|
2018-10-06 03:32:43 +00:00
|
|
|
// Plugin is the go-plugin implementation
|
|
|
|
type Plugin struct {
|
|
|
|
plugin.NetRPCUnsupportedPlugin
|
2018-10-16 17:49:50 +00:00
|
|
|
impl DockerLogger
|
2018-10-06 03:32:43 +00:00
|
|
|
}
|
|
|
|
|
2018-11-06 05:39:00 +00:00
|
|
|
func NewPlugin(impl DockerLogger) *Plugin {
|
|
|
|
return &Plugin{impl: impl}
|
|
|
|
}
|
|
|
|
|
2018-10-06 03:32:43 +00:00
|
|
|
// GRPCServer registered the server side implementation with the grpc server
|
|
|
|
func (p *Plugin) GRPCServer(broker *plugin.GRPCBroker, s *grpc.Server) error {
|
2018-10-16 17:49:50 +00:00
|
|
|
proto.RegisterDockerLoggerServer(s, &dockerLoggerServer{
|
2018-10-06 03:32:43 +00:00
|
|
|
impl: p.impl,
|
|
|
|
broker: broker,
|
|
|
|
})
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// GRPCClient returns a client side implementation of the plugin
|
|
|
|
func (p *Plugin) GRPCClient(ctx context.Context, broker *plugin.GRPCBroker, c *grpc.ClientConn) (interface{}, error) {
|
2018-10-16 17:49:50 +00:00
|
|
|
return &dockerLoggerClient{client: proto.NewDockerLoggerClient(c)}, nil
|
2018-10-06 03:32:43 +00:00
|
|
|
}
|