Dims, Thanks for splitting the k8sclient code out. Below is my answer to your question.
- Should this be a new openstack/ repo? Yes, I think so. We need it in openstack namespace in order to leverage the openstack infra for testing and packaging. - Would the Magnum team own the repo and use the new python package? If this library is mainly used by Magnum, I think Magnum team has no problem to own it. If it is also used by other projects, I am afraid Magnum team won't have enough bandwidth to support it. In such case, it is better to have other teams to share the ownership. Best regards, Hongbin -----Original Message----- From: Davanum Srinivas [mailto:[email protected]] Sent: April-01-16 3:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Split k8s-client in separate python package Team, I've been meaning to do this for a while. Short version, see repo: https://github.com/dims/python-k8sclient/ Long version: - Started from the magnum repo. - pulled out just ./magnum/common/pythonk8sclient - preserved entire history in case we had to go back - reorganized directory structure - ran openstack cookie cutter and added generated files - added a test that actually works against a live k8s :) https://github.com/dims/python-k8sclient/blob/master/k8sclient/tests/test_k8sclient.py Question: - Should this be a new openstack/ repo? - Would the Magnum team own the repo and use the new python package? Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
