nextflow-io / nextflow-io/nextflow
Getting a IP Address of an Instance
Nobody has claimed this yet.
- #4155 by @bentsherman — closed without merging
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
I've looked trough AWS documentation and have found that its relatively simple to capture the IP of an instance:
curl http://169.254.169.254/latest/meta-data/local-ipv4
They can put that inside a process (or prior to a process) to know where its being executed. However they would like that information to be accessible from Tower, so when I click on a process I can easily find out where to log in to diagnose possible problems.
Usage scenario
They are utilizing AWS/Batch to install Nextflow and Tower to monitor the operating pipeline. Right now, I'm having trouble determining where a certain process is situated in the EC2 instances that I have running.
Suggest implementation
There us a recent PR https://github.com/nextflow-io/nextflow/pull/4155/files that does a similar process.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's linked PR 4155 and the AWS Batch/Tower integration it references. Trace how process details are exposed to Tower; done means the EC2 instance IP is visible when viewing a process so its execution host can be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, groovy
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100