Budh Ram Gurung (BRG)

CDK 2.1 behavior: ``` $ vagrant up; vagrant service-manager status Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2.1'... ... ==> default: Copying TLS certificates to...

CDK 2.2 with `systemctl start openshift` provisioner: ``` $ vagrant up; vagrant service-manager status Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2'... ....... ==> default:...

Blocked on https://github.com/projectatomic/adb-utils/issues/194

> @budhrg If it works with systemctl we can change the Vagrant config in the respective feature files to use systemctl. At least this is better than a "random" sleep....

@hferentschik Somehow now I am not able to get `systemctl start openshift` shell provisioner running now. Even same reported by CI too https://ci.centos.org/job/vagrant-service-manager-budh/20/console Required changes I did are https://github.com/budhrg/vagrant-service-manager/commit/5e6a3721ed2ed2cb7c0f071511b0c022ba6497f1 Locally...

@hferentschik @LalatenduMohanty I believe its a documentation issue. Any perfect place this can go which is easily visible? cc @Preeticp

@hferentschik Note is required for openshift specifically as we assume that `vagrant init projectatomic/adb` should just work with `config.servicemanager.services = 'docker'` line. This these two lines are enough for docker...

Hi @Preeticp , I will let you to decide the appropriate place to document it. Since it is more of service-manager specific, I thought better it will be here in...

> then the vagrant init method will also need to be reintroduced in the docs. Yes, we need to get clarify it first. The thing is as a developer I...

@hferentschik Are you following this issue? Can we have some conclusion here?