-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Armada V1 and Armada V2 diagrams #2738
Comments
@Sharpz7 I would like to work on this. Please assign this to me. |
@Sharpz7 would you like both diagrams in a single generate.py file or seperate python programs? |
Either or, whatever your preference is :)) |
When I run generate.py file, it is not able to access images. I changed the reference to "images/armada.png" from "../files/armada.png" but still it's not accessing images. I don't know if it unique to my environment or is it something I don't understand. How to fix this? P.S: I changed "Lookout" to "Lookout V2". |
After hours of exploration, I finally found solution. should we add this info in our README.md ? |
Good spot with the I/o issues, feel free to edit it and document it as you see fit to get it working. |
Armada is migrating to a new set of components. To help users with that move, we need to have diagrams of both setups.
Currently we have https://github.com/armadaproject/armada/blob/master/docs/design/diagrams/relationships/armada_system.png, which is created using code from here https://github.com/armadaproject/armada/blob/master/docs/design/diagrams/relationships/generate.py. The one change that needs to happen, is it should be called "Lookout V2" instead of just "Lookout".
For the Lookout V1 Doc, it should instead look like this: https://drive.google.com/uc?id=1XtXdCP2dVXa2pXqLFGHdeSNkh8A6hBt8. Where items crossed out are part of V2, and the items in the green box are all one component.
We should have https://github.com/armadaproject/armada/blob/master/docs/design/relationships_diagram.md be changed to include both diagrams. I expect a PR for this to be a back-and-forth process.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: