forked from opentelekomcloud/otc-tools
-
Notifications
You must be signed in to change notification settings - Fork 0
Simple bash/curl/jq based command line tool using the OpenStack and OTC specific REST APIs.
License
zamiam69/otc-tools
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About otc-tools =============== This is the otc tool for using the Open Telekom Cloud APIs. It is a simple demonstrator using shell/curl/jq to use the OpenTelekomCloud's OpenStack and OTC specific REST interfaces. It is used for testing by the OTC engineering team and can be used as a blueprint for own tooling. Unlike the more extensive tools, this one does not pull in a load of dependencies. Prefix any command by debug to observe the REST calls being made. For production use, we recommend using the native OpenStack python client tools (python-novaclient etc or the newer python-openstackclient), complemented by the python-otcctools for specific OTC functions. Or of course higher level tools, such as ansible with python-shade or terraform. Usage ----- Set your OpenStack environment (OS_ variables) just like you do for the native OpenStack clients (typically by sourcing a ~/.ostackrc or ~/novarc or ~/.openrc file). Optionally, you can also set some additional defaults on otc_env.sh by editing it and copying it into your home as ~/.otc_env.sh. When managing multipe OTC domains, you may create ~/.ostackrc.SUFFIX and ~/.s3rc.SUFFIX and set OTC_DOMAIN=SUFFIX to make otc read these files. Please have a look the otc_env.sh file and look at the output from otc help -- this provides sufficient information to get doing. Limitations ----------- This tool does not try to cover all functionality of ITC. Rather it tries to be a demo and test tool for many functions; it however does fill in some gaps where the OTC API is extended or different from the standard OpenStack API, so feel free to use it here and contribute to fill gaps you care about. There is a small, but active community on github.com/OpenTelekomCloud/. The OpenStack REST API has a paginated interfaces to allow the consumer to control how large a response may get. otc-tools currently just always tries to get everything in one go; it increases the default limits to at least 500 (higher, up to 1200 in some categories). These limits should be more than large enough to avoid you running into them if you move within the default quotas. However, if you have very large environments, keep in mind that otc-tools might not show you the whole truth any more. Please talk to us or submit a PR if you need further increases in the limits. Packages -------- Packages (RPMs/DEBs) on open Build Service home:garloff:OTC https://build.opensuse.org/package/show/home:garloff:OTC/otc-tools A docker container image [tsiotc/otc-client](https://hub.docker.com/r/tsiotc/otc-client) is available on dockerhub. You can of course also just grab this script from github; please install curl and jq to make it work; optionally also s3 (libs3/libs3-2).
About
Simple bash/curl/jq based command line tool using the OpenStack and OTC specific REST APIs.
Resources
License
Stars
Watchers
Forks
Packages 0
No packages published
Languages
- Shell 100.0%