Re: CF app that helps with self-healing
Daniel Mikusa
Not sure I totally get what you are asking, but `cf restart-app-instance` will restart an instance, so if you have an alert trigger a script, you could script the restart. Or you could just have the app itself know when it gets into a bad state, presumably it would if it's emitting the metrics to indicate this, and exit. When it exits the platform will just restart the app. Dan On Fri, Jan 24, 2020 at 12:30 PM Siva <mailsiva@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
CF app that helps with self-healing
Siva <mailsiva@...>
Dear CF community, We are trying to find a way to selectively restart some instances of apps or to restart a specific app on an as needed basis based on some alerts that we receive from our monitoring solution. One option we are considering is to have a self-healing app deployed in CF which will have some REST endpoints exposed which we can call from our alert policies that will perform those actions for us. This self-healing app will essentially have the capabilities of CF CLI for stopping and starting services and instances. This app will also be protected by UAA. Before we go off and start developing this app, I wanted to check if anyone in the CF community has thought about this approach before and have a solution in place or any ideas to consider. Thanks, Siva Balan |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Cloud Foundry Summit is BACK - Submit a Talk!
Dear cloud foundry community, It is not every day that you see two emails from me in one day :-) I wanted to make sure you all received this and noticed the link[1] to CF Summit CFP and the timeline:
We look forward to seeing you all at Summit. Please do not hesitate to contact any of us at the Foundation if you have any questions. -- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more. ---------- Forwarded message --------- From: Deborah Giles <dgiles@...> Date: Thu, Jan 23, 2020 at 12:00 PM Subject: Cloud Foundry Summit is BACK - Submit a Talk! To: <spodila@...>
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
New lead for Community (CAB) meetings
Dear CF Community, Max (popularly known as "Dr. Max", cc'd here) has been running Cloud Foundry Community Advisory Board (CAB) meetings for the past 4-ish years now. As he mentioned during the recent calls, 2020 is a great opportunity for any of you in the community to nominate yourself (or someone you know is interested) to take the baton from Max. Max will continue being an active member of our community; we just think that other members may want to take an opportunity to step up and make their mark in our community. The responsibilities will be to host
If you are unsure of the responsibilities or if you would like to talk to Max directly, please feel free to reach out to him. Please send us your nominations no later than February 5th. -- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry FoundationYou can read more about pronouns here, or please ask if you'd like to find out more. |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: UAA Deployment
#uaa
Dr Nic Williams <drnicwilliams@...>
I coded up running UAA locally awhile back and you might find something useful in my scripts, or consider using the scripts yourself Nic -- |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
UAA Deployment
#uaa
santiago@...
Hello,
I'm facing issues when trying to deploy a war file into Tomcat.I can build the file and everything but after deploying it into Tomcat I'm getting the below error. Can anyone help me? thanks! Exception javax.servlet.ServletException: Servlet.init() for servlet [spring] threw exception org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1598) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.base/java.lang.Thread.run(Thread.java:834) Root Cause java.lang.IllegalStateException: Listeners cannot be added to context [/uaa] as the context has been initialised org.cloudfoundry.identity.uaa.impl.config.YamlServletProfileInitializer.initialize(YamlServletProfileInitializer.java:80) org.cloudfoundry.identity.uaa.impl.config.YamlServletProfileInitializer.initialize(YamlServletProfileInitializer.java:50) org.springframework.web.servlet.FrameworkServlet.applyInitializers(FrameworkServlet.java:764) org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:701) org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:668) org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:716) org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:591) org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:530) org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:170) javax.servlet.GenericServlet.init(GenericServlet.java:158) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1598) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.base/java.lang.Thread.run(Thread.java:834) |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Routing Release 0.197.0
Keshav Sharma <ksharma@...>
Hello CF community, Release Highlights
CF-Bosh Networking
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: CF vs PAS4BOSH vs PAS4K8s vs TKG
Daniel Jones
Ta! Regards, Daniel 'Deejay' Jones - CTO +44 (0)79 8000 9153 EngineerBetter Ltd - More than cloud platform specialists On Wed, 15 Jan 2020 at 15:49, Eric Malm <emalm@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Request for Feedback - Cloudfoundry for Kubernetes Integration artifact from Release Integration team
Saikiran Yerram
Hi CF Community, The Release Integration team has been working on a proposal for supporting the integration needs of projects contributing to Cloudfoundry on Kubernetes. We are looking for feedback from the Cloud Foundry Community on what we have proposed so far. You can find the proposal here. Looking forward to hearing from you. Thanks -- Saikiran Yerram Release Integration team |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: CF vs PAS4BOSH vs PAS4K8s vs TKG
Eric Malm <emalm@...>
Hi, Daniel, In general, "PAS" refers to VMware's commercial distribution of CFAR. "PAS4K8s" is shorthand for the K8s-targeted version currently under pre-GA development, and "PAS4BOSH" is the parallel construction referring specifically to the current BOSH-based product. As with Pivotal/VMware's previous commercialized CFAR products, we intend to build PAS4K8s on top of project development taking place openly in the CFF community. That said, I would encourage commentary on the document to focus on contributions to and development of those CFF projects, and not to any vendor-specific concerns or products. Thanks, Eric On Wed, Jan 15, 2020 at 2:00 AM Daniel Jones <daniel.jones@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: CF vs PAS4BOSH vs PAS4K8s vs TKG
Daniel, As i understand it, TKG is an internal project unrelated to either OSS communities (CF or k8s). Thanks, Dims On Wed, Jan 15, 2020 at 5:00 AM Daniel Jones <daniel.jones@...> wrote:
--
Davanum Srinivas :: https://twitter.com/dims |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
CF vs PAS4BOSH vs PAS4K8s vs TKG
Daniel Jones
Hi all, Would it be possible for someone from VMware MAPBU to clarify a few terms for the benefit of the community?
These questions came up as a result of reading the comments on CF-RFC 030:
It's great that folks are having these discussions in the open, and I wouldn't want to discourage this from happening. I also appreciate that things are probably in flux and being figured out currently. Regards, Daniel 'Deejay' Jones - CTO +44 (0)79 8000 9153 EngineerBetter Ltd - More than cloud platform specialists |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: [CF-RFC] 030: Use Consistent Human Readable Timestamps for CF Component Logs
Daniel Jones
As someone who has had to debug live CF systems for many years, I'm very pleased to see this. Regards, Daniel 'Deejay' Jones - CTO +44 (0)79 8000 9153 EngineerBetter Ltd - More than cloud platform specialists On Mon, 13 Jan 2020 at 16:54, Amelia Downs <adowns@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
FINAL REMINDER: CAB call for January 2020 is next week Wednesday 15th @ 8a Pacific
Michael Maximilien
Hi, all,
Final reminder for the CAB call this Wednesday @ 8a Pacific.
In addition to regular business, we have a great talk planned on KubeCF (see below).
Finally, please take 5 minutes (might be less) to fill out the survey: https://www.surveymonkey.com/
I plan to close it tomorrow around noon Pacific and I will present the results during the CAB.
All info below. Zoom soon,
------ dr.max ibm ☁ silicon valley, ca maximilien.org ----- Original message ----- |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
[CF-RFC] 030: Use Consistent Human Readable Timestamps for CF Component Logs
Amelia Downs
Hi All, Here is a link for a request for comment #030. This is targeted towards teams that provide releases to cf-deployment and to consumers of cf-deployment who read logs. INTENTION We intend to have all component jobs to use, or have the option to use, the same human-readable timestamp format for its logs (RFC3339) so that it’s easier for a human to skim logs to find entries for a given time and so that less toil is required to correlate log entries generated by different sub-components. FEEDBACK Please add comments or suggested edits inside the RFC document for convergent discussion, rather than replying to this email. Please use the Slack channel (#cf-rfc-030) for information conversation about the RFC and related subjects that may or may not result in suggesting an edit to the document. DATES We are planning to start working on this soon. This RFC will be open starting today, and will be closed in two weeks, receiving comments through January 24, 2020. Thanks, Amelia Downs and Josh Collins |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: Uaa.log
Palani Samy <palani160385@...>
Hi Team, Thanks for quick response, here i have already log4j configuration under tomcat lib folder. But still its now working, uaa.log file is creating under /tomcat/logs/uaa.log
On Sat, Jan 11, 2020 at 11:48 AM Filip Hanik <fhanik@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Re: Uaa.log
Filip Hanik
You can control logging in the log4j configuration file. On Fri, Jan 10, 2020 at 20:02 Palani Samy <palani160385@...> wrote:
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
Uaa.log
Palani Samy <palani160385@...>
Hi Team I deployed cloud foudary war file inside the tomcat, and we can able to access foundry home page in browser. Now uaa.log file is available under the /tomcat/logs folder location by default, now the question is i don't want generate uaa.log file in this location, instead of this it should be some where else required. Please find the below logs view structure. -rw-r----- 1 root root 0 Dec 26 06:01 manager.2019-12-26.log Thanks, |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
RFC Kubernetes-idiomatic Cloud Foundry components guidelines
Hi everyone,
As you all know Cloud Foundry is moving to the Kubernetes direction. Several teams have started to work on deploying Cloud Foundry projects on Kubernetes. I have created a document with best practices for applications running in Kubernetes based on my experience working with Kubernetes at CFCR & Eirini. It might become an official Cloud Foundry document. Feel free to leave your comments. https://docs.google.com/document/d/1aVQkmCGmHMuCJS9h1UfO-THcP7ENdqIZe5lYtOzcPPA/edit?ts=5e16cdb3# Later I plan to put it in a GitHub repo in Cloud foundry organisation, so it will be more searchable. Best regards, Oleksandr Slynko |
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
CAB call for January 2020 is next week Wednesday 15th @ 8a Pacific
Michael Maximilien
FYI...
CAB call [0] for January 2020 is next week Wednesday 15th @ 8a Pacific.
In addition to usual business, we have two planned talks / discussions:
1. KubeCF by Vlad Iovanov, Troy Topnik, and SUSE team [1]
2. CAB 2019 Survey Results and Future Direction by me [2]
Finally, if you have not taken the survey, please do so now: https://www.surveymonkey.com/
It will only take you a few minutes (promise :) and this is your chance to shape the CAB call and provide feedback on how to move forward.
Finally, note that I will be at Pivotal SF for this call so if you are in SF join me.
Zoom [0] with you soon.
Best,
------ dr.max ibm ☁ silicon valley, ca maximilien.org |
|||||||||||||||||||||||||||||||
|