RFE: Continue breaking out quads.py about quads HOT 5 CLOSED

@jtaleric thank you for the suggestions, we're always welcome to improvements in design and structure. We'll chip away at this, possibly breaking them up into smaller pieces (we want to avoid large changesets for obvious reasons).

from quads.

Sounds good will, please keep this issue updated so I can track it here. I will discuss further ideas with @kambiz-aghaiepour.

from quads.

@kambiz-aghaiepour Furthermore, I would break out the expect script https://github.com/redhat-performance/quads/blob/master/bin/juniper-set-port.exp and convert that to pyexpect. Also, I would use the same methodology above for this.

Ie create a networking.py, and then a juniper.py which inherits networking.py.

from quads.

I would also recommend moving the code base into a lib/ instead of bin/ -- You can create a bin/quads.py that imports the quads lib, imports the config and executes the main method.

This part is completed. We are keeping this open and are chipping away at it.

from quads.

A lot of things have changed since this was last filed, I don't think it's relevant any longer and most of the ideas behind this have been implemented.

I think a better place to watch the more pythonic enhancements is going to be these RFE here:

#140
#156

Above, we're going to see a full move from a legacy API built around SimpleHTTPServer and a move into CherryPy.

We'll also see a new API that's fully RESTful put in place and lastly a move away from manipulating locking, reads and writes of flat files into a proper ODM with mongo documents.

from quads.