Date   

Re: Set maxHttpHeaderSize in tomcat server as a parameter

sajjadgholami2006@...
 

I see what you mean Dan, I know that it doesn't need the whole repo to be forked and it's just tomcat configuration; but that still needs another 'public' repo to host the tomcat customized configuration. Look at it from a corporation's view, they don't want to trust more repositories than the formal open source repos having a support of a community and it's secure since the community has it under control, instead of my own public repo that I can mess it up anytime. That's my whole point, it can be a parameter exposed in the formal code base which everyone has trust on. 


Re: Set maxHttpHeaderSize in tomcat server as a parameter

Daniel Mikusa
 

On Mon, Sep 17, 2018 at 1:28 PM, <sajjadgholami2006@...> wrote:

[Edited Message Follows]

Thanks Lingesh for sharing your repo; right I actually did try it on my own repo as well, but we want it to be formally accepted and be in the original build-pack to use.

Daniel, you're right; but again this needs another repo to be setup, we want to only trust the one formal original CF repo that has the community watching it instead of moving to unreliable sources or to create and maintain our own repo besides this that's why I'm suggesting to make the change in original repo :)

Not sure what you mean. It doesn't require that you fork the buildpack. You just need to host your Tomcat config somewhere. That's cause the buildpack will need to download it, since it's not part of the JBP. The easiest way is to push your config w/the Staticfile buildpack. Then you can use `cf set-env` and tell the JBP to use your external config bundle from your Staticfile app. You could post the config elsewhere too, like S3 or any other HTTP server.

Dan


 



Re: Set maxHttpHeaderSize in tomcat server as a parameter

sajjadgholami2006@...
 

Thanks Lingesh,

We can argue that this is kind of needed for CF services, due to the nature of using JWT token in header; if you want to put something convincing in the pull-request comment ;) 


Re: Set maxHttpHeaderSize in tomcat server as a parameter

Lingesh Mouleeshwaran
 

Alright Thanks, Sajjid, Let me create a pull request for the same. Need to wait for the community concerns as well

On Mon, Sep 17, 2018 at 10:58 PM, <sajjadgholami2006@...> wrote:

[Edited Message Follows]

Thanks Lingesh for sharing your repo; right I actually did try it on my own repo as well, but we want it to be formally accepted and be in the original build-pack to use.

Daniel, you're right; but again this needs another repo to be setup, we want to only trust the one formal original CF repo that has the community watching it instead of moving to unreliable sources or to create and maintain our own repo besides this that's why I'm suggesting to make the change in original repo :)



Re: Set maxHttpHeaderSize in tomcat server as a parameter

sajjadgholami2006@...
 
Edited

Thanks Lingesh for sharing your repo; right I actually did try it on my own repo as well, but we want it to be formally accepted and be in the original build-pack to use.

Daniel, you're right; but again this needs another repo to be setup, we want to only trust the one formal original CF repo that has the community watching it instead of moving to unreliable sources or to create and maintain our own repo besides this that's why I'm suggesting to make the change in original repo :)


Re: Set maxHttpHeaderSize in tomcat server as a parameter

Daniel Mikusa
 

Have you tried the support that's already in the Java buildpack for customizing Tomcat configuration?


This lets you configure all aspects of Tomcat's config, not just the header size.

Dan


On Sat, Sep 15, 2018 at 7:08 AM, Lingesh Mouleeshwaran <lingeshmouleeshwaran@...> wrote:
Hello Sajjad, 

your expected changes are available in my git repo. 
https://github.com/hmlingesh/java-buildpack/commit/5ae18c3fdd873837bcb9427b5659ef52239b30a1  Please have a look I will make a pull request for the same.

Note: by default, Apache community give 8kb as default header size, also I prefer to keep 64 kb as default. 

Regards
Lingesh M

On Fri, Sep 14, 2018 at 6:02 AM, <sajjadgholami2006@...> wrote:
Hi there,

We have a service that gets http requests with big header size, so I was wondering if we can just expose a parameter to set the maximum http header size in tomcat/conf/server.xml to be set by a new option in tomcat.yml file (e.g. "maxHttpHeaderSize" under "tomcat").
I can create a pull-request for this.

I'll appreciate your input ;)

Best,
Sajjad




Re: Set maxHttpHeaderSize in tomcat server as a parameter

Lingesh Mouleeshwaran
 

Hello Sajjad, 

your expected changes are available in my git repo. 
https://github.com/hmlingesh/java-buildpack/commit/5ae18c3fdd873837bcb9427b5659ef52239b30a1  Please have a look I will make a pull request for the same.

Note: by default, Apache community give 8kb as default header size, also I prefer to keep 64 kb as default. 

Regards
Lingesh M

On Fri, Sep 14, 2018 at 6:02 AM, <sajjadgholami2006@...> wrote:
Hi there,

We have a service that gets http requests with big header size, so I was wondering if we can just expose a parameter to set the maximum http header size in tomcat/conf/server.xml to be set by a new option in tomcat.yml file (e.g. "maxHttpHeaderSize" under "tomcat").
I can create a pull-request for this.

I'll appreciate your input ;)

Best,
Sajjad



Re: Cloud Foundry Community Awards

Swarna Podila
 

A friendly reminder, y'all -- the deadline is tomorrow; so please nominate ASAP!  Nominate your peers for a Stealth-Ops or Helping Hands award or an end user story for the Coolest User Story award!
 


Set maxHttpHeaderSize in tomcat server as a parameter

sajjadgholami2006@...
 

Hi there,

We have a service that gets http requests with big header size, so I was wondering if we can just expose a parameter to set the maximum http header size in tomcat/conf/server.xml to be set by a new option in tomcat.yml file (e.g. "maxHttpHeaderSize" under "tomcat").
I can create a pull-request for this.

I'll appreciate your input ;)

Best,
Sajjad


Re: REMINDER: CAB call for September is Wednesday 09/19 @ 8a PST or 11a EST

Michael Maximilien
 

Thank you Ashish. Adding your talk. 

Zoom next week.

Best,

Max 

On Wed, Sep 12, 2018 at 11:55 PM Jain, Ashish <ashish.jain09@...> wrote:

Hi Dr. Max,

We would like to present “Service Fabrik 2.0 – Architecture, Design followed by a demo”.  Presenter would be @Chattopadhyay, Subhankar. We would need a slot of 20-30 minutes.

Best regards,

Ashish

From: <cf-dev@...> on behalf of Michael Maximilien <maxim@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 13 September 2018 at 3:35 AM
To: "cf-dev@..." <cf-dev@...>
Cc: "ureddy@..." <ureddy@...>
Subject: [cf-dev] REMINDER: CAB call for September is Wednesday 09/19 @ 8a PST or 11a EST

 

Hi, all,

 

Quick reminder for the CAB call next Wednesday and announcing one talk:

 

1. “Updates on CF Container Runtime (aka Kubo)” by Urvashi Reddy of Pivotal

2. TBD - if you have a talk please email me ASAP

 

Full agenda and Zoom details in [0]. Zoom soon. Best,

 

------

dr.max

ibm  

silicon valley, ca

maximilien.org

 

[0] https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#heading=h.mewn94q54hla

[1] https://github.com/cloudfoundry-incubator/kubo-release

 

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


Re: REMINDER: CAB call for September is Wednesday 09/19 @ 8a PST or 11a EST

Jain, Ashish
 

Hi Dr. Max,

We would like to present “Service Fabrik 2.0 – Architecture, Design followed by a demo”.  Presenter would be @Chattopadhyay, Subhankar. We would need a slot of 20-30 minutes.

Best regards,

Ashish

From: <cf-dev@...> on behalf of Michael Maximilien <maxim@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 13 September 2018 at 3:35 AM
To: "cf-dev@..." <cf-dev@...>
Cc: "ureddy@..." <ureddy@...>
Subject: [cf-dev] REMINDER: CAB call for September is Wednesday 09/19 @ 8a PST or 11a EST

 

Hi, all,

 

Quick reminder for the CAB call next Wednesday and announcing one talk:

 

1. “Updates on CF Container Runtime (aka Kubo)” by Urvashi Reddy of Pivotal

2. TBD - if you have a talk please email me ASAP

 

Full agenda and Zoom details in [0]. Zoom soon. Best,

 

------

dr.max

ibm  

silicon valley, ca

maximilien.org

 

[0] https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#heading=h.mewn94q54hla

[1] https://github.com/cloudfoundry-incubator/kubo-release

 


REMINDER: CAB call for September is Wednesday 09/19 @ 8a PST or 11a EST

Michael Maximilien
 

Hi, all,


Quick reminder for the CAB call next Wednesday and announcing one talk:

 

1. “Updates on CF Container Runtime (aka Kubo)” by Urvashi Reddy of Pivotal

2. TBD - if you have a talk please email me ASAP

 

Full agenda and Zoom details in [0]. Zoom soon. Best,

 

------

dr.max

ibm ☁ 

silicon valley, ca

maximilien.org

 

[0] https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#heading=h.mewn94q54hla

[1] https://github.com/cloudfoundry-incubator/kubo-release



CF CLI v6.39.0 Released Today

Abby Chau
 

Hey everyone,

The CF CLI team released cf CLI v6.39.0 today; please see release notes for full details. 

Highlights include: 

Refactors (rewrites):

Buildpacks-related commands
  • In order to prepare for the buildpack - stack association feature (see below), the CLI embarked on a rewrite (refactor) of a subset of buildpacks-related (create-buildpack, update-buildpack, and rename-buildpack) commands. User-facing changes include promoting consistency, improving error messages, and enhancing the UX to provide additional information. 
Create-org command
  • We also refactored the `create-org` command to prepare for work on fixing an existing issue with creating orgs whilst logged with client credentials. (see below)

Buildpacks association with stacks feature
  • In order to help with the transition to cflinuxsf3 in April 2019, stack association with buildpack is introduced in this release. Buildpacks can now have the same name, as long as they are associated with a unique stack.  Several buildpacks-related commands (update-buildpack, rename-buildpack, and delete-buildpack now take a `-s` flag to disambiguate buildpacks that have the same name. 

Services-related features 
  • `cf bind-service` and `cf unbind-service` now supports asynchronous operations
  • `cf share-service` and `cf unshare-service` are no longer experimental features

Enhancements and bug fixes
  • `cf auth` now supports the `--origin` option to log into different identity providers
  • `cf start`, `cf restart`, `cf restage` have been updated to use the new v3 `cf app` display
  • fixes an issue with internal domains as your default domain: if you are using internal domains, and the internal domain is the first domain created, the CLI will ignore the internal domain and when you run `cf push` will choose the next non-internal domain to map your app
  • bug fix for a `brew install cf-cli` issue for users using the unreleased master branch of Homebrew
  • bug fix for users logging in with client credentials, now `create-org` properly assigns the user role to the client id

Contributors:  An Yu, Sebastian Vidrio, Anande Gaitonde, Thomas Viehman, Alex Zhao, Abby Chau, Spencer Hawley, Renee Chu, Nick Guerette, Ryan Tang, William Murphy

Special Guests: Buildpacks team (for help with the buildpack-stack association feature), SAPI London team (for pull requests and the async operation work), SAP and UAA Team (for help with the `cf auth` `--origin` work)

Feedback

Please contact us on the #cli channel on Cloud Foundry Slack. Alternatively, respond directly to this email.


Best,

Abby and the CLI team


Re: Help required

Liming Liu <andliu@...>
 

Sorry, minor change,  it’s v6.38.0 not v6.28.0.

 

From: Andy Liu <andliu@...>
Date: Monday, September 10, 2018 at 2:17 PM
To: "cf-dev@..." <cf-dev@...>, Umesh Moudgil <umoudgil08@...>, Scott Sisil <ssisil@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

I did a test the cfdev plugin on the windows 10 pro on windows azure with Standard D4s v3, it works.

 

Details steps:

  1. Create one “Standard D4s v3” windows 10 pro VM on azure.
  2. Enable the hyper-v follow this document https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v
  3. Download& install  cf-cli v6.28.0 => v6.38.0 from https://github.com/cloudfoundry/cli/releases
  4. install the plugin  cf install-plugin cfdev
  5. run the cf dev start.
  6. Login into the cf using : “cf login -a https://api.dev.cfdev.sh --skip-ssl-validation”
  7. Clone one sample application https://github.com/bingosummer/2048
  8. cf push

the app start up correctly.

 

BTW, I also tested the windows server 2016, it does not work for now, that’s due to the hyper-v detection logic does not cover the windows server 2016.

@Scott Sisil PR to add the support for the windows server 2016 sent : https://github.com/cloudfoundry-incubator/cfdev/pull/44

 

 

Thanks,

Andy

 

From: Andy Liu <andliu@...>
Date: Friday, September 7, 2018 at 11:23 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

 

And also I have another way to do the cf development, deploy the cloud foundry on one box:

https://github.com/virtualcloudfoundry/cf-azure-deployment/tree/master/cf-lite

here’s the sample scripts to do the deployment:

terraform apply -var prefix="cf-blabla" -var subscription_id="<your subsciption id>" -var client_id="<your client id>" -var client_secret="<your client secret>" -var tenant_id="<your tenant id>" -var ssh_user_username="cfcf" -var ssh_public_key_filename="./ssh_key.pub" -var auto_deploy_bosh="enabled" -var auto_deploy_cf="enabled" -var location="eastasia"

 

after run this, you would get one dev box, and one box, and one cf box.

You can login into the dev box to do the cf push and so on. (using cfcf and the ssh_key.priv to connect to it)

 

it’s not an official release, but normally I use it for cf feature development.

Feel free to shoot me one email if you have problem using it.

 

Thanks,

Andy

 

From: Andy Liu <andliu@...>
Date: Friday, September 7, 2018 at 11:09 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

Just got message from cf dev team, the cfdev plugin only available on windows 10 and macos for now.

And here’s the tracking issue for the support on Linux box: https://github.com/cloudfoundry-incubator/cfdev/issues/18

 

So maybe you should use a windows 10 or windows server 2016 vm to use the cfdev 😊

I also will try it later. Will post the result on this thread.

 

Thanks

Andy

 

From: <cf-dev@...> on behalf of Umesh Moudgil <umoudgil08@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, September 7, 2018 at 4:47 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Dear Scott,

 

Thanks a lot for prompt reply !!!

I tried running the commands however I didn't get the plugin from CF community.

 

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

 

I have below Azure VM with 16GB RAM.

 


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

 

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.

Please let me know if you have any other troubleshooting steps to follow.

Regards,

Umesh Kumar

 

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:

Hi Umesh,

 

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

 

You can get this version if you uninstall the legacy pcf dev plugin 

 

`cf uninstall-plugin pcfdev`

 

and then install the latest version of cf dev

 

`cf install-plugin cfdev`

 

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

 

-Scott

 

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:

pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.

 

Error! Filename not specified.

Corneil du Plessis

Error! Filename not specified.about.me/corneil

 

 

 

On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:

Dear All,

 

I am trying to setup PCF Dev on my Azure VM.

However when I run "pcf dev start" command, I will below error:

 

 

[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp

 

 

 

Please let me know if you require any further details.
.


Re: Help required

Liming Liu <andliu@...>
 

Hi Umesh,

I did a test the cfdev plugin on the windows 10 pro on windows azure with Standard D4s v3, it works.

 

Details steps:

  1. Create one “Standard D4s v3” windows 10 pro VM on azure.
  2. Enable the hyper-v follow this document https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v
  3. Download& install  cf-cli v6.28.0 from https://github.com/cloudfoundry/cli/releases
  4. install the plugin  cf install-plugin cfdev
  5. run the cf dev start.
  6. Login into the cf using : “cf login -a https://api.dev.cfdev.sh --skip-ssl-validation”
  7. Clone one sample application https://github.com/bingosummer/2048
  8. cf push

the app start up correctly.

 

BTW, I also tested the windows server 2016, it does not work for now, that’s due to the hyper-v detection logic does not cover the windows server 2016.

@Scott Sisil PR to add the support for the windows server 2016 sent : https://github.com/cloudfoundry-incubator/cfdev/pull/44

 

 

Thanks,

Andy

 

From: Andy Liu <andliu@...>
Date: Friday, September 7, 2018 at 11:23 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

 

And also I have another way to do the cf development, deploy the cloud foundry on one box:

https://github.com/virtualcloudfoundry/cf-azure-deployment/tree/master/cf-lite

here’s the sample scripts to do the deployment:

terraform apply -var prefix="cf-blabla" -var subscription_id="<your subsciption id>" -var client_id="<your client id>" -var client_secret="<your client secret>" -var tenant_id="<your tenant id>" -var ssh_user_username="cfcf" -var ssh_public_key_filename="./ssh_key.pub" -var auto_deploy_bosh="enabled" -var auto_deploy_cf="enabled" -var location="eastasia"

 

after run this, you would get one dev box, and one box, and one cf box.

You can login into the dev box to do the cf push and so on. (using cfcf and the ssh_key.priv to connect to it)

 

it’s not an official release, but normally I use it for cf feature development.

Feel free to shoot me one email if you have problem using it.

 

Thanks,

Andy

 

From: Andy Liu <andliu@...>
Date: Friday, September 7, 2018 at 11:09 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

Just got message from cf dev team, the cfdev plugin only available on windows 10 and macos for now.

And here’s the tracking issue for the support on Linux box: https://github.com/cloudfoundry-incubator/cfdev/issues/18

 

So maybe you should use a windows 10 or windows server 2016 vm to use the cfdev 😊

I also will try it later. Will post the result on this thread.

 

Thanks

Andy

 

From: <cf-dev@...> on behalf of Umesh Moudgil <umoudgil08@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, September 7, 2018 at 4:47 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Dear Scott,

 

Thanks a lot for prompt reply !!!

I tried running the commands however I didn't get the plugin from CF community.

 

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

 

I have below Azure VM with 16GB RAM.

 


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

 

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.

Please let me know if you have any other troubleshooting steps to follow.

Regards,

Umesh Kumar

 

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:

Hi Umesh,

 

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

 

You can get this version if you uninstall the legacy pcf dev plugin 

 

`cf uninstall-plugin pcfdev`

 

and then install the latest version of cf dev

 

`cf install-plugin cfdev`

 

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

 

-Scott

 

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:

pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.

 

Error! Filename not specified.

Corneil du Plessis

Error! Filename not specified.about.me/corneil

 

 

 

On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:

Dear All,

 

I am trying to setup PCF Dev on my Azure VM.

However when I run "pcf dev start" command, I will below error:

 

 

[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp

 

 

 

Please let me know if you require any further details.
.


Re: Help required

Liming Liu <andliu@...>
 

Hi Umesh,

 

And also I have another way to do the cf development, deploy the cloud foundry on one box:

https://github.com/virtualcloudfoundry/cf-azure-deployment/tree/master/cf-lite

here’s the sample scripts to do the deployment:

terraform apply -var prefix="cf-blabla" -var subscription_id="<your subsciption id>" -var client_id="<your client id>" -var client_secret="<your client secret>" -var tenant_id="<your tenant id>" -var ssh_user_username="cfcf" -var ssh_public_key_filename="./ssh_key.pub" -var auto_deploy_bosh="enabled" -var auto_deploy_cf="enabled" -var location="eastasia"

 

after run this, you would get one dev box, and one box, and one cf box.

You can login into the dev box to do the cf push and so on. (using cfcf and the ssh_key.priv to connect to it)

 

it’s not an official release, but normally I use it for cf feature development.

Feel free to shoot me one email if you have problem using it.

 

Thanks,

Andy

 

From: Andy Liu <andliu@...>
Date: Friday, September 7, 2018 at 11:09 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Hi Umesh,

Just got message from cf dev team, the cfdev plugin only available on windows 10 and macos for now.

And here’s the tracking issue for the support on Linux box: https://github.com/cloudfoundry-incubator/cfdev/issues/18

 

So maybe you should use a windows 10 or windows server 2016 vm to use the cfdev 😊

I also will try it later. Will post the result on this thread.

 

Thanks

Andy

 

From: <cf-dev@...> on behalf of Umesh Moudgil <umoudgil08@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, September 7, 2018 at 4:47 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Dear Scott,

 

Thanks a lot for prompt reply !!!

I tried running the commands however I didn't get the plugin from CF community.

 

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

 

I have below Azure VM with 16GB RAM.

 


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

 

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.

Please let me know if you have any other troubleshooting steps to follow.

Regards,

Umesh Kumar

 

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:

Hi Umesh,

 

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

 

You can get this version if you uninstall the legacy pcf dev plugin 

 

`cf uninstall-plugin pcfdev`

 

and then install the latest version of cf dev

 

`cf install-plugin cfdev`

 

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

 

-Scott

 

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:

pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.

 

Error! Filename not specified.

Corneil du Plessis

Error! Filename not specified.about.me/corneil

 

 

 

On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:

Dear All,

 

I am trying to setup PCF Dev on my Azure VM.

However when I run "pcf dev start" command, I will below error:

 

 

[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp

 

 

 

Please let me know if you require any further details.
.


Re: Help required

Liming Liu <andliu@...>
 

Hi Umesh,

Just got message from cf dev team, the cfdev plugin only available on windows 10 and macos for now.

And here’s the tracking issue for the support on Linux box: https://github.com/cloudfoundry-incubator/cfdev/issues/18

 

So maybe you should use a windows 10 or windows server 2016 vm to use the cfdev 😊

I also will try it later. Will post the result on this thread.

 

Thanks

Andy

 

From: <cf-dev@...> on behalf of Umesh Moudgil <umoudgil08@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, September 7, 2018 at 4:47 PM
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Help required

 

Dear Scott,

 

Thanks a lot for prompt reply !!!

I tried running the commands however I didn't get the plugin from CF community.

 

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

 

I have below Azure VM with 16GB RAM.

 


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

 

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.

Please let me know if you have any other troubleshooting steps to follow.

Regards,

Umesh Kumar

 

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:

Hi Umesh,

 

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

 

You can get this version if you uninstall the legacy pcf dev plugin 

 

`cf uninstall-plugin pcfdev`

 

and then install the latest version of cf dev

 

`cf install-plugin cfdev`

 

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

 

-Scott

 

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:

pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.

 

Error! Filename not specified.

Corneil du Plessis

Error! Filename not specified.about.me/corneil

 

 

 

On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:

Dear All,

 

I am trying to setup PCF Dev on my Azure VM.

However when I run "pcf dev start" command, I will below error:

 

 

[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp

 

 

 

Please let me know if you require any further details.
.


Re: Help required

Mike Lloyd <klloyd@...>
 

Umesh,

There was an interesting task I helped someone at Microsoft with regarding this same use case. I sent them your thread since they're not on the mailing list and I'll update you if/when he gets back to me on his testing and validation.

Thanks,

Mike.

On Fri, Sep 7, 2018 at 2:47 AM Umesh Moudgil <umoudgil08@...> wrote:
Dear Scott,

Thanks a lot for prompt reply !!!
I tried running the commands however I didn't get the plugin from CF community.

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

I have below Azure VM with 16GB RAM.


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.
Please let me know if you have any other troubleshooting steps to follow.

Regards,
Umesh Kumar

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:
Hi Umesh,

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

You can get this version if you uninstall the legacy pcf dev plugin 

`cf uninstall-plugin pcfdev`

and then install the latest version of cf dev

`cf install-plugin cfdev`

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

-Scott

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:
pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.


On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:
Dear All,

I am trying to setup PCF Dev on my Azure VM.
However when I run "pcf dev start" command, I will below error:


[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp



Please let me know if you require any further details.
.

--
Thanks,

Mike.

(on mobile, apologies for typos!)


Re: Help required

Umesh Moudgil <umoudgil08@...>
 

Dear Scott,

Thanks a lot for prompt reply !!!
I tried running the commands however I didn't get the plugin from CF community.

[root@GBAZUKSL025 ~]# cf uninstall-plugin pcfdev
Uninstalling plugin pcfdev...
OK
Plugin pcfdev 0.30.0 successfully uninstalled.
[root@GBAZUKSL025 ~]# cf install-plugin cfdev
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

I have below Azure VM with 16GB RAM.


[root@GBAZUKSL025 ~]# uname -a
Linux GBAZUKSL025 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

I believe, it will not work till you make some tweaking in PFC Dev as per specific platform.
Please let me know if you have any other troubleshooting steps to follow.

Regards,
Umesh Kumar

On Thu, Sep 6, 2018 at 3:09 PM Scott Sisil <ssisil@...> wrote:
Hi Umesh,

Im the PM for CF Dev - you are using the legacy PCF Dev plugin - please use the latest version the new CF Dev that uses native hypervisors instead of virtual box for virtualization

You can get this version if you uninstall the legacy pcf dev plugin 

`cf uninstall-plugin pcfdev`

and then install the latest version of cf dev

`cf install-plugin cfdev`

As Frederic mentioned earlier in the chain - this tool is intended to run on a local machine, not an Azure VM.  However, in theory it should work on an Azure VM if you configure the VM with 4 cores and a generous amount of RAM (64 GB +) and also configure it to use nested VMs (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) so it can use native hypervisors. 

We have not seen this setup work on our team - but you may be able to get it to work. Let us know.

-Scott

On Thu, Sep 6, 2018 at 8:59 AM Corneil du Plessis <corneil.duplessis@...> wrote:
pcfdev is aimed at running in VirtualBox on your desktop. I don't think it is going to work when trying to install in another VM.


On Thu, 6 Sep 2018 at 15:47, Umesh Moudgil <umoudgil08@...> wrote:
Dear All,

I am trying to setup PCF Dev on my Azure VM.
However when I run "pcf dev start" command, I will below error:


[root@GBAZUKSL025 softwares]# cf dev start
Using existing image.
Allocating 4096 MB out of 16030 MB total system memory (12709 MB free).
Importing VM...
FAILED
Error: failed to import VM: failed to execute 'VBoxManage clonemedium disk /root/.pcfdev/vms/pcfdev-v0.549.0-disk1.vmdk.compressed /root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk': exit status 1: 0%!.(MISSING).10%!.(MISSING).20%!.(MISSING).30%!.(MISSING).40%!.(MISSING).50%!.(MISSING).60%!.(MISSING).70%!.(MISSING).80%!.(MISSING).
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Failed to clone medium
VBoxManage: error: Could not create the clone medium '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/root/.pcfdev/vms/pcfdev-v0.549.0/pcfdev-v0.549.0-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium
VBoxManage: error: Context: "RTEXITCODE handleCloneMedium(HandlerArg*)" at line 990 of file VBoxManageDisk.cpp



Please let me know if you require any further details.
.


REQUEST for REVIEW - Proposed Scope for CF-Deployment 5.0

Josh Collins
 

Hello Fellow Cloud-Foundrians,

I'd like to share and gather feedback on proposed scope of the next major release of cf-deployment.

I've created a Google Doc which describes the high-level changes under proposal.


Anyone with the link above can review and comment.
Please feel free to review and provide feedback in the document as soon as you're able.

We'll be locking the scope the middle of next week (Monday September 17th).

For those interested in following, here's the v5.0 epic in our backlog.
 
Lastly, if you've got breaking changes that you'd like Release Integration to consider in the future please bring them to my and the team's attention:
Thanks very much for reading to the end and Happy Thursday!

-- 
Josh Collins
PM - CF R&D Release Integration
--
Josh Collins
PM - CF R&D Release Integration