Date   

Re: CF space application sharing

John jerrby
 

Hi George,

Thanks!
1. So who "pay" :) when the application in CPU intensive ? if not other app in the cell ...
2. if there any documentation which can shad some additional lights on this topic it it will be great if you can share it...

Thanks a lot and have a nice day,

John


Re: CF space application sharing

George Lestaris
 

Hey John,

As Natalie mentioned before, Diego (the container scheduler) does not know
about CF spaces. Diego does not treat applications in the same space
differently.

Further down the stack, Garden uses CPU cgroups to achieve CPU resource
management. CPU intensive applications can not affect other applications in
the same space, org or cell.

On Tue, Jul 18, 2017 at 9:08 AM, John jerrby <jjerrby(a)gmail.com> wrote:

Ok thanks, but for example does application with CPU intensive tasks can
infulance on other application in the same space or even org, which mean
that other application can be un-responsive during load CPU of application
, am I right ?

let's say that I dont use isolation segment...
--
George Lestaris
GrootFS <https://www.github.com/cloudfoundry/grootfs> Product Manager, Cloud
Foundry <https://www.cloudfoundry.org/>, Pivotal <https://www.pivotal.io/>


Re: CF space application sharing

John jerrby
 

Ok thanks, but for example does application with CPU intensive tasks can infulance on other application in the same space or even org, which mean that other application can be un-responsive during load CPU of application , am I right ?

let's say that I dont use isolation segment...


Mailing lists and links to archived messages

Stanislav German-Evtushenko
 

Hi,

Can anybody reach mailing list server admin and ask them to fix the hostname so that "Archived-At" has lists.cloudfoundry.org instead of localhost and (if possible) to add the same link to the email body?

Best regards,
Stanislav


EOL for Diego-Enabler cf CLI plugin 31 July 2017

Koper, Dies <diesk@...>
 

Hi community,

The cf CLI team plans to discontinue support for the Diego-Enabler cf CLI plugin [1] from the end of this month.
Details below. Please respond if you have any questions or concerns.

Plan:
On 1 Aug 2017, we will remove the plugin from the CF Community CLI plugins site [2] and move its GitHub repository to the cloudfoundry-attic.

Impact:
If you are currently using the Diego-Enabler plugin and have it installed already, there is no impact.
If you intend to use it after this date, you can still install its binaries from the cloudfoundry-attic repo, but note that it is not receiving any updates anymore, not even for security patches.

Background:
This plugin was initially developed and made available to help platform operators and space managers migrate apps from DEA to Diego, one by one or in bulk.
As the DEA architecture reached EOL two months ago, the assumption is that people have completed their migrations. I hope the plugin was useful.

As you may also be aware, Golang 1.9 is expected to be released in mid-August.
According to their Release Policy [3], Golang 1.7 will then no longer receive any updates, not even fixes to critical security problems.

As such, the cf CLI team wants to ensure our releases are built using Golang 1.8 before that day, so we can promptly apply security patches if required.
The cf CLI 6.27.0 and higher are built with Golang 1.8, but the Diego-Enabler plugin is still on Golang 1.7.
We prefer not to release an update to the Diego-Enabler plugin as it would require us to invest in the effort of building a dual DEA and Diego environment to test it.

Best,
Dies Koper
Cloud Foundry Product Manager - CLI

[1] https://github.com/cloudfoundry-incubator/Diego-Enabler
[2] https://plugins.cloudfoundry.org
[3] https://golang.org/doc/devel/release.html#policy


Re: Issue with cf service plan name access and update

Zach Robinson
 

Hello Ketaki,

This is a known issue. When a plan is disabled it becomes "invisible" to users. However, we don't remove existing service instances because this would break existing apps. Ideally a user would then update to a new plan that is supported by their marketplace. However, as you noted, the update doesn't work because the user can no longer see the old plan.

We addressed this in this story https://www.pivotaltracker.com/story/show/137123835 and the fix should be available in cf release 255 or greater.

-Zach


Re: CF space application sharing

Natalie Bennett
 

There's no additional security risk, no.

Diego (the container runtime engine) has no concept of spaces, so long
running processes that happen to be in the same space from the Cloud
Controller's perspective have no special relationship.

- Natalie

On Sun, Jul 16, 2017 at 6:20 AM John jerrby <jjerrby(a)gmail.com> wrote:

HI All,

Any idea ? some reference ?


Re: Request to add fog storage provider InternetArchive

Ronak Banka
 

Nitin, you can always pack your own cf-release and deploy using that one.

Looks like fog change was made in this commit
<https://github.com/cloudfoundry/cloud_controller_ng/commit/e42d61adb9335ac18690456e1ae0997432b4f390>
on cloud controller.


On Mon, Jul 17, 2017 at 3:01 PM, nitin padalia <padalia.nitin(a)gmail.com>
wrote:

Thanks! Raunak,

That's what I was thinking, so seems feature back porting isn't supported.


Re: Request to add fog storage provider InternetArchive

nitin padalia
 

Thanks! Raunak,

That's what I was thinking, so seems feature back porting isn't supported.


Re: cli plugin debugging

Dieu Cao <dcao@...>
 

Suggest asking this question in the #cli channel on the cloudfoundry slack
at cloudfoundry.slack.com

Hope that helps!

Dieu

On Jul 14, 2017 9:47 AM, "David Gu" <sysintelligent(a)gmail.com> wrote:

The error can be reproduced using basic_plugin.go. This time the message
is changed to "dial tcp: lookup tcp/basic-plugin-command: getaddrinfow: The
specified class was not found.". Is there something obvious I'm missing in
the debug configuration file? How do you debug the code in func (c
*BasicPlugin) Run(cliConnection plugin.CliConnection, args []string) ?

{
"version": "0.2.0",
"configurations": [
{
"name": "Launch",
"type": "go",
"request": "launch",
"mode": "debug",
"remotePath": "",
"port": 2345,
"host": "127.0.0.1",
"program": "${fileDirname}",
"env": {},
"args": ["basic-plugin-command"],
"showLog": true
}
]
}


Re: CF Local - Stage and launch CF apps locally in Docker

David Gu
 

Hi Steven, I like your tool. Just a quick question: how do you debug a plugin in cloud foundry?

Thanks
David


Re: CF space application sharing

John jerrby
 

HI All,

Any idea ? some reference ?


Re: Request to add fog storage provider InternetArchive

Ronak Banka
 

Hi Nitin,

You can open a issue here

https://github.com/cloudfoundry/capi-release

But even if you open a issue here and upstream starts working on it , it
will be available in latest release. In that case you have to bump from 251
to the one in which this feature will be added.

Thanks
Ronak

On Sat, Jul 15, 2017 at 6:12 Sachin Garg <satch326(a)gmail.com> wrote:

Can we please get the Internet Archive fog added please?

It is breaking our upgrades beyond cf 251

Thanks
Sachin

Sent from my iPhone

On Jul 14, 2017, at 7:10 AM, nitin padalia <padalia.nitin(a)gmail.com>
wrote:

Hi,
From release CF v252 onwards only few fog providers are supported in
CAPI. Release notes says on request further providers can also be added.

How can I raise the request and get enhancement of same on CF v252?

Thanks!


Re: Any guides on clearing enormous bosh cache data?

PARTHASARATHI KUNDU
 

I am struggling to update a gem. Every time I found my old gem until I change the gem version.

I am using the following command for deployment on bosh-lite

bosh1 create release --force && bosh1 upload release && bosh1 deploy --recreate

I am changing some change gem used for azure blobstore in cloud_controller_ng

I verified the jumpbox alost /var/vcap/store/warden_cpi where basically the gems are stored .

Please let me get rid of the cache so that in deploying the release is forced to update the new file.


Any guides on clearing bosh cache data?

PARTHASARATHI KUNDU
 

I looked at the mail thread
https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/HUJOLHETG6DCGEGONWTZZV64ZXLXFXP7/

I am struggling to update a gem. Every time I found my old gem until I
change the gem version.

I am using the following command for deployment on bosh-lite

bosh1 create release --force && bosh1 upload release && bosh1 deploy
--recreate

I am changing some change gem used for azure blobstore in
cloud_controller_ng

I verified the jumpbox alost /var/vcap/store/warden_cpi where
basically the gems are stored .

Please help me to get rid of the cache so that in deploying the release
is forced to update the new file.

--
Regards Partha


Re: Request to add fog storage provider InternetArchive

Sachin
 

Can we please get the Internet Archive fog added please?

It is breaking our upgrades beyond cf 251

Thanks
Sachin

Sent from my iPhone

On Jul 14, 2017, at 7:10 AM, nitin padalia <padalia.nitin(a)gmail.com> wrote:

Hi,
From release CF v252 onwards only few fog providers are supported in CAPI. Release notes says on request further providers can also be added.

How can I raise the request and get enhancement of same on CF v252?

Thanks!


Re: cli plugin debugging

David Gu
 

The error can be reproduced using basic_plugin.go. This time the message is changed to "dial tcp: lookup tcp/basic-plugin-command: getaddrinfow: The specified class was not found.". Is there something obvious I'm missing in the debug configuration file? How do you debug the code in func (c *BasicPlugin) Run(cliConnection plugin.CliConnection, args []string) ?

{
"version": "0.2.0",
"configurations": [
{
"name": "Launch",
"type": "go",
"request": "launch",
"mode": "debug",
"remotePath": "",
"port": 2345,
"host": "127.0.0.1",
"program": "${fileDirname}",
"env": {},
"args": ["basic-plugin-command"],
"showLog": true
}
]
}


cli plugin debugging

David Gu
 

Hey does anyone know how to debug cli plugin command? I'm using vs code and it always give me 'dial tcp: lookup tcp/localize...: getaddrinfow: The specified class was not found.' error.

My vs debug configuration looks like this:

{
"name": "Launch file",
"type": "go",
"request": "launch",
"mode": "debug",
"program": "${file}",
"args": [
"localize"
],
"showLog": true,
"trace": false
}

I can place a break point in main() without any problem. Just wondering how to debug the code in command. e.g., cf localize (localize is defined in args above).

func main() {
myinit()
fmt.Println("Home dir", home)
plugin.Start(new(LocalCmd))
}

TIA.


Request to add fog storage provider InternetArchive

nitin padalia
 

Hi,
From release CF v252 onwards only few fog providers are supported in CAPI. Release notes says on request further providers can also be added.

How can I raise the request and get enhancement of same on CF v252?

Thanks!


Re: Incubation Proposal: BOSH Backup and Restore

Michael Maximilien
 

Hi, all,

The BBR proposal has gone through a few weeks of review and almost all
comments have been addressed by instigators. They are asking to move for a
vote.

Before we do so, *let me kindly ask the community to add any final comments
and questions by Thursday July 20th noon PDT.*

Assuming no major unresolved comments we will move for a vote next Friday.
So please please take a look at the BBR proposal (links below from
Therese's email).

Best,

Max



On Tue, Jun 13, 2017 at 10:51 AM Therese Stowell <tstowell(a)pivotal.io>
wrote:

Hello,



Pivotal would like to propose to the CF Extensions PMC a new incubation
project , “BOSH Backup and Restore”, focusing on backing up and restoring
BOSH deployments and BOSH directors. This project aims to enable
consistent, reliable backups of CF.



Project name: BOSH Backup and Restore



Project proposal:


https://docs.google.com/document/d/1xQ--FzwoADAepTPjxjcbu0at3jtrp0anvLQE89SViuw/edit#heading=h.7nvp15pyiad8



Project overview presentation:


https://drive.google.com/file/d/0BxHFe1wja8KpaEY1TjU3MWRVZ1k/view?usp=sharing



Video demo:


https://drive.google.com/file/d/0BxHFe1wja8KpZ1ppM0Rxb05qX00/view?usp=sharing



Proposed Project Lead: Therese Stowell (Pivotal)

Development Operating Model: Pairing Model

Technical Approach: See "Examples" in the proposal

Initial team committed: 4 engineers from Pivotal



Please let us know if you have any questions.



Thanks,

Therese Stowell, Pivotal

--
dr.max Sent from my iPhone http://maximilien.org

2341 - 2360 of 9389