Re: [openstack-dev] [ClusterLabs Developers] [HA] future of OpenStack OCF resource agents (was: resource-agents v4.2.0)

Hi Tim, Tim Bell wrote: Adam, Personally, I would prefer the approach where the OpenStack resource agents are part of the repository in which they are used. Thanks for chipping in. Just checking - by this you mean the resource-agents rather than openstack-resource-agents, right?

Re: [openstack-dev] [ClusterLabs Developers] [HA] future of OpenStack OCF resource agents (was: resource-agents v4.2.0)

[cross-posting to openstack-dev] Oyvind Albrigtsen wrote: ClusterLabs is happy to announce resource-agents v4.2.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0 The most significant enhancements in this release are: - new resource agents:

[openstack-dev] [infra] Gerrit User Summit, November 2018

Hi all, The next forthcoming Gerrit User Summit 2018 will be Nov 15th-16th in Palo Alto, hosted by Cloudera. See the Gerrit User Summit page at: https://gerrit.googlesource.com/summit/2018/+/master/index.md and the event registration at: https://gus2018.eventbrite.com Hopefully some

Re: [openstack-dev] [Openstack-sigs] [self-healing][heat][vitrage][mistral] Self-Healing with Vitrage, Heat, and Mistral

Hi Rico, Firstly sorry for the slow reply! I am finally catching up on my backlog. Rico Lin wrote: Dear all Back to Vancouver Summit, Ifat brings out the idea of integrating Heat, Vitrage, and Mistral to bring better self-healing scenario. For previous works, There already works cross Heat,

Re: [openstack-dev] PTG Denver Horns

Matthew Thode wrote: On 18-08-07 23:18:26, David Medberry wrote: Requests have finally been made (today, August 7, 2018) to end the horns on the train from Denver to Denver International airport (within the city limits of Denver.) Prior approval had been given to remove the FLAGGERS that were

Re: [openstack-dev] [sig][upgrades][ansible][charms][tripleo][kolla][airship] reboot or poweroff?

[Adding openstack-sigs list too; apologies for the extreme cross-posting, but I think in this case the discussion deserves wide visibility. Happy to be corrected if there's a better way to handle this.] Hi James, James Page wrote: Hi All tl;dr we (the original founders) have not managed to

Re: [openstack-dev] [ptg] Self-healing SIG meeting moved to Thursday morning

Thierry Carrez wrote: Hi! Quick heads-up: Following a request[1] from Adam Spiers (SIG lead), we modified the PTG schedule to move the Self-Healing SIG meeting from Friday (all day) to Thursday morning (only morning). You can see the resulting schedule at: https://www.openstack.org/ptg

Re: [openstack-dev] [self-healing] [ptg] [monasca] PTG track schedule published

could probably offer you half-day of Monasca slot on Monday or Tuesday afternoon. I'm afraid though that our room might be too small for you. Cheers Witek -Original Message- From: Thierry Carrez Sent: Freitag, 20. Juli 2018 18:46 To: Adam Spiers Cc: openstack-dev mailing list

Re: [openstack-dev] [self-healing] [ptg] PTG track schedule published

Thierry Carrez wrote: Thierry Carrez wrote: Hi everyone, Last month we published the tentative schedule layout for the 5 days of PTG. There was no major complaint, so that was confirmed as the PTG event schedule and published on the PTG website: https://www.openstack.org/ptg#tab_schedule

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Doug Hellmann wrote: Excerpts from Adam Spiers's message of 2018-04-25 18:15:42 +0100: [BTW I hope it's not considered off-bounds for those of us who aren't TC election candidates to reply within these campaign question threads to responses from the candidates - but if

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

[BTW I hope it's not considered off-bounds for those of us who aren't TC election candidates to reply within these campaign question threads to responses from the candidates - but if so, let me know and I'll shut up ;-) ] Zhipeng Huang wrote: Culture wise, being too

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini wrote: On 15/03/2018 01:57, Ghanshyam Mann wrote: Thanks all for starting the collaboration on this which is long pending things and we all want to have some start on this. Myself and SamP talked about it during OPS meetup in Tokyo and we talked about below

[openstack-dev] [self-healing] Dublin PTG summary, and request for feedback

Hi all, I just posted a summary of the Self-healing SIG session at the Dublin PTG: http://lists.openstack.org/pipermail/openstack-sigs/2018-March/000317.html If you are interested in the topic of self-healing within OpenStack, you are warmly invited to subscribe to the openstack-sigs mailing

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini <ra...@redhat.com> wrote: On 08/03/2018 17:03, Adam Spiers wrote: [...] Yes agreed again, this is a strong case for collaboration between the self-healing and QA SIGs.  In Dublin we also discussed the idea of the self-healing and API SIGs collaborating on the related

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Georg Kunz wrote: Hi Adam, Raoul Scarazzini wrote: In the meantime, I'll check yardstick to see which kind of bridge we can build to avoid reinventing the wheel. Great, thanks! I wish I could immediately help with this, but I haven't had the

Re: [openstack-dev] [kolla] PTG Summary

Paul Bourke wrote: Hi all, Here's my summary of the various topics we discussed during the PTG. There were one or two I had to step out for but hopefully this serves as an overall recap. Please refer to the main etherpad[0] for more details and links to the session

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini <ra...@redhat.com> wrote: On 06/03/2018 13:27, Adam Spiers wrote: Hi Raoul and all, Sorry for joining this discussion late! [...] I do not work on TripleO, but I'm part of the wider OpenStack sub-communities which focus on HA[0] and more recently, self-hea

Re: [openstack-dev] [TripleO][CI][QA][HA] Validating HA on upstream

Hi Raoul and all, Sorry for joining this discussion late! Raoul Scarazzini wrote: TL;DR: we would like to change the way HA is tested upstream to avoid being hitten by evitable bugs that the CI process should discover. Long version: Today HA testing in upstream consist

Re: [openstack-dev] [masakari] Any masakari folks at the PTG this week ?

My claim to being a masakari person is pretty weak, but still I'd like to say hello too :-) Please ping me (aspiers on IRC) if you guys are meeting up! Bhor, Dinesh wrote: Hi Greg, We below are present: Tushar Patil(tpatil) Yukinori Sagara(sagara) Abhishek

[openstack-dev] [self-healing][PTG] etherpad for PTG session on self-healing

Hi all, Yushiro kindly created an etherpad for the self-healing SIG session at the Dublin PTG on Tuesday afternoon next week, and I've fleshed it out a bit: https://etherpad.openstack.org/p/self-healing-ptg-rocky Anyone with an interest in self-healing is of course very welcome to attend

Re: [openstack-dev] Etherpad for self-healing

Furukawa, Yushiro wrote: Hi everyone, I am seeing Self-healing scheduled on Tuesday afternoon[1], but the etherpad for it is not listed in [2]. I made following etherpad by some chance. Thanks! You beat me to it ;-) Would it be possible to update Etherpads

[openstack-dev] Remembering Shawn Pearce (fwd)

/01/30/gerrithub-io-donations-to-shawns-family/ Thank you Shawn for enriching our lives with your great contributions to the FLOSS community. - Forwarded message from Adam Spiers <aspi...@suse.com> - Date: Fri, 2 Feb 2018 15:12:35 + From: Adam Spiers <aspi...@suse.com&

[openstack-dev] ANNOUNCE: Self-healing SIG officially formed (fwd)

As per below, I'm happy to announce that the Self-healing SIG is now officially formed. For now, all discussions will happen on <openstack-s...@lists.openstack.org>, so please subscribe to that list if you are interested in this topic! Cheers, Adam - Forwarded message from Adam

Re: [openstack-dev] [all][deployment][kolla][tripleo][osa] Service diagnostics task force

Michał Jastrzębski wrote: Hello my dearest of communities, During deployment tools session on PTG we discussed need for deep health checking and metering of running services. It's very relevant in context of containers (especially k8s) and HA. Things like watchdog, heartbeats

[openstack-dev] [Openstack-sigs] [meta] Proposal for self-healing SIG (fwd)

! Adam - Forwarded message from Adam Spiers <aspi...@suse.com> - Date: Sun, 17 Sep 2017 23:35:02 +0100 From: Adam Spiers <aspi...@suse.com> To: OpenStack SIGs list <openstack-s...@lists.openstack.org> Subject: [Openstack-sigs] [meta] Proposal for self-healing SIG Hi all,

Re: [openstack-dev] [oslo][barbican][sahara] start RPC service before launcher wait?

ent > threads to the same TaskServer instance: > > https://paste.fedoraproject.org/paste/dyPq~lr26sQZtMzHn5w~Vg > > Is that expected? Unfortunately in the interim, your pastes seem to have vanished - any chance you could repaste them? Thanks, Adam > On Mon, Jul 31, 2017 at 9:32 PM, Ada

Re: [openstack-dev] [oslo][barbican][sahara] start RPC service before launcher wait?

Ken Giusti <kgiu...@gmail.com> wrote: On Mon, Jul 31, 2017 at 10:01 AM, Adam Spiers <aspi...@suse.com> wrote: I recently discovered a bug where barbican-worker would hang on shutdown if queue.asynchronous_workers was changed from 1 to 2: https://bugs.launchpad.net/barbican/

[openstack-dev] [oslo][barbican][sahara] start RPC service before launcher wait?

Hi all, I recently discovered a bug where barbican-worker would hang on shutdown if queue.asynchronous_workers was changed from 1 to 2: https://bugs.launchpad.net/barbican/+bug/1705543 resulting in a warning like this: WARNING oslo_messaging.server [-] Possible hang: stop is waiting for

Re: [openstack-dev] [vitrage] [nova] [HA] [masakari] VM Heartbeat / Healthcheck Monitoring

inking of including this user story in the scope of what masakari would be looking at ? Greg. From: Adam Spiers <aspi...@suse.com> Reply-To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date: Wednesday, May 17, 2017 at 10:08 AM To: "openstack-dev@li

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

- Aodh - ... - VNF-Manager - (StateChange) - Nova - ... - VNF Manager Greg. From: Adam Spiers <aspi...@suse.com> Reply-To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

t when you were talking about host-monitoring, you were looking at having alternative backends for reporting e.g. to masakari-api or to mistral or ... to Vitrage :) Greg. From: Adam Spiers <aspi...@suse.com> Reply-To: "openstack-dev@lists.openstack.org" <openstack-dev@

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

Waines, Greg wrote: Sam, Two other more higher-level points I wanted to discuss with you about Masaraki. First, so I notice that you are doing both monitoring, auto-recovery and even host maintenance type functionality as part of the Masaraki architecture. are

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

Waines, Greg wrote: thanks for the pointers Sam. I took a quick look. I agree that the VM Heartbeat / Health-check looks like a good fit into Masakari. Currently your instance monitoring looks like it is strictly black-box type monitoring thru libvirt events. Is

Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck Monitoring

Afek, Ifat (Nokia - IL/Kfar Sava) wrote: On 16/05/2017, 4:36, "Sam P" wrote: Hi Greg, In Masakari [0] for VMHA, we have already implemented some what similar function in masakri-monitors. Masakari-monitors runs on nova-compute node,

[openstack-dev] [HA] follow-up from HA discussion at Boston Forum

Hi all, Sam P wrote: This is a quick reminder for HA Forum session at Boston Summit. Thank you all for your comments and effort to make this happen in Boston Summit. Time: Thu 11 , 11:00am-11:40am Location: Hynes Convention Center - Level One - MR 103 Etherpad:

Re: [openstack-dev] [Openstack] OpenStack-Ansible HA solution

Wei Hui wrote: Liyuenan (Maxwell Li) wrote: Hi, all I have some questions about OSA project. [snipped] 2. Could OSA support compute node high available? If my compute node down, could the instance on this node move to other nodes? 2. As

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

Anil Venkata <anilvenk...@redhat.com> wrote: > On Thu, Feb 23, 2017 at 12:10 AM, Miguel Angel Ajo Pelayo > <majop...@redhat.com> wrote: > > On Wed, Feb 22, 2017 at 11:28 AM, Adam Spiers <aspi...@suse.com> wrote: > >> With help from others, I have started an

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

Kosnik, Lubosz wrote: > About success of RDO we need to remember that this deployment utilizes > Peacemaker and when I was working on this feature and even I spoke with Assaf > this external application was doing everything to make this solution working. > Peacemaker

Re: [openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Timur Nurlygayanov wrote: > Hi OpenStack developers and operators, > > we are going to create the test suite for destructive testing of > OpenStack clouds. We want to hear your feedback and ideas > about possible destructive and failover scenarios which we need > to

Re: [openstack-dev] [Openstack] The possible ways of high availability for non-cloud-ready apps running on openstack

Hi Hossein, hossein zabolzadeh wrote: > Hi there. > I am dealing with large amount of legacy application(MediaWiki, Joomla, > ...) running on openstack. I am looking for the best way to improve high > availability of my instances. All applications are not designed for >

Re: [openstack-dev] [HA] RFC: High Availability track at future Design Summits

Hi Thierry, Thierry Carrez <thie...@openstack.org> wrote: > Adam Spiers wrote: > > I doubt anyone would dispute that High Availability is a really > > important topic within OpenStack, yet none of the OpenStack > > conferences or Design Summits so far have p

[openstack-dev] [HA] RFC: High Availability track at future Design Summits

Hi all, I doubt anyone would dispute that High Availability is a really important topic within OpenStack, yet none of the OpenStack conferences or Design Summits so far have provided an "official" track or similar dedicated space for discussion on HA topics. This is becoming increasingly

[openstack-dev] [HA] weekly High Availability meetings on IRC: change of time

Hi everyone, I have proposed moving the weekly High Availability IRC meetings one hour later, back to the original time of 0900 UTC every Monday. https://review.openstack.org/#/c/349601/ Everyone is welcome to attend these meetings, so if you think you are likely to regularly attend, feel

[openstack-dev] [HA] RFC: user story including hypervisor reservation / host maintenance / storage AZs / event history

[Cc'ing product-wg@ - when replying, first please consider whether cross-posting is appropriate] Hi all, Currently the OpenStack HA community is putting a lot of effort into converging on a single upstream solution for high availability of VMs and hypervisors[0], and we had a lot of very

Re: [openstack-dev] [HA] About next HA Team meeting (VoIP)

Sam P wrote: > Hi All, > > In today's ( 9th May 2016) meeting we agree to skip the next IRC > meeting (which is 16th May 2016) in favour of a gotomeeting VoIP on > 18th May 2016 (Wednesday). > Today's meeting logs and summary can be found here. >

Re: [openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Sergii Golovatiuk wrote: > > > [2] declares meetings at 9am UTC which might be tough for US based > > folks. I > > > might be wrong here as I don't know the location of HA experts. > > > > > > [2] http://eavesdrop.openstack.org/#High_Availability_Meeting > > > > Yes, I

Re: [openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Hi Sergii, Thanks a lot for the feedback! Sergii Golovatiuk wrote: > Hi Adam, > > It's great we are moving forward with HA community. Thank you so much for > brining HA to next level. However, I have couple of comments > > [1] contains agenda. I guess we should move

[openstack-dev] [HA] ANNOUNCE: new "[HA]" topic category in mailman configuration

Hi all, As you may know, Mailman allows server-side filtering of mailing list traffic by topic categories: http://lists.openstack.org/cgi-bin/mailman/options/openstack-dev (N.B. needs authentication) Thierry has kindly added "[HA]" as a new topic category in the mailman configuration for

[openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Hi all, After some discussion in Tokyo by stakeholders in OpenStack High Availability, I'm pleased to announce that from next Monday we're starting a series of weekly meetings on IRC. Details are here: https://wiki.openstack.org/wiki/Meetings/HATeamMeeting

Re: [openstack-dev] [ANNOUNCE] [HA] new #openstack-ha IRC channel on FreeNode

Sorry! It would have helped if I'd used the right address for the openstack list in the To: and Reply-To: headers :-/ Hopefully second time lucky ... Adam Spiers <aspi...@suse.com> wrote: > [cross-posting to several lists; please trim the recipients list > before replying!]

[openstack-dev] [ANNOUNCE] [HA] new #openstack-ha IRC channel on FreeNode

[cross-posting to several lists; please trim the recipients list before replying!] Hi all, After discussion with members of the openstack-infra team, I registered new FreeNode IRC channel #openstack-ha. Discussion on all aspects of OpenStack High Availability is welcome in this channel.

[openstack-dev] [ANNOUNCE] [HA] [Pacemaker] new, maintained openstack-resource-agents repository

[cross-posting to openstack-dev and pacemaker user lists; please consider trimming the recipients list if your reply is not relevant to both communities] Hi all, Back in June I proposed moving the well-used but no longer maintained https://github.com/madkiss/openstack-resource-agents/ repository

[openstack-dev] [HA] RFC: moving Pacemaker openstack-resource-agents to stackforge

[cross-posting to openstack-dev and pacemaker lists; please consider trimming the recipients list if your reply is not relevant to both communities] Hi all, https://github.com/madkiss/openstack-resource-agents/ is a nice repository of Pacemaker High Availability resource agents (RAs) for

Re: [openstack-dev] [ClusterLabs] [HA] RFC: moving Pacemaker openstack-resource-agents to stackforge

Digimer li...@alteeve.ca wrote: Resending to the Cluster Labs mailing list, this list is deprecated Thanks, I only realised that after getting a deprecation warning :-( On 23/06/15 06:27 AM, Adam Spiers wrote: [cross-posting to openstack-dev and pacemaker lists; please consider trimming

[openstack-dev] tools for making upstreaming / backporting easier in git

Hi all, Back in April, I created some wrapper scripts around git-cherry(1) and git-notes(1), which can help when you have more than a trivial number of commits to upstream or backport from one branch to another. Since then I've improved these tools, and also written a higher-level CLI which