Hi Ajay,
Thanks for the interest on contrail-api-cli. I'm not really in favor
of merging the tool in the contrail-controller repo. I'd like to keep
it version agnostic like the contrail neutron plugin which has its own
repo. It also has no dependencies on libs that are in
contrail-controller
so it's really easy to package it from it's own repo. To make it more
visible it could be moved in the Juniper organization on github ?
And since the code is moving fast it it would need nightly packages or
something like that.
As for the CI, I think that since the code is not very mature yet it
could slow down the developement of the tool for now. But when the API
has
stabilized it would be nice to include it in the CI. For now I'd rather
go with pull requests and have unit tests be run by travis. But in
the future yes, why not.
As for your suggestions:
1. Yes this is a good idea and I've started to refactor the code a
bit to be able to do this. It should be available soon.
2. Seems that cmd2 is like an alternative to the prompt_toolkit
library that I'm using so I'm not sure if I can use it without
loosing the nice features prompt_toolkit has (like the
autocompletion menu).
3. Yes the concept is nice I think. I wanted to be able to query
introspects (schema, vrouter...) since they don't have any cli too.
Jean-Philippe
Le 03/11/2015 23:17, Hampapur Ajay a écrit :
Hi Jean-Phillippe,
Thanks for the nice work on contrail-api-cli [1]! Following up on
queries during the presentation about possibility of other users to
leverage this work, would you be interested in hosting this on the
main contrail-controller repo [2]? This way it will be easy to bundle
into debian/rpm package, follow the branching and leverage CI on this
repo.
I do have some suggestions/queries based on some similar draft work
[3] I had done.
1. Could we have a command passed to the program and have it return
output in stdout. this way using bash(or your favorite shell) we can
process with pipes + sed/awk etc. (see the examples in gist above)
2. If we could also incorporate cmd2 [4] into your work and get its
associated benefits like transcript-based testing etc.
3. We could in future also have a ‘mount’ like concept with an
associated file-system(backed by api) such that if you 'ls
/neutron/network/<uuid>' or 'ls /nova/vm/<uuid>’ the neutron/nova
api can be used to manipulate data.
Thanks
ajay
Links:
------
[1] https://github.com/eonpatapon/contrail-api-cli/
[2] https://github.com/Juniper/contrail-controller/
[3] https://gist.github.com/ajayhn/ed2dd82acf1c1c7af399
[4] https://pythonhosted.org/cmd2/
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
