← Back to team overview

fuel-dev team mailing list archive

Re: [openstack-dev] [fuel-dev] [Fuel] Issues about OSTF tests

 

Hi all,
Timur in OSTF we've already request this info(API/nodes?cluster_id)but do not use all data from response(we take some of them like node status)So if you need example, you should go to the config.py  and see   _parse_nodes_cluster_id(self) method. 
All response is saved in data variable, so you could just get info about hw from here.



Отправлено с iPhone

> 6 апр. 2014, в 22:26, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx> написал(а):
> 
> Timur,
> sorry for missing your question.
> We are switching from fuel-dev ML to openstack-dev, and will keep watching for all Fuel-related questions.
> 
> Back to your question, you can use GET request like this:
> GET /api/nodes?cluster_id=1
> 
> 
> 
> Following is just part of the response:
> [{"model": "WDC WD3200BPVT-7", "disk": "sda", "name": "sda", "size": 320072933376}], "cpu": {"real": 1, "total": 8, "spec": [{"model": "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz", "frequency": 2201}, {"model": "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz", "frequency": 2201}, {"model": "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz", "frequency": 2201}, {"model": "Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz", "frequency": 2201},
> 
> .....
>  "memory": {"slots": 2, "total": 8589934592, "maximum_capacity": 17179869184, "devices": [{"frequency": 1333, "type": "DDR3", "size": 4294967296}, {"frequency": 1333, "type": "DDR3", "size": 4294967296}]}}, "pending_deletion": false, "online": true, "progress": 0, "pending_roles": ["controller"], "os_platform": "ubuntu", "id": 2, "manufacturer": "80AD"}]
> 
> See REST API refs here: http://docs.mirantis.com/fuel-dev/develop/api_doc.html
> 
> Thanks,
> 
> 
> 
>> On Mon, Mar 31, 2014 at 6:22 PM, Timur Nurlygayanov <tnurlygayanov@xxxxxxxxxxxx> wrote:
>> Hi Fuel team,
>> 
>> I have a questions about the OSTF tests for next release 5.0.
>> 
>> In this release we plan to include Murano 0.5, which will have significant architecture changes and it will require significant changes in OSTF tests for Murano.
>> For example, we will not support all services, which Murano supports in the last stable release (we have moved to another engine).
>> 
>> 
>> About the changes in OSTF tests for Murano:
>> 1. We will remove all tests for not-supported services
>> 2. We want to add some additional checks for OSTF tests, which will collect information about OpenStack cluster configuration and will skip some tests, if we have no required resources.
>> 
>> And now I have a question: how we can get the information about the OpenStack cloud resources, like summary size of RAM on compute nodes? (I know that we can use Nailgan API, but some working examples will be very useful)
>> 
>> Thank you! :)
>> 
>> -- 
>> 
>> Timur,
>> QA Engineer
>> OpenStack Projects
>> Mirantis Inc
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@xxxxxxxxxxxxxxxxxxx
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> -- 
> Mike Scherbakov
> #mihgen
> -- 
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp

References