Laurent, *: In german: "Am Ast saegen auf dem man sitzt", aka:
https://www.fotocommunity.de/photo/am-ast-saegen-auf-dem-man-sitzt-smithi/32932119 Not sure what the best english equivalent saying is. In german there are actually multiple of these idioms. In networking this problem is inband management of IP networks. You use use IP network that you configure to provide you connectibity for that configuration. Epic Fail. Thats why in Data Centers and SPs you stil often have separate out-of-band management networks. ACP is the best current attempt to solve this issue without the cost overhead of a separate out-of-band-network. The google incident is exactly solved by ACP: The ACP is absent of any configuration. Therefore also absent of any misconfiguration. The magic of resilience lies in the correct layering. In the best of implementation designs, the whole ACP implementation on a node is running on resources that nobody can misconfigure and any user traffic and contrl plane configuration does not touch it. This is perfectly possible by combining ACP IETF spec with appropriate implementation techniques on the nodes. At IEEE IRIC 2016 conference, i had some slides, showing for example, how one could consider to put ACP into the firmware of a BMC on every node. And you could segment the NPU as well. Not rocket science. Just better engineering than what's done today. Cheers Toerless On Fri, Dec 18, 2020 at 08:42:02AM +0000, Ciavaglia, Laurent (Nokia - FR/Paris-Saclay) wrote: > Hi Brian, > > Thanks for sharing interesting incidents and reflecting on the role of ANIMA > technologies. > > Reading the report, it seems the outage results from a series of indirectly > linked events > leading to isolation of a portion of the GCP network. > > For the incident you refer here, how/where would you see ANIMA components to > have (helped) avoided the outage? > Could we expect ANIMA networks to provide better/longer data plane operation > in case of failed control plane/control plane functions? Beyond the pure > ability to do so, there is a gain/risk trade-off to let a DP run out of sync > of its CP. > Could we expect ANIMA components to have reacted differently and circumvent > the issue, preventing the full disconnection of the GCP network portion? Or > mitigated at intermediate points? > The incident seems to have been triggered by a legitimate/valid configuration > change but with resulting with a functionality loosing its access to files it > needed to perform. The config. change validation basically didn't notice > there was a possible issue. > Would such a miss been caught by ANIMA components? (e.g. via a different > validation-dependencies approach?) > > Why I'm a bit doubtful here is because even if we deploy robust autonomic > functions/agents, the above problem seems to originate from an issue in how > the system has been configured. > And even ASAs would still need to get some form/level of initial > configuration or guidance. > > > Best regards, > Laurent > > > -----Original Message----- > > From: Anima <[email protected]> On Behalf Of Brian E Carpenter > > Sent: Thursday, December 17, 2020 02:47 > > To: Anima WG <[email protected]> > > Subject: Re: [Anima] ANIMA when there is a system-wide issue > > > > And here's what happens when the control plane itself falls over: > > > > https://status.cloud.google.com/incident/zall/20011#20011006 > > > > It seems pretty clear that Cloud needs ANIMA. > > > > Regards > > Brian > > > > On 01-Dec-20 11:02, Brian E Carpenter wrote: > > > "AWS reveals it broke itself by exceeding OS thread limits" > > > > > > https://www.theregister.com/2020/11/30/aws_outage_explanation/ > > > > > > Especially: > > > "The TIFU-like post also outlines why Amazon's dashboards offered only > > scanty info about the incident ??? because they, too, depend on a service > > that depends on Kinesis." > > > > > > Perhaps there is something we should specify in ANIMA to prevent the > > ANIMA infrastructure falling into this sort of trap: when there is a > > system-wide issue (such as hitting an O/S resource limit everywhere at the > > same time) it also prevents the autonomic mechanisms from working. > > > > > > Regards > > > Brian Carpenter > > > > > > > _______________________________________________ > > Anima mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/anima > _______________________________________________ > Anima mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/anima -- --- [email protected] _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
