It would be good to have plan renaming feature, also would be good to
have it only as display name so that it can be changed without much of
dependency. We have also faced similar situations previously.

--




Subhankar Chattopadhyay
Bangalore, India

Hi,

Try the binary buildpack or a Docker image.
There you have most flexibility.

Best regards,
Petar


On Wed, Jul 26, 2017 at 5:48 PM, Raghuvamsi Uthpala <
Raghuvamsi.Uthpala(a)indegene.com> wrote:

Hi Team,



I’m new to cloud foundry and we are setting up CF for our organization.



We have a requirement for one of our apps that it needs openJFX with java
8 . I’ve tried creating some custom build packs but not successful.

Can some one help me out if there are some build packs which I can use
that support openJFX or some steps to add this to default java-buildpack.



Appreciate your help.



*Raghuvamsi Uthpala*

Office: +91-80-39204567 <+91%2080%203920%204567>

DevOps – Lead.

Software Engineering Services

Mobile: +91- 9492901250 <+91%2094929%2001250>

Email: raghuvamsi.uthpala(a)indegene.com

Web: www.indegene.com

[image: cid:image001.png(a)01D1006F.0E0455B0] <http://www.indegene.com/>

Follow us:

*[image: cid:image002.png(a)01D1006F.0E0455B0]*
<https://www.linkedin.com/company/68889?trk=tyah&trkInfo=clickedVertical:company,clickedEntityId:68889,idx:2-1-2,tarId:1438602556067,tas:indege>

*[image: cid:image003.png(a)01D1006F.0E0455B0]*
<https://www.facebook.com/Indegene>



[image: cid:image004.png(a)01D1006F.0E0455B0] <http://www.indegene.com/atom>



Disclaimer: This email (including any attachments) contains information,
which is confidential and may be subject to legal privilege. If you are not
the intended recipient, you must not use, distribute, or copy this email.
If you have received this email in error, please notify the sender
immediately and delete this. Any views expressed in this mail are not
necessarily the views of INDEGENE. Thank you.






Disclaimer : This message and any attachments are solely for the intended
recipient and may contain confidential or privileged information. If you
are not the intended recipient, any disclosure, copying, use, or
distribution of the information included in this message and any
attachments is prohibited. If you have received this communication in
error, please notify us by reply e-mail to IT(a)Indegene.com and
immediately and permanently delete this message and any attachments. Any
views expressed in this mail are not necessarily the views of INDEGENE.
Thank you.

We have renamed plans and services in the past. I would like to be able to
continue to update them in the future. But I wouldn't consider it a must
have feature but it does has come in handy in the past.

Mike

The Service Broker API currently supports modifying the service name and
plan name fields, as a uuid is used as the unique identifier. These names
are used in CLI workflows, and are used by applications to parse the
VCAP_SERVICES environment variable to identify credentials. In practice, if
these names are changed it may require updating an application to use the
new service name to identify credentials.

The metadata field is often used to expose display names for services and
plans.

The Open Service Broker API working group is interested to know how often
these names actually change, and whether they could be considered immutable
in the future.

Best,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

Hi Raghuvamsi,

It may be worth opening an issue about this on the Java buildpack Github
issue tracker[1].

[1] https://github.com/cloudfoundry/java-buildpack/issues

Thanks,
Stephen

On Wed, Jul 26, 2017 at 10:48 AM, Raghuvamsi Uthpala <
Raghuvamsi.Uthpala(a)indegene.com> wrote:

Hi Team,



I’m new to cloud foundry and we are setting up CF for our organization.



We have a requirement for one of our apps that it needs openJFX with java
8 . I’ve tried creating some custom build packs but not successful.

Can some one help me out if there are some build packs which I can use
that support openJFX or some steps to add this to default java-buildpack.



Appreciate your help.



*Raghuvamsi Uthpala*

Office: +91-80-39204567 <+91%2080%203920%204567>

DevOps – Lead.

Software Engineering Services

Mobile: +91- 9492901250 <+91%2094929%2001250>

Email: raghuvamsi.uthpala(a)indegene.com

Web: www.indegene.com

[image: cid:image001.png(a)01D1006F.0E0455B0] <http://www.indegene.com/>

Follow us:

*[image: cid:image002.png(a)01D1006F.0E0455B0]*
<https://www.linkedin.com/company/68889?trk=tyah&trkInfo=clickedVertical:company,clickedEntityId:68889,idx:2-1-2,tarId:1438602556067,tas:indege>

*[image: cid:image003.png(a)01D1006F.0E0455B0]*
<https://www.facebook.com/Indegene>



[image: cid:image004.png(a)01D1006F.0E0455B0] <http://www.indegene.com/atom>



Disclaimer: This email (including any attachments) contains information,
which is confidential and may be subject to legal privilege. If you are not
the intended recipient, you must not use, distribute, or copy this email.
If you have received this email in error, please notify the sender
immediately and delete this. Any views expressed in this mail are not
necessarily the views of INDEGENE. Thank you.






Disclaimer : This message and any attachments are solely for the intended
recipient and may contain confidential or privileged information. If you
are not the intended recipient, any disclosure, copying, use, or
distribution of the information included in this message and any
attachments is prohibited. If you have received this communication in
error, please notify us by reply e-mail to IT(a)Indegene.com and
immediately and permanently delete this message and any attachments. Any
views expressed in this mail are not necessarily the views of INDEGENE.
Thank you.

Hi cf-dev,

To add to this, I wanted to clarify what the Release Integration team is
currently validating, and what we will plan to validate, in our pipelines.

*Currently*
We validate cf-release against the deprecated Vagrant workflow, and
cf-deployment against the new bosh-lite workflow that uses bosh-deployment
as described on bosh.io.

*In the near future -- about two weeks*
We're going to switch to using the bosh-deployment workflow for cf-release,
and support that for the remainder of cf-release's lifetime. cf-deployment
will continue to be validated on the bosh-deployment workflow as well.

*tl;dr - The Release Integration team will stop validating the Vagrant
workflow for bosh-lite in two weeks, so please switch to using the workflow
described on bosh.io <http://bosh.io>*

Thanks,
David Sabeti
CF Release Integration Project Lead

cf-deployment will be going GA over the next couple of months, and
production transitions between cf-release and cf-deployment will be
painful. (My team is working on the first one now.)

If you set up with cf-deployment and give David Sabeti (PM of the team
making it) feedback about any features you need, you'll save yourself a lot
of time and pain.

You'll also be able to use BOSH to generate all your certs automatically.

- Natalie
Pivotal Cloud Operations

On Mon, Aug 7, 2017 at 4:49 AM Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi David McClure,

Right now I am preparing this for testing environment. But surely after
this proof of concept , It will be on production environment.

Hi David McClure,

I have tried above mentioned method, but I am getting error like this:

Task 101

07:35:43 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Required property 'networks' was not specified in object ({})

07:35:44 | Error: Required property 'networks' was not specified in object ({})

Started Tue Aug 8 07:35:43 UTC 2017
Finished Tue Aug 8 07:35:44 UTC 2017
Duration 00:00:01

Task 101 error

Updating deployment:
Expected task '101' to succeed but state is 'error'

Exit code 1


Can you help me with this?

Hi David McClure,

Got the link. Thanks for your response. Let me check and try with this.

Hey David,

The link which you shared me, it is giving 404 error.

Hi David McClure,

Right now I am preparing this for testing environment. But surely after this proof of concept , It will be on production environment.

+cf-dev

Since Diego-Release v1.21.0, the Route Emitter job has supported
registration of both HTTP routes (via NATS) and TCP routes (via Routing
API). This makes the TCP-Emitter in the Routing-Release no longer
necessary. The Routing team will drop the TCP-Emitter job from
Routing-Release in v0.164.0.

To configure the Route Emitter to register TCP routes, configure the
following properties in your manifest for the router-emitter job:

tcp.enabled: true
routing_api.url: defaults to http://routing-api.service.cf.internal
routing_api.port: defaults to 3000
routing_api.auth_enabled: defaults to true

We also recommend running the route-emitter job in "Local Mode", as this
removes a dependency on Consul for a distributed lock. This can be
configured by colocating the job on each Cell and configuring the following
property:

diego.route_emitter.local_mode: true.

Please reply with questions or concerns.

Thank you!

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

Is this for production or testing?

If its for testing, definitely check out cf-deployment
<https://github.com/cloudfoundry/cf-deployment> which uses new features of
bosh to generate certs and keys for you automatically.

If its for production, keep an eye on this table
<https://github.com/cloudfoundry/cf-deployment#readiness>.

I'm not sure what the most straightforward thing to do is with cf-release
these days. I know many releases maintained their own scripts to generate
certs and keys, so that's one option. Another would be to use
cf-deployment with bosh interpolate to generate all the certs, keys and
passwords, and then copy those into the necessary slots in the cf-release
stubs or manifests.


On Fri, Aug 4, 2017 at 6:46 AM, Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Dear Team,

I am planning to deploy cloudfoundry on openstack. I have deployed bosh on
openstack. But Stub manifest file asking for lot of certs and keys. Any
simple stub file? so atleast i can just check how cloudfoundry works.

Thanks & Regards:
Arpit

Dear Team,

I am planning to deploy cloudfoundry on openstack. I have deployed bosh on openstack. But Stub manifest file asking for lot of certs and keys. Any simple stub file? so atleast i can just check how cloudfoundry works.

Thanks & Regards:
Arpit

Hello!

Christine Lee and I are designers on the CAPI team, and we are looking for Application Developers to participate in user research in the coming weeks - to get a better understanding of the app dev lifecycle, and needs around uptime.

If you're open to spending ~30 min sharing about your experience using CF, please use this form to sign up for a time:

https://goo.gl/forms/54xNBIuDZmvnlqey1

We'd really appreciate the opportunity to learn about some of your needs and painpoints using CF. Thank you in advance!

Cheers,
Kim Eberz and Christine Lee
Pivotal Product Designers on CAPI

Hello all,

Pivotal is nominating Colin Jackson for the Garden Windows (Greenhouse)
Project Lead in the Runtime PMC.

Colin joined Pivotal in February 2015 as an engineer on the Buildpacks team
in New York, while the team was adopting the PHP buildpack. He also worked
on Lattice, a frontend CLI and canonical deployment, and anchored a PCF
team. Colin transitioned to a PM role in September 2016, and has been
shadowing A William Martin over the past few months on Greenhouse.

Any other nominations should be sent to me/in reply by end of day August
7th, 2017.

If you have any questions about the role/process, please let me know.
These are described in the CFF governance documents. [1]

-Dieu Cao

Runtime PMC Lead

[1]
https://www.cloudfoundry.org/wp-content/uploads/2015/09/CFF_Development_Operations_Policy.pdf

Hi, all,

The Diego team is planning to remove a minor piece of configurability in
diego-release, but wanted first to verify that it will have no substantial
impact to operators. *If you have never configured the
diego.executor.cache_path property for your Diego cells, feel free to stop
reading now.*

This property controls the location of the cache of downloaded assets
(primarily buildpacks and droplets) on the Diego cells. We intend to change
its location to a fixed subdirectory of /var/vcap/data/rep as part of
consolidating the Diego rep job's working directory structure on a
BOSH-deployed VM in https://www.pivotaltracker.com/story/show/149742283,
but we realized that it does happen to be configurable via the above BOSH
property.

As we understand it, any significant change to this value (say, moving it
to another mounted volume) never even worked at all: the cell uses
rename(2) to move files between this directory and other directories
hard-coded to be on the BOSH ephemeral disk, and rename does not work
across volumes. In any case, if having this value always be hard-coded in
your CF or Diego deployments will be a problem, please let me know why.

Thanks,
Eric, CF Diego PM

Hello all,

A William Martin, the Project Lead for the Garden Windows (Greenhouse) team
within the Runtime PMC, will be focusing more of his time on the BOSH
Windows team in the BOSH PMC. We thank him for his time serving as the
Garden Windows Project Lead.

The Garden Windows team, primarily located in New York, New York, now has
an opening for its project lead. The team currently maintains the Garden
Windows release. Project leads must be nominated by a Cloud Foundry
Foundation member.

Please send nominations to me/in reply to this posting by end of day August
7th, 2017.

If you have any questions about the role/process, please let me know.
These are described in the CFF governance documents. [1]

-Dieu Cao

Runtime PMC Lead

[1] https://www.cloudfoundry.org/wp-content/uploads/2015/09/
CFF_Development_Operations_Policy.pdf

You could try this: https://github.com/cloudfoundry/cf-mysql-release

Once you have the broker up and running, you add it to the local CF
marketplace (see service broker docs on docs.cloudfoundry.org)

On Mon, Jul 31, 2017 at 10:40 AM Sunil Valmiki <sunilhvalmiki(a)gmail.com>
wrote:

Ya David, I followed your links and I can successfully push app and run
them.
I followed this link also:
https://github.com/cloudfoundry/diego-release
How to setup the Mysql database?
How can I connect the apps to the Mysql database?




--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Difference-Between-Cloud-foundry-and-Pivotal-Cloud-Foundry-tp7259p7434.html
Sent from the CF Dev mailing list archive at Nabble.com.

--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815