Skip to content
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

Rosetta Modularity and Authoring My Own Driver #44

Open
brotherdust opened this issue Jun 1, 2020 · 0 comments
Open

Rosetta Modularity and Authoring My Own Driver #44

brotherdust opened this issue Jun 1, 2020 · 0 comments

Comments

@brotherdust
Copy link

brotherdust commented Jun 1, 2020

This looks to be such a cool project! Thanks for making it.

I'd like to write my own driver for Mikrotik RouterOS. Looking over the directory structure, it seems like the drivers really aren't all that modular. There's multiple JunOS and IOS subdirectories in various locations. In other words, the directory structure is very tightly integrated into the code. To write a module, I'd have to spread the code out over these locations. Wouldn't it make more sense to have something like single subdirectory for each NOS one would want to support, then have parser.py and driver.py, and ancillary code in there?

I'm happy to contribute code to this project (assuming you want contributions), but the directory structure, and lack of documentation of what code goes where, makes it somewhat difficult to get a grasp on how things are supposed to work. It might seem obvious to the authors, but it's not to me. =)

Thank you for taking the time to consider this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant