{"id":24989350,"url":"https://github.com/workfloworchestrator/nsi-aura","last_synced_at":"2025-03-29T11:44:14.697Z","repository":{"id":273377389,"uuid":"917624187","full_name":"workfloworchestrator/nsi-aura","owner":"workfloworchestrator","description":"ANA ultimate Requester Agent","archived":false,"fork":false,"pushed_at":"2025-03-26T17:21:28.000Z","size":1899,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":15,"default_branch":"main","last_synced_at":"2025-03-26T18:29:33.533Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/workfloworchestrator.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-01-16T10:44:51.000Z","updated_at":"2025-03-26T17:21:32.000Z","dependencies_parsed_at":"2025-03-04T09:29:07.935Z","dependency_job_id":"14ba02d3-6485-4b06-b87f-ddadb7230ec9","html_url":"https://github.com/workfloworchestrator/nsi-aura","commit_stats":null,"previous_names":["workfloworchestrator/nsi-aura"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/workfloworchestrator%2Fnsi-aura","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/workfloworchestrator%2Fnsi-aura/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/workfloworchestrator%2Fnsi-aura/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/workfloworchestrator%2Fnsi-aura/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/workfloworchestrator","download_url":"https://codeload.github.com/workfloworchestrator/nsi-aura/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246180885,"owners_count":20736459,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-02-04T12:57:06.309Z","updated_at":"2025-03-29T11:44:14.682Z","avatar_url":"https://github.com/workfloworchestrator.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# nsi-aura\n\n## Introduction\nNSI-AuRA, the Network Service Interface (NSI) ultimate Requester Agent (uRA) for the Advanced\nNorth Atlantic (ANA) consortium (https://www.anaeng.global). This is part of a project called\nANA-GRAM, the ANA Global Resource Aggregation Method, to federate the ANA trans-Atlantic links \nvia network automation. \n\n\n## Getting started\n\nClone the GitHub repository:\n\n```shell\ngit clone https://github.com/workfloworchestrator/nsi-aura.git\n```\n\nCreate a Python virtual environment, like `venv`, and install the dependencies:\n\n```shell\npython -m venv venv\n. venv/bin/activate\npip install .\n```\n\nAnd run nsi-aura:\n\n```shell\nPYTHONPATH=. python aura\n```\n\n## Development\n\nEditable install with development tools:\n\n```shell\npip install '.[dev]'\n```\n\n### Create statemachine image(s)\n\nBesides the Python packages from `dev`, also Graphviz needs to be installed and available\nin your `PATH`. Depending on the platform being used for development, use something like the following\nto install Graphviz:\n\n```shell\nbrew install graphviz\n```\n\nor\n\n```shell\napt install graphviz\n```\n\nAnd then (re)generate the image(s) in the `images` folder:\n\n```shell\npython aura/fsm.py\n```\n\n## Authors\nArno Bakker (SURF)  \nHans Trompert (SURF)\n\n## License\nApache-2.0\n\n\u003c!--\n## TODO\n\n## Name\nChoose a self-explaining name for your project.\n\n## Description\nLet people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.\n\n## Badges\nOn some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.\n\n## Visuals\nDepending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.\n\n## Installation\nWithin a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.\n\n## Usage\nUse examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.\n\n## Support\nTell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.\n\n## Roadmap\nIf you have ideas for releases in the future, it is a good idea to list them in the README.\n\n## Contributing\nState if you are open to contributions and what your requirements are for accepting them.\n\nFor people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.\n\nYou can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.\n\n## Authors and acknowledgment\nShow your appreciation to those who have contributed to the project.\n\n## License\nFor open source projects, say how it is licensed.\n\n## Project status\nIf you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.\n--\u003e","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fworkfloworchestrator%2Fnsi-aura","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fworkfloworchestrator%2Fnsi-aura","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fworkfloworchestrator%2Fnsi-aura/lists"}