|
Oratos: Containerized Experiments with Loggregator + Log Cache
#loggregator
ορατός • (oratós) m (feminine ορατή, neuter ορατό)
As a follow up to Wednesday's special interest group call about K8s and Cloud Foundry I wanted to share a backlog[1] and slack channel[2] and encourage everyone to get involved in the discussion around experiments to use Loggregator and Log Cache release[3] with Cloud Foundry Container runtime. Some of this has already been tinkered with and we have a working demo that uses fluentd to ingress into Loggregator in a K8's Pod[4]. We are looking to further experiments with the goal of demoing a consistent telemetry experience across CFAR and CFCR. I have proposed similar things in the past[5] so feel free to read more about these ideas, but keep in mind the landscape has changed since that document was written and I'd encourage you to get involved by joining our slack channel if these topics interest you. We'll be posting about progress, and contributing to the conversation about in the monthly community calls as well. 1. https://www.pivotaltracker.com/n/projects/2167209 2. https://cloudfoundry.slack.com/messages/CAD9NBZTK 3. https://github.com/cloudfoundry/log-cache-release 4. https://github.com/cloudfoundry-incubator/loggregator-k8s-deployment 5. https://drive.google.com/open?id=1ISmtxrLW8svIRwzw0je4OH1cOEY3va3E-z45_pfgKBM
|
|
|
|
Re: Call for Demos - CF / K8S Integration SIG Meeting
Chip - we'd love to demo the experiments with k8s loggregator deployment and log-cache integrations and how that can create a consistent observability experience across both CFAR and CFCR.
|
|
|
|
Re: Call for Demos - CF / K8S Integration SIG Meeting
Julz Friedman
Happy to demo Eirini (the artist formerly known as Cube), too. Thanks!
On Fri, 27 Apr 2018 at 17:54 Michael Maximilien <mmaximilien@...> wrote:
|
|
|
|
Re: Call for Demos - CF / K8S Integration SIG Meeting
Michael Maximilien
Hi, DK and I will be presenting BOSH Kube CPI at CF-Day next week* Tuesday May 1st in Copenhagen. We will also (on that day) make all the code public and ready for all to try and provide feedback. We have tested on IBM Cloud, GKE, AKS, and MiniKube. Likely any and all recent Kube clusters should work fine. It's a cool live demo from pretty much scratch deploying and managing non-trivial workloads (CF included). So we need about 20 to 30 minutes with brief slides and QAs. We'd be happy to demo this at next SIG and CAB calls. Best, max * I will be there live in Cope but DK will be in spirit :) or Zoom, if I can shame him some more for not taking the 24 hours round trip flights.
On Thu, Apr 26, 2018 at 8:53 AM, Chip Childers <cchilders@...> wrote:
--
|
|
|
|
Summit EU: CFP and Co-Chair Nominations
Folks,
Wanted to highlight a few highlights and a deadline coming up for our EU Summit:
Please don't hesitate to ping me on email or slack if you have any questions. --Swarna.
|
|
|
|
Call for Demos - CF / K8S Integration SIG Meeting
Chip Childers <cchilders@...>
During yesterday's CF/K8S SIG meeting, several speakers proposed demo'ing their various efforts during a future call. -- I'd like to formally request replies from anyone interested in giving a demo, and we'll work out an agenda for the next (and future) SIG calls based on responses. So far, I have an offer from SAP for Dobromir Zahariev to demo the work around service catalog sync between CFAR and K8S. Anyone else willing? -chip Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Re: Understanding hard CPU limits
Stanislav German-Evtushenko
Hi Eric,
The current logic looks a little bit too complicated. Wouldn't it be simpler if it was not using CPU shares in calculation and just using memory share (container memory / cell memory) for this? In that case we could just specify CPU FACTOR which is easy to understand. For example: # Maximum CPU time is proportional to Memory share # In this example scaling factor is 2 CPU_MAX_FACTOR = 2 CELL_CPU = 8 CELL_MEMORY = 16 * 1024^3 # 16 GiB CONTAINER_MEMORY = 4 * 1024^3 # 4 GiB PERIOD = 100000 # 100 ms (default) QUOTA_RATIO = ( CONTAINER_MEMORY / CELL_MEMORY ) * CELL_CPU * CPU_MAX_FACTOR = 1/4 * 8 * 2 = 4 # i.e. 4 CPUs time at max QUOTA = QUOTA_RATIO * PERIOD = 400000 # in ms PERIOD could also be made configurable so that we could adjust this to our latency requirements if needed. Best regards, Stanislav
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Jain, Ashish <ashish.jain09@...>
Hi Amulya,
We did a demo on the similar use during the CF summit at Boston https://cfna18.sched.com/event/DdZu/service-fabrik-20-a-more-pluggable-and-flexible-backing-service-shashank-mohan-jain-ashish-jain-sap?iframe=no&w=&sidebar=yes&bg=no . We can definitely connect and discuss more on this.
Best regards, Ashish
From: <cf-dev@...> on behalf of Amulya Sharma <amulya.sharma@...>
Thanks for informational Chip
I am actively working on integrating these two run times To begin with we are using k8 to run our persisted workloads for stateless apps in cloudfoundry persisted workloads will be created by service broker in cloud foundry
Wondering is anyone else working on same love to connect and share what we have so far
Thanks Amulya
On Wed, Apr 25, 2018 at 11:22 AM Chip Childers <cchilders@...>
wrote:
--
Thanks and Regards Amulya Sharma
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Chip Childers <cchilders@...>
Lots of folks are working on different aspects. Some rough notes from today's call are here: https://docs.google.com/document/d/1fUssMxFjII01viJcVOXu3RToENW_S11oI96rvnRdlkY/edit Feel free to dive into the URL's noted and / or the more formal project team backlogs.
On Wed, Apr 25, 2018 at 3:26 PM Amulya Sharma <amulya.sharma@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Amulya Sharma <amulya.sharma@...>
Thanks for informational Chip I am actively working on integrating these two run times To begin with we are using k8 to run our persisted workloads for stateless apps in cloudfoundry persisted workloads will be created by service broker in cloud foundry Wondering is anyone else working on same love to connect and share what we have so far Thanks Amulya
On Wed, Apr 25, 2018 at 11:22 AM Chip Childers <cchilders@...> wrote:
--
Thanks and Regards Amulya Sharma
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Chip Childers <cchilders@...>
This is a Cloud Foundry community activity (not a k8s SIG in the formal sense), but it may be interesting to find a way to bridge over to the k8s community somehow... That said, it's open to anyone to join! It's listed on the Cloud Foundry community public calendar for future reference: https://calendar.google.com/calendar/embed?src=cloudfoundry.org_oedb0ilotg5udspdlv32a5vc78%40group.calendar.google.com&ctz=America%2FNew_York We'll also remind people via this list.
On Wed, Apr 25, 2018 at 2:19 PM Amulya Sharma <amulya.sharma@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Amulya Sharma <amulya.sharma@...>
thanks for setting this up .... how can I join this SIG is it on kubernates SIG github page Thanks and Regards Amulya Sharma
On Wed, Apr 25, 2018 at 10:04 AM Chip Childers <cchilders@...> wrote:
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Chip Childers <cchilders@...>
Hey all, First call happened just now, and hopefully it was useful for those that attended. There is obviously TONS of activity happening around the community on this topic. I attempted to keep notes about what each speaker shared, but would welcome edits to make ti more accurate. As I said on the call, open to feedback on format, frequency, etc... Thanks!
On Mon, Apr 23, 2018 at 11:22 AM Chip Childers <cchilders@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Re: CF Crypto operations as a Service
cfcrypto <cfcrypto@...>
Hi sanjeevkumar761,
Thank you for your prompt and valuable response to my question. Currently I'm researching the CF and I should compare the CF and Kubernetes functionalities as well. So once I'm done with that part I can think about the efforts, implementation and future collaborations. Containerized Service Broker is exactly what I need for the implementation. Best Regards -- Sent from: http://cf-dev.70369.x6.nabble.com/
|
|
|
|
Re: Proposal: Pluggable scheduling with Kubernetes implementation for Cloud Foundry ("Project Eirini")
Chip Childers <cchilders@...>
It's really great to see this proposal moving forward. Experimenting like this, to explore possibilities and new combinations of tech, is exactly what the CF community is about. Thanks for continuing to push this forward.
On Wed, Apr 25, 2018 at 8:35 AM Julz Friedman <julz.friedman@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Proposal: Pluggable scheduling with Kubernetes implementation for Cloud Foundry ("Project Eirini")
Julz Friedman
Hi cf-dev! After quite a successful presentation of our CF and K8s integration work at cf summit, we are now excited to get started on it “for real”! There’s a long proposal document linked below [0] which spends a lot of time (for obvious reasons!) on motivation, goals and mitigations (with many many thanks in particular to Eric Malm, Shannon Coen, Dieu Cao, and Zack Robinson for feedback so far which has improved it immensely), but the tl;dr is we’re proposing an incubation project to add the ability (alongside Diego) to use Kubernetes as a scheduler, for those folks who already have Kubernetes available (e.g. via CFCR) and who want to gain operational efficiencies by only managing one scheduler. Since it turns out that our previous name, “Cube”, is a little difficult to discern from “Kube” when said out loud (who knew?), we’re also renaming the project to “Eirini”, which is greek for “Peace” and comes from the same root as the greek word for “Connection” - seems quite appropriate! Additionally, for 80s music fans, this means when it goes wrong you will be able to shout “Come on Eirini” at the computer. We intend to propose the project for incubation in the runtime-pmc meeting on May 1st, so we’re very happy indeed to receive feedback both here and on the document! [0]: https://docs.google.com/document/d/1qs6UQQDWMkfOpY19XqS3CfvI00jCns876TjplJ6E95s/edit?usp=sharing Looking forward to all your feedback, Simon & Dr.Julz
|
|
|
|
Re: After customization of uaa login.html page login functionality is not working
#cf
abdul.q@...
thank you for the reply,
can it be possible that create account and forgot password should not be displayed totally on my login page? thank you.
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Chris Clark
I added a link to the Community Event Calendar towards the top of the cloudfoundry.org Events page. We'll all add the CF and K8s Integrations SIG meeting as a recurring event or our the calendar below.
On Tue, Apr 24, 2018 at 2:11 PM, Chip Childers <cchilders@...> wrote:
--
Chris Clark Technical Operations Manager Cloud Foundry Foundation
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Chip Childers <cchilders@...>
Nope, but it should be for sure. :) We'll get it added.
On Tue, Apr 24, 2018 at 2:10 PM Eric Malm <emalm@...> wrote:
--
Chip Childers CTO, Cloud Foundry Foundation 1.267.250.0815
|
|
|
|
Re: CF / K8S (and related projects) Special Interest Group Call
Eric Malm <emalm@...>
Thanks for the calendar link, Chip! Is that link on the cloudfoundry.org site anywhere? I couldn't find it after spending a few minutes searching for it on the pages where I would expect to find it (such as the main page, Community, Events, and About Us). Thanks again, Eric
On Tue, Apr 24, 2018 at 11:02 AM, Amit Kumar Gupta <agupta@...> wrote:
|
|
|