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