[FOLIO-2711] Deploy mod-ldp Created: 03/Aug/20  Updated: 10/Nov/20  Resolved: 10/Nov/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Roman Ruiz-Esparza Assignee: Ian Hardy
Resolution: Done Votes: 0
Labels: devops-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-2260 Include LDP in reference environments Closed
Relates
relates to FOLIO-2664 Build mod-ldp Closed
Sprint: DevOps: Sprint 99, DevOps: Sprint 101, DevOps: Sprint 100
Development Team: FOLIO DevOps

 Description   

Now that we have the mod-ldp image built, we would like it deployed to FOLIO snapshot

Java Server: https://github.com/library-data-platform/mod-ldp
UI: https://github.com/library-data-platform/ui-ldp



 Comments   
Comment by Ian Hardy [ 03/Aug/20 ]

If this module goes into platform-complete it will show up on all builds based on that platform (folio-testing, folio-snapshot, snapshot-load).

Nassib Nassar mentioned that there's an existing LDP instnance for folio snapshot that we can connect to. Using an external instance not controlled by the FOLIO devops team does raise a few questions:

  • what happens if its unavailable
  • would there be an ldp for each build based on platform-complete?
  • how do data need to be synced between the extant ldp system and the reference environments (which are built daily).

Another approach may be to add ldp to the builds so it's running on the same system as the FOLIO builds.

Comment by Ian Hardy [ 19/Oct/20 ]

Hi Roman Ruiz-Esparza the test build is failing because there are no published ui-ldp npm's in the folio repo. I updated the Jenkinsfile to turn publishing NPMs on. We're still not getting artifacts since the tests are failing. Would you mind having a look at these tests?

https://jenkins-aws.indexdata.com/job/library-data-platform/job/ui-ldp/job/master/6/console

Comment by Ian Hardy [ 20/Oct/20 ]

Hi Roman Ruiz-Esparza, Here's a test build with these modules installed: https://folio-snapshot-test.dev.folio.org/

I see that the mod-ldp container has crashed. This is the complete log

ubuntu@ip-10-36-1-199:~$ sudo docker logs b60b1cbde94a
exec java -cp . -jar /usr/verticles/mod-ldp.jar
no main manifest attribute, in /usr/verticles/mod-ldp.jar

Perhaps the package is not getting built correctly? I get the same error when I build locally (./mvnw clean package).

Looking ahead, I'm also wondering what the mechanism for setting things like the host, port etc for the ldp instance mod-ldp will be connecting to.

Thanks,

Ian

Comment by Roman Ruiz-Esparza [ 20/Oct/20 ]

Thanks, I'll test locally and get back to you.

Comment by Roman Ruiz-Esparza [ 21/Oct/20 ]

Former user Updated pom.xml so the main class is set in the jar. A command-line option `--server.port=8090` can be used to set the port. Added this option to the readme.

Generated at Thu Feb 08 23:22:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.