[Container-tools] Deduplication problem in answers.conf{, .sample}

[Jeroen van Meeuwen]

On 2015-11-16 18:15, Ratnadeep Debnath wrote:
> Hi Jeroen,
> 

Hi Ratnadeep,

> On Mon, Nov 16, 2015 at 3:47 PM, Jeroen van Meeuwen 
> <kanarip at kanarip.ch> wrote:
>>   $ atomic install kolab/manticore-atomicapp
>>   (...snip...)
>>   $ cat answers.conf.sample
>>   [mongodb-atomicapp]
>>   mongodb_admin_password = None
>>   image = centos/mongodb-26-centos7
>>   mongodb_password = None
>>   mongodb_username = None
>>   mongodb_quiet = True
>>   mongodb_noprealloc = True
>>   mongodb_smallfiles = True
>>   mongodb_database = None
>>   [manticore-atomicapp]
>>   image = kolab/manticore
>>   mongodb_database = None
>>   mongodb_password = None
>>   mongodb_hostname = mongodb:27017
>>   mongodb_username = None
>>   [general]
>>   namespace = default
>>   provider = kubernetes
> 
> **mongodb-atomicapp** is an external Nulecule app[1], which defines
> it's own set of params. The params for **mongodb-atomicapp** has no
> knowledge and relation with params defined in **manticore-atomicapp**
> component[2]. Since, some the param names in both the components:
> mongodb-atomicapp, manticore-atomicapp are same, it seems like that
> they are redundant, but actually, they are different.
> 
>> While I would expect something closer to the following:
>> 
>>   $ atomic install projectatomic/wordpress-centos7-atomicapp
>>   (...snip...)
> 
> On the other hand, this example does not have an external dependency
> to another Nulecule application.
> 
> Currently, given the schema of answers file, and also due to the
> Nulecule spec, there isn't a way to pass params and data from one
> component to the other, or have proper inheritance of components. This
> is a limitation and we are brainstorming on how to make things better.
> 
> I hope that this answers your question. Let us know if you have any 
> doubt.
> 

I'm failing to understand the differences between [1] and [2] on the one 
hand, and [3] and [4] on the other, though. It seems to me that [3] 
establishes projectatomic/mariadb-centos7-atomicapp as an external app 
as well, and so I attempted to replicate just that.

I may have to add that I'm based off of projectatomic/atomicapp:0.1.12, 
which, judging from browsing the atomicapp code is quite different from 
"current", but I couldn't move forward to projectatomic/atomicapp:0.2.x 
as it made the ADB/CDB Vagrant image (v1.4.0) fail in miserable ways. 
Now that I have tweaked some images and workstations to work without the 
Vagrant and without the ADB/CDB, I probably should move forward -- more 
on that later tonight.

Would you have some insight on whether my expectations are wrong here, 
though? The application in question is "kolab/atomicapp". I hope to be 
able to have "kolab/atomicapp" pull in "kolab/manticore-atomicapp" which 
in turn would pull in "kolab/mongodb-centos7-atomicapp" (again, pull 
request #22 to make that "projectatomic/mongodb-centos7-atomicapp").

TIA,

> [1]:
> https://github.com/kanarip/kolab-atomicapp/blob/master/05-manticore-atomicapp/Nulecule#L12
> [2]:
> https://github.com/kanarip/kolab-atomicapp/blob/master/05-manticore-atomicapp/Nulecule#L15
> 

[3] 
https://github.com/projectatomic/nulecule-library/blob/master/wordpress-centos7-atomicapp/Nulecule#L11
[4] 
https://github.com/projectatomic/nulecule-library/blob/master/wordpress-centos7-atomicapp/Nulecule#L13

[5] 
https://github.com/projectatomic/atomicapp/blob/master/atomicapp/utils.py#L171

-- 
Regards,

-- Jeroen