search

ansible / ansible-container

DEPRECATED -- Ansible Container was a tool to build Docker images and orchestrate containers using only Ansible playbooks.
GNU Lesser General Public License v3.0
2.19k stars 392 forks source link

namespace detection when using 'oc run' vs 'docker run' #395

Open jmontleon opened 7 years ago

jmontleon commented 7 years ago
ISSUE TYPE

We're trying to use ansible-container as a base for AnsibleApps used with Ansible Service Broker (names may change).

We've noticed that the default behavior when invoking with 'docker run' and providing auth information for openshift the deployment is always performed in the project_name specified in the main.yml for each openshift object.

However, when using 'oc run' we're finding deployments are being performed in the project the meta-container is running in. We're trying to understand this behavior better and whether there is something we can pass as an environment variable to manipulate which namespace the containers are deployed to.

Would someone from the ansible-container team be able to help us understand the behavior?

calfonso commented 7 years ago

@chouseknecht thoughts on this?

chouseknecht commented 7 years ago

I would say at the moment that's a flaw in Ansible Container. We made the assumption that the Ansible Container project would be deployed to OpenShift using the base project name as the namespace or project name.

The project_name, which gets passed into the generated Ansible role is set here from the base project path.

In other words, if you create an Ansible Container project called foo, later when you run the shipit command, foo becomes the OpenShift namespace or project name.

That's definitely something we can fix in the coming release. Or, if you need it right now, I don't think it would be terribly difficult to add a command line option to shipit.