Hi Zhenguo, Please checkout the latest valence api spec, current it support two ways to specify the arguments when composing node via valence api. 1. Specify flavor for composition - Specify flavor uuid in ‘flavor_id’ field {flavor_id: flavor_uuid} besides the name and description fields. An example of request body shows as below. {‘name’: ‘new_node’, ‘description’: ‘test composition’, ‘flavor_id’: ‘fake_uuid’}
2. Specify every hardware details, like cpu, memory, local/remote drive, nic, in ‘properties’ field. {‘name’: ‘new_node’, ‘description’: ‘test composition’, ‘properties’: {‘processor’: {‘total_cores’:8, ‘model’: ‘fale_model’}, ‘memore’: {‘capacity_mib’: 4096, ‘type’: ‘DDR3’}}} We will update user document to list all available parameters for node composition soon. [0] https://github.com/openstack/valence/blob/0db8a8e186e25ded2b17460f5ae2ce9abf576851/api-ref/source/valence-api-v1-nodes.inc Thanks, Lin. From: Zhenguo Niu [mailto:niu.zgli...@gmail.com] Sent: Tuesday, March 21, 2017 4:20 AM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [mogan][valence] Valence integration hi guys, Here is a spec about Mogan and Valence integration[1], but before this happen, I would like to know what information needed when requesting to compose a node through Valence. From the API doc[2], I can only find name and description parameters, but seems like it's incorrect, I suppose that it should at least include cpus, ram, disk or maybe cpuinfo. We need to align with this before introducing a new flavor for both RSD nodes and generic nodes. [1] https://review.openstack.org/#/c/441790/ [2] https://github.com/openstack/valence/blob/master/api-ref/source/valence-api-v1-nodes.inc#request -- Best Regards, Zhenguo Niu
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev