<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;color:#351c75">Hi Clint, </div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#351c75"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#351c75">Yes this is a specific use case, I am trying to analyze if there would be any performance improvement if we use processor queue length as a weight in the filter scheduler. </div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div>Regards,</div>Rahul U Nair <br> </div></div></div>
<br><div class="gmail_quote">On Wed, Oct 21, 2015 at 2:54 AM, <span dir="ltr"><<a href="mailto:openstack-dev-request@lists.openstack.org" target="_blank">openstack-dev-request@lists.openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OpenStack-dev mailing list submissions to<br>
<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openstack-dev-request@lists.openstack.org" target="_blank">openstack-dev-request@lists.openstack.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openstack-dev-owner@lists.openstack.org" target="_blank">openstack-dev-owner@lists.openstack.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenStack-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [Neutron] Do not merge until further notice (Armando M.)<br>
2. Re: [Neutron] HenryG addition to the Neutron Drivers team<br>
(Kevin Benton)<br>
3. Re: [Fuel][QA][Plugins] Move functional tests from fuel-qa to<br>
the plugins (Anastasia Urlapova)<br>
4. Re: [Fuel] Modularization activity POC (Mike Scherbakov)<br>
5. Re: [Fuel][Plugins] Plugin deployment questions (Mike Scherbakov)<br>
6. Re: [Fuel][QA][Plugins] Move functional tests from fuel-qa to<br>
the plugins (Mike Scherbakov)<br>
7. Re: [all][heat] Which repo to use in docs --<br>
<a href="http://git.openstack.org" rel="noreferrer" target="_blank">git.openstack.org</a> or <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a>? (Flavio Percoco)<br>
8. Re: [mistral] How to call 3rd-party tools(such as Ansible) in<br>
Mistral (Renat Akhmerov)<br>
9. Re: [mistral] How to call 3rd-party tools(such as Ansible) in<br>
Mistral (Renat Akhmerov)<br>
10. Re: [Fuel][QA][Plugins] Move functional tests from fuel-qa to<br>
the plugins (Sebastian Kalinowski)<br>
11. Re: [Heat] core team nomination (Qiming Teng)<br>
12. Re: Custom Nova scheduler based on CPU queue length (Clint Byrum)<br>
13. [openstack-dev]<br>
openstack-barbican-authenticate-keystone-barbican-command<br>
(OpenStack Mailing List Archive)<br>
14. Re: [Neutron] HenryG addition to the Neutron Drivers team<br>
(Anna Kamyshnikova)<br>
15. Re: [Heat] core team nomination (Sergey Kraynev)<br>
16. [Magnum] Mitaka Design Summit Sessions in Tokyo (Adrian Otto)<br>
17. Re: [Heat] core team nomination (Manickam, Kanagaraj)<br>
18. [Glance] Spec review sprint in Tokyo (Flavio Percoco)<br>
19. [security] The first version of the Logo for Openstack<br>
Security Project (Michael Xin)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 20 Oct 2015 22:48:30 -0700<br>
From: "Armando M." <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Neutron] Do not merge until further<br>
notice<br>
Message-ID:<br>
<<a href="mailto:CAK%2BRQebGqr__QcHJ2Ca3y6dRdNd2s1xRPTzovXRryGMB4TTMow@mail.gmail.com" target="_blank">CAK+RQebGqr__QcHJ2Ca3y6dRdNd2s1xRPTzovXRryGMB4TTMow@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On 20 October 2015 at 19:46, Takashi Yamamoto <<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>> wrote:<br>
<br>
> i missed the "further notice"?<br>
><br>
<br>
No, you didn't. RC3 released, Liberty released, the world moved on and I<br>
didn't think of sending an email. Sorry.<br>
<br>
<br>
><br>
> On Wed, Oct 14, 2015 at 4:07 AM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:<br>
> > Hi folks,<br>
> ><br>
> > We are in the last hours of Liberty, let's pause for a second and<br>
> consider<br>
> > merging patches only if absolutely necessary. The gate is getting clogged<br>
> > and we need to give priority to potential RC3 fixes or gate stability<br>
> fixes.<br>
> ><br>
> > Thanks,<br>
> > Armando<br>
> ><br>
> ><br>
> __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151020/11840378/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151020/11840378/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 20 Oct 2015 22:49:32 -0700<br>
From: Kevin Benton <<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Neutron] HenryG addition to the Neutron<br>
Drivers team<br>
Message-ID:<br>
<<a href="mailto:CAO_F6JNjG9y1yXZB8BaOn7%2BKrNm_icGitbpJb6KMRe7mP62T4w@mail.gmail.com" target="_blank">CAO_F6JNjG9y1yXZB8BaOn7+KrNm_icGitbpJb6KMRe7mP62T4w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Excellent addition! Remember everyone, if the feature you want doesn't make<br>
it into Neutron, it's now Henry's fault. :)<br>
<br>
On Tue, Oct 20, 2015 at 8:14 PM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:<br>
<br>
> Hi folks,<br>
><br>
> Henry has been instrumental in many areas of the projects and his crazy<br>
> working hours makes even Kevin and I bow in awe.<br>
><br>
> Jokes aside, I would like to announce HenryG as a new member of the<br>
> Neutron Drivers team.<br>
><br>
> Having a propension to attendance, and desire to review of RFEs puts you<br>
> on the right foot to join the group, whose members are rotated regularly so<br>
> that everyone is given the opportunity to grow, and no-one burns out.<br>
><br>
> The team [1] meets regularly on Tuesdays [2], and anyone is welcome to<br>
> attend.<br>
><br>
> Please, join me in welcome Henry to the team.<br>
><br>
> Cheers,<br>
> Armando<br>
><br>
> [1]<br>
> <a href="http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team</a><br>
> [2] <a href="https://wiki.openstack.org/wiki/Meetings/NeutronDrivers" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/NeutronDrivers</a><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
<br>
<br>
--<br>
Kevin Benton<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151020/62a1ce69/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151020/62a1ce69/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 21 Oct 2015 08:54:56 +0300<br>
From: Anastasia Urlapova <<a href="mailto:aurlapova@mirantis.com" target="_blank">aurlapova@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests<br>
from fuel-qa to the plugins<br>
Message-ID:<br>
<CAC+XjbadzDBoPB=<a href="mailto:nRrO%2BZDF2KfGt192xvZb9D9mAeCeNczisJQ@mail.gmail.com" target="_blank">nRrO+ZDF2KfGt192xvZb9D9mAeCeNczisJQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Simon,<br>
structure of fuel-web repo is much more complex than fuel-qa, ~ 50 active<br>
contributors work with fuel-web.<br>
There is the functionality of the different Fuel domains and each requires<br>
its own expertise, so maintenance is divided by folders.<br>
In case of fuel-qa maintainers are doing review for whole repository,<br>
structure of file[0] is correct.<br>
<br>
<br>
Nastya.<br>
[0] <a href="https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS</a><br>
<br>
On Wed, Oct 21, 2015 at 2:15 AM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>><br>
wrote:<br>
<br>
> Simon,<br>
> I believe that it's a mistake in fuel-qa. Valid structure is in fuel-web.<br>
> Please fix the one in fuel-qa.<br>
><br>
> I'm also looking forward for automated adding of people to review requests<br>
> based on this file. Here is the task to track it:<br>
> <a href="https://bugs.launchpad.net/fuel/+bug/1497655" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1497655</a><br>
><br>
> On Tue, Oct 20, 2015 at 2:10 AM Simon Pasquier <<a href="mailto:spasquier@mirantis.com" target="_blank">spasquier@mirantis.com</a>><br>
> wrote:<br>
><br>
>> Thanks for the reply, Andrew! I must admit that I haven't read thoroughly<br>
>> the specification on the new team structure [1]. IIUC plugin developers<br>
>> should be added to the MAINTAINERS file of fuel-qa for the directories that<br>
>> concern their plugins. If I take LMA as an example, this would be:<br>
>> fuelweb_test/tests/plugins/plugin_elasticsearch<br>
>> fuelweb_test/tests/plugins/plugin_lma_collector<br>
>> fuelweb_test/tests/plugins/plugin_lma_infra_alerting<br>
>><br>
>> Is that right?<br>
>><br>
>> I can submit a change to fuel-qa for adding the LMA team to the<br>
>> MAINTAINERS file but I can't figure out the structure of the YAML data:<br>
>> fuel-web/MAINTAINERS [2] is organized as "{directory1: [maintainer1,<br>
>> maintainer2, ...], directory2: [...], ...}" while for fuel-qa [3] (and<br>
>> other Fuel projects), it's "[maintainer1, maintainer2, ...]".<br>
>><br>
>> BR,<br>
>> Simon<br>
>><br>
>> [1]<br>
>> <a href="http://specs.fuel-infra.org/fuel-specs-master/policy/team-structure.html" rel="noreferrer" target="_blank">http://specs.fuel-infra.org/fuel-specs-master/policy/team-structure.html</a><br>
>> [2] <a href="https://github.com/openstack/fuel-web/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-web/blob/master/MAINTAINERS</a><br>
>> [3] <a href="https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS</a><br>
>><br>
>><br>
>> On Sat, Oct 17, 2015 at 2:21 AM, Andrew Woodward <<a href="mailto:xarses@gmail.com" target="_blank">xarses@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> We have already discussed this to be a result of describing data driven<br>
>>> testing, untill this spec is completed there is little sense to remove all<br>
>>> of these since fuel-qa is 100% required to operate this way. In the interim<br>
>>> we should just specify the appropriate SME with the MAINTAINERS file.<br>
>>><br>
>>> On Fri, Oct 16, 2015 at 11:34 AM Sergii Golovatiuk <<br>
>>> <a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>> wrote:<br>
>>><br>
>>>> Tests should be in plugin<br>
>>>><br>
>>>> --<br>
>>>> Best regards,<br>
>>>> Sergii Golovatiuk,<br>
>>>> Skype #golserge<br>
>>>> IRC #holser<br>
>>>><br>
>>>> On Fri, Oct 16, 2015 at 5:58 PM, Simon Pasquier <<a href="mailto:spasquier@mirantis.com" target="_blank">spasquier@mirantis.com</a><br>
>>>> > wrote:<br>
>>>><br>
>>>>> Hello Alexey,<br>
>>>>><br>
>>>>> On Fri, Oct 16, 2015 at 5:35 PM, Alexey Elagin <<a href="mailto:aelagin@mirantis.com" target="_blank">aelagin@mirantis.com</a>><br>
>>>>> wrote:<br>
>>>>><br>
>>>>>> Hello Simon!<br>
>>>>>><br>
>>>>>> We are going to remove plugins' functional tests from fuel-qa because<br>
>>>>>> this tests don't use for our plugins CI process.<br>
>>>>>><br>
>>>>><br>
>>>>> And where are the existing tests going to be stored then?<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>> Simon<br>
>>>>><br>
>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> __________________________________________________________________________<br>
>>>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>>>> Unsubscribe:<br>
>>>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> __________________________________________________________________________<br>
>>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>>> Unsubscribe:<br>
>>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>> __________________________________________________________________________<br>
>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>> Unsubscribe:<br>
>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>> --<br>
>>><br>
>>> --<br>
>>><br>
>>> Andrew Woodward<br>
>>><br>
>>> Mirantis<br>
>>><br>
>>> Fuel Community Ambassador<br>
>>><br>
>>> Ceph Community<br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
> --<br>
> Mike Scherbakov<br>
> #mihgen<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/28009ffb/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/28009ffb/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 21 Oct 2015 06:01:36 +0000<br>
From: Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Fuel] Modularization activity POC<br>
Message-ID:<br>
<CAKYN3rO0PLn6H=<a href="mailto:h-4Qnc2USp6f9UCigQiCHCP6YKuKyXtKi0Sw@mail.gmail.com" target="_blank">h-4Qnc2USp6f9UCigQiCHCP6YKuKyXtKi0Sw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks Eugene. I'd recommend to start integration as early as possible...<br>
<br>
On Tue, Oct 20, 2015 at 2:11 AM Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>> wrote:<br>
<br>
> Hi Mike,<br>
><br>
> 1. our plan is to have working partitioning/provisioning in a couple of<br>
> weeks,<br>
> networking is more complicated and it's better to ask Vladimir/Ryan.<br>
> 2, 3. here we have just some general ideas, we should have independent<br>
> releases on pypi,<br>
> each component should have responsible person (team), the same way we<br>
> do it for fuel-plugin-builder<br>
> and fuelclient. The same applies to independent docker containers.<br>
> Another thing is how<br>
> we are going to combine it in ready to use tool, there are several<br>
> ways, if we drop containers,<br>
> those will be just rpm/deb packages and dependencies between them, if<br>
> we continue using<br>
> docker containers, the simplest and the most robust way is to build a<br>
> single container which<br>
> has everything user needs.<br>
><br>
> Regarding the spec our plan is to start writing spec after we have working<br>
> POC.<br>
><br>
> Thanks,<br>
><br>
><br>
> On Tue, Oct 20, 2015 at 4:43 AM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a><br>
> > wrote:<br>
><br>
>> This is great start, Evgeny.<br>
>> I have a few questions:<br>
>><br>
>> 1. When do you expect to have POC to show?<br>
>> 2. Do you plan to put new services into separate repos?<br>
>> 3. How do you plan to package those - will you create RPM package for<br>
>> each, as well as Docker container (as we have everything in containers on<br>
>> Fuel master node)<br>
>><br>
>> These questions, of course, should be covered in spec - so may be I<br>
>> should just wait for you guys to create specs. I just think that it's very<br>
>> important to think about integration from the very beginning.<br>
>><br>
>> Thanks,<br>
>><br>
>> On Mon, Oct 19, 2015 at 8:54 AM Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>><br>
>> wrote:<br>
>><br>
>>> Hey Evgeniy.<br>
>>><br>
>>> This is awesome news1 I believe that microservices is way to go.<br>
>>> Despite the fact that them bring a set of classical problems (e.g.<br>
>>> duplication of domain entities) we will win more than loose. :)<br>
>>><br>
>>> If there will be any specs or design meetings, please send me invite -<br>
>>> I'd gladly join discussions.<br>
>>><br>
>>> Thanks,<br>
>>> Igor<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> On Wed, Oct 14, 2015 at 5:30 PM, Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>> wrote:<br>
>>> > Hi,<br>
>>> ><br>
>>> > We are starting Fuel modularization POC activity which is basically in<br>
>>> one<br>
>>> > sentence<br>
>>> > can be explained as "Use Fuel without Fuel", it means that we want to<br>
>>> > provide<br>
>>> > for a user a way to use some good things from Fuel, without entire<br>
>>> master<br>
>>> > node and<br>
>>> > other parts which user doesn't need.<br>
>>> ><br>
>>> > Currently we have monolithic system which includes every aspect of<br>
>>> > deployment<br>
>>> > logic, those components tightly coupled together, and there are few<br>
>>> persons<br>
>>> > who understand all the interactions between components.<br>
>>> ><br>
>>> > As a result of modularization we will get the next benefits:<br>
>>> > 1. reusability of components<br>
>>> > 1.1. it will lead to more components consumers (users)<br>
>>> > 1.2. better integration with the community (some community projects<br>
>>> might<br>
>>> > be interested in using some parts of Fuel)<br>
>>> > 2. components decoupling will lead to clear interfaces between<br>
>>> components<br>
>>> > 2.1. so it will be easier to replace some component<br>
>>> > 2.2. it will be easier to split the work between teams and it will help<br>
>>> > scale teams in<br>
>>> > a much more efficient way<br>
>>> ><br>
>>> > Here are some thing which naturally can be used separately:<br>
>>> > * network configuration (is a part of POC)<br>
>>> > * advanced partitioning/provisioning (is a part of POC)<br>
>>> > * discovery mechanism (ironic-inspector?)<br>
>>> > * power management (ironic?)<br>
>>> > * network verification<br>
>>> > * diagnostic snapshot<br>
>>> > * etc<br>
>>> ><br>
>>> > The main purpose of POC is to try to make partly working system to<br>
>>> figure<br>
>>> > out the<br>
>>> > scope of work which we will have to do upstream in order to make it<br>
>>> > production ready.<br>
>>> ><br>
>>> > Here are few basic component-specific ideas:<br>
>>> ><br>
>>> > Advanced partitioning/provisioning<br>
>>> > * split provisioning into two independent actions partitioning and<br>
>>> > provisioning<br>
>>> > (currently we have a single call which does partitioning,<br>
>>> provisioning,<br>
>>> > post provisioning configuration)<br>
>>> > * figure out the data format (currently it's too Fuel and Cobbler<br>
>>> specific)<br>
>>> ><br>
>>> > Network configuration<br>
>>> > * CRUD api on any entity in the system (in Fuel not all of the data are<br>
>>> > exposed via api,<br>
>>> > so user has to go and edit entries in db manually)<br>
>>> > * no constraints regarding to network topology (in Fuel there are a<br>
>>> lot of<br>
>>> > hardcoded<br>
>>> > assumptions)<br>
>>> ><br>
>>> > Node hardware discovery<br>
>>> > * should be able to support different source drivers at the same time<br>
>>> > (csv file, fuel-nailgun-agent, CMDB, dhcp, cobbler etc)<br>
>>> > * versioning of HW information (required for life cycle management)<br>
>>> > * notification about changes in hardware or about node statuses<br>
>>> > (required for life cycle management)<br>
>>> ><br>
>>> > Common requirements for components:<br>
>>> > * every component must follow OpenStack coding standards when<br>
>>> > we start working upstream after POC (so there shouldn't be a question<br>
>>> > what to use pecan of flask)<br>
>>> > * Fuel specific interfaces should be implemented as drivers<br>
>>> > * this one is obvious, but currently one of the most problematic parts<br>
>>> in<br>
>>> > Fuel,<br>
>>> > HW gets changed, interface can be replaced, disk can be removed,<br>
>>> > component should have a way to handle it<br>
>>> ><br>
>>> > Technically speaking, we want to have separate services for every<br>
>>> component,<br>
>>> > it is one of the technical ways to force components to have clear<br>
>>> > interfaces.<br>
>>> ><br>
>>> > Other architecture decision which we want to try to solve is<br>
>>> extendability,<br>
>>> > currently we have a problem that all of the logic which is related to<br>
>>> > deployment<br>
>>> > data is hardcoded in Nailgun. Plugins should be able to retrieve any<br>
>>> data it<br>
>>> > needs from the system, in order to perform plugin deployment, these<br>
>>> data<br>
>>> > should<br>
>>> > be retrieved using some interface, and we already have interface where<br>
>>> we<br>
>>> > can<br>
>>> > provide stability and versioning, it's REST API. So basically<br>
>>> deployment<br>
>>> > should<br>
>>> > consist of two steps first is to retrieve all required data from any<br>
>>> source<br>
>>> > it needs,<br>
>>> > and after that send data to the nodes and start deployment.<br>
>>> ><br>
>>> > If you have any questions/suggestion don't hesitate to ask.<br>
>>> ><br>
>>> > Thanks,<br>
>>> ><br>
>>> ><br>
>>> __________________________________________________________________________<br>
>>> > OpenStack Development Mailing List (not for usage questions)<br>
>>> > Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>> ><br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>> --<br>
>> Mike Scherbakov<br>
>> #mihgen<br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
--<br>
Mike Scherbakov<br>
#mihgen<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/e685148d/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/e685148d/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 21 Oct 2015 06:04:43 +0000<br>
From: Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>>, Matthew Mosesohn<br>
<<a href="mailto:mmosesohn@mirantis.com" target="_blank">mmosesohn@mirantis.com</a>><br>
Subject: Re: [openstack-dev] [Fuel][Plugins] Plugin deployment<br>
questions<br>
Message-ID:<br>
<<a href="mailto:CAKYN3rMrpEb3Xhedud3j6Bwh-Fk5-0r3EoZPTdNrTEaEm0vfag@mail.gmail.com" target="_blank">CAKYN3rMrpEb3Xhedud3j6Bwh-Fk5-0r3EoZPTdNrTEaEm0vfag@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi all,<br>
is there a plan to remove this restriction permanently? Any bug/blueprint<br>
covering it?<br>
<br>
On Tue, Oct 20, 2015 at 5:07 AM Patrick Petit <<a href="mailto:ppetit@mirantis.com" target="_blank">ppetit@mirantis.com</a>> wrote:<br>
<br>
> Hi Matthew,<br>
><br>
> That?s useful.<br>
> Thanks<br>
><br>
> On 20 Oct 2015 at 11:22:07, Matthew Mosesohn (<a href="mailto:mmosesohn@mirantis.com" target="_blank">mmosesohn@mirantis.com</a>)<br>
> wrote:<br>
><br>
> Hi Patrick,<br>
><br>
> During the 7.0 development cycle we made a lot of enhancements to what<br>
> environment characteristics can be modified through a plugin. One item that<br>
> plugins cannot directly modify is the default Fuel roles and their<br>
> metadata. That having been said, there is an open-ended post_install.sh<br>
> script you can use for your plugin to "hack" this value. I know of one<br>
> project that currently disables the requirement for controller role in a<br>
> deployment. This may be helpful in testing a given standalone role that<br>
> doesn't depend on a controller.<br>
><br>
> Here's a link to the script: <a href="http://paste.openstack.org/show/476821/" rel="noreferrer" target="_blank">http://paste.openstack.org/show/476821/</a><br>
> Note that this doesn't reflect "enabled" status of a plugin. It will make<br>
> controller min count 0 for all environments. That won't break them, but it<br>
> just removes the restriction.<br>
><br>
> Best Regards,<br>
> Matthew Mosesohn<br>
><br>
> On Mon, Oct 19, 2015 at 3:29 PM, Dmitry Mescheryakov <<br>
> <a href="mailto:dmescheryakov@mirantis.com" target="_blank">dmescheryakov@mirantis.com</a>> wrote:<br>
><br>
>> Hello folks,<br>
>><br>
>> I second Patrick's idea. In our case we would like to install standalone<br>
>> RabbitMQ cluster with Fuel reference architecture to perform destructive<br>
>> tests on it. Requirement to install controller is an excessive burden in<br>
>> that case.<br>
>><br>
>> Thanks,<br>
>><br>
>> Dmitry<br>
>><br>
>> 2015-10-19 13:44 GMT+03:00 Patrick Petit <<a href="mailto:ppetit@mirantis.com" target="_blank">ppetit@mirantis.com</a>>:<br>
>><br>
>>> Hi There,<br>
>>><br>
>>> There are situations where we?d like to deploy only Fuel plugins in an<br>
>>> environment.<br>
>>> That?s typically the case with Elasticsearch and InfluxDB plugins of LMA<br>
>>> tools.<br>
>>> Currently it?s not possible because you need to at least have one<br>
>>> controller.<br>
>>> What exactly is making that limitation? How hard would it be to have it<br>
>>> removed?<br>
>>><br>
>>> Thanks<br>
>>> Patrick<br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
--<br>
Mike Scherbakov<br>
#mihgen<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/37e39f64/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/37e39f64/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 21 Oct 2015 06:11:42 +0000<br>
From: Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests<br>
from fuel-qa to the plugins<br>
Message-ID:<br>
<CAKYN3rN9ng9P_szKirFJn5H_j5nQP5O0gz=<a href="mailto:XDnuC-LCURko5%2BA@mail.gmail.com" target="_blank">XDnuC-LCURko5+A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Nastya,<br>
according to the template I provided initially [1] format in fuel-qa is<br>
invalid. I've requested to support only one format [2].<br>
File must always have a folder. If you want to cover the whole repo, then<br>
the right structure would be<br>
<br>
maintainers:<br>
<br>
<br>
- ./:<br>
<br>
- name: ...<br>
<br>
email: ...<br>
<br>
IRC: ...<br>
e.g. you'd just refer to the current folder, which should be root of the<br>
repo by default.<br>
Simon is asking a valid request: if you add his folder in the file, he will<br>
be always added to the review request by script, once it's implemented.<br>
Only in the case when contribution is made to his particular area of<br>
responsibility.<br>
<br>
[1] <a href="https://github.com/openstack/fuel-web/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-web/blob/master/MAINTAINERS</a><br>
[2] <a href="https://bugs.launchpad.net/fuel/+bug/1497655" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1497655</a><br>
<br>
On Tue, Oct 20, 2015 at 11:03 PM Anastasia Urlapova <<a href="mailto:aurlapova@mirantis.com" target="_blank">aurlapova@mirantis.com</a>><br>
wrote:<br>
<br>
> Simon,<br>
> structure of fuel-web repo is much more complex than fuel-qa, ~ 50 active<br>
> contributors work with fuel-web.<br>
> There is the functionality of the different Fuel domains and each requires<br>
> its own expertise, so maintenance is divided by folders.<br>
> In case of fuel-qa maintainers are doing review for whole repository,<br>
> structure of file[0] is correct.<br>
><br>
><br>
> Nastya.<br>
> [0] <a href="https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS</a><br>
><br>
> On Wed, Oct 21, 2015 at 2:15 AM, Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a><br>
> > wrote:<br>
><br>
>> Simon,<br>
>> I believe that it's a mistake in fuel-qa. Valid structure is in fuel-web.<br>
>> Please fix the one in fuel-qa.<br>
>><br>
>> I'm also looking forward for automated adding of people to review<br>
>> requests based on this file. Here is the task to track it:<br>
>> <a href="https://bugs.launchpad.net/fuel/+bug/1497655" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1497655</a><br>
>><br>
>> On Tue, Oct 20, 2015 at 2:10 AM Simon Pasquier <<a href="mailto:spasquier@mirantis.com" target="_blank">spasquier@mirantis.com</a>><br>
>> wrote:<br>
>><br>
>>> Thanks for the reply, Andrew! I must admit that I haven't read<br>
>>> thoroughly the specification on the new team structure [1]. IIUC plugin<br>
>>> developers should be added to the MAINTAINERS file of fuel-qa for the<br>
>>> directories that concern their plugins. If I take LMA as an example, this<br>
>>> would be:<br>
>>> fuelweb_test/tests/plugins/plugin_elasticsearch<br>
>>> fuelweb_test/tests/plugins/plugin_lma_collector<br>
>>> fuelweb_test/tests/plugins/plugin_lma_infra_alerting<br>
>>><br>
>>> Is that right?<br>
>>><br>
>>> I can submit a change to fuel-qa for adding the LMA team to the<br>
>>> MAINTAINERS file but I can't figure out the structure of the YAML data:<br>
>>> fuel-web/MAINTAINERS [2] is organized as "{directory1: [maintainer1,<br>
>>> maintainer2, ...], directory2: [...], ...}" while for fuel-qa [3] (and<br>
>>> other Fuel projects), it's "[maintainer1, maintainer2, ...]".<br>
>>><br>
>>> BR,<br>
>>> Simon<br>
>>><br>
>>> [1]<br>
>>> <a href="http://specs.fuel-infra.org/fuel-specs-master/policy/team-structure.html" rel="noreferrer" target="_blank">http://specs.fuel-infra.org/fuel-specs-master/policy/team-structure.html</a><br>
>>> [2] <a href="https://github.com/openstack/fuel-web/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-web/blob/master/MAINTAINERS</a><br>
>>> [3] <a href="https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS</a><br>
>>><br>
>>><br>
>>> On Sat, Oct 17, 2015 at 2:21 AM, Andrew Woodward <<a href="mailto:xarses@gmail.com" target="_blank">xarses@gmail.com</a>><br>
>>> wrote:<br>
>>><br>
>>>> We have already discussed this to be a result of describing data driven<br>
>>>> testing, untill this spec is completed there is little sense to remove all<br>
>>>> of these since fuel-qa is 100% required to operate this way. In the interim<br>
>>>> we should just specify the appropriate SME with the MAINTAINERS file.<br>
>>>><br>
>>>> On Fri, Oct 16, 2015 at 11:34 AM Sergii Golovatiuk <<br>
>>>> <a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>> wrote:<br>
>>>><br>
>>>>> Tests should be in plugin<br>
>>>>><br>
>>>>> --<br>
>>>>> Best regards,<br>
>>>>> Sergii Golovatiuk,<br>
>>>>> Skype #golserge<br>
>>>>> IRC #holser<br>
>>>>><br>
>>>>> On Fri, Oct 16, 2015 at 5:58 PM, Simon Pasquier <<br>
>>>>> <a href="mailto:spasquier@mirantis.com" target="_blank">spasquier@mirantis.com</a>> wrote:<br>
>>>>><br>
>>>>>> Hello Alexey,<br>
>>>>>><br>
>>>>>> On Fri, Oct 16, 2015 at 5:35 PM, Alexey Elagin <<a href="mailto:aelagin@mirantis.com" target="_blank">aelagin@mirantis.com</a>><br>
>>>>>> wrote:<br>
>>>>>><br>
>>>>>>> Hello Simon!<br>
>>>>>>><br>
>>>>>>> We are going to remove plugins' functional tests from fuel-qa<br>
>>>>>>> because this tests don't use for our plugins CI process.<br>
>>>>>>><br>
>>>>>><br>
>>>>>> And where are the existing tests going to be stored then?<br>
>>>>>><br>
>>>>>> Thanks,<br>
>>>>>> Simon<br>
>>>>>><br>
>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> __________________________________________________________________________<br>
>>>>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>>>>> Unsubscribe:<br>
>>>>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> __________________________________________________________________________<br>
>>>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>>>> Unsubscribe:<br>
>>>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>> __________________________________________________________________________<br>
>>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>>> Unsubscribe:<br>
>>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>><br>
>>>> --<br>
>>>><br>
>>>> --<br>
>>>><br>
>>>> Andrew Woodward<br>
>>>><br>
>>>> Mirantis<br>
>>>><br>
>>>> Fuel Community Ambassador<br>
>>>><br>
>>>> Ceph Community<br>
>>>><br>
>>>><br>
>>>> __________________________________________________________________________<br>
>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>> Unsubscribe:<br>
>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>> --<br>
>> Mike Scherbakov<br>
>> #mihgen<br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
--<br>
Mike Scherbakov<br>
#mihgen<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/44b9ceb8/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/44b9ceb8/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 21 Oct 2015 15:27:39 +0900<br>
From: Flavio Percoco <<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [all][heat] Which repo to use in docs --<br>
<a href="http://git.openstack.org" rel="noreferrer" target="_blank">git.openstack.org</a> or <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a>?<br>
Message-ID: <<a href="mailto:20151021062739.GC6691@redhat.com" target="_blank">20151021062739.GC6691@redhat.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
On 20/10/15 18:34 +0000, Jeremy Stanley wrote:<br>
>On 2015-10-20 13:20:34 -0500 (-0500), Dolph Mathews wrote:<br>
>[...]<br>
>> +1 I would never direct anyone new straight to <a href="http://git.openstack.org" rel="noreferrer" target="_blank">git.openstack.org</a> because it<br>
>> makes a poor first impression relative to <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a>. I assume that's the<br>
>> reason why we keep <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a> as a mirror at all (?).<br>
><br>
>Directing someone to a proprietary/non-open service seems like a far<br>
>worse impression to me.<br>
><br>
>We did look into a mechanism to auto-render README pages on the fly<br>
>in cgit, but any reasonably trivial implementation with its filter<br>
>mechanism made it hard to get to the non-rendered version of the<br>
>document. Ultimately we determined that putting work into making it<br>
>easier to render and publish documentation was a far better use of<br>
>our time than trying to turn a code browser into a documentation<br>
>viewer.<br>
><br>
>So if the question is whether to point people at <a href="http://git.openstack.org" rel="noreferrer" target="_blank">git.openstack.org</a><br>
>or <a href="http://github.com" rel="noreferrer" target="_blank">github.com</a> as a homepage for a project, my recommendation is:<br>
>neither. Link them to your published documentation (and make sure it<br>
>includes information on where to browse and clone your source<br>
>code!).<br>
<br>
Just want to say that I fully agree with the above. Well said!<br>
<br>
--<br>
@flaper87<br>
Flavio Percoco<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/764a9a04/attachment-0001.pgp" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/764a9a04/attachment-0001.pgp</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Wed, 21 Oct 2015 12:32:41 +0600<br>
From: Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com" target="_blank">rakhmerov@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [mistral] How to call 3rd-party<br>
tools(such as Ansible) in Mistral<br>
Message-ID: <<a href="mailto:AC6B6305-BCAC-44BC-B53B-BFB1771717BB@mirantis.com" target="_blank">AC6B6305-BCAC-44BC-B53B-BFB1771717BB@mirantis.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
> On 19 Oct 2015, at 13:18, WANG, Ming Hao (Tony T) <<a href="mailto:tony.a.wang@alcatel-lucent.com" target="_blank">tony.a.wang@alcatel-lucent.com</a>> wrote:<br>
><br>
> I like your option2(<a href="https://blueprints.launchpad.net/mistral/+spec/action-providers" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/mistral/+spec/action-providers</a> <<a href="https://blueprints.launchpad.net/mistral/+spec/action-providers" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/mistral/+spec/action-providers</a>>). J<br>
> Any schedule for this? Looks like it isn?t started yet.<br>
<br>
No particular plans yet. It?s been around for several months by now. It could be included in Mitaka as long as our resources allows to do that.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/0a78dc25/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/0a78dc25/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Wed, 21 Oct 2015 12:34:33 +0600<br>
From: Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com" target="_blank">rakhmerov@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [mistral] How to call 3rd-party<br>
tools(such as Ansible) in Mistral<br>
Message-ID: <<a href="mailto:69E1BA92-E28A-498D-8A8A-5636C4E26CB8@mirantis.com" target="_blank">69E1BA92-E28A-498D-8A8A-5636C4E26CB8@mirantis.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
> On 20 Oct 2015, at 14:58, WANG, Ming Hao (Tony T) <<a href="mailto:tony.a.wang@alcatel-lucent.com" target="_blank">tony.a.wang@alcatel-lucent.com</a>> wrote:<br>
><br>
> Another question is:<br>
> If I use custom action to run Ansible, the Ansible playbook should be stored on the same server of Mistral. Is it right?<br>
<br>
Depends on how this action is implemented (it can, for example, do ssh to other servers) but the simplest implementation would be with playbooks on the same server, yes.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/bdfe9ea8/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/bdfe9ea8/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Wed, 21 Oct 2015 08:34:51 +0200<br>
From: Sebastian Kalinowski <<a href="mailto:skalinowski@mirantis.com" target="_blank">skalinowski@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests<br>
from fuel-qa to the plugins<br>
Message-ID:<br>
<<a href="mailto:CAGRGKG4mKNMbJTWjRwcKYBA_%2BA2b3sh7Q05cGHvw7X3Hhv7g4Q@mail.gmail.com" target="_blank">CAGRGKG4mKNMbJTWjRwcKYBA_+A2b3sh7Q05cGHvw7X3Hhv7g4Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
2015-10-21 8:11 GMT+02:00 Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>>:<br>
<br>
><br>
> Simon is asking a valid request: if you add his folder in the file, he<br>
> will be always added to the review request by script, once it's<br>
> implemented. Only in the case when contribution is made to his particular<br>
> area of responsibility.<br>
><br>
<br>
Mike, when this sript will be implemented? It was promised long time ago<br>
[1]. It is a important part of whole review process change and I doubt that<br>
people would like to manually go<br>
through MAINTAINERS with every review they post.<br>
<br>
Also there was a request to add a job for validating MAINTAINERS file, how<br>
is the progress with that?<br>
<br>
[1] <a href="https://bugs.launchpad.net/fuel/+bug/1497655" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1497655</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/87c213b1/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/87c213b1/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Wed, 21 Oct 2015 14:45:19 +0800<br>
From: Qiming Teng <<a href="mailto:tengqim@linux.vnet.ibm.com" target="_blank">tengqim@linux.vnet.ibm.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Heat] core team nomination<br>
Message-ID: <20151021064518.GA18123@qiming-ThinkCentre-M58p><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
+1 to both.<br>
<br>
Qiming<br>
<br>
On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote:<br>
> I'd like to propose new candidates for heat core-team:<br>
> Rabi Mishra<br>
> Peter Razumovsky<br>
><br>
> According statistic both candidate made a big effort in Heat as<br>
> reviewers and as contributors [1][2].<br>
> They were involved in Heat community work during last several releases and<br>
> showed good understanding of Heat code.<br>
> I think, that they are ready to became core-reviewers.<br>
><br>
> Heat-cores, please vote with +/- 1.<br>
><br>
> [1] <a href="http://stackalytics.com/report/contribution/heat-group/180" rel="noreferrer" target="_blank">http://stackalytics.com/report/contribution/heat-group/180</a><br>
> [2] <a href="http://stackalytics.com/?module=heat-group&metric=person-day" rel="noreferrer" target="_blank">http://stackalytics.com/?module=heat-group&metric=person-day</a><br>
> --<br>
> Regards,<br>
> Sergey.<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Wed, 21 Oct 2015 00:04:46 -0700<br>
From: Clint Byrum <<a href="mailto:clint@fewbar.com" target="_blank">clint@fewbar.com</a>><br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] Custom Nova scheduler based on CPU queue<br>
length<br>
Message-ID: <<a href="mailto:1445410895-sup-581@fewbar.com" target="_blank">1445410895-sup-581@fewbar.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Excerpts from Rahul Nair's message of 2015-10-20 18:53:09 -0700:<br>
> ?Hi All,<br>
><br>
> I am fairly new to the OpenStack community and is trying to create a custom<br>
> scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize<br>
> if there are any inaccuracies in my statements.<br>
><br>
> As I understand a weigher for the filter scheduler that weighs filtered<br>
> host machines based on the host weight option, 'cpu.percent' can be<br>
> configured to prioritize the hosts based on CPU percentage, but there are<br>
> only limited options when it comes to filtering of machines in the first<br>
> place, that too using the CPU queue length.<br>
><br>
> Also, I understand that IBM has its platform resource scheduler that can be<br>
> used to build custom plugins to get user defined metrics, is there a<br>
> similar way in pure Openstack which can be used to get the CPU queue length.<br>
><br>
> As of now, I am thinking of writing a custom script to be kept in all<br>
> compute nodes to retrieve the CPU queue length and send it to the Nova<br>
> controller, is this the way to go, or is there a defined approach that I<br>
> can follow to implement a scheduler that uses CPU queue length to filter<br>
> physical machines.<br>
><br>
> Any pointers on this would be really helpful.<br>
<br>
Rahul, I'm realy curious about what it is you're trying to accomplish<br>
here.<br>
<br>
The CPU queue length is an extremely volatile statistic. Is this maybe<br>
for a single-purpose cloud where you do have some idea what might be<br>
running?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Wed, 21 Oct 2015 00:11:52 -0700<br>
From: OpenStack Mailing List Archive <<a href="mailto:corpqa@gmail.com" target="_blank">corpqa@gmail.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev]<br>
openstack-barbican-authenticate-keystone-barbican-command<br>
Message-ID: <<a href="mailto:f2a4370f35dc15b08f2abdaaa09e856d@openstack.nimeyo.com" target="_blank">f2a4370f35dc15b08f2abdaaa09e856d@openstack.nimeyo.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/1b161c84/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/1b161c84/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Wed, 21 Oct 2015 10:13:25 +0300<br>
From: Anna Kamyshnikova <<a href="mailto:akamyshnikova@mirantis.com" target="_blank">akamyshnikova@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Neutron] HenryG addition to the Neutron<br>
Drivers team<br>
Message-ID:<br>
<CAOBv_tL2-5D1OfMwtc9FX0fm5dx=<a href="mailto:hViAiBtPDyk6rVUjJn2XuQ@mail.gmail.com" target="_blank">hViAiBtPDyk6rVUjJn2XuQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Congratulations Henry!<br>
<br>
On Wed, Oct 21, 2015 at 8:49 AM, Kevin Benton <<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>> wrote:<br>
<br>
> Excellent addition! Remember everyone, if the feature you want doesn't<br>
> make it into Neutron, it's now Henry's fault. :)<br>
><br>
> On Tue, Oct 20, 2015 at 8:14 PM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:<br>
><br>
>> Hi folks,<br>
>><br>
>> Henry has been instrumental in many areas of the projects and his crazy<br>
>> working hours makes even Kevin and I bow in awe.<br>
>><br>
>> Jokes aside, I would like to announce HenryG as a new member of the<br>
>> Neutron Drivers team.<br>
>><br>
>> Having a propension to attendance, and desire to review of RFEs puts you<br>
>> on the right foot to join the group, whose members are rotated regularly so<br>
>> that everyone is given the opportunity to grow, and no-one burns out.<br>
>><br>
>> The team [1] meets regularly on Tuesdays [2], and anyone is welcome to<br>
>> attend.<br>
>><br>
>> Please, join me in welcome Henry to the team.<br>
>><br>
>> Cheers,<br>
>> Armando<br>
>><br>
>> [1]<br>
>> <a href="http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team</a><br>
>> [2] <a href="https://wiki.openstack.org/wiki/Meetings/NeutronDrivers" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/NeutronDrivers</a><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
><br>
><br>
> --<br>
> Kevin Benton<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
<br>
<br>
--<br>
Regards,<br>
Ann Kamyshnikova<br>
Mirantis, Inc<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/2f942b8e/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/2f942b8e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 15<br>
Date: Wed, 21 Oct 2015 10:26:54 +0300<br>
From: Sergey Kraynev <<a href="mailto:skraynev@mirantis.com" target="_blank">skraynev@mirantis.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Heat] core team nomination<br>
Message-ID:<br>
<<a href="mailto:CAAbQNRms7Ut1gHt6x5W%2BLPGqF-kYNwin18iQ2VKpT4PpXrOA2w@mail.gmail.com" target="_blank">CAAbQNRms7Ut1gHt6x5W+LPGqF-kYNwin18iQ2VKpT4PpXrOA2w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Rabi, Peter, my congradulations. You were elected by a unanimous vote :)<br>
I will add you to heat-core group. Enjoy and stay on this course ! :)<br>
<br>
On 21 October 2015 at 09:45, Qiming Teng <<a href="mailto:tengqim@linux.vnet.ibm.com" target="_blank">tengqim@linux.vnet.ibm.com</a>> wrote:<br>
> +1 to both.<br>
><br>
> Qiming<br>
><br>
> On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote:<br>
>> I'd like to propose new candidates for heat core-team:<br>
>> Rabi Mishra<br>
>> Peter Razumovsky<br>
>><br>
>> According statistic both candidate made a big effort in Heat as<br>
>> reviewers and as contributors [1][2].<br>
>> They were involved in Heat community work during last several releases and<br>
>> showed good understanding of Heat code.<br>
>> I think, that they are ready to became core-reviewers.<br>
>><br>
>> Heat-cores, please vote with +/- 1.<br>
>><br>
>> [1] <a href="http://stackalytics.com/report/contribution/heat-group/180" rel="noreferrer" target="_blank">http://stackalytics.com/report/contribution/heat-group/180</a><br>
>> [2] <a href="http://stackalytics.com/?module=heat-group&metric=person-day" rel="noreferrer" target="_blank">http://stackalytics.com/?module=heat-group&metric=person-day</a><br>
>> --<br>
>> Regards,<br>
>> Sergey.<br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Regards,<br>
Sergey.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 16<br>
Date: Wed, 21 Oct 2015 07:30:57 +0000<br>
From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [Magnum] Mitaka Design Summit Sessions in<br>
Tokyo<br>
Message-ID: <<a href="mailto:9AA00739-42B3-4905-BBEA-E5AFCC3FDE12@rackspace.com" target="_blank">9AA00739-42B3-4905-BBEA-E5AFCC3FDE12@rackspace.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Magnum Team,<br>
<br>
For those of you attending the Mitaka Design Summit in Tokyo next week, here are the sessions that I respectfully request you attend:<br>
<br>
2015-10-28, 11:15-11:55 <a href="http://sched.co/4Qck" rel="noreferrer" target="_blank">http://sched.co/4Qck</a> Heat Template Refactoring<br>
2015-10-28, 12:05-12:45 <a href="http://sched.co/4Qdc" rel="noreferrer" target="_blank">http://sched.co/4Qdc</a> Magnum Scalability (Work Session)<br>
2015-10-28, 14:00-14:40 <a href="http://sched.co/4Qaf" rel="noreferrer" target="_blank">http://sched.co/4Qaf</a> Magnum Security (Work Session)<br>
2015-10-28, 16:40-17:20 <a href="http://sched.co/49xE" rel="noreferrer" target="_blank">http://sched.co/49xE</a> OpenStack Magnum - Containers-as-a-Service (Summit Session)<br>
2015-10-29, 09:00-09:40 <a href="http://sched.co/4QdW" rel="noreferrer" target="_blank">http://sched.co/4QdW</a> Magnum: Storage Features (Fishbowl)<br>
2015-10-29, 09:50-10:30 <a href="http://sched.co/4Qel" rel="noreferrer" target="_blank">http://sched.co/4Qel</a> Netwoking: Past, Present, and Future (Fishbowl)<br>
2015-10-29, 11:00-11:40 <a href="http://sched.co/4Qeo" rel="noreferrer" target="_blank">http://sched.co/4Qeo</a> Magnum Auto-scaling (Workroom)<br>
2015-10-29, 11:50-12:30 <a href="http://sched.co/4QeX" rel="noreferrer" target="_blank">http://sched.co/4QeX</a> Functional Testing (Work Session)<br>
2015-10-29, 13:50-14:30 <a href="http://sched.co/4Qem" rel="noreferrer" target="_blank">http://sched.co/4Qem</a> Magnum: Bare Metal Bays (Fishbowl)<br>
2015-10-29, 14:40-15:20 <a href="http://sched.co/4Qcw" rel="noreferrer" target="_blank">http://sched.co/4Qcw</a> Magnum: Getting Started for Developers and Sysadmins (Fishbowl)<br>
2015-10-29, 15:30-16:10 <a href="http://sched.co/4Qdj" rel="noreferrer" target="_blank">http://sched.co/4Qdj</a> Magnum: Scope of Magnum (Fishbowl)<br>
2015-10-30, 09:00-12:30 <a href="http://sched.co/4Qdh" rel="noreferrer" target="_blank">http://sched.co/4Qdh</a> Magnum contributors meetup<br>
2015-10-30, 14:00-17:30 <a href="http://sched.co/4Qbc" rel="noreferrer" target="_blank">http://sched.co/4Qbc</a> Magnum contributors meetup<br>
<br>
Note that the contributors meetups have a shared open agenda. Find the etherpad linked to the shed entry. Please put your topics in the list, and we will sort them as a group together so we can cover anything that was not already addressed in the previous sessions.<br>
<br>
Also note that you can star these sessions in Sched, and then subscribe to the iCal feed, labeled ?Mobile App + iCal? so all of your selected sessions show in your calendar if you subscribe to that iCal feed.<br>
<br>
I have also published this same information on our Wiki:<br>
<a href="https://wiki.openstack.org/wiki/Magnum/Summit" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Magnum/Summit</a><br>
<br>
See you at the summit!<br>
<br>
Thanks,<br>
<br>
Adrian<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/41f6b155/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/41f6b155/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 17<br>
Date: Wed, 21 Oct 2015 07:36:21 +0000<br>
From: "Manickam, Kanagaraj" <<a href="mailto:kanagaraj.manickam@hpe.com" target="_blank">kanagaraj.manickam@hpe.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [Heat] core team nomination<br>
Message-ID:<br>
<<a href="mailto:D829F158B90303479A71BCAA89E1E760391E2CAA@G9W0723.americas.hpqcorp.net" target="_blank">D829F158B90303479A71BCAA89E1E760391E2CAA@G9W0723.americas.hpqcorp.net</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Congrats Rabi and Peter :)<br>
<br>
-----Original Message-----<br>
From: Sergey Kraynev [mailto:<a href="mailto:skraynev@mirantis.com" target="_blank">skraynev@mirantis.com</a>]<br>
Sent: Wednesday, October 21, 2015 12:57 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [Heat] core team nomination<br>
<br>
Rabi, Peter, my congradulations. You were elected by a unanimous vote :) I will add you to heat-core group. Enjoy and stay on this course ! :)<br>
<br>
On 21 October 2015 at 09:45, Qiming Teng <<a href="mailto:tengqim@linux.vnet.ibm.com" target="_blank">tengqim@linux.vnet.ibm.com</a>> wrote:<br>
> +1 to both.<br>
><br>
> Qiming<br>
><br>
> On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote:<br>
>> I'd like to propose new candidates for heat core-team:<br>
>> Rabi Mishra<br>
>> Peter Razumovsky<br>
>><br>
>> According statistic both candidate made a big effort in Heat as<br>
>> reviewers and as contributors [1][2].<br>
>> They were involved in Heat community work during last several<br>
>> releases and showed good understanding of Heat code.<br>
>> I think, that they are ready to became core-reviewers.<br>
>><br>
>> Heat-cores, please vote with +/- 1.<br>
>><br>
>> [1] <a href="http://stackalytics.com/report/contribution/heat-group/180" rel="noreferrer" target="_blank">http://stackalytics.com/report/contribution/heat-group/180</a><br>
>> [2] <a href="http://stackalytics.com/?module=heat-group&metric=person-day" rel="noreferrer" target="_blank">http://stackalytics.com/?module=heat-group&metric=person-day</a><br>
>> --<br>
>> Regards,<br>
>> Sergey.<br>
>><br>
>> _____________________________________________________________________<br>
>> _____ OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
> ______________________________________________________________________<br>
> ____ OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Regards,<br>
Sergey.<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 18<br>
Date: Wed, 21 Oct 2015 16:44:41 +0900<br>
From: Flavio Percoco <<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [Glance] Spec review sprint in Tokyo<br>
Message-ID: <<a href="mailto:20151021074441.GE6691@redhat.com" target="_blank">20151021074441.GE6691@redhat.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Greetings,<br>
<br>
The drivers team will have a Spec Rewview sprint next friday at the<br>
Glance meetup in Tokyo (Friday Oct 30th).<br>
<br>
This email is a heads up for all spec authors[0] to address pending<br>
comments so that we can work on your specs and speed up the process.<br>
<br>
[0] <a href="https://review.openstack.org/#/q/status:open+project:openstack/glance-specs,n,z" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/glance-specs,n,z</a><br>
<br>
<br>
Thanks in advance,<br>
Flavio<br>
<br>
--<br>
@flaper87<br>
Flavio Percoco<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/2a32cc3e/attachment-0001.pgp" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/2a32cc3e/attachment-0001.pgp</a>><br>
<br>
------------------------------<br>
<br>
Message: 19<br>
Date: Wed, 21 Oct 2015 07:54:43 +0000<br>
From: Michael Xin <<a href="mailto:michael.xin@RACKSPACE.COM" target="_blank">michael.xin@RACKSPACE.COM</a>><br>
To: "<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
Cc: Rachel Grahmann <<a href="mailto:rachel.grahmann@RACKSPACE.COM" target="_blank">rachel.grahmann@RACKSPACE.COM</a>><br>
Subject: [openstack-dev] [security] The first version of the Logo for<br>
Openstack Security Project<br>
Message-ID: <<a href="mailto:D24CAE20.6FBF8%25michael.xin@rackspace.com" target="_blank">D24CAE20.6FBF8%michael.xin@rackspace.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi, guys:<br>
Thanks for your help. We are designing a logo and a flyer for Openstack Security Project. Rachel helped us with the task. Attached is her first version of the logo. Please let us know your feedback.<br>
<br>
<a href="http://5d100f09242e1d85fe65-9262bad2bd2ce9d805c21cb30838f376.r18.cf1.rackcdn.com/os-security-project-logo.png" rel="noreferrer" target="_blank">http://5d100f09242e1d85fe65-9262bad2bd2ce9d805c21cb30838f376.r18.cf1.rackcdn.com/os-security-project-logo.png</a><br>
Thanks and have a great day.<br>
<br>
Yours,<br>
Michael<br>
<br>
-----------------------------------------------------------------------------<br>
Michael Xin | Manager, Security Engineering - US<br>
Product Security |Rackspace Hosting<br>
Office #: 501-7341 or 210-312-7341<br>
Mobile #: 210-284-8674<br>
5000 Walzem Road, San Antonio, Tx 78218<br>
----------------------------------------------------------------------------<br>
Experience fanatical support<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/5b36ea11/attachment.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/5b36ea11/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: os-security-project-logo.png<br>
Type: image/png<br>
Size: 545514 bytes<br>
Desc: os-security-project-logo.png<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/5b36ea11/attachment.png" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/5b36ea11/attachment.png</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
End of OpenStack-dev Digest, Vol 42, Issue 57<br>
*********************************************<br>
</blockquote></div><br></div></div>