Hi Alan, Thanks for the input. Yes you are very correct. Activity configuration has the information of the container. But what I meant more like is, what to do ? start/stop etc. For Health check, the interface taverna already given apparently does not expect to check those individual entities separately. But more like check whether create/start/inspect (all possible activities) potentially healthy to execute as a whole. Is that correct ?
On Sun, Aug 7, 2016 at 3:39 PM, Alan Williams <alanin...@googlemail.com> wrote: > On 05-Aug-16 04:29, Nadeesh Dilanga wrote: > >> Hi, >> With the health check I hit on a road block and spent time to figure out >> how. But could not get through. Hence asking for some help. >> >> In my activity plugin, in executeAsynch(), I am reading action parameters >> from map (Map<String, T2Reference> map). (Not from JsonNode set from >> Activity.configure()). I thought that is the correct way(correct me if I >> am >> wrong) >> > > No. I think that is the right thing to do, at least for the first version > of the activity. > > ex: action=start-container and name=myTestContainer1 >> action=inspect-image and image-id=img123 >> > > From HealthCheck visit() interface, how can I get hold to this input >> parameter map similar to what I get in Activity#executeAsynch() . >> > > You cannot. There is enough information in the DockerConfiguration to so > some checks. > > Alan > >
