CAB call for November 2019 is next week Wednesday 20th @ 8a Pacific - LAST CAB call for 2019!
Michael Maximilien
FYI...
CAB call for November 2019 is next week Wednesday 20th @ 8a Pacific.
If you have a talk, a project, or would like to present something, please contact me ASAP.
Reply here (to me) or ping me on Slack. Best,
------ dr.max ibm ☁ silicon valley, ca maximilien.org
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Michael Maximilien
Congratulations to the whole Eirini team! Julz and team, interested in presenting at the next CAB call next week Wednesday @ 8a Pacific time? Perhaps an overview of 1.0, brief demo(s) of features. Also any roadmap for next release will be interesting as well as how you all plan to sync both with CF and k8s releases? Let me know soon. Feel free to slack if you want to discuss. Best, Max
On Tue, Nov 12, 2019 at 10:33 PM Ian Huston <ihuston@...> wrote:
--
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Ian Huston <ihuston@...>
Congratulations Eirini team, and everyone involved!
On Tue, 12 Nov 2019 at 11:59, Krannich, Bernd <bernd.krannich@...> wrote:
--
Ian Huston Director of Engineering Pivotal Dublin
|
||||||||||||
|
||||||||||||
Istio integration for Cloud Foundry on Kubernetes
Gabriel Rosenhouse <grosenhouse@...>
Hi all, The Cloud Foundry Networking team is planning to integrate Istio into our CF-on-K8s efforts. In particular, we're planning to automatically inject Envoy proxy sidecars into all application workloads, and to automatically inject sidecars into Kubernetes-hosted system components such as Cloud Controller and UAA. We have a bit more detail (and diagrams) in this document [0]. Please leave feedback and questions as comments there, or reply to this email. Regards, Gabe
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Eric Malm <emalm@...>
Congratulations to Julz and all the past and present contributors on the Eirini team! That's great news, and it's exciting to hear about the forward progress! Best, Eric
On Tue, Nov 12, 2019 at 7:44 AM Nima <nkavian@...> wrote:
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Nima
This is great news, way to go Eirinauts!
On Nov 12, 2019, at 7:14 AM, Simon D Moser <smoser@...> wrote:
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Simon D Moser
Big shoutout to the
awesome Eirini team and contributing companies. Y'all rock!
From: "Krannich, Bernd" <bernd.krannich@...> To: "cf-dev@..." <cf-dev@...> Date: 12/11/2019 12:58 Subject: [EXTERNAL] Re: [cf-dev] Eirini is 1.0! Sent by: cf-dev@... Hi Eirini team,
Great news – congratulations and thank you very much to all the individuals and companies contributing!
Cheers, Bernd
From:
<cf-dev@...> on behalf of Julz Friedman <julz.friedman@...>
Hi cloud foundries, We’re happy to announce the Eirini team has hit our internal “1.0” milestone and shipped a release marked as 1.0[0]!.
This means we believe the core Eirini component is stable and ready to use (although there are some optional features - such as the new v3 API, tasks and container-to-container networking support - that are only available in the Diego backend, for now).
This work would not have been possible without contributions from across the Cloud Foundry community, but especially from IBM, Pivotal, SAP, SUSE and Google.
# What is Eirini?
Eirini brings the simplicity of `cf push` to Kubernetes. Kubernetes has quickly become the de-facto standard container scheduler across the cloud community, and now - via Eirini - Cloud Foundry users can take advantage of this powerful technology to put their containers on servers. Even better (in my opinion anyway), Kubernetes users can now try out the Cloud Foundry developer experience in a native, easy and interoperable way -- which means: less YML, more code.
# How can I try Eirini / Cloud Foundry on Kubernetes?
Eirini-based Cloud Foundry is already available commercially as a technology preview from IBM Cloud, SUSE and Pivotal. You can also deploy your own Eirini from the open-source bits by following the instructions in the eirini-release repository[1] (these are still a little harder than we'd like them to be, but there's lots of work going on in the wider eiriniverse to make them better!) - and let us know how you get on (see next paragraph!).
# Talking to us:
We’re available in Cloud Foundry slack in the #eirini-dev and #cf-for-k8s channels, and there’s a cross-community meeting[2] discussing CF on Kubernetes and the broader “Eiriniverse” every second Tuesday which you can find in the CF Community Calendar[3] - everyone is very very welcome to join and help steer the direction of the projects.
Thanks y’all- The Eirini Team,
[0]: https://github.com/cloudfoundry-incubator/eirini-release/releases/tag/v1.0.0 [1]: https://github.com/cloudfoundry-incubator/eirini-release [3]: https://www.cloudfoundry.org/community-calendar/
|
||||||||||||
|
||||||||||||
Re: Eirini is 1.0!
Krannich, Bernd
Hi Eirini team,
Great news – congratulations and thank you very much to all the individuals and companies contributing!
Cheers, Bernd
From: <cf-dev@...> on behalf of Julz Friedman <julz.friedman@...>
Hi cloud foundries,
We’re happy to announce the Eirini team has hit our internal “1.0” milestone and shipped a release marked as 1.0 [0]!.
This means we believe the core Eirini component is stable and ready to use (although there are some optional features - such as the new v3 API, tasks and container-to-container networking support - that are only available in the Diego backend, for now).
This work would not have been possible without contributions from across the Cloud Foundry community, but especially from IBM, Pivotal, SAP, SUSE and Google.
# What is Eirini?
Eirini brings the simplicity of `cf push` to Kubernetes. Kubernetes has quickly become the de-facto standard container scheduler across the cloud community, and now - via Eirini - Cloud Foundry users can take advantage of this powerful technology to put their containers on servers. Even better (in my opinion anyway), Kubernetes users can now try out the Cloud Foundry developer experience in a native, easy and interoperable way -- which means: less YML, more code.
# How can I try Eirini / Cloud Foundry on Kubernetes?
Eirini-based Cloud Foundry is already available commercially as a technology preview from IBM Cloud, SUSE and Pivotal. You can also deploy your own Eirini from the open-source bits by following the instructions in the eirini-release repository [1] (these are still a little harder than we'd like them to be, but there's lots of work going on in the wider eiriniverse to make them better!) - and let us know how you get on (see next paragraph!).
# Talking to us:
We’re available in Cloud Foundry slack in the #eirini-dev and #cf-for-k8s channels, and there’s a cross-community meeting [2] discussing CF on Kubernetes and the broader “Eiriniverse” every second Tuesday which you can find in the CF Community Calendar [3] - everyone is very very welcome to join and help steer the direction of the projects.
Thanks y’all- The Eirini Team,
[0]: https://github.com/cloudfoundry-incubator/eirini-release/releases/tag/v1.0.0 [1]: https://github.com/cloudfoundry-incubator/eirini-release
|
||||||||||||
|
||||||||||||
Eirini is 1.0!
Julz Friedman
Hi cloud foundries, We’re happy to announce the Eirini team has hit our internal “1.0” milestone and shipped a release marked as 1.0 [0]!. This means we believe the core Eirini component is stable and ready to use (although there are some optional features - such as the new v3 API, tasks and container-to-container networking support - that are only available in the Diego backend, for now). This work would not have been possible without contributions from across the Cloud Foundry community, but especially from IBM, Pivotal, SAP, SUSE and Google. # What is Eirini? Eirini brings the simplicity of `cf push` to Kubernetes. Kubernetes has quickly become the de-facto standard container scheduler across the cloud community, and now - via Eirini - Cloud Foundry users can take advantage of this powerful technology to put their containers on servers. Even better (in my opinion anyway), Kubernetes users can now try out the Cloud Foundry developer experience in a native, easy and interoperable way -- which means: less YML, more code. # How can I try Eirini / Cloud Foundry on Kubernetes? Eirini-based Cloud Foundry is already available commercially as a technology preview from IBM Cloud, SUSE and Pivotal. You can also deploy your own Eirini from the open-source bits by following the instructions in the eirini-release repository [1] (these are still a little harder than we'd like them to be, but there's lots of work going on in the wider eiriniverse to make them better!) - and let us know how you get on (see next paragraph!). # Talking to us: We’re available in Cloud Foundry slack in the #eirini-dev and #cf-for-k8s channels, and there’s a cross-community meeting [2] discussing CF on Kubernetes and the broader “Eiriniverse” every second Tuesday which you can find in the CF Community Calendar [3] - everyone is very very welcome to join and help steer the direction of the projects. Thanks y’all- The Eirini Team, [0]: https://github.com/cloudfoundry-incubator/eirini-release/releases/tag/v1.0.0 [1]: https://github.com/cloudfoundry-incubator/eirini-release [3]: https://www.cloudfoundry.org/community-calendar/
|
||||||||||||
|
||||||||||||
cf CLI v7.0.0-beta.27 is available
Abby Chau
Hi everyone, We've released cf7 CLI beta.27! Here are some highlights:
See release notes for more information including new commands now backed by the v3 API. Review our roadmap for information on what's coming next, and to provide feedback for items under consideration. If you are using the cf CLI v7 release, we would love to hear from you. Please respond via this email or find us in Cloud Foundry Slack #cli or #v3-acceleration-team. Best, Abby, the cf CLI and v3 Acceleration teams
|
||||||||||||
|
||||||||||||
The Cloud Foundry Volume Services team wants your feedback.
Hjortshoj, Julian <Julian.Hjortshoj@...>
Hi everyone,
Apologies for the bulk email. If you don't use volume services in CF, and have no plans to use them, you can discard this message.
If you are still reading however, then we'd really like to hear from you to better prioritize our future work.
We've created a customer questionnaire which we are really hoping some customers will fill out. We have made all the questions on the form optional so that you can tell us as little or as much as you want. You can find the feedback form here:
https://forms.gle/64YsHNvCyr2URGKY9
Thanks much,
-Julian & the Volume Services team.
|
||||||||||||
|
||||||||||||
cf CLI 6.47.2 released today
Abby Chau
Hi everyone, The cf CLI team released v6.47.2 today which includes a bump to Golang 1.12.12 to address Golang-related security concerns. Please reach out if you have any questions. Thanks. Best, Abby and the cf CLI team
|
||||||||||||
|
||||||||||||
Remove support for TLS 1.0 and 1.1 in the CF CLI
Steve Taylor
Hi CF CLI community, The minimum version of TLS supported by the current CF CLI is TLS 1.0. Does anyone object to us bumping the minimum version of TLS to 1.2 in a near-future minor release of the CLI? Regards, The CF CLI Team
|
||||||||||||
|
||||||||||||
CF CLI: Dropping Support for Legacy Operating Systems related to GoLang 1.13
#cf
Eric Promislow
Greetings CF CLI community, The current binary releases of the CF CLI are built using Go 1.12. We plan to start using Go 1.13 soon. The GoLang 1.12 release included the following warning: Go 1.12 is the last release that will run on macOS 10.10 Yosemite. Go 1.13 will require macOS 10.11 El Capitan or later. And the GoLang 1.13 release included the following warning: The Windows version specified by internally-linked Windows binaries is now Windows 7 rather than NT 4.0. As a result of these two announcements, we plan the following binary support matrix for an upcoming release of the CF CLI binaries built with Go 1.13:
Please reach out if you have any questions or concerns. Regards, The CF CLI team
|
||||||||||||
|
||||||||||||
Re: CF Application Runtime PMC: Loggregator Project Lead Call for Nominations
Eric Malm <emalm@...>
Hi, everyone, Pivotal is nominating Jesse Weaver for the Loggregator Project Lead in the Application Runtime PMC. Jesse is a product manager at Pivotal working on the Loggregator team, and previously was an engineer working on Cloud Foundry in Denver. His previous work includes full-stack engineering and design for web applications, and engineering and product design for open-source projects. Please send any other nominations directly to me or in reply to this message no later than 11:59 PM PDT on Monday, Nov 11, 2019. Thanks, Eric Malm
On Tue, Oct 29, 2019 at 11:05 AM Eric Malm <emalm@...> wrote:
|
||||||||||||
|
||||||||||||
CF Application Runtime PMC: Loggregator Project Lead Call for Nominations
Eric Malm <emalm@...>
Hi, everyone, Allen Duet, the lead for the Loggregator project within the Application Runtime PMC, is stepping down from the project, as he has recently left Pivotal. We thank him for his service. The Loggregator team, located in Denver, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PDT on Monday, Nov 11, 2019. Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know. Thanks, Eric Malm, CF Application Runtime PMC Lead
|
||||||||||||
|
||||||||||||
Automating minor stemcell releases
Saikiran Yerram
TLDR We will now automatically release minor versions of CF Deployment for every new minor stemcell version bump. Why we are doing this CF users want to upgrade their foundation as soon as bosh stemcell versions are available in CF-deployment. However, the bosh stemcell bumps are packaged with unrelated changes and scheduled as part of regular release cycles. If there are any new stemcell updates (including CVE fixes), users will have to wait for the next release even if it might include other component updates. If any change results in a build failure at any stage in the pipeline, a stemcell update might be blocked until unrelated changes are fixed. Furthermore, a minor stemcell bump can be packaged with a major version cf-deployment release with component related breaking changes. This forces cf users to either perform a major upgrade just to get the latest stemcell version or run the risk of falling behind. Solution The Release Integration team will release a cf-deployment minor release with just one single change - minor stemcell bump - as soon as a new stemcell is available, so cf users can stay up to date with the latest stemcell (and not worry about other unrelated changes). Version 12.3.0 is one such example.
|
||||||||||||
|
||||||||||||
Re: cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi everyone, cf CLI 6.47.1 now has support for Windows. In summary, cf CLI 6.47.1 supports all previous supported operating systems, and it fixes a regression for cf login. Thanks everyone for your patience, and let us know if you have any feedback. Best, Abby and the CLI and VAT
On Tue, Oct 22, 2019 at 12:22 PM Abby Chau <achau@...> wrote:
|
||||||||||||
|
||||||||||||
Re: What happened to Maven Central releases
#uaa
Dan Beneke
Hi Mike - The project's primary intent is to publish new releases on Github within cloudfoundry/uaa. I recognize that there was a time that they were being published to Maven, and that publish has been interrupted. Historically, the Maven artifacts were hosted by the Spring/Pivotal organization, meaning publish access was restricted to members of that org. There is UAA community intent to move the hosting location to a CFF (or other shared) site, so that contributing project members outside of Spring/Pivotal could be provided publish access to the new location. All of this is to say that Maven artifact publish may continue, but not until a new hosting location is identified. Dan
On Tue, Oct 22, 2019 at 5:47 AM Mike Roda <m2roda@...> wrote: Thanks but I need the jars, specifically the cloudfoundry-identity-server and cloudfoundry-identity-model projects.
|
||||||||||||
|
||||||||||||
Re: cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi everyone, A quick update: we are still working on Windows Support. In the meantime, the cf CLI eng team applied a temporary fix for the Windows issue: links for the latest Windows version temporarily redirects to use cf CLI 6.46.1 which is the last known working version. The Linux and OSX installers/binaries are still pointing at cf CLI 6.47.1, which fixes the aforementioned regression for login. Once we have the new Windows cert working, we will release Windows support which will be on par with cf CLI 6.47.1. Please reach out if you have any questions or concerns, thanks. Abby
On Mon, Oct 21, 2019 at 5:25 PM Abby Chau <achau@...> wrote:
|
||||||||||||
|