[
https://issues.jboss.org/browse/JBTM-2267?page=com.atlassian.jira.plugin....
]
Mark Little commented on JBTM-2267:
-----------------------------------
There's no obvious place where this stuff can be checked in for now so I'll add
the information here. I'll also create a few relevant JIRAs.
First all relevant builds and files can be found
https://github.com/nmcl/docker-narayana
Start with a Fedora image.
Then using the Dockerfile run 'docker build .'
Start the image using 'docker run -i -t <id>'
The Dockerfile is basic. It uses a pre-built version of Narayana and then starts the
recovery manager and transaction manager. The resulting IOR for the transaction manager is
stored in the CosServices.cfg within the running docker image. It (or the contents) need
to be copied or made available to a client running outside of the image, so we can show
that we have a transactionmanager-as-a-service. I used git for this and pushed the
CosServices.cfg up to the aforementioned git repo, pulling it down from there to a local
fedora instance. But there has to be a better way of doing this.
Anyway, once you've got the CosServices.cfg file, use the modified TMTest client to
check to see that we can create a transaction in the running Docker image. Output should
show this to be the case, e.g., see attached image.
This is a POC. It works and demonstrates what's possible. But it needs tidying up at
least. See associated JIRAs.
Create a docker image with JTS transaction manager and recovery
manager
-----------------------------------------------------------------------
Key: JBTM-2267
URL:
https://issues.jboss.org/browse/JBTM-2267
Project: JBoss Transaction Manager
Issue Type: Task
Components: JTS
Affects Versions: 5.0.3
Reporter: Mark Little
Assignee: Mark Little
Attachments: Screen Shot 2014-11-23 at 18.35.40.png
Should help with a) using docker and b) providing transactions-as-a-service.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)