[Container-tools] "atomic projectatomic/helloapache" UX feedback

[Václav Pavlín]

On 21.5.2015 08:22, Nick Coghlan wrote:
> On 21 May 2015 at 15:44, Václav Pavlín <vpavlin at redhat.com> wrote:
>>> $ mv answers.conf.sample answers.conf
>>> $ sudoedit answers.conf
>>> [Change the provider from kubernetes to docker]
>> Yeah, helloapache does not have data for docker provider anyway so it would
>> fail with that error - any suggestion how to let the user know in advance?
> Would it be possible to use Docker image labels for this, by having
> "atomicapp build" specify in the Docker image metadata that it's a
> Nulecule deployment orchestration image and which orchestration
> providers the image supports?
Good idea, although as we build examples in Docker Hub by Automated 
Build, it would have to be specified in Dockerfile explicitly - i.e. it 
should probably go to docs and be added to examples and template. Later 
when we have DevAssistant fro Nulecule ready, it can be added 
automatically. But yes, something like

io.projectatomic.nulecule.providers = "kubernetes,docker,openshift"

could be helpful
>
> It would also be potentially handy if atomicapp could be run locally
> to see which orchestration providers were available (I'm assuming we
> don't want awareness of orchestration engines leaking into the base
> atomic command).
You can run atomicapp locally: 
https://github.com/projectatomic/atomicapp#developers
>
> Cheers,
> Nick.
>

-- 

Lead Infrastructure Engineer
Developer Experience
Brno, Czech Republic
Phone: +420 739 666 824