8d9b62daf3
This commit implements Phase 2 of the CHORUS Task Execution Engine development plan, providing a comprehensive execution environment abstraction layer with Docker container sandboxing support. ## New Features ### Core Sandbox Interface - Comprehensive ExecutionSandbox interface with isolated task execution - Support for command execution, file I/O, environment management - Resource usage monitoring and sandbox lifecycle management - Standardized error handling with SandboxError types and categories ### Docker Container Sandbox Implementation - Full Docker API integration with secure container creation - Transparent repository mounting with configurable read/write access - Advanced security policies with capability dropping and privilege controls - Comprehensive resource limits (CPU, memory, disk, processes, file handles) - Support for tmpfs mounts, masked paths, and read-only bind mounts - Container lifecycle management with proper cleanup and health monitoring ### Security & Resource Management - Configurable security policies with SELinux, AppArmor, and Seccomp support - Fine-grained capability management with secure defaults - Network isolation options with configurable DNS and proxy settings - Resource monitoring with real-time CPU, memory, and network usage tracking - Comprehensive ulimits configuration for process and file handle limits ### Repository Integration - Seamless repository mounting from local paths to container workspaces - Git configuration support with user credentials and global settings - File inclusion/exclusion patterns for selective repository access - Configurable permissions and ownership for mounted repositories ### Testing Infrastructure - Comprehensive test suite with 60+ test cases covering all functionality - Docker integration tests with Alpine Linux containers (skipped in short mode) - Mock sandbox implementation for unit testing without Docker dependencies - Security policy validation tests with read-only filesystem enforcement - Resource usage monitoring and cleanup verification tests ## Technical Details ### Dependencies Added - github.com/docker/docker v28.4.0+incompatible - Docker API client - github.com/docker/go-connections v0.6.0 - Docker connection utilities - github.com/docker/go-units v0.5.0 - Docker units and formatting - Associated Docker API dependencies for complete container management ### Architecture - Interface-driven design enabling multiple sandbox implementations - Comprehensive configuration structures for all sandbox aspects - Resource usage tracking with detailed metrics collection - Error handling with retryable error classification - Proper cleanup and resource management throughout sandbox lifecycle ### Compatibility - Maintains backward compatibility with existing CHORUS architecture - Designed for future integration with Phase 3 Core Task Execution Engine - Extensible design supporting additional sandbox implementations (VM, process) This Phase 2 implementation provides the foundation for secure, isolated task execution that will be integrated with the AI model providers from Phase 1 in the upcoming Phase 3 development. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
43 lines
1.6 KiB
Go
43 lines
1.6 KiB
Go
// Copyright The OpenTelemetry Authors
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
package otel // import "go.opentelemetry.io/otel"
|
|
|
|
import (
|
|
"go.opentelemetry.io/otel/internal/global"
|
|
"go.opentelemetry.io/otel/metric"
|
|
)
|
|
|
|
// Meter returns a Meter from the global MeterProvider. The name must be the
|
|
// name of the library providing instrumentation. This name may be the same as
|
|
// the instrumented code only if that code provides built-in instrumentation.
|
|
// If the name is empty, then a implementation defined default name will be
|
|
// used instead.
|
|
//
|
|
// If this is called before a global MeterProvider is registered the returned
|
|
// Meter will be a No-op implementation of a Meter. When a global MeterProvider
|
|
// is registered for the first time, the returned Meter, and all the
|
|
// instruments it has created or will create, are recreated automatically from
|
|
// the new MeterProvider.
|
|
//
|
|
// This is short for GetMeterProvider().Meter(name).
|
|
func Meter(name string, opts ...metric.MeterOption) metric.Meter {
|
|
return GetMeterProvider().Meter(name, opts...)
|
|
}
|
|
|
|
// GetMeterProvider returns the registered global meter provider.
|
|
//
|
|
// If no global GetMeterProvider has been registered, a No-op GetMeterProvider
|
|
// implementation is returned. When a global GetMeterProvider is registered for
|
|
// the first time, the returned GetMeterProvider, and all the Meters it has
|
|
// created or will create, are recreated automatically from the new
|
|
// GetMeterProvider.
|
|
func GetMeterProvider() metric.MeterProvider {
|
|
return global.MeterProvider()
|
|
}
|
|
|
|
// SetMeterProvider registers mp as the global MeterProvider.
|
|
func SetMeterProvider(mp metric.MeterProvider) {
|
|
global.SetMeterProvider(mp)
|
|
}
|