Yep, a complete build for TAP is required before containerization.

It's the opinion of Lewis and Peter Wang that a single container for 
TAP+Distill+Elastic is likely the best bet for a releasable version of SensSoft 
that will be adoptable.

The existing containers with Distill and Elastic were built for a specific 
project and won't go to waste.

Josh

-----Original Message-----
From: Clay Gimenez (JIRA) [mailto:[email protected]]
Sent: Monday, September 26, 2016 2:58 PM
To: [email protected]
Subject: [jira] [Commented] (SENSSOFT-84) Docker Container for 
TAP+Elastic+Distill


    [ 
https://issues.apache.org/jira/browse/SENSSOFT-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523889#comment-15523889
 ]

Clay Gimenez commented on SENSSOFT-84:
--------------------------------------

Yeah we definitely want to get a Docker container set up for Tap.  We have some 
environment issues and missing features that should probably be worked out 
first though.

Do you think there's a strong case for a single parent container that includes 
everything for a one-stop solution?

Also, is there already a container for Userale's Elastic backend?  It looks 
like it might be included in Distill's?

> Docker Container for TAP+Elastic+Distill
> ----------------------------------------
>
>                 Key: SENSSOFT-84
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-84
>             Project: SensSoft
>          Issue Type: Task
>          Components: Distill, TAP
>         Environment: Docker
>            Reporter: Joshua Poore
>            Assignee: Clay Gimenez
>
> Following a discussion with Peter Wang (Continuum Analytics), it may benefit 
> us (from a community growth perspective) to containerize TAP+Distill+Elastic 
> in a single bundle. Then provide users with instructions for how to deploy 
> UserALE, and an option of deploying Distill through PIP. He really emphasized 
> that bundling as much as we can will have a large impact on how willing 
> people are to use our products.
> Also, bundle should be packaged with a neat little json blob so that TAP can 
> be experimented with.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
________________________________
 Notice: This email and any attachments may contain proprietary (Draper 
non-public) and/or export-controlled information of Draper. If you are not the 
intended recipient of this email, please immediately notify the sender by 
replying to this email and immediately destroy all copies of this email.
________________________________

Reply via email to