Re: [openstack-dev] [Senlin] Does Senlin support Prometheus？
Senlin integrates with Aodh using webhooks. As shown in [1], you create a receiver of type webhook and then create a Aodh alarm to call this webhook [2] on the desired condition. Prometheus AlertManager supports notifications to webhooks [3]. While I have not tried this myself, I believe that it should be as simple as setting up Prometheus AlertManager to notify the webhook created in Senlin (see [1]). Regards, Duc (dtruong) [1] https://docs.openstack.org/senlin/latest/scenarios/autoscaling_ceilometer.html#step-2-create-receivers [2] https://docs.openstack.org/senlin/latest/scenarios/autoscaling_ceilometer.html#step-3-creating-aodh-alarms [3] https://prometheus.io/docs/alerting/configuration/#webhook_config On Mon, Nov 19, 2018 at 6:33 PM xuc...@chinacloud.com.cn wrote: > > Hi， > > Senlin, Ceilometer/Aodh is currently integrated, does it support Prometheus ？ > > > thanks > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] No meeting this week and next week
Everyone, This is a reminder that there won't be a meeting this week due to the summit and next week due to the Thanksgiving holiday The next meeting will be on Friday, November 30. Regards, Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Meeting today at 530 UTC
Everyone, As a reminder, we will be having our regular meeting today at 530 UTC. The meetings for Nov 16 and Nov 23 will be cancelled due to the summit next week and the U.S. Thanksgiving holiday the following week, Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration
Thanks for getting the forum setup. I have added some high-level autoscaling use case to the etherpad that will help during the discussion. Duc (dtruong) On Wed, Oct 24, 2018 at 2:10 AM Rico Lin wrote: > Hi all, I'm glad to notify you all that our forum session has been > accepted [1] and that forum time schedule (Thursday, November 15, > 9:50am-10:30am) should be stable by now. So please save your schedule for > it!! > Any feedback are welcome! > > > > [1] > https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22753/autoscaling-integration-improvement-and-feedback > > On Tue, Oct 9, 2018 at 3:07 PM Rico Lin wrote: > >> a reminder for all, please put your ideas/thoughts/suggest actions in our >> etherpad [1], >> which we gonna use for further discussion in Forum, or in PTG if we got >> no forum for it. >> So we won't be missing anything. >> >> >> >> [1] https://etherpad.openstack.org/p/autoscaling-integration-and-feedback >> >> On Tue, Oct 9, 2018 at 2:22 PM Qiming Teng wrote: >> >>> > >One approach would be to switch the underlying Heat AutoScalingGroup >>> > >implementation to use Senlin and then deprecate the AutoScalingGroup >>> > >resource type in favor of the Senlin resource type over several >>> > >cycles. >>> > >>> > The hard part (or one hard part, at least) of that is migrating the >>> existing >>> > data. >>> >>> Agreed. In an ideal world, we can transparently transplant the "scaling >>> group" resource implementation onto something (e.g. a library or an >>> interface). This sounds like an option for both teams to brainstorm >>> together. >>> >>> - Qiming >>> >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> -- >> May The Force of OpenStack Be With You, >> >> *Rico Lin*irc: ricolin >> >> > > -- > May The Force of OpenStack Be With You, > > *Rico Lin*irc: ricolin > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Meeting cancelled for Nov 2
Everyone, There isn't much to talk about this week so I'm cancelling the weekly meeting. The only thing that needs attention is the upgrade checker patch set: https://review.openstack.org/#/c/613788/ If anybody has time, please take a look and see if you can figure out why it is not working. Thanks, Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Meeting cancelled for this week
Everyone, I’m canceling the Senlin meeting this week because I’m unavailable. We will resume at the scheduled time next week. Duc (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Senlin Monthly(ish) Newsletter Oct 2018
HTML: https://dkt26111.wordpress.com/2018/10/17/senlin-monthlyish-newsletter-october-2018/ This is the October edition of the Senlin monthly(ish) newsletter. The goal of the newsletter is to highlight happenings in the Senlin project. If you have any feedback or questions regarding the contents, please feel free to reach out to me in the #senlin IRC channel. News * There will be no Senlin meeting this week (Friday October 19, 2018) because I'm unavailable this week. We will resume regular meetings next week. * Autoscaling forum has been scheduled for the Berlin Summit (https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22753/autoscaling-integration-improvement-and-feedback). Add your comments/feedback to this etherpad: https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Blueprint Status * Fail fast locked resource - https://blueprints.launchpad.net/senlin/+spec/fail-fast-locked-resource - Implementation is completed and has been merged. - Working on documentation and release notes. * Multiple detection modes - https://blueprints.launchpad.net/senlin/+spec/multiple-detection-modes - Implementation is completed and has been merged. - Working on documentation and release notes. * Fail-fast on cooldown for scaling operations - https://blueprints.launchpad.net/senlin/+spec/scaling-action-acceptance - Implementation is completed. - Waiting for more reviews: https://review.openstack.org/#/c/585573/ * OpenStackSDK support senlin function test - Basic test cases have been implemented and merged: https://review.openstack.org/#/c/607061/ * Senlin add support use limit return - Waiting for blueprint submission. * Add zun driver in senlin, use zun manager container - Waiting for blueprint submission. Community Goal Status - * Python 3 - All patches by Python 3 goal champions for zuul migration, documentation and unit test changes have been merged. * Upgrade Checkers - No work has started on this. If you like to help out with this task, please let me know. Recently Merged Changes --- * Multiple detection mode support was added as part of the same blueprint: https://review.openstack.org/#/c/589990/. This change introduces version 1.1 of the health policy that includes breaking changes affecting clusters using the health policy version 1.0. We are working to address this issue. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][plugins] npm jobs fail due to new XStatic-jQuery release (was: Horizon gates are broken)
Hi Shu, Thanks for proposing your fix. It looks good to me. I have submitted a similar patch for senlin-dashboard to unblock the broken gate test [1]. [1] https://review.openstack.org/#/c/607003/ Regards, Duc (dtruong) On Fri, Sep 28, 2018 at 2:24 AM Shu M. wrote: > > Hi Ivan, > > Thank you for your help to our plugins and sorry for bothering you. > I found problem on installing horizon in "post-install", e.g. we should > install horizon with upper-constraints.txt in "post-install". > I proposed patch[1] in zun-ui, please check it. If we can merge this, I will > expand it the other remaining plugins. > > [1] https://review.openstack.org/#/c/606010/ > > Thanks, > Shu Muto > > 2018年9月28日(金) 3:34 Ivan Kolodyazhny : >> >> Hi, >> >> Unfortunately, this issue affects some of the plugins too :(. At least gates >> for the magnum-ui, senlin-dashboard, zaqar-ui and zun-ui are broken now. I'm >> working both with project teams to fix it asap. Let's wait if [5] helps for >> senlin-dashboard and fix all the rest of plugins. >> >> >> [5] https://review.openstack.org/#/c/605826/ >> >> Regards, >> Ivan Kolodyazhny, >> http://blog.e0ne.info/ >> >> >> On Wed, Sep 26, 2018 at 4:50 PM Ivan Kolodyazhny wrote: >>> >>> Hi all, >>> >>> Patch [1] is merged and our gates are un-blocked now. I went throw review >>> list and post 'recheck' where it was needed. >>> >>> We need to cherry-pick this fix to stable releases too. I'll do it asap >>> >>> Regards, >>> Ivan Kolodyazhny, >>> http://blog.e0ne.info/ >>> >>> >>> On Mon, Sep 24, 2018 at 11:18 AM Ivan Kolodyazhny wrote: Hi team, Unfortunately, horizon gates are broken now. We can't merge any patch due to the -1 from CI. I don't want to disable tests now, that's why I proposed a fix [1]. We'd got released some of XStatic-* packages last week. At least new XStatic-jQuery [2] breaks horizon [3]. I'm working on a new job for requirements repo [4] to prevent such issues in the future. Please, do not try 'recheck' until [1] will be merged. [1] https://review.openstack.org/#/c/604611/ [2] https://pypi.org/project/XStatic-jQuery/#history [3] https://bugs.launchpad.net/horizon/+bug/1794028 [4] https://review.openstack.org/#/c/604613/ Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration
On Thu, Sep 27, 2018 at 11:14 AM Zane Bitter wrote: > > > and we will gradually fade out the existing 'AutoScalingGroup' > > and related resource types in Heat. > > That's almost impossible to do without breaking existing users. One approach would be to switch the underlying Heat AutoScalingGroup implementation to use Senlin and then deprecate the AutoScalingGroup resource type in favor of the Senlin resource type over several cycles. Not saying that this is the definitive solution, but it is worth discussing as an option since this follows a path other projects have taken (e.g. nova-volume extraction into cinder). A prerequisite to this approach would probably require Heat to create the so-called common library to house the autoscaling code. Then Senlin would need to achieve feature parity against this autoscaling library before the switch could happen. > > Clearly there are _some_ parts that could in principle be shared. (I > added some comments to the etherpad to clarify what I think Rico was > referring to.) > > It seems to me that there's value in discussing it together rather than > just working completely independently, even if the outcome of that > discussion is that +1. The outcome of any discussion will be beneficial not only to the teams but also the operators and users. Regards, Duc (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [penstack-dev]Discussion about the future of OpenStack in China
Senlin also supports the HA use case via its health policy. On Mon, Sep 24, 2018 at 4:26 PM Zhipeng Huang wrote: > > watcher is known by some, but I don't think Masakari is > > On Tue, Sep 25, 2018 at 5:47 AM Matt Riedemann wrote: >> >> On 9/24/2018 12:12 PM, Jay Pipes wrote: >> > There were a couple points that I did manage to decipher, though. One >> > thing that both articles seemed to say was that OpenStack doesn't meet >> > public (AWS-ish) cloud use cases and OpenStack doesn't compare favorably >> > to VMWare either. >> >> Yeah I picked up on that also - trying to be all things to all people >> means we do less well at any single thing. No surprises there. >> >> > >> > Is there a large contingent of Chinese OpenStack users that expect >> > OpenStack to be a free (as in beer) version of VMware technology? >> > >> > What are the 3 most important features that Chinese OpenStack users >> > would like to see included in OpenStack projects? >> >> Yeah I picked up on a few things as well. The article was talking about >> gaps in upstream services: >> >> a) they did a bunch of work on trove for their dbaas solution, but did >> they contribute any of that work? >> >> b) they mentioned a lack of DRS and HA support, but didn't mention the >> Watcher or Masakari projects - maybe they didn't know they exist? >> >> -- >> >> Thanks, >> >> Matt >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Zhipeng (Howard) Huang > > Standard Engineer > IT Standard & Patent/IT Product Line > Huawei Technologies Co,. Ltd > Email: huangzhip...@huawei.com > Office: Huawei Industrial Base, Longgang, Shenzhen > > (Previous) > Research Assistant > Mobile Ad-Hoc Network Lab, Calit2 > University of California, Irvine > Email: zhipe...@uci.edu > Office: Calit2 Building Room 2402 > > OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Senlin Monthly(ish) Newsletter Sep 2018
HTML: https://dkt26111.wordpress.com/2018/09/19/senlin-monthlyish-newsletter-september-2018/ This is the inaugural Senlin monthly(ish) newsletter. The goal of the newsletter is to highlight happenings in the Senlin project. If you have any feedback or questions regarding the contents, please feel free to reach out to me or anyone in the #senlin IRC channel. News * Senlin weekly meeting time was changed at the beginning of the Stein cycle to 5:30 UTC every Friday. Feel free to drop in. * Two new core members were added to the Senlin project. Welcome jucross and eandersson. * One new stable reviewer was added for Senlin stable maintainance. Welcome chenyb4. * Autoscaling forum is being proposed for the Berlin Summit (http://lists.openstack.org/pipermail/openstack-dev/2018-September/134770.html). Add your comments/feedback to this etherpad: https://etherpad.openstack.org/p/autoscaling-integration-and-feedback Blueprint Status * Fail fast locked resource - https://blueprints.launchpad.net/senlin/+spec/fail-fast-locked-resource - Spec was approved and implementation is WIP. * Multiple detection modes - https://blueprints.launchpad.net/senlin/+spec/multiple-detection-modes - Spec approval is pending (https://review.openstack.org/#/c/601471/). * Fail-fast on cooldown for scaling operations - Waiting for blueprint/spec submission. * OpenStackSDK support senlin function test - Waiting for blueprint submission. * Senlin add support use limit return - Waiting for blueprint submission. * Add zun driver in senlin, use zun manager container - Waiting for blueprint submission. Community Goal Status - * Python 3 - All patches by Python 3 goal champions for zuul migration, documentation and unit test changes have been merged. * Upgrade Checkers - No work has started on this. If you like to help out with this task, please let me know. Recently Merged Changes --- * Bug# 174 was fixed (https://review.openstack.org/#/c/594643/) * Improvements to node poll URL mode in health policy (https://review.openstack.org/#/c/588674/) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration
Thanks for creating the etherpad. I have added a question on the common library in the etherpad. I think we can iterate on the basic proposal before the forum in Berlin so that we can get input from developers who won't be able to attend in person. On Tue, Sep 18, 2018 at 11:46 AM Rico Lin wrote: > cool Duc, and it's nicely started: > https://etherpad.openstack.org/p/autoscaling-integration-and-feedback > I also submit the etherpad, will add you as moderator once it's selected > (don't know why, but can't add any more now from the web). > > Please add whatever you like to that etherpad, I will try to input more > information ASAP. > all information will continue to be used with or without that forum. > > On Wed, Sep 19, 2018 at 12:51 AM Duc Truong > wrote: > >> Hi Rico, >> >> I'm the Senlin PTL and would be happy to have a forum discussion in >> Berlin about the future of autoscaling. >> >> Can you go ahead and start an etherpad to capture the proposed agenda >> and discussion items? Also, feel free to submit the forum submission >> so that we can get it on the schedule. >> >> Thanks, >> >> Duc (dtruong) >> >> On Mon, Sep 17, 2018 at 8:28 PM Rico Lin >> wrote: >> >>> *TL;DR* >>> *How about a forum in Berlin for discussing autoscaling integration (as >>> a long-term goal) in OpenStack?* >>> >>> >>> Hi all, as we start to discuss how can we join develop from Heat and >>> Senlin as we originally planned when we decided to fork Senlin from Heat >>> long time ago. >>> >>> IMO the biggest issues we got now are we got users using autoscaling in >>> both services, appears there is a lot of duplicated effort, and some great >>> enhancement didn't exist in another service. >>> As a long-term goal (from the beginning), we should try to join >>> development to sync functionality, and move users to use Senlin for >>> autoscaling. So we should start to review this goal, or at least we should >>> try to discuss how can we help users without break or enforce anything. >>> >>> What will be great if we can build common library cross projects, and >>> use that common library in both projects, make sure we have all improvement >>> implemented in that library, finally to use Senlin from that from that >>> library call in Heat autoscaling group. And in long-term, we gonna let all >>> user use more general way instead of multiple ways but generate huge >>> confusing for users. >>> >>> *As an action, I propose we have a forum in Berlin and sync up all >>> effort from both teams to plan for idea scenario design. The forum >>> submission [1] ended at 9/26.* >>> Also would benefit from both teams to start to think about how they can >>> modulize those functionalities for easier integration in the future. >>> >>> From some Heat PTG sessions, we keep bring out ideas on how can we >>> improve current solutions for Autoscaling. We should start to talk about >>> will it make sense if we combine all group resources into one, and inherit >>> from it for other resources (ideally gonna deprecate rest resource types). >>> Like we can do Batch create/delete in Resource Group, but not in ASG. We >>> definitely got some unsynchronized works inner Heat, and cross Heat and >>> Senlin. >>> >>> Please let me know who is interesting in this idea, so we can work >>> together and reach our goal step by step. >>> Also please provide though if you got any concerns about this proposal. >>> >>> [1] https://www.openstack.org/summit/berlin-2018/call-for-presentations >>> -- >>> May The Force of OpenStack Be With You, >>> >>> *Rico Lin*irc: ricolin >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > -- > May The Force of OpenStack Be With You, > > *Rico Lin*irc: ricolin > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration
Hi Rico, I'm the Senlin PTL and would be happy to have a forum discussion in Berlin about the future of autoscaling. Can you go ahead and start an etherpad to capture the proposed agenda and discussion items? Also, feel free to submit the forum submission so that we can get it on the schedule. Thanks, Duc (dtruong) On Mon, Sep 17, 2018 at 8:28 PM Rico Lin wrote: > *TL;DR* > *How about a forum in Berlin for discussing autoscaling integration (as a > long-term goal) in OpenStack?* > > > Hi all, as we start to discuss how can we join develop from Heat and > Senlin as we originally planned when we decided to fork Senlin from Heat > long time ago. > > IMO the biggest issues we got now are we got users using autoscaling in > both services, appears there is a lot of duplicated effort, and some great > enhancement didn't exist in another service. > As a long-term goal (from the beginning), we should try to join > development to sync functionality, and move users to use Senlin for > autoscaling. So we should start to review this goal, or at least we should > try to discuss how can we help users without break or enforce anything. > > What will be great if we can build common library cross projects, and use > that common library in both projects, make sure we have all improvement > implemented in that library, finally to use Senlin from that from that > library call in Heat autoscaling group. And in long-term, we gonna let all > user use more general way instead of multiple ways but generate huge > confusing for users. > > *As an action, I propose we have a forum in Berlin and sync up all effort > from both teams to plan for idea scenario design. The forum submission [1] > ended at 9/26.* > Also would benefit from both teams to start to think about how they can > modulize those functionalities for easier integration in the future. > > From some Heat PTG sessions, we keep bring out ideas on how can we improve > current solutions for Autoscaling. We should start to talk about will it > make sense if we combine all group resources into one, and inherit from it > for other resources (ideally gonna deprecate rest resource types). Like we > can do Batch create/delete in Resource Group, but not in ASG. We definitely > got some unsynchronized works inner Heat, and cross Heat and Senlin. > > Please let me know who is interesting in this idea, so we can work > together and reach our goal step by step. > Also please provide though if you got any concerns about this proposal. > > [1] https://www.openstack.org/summit/berlin-2018/call-for-presentations > -- > May The Force of OpenStack Be With You, > > *Rico Lin*irc: ricolin > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [senlin][stable] Nominating chenyb4 to Senlin Stable Maintainers Team
Voting has concluded. Welcome chenyb4 to the Senlin stable review team. On Thu, Sep 13, 2018 at 10:50 PM Qiming Teng wrote: > > +2 from me. > > Thanks. > - Qiming > > On Mon, Sep 10, 2018 at 09:56:10AM -0700, Duc Truong wrote: > > Hi Senlin Stable Team, > > > > I would like to nominate Yuanbin Chen (chenyb4) to the Senlin stable > > review team. Yuanbin has been doing stable reviews and shown that he > > understands the policy for merging stable patches [1]. > > > > Voting is open for 7 days. Please reply with your +1 vote in favor or > > -1 as a veto vote. > > > > [1] > > https://review.openstack.org/#/q/branch:%255Estable/.*+reviewedby:cybing4%2540gmail.com > > > > Regards, > > > > Duc (dtruong) > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [senlin] Nominations to Senlin Core Team
Voting has concluded. Welcome Jude and Erik to the Senlin Core team. On Thu, Sep 13, 2018 at 12:14 AM x Lyn wrote: > > +1 to both, looking forward to their future contribution. > > > On Sep 11, 2018, at 12:59 AM, Duc Truong wrote: > > > > Hi Senlin Core Team, > > > > I would like to nominate 2 new core reviewers for Senlin: > > > > [1] Jude Cross (jucr...@blizzard.com) > > [2] Erik Olof Gunnar Andersson (eanders...@blizzard.com) > > > > Jude has been doing a number of reviews and contributed some important > > patches to Senlin during the Rocky cycle that resolved locking > > problems. > > > > Erik has the most number of reviews in Rocky and has contributed high > > quality code reviews for some time. > > > > [1] > > http://stackalytics.com/?module=senlin-group=marks=rocky_id=jucr...@blizzard.com > > [2] > > http://stackalytics.com/?module=senlin-group=marks_id=eandersson=rocky > > > > Voting is open for 7 days. Please reply with your +1 vote in favor or > > -1 as a veto vote. > > > > Regards, > > > > Duc (dtruong) > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Nominations to Senlin Core Team
Hi Senlin Core Team, I would like to nominate 2 new core reviewers for Senlin: [1] Jude Cross (jucr...@blizzard.com) [2] Erik Olof Gunnar Andersson (eanders...@blizzard.com) Jude has been doing a number of reviews and contributed some important patches to Senlin during the Rocky cycle that resolved locking problems. Erik has the most number of reviews in Rocky and has contributed high quality code reviews for some time. [1] http://stackalytics.com/?module=senlin-group=marks=rocky_id=jucr...@blizzard.com [2] http://stackalytics.com/?module=senlin-group=marks_id=eandersson=rocky Voting is open for 7 days. Please reply with your +1 vote in favor or -1 as a veto vote. Regards, Duc (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin][stable] Nominating chenyb4 to Senlin Stable Maintainers Team
Hi Senlin Stable Team, I would like to nominate Yuanbin Chen (chenyb4) to the Senlin stable review team. Yuanbin has been doing stable reviews and shown that he understands the policy for merging stable patches [1]. Voting is open for 7 days. Please reply with your +1 vote in favor or -1 as a veto vote. [1] https://review.openstack.org/#/q/branch:%255Estable/.*+reviewedby:cybing4%2540gmail.com Regards, Duc (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] weekly meeting
Hi everyone, We'll be having our weekly meeting today at 0530 UTC in the #senlin channel. The meeting agenda has been posted: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282018-08-31_0530_UTC.29 Regards, Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Senlin Weekly Meeting Time Change
Thanks everyone for replying. Since there were no objections, we will move to the new meeting time. Our first meeting will be this week on Friday August 24 at 5:30 UTC. The meeting agenda has been posted: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282018-08-24_0530_UTC.29 Feel free to add any items you want to discuss. Looking forward to seeing everyone at the meeting. Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [senlin] Senlin Weekly Meeting Time Change
Hi, As we are starting the Stein cycle, I would like to start having weekly meetings again for Senlin. I'm proposing to move the weekly meeting to the following time: Friday 5:30 UTC to 6:30 UTC in #senlin channel Please reply if this works for you or reply with an alternative time slot. Thanks, Duc __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Senlin][PTL][Election] Candidacy for Senlin PTL for Stein
Hello everyone, I'd like to announce my candidacy for the Senlin PTL position during the Stein cycle. I've been contributing to Senlin since the Queens cycle and became a core reviewer during the Rocky cycle. I work for Blizzard Entertainment where I'm an active operator and upstream developer for Senlin. I believe this dual role gives me a unique perspective on the use cases for Senlin. If elected as PTL, I will focus on the following priorities: * Testing: More integration tests are needed to avoid any regression due to new feature implementations. More rally tests are needed to cover stress testing scenarios in HA deployments of Senlin. * Bug fixes: Actively monitor incoming bug reports and triage them. Clean out old bugs that can no longer be reproduced. * Technical debt: Identify areas of code that can be reimplemented more efficiently and/or simplified. * User documentation: Restructure the Senlin documentation to make it easier for the users to find the relevant information. * Grow the Senlin community: My goal is to grow the Senlin user base and encourage more developers to contribute. To do so, I propose changing the weekly meetings to office hours and hold those office hours consistently so that new users and/or developers can ask questions and receive feedback. Moreover, I want to increase Senlin's visibility in the developer community by more actively using the mailing list. One idea would be to send out Senlin project updates to the mailing list throughout the cycle like many other projects are doing now. Thanks for your consideration. Duc Truong (dtruong) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
