OpenStack Magnum Design Specifications¶
Caracal approved specs:
Bobcat approved specs:
Ussuri approved specs:
Stein approved specs:
Queens approved specs:
Pike approved specs:
Ocata approved specs:
Pre-Ocata implemented specs:
- Asynchronous Container Operations
- Problem Description
- Use Cases
- Proposed Changes
- 1. Configurable mode of operation - async
- 2. Type of operations
- 3. Ensuring the order of execution - Phase-0
- 4. Ensuring the order of execution - phase-1
- 5. Status of progress
- Alternatives
- Data model impact
- REST API impact
- Security impact
- Notifications impact
- Other end user impact
- Performance impact
- Other deployer impact
- Developer impact
- Implementation
- Assignee(s)
- Work Items
- Dependencies
- Testing
- Documentation Impact
- References
- Container Orchestration Engine drivers
- Magnum Container Networking Model
- Magnum Container Volume Integration Model
- Containers Service
- Create a trustee user for each bay
- Web Interface for Magnum in Horizon
- Magnum and Open DC/OS Integration
- Quota for Magnum Resources
- TLS support in Magnum
- Problem Description
- Use Cases
- Proposed Changes
- 1. TLS support in Kubernetes Client Code.
- 2. Generating certificates
- 2.1. Magnum script
- 2.2. Using Barbican
- 3. TLS Support in Magnum code
- 3.1. Create secure bay
- 3.1.1. Generate certificates
- 3.1.2. Copy certificates
- 3.1.2.1. Using Magnum script
- 3.1.2.2. Using Barbican
- 3.1.3. Start a secure kube-apiserver
- 3.2. Support https
- 4. Barbican support to store certificates securely
- Data model impact
- REST API impact
- Security impact
- Notifications impact
- Other end user impact
- Performance impact
- Other deployer impact
- Developer impact
- Implementation
- Assignee(s)
- Work Items
- Dependencies
- Testing
- Documentation Impact
- References
