The below would affect adb-utils, vagrant-service-manager and adb.

Create a "proper" docker service in sccli that can then be leveraged for management by other tools.

1. Breakout docker as a proper service to be managed
  - Add configuration reporting to allow for fixes for
- DOCKER_TLS_VERIFY always set: https://github.com/projectatomic/vagrant-service-manager/issues/17 - Don't report cert info if disabled: https://github.com/projectatomic/vagrant-service-manager/issues/19
  - Add cert generation to allow for fixes for
- Calling a script to generate new certificates: https://github.com/projectatomic/vagrant-service-manager/issues/106
  - Do startup configuration allowing us to
- consider moving lines 132-136 out of https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/build_tools/kickstarts/centos-7-adb-vagrant.ks and into a service startup with sccli - More cleanly define the startup of the box (TCP vs socket) and cert generation - https://github.com/projectatomic/adb-atomic-developer-bundle/issues/266
      - https://github.com/projectatomic/vagrant-service-manager/issues/82

Opinions?

regards,

bex

_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools

Reply via email to