[openstack-dev] [Valence] Nominate Anusha and Bian for Valence core reviewers

[Yang, Lin A]

Hi,

I would like to nominate Anusha Ramineni and Bian Hu as core reviewer for 
Valence.

They are excellent contributor to our project since the project's creation, and 
have shown great knowledge in Valence, OpenStack and Python. Please response 
with your +1 or any objections.

Thanks,
Lin.

__
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

Re: [openstack-dev] [mogan][valence] Valence integration

[Yang, Lin A]

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:niu.zgli...@gmail.com]
Sent: Friday, March 24, 2017 7:23 PM
To: Yang, Lin A 
Cc: OpenStack Development Mailing List (not for usage questions) 

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 
mailto:lin.a.y...@intel.com>> 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:niu.zgli...@gmail.com<mailto:niu.zgli...@gmail.com>]
Sent: Tuesday, March 21, 2017 4:20 AM
To: OpenStack Development Mailing List 
mailto: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
__
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

Re: [openstack-dev] [mogan][valence] Valence integration

[Yang, Lin A]

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 
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

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

[Yang, Lin A]

+1 both for Alexander Tivelkov and Zhu Rong. Well deserved.

Regards,
Lin Yang

On Jun 15, 2016, at 3:17 AM, Kirill Zaitsev 
mailto:kzait...@mirantis.com>> wrote:

Hello team, I want to annonce the following changes to murano core team:

1) I’d like to nominate Alexander Tivelkov for murano core. He has been part of 
the project for a very long time and has contributed to almost every part of 
murano. He has been fully committed to murano during mitaka cycle and continues 
doing so during newton [1]. His work on the scalable framework architecture is 
one of the most notable features scheduled for N release.

2) I’d like to nominate Zhu Rong for murano core. Last time he was nominated I 
-1’ed the proposal, because I believed he needed to start making more 
substantial contributions. I’m sure that Zhu Rong showed his commitment [2] to 
murano project and I’m happy to nominate him myself. His work on the separating 
cfapi from murano api and contributions headed at addressing murano’s technical 
debt are much appreciated.

3) Finally I would like to remove Steve McLellan[3] from murano core team. 
Steve has been part of murano from very early stages of it. However his focus 
has since shifted and he hasn’t been active in murano during last couple of 
cycles. I want to thank Steve for his contributions and express hope to see him 
back in the project in future.


Murano team, please respond with +1/-1 to the proposed changes.

[1] http://stackalytics.com/?user_id=ativelkov&metric=marks
[2] http://stackalytics.com/?metric=marks&user_id=zhu-rong
[3] http://stackalytics.com/?user_id=sjmc7
--
Kirill Zaitsev
Software Engineer
Mirantis, Inc
__
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

__
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

Re: [openstack-dev] [murano] Nominate Victor Ryzhenkin to Murano Core

[Yang, Lin A]

Glad to see this happened. :)
Well deserved, Victor.

Lin Yang
@Intel

> On Jan 23, 2016, at 01:33, Serg Melikyan  wrote:
> 
> I would like to nominate Victor Ryzhenkin (freerunner on IRC) join to the 
> Murano
> core-reviewers team. He has been an active member of the Murano team
> for some time now. You can check his review activity report here:
> http://stackalytics.com/report/contribution/murano-group/90
> 
> Team please vote for this change in reply to this message.
> -- 
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelik...@mirantis.com
> 
> __
> 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


__
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

Re: [openstack-dev] [mistral] [murano] [yaql] An online YAQL evaluator [was RE: [mistral] [murano] An online YAQL evaluator]

[Yang, Lin A]

Moshe, awesome and handy tool!!! Especially hear about completed
this in 24 hours Hackathon session. :)

Lin Yang
@Intel
> On Jan 17, 2016, at 08:25, Stan Lagun  wrote:
> 
> Very cool, indeed! Even myself (developer of yaql) often use yaqluator
> instead of yaql CLI :)
> 
> Finally took a time to see source codes.
> Few tips that you may find useful:
> * The most expensive operation in yaql is YaqlFactory.create(). This
> method builds a parser and it takes significant time (orders of
> magnitude more then expression parsing). I see that you create
> factory/parser
>  on each evaluation. However parser was designed to be immutable and
> thread safe so it may be reasonable to create it only once (+1 for
> legacy mode) and reuse it across queries. This will make a big
> difference
>  if the site become popular
> * You don't use engine options. There are number of useful settings
> that allow to limit iterator length or memory usage. For example looks
> like I killed the site by executing [1, 2].cycle() which returns
> indefinite collection.
>   Sorry for that. Another useful option is the one that converts sets
> to lists on output. Without it set function cannot be used in
> yaqluator. Also see [1]
> 
> [1]: https://review.openstack.org/#/c/268673/
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
> 
> 
> 
> On Wed, Jan 13, 2016 at 9:17 AM, Renat Akhmerov  
> wrote:
>> Very cool! It now even supports code assistance :)
>> 
>> Moshe, can’t stop saying good words :) Amazing!
>> 
>> Renat Akhmerov
>> @ Mirantis Inc.
>> 
>> 
>> 
>> On 22 Dec 2015, at 23:06, ELISHA, Moshe (Moshe)
>>  wrote:
>> 
>> Hi all,
>> 
>> Thank you for the kind words.
>> Just wanted to let you know that yaqluator[1] was updated and now supports
>> YAQL 1.0.2.
>> There is also a checkbox there to work in “Legacy Mode”.
>> 
>> Hope you will find it useful.
>> 
>> [1] http://yaqluator.com/
>> 
>> 
>> From: Renat Akhmerov [mailto:rakhme...@mirantis.com]
>> Sent: Friday, August 14, 2015 11:51 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator
>> 
>> I just read this thread so decided to add my 2 cents into the collection of
>> opinions.
>> 
>> Guys, I tried it out a couple of weeks ago (was told about it by one of my
>> colleagues). This is really incredible! Especially given that you completed
>> it in 24 hours :) I think as YAQL attracts more and more users it will be
>> very handy tool. I am actually for improving it further.
>> 
>> Thanks a lot! Looking forward to switch to yaql 1.0!
>> 
>> Renat Akhmerov
>> @ Mirantis Inc.
>> 
>> 
>> 
>> 
>> On 05 Aug 2015, at 04:09, Stan Lagun  wrote:
>> 
>> Dmitry,
>> 
>> yaql 1.0 has both str() and len() and much much more so there is no need to
>> support them explicitly since Mistral is going to switch to yaql 1.0 and
>> yaqluator.com is going to do the same
>> 
>> Sincerely yours,
>> Stan Lagun
>> Principal Software Engineer @ Mirantis
>> 
>> 
>> 
>> On Tue, Aug 4, 2015 at 8:55 PM, Dmitri Zimine 
>> wrote:
>> Awesome! Really.
>> 
>> Thank you folks for doing this.
>> 
>> I am so much looking forward to moving it to 1.0 with more built-in
>> functions and more power to extend it...
>> 
>> Note that Mistral has a few extensions, like `str`, `len`, which are not in
>> the scope of evaluator.
>> 
>> DZ>
>> 
>> 
>> On Aug 2, 2015, at 12:44 PM, Stan Lagun  wrote:
>> 
>> 
>> Guys, this is awesome!!!
>> 
>> Happy to see yaql gets attention. One more initiative that you may find
>> interesting is https://review.openstack.org/#/c/159905/
>> This is an attempt to port yaql 1.0 from Python to JS so that the same can
>> be done in browser
>> 
>> Sincerely yours,
>> Stan Lagun
>> Principal Software Engineer @ Mirantis
>> 
>> 
>> 
>> On Sun, Aug 2, 2015 at 5:30 PM, Nikolay Makhotkin 
>> wrote:
>> Hi guys!
>> 
>> That's awesome! It is very useful for all us!
>> 
>> --
>> Best Regards,
>> Nikolay
>> 
>> 
>> __
>> 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
>> 
>> 
>> __
>> 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
>> 
>> 
>> 
>> __
>> 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
>> 
>> 
>> __
>> OpenStack Development Mailing List (no

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

[Yang, Lin A]

+1
Glad to see this happen.

Thanks,
Lin.

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com] 
Sent: Monday, December 7, 2015 10:36 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

Greetings,

Not long ago, Ian Cordasco, sent an email out stepping down from his core roles 
as he didn't have the time to dedicate to the project team's he was part of.

Ian has contacted me mentioning that he's gotten clearance, and therefore, time 
to dedicate to Glance and other activities around our community (I'll let him 
expand on this and answer questions if there are).

As it was mentioned in the "goodbye thread" - and because Ian knows Glance 
quite well already, including the processes we follow - I'd like to propose a 
fast-track addition for him to join the team again.

Please, just like for every other folk volunteering for this role, do provide 
your feedback on this. If no rejections are made, I'll proceed to adding Ian 
back to our core team in a week from now.

Cheers,
Flavio

--
@flaper87
Flavio Percoco
__
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