OK, thanks Yang, Lin, I will prepare a spec for the new flavor soon! On Tue, Mar 28, 2017 at 1:32 AM, Yang, Lin A <[email protected]> wrote:
> Hi Zhenguo, > > > > The spec looks prefect to me, thanks a lot for doing that. > > > > The python-valenceclient is high priority of valence Pike release, and > still undergoing right now. We plan to release the python binding library > at first. Now you need a simple wrapper if you start coding right now. > > > > Regards, > > Lin. > > > > *From:* Zhenguo Niu [mailto:[email protected]] > *Sent:* Friday, March 24, 2017 7:23 PM > *To:* Yang, Lin A <[email protected]> > *Cc:* OpenStack Development Mailing List (not for usage questions) < > [email protected]> > *Subject:* Re: [openstack-dev] [mogan][valence] Valence integration > > > > Thanks Yang, Lin for the explanation! > > > > The Valence flavor shows a good example for baremetal instances, we do > need such a flavor :D > > > > I will draft a spec for this, you can help to review later. Another > question is whether the Valence client is ready to use or we need to wrap > the REST API ourselves? > > > > > > > > On Sat, Mar 25, 2017 at 9:37 AM, Yang, Lin A <[email protected]> wrote: > > 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:[email protected]] > *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 > > > > > > -- > > Best Regards, > > Zhenguo Niu > -- Best Regards, Zhenguo Niu
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
