Re: CF CLI v6.37.0 Released Today: Variable Substitution
Abby Chau
Hey Carlo, thanks for reaching out. Arrays and hashes are not supported for the Variable Substitution feature. Let us know if you have any additional questions. Thanks. Best, Abby
On Wed, May 30, 2018 at 7:48 PM, Carlo Alberto Ferraris <carloalberto.ferraris@...> wrote:
|
|
Re: CF CLI v6.37.0 Released Today: Variable Substitution
Ronak Banka
Hi Abby, Going forward is there something on roadmap to use ops files for cf CLI too, like we do for Bosh CLI or yaml patch? Use case can be CI/CD pipelines where part of manifest can be injected for different environment. Thanks Ronak
On Thu, 31 May 2018 at 7:37 AM, Abby Chau <achau@...> wrote:
|
|
Re: Deprecation Notice: bosh-hm-forwarder is moving
Mike -
I am not sure, but probably. I'll ping some folks that would know and have them chime in. Adam
|
|
Oratos Incubation Proposal
#loggregator
As many of you know, the Loggregator team has been experimenting with containerizing the Loggregator and Log cache components for use in a K8s context. I posted about these efforts previously[1], and we would like to officially nominate these efforts for incubation within the Runtime PMC (we have also considered extensions - but this would mean twice as many meetings for me ;-) ). We feel that assigning a specific team to this effort is worthwhile to formalize the efforts around product research and design and also want better communicate our intentions to the CF community to gather feedback. Additionally we have identified a first up feature proposal[2] to focus on.
Please review this proposal and FAQ[3] and provide your feedback and comments here or in the document. 1. https://lists.cloudfoundry.org/g/cf-dev/topic/oratos_containerized/18106811?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,18106811 2. https://docs.google.com/document/d/1PjbaImDrSs3qj1oqu46lSChGgJ6ka_N5AuQv0HVkBbI/edit# 3. https://docs.google.com/document/d/1oX4f3VLbTB9AXHOGUA8auGdwK19OVv1dRcKQYc8QsWk/edit#
|
|
Re: Oratos Incubation Proposal
#loggregator
...clickable links.
1. https://lists.cloudfoundry.org/g/cf-dev/topic/oratos_containerized/18106811?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,18106811 2. https://docs.google.com/document/d/1PjbaImDrSs3qj1oqu46lSChGgJ6ka_N5AuQv0HVkBbI/edit# 3. https://docs.google.com/document/d/1oX4f3VLbTB9AXHOGUA8auGdwK19OVv1dRcKQYc8QsWk/edit#
|
|
Re: Oratos Incubation Proposal
#loggregator
Dr Nic Williams
I hope all K8s operators and users are excited for CF logging system!
Question: why did Naomi have to wait 6 months for Cody (to “bosh deploy” CFCR?) :)
From: cf-dev@... <cf-dev@...> on behalf of Adam Hevenor <ahevenor@...>
Sent: Saturday, June 2, 2018 12:06:00 AM To: cf-dev@... Subject: Re: [cf-dev] Oratos Incubation Proposal #loggregator ...clickable links.
1. https://lists.cloudfoundry.org/g/cf-dev/topic/oratos_containerized/18106811?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,18106811 2. https://docs.google.com/document/d/1PjbaImDrSs3qj1oqu46lSChGgJ6ka_N5AuQv0HVkBbI/edit# 3. https://docs.google.com/document/d/1oX4f3VLbTB9AXHOGUA8auGdwK19OVv1dRcKQYc8QsWk/edit#
|
|
Re: Oratos Incubation Proposal
#loggregator
Krannich, Bernd <bernd.krannich@...>
Hi Adam,
Congrats, excited to see this as an incubation proposal, following the Eirini example directly in the Runtime PMC. It is great to see these pieces of technology moving into the core of CF right away.
I left a few smaller cosmetic feedbacks inside the docs you shared.
Regards, Bernd
Bernd Krannich SAP Cloud Platform SAP SE Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
|
|
NOTICE: [php-buildpack] Default PHP version will change from 5.6.x to 7.2.x after 2018-07-02
Scott Sisil
The default version of PHP will be updated to 7.2.x in the first release after 2018-07-02. Per the PHP supported versions website, all support for the 5.6.x series of releases will end on 2018-12-31, roughly four years after the initial release[1]. We are giving users a 30 day notice before we change the default version of PHP to 7.2.x. We will continue to support 5.6.x until the end of the year, but if you are still using PHP 5.6.x, we strongly encourage you to upgrade to a more recent, fully supported version of PHP. [1] http://php.net/supported-versions.php Scott CF Buildpacks PM
|
|
Re: Deprecation Notice: bosh-hm-forwarder is moving
Joseph Rodriguez <jrodriguez@...>
Bosh system metrics can not filter based on deployment (or any other criteria).
We haven't heard about this use case yet but it does sound interesting. If filtering were an option, would you have one deployment of CF with no filter enabled to receive metrics from deployments for non-cf releases (e.g. postgres, redis, et cetera)? In terms of security, there are no deployment-level permissions on the forwarder client: any consumer that successfully connects to the bosh-system-metrics-server has access to the entire stream. Filtering could occur on either end (director or forwarder), but either way, all metrics will be accessible to any deployment. It would be relatively straight-forward to fork and add a deployment filter option to the code (1). 1. This is where the bosh-system-metrics-forwarder receives metrics from the bosh-system-metrics-server: https://github.com/cloudfoundry/bosh-system-metrics-forwarder-release/blob/master/src/github.com/pivotal-cf/bosh-system-metrics-forwarder/pkg/ingress/ingress.go#L182
|
|
Re: Deprecation Notice: bosh-hm-forwarder is moving
Mike Youngstrom
Thanks Joseph, Perhaps just sending everything would be fine as long as the deployment were added as a tag to the metric or something. I'll keep thinking about it, look at the code now that it is available, and create an issue in the release repository if I want to discuss it further before putting together any kind of PR or anything. Thanks, Mike
On Mon, Jun 4, 2018 at 1:42 PM, Joseph Rodriguez <jrodriguez@...> wrote: Bosh system metrics can not filter based on deployment (or any other criteria).
|
|
Re: CF CLI v6.37.0 Released Today: Variable Substitution
Abby Chau
Hi Ronak, We don't currently have that prioritised currently for the CF CLI, but please create a github issue for visibility and future consideration. Thanks, Abby
On Thu, May 31, 2018 at 11:44 PM, Ronak Banka <ronakbanka.cse@...> wrote:
|
|
(action requested) Changing CF App Display
Abby Chau
Hello cf-dev, Actions: Please fill out this short survey [1] to help us understand how you use the cf app app-name command display, and your thoughts on changing the display to default to the V3-app version of the command. The survey will close by end of day, June 15th. Thanks in advance for your time and participation. Best, Abby Chau CF Product Manager - CLI
|
|
Re: Is anyone successfully using IPSec along with Windows Server 2016 (1709)?
Aaron Huber
After further testing with both the 1709 and 1803 versions of Windows Server 2016 it does appear that the WinNAT component being used by the Host Network Service in Windows does not play well with IPSec. We've confirmed with both the open source Cloud Foundry and commercial PCF deployments that traffic to the containers stops working once IPSec is enabled. We've also tested using out-of-the-box installations of both 1709 and 1803 with Docker for Windows and can replicate the same results - traffic to a container over the NAT connection to an exposed port stops working as soon as IPSec is enabled.
If anyone has successfully been able to get this working, please reply with any details. In the mean time we'll be trying to reach out to Microsoft to confirm if this is a bug that can be fixed or if this is working as intended. Aaron
|
|
Database support for UAA
Enrique Cano
I understand that UAA can run against MySQL and Postgres as the backend database, and Oracle was considered in the past but was discarded due to the enterprise licensing model (https://github.com/cloudfoundry/uaa/issues/291).
My question is whether there is a way to develop support for Oracle (or any other database) without having to integrate the code within the UAA repo. In other words, is there a way to externalise the components to support a different database and then make it work alongside UAA's war file? Thanks Enrique
|
|
Re: Proposed BOSH logging interface
Carlo Alberto Ferraris
Jesse,
sorry for the late reply. One thing we normally add to our internal bosh releases - something that is especially useful for the control/drain scripts, but that we do almost for every single process, is the ability to add a timestamp to each line and the PID of the process generating the logs. It would be very neat if the logging interface had an (opt-in?) provision to handle this so that release authors don't have to do it manually.
|
|
Re: Database support for UAA
Filip Hanik
hi Enrique, What became problematic for the UAA was test driven development and continuous integration. Having actual Oracle database instances running in multiple environments. The different databases have three components in UAA 1. The configuration - including some DB specific components to modify the JDBC URL on the fly [1] [2] 2. The migration scripts [3][4] This can definitely be extracted to make it externally configurable to an already compiled version of the UAA. Such functionality does not exist today, it would have to be added through a contribution with accompanying tests.
On Wed, Jun 6, 2018 at 10:01 AM, <enrique.canocarballar@...> wrote: I understand that UAA can run against MySQL and Postgres as the backend database, and Oracle was considered in the past but was discarded due to the enterprise licensing model (https://github.com/
|
|
CF Summit EU: CFP Deadline
Our community has done a phenomenal job of electing the co-chairs for Summit EU in Basel. Please take a look at the co-chairs at https://www.cloudfoundry.org/blog/announcing-2018-cloud-foundry-eu-summit-track-co-chairs-cfp-extension/.
The deadline to submit your speaking proposals is tomorrow, June 8th at 11.59pm US Pacific time. Have a question before submitting your proposal? Post it on #summit channel on slack and/or tag @cfp-help. Submitted your proposal already but not sure how to edit it? Email me directly or send me a slack private message.
|
|
Proposal: Metadata for API resources
Zach Robinson
Hey all,
The CAPI team would like to share a proposal to apply metadata to API resources. Please have a look and add comments for any questions or concerns. https://docs.google.com/document/d/1Ebko_wNu4wWLnAdHg6wmydEMTx_IdwYnb4Ys0mxVmM4/edit?usp=sharing Thanks! -Zach, CAPI Project Lead
|
|
Re: Proposal: Metadata for API resources
David McClure
I read through this yesterday and didn't have any specific comments to leave in-line, but I am happy to see this surface now as I know it's come up in a number of settings in the past. I also thought it was interesting to see the open, implicit acknowledgement of seeking inspiration of convergence with the analogous feature set in Kubernetes. This feels like a healthy thing to see continuing to happen in this community, but I'm also curious to know whether there's any more to it that is worth sharing in this particular case. Aside from meeting user expectations because they may end up using similar features on either CF or Kubernetes, is there any reason or background in the thinking around aiming to have these APIs or experiences be more or less similar to each other?
On Thu, Jun 7, 2018 at 10:46 AM Zach Robinson <zrobinson@...> wrote: Hey all,
|
|
Re: CF Summit EU: CFP Deadline
Sara Elshahawy
Hi Swarna, Thanks for the email. Actually I was wondering how to edit my proposal after submitting it, I would like to add few more points. Hope you can help! Sara Sr. TPM | Cloud Foundry | Dublin
On Thu, Jun 7, 2018 at 6:51 PM Swarna Podila <spodila@...> wrote: Our community has done a phenomenal job of electing the co-chairs for Summit EU in Basel. Please take a look at the co-chairs at https://www.cloudfoundry.org/blog/announcing-2018-cloud-foundry-eu-summit-track-co-chairs-cfp-extension/.
|
|