[Container-tools] OpenShift provider and labeling artifacts

[Václav Pavlín]

On 07/01/2015 04:53 PM, Dusty Mabe wrote:
> On Wed, Jul 01, 2015 at 02:56:38PM +0200, V??clav Pavl??n wrote:
>> Hi Dusty,
> Hi Vasek,
>
>> If you would like to join Atomic App development, it would be great if you
>> could take a look at
>>
>> https://github.com/projectatomic/atomicapp/issues/114 - Label all artifacts
>> for kubernetes and openshift
> Looking at the issue this appears to enable us to have a feature that
> I considered to be *missing* when first playing with atomic. If we
> have the ability to *atomic run* then we need the ability to *atomic
> stop*. I'm definitely interested in having this as a feature.
The stop is there. But it's problematic for OpenShift - I think labels 
would make it much more convenient and also would make it easy for user 
to query the state of his application in case of many 
pods/services/deploymentConfigs running on a single instance.
>
>
>> I'd like to see the whole application being labeled with a single label
>> (nulecule-$appid) or something like that. I think it should be doable for
>> both - Kubes and OSv3, but my quick try didn't lead to anything useful:( -
>> probably caused by gaps in my knowledge about kubes and OpenShift.
>>
>> Would it be possible for you to take a look at it?
> I'll take a look but I can't promise that I'll have time to work on it
> in the next few weeks. I'm training my replacement and that demands quite
> a bit of my time.
Sure, np:)

Vašek
>
> Dusty
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools

-- 

Architect - Senior Software Engineer
Developer Experience
Brno, Czech Republic
Phone: +420 739 666 824