Skip to content

Rosetta Modularity and Authoring My Own Driver #44

@brotherdust

Description

@brotherdust

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions