Re: Proposal for Incubation in the Extensions PMC: CF Dev

Dr Nic Williams <drnicwilliams@...>

Wow, a 3G ram footprint would be incredible goal.

From: cf-dev@... <cf-dev@...> on behalf of Scott Sisil <ssisil@...>
Sent: Monday, April 16, 2018 8:03:21 AM
To: Guillaume Berche
Cc: cf-dev; Casey, Emily (Pivotal); Chip Childers
Subject: Re: [cf-dev] Proposal for Incubation in the Extensions PMC: CF Dev
Hi All,

We wanted to give everyone a quick update on progress we have made with CF Dev:
  •  We fixed the privileged port access bug (Issue #11). Now all users should be able to login to CF Dev using the CF CLI.
  •  We received a lot of feedback on the memory / disk space footprint. The team is actively working on shrinking both of these with a goal that we can get to a memory footprint of less than 3 GB
  •  We have added telemetry to start collecting anonymous usage analytics. The raw analytics data will be available via a public Amazon S3 bucket. We also plan to publish a quarterly analytics report to the projects Github page.

Just a quick reminder that Stephen Levine will be presenting a demo of CF Dev at the Thursday keynote @ CF Summit this week.

Finally, we would appreciate any additional feedback to the project - please submit feedback in the proposal itself or respond directly to this email thread.


On Tue, Feb 27, 2018 at 4:32 AM, Guillaume Berche <bercheg@...> wrote:
Thanks Stephen.


On Tue, Feb 27, 2018 at 12:09 AM, Stephen Levine <slevine@...> wrote:
Hi Guillaume,

Apologies for the google doc permissions issue -- should be fixed now :)

We don't have a public tracker or design docs yet, but we plan to have both soon.


On Mon, Feb 26, 2018 at 5:56 PM, Guillaume Berche <bercheg@...> wrote:
Thanks Stephen for opensourcing CF Dev through this proposal, seems great!

I wonder whether there is a public backlog for the project ? I see some commits such as [1] apparently refer to pivotal tracker story ids, but the project does not yet seem public [2].
May be the tracker refers to some design doc that I could not yet find in the source, if not this might be useful to the community.

Thanks in advance,


ps: the proposal google doc permissions seem to be set to read-only and not accept comments or suggestions.


On Mon, Feb 26, 2018 at 5:28 PM, Stephen Levine <slevine@...> wrote:
PCF Dev is already often (mistakenly) referred to as CF Dev, as `cf dev [command]` is the CLI invocation. We figured that calling this product CF Dev would give both products consistent names that make sense.

We considered the conflict with the list alias, but given that a mailing list alias and a software tool are significantly different things, and that CF Dev is already commonly used to refer to PCF Dev anyways, we decided not to change it.

On Mon, Feb 26, 2018 at 11:04 AM, Michael Maximilien <maxim@...> wrote:
We’ll definitely have to find better names as cf-dev is also this mailing list. Too many polymorphic usage of this one moniker. Let’s be creative!

ibm ☁ 
silicon valley, ca

ibm ☁ 
silicon valley, ca

On Feb 23, 2018, at 2:40 PM, Hjortshoj, Julian <Julian.Hjortshoj@...> wrote:

Is it too late to change the name?  I suspect that folks might not instantly understand that cf-dev and CF Dev are two entirely different things. 

From: <cf-dev@...> on behalf of Stephen Levine <slevine@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Friday, February 23, 2018 at 12:20 PM
To: "cf-dev@..." <cf-dev@...>
Cc: "Sisil, Scott (Pivotal)" <ssisil@...>, "Casey, Emily (Pivotal)" <ecasey@...>, Chip Childers <cchilders@...>, Michael Maximilien <maxim@...>
Subject: [cf-dev] Proposal for Incubation in the Extensions PMC: CF Dev

Hi All,

Pivotal is proposing CF Dev for inclusion in the Extensions PMC as a new incubating project.

CF Dev is a deployment of BOSH and cf-deployment that runs locally in Garden containers. It uses native hypervisors to start quickly with zero external dependencies. It also provides a fully functional BOSH director.

CF Dev is currently available on Github [1].

I would also like to introduce everyone to Scott Sisil, who is joining me as Co-PM on Pivotal's local and community developer initiatives. Please reach out to Scott and/or myself for questions about CF Dev.


Project Name: CF Dev

Project Proposal: See [2], and attached.

Proposed Project Leads: Stephen Levine, Pivotal & Scott Sisil Pivotal

Proposed Contributors: Emily Casey, Pivotal; Dave Protasowski, Pivotal; Stephen Hiehn, Pivotal

Proposed Scope: See [2], and attached.

Development Operating Model: Pairing (local + remote)

Technical Approach: CF CLI plugin that starts a VM using the OS native hypervisor.

Please let us know if you have any questions or feedback.



Join to automatically receive all group messages.