[Container-tools] Application Entity Cockpit UI

[Stef Walter]

On 29.04.2015 09:28, Václav Pavlín wrote:
> Hello Stef,
> 
> I'll also say it - great!
> 
> Comments in-line
> 
> On 04/28/2015 05:24 PM, Christoph Görn wrote:
> Hey Stef,
>   great!! to see adoption!
> 
>   I have browsed thru your feature page shortly and got a few comments
> 
>   "Phillip: Opens the Kubernetes dashboard" So to translate this to
> Nulecules land: you are assuming that the Atomicapp Phillip is going
> to deploy is enabled/is having a kubernetes provider (or atomichost as
> we sometimes call it) and therefore should be deployed via kubernetes
> dashboard.
> 
>   "We should pull the image from docker via the docker REST API, so we
> can provide intelligent data. " From Atomicapp point of view the
> pollper.io-atomicapp will download all that is required to deploy the
> app. So if you 'atomic install poppler.io-atomicapp' there should be
> no need to download anything separately to deploy the app. Not saying
> that you may not want to download that image if cockpit is going to do
> something with in.
>> atomic install will pull and unpack all the information  so if you want
>> to display anything from the metadata, you will be able to find it on
>> the disk (this might potentially change in the future, but it's how it
>> is now)
>   Question: How do we get information about what the answer file should
> look like? Best answer is: the answer file is a INI, see [1]
>> Answers can be in a any of these: INI, json, yaml - I am using Anymarkup
>> (https://github.com/bkabrda/anymarkup) which can guess format and parse
>> any of these - i.e.
> 
>> [my-app]
>> some_param = some_value
> 
>> my-app:
>>   some_param: some_value
> 
>> {
>>   "my-app": {
>>      "some_param": "some_value"
>>      }
>> }

Hmmm, yes, these are the kind of files that we would need to build UI
from and then populate and pass back to the atomicapp tooling.

But Cockpit is written in javascript and runs in the browser.

In order to parse such files, do we have to port anymarkup to
javascript? I noticed that in particular yaml is extremely complex, and
takes nearly 4000 lines of javascript of code to write a parser.

Perhaps it would be good to have a tool that we can call to convert
these arbitrary files into JSON so we can make sense of them.

Stef

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/container-tools/attachments/20150429/4668eeca/attachment.sig>