-
Notifications
You must be signed in to change notification settings - Fork 17
Mixcoatl 0.10.32
Announcing mixcoatl 0.10.32!
-
PIP
pip install -U mixcoatl
-
easy_install
easy_install --upgrade mixcoatl
0.10.32? But weren't we just on 0.3.4? What gives?
We changed versioning schemes to more closely match the releases of [Dell Cloud Manager] (http://www.enstratius.com/our-product/dcm-new-release)
Setting DCM_DEBUG = 1 will activate a more verbose debugging mode, where additional information will be printed to standard output.
With this mode set, mixcoatl will return header information, along with the total time elapsed to return results.
[Sample Output] (https://gist.github.com/zomGreg/46126b109be051313e81)
The time taken to issue calls and return results has been cut by up to 90% in some cases.
[Before] (https://gist.github.com/zomGreg/4cb9d92d4bba8af0694c)
[After] (https://gist.github.com/zomGreg/a93fdc6a4764726e9836)
PrettyTable, JSON, XML, & CSV for all dcm-list-* utilities.
[PrettyTable] (https://gist.github.com/zomGreg/86b66705b22ce1e7b282)
[JSON] (https://gist.github.com/zomGreg/d0777304b2adcc02cf84)
[XML] (https://gist.github.com/zomGreg/cde3849561fdcdb8bb3c)
[CSV] (https://gist.github.com/zomGreg/d6a20293fa7160b3423c)
Mixcoatl has generic [RESTful API commands] (http://mixcoatl.net/rest_tools/rest_tools.html) and we added query strings to the dcm-get utility, for example:
dcm-get 'infrastructure/MachineImage?regionId=1031&status=ACTIVE'
[Machine Image, Region, State] (https://gist.github.com/zomGreg/990785f6a13e2c5ca17d)
We've added some DCM API operational testing functionality into mixcoatl.
[Here is the help text for the read (GET) tests] (https://gist.github.com/zomGreg/1db9c41ef39c167fcad6)
###GET
GET testing is reads only, and will either select a cloud region at random for the reads testing or cycle through every known region.
[Single region] (https://gist.github.com/zomGreg/a93fdc6a4764726e9836)
[All regions] (https://gist.github.com/zomGreg/1a0122b40f3573dc1106)
In the second case, I also passed the -l
flag, which causes the elapsed time
for each test to be written to /tmp/api-test.log
###POST
POST will cause consumption of cloud resources.
[POST testing] (https://gist.github.com/bdwilliams/a335be77cb12bdef06a4#file-gistfile1-txt)
- Create machine images (
dcm-create-machine-image
) from a server - Deprecate (
dcm-deprecate-machine-image
) a machine image (note that un-deprecate functionality does not exist in the API). - Rename a server (
dcm-rename-server
) - Can now list servers (
dcm-list-servers
) by region - List your mixcoatl version (
mixcoatl -v
) - Removed all deployment related scripts from Mixcoatl.
- Update documentation
- Allow config file (~/.mixcoatl) with support to quickly change between environments
- Complete PEP8 code formating (https://www.python.org/dev/peps/pep-0008/)
- Fully automate the setting up of an environment (users, groups, roles, cloud accounts, budgets, etc.) using the premise of
dcm-api-tests --post
. - Add environment information to
mixcoatl -v
such as OS, path, DCM API version, API Key Level (System, Customer, or User), etc.
Submit bugs and feature requests on the mixcoatl github issues page
Wanna help out? Send email to The Mixcoatl Team
or just fork the mixcoatl repository and work your magic.
Cheers,
The Mixcoatl Team