[Container-tools] How adb and Nulecule fit together?

[Lalatendu Mohanty]

On 02/04/2016 03:56 PM, Suraj Deshmukh wrote:
> ----- Original Message -----
>> From: "Lalatendu Mohanty" <lmohanty at redhat.com>
>> To: "Suraj Deshmukh" <sdeshmuk at redhat.com>, container-tools at redhat.com
>> Sent: Thursday, February 4, 2016 11:38:46 AM
>> Subject: Re: [Container-tools] How adb and Nulecule fit together?
>>
>> On 02/03/2016 03:59 PM, Suraj Deshmukh wrote:
>>> Hi,
>>>
>>> How adb and Nulecule fit together?
>>>
>>> I have tried using adb in the form of Vagrant box, from eclipse plugin
>>> and it works fine. The part that I am still confused is how does 'adb'
>>> and 'Nulecule' come together into picture.
>>>
>>> Once there is adb Vagrant box up and running, what do I do to run a
>>> nuleculized application? Does the adb Vagrant box has all the required
>>> applications installed(e.g. atomic) or services up and running(e.g.
>>> kubernetes)? Or do I have to do it manually in that Vagrant Box? How
>>> do they come into picture together?
>>>
>> ADB and Nulecule are two different projects and they have different
>> objectives.
>>
>> That being said , there is a relationship between these projects where
>> they can get benefited from each other.
>>
>> ADB as a developer tool chain, supports Nulecule and AtomicApp i.e.
>> Nulecule based are applications are first class citizen in ADB. ADB
>> provides way to quickly setup developer environments for providers which
>> Nulecule supports i.e. Kubernetes, OpenShift , Mesos etc and you should
>> be able to run Nulecule based applications in ADB successfully i.e. ADB
>> should provid all required stuff that a developer need to develop
>> Nulecule based applications and test them quickly
>>
> So in that case, why we don't have Kubernetes pre-loaded/installed into the 'adb' box? Given the situation user can choose to install it later! But since the whole point is to give everything to user out of the box without having to go through hassle of extra configurations and setup.

We have Kubernetes pre-loaded/installed in ADB box.

If you are talking about why it is not setup as a single node setup ,  
then the answer is Kubernetes, OpenShift and Mesos uses the same ports . 
So if we default to one service the user has to do firefighting to run 
other provider at this point. So to keep things simpler , all the 
provider configurations are provided as part of Vagrantfiles. If user 
wants a setup, he/she has use the specific Vagrantfile and do a vagrant up.


>
>> Thanks,
>> Lala
>>