Date   

Re: Proposal to end-of-life the varz nozzle

Jim CF Campbell
 

Hi Marco,

the varz nozzle is only for metrics that are *already* in the firehose. It
connects to the firehose and offers a /varz endpoint to the metrics that
come through the firehose. It is designed to support systems that only want
their metrics via varz. There are metrics from DEA and HM9000 that are
currently not in the firehose and only available via /varz.

Does that make sense?

On Fri, Feb 19, 2016 at 11:47 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote:

Dear Jim,

I understand that you want to get rid of a deprecated approach. However,
I'm not sure if there is a parity for the new approach yet and if we've
seen a grace period allowing people to switch.

Can you give us an up-to-date overview about which metrics are available
over the firehose and which *only* over /varz? For example, for quite a
long time the metrics of DEAs were not available in the firehose. I know
that this has recently changed [1], but there hasn't been a cf-release
include these changes.

As this is only one example I remember from the top of my head I'd like to

- be sure that we actually have everything available in the firehose
that we're getting from /varz today
- after that is the case wait some time so people can switch and use
the new approach

Thanks and warm regards
Marco

[1]
https://github.com/cloudfoundry/dea_ng/commit/a1aa10a887c5facb10270f82bba6214529fcfa3d#diff-9edf5787563a04c03ce32d85b1f6d7ab

On 19/02/16 01:21, "Jim CF Campbell" <jcampbell(a)pivotal.io> wrote:

The initial implementation of CF metrics used the Collector to poll /varz
endpoints of various components and then emit them to consumers such as
Datadog, Graphite and others. With the implementation of Loggregator and
the firehose, the default metric path became nozzles attached to the
firehose.

The varz nozzle was created to consume metrics from the firehose and then
present them via polled /varz endpoints to the Collector to allow backward
compatibility. This is a long-deprecated technique and the Loggregator team
is proposing to end support and maintenance of the varz nozzle.

This will be followed soon by an effort to end-of-life the Collector
itself.

We would like community input on this.

--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963



--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963


Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Hi Amit

I will resolve the mysql error. Now I tried to generate the manifest.
I get the below error. We use floating ip for vms.
Please help on this

root(a)vmtest11:/home/cloud-user/test/cf-release# ./generate_deployment_manifest openstack /home/cloud-user/cf-freshvmsdev6a.yml > cf-depolyment.yml
2016/02/19 22:24:57 error generating manifest: unresolved nodes:
(( merge )) in ./templates/cf-infrastructure-openstack.yml meta.floating_static_ips (meta.floating_static_ips)
(( merge )) in ./templates/cf-infrastructure-openstack.yml networks (networks)
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.uaa.clients (properties.uaa.clients)
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.uaadb.roles.[0].password (properties.uaadb.roles.uaaadmin.password)
(( jobs.postgres_z1.networks.cf1.static_ips.[0] )) in dynaml properties.uaadb.address ()
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.cc (properties.cc)
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.ccdb.roles.[0].password (properties.ccdb.roles.ccadmin.password)
(( jobs.postgres_z1.networks.cf1.static_ips.[0] )) in dynaml properties.ccdb.address ()
(( jobs.postgres_z1.networks.cf1.static_ips.[0] )) in dynaml properties.databases.address ()
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.databases.roles.[0].password (properties.databases.roles.ccadmin.password)
(( merge )) in ./templates/cf-infrastructure-openstack.yml properties.databases.roles.[1].password (properties.databases.roles.uaaadmin.password)
(( meta.floating_static_ips )) in dynaml jobs.[0].networks.[0].static_ips ()
(( static_ips(0) )) in ./templates/cf-infrastructure-openstack.yml jobs.[0].networks.[1].static_ips ()
(( static_ips(1) )) in ./templates/cf-infrastructure-openstack.yml jobs.[1].networks.[0].static_ips ()
(( static_ips(2) )) in ./templates/cf-infrastructure-openstack.yml jobs.[2].networks.[0].static_ips ()
(( static_ips(3) )) in ./templates/cf-infrastructure-openstack.yml jobs.[3].networks.[0].static_ips ()
(( static_ips(4) )) in ./templates/cf-infrastructure-openstack.yml jobs.[4].networks.[0].static_ips ()
(( static_ips(5) )) in ./templates/cf-infrastructure-openstack.yml jobs.[5].networks.[0].static_ips ()
(( static_ips(11) )) in ./templates/cf-infrastructure-openstack.yml jobs.[6].networks.[0].static_ips ()
(( static_ips(8, 9, 10) )) in ./templates/cf-infrastructure-openstack.yml jobs.[10].networks.[0].static_ips ()
(( static_ips(12, 13, 14) )) in ./templates/cf-infrastructure-openstack.yml jobs.[11].networks.[0].static_ips ()

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 3:22 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Nithiyasri,

That's something you will have to research yourself. gem install mysql2 -v '0.3.13' could be failing for many reasons related to what's installed on your machine, it's not specific to cloud foundry.

Let me know once you get past that hurdle if you run into any more issues.

Best,
Amit

On Fri, Feb 19, 2016 at 1:47 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amith

After updating, I get the following error
Building cloud_controller_ng...
No artifact found for cloud_controller_ng
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-16

> An error occurred while installing mysql2 (0.3.13), and Bundler cannot continue.
> Make sure that `gem install mysql2 -v '0.3.13'` succeeds before bundling.
'cloud_controller_ng' pre-packaging failed
-------------------------------------------------------------------------------------------------------------
root(a)vmtest11:/home/cloud-user/test/cf-release# gem install mysql2 -v '0.3.13'
Building native extensions. This could take a while...
ERROR: Error installing mysql2:
ERROR: Failed to build gem native extension.

/usr/local/rvm/rubies/ruby-2.1.4/bin/ruby -r ./siteconf20160219-26375-1cfojyi.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.




From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Saturday, February 20, 2016 3:02 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

After checking out, I don have update folder at all in scripts directory.
Instead I have the following in scripts..

root(a)vmtest11:/home/cloud-user/test/cf-release/scripts# ls
create-dev-release.sh remove_blob test travis unused_blobs

Should I run create-dev-release.sh ?


Oops, I have update in cf-release folder…
I will run that…

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 2:59 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Ah, my bad. Yes, after the branch checkout.

On Fri, Feb 19, 2016 at 1:28 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Oh should I ?
I ran update script before checking out the branch.
Even in the steps, you had updated before checking out the branch

From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:56 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Did you run

./update

after checking out the branch?


On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit
Thank you very much for your reply..
Yes after checking out the branch of 3c790dfd, uaa-release folder is removed.
I am using all the backed up src contents of uaa-release in src/uaa folder, because the src/uaa folder is empty..

I am doing the same steps as you had listed down.
Am changing jobs/haproxy/templates/haproxy.config.erb and jobs/haproxy/spec files only..

Now am getting the following error … Some how resolved the previous one

Building uaa...
No artifact found for uaa
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle- for-identity
> Download https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar
> Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4 .3.2/httpcore-4.3.2.jar
> Download https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/ commons-logging-1.2.jar
> :cloudfoundry-identity-model:compileJava FAILED
> :cloudfoundry-identity-model:compileJava took 7095ms
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':cloudfoundry-identity-model:compileJava'.
> > invalid source release: 1.8
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --de bug option to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 5.922 secs
> Task timings:
> 7095ms :cloudfoundry-identity-model:compileJava
> Test timings:
'uaa' pre-packaging failed


Regards
Nithiyasri
From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:11 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: Reg the dev release of cf-205

Amit Kumar Gupta
 

Hi Nithiyasri,

That's something you will have to research yourself. gem install mysql2 -v
'0.3.13' could be failing for many reasons related to what's installed on
your machine, it's not specific to cloud foundry.

Let me know once you get past that hurdle if you run into any more issues.

Best,
Amit

On Fri, Feb 19, 2016 at 1:47 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amith



After updating, I get the following error

*Building cloud_controller_ng...*

* No artifact found for cloud_controller_ng*

* Generating...*

* Pre-packaging...*

* > + set -e -x*

* > + cd /tmp/d20160219-16*



* > An error occurred while installing mysql2 (0.3.13), and Bundler
cannot continue.*

* > Make sure that `gem install mysql2 -v '0.3.13'` succeeds before
bundling.*

*'cloud_controller_ng' pre-packaging failed*


-------------------------------------------------------------------------------------------------------------

root(a)vmtest11:/home/cloud-user/test/cf-release# *gem install mysql2 -v
'0.3.13'*

Building native extensions. This could take a while...

ERROR: Error installing mysql2:

ERROR: Failed to build gem native extension.



/usr/local/rvm/rubies/ruby-2.1.4/bin/ruby -r
./siteconf20160219-26375-1cfojyi.rb extconf.rb

*** extconf.rb failed ***

Could not create Makefile due to some reason, probably lack of necessary

libraries and/or headers. Check the mkmf.log file for more details. You
may

need configuration options.









*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Saturday, February 20, 2016 3:02 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



After checking out, I don have update folder at all in scripts directory.

Instead I have the following in scripts..



root(a)vmtest11:/home/cloud-user/test/cf-release/scripts# ls

create-dev-release.sh remove_blob test travis unused_blobs



Should I run create-dev-release.sh ?





Oops, I have update in cf-release folder…

I will run that…



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Saturday, February 20, 2016 2:59 AM

*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Ah, my bad. Yes, after the branch checkout.



On Fri, Feb 19, 2016 at 1:28 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Oh should I ?

I ran update script before checking out the branch.

Even in the steps, you had updated before checking out the branch



*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 2:56 AM


*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Did you run



./update



after checking out the branch?





On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Thank you very much for your reply..

Yes after checking out the branch of 3c790dfd, uaa-release folder is
removed.

I am using all the backed up src contents of uaa-release in src/uaa
folder, because the src/uaa folder is empty..



I am doing the same steps as you had listed down.

Am changing jobs/haproxy/templates/haproxy.config.erb and
jobs/haproxy/spec files only..



Now am getting the following error … Some how resolved the previous one



Building uaa...

No artifact found for uaa

Generating...

Pre-packaging...

> + set -e -x

> + cd
/tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle-
for-identity

> Download
https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar

> Download
https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4
.3.2/httpcore-4.3.2.jar

> Download
https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/
commons-logging-1.2.jar

> :cloudfoundry-identity-model:compileJava FAILED

> :cloudfoundry-identity-model:compileJava took 7095ms

>

> FAILURE: Build failed with an exception.

>

> * What went wrong:

> Execution failed for task ':cloudfoundry-identity-model:compileJava'.

> > invalid source release: 1.8

>

> * Try:

> Run with --stacktrace option to get the stack trace. Run with --info
or
--de
bug option to get more log output.

>

> BUILD FAILED

>

> Total time: 1 mins 5.922 secs

> Task timings:

> 7095ms :cloudfoundry-identity-model:compileJava

> Test timings:

'uaa' pre-packaging failed





Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 2:11 AM


*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



If you're using a change on top of v205, there was no uaa-release.



Can you please tell me all the steps you're doing?



git clone https://github.com/cloudfoundry/cf-release

cd cf-release

./update

git checkout -b branch1 3c790dfd

# change some files. Which files???

bosh create release



Are you sure these are the exact steps you're doing?









On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

No its not there. I copied gradlew files from uaa-release and ran again .
I asks me to install gem install eventmachine -v '1.0.3'

But installing that , following error is thrown.. I am using ruby2.1.4..
Following error tells me to use ruby1.9.1.

Pls tell me which one I should use



root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v
'1.0.3'

Building native extensions. This could take a while...

ERROR: Error installing eventmachine:

ERROR: Failed to build gem native extension.



/usr/bin/ruby1.9.1 extconf.rb

/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot
load such file -- mkmf (LoadError)

from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'

from extconf.rb:2:in `<main>'





Gem files will remain installed in
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.

Results logged to
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out





*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 1:33 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>


*Subject:* Re: [cf-dev] Reg the dev release of cf-205



In your cf-release directory, under src/uaa, do you see a file called
gradlew?



On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I tried multiple times to create bosh release of cloud foundry on top
of 205. It repeatedly failing at uaa only.



man/man1/javah.1
> release

> THIRD_PARTY_README

> + export
JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + export
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> +
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



Your help on this is much appreciated..



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, February 19, 2016 11:33 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal
(jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



Hi Amit



We have problems in creating a dev release (with haproxy.conf.erb changes)
on top of cloud foundry 205 release and as well problem in creating
manifest for the latest release of cf-230.



But first creating a dev release on cf-205 is our high priority..

So we can focus on this now and I have some answers for your questions reg
that.



We dint make any changes on uaa .. We modified only haproxy.conf.erb and
its spec file .



As I had stated in my first mail, after removing ruby2.1.4 and login
folders from packages directory, I a struck with uaa error..



I used “bosh create release –force –with-tarball” command to create the
release…



Kindly let me know why do I get the above errors and how to reolve the uaa
issue..



Thank you very much for your quick replies…



Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, February 19, 2016 8:00 AM
*To:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>


*Cc:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Are you having problems creating a release or generating a manifest? For
the release, run 'bosh create release', and if you have errors please tell
us the specific errors and the specific changes you've made.



For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Thanks Amit for the pointer!



We hit several challenges while generating the manifest file to deploy
Cloud Foundry. Currently we have an yml file which works for CF-205.



My question is how do I make custom changes to CF release and build a tar
ball with my changes. Is this possible? If yes, what are steps?





Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 6:02 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>
*Cc: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayarajan,



Many people use the generate_deployment_manifest script [1]. It supports
manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage
is documented in [2].



[1]
https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest


[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html



Best,

Amit





On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



We are planning to move to the latest available Cloud Foundry public
release. We built cf-230 and tried to deploy. But we are unable to complete
deployment since it is complaining about missing entries in the deployment
yml file. Our deployment yml file works for cf-205. But it is not
compatible with cf-230.



Could you please let me know how to create a working yml file for cf-230.
I have some custom changes in the haproxy.cfg file which is used while
starting the haproxy job.

I need to put this change in the cf release and build and deploy it.
Please help!



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 4:29 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>


*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayaraj,



What you're describing sounds fairly unsustainable. Do you plan on
maintaining a fork for several years? There have been critical CVEs
addressed in recent releases which you are vulnerable to if you're using
v205. Since you have changed things and are not actually building off the
SHA you said in your original email, I'm not sure how to debug the issues
you're hitting.



Have you changed stuff about the uaa part of cf-release that's affecting
the prepackaging?



Amit



On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for the reply!



Currently we have deployed cf-205 using an yml file and it is in
production. For our deployment we are using dynamic IP and the yml
generation is very complex with static IPs and we are running into issues.
We could never generate an yml successfully and use it for the deployment.



Using the same yml file we are unable to deploy later versions of Cloud
Foundry. We have to make some changes in the cf release to replace some
config files and build another release.

Could you help us building cf-205 with some custom changes which are
required for our use case and deploy.



Really appreciate your quick reply as we are completely stuck.



Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 11:35 AM
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Cc: *Rohit Kumar <rokumar(a)pivotal.io>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Why not just use v206? It's the same thing as the SHA you're checking
out.



http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206



On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Rohit



Kindly forward this to the related person/mailer, if you are not
associated with this clarification, as it is a show-stopper issue for us.



I tried to build a development release on top of cf-205.yml. I am facing
many issues while creating the bosh release.

I have listed them below.. We cloned the git repo and checked out a
detached branch of cf-205 release



§ git clone https://github.com/cloudfoundry/cf-release.git



§ git checkout -b branch1 3c790dfd

*Issues below:*



1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> +
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



I am struck with this… Please let me know how can I resolve this and the
above issues



*Please note:*



I got following error while checking out. So I removed the directories
manually except collector,cloud_controller_ng,loggregator,smoke-tests



$ git checkout -b branch1 3c790dfd

warning: unable to rmdir src/cf-routing-release: Directory not empty

warning: unable to rmdir src/consul-release: Directory not empty

warning: unable to rmdir src/dea-hm-workspace: Directory not empty

warning: unable to rmdir src/etcd-release: Directory not empty

warning: unable to rmdir src/
github.com/cloudfoundry-incubator/route-registrar:
Directory not empty

warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests:
Direct
ory not empty

warning: unable to rmdir src/github.com/cloudfoundry/gorouter: Directory
not emp
ty

warning: unable to rmdir src/statsd-injector: Directory not empty

warning: unable to rmdir src/uaa-release: Directory not empty

M src/cloud_controller_ng

M src/collector

M src/loggregator

M src/smoke-tests

Switched to a new branch 'branch1'



*Background*:

I installed the below to make the packaging work to some extent…



sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]









Regards

Nithiyasri















Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Hi Amith

After updating, I get the following error
Building cloud_controller_ng...
No artifact found for cloud_controller_ng
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-16

> An error occurred while installing mysql2 (0.3.13), and Bundler cannot continue.
> Make sure that `gem install mysql2 -v '0.3.13'` succeeds before bundling.
'cloud_controller_ng' pre-packaging failed
-------------------------------------------------------------------------------------------------------------
root(a)vmtest11:/home/cloud-user/test/cf-release# gem install mysql2 -v '0.3.13'
Building native extensions. This could take a while...
ERROR: Error installing mysql2:
ERROR: Failed to build gem native extension.

/usr/local/rvm/rubies/ruby-2.1.4/bin/ruby -r ./siteconf20160219-26375-1cfojyi.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.




From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Saturday, February 20, 2016 3:02 AM
To: 'Amit Gupta' <agupta(a)pivotal.io>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: RE: [cf-dev] Reg the dev release of cf-205

After checking out, I don have update folder at all in scripts directory.
Instead I have the following in scripts..

root(a)vmtest11:/home/cloud-user/test/cf-release/scripts# ls
create-dev-release.sh remove_blob test travis unused_blobs

Should I run create-dev-release.sh ?


Oops, I have update in cf-release folder…
I will run that…

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 2:59 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Ah, my bad. Yes, after the branch checkout.

On Fri, Feb 19, 2016 at 1:28 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Oh should I ?
I ran update script before checking out the branch.
Even in the steps, you had updated before checking out the branch

From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:56 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Did you run

./update

after checking out the branch?


On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit
Thank you very much for your reply..
Yes after checking out the branch of 3c790dfd, uaa-release folder is removed.
I am using all the backed up src contents of uaa-release in src/uaa folder, because the src/uaa folder is empty..

I am doing the same steps as you had listed down.
Am changing jobs/haproxy/templates/haproxy.config.erb and jobs/haproxy/spec files only..

Now am getting the following error … Some how resolved the previous one

Building uaa...
No artifact found for uaa
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle- for-identity
> Download https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar
> Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4 .3.2/httpcore-4.3.2.jar
> Download https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/ commons-logging-1.2.jar
> :cloudfoundry-identity-model:compileJava FAILED
> :cloudfoundry-identity-model:compileJava took 7095ms
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':cloudfoundry-identity-model:compileJava'.
> > invalid source release: 1.8
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --de bug option to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 5.922 secs
> Task timings:
> 7095ms :cloudfoundry-identity-model:compileJava
> Test timings:
'uaa' pre-packaging failed


Regards
Nithiyasri
From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:11 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

After checking out, I don have update folder at all in scripts directory.
Instead I have the following in scripts..

root(a)vmtest11:/home/cloud-user/test/cf-release/scripts# ls
create-dev-release.sh remove_blob test travis unused_blobs

Should I run create-dev-release.sh ?


Oops, I have update in cf-release folder…
I will run that…

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 2:59 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Ah, my bad. Yes, after the branch checkout.

On Fri, Feb 19, 2016 at 1:28 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Oh should I ?
I ran update script before checking out the branch.
Even in the steps, you had updated before checking out the branch

From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:56 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Did you run

./update

after checking out the branch?


On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit
Thank you very much for your reply..
Yes after checking out the branch of 3c790dfd, uaa-release folder is removed.
I am using all the backed up src contents of uaa-release in src/uaa folder, because the src/uaa folder is empty..

I am doing the same steps as you had listed down.
Am changing jobs/haproxy/templates/haproxy.config.erb and jobs/haproxy/spec files only..

Now am getting the following error … Some how resolved the previous one

Building uaa...
No artifact found for uaa
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle- for-identity
> Download https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar
> Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4 .3.2/httpcore-4.3.2.jar
> Download https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/ commons-logging-1.2.jar
> :cloudfoundry-identity-model:compileJava FAILED
> :cloudfoundry-identity-model:compileJava took 7095ms
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':cloudfoundry-identity-model:compileJava'.
> > invalid source release: 1.8
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --de bug option to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 5.922 secs
> Task timings:
> 7095ms :cloudfoundry-identity-model:compileJava
> Test timings:
'uaa' pre-packaging failed


Regards
Nithiyasri
From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:11 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: Reg the dev release of cf-205

Amit Kumar Gupta
 

Ah, my bad. Yes, after the branch checkout.

On Fri, Feb 19, 2016 at 1:28 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Oh should I ?

I ran update script before checking out the branch.

Even in the steps, you had updated before checking out the branch



*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 2:56 AM

*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Did you run



./update



after checking out the branch?





On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Thank you very much for your reply..

Yes after checking out the branch of 3c790dfd, uaa-release folder is
removed.

I am using all the backed up src contents of uaa-release in src/uaa
folder, because the src/uaa folder is empty..



I am doing the same steps as you had listed down.

Am changing jobs/haproxy/templates/haproxy.config.erb and
jobs/haproxy/spec files only..



Now am getting the following error … Some how resolved the previous one



Building uaa...

No artifact found for uaa

Generating...

Pre-packaging...

> + set -e -x

> + cd
/tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle-
for-identity

> Download
https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar

> Download
https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4
.3.2/httpcore-4.3.2.jar

> Download
https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/
commons-logging-1.2.jar

> :cloudfoundry-identity-model:compileJava FAILED

> :cloudfoundry-identity-model:compileJava took 7095ms

>

> FAILURE: Build failed with an exception.

>

> * What went wrong:

> Execution failed for task ':cloudfoundry-identity-model:compileJava'.

> > invalid source release: 1.8

>

> * Try:

> Run with --stacktrace option to get the stack trace. Run with --info
or
--de
bug option to get more log output.

>

> BUILD FAILED

>

> Total time: 1 mins 5.922 secs

> Task timings:

> 7095ms :cloudfoundry-identity-model:compileJava

> Test timings:

'uaa' pre-packaging failed





Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 2:11 AM


*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



If you're using a change on top of v205, there was no uaa-release.



Can you please tell me all the steps you're doing?



git clone https://github.com/cloudfoundry/cf-release

cd cf-release

./update

git checkout -b branch1 3c790dfd

# change some files. Which files???

bosh create release



Are you sure these are the exact steps you're doing?









On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

No its not there. I copied gradlew files from uaa-release and ran again .
I asks me to install gem install eventmachine -v '1.0.3'

But installing that , following error is thrown.. I am using ruby2.1.4..
Following error tells me to use ruby1.9.1.

Pls tell me which one I should use



root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v
'1.0.3'

Building native extensions. This could take a while...

ERROR: Error installing eventmachine:

ERROR: Failed to build gem native extension.



/usr/bin/ruby1.9.1 extconf.rb

/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot
load such file -- mkmf (LoadError)

from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'

from extconf.rb:2:in `<main>'





Gem files will remain installed in
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.

Results logged to
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out





*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 1:33 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>


*Subject:* Re: [cf-dev] Reg the dev release of cf-205



In your cf-release directory, under src/uaa, do you see a file called
gradlew?



On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I tried multiple times to create bosh release of cloud foundry on top
of 205. It repeatedly failing at uaa only.



man/man1/javah.1
> release

> THIRD_PARTY_README

> + export
JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + export
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> +
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



Your help on this is much appreciated..



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, February 19, 2016 11:33 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal
(jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



Hi Amit



We have problems in creating a dev release (with haproxy.conf.erb changes)
on top of cloud foundry 205 release and as well problem in creating
manifest for the latest release of cf-230.



But first creating a dev release on cf-205 is our high priority..

So we can focus on this now and I have some answers for your questions reg
that.



We dint make any changes on uaa .. We modified only haproxy.conf.erb and
its spec file .



As I had stated in my first mail, after removing ruby2.1.4 and login
folders from packages directory, I a struck with uaa error..



I used “bosh create release –force –with-tarball” command to create the
release…



Kindly let me know why do I get the above errors and how to reolve the uaa
issue..



Thank you very much for your quick replies…



Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, February 19, 2016 8:00 AM
*To:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>


*Cc:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Are you having problems creating a release or generating a manifest? For
the release, run 'bosh create release', and if you have errors please tell
us the specific errors and the specific changes you've made.



For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Thanks Amit for the pointer!



We hit several challenges while generating the manifest file to deploy
Cloud Foundry. Currently we have an yml file which works for CF-205.



My question is how do I make custom changes to CF release and build a tar
ball with my changes. Is this possible? If yes, what are steps?





Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 6:02 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>
*Cc: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayarajan,



Many people use the generate_deployment_manifest script [1]. It supports
manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage
is documented in [2].



[1]
https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest


[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html



Best,

Amit





On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



We are planning to move to the latest available Cloud Foundry public
release. We built cf-230 and tried to deploy. But we are unable to complete
deployment since it is complaining about missing entries in the deployment
yml file. Our deployment yml file works for cf-205. But it is not
compatible with cf-230.



Could you please let me know how to create a working yml file for cf-230.
I have some custom changes in the haproxy.cfg file which is used while
starting the haproxy job.

I need to put this change in the cf release and build and deploy it.
Please help!



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 4:29 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>


*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayaraj,



What you're describing sounds fairly unsustainable. Do you plan on
maintaining a fork for several years? There have been critical CVEs
addressed in recent releases which you are vulnerable to if you're using
v205. Since you have changed things and are not actually building off the
SHA you said in your original email, I'm not sure how to debug the issues
you're hitting.



Have you changed stuff about the uaa part of cf-release that's affecting
the prepackaging?



Amit



On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for the reply!



Currently we have deployed cf-205 using an yml file and it is in
production. For our deployment we are using dynamic IP and the yml
generation is very complex with static IPs and we are running into issues.
We could never generate an yml successfully and use it for the deployment.



Using the same yml file we are unable to deploy later versions of Cloud
Foundry. We have to make some changes in the cf release to replace some
config files and build another release.

Could you help us building cf-205 with some custom changes which are
required for our use case and deploy.



Really appreciate your quick reply as we are completely stuck.



Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 11:35 AM
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Cc: *Rohit Kumar <rokumar(a)pivotal.io>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Why not just use v206? It's the same thing as the SHA you're checking
out.



http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206



On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Rohit



Kindly forward this to the related person/mailer, if you are not
associated with this clarification, as it is a show-stopper issue for us.



I tried to build a development release on top of cf-205.yml. I am facing
many issues while creating the bosh release.

I have listed them below.. We cloned the git repo and checked out a
detached branch of cf-205 release



§ git clone https://github.com/cloudfoundry/cf-release.git



§ git checkout -b branch1 3c790dfd

*Issues below:*



1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> +
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



I am struck with this… Please let me know how can I resolve this and the
above issues



*Please note:*



I got following error while checking out. So I removed the directories
manually except collector,cloud_controller_ng,loggregator,smoke-tests



$ git checkout -b branch1 3c790dfd

warning: unable to rmdir src/cf-routing-release: Directory not empty

warning: unable to rmdir src/consul-release: Directory not empty

warning: unable to rmdir src/dea-hm-workspace: Directory not empty

warning: unable to rmdir src/etcd-release: Directory not empty

warning: unable to rmdir src/
github.com/cloudfoundry-incubator/route-registrar:
Directory not empty

warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests:
Direct
ory not empty

warning: unable to rmdir src/github.com/cloudfoundry/gorouter: Directory
not emp
ty

warning: unable to rmdir src/statsd-injector: Directory not empty

warning: unable to rmdir src/uaa-release: Directory not empty

M src/cloud_controller_ng

M src/collector

M src/loggregator

M src/smoke-tests

Switched to a new branch 'branch1'



*Background*:

I installed the below to make the packaging work to some extent…



sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]









Regards

Nithiyasri













Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Oh should I ?
I ran update script before checking out the branch.
Even in the steps, you had updated before checking out the branch

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 2:56 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Did you run

./update

after checking out the branch?


On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit
Thank you very much for your reply..
Yes after checking out the branch of 3c790dfd, uaa-release folder is removed.
I am using all the backed up src contents of uaa-release in src/uaa folder, because the src/uaa folder is empty..

I am doing the same steps as you had listed down.
Am changing jobs/haproxy/templates/haproxy.config.erb and jobs/haproxy/spec files only..

Now am getting the following error … Some how resolved the previous one

Building uaa...
No artifact found for uaa
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle- for-identity
> Download https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar
> Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4 .3.2/httpcore-4.3.2.jar
> Download https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/ commons-logging-1.2.jar
> :cloudfoundry-identity-model:compileJava FAILED
> :cloudfoundry-identity-model:compileJava took 7095ms
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':cloudfoundry-identity-model:compileJava'.
> > invalid source release: 1.8
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --de bug option to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 5.922 secs
> Task timings:
> 7095ms :cloudfoundry-identity-model:compileJava
> Test timings:
'uaa' pre-packaging failed


Regards
Nithiyasri
From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 2:11 AM

To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: Reg the dev release of cf-205

Amit Kumar Gupta
 

Did you run

./update

after checking out the branch?


On Fri, Feb 19, 2016 at 1:22 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Thank you very much for your reply..

Yes after checking out the branch of 3c790dfd, uaa-release folder is
removed.

I am using all the backed up src contents of uaa-release in src/uaa
folder, because the src/uaa folder is empty..



I am doing the same steps as you had listed down.

Am changing jobs/haproxy/templates/haproxy.config.erb and
jobs/haproxy/spec files only..



Now am getting the following error … Some how resolved the previous one



Building uaa...

No artifact found for uaa

Generating...

Pre-packaging...

> + set -e -x

> + cd
/tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle-
for-identity

> Download
https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar

> Download
https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4
.3.2/httpcore-4.3.2.jar

> Download
https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/
commons-logging-1.2.jar

> :cloudfoundry-identity-model:compileJava FAILED

> :cloudfoundry-identity-model:compileJava took 7095ms

>

> FAILURE: Build failed with an exception.

>

> * What went wrong:

> Execution failed for task ':cloudfoundry-identity-model:compileJava'.

> > invalid source release: 1.8

>

> * Try:

> Run with --stacktrace option to get the stack trace. Run with --info
or
--de
bug option to get more log output.

>

> BUILD FAILED

>

> Total time: 1 mins 5.922 secs

> Task timings:

> 7095ms :cloudfoundry-identity-model:compileJava

> Test timings:

'uaa' pre-packaging failed





Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 2:11 AM

*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



If you're using a change on top of v205, there was no uaa-release.



Can you please tell me all the steps you're doing?



git clone https://github.com/cloudfoundry/cf-release

cd cf-release

./update

git checkout -b branch1 3c790dfd

# change some files. Which files???

bosh create release



Are you sure these are the exact steps you're doing?









On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

No its not there. I copied gradlew files from uaa-release and ran again .
I asks me to install gem install eventmachine -v '1.0.3'

But installing that , following error is thrown.. I am using ruby2.1.4..
Following error tells me to use ruby1.9.1.

Pls tell me which one I should use



root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v
'1.0.3'

Building native extensions. This could take a while...

ERROR: Error installing eventmachine:

ERROR: Failed to build gem native extension.



/usr/bin/ruby1.9.1 extconf.rb

/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot
load such file -- mkmf (LoadError)

from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'

from extconf.rb:2:in `<main>'





Gem files will remain installed in
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.

Results logged to
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out





*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 1:33 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>


*Subject:* Re: [cf-dev] Reg the dev release of cf-205



In your cf-release directory, under src/uaa, do you see a file called
gradlew?



On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I tried multiple times to create bosh release of cloud foundry on top
of 205. It repeatedly failing at uaa only.



man/man1/javah.1
> release

> THIRD_PARTY_README

> + export
JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + export
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> +
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



Your help on this is much appreciated..



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, February 19, 2016 11:33 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal
(jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



Hi Amit



We have problems in creating a dev release (with haproxy.conf.erb changes)
on top of cloud foundry 205 release and as well problem in creating
manifest for the latest release of cf-230.



But first creating a dev release on cf-205 is our high priority..

So we can focus on this now and I have some answers for your questions reg
that.



We dint make any changes on uaa .. We modified only haproxy.conf.erb and
its spec file .



As I had stated in my first mail, after removing ruby2.1.4 and login
folders from packages directory, I a struck with uaa error..



I used “bosh create release –force –with-tarball” command to create the
release…



Kindly let me know why do I get the above errors and how to reolve the uaa
issue..



Thank you very much for your quick replies…



Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, February 19, 2016 8:00 AM
*To:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>


*Cc:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Are you having problems creating a release or generating a manifest? For
the release, run 'bosh create release', and if you have errors please tell
us the specific errors and the specific changes you've made.



For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Thanks Amit for the pointer!



We hit several challenges while generating the manifest file to deploy
Cloud Foundry. Currently we have an yml file which works for CF-205.



My question is how do I make custom changes to CF release and build a tar
ball with my changes. Is this possible? If yes, what are steps?





Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 6:02 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>
*Cc: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayarajan,



Many people use the generate_deployment_manifest script [1]. It supports
manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage
is documented in [2].



[1]
https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest


[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html



Best,

Amit





On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



We are planning to move to the latest available Cloud Foundry public
release. We built cf-230 and tried to deploy. But we are unable to complete
deployment since it is complaining about missing entries in the deployment
yml file. Our deployment yml file works for cf-205. But it is not
compatible with cf-230.



Could you please let me know how to create a working yml file for cf-230.
I have some custom changes in the haproxy.cfg file which is used while
starting the haproxy job.

I need to put this change in the cf release and build and deploy it.
Please help!



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 4:29 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>


*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayaraj,



What you're describing sounds fairly unsustainable. Do you plan on
maintaining a fork for several years? There have been critical CVEs
addressed in recent releases which you are vulnerable to if you're using
v205. Since you have changed things and are not actually building off the
SHA you said in your original email, I'm not sure how to debug the issues
you're hitting.



Have you changed stuff about the uaa part of cf-release that's affecting
the prepackaging?



Amit



On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for the reply!



Currently we have deployed cf-205 using an yml file and it is in
production. For our deployment we are using dynamic IP and the yml
generation is very complex with static IPs and we are running into issues.
We could never generate an yml successfully and use it for the deployment.



Using the same yml file we are unable to deploy later versions of Cloud
Foundry. We have to make some changes in the cf release to replace some
config files and build another release.

Could you help us building cf-205 with some custom changes which are
required for our use case and deploy.



Really appreciate your quick reply as we are completely stuck.



Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 11:35 AM
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Cc: *Rohit Kumar <rokumar(a)pivotal.io>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Why not just use v206? It's the same thing as the SHA you're checking
out.



http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206



On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Rohit



Kindly forward this to the related person/mailer, if you are not
associated with this clarification, as it is a show-stopper issue for us.



I tried to build a development release on top of cf-205.yml. I am facing
many issues while creating the bosh release.

I have listed them below.. We cloned the git repo and checked out a
detached branch of cf-205 release



§ git clone https://github.com/cloudfoundry/cf-release.git



§ git checkout -b branch1 3c790dfd

*Issues below:*



1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> +
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



I am struck with this… Please let me know how can I resolve this and the
above issues



*Please note:*



I got following error while checking out. So I removed the directories
manually except collector,cloud_controller_ng,loggregator,smoke-tests



$ git checkout -b branch1 3c790dfd

warning: unable to rmdir src/cf-routing-release: Directory not empty

warning: unable to rmdir src/consul-release: Directory not empty

warning: unable to rmdir src/dea-hm-workspace: Directory not empty

warning: unable to rmdir src/etcd-release: Directory not empty

warning: unable to rmdir src/
github.com/cloudfoundry-incubator/route-registrar:
Directory not empty

warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests:
Direct
ory not empty

warning: unable to rmdir src/github.com/cloudfoundry/gorouter: Directory
not emp
ty

warning: unable to rmdir src/statsd-injector: Directory not empty

warning: unable to rmdir src/uaa-release: Directory not empty

M src/cloud_controller_ng

M src/collector

M src/loggregator

M src/smoke-tests

Switched to a new branch 'branch1'



*Background*:

I installed the below to make the packaging work to some extent…



sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]









Regards

Nithiyasri











Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Hi Amit
Thank you very much for your reply..
Yes after checking out the branch of 3c790dfd, uaa-release folder is removed.
I am using all the backed up src contents of uaa-release in src/uaa folder, because the src/uaa folder is empty..

I am doing the same steps as you had listed down.
Am changing jobs/haproxy/templates/haproxy.config.erb and jobs/haproxy/spec files only..

Now am getting the following error … Some how resolved the previous one

Building uaa...
No artifact found for uaa
Generating...
Pre-packaging...
> + set -e -x
> + cd /tmp/d20160219-32061-l32r1w/d20160219-32061-fd2atu/cf-registrar-bundle- for-identity
> Download https://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar
> Download https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore/4 .3.2/httpcore-4.3.2.jar
> Download https://repo1.maven.org/maven2/commons-logging/commons-logging/1.2/ commons-logging-1.2.jar
> :cloudfoundry-identity-model:compileJava FAILED
> :cloudfoundry-identity-model:compileJava took 7095ms
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':cloudfoundry-identity-model:compileJava'.
> > invalid source release: 1.8
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --de bug option to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 5.922 secs
> Task timings:
> 7095ms :cloudfoundry-identity-model:compileJava
> Test timings:
'uaa' pre-packaging failed


Regards
Nithiyasri
From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 2:11 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] Reg the dev release of cf-205

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: build pack

Daniel Mikusa
 

Python buffers what you write to stdout. That's probably why you're not
seeing it. You need change that. There's a handful of ways to make that
happen. Here's what the PHP build pack does.

https://github.com/cloudfoundry/php-buildpack/blob/master/lib/build_pack_utils/cloudfoundry.py#L24-L31

It's also not a good idea to write to stdout during the detect script as
that can conflict with the contract of the detect script, which is supposed
to write a specific value to stdout.

http://docs.cloudfoundry.org/buildpacks/custom.html#detect-script

Try dumping info during the compile script. It should basically be the
same as what you'd get during detect.

Dan

PS. I don't see your script.

On Fri, Feb 19, 2016 at 3:56 PM, Stanley Goston <
stanley.w.goston.iv(a)lmco.com> wrote:

I am trying to output to the terminal or cf logs a message and what some
variable values are inside my detect script. I am using python and was
wondering how this would be done. I have tried both echo and print. Here is
my script:


build pack

Stanley Goston
 

I am trying to output to the terminal or cf logs a message and what some variable values are inside my detect script. I am using python and was wondering how this would be done. I have tried both echo and print. Here is my script:


Re: Reg the dev release of cf-205

Amit Kumar Gupta
 

If you're using a change on top of v205, there was no uaa-release.

Can you please tell me all the steps you're doing?

git clone https://github.com/cloudfoundry/cf-release
cd cf-release
./update
git checkout -b branch1 3c790dfd
# change some files. Which files???
bosh create release

Are you sure these are the exact steps you're doing?




On Fri, Feb 19, 2016 at 12:10 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

No its not there. I copied gradlew files from uaa-release and ran again .
I asks me to install gem install eventmachine -v '1.0.3'

But installing that , following error is thrown.. I am using ruby2.1.4..
Following error tells me to use ruby1.9.1.

Pls tell me which one I should use



root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v
'1.0.3'

Building native extensions. This could take a while...

ERROR: Error installing eventmachine:

ERROR: Failed to build gem native extension.



/usr/bin/ruby1.9.1 extconf.rb

/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot
load such file -- mkmf (LoadError)

from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'

from extconf.rb:2:in `<main>'





Gem files will remain installed in
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.

Results logged to
/var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out





*From:* Amit Gupta [mailto:agupta(a)pivotal.io]
*Sent:* Saturday, February 20, 2016 1:33 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>;
Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>

*Subject:* Re: [cf-dev] Reg the dev release of cf-205



In your cf-release directory, under src/uaa, do you see a file called
gradlew?



On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I tried multiple times to create bosh release of cloud foundry on top
of 205. It repeatedly failing at uaa only.



man/man1/javah.1
> release

> THIRD_PARTY_README

> + export
JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + export
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> +
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



Your help on this is much appreciated..



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, February 19, 2016 11:33 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal
(jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



Hi Amit



We have problems in creating a dev release (with haproxy.conf.erb changes)
on top of cloud foundry 205 release and as well problem in creating
manifest for the latest release of cf-230.



But first creating a dev release on cf-205 is our high priority..

So we can focus on this now and I have some answers for your questions reg
that.



We dint make any changes on uaa .. We modified only haproxy.conf.erb and
its spec file .



As I had stated in my first mail, after removing ruby2.1.4 and login
folders from packages directory, I a struck with uaa error..



I used “bosh create release –force –with-tarball” command to create the
release…



Kindly let me know why do I get the above errors and how to reolve the uaa
issue..



Thank you very much for your quick replies…



Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, February 19, 2016 8:00 AM
*To:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>


*Cc:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Are you having problems creating a release or generating a manifest? For
the release, run 'bosh create release', and if you have errors please tell
us the specific errors and the specific changes you've made.



For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Thanks Amit for the pointer!



We hit several challenges while generating the manifest file to deploy
Cloud Foundry. Currently we have an yml file which works for CF-205.



My question is how do I make custom changes to CF release and build a tar
ball with my changes. Is this possible? If yes, what are steps?





Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 6:02 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>
*Cc: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayarajan,



Many people use the generate_deployment_manifest script [1]. It supports
manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage
is documented in [2].



[1]
https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest


[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html



Best,

Amit





On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



We are planning to move to the latest available Cloud Foundry public
release. We built cf-230 and tried to deploy. But we are unable to complete
deployment since it is complaining about missing entries in the deployment
yml file. Our deployment yml file works for cf-205. But it is not
compatible with cf-230.



Could you please let me know how to create a working yml file for cf-230.
I have some custom changes in the haproxy.cfg file which is used while
starting the haproxy job.

I need to put this change in the cf release and build and deploy it.
Please help!



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 4:29 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>


*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayaraj,



What you're describing sounds fairly unsustainable. Do you plan on
maintaining a fork for several years? There have been critical CVEs
addressed in recent releases which you are vulnerable to if you're using
v205. Since you have changed things and are not actually building off the
SHA you said in your original email, I'm not sure how to debug the issues
you're hitting.



Have you changed stuff about the uaa part of cf-release that's affecting
the prepackaging?



Amit



On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for the reply!



Currently we have deployed cf-205 using an yml file and it is in
production. For our deployment we are using dynamic IP and the yml
generation is very complex with static IPs and we are running into issues.
We could never generate an yml successfully and use it for the deployment.



Using the same yml file we are unable to deploy later versions of Cloud
Foundry. We have to make some changes in the cf release to replace some
config files and build another release.

Could you help us building cf-205 with some custom changes which are
required for our use case and deploy.



Really appreciate your quick reply as we are completely stuck.



Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 11:35 AM
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Cc: *Rohit Kumar <rokumar(a)pivotal.io>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Why not just use v206? It's the same thing as the SHA you're checking
out.



http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206



On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Rohit



Kindly forward this to the related person/mailer, if you are not
associated with this clarification, as it is a show-stopper issue for us.



I tried to build a development release on top of cf-205.yml. I am facing
many issues while creating the bosh release.

I have listed them below.. We cloned the git repo and checked out a
detached branch of cf-205 release



§ git clone https://github.com/cloudfoundry/cf-release.git



§ git checkout -b branch1 3c790dfd

*Issues below:*



1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> +
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



I am struck with this… Please let me know how can I resolve this and the
above issues



*Please note:*



I got following error while checking out. So I removed the directories
manually except collector,cloud_controller_ng,loggregator,smoke-tests



$ git checkout -b branch1 3c790dfd

warning: unable to rmdir src/cf-routing-release: Directory not empty

warning: unable to rmdir src/consul-release: Directory not empty

warning: unable to rmdir src/dea-hm-workspace: Directory not empty

warning: unable to rmdir src/etcd-release: Directory not empty

warning: unable to rmdir src/
github.com/cloudfoundry-incubator/route-registrar:
Directory not empty

warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests:
Direct
ory not empty

warning: unable to rmdir src/github.com/cloudfoundry/gorouter: Directory
not emp
ty

warning: unable to rmdir src/statsd-injector: Directory not empty

warning: unable to rmdir src/uaa-release: Directory not empty

M src/cloud_controller_ng

M src/collector

M src/loggregator

M src/smoke-tests

Switched to a new branch 'branch1'



*Background*:

I installed the below to make the packaging work to some extent…



sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]









Regards

Nithiyasri









Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

No its not there. I copied gradlew files from uaa-release and ran again . I asks me to install gem install eventmachine -v '1.0.3'
But installing that , following error is thrown.. I am using ruby2.1.4.. Following error tells me to use ruby1.9.1.
Pls tell me which one I should use

root(a)vmtest11:/home/cloud-user/cf-release# gem install eventmachine -v '1.0.3'
Building native extensions. This could take a while...
ERROR: Error installing eventmachine:
ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `<main>'


Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out


From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Saturday, February 20, 2016 1:33 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Subject: Re: [cf-dev] Reg the dev release of cf-205

In your cf-release directory, under src/uaa, do you see a file called gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Re: Specifying a Default Domain for an Org

Dieu Cao <dcao@...>
 

There's not currently a way to do this.
The cf CLI actually chooses the default shared domain simply be being the
first in the list.
I've often thought about allowing an Org Manager/Space Manager to specify a
preferred default domain for the Org/Space.
This would of course require changes for the cf CLI and other clients to
respect that selction.
If you are very interested in this feature, I think a PR for this type of
enhancement would be fine.

-Dieu
CF CAPI PM

On Fri, Feb 19, 2016 at 11:33 AM, Stephen Byers <smbyers(a)gmail.com> wrote:

I have a shared domain that spans all orgs and is currently the default
domain used when I push an app. I have created a private domain in an org
that is specific for, say, integration. Is there a way to set the private
domain of a particular org to the default one that is used when none is
specified in the manifest? This would allows us to use the same manifest
but push to one org for a sandbox/dev area and another org from the CI
pipeline without having host collisions in the same Cloud Foundry
installation.

If there is another way I should be thinking about this, that is welcome
also.

Thanks in advance.


Re: Reg the dev release of cf-205

Amit Kumar Gupta
 

In your cf-release directory, under src/uaa, do you see a file called
gradlew?

On Fri, Feb 19, 2016 at 11:41 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I tried multiple times to create bosh release of cloud foundry on top
of 205. It repeatedly failing at uaa only.



man/man1/javah.1
> release

> THIRD_PARTY_README

> + export
JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java

> + export
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> +
PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global
/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin

> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



Your help on this is much appreciated..



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, February 19, 2016 11:33 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal
(jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Reg the dev release of cf-205



Hi Amit



We have problems in creating a dev release (with haproxy.conf.erb changes)
on top of cloud foundry 205 release and as well problem in creating
manifest for the latest release of cf-230.



But first creating a dev release on cf-205 is our high priority..

So we can focus on this now and I have some answers for your questions reg
that.



We dint make any changes on uaa .. We modified only haproxy.conf.erb and
its spec file .



As I had stated in my first mail, after removing ruby2.1.4 and login
folders from packages directory, I a struck with uaa error..



I used “bosh create release –force –with-tarball” command to create the
release…



Kindly let me know why do I get the above errors and how to reolve the uaa
issue..



Thank you very much for your quick replies…



Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, February 19, 2016 8:00 AM
*To:* Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>

*Cc:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Reg the dev release of cf-205



Are you having problems creating a release or generating a manifest? For
the release, run 'bosh create release', and if you have errors please tell
us the specific errors and the specific changes you've made.



For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Thanks Amit for the pointer!



We hit several challenges while generating the manifest file to deploy
Cloud Foundry. Currently we have an yml file which works for CF-205.



My question is how do I make custom changes to CF release and build a tar
ball with my changes. Is this possible? If yes, what are steps?





Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 6:02 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>
*Cc: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayarajan,



Many people use the generate_deployment_manifest script [1]. It supports
manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage
is documented in [2].



[1]
https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest


[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html



Best,

Amit





On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



We are planning to move to the latest available Cloud Foundry public
release. We built cf-230 and tried to deploy. But we are unable to complete
deployment since it is complaining about missing entries in the deployment
yml file. Our deployment yml file works for cf-205. But it is not
compatible with cf-230.



Could you please let me know how to create a working yml file for cf-230.
I have some custom changes in the haproxy.cfg file which is used while
starting the haproxy job.

I need to put this change in the cf release and build and deploy it.
Please help!



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 4:29 PM
*To: *Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com>


*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Hi Jayaraj,



What you're describing sounds fairly unsustainable. Do you plan on
maintaining a fork for several years? There have been critical CVEs
addressed in recent releases which you are vulnerable to if you're using
v205. Since you have changed things and are not actually building off the
SHA you said in your original email, I'm not sure how to debug the issues
you're hitting.



Have you changed stuff about the uaa part of cf-release that's affecting
the prepackaging?



Amit



On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for the reply!



Currently we have deployed cf-205 using an yml file and it is in
production. For our deployment we are using dynamic IP and the yml
generation is very complex with static IPs and we are running into issues.
We could never generate an yml successfully and use it for the deployment.



Using the same yml file we are unable to deploy later versions of Cloud
Foundry. We have to make some changes in the cf release to replace some
config files and build another release.

Could you help us building cf-205 with some custom changes which are
required for our use case and deploy.



Really appreciate your quick reply as we are completely stuck.



Regards

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Thursday, February 18, 2016 at 11:35 AM
*To: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
*Cc: *Rohit Kumar <rokumar(a)pivotal.io>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>
*Subject: *Re: [cf-dev] Reg the dev release of cf-205



Why not just use v206? It's the same thing as the SHA you're checking
out.



http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206



On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Rohit



Kindly forward this to the related person/mailer, if you are not
associated with this clarification, as it is a show-stopper issue for us.



I tried to build a development release on top of cf-205.yml. I am facing
many issues while creating the bosh release.

I have listed them below.. We cloned the git repo and checked out a
detached branch of cf-205 release



§ git clone https://github.com/cloudfoundry/cf-release.git



§ git checkout -b branch1 3c790dfd

*Issues below:*



1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> +
PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed



I am struck with this… Please let me know how can I resolve this and the
above issues



*Please note:*



I got following error while checking out. So I removed the directories
manually except collector,cloud_controller_ng,loggregator,smoke-tests



$ git checkout -b branch1 3c790dfd

warning: unable to rmdir src/cf-routing-release: Directory not empty

warning: unable to rmdir src/consul-release: Directory not empty

warning: unable to rmdir src/dea-hm-workspace: Directory not empty

warning: unable to rmdir src/etcd-release: Directory not empty

warning: unable to rmdir src/
github.com/cloudfoundry-incubator/route-registrar:
Directory not empty

warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests:
Direct
ory not empty

warning: unable to rmdir src/github.com/cloudfoundry/gorouter: Directory
not emp
ty

warning: unable to rmdir src/statsd-injector: Directory not empty

warning: unable to rmdir src/uaa-release: Directory not empty

M src/cloud_controller_ng

M src/collector

M src/loggregator

M src/smoke-tests

Switched to a new branch 'branch1'



*Background*:

I installed the below to make the packaging work to some extent…



sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]









Regards

Nithiyasri








Re: Reg the dev release of cf-205

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Hi Amit

I tried multiple times to create bosh release of cloud foundry on top of 205. It repeatedly failing at uaa only.

man/man1/javah.1
> release
> THIRD_PARTY_README
> + export JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + JAVA_HOME=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java
> + export PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + PATH=/tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/java/bin:/usr/local/rvm/gems/ruby-2.1.4/bin:/usr/local/rvm/gems/ruby-2.1.4(a)global/bin:/usr/local/rvm/rubies/ruby-2.1.4/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/bin:/usr/bin
> + cd /tmp/d20160219-32145-1jjnzas/d20160219-32145-9pvy4h/uaa
> + ./gradlew assemble
> pre_packaging: line 35: ./gradlew: No such file or directory
'uaa' pre-packaging failed

Your help on this is much appreciated..

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, February 19, 2016 11:33 PM
To: 'Amit Gupta' <agupta(a)pivotal.io>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
Subject: RE: [cf-dev] Reg the dev release of cf-205

Hi Amit

We have problems in creating a dev release (with haproxy.conf.erb changes) on top of cloud foundry 205 release and as well problem in creating manifest for the latest release of cf-230.

But first creating a dev release on cf-205 is our high priority..
So we can focus on this now and I have some answers for your questions reg that.

We dint make any changes on uaa .. We modified only haproxy.conf.erb and its spec file .

As I had stated in my first mail, after removing ruby2.1.4 and login folders from packages directory, I a struck with uaa error..

I used “bosh create release –force –with-tarball” command to create the release…

Kindly let me know why do I get the above errors and how to reolve the uaa issue..

Thank you very much for your quick replies…

Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, February 19, 2016 8:00 AM
To: Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Cc: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Are you having problems creating a release or generating a manifest? For the release, run 'bosh create release', and if you have errors please tell us the specific errors and the specific changes you've made.

For generating manifest, please tell us the specific errors you're getting.

On Thursday, February 18, 2016, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Thanks Amit for the pointer!

We hit several challenges while generating the manifest file to deploy Cloud Foundry. Currently we have an yml file which works for CF-205.

My question is how do I make custom changes to CF release and build a tar ball with my changes. Is this possible? If yes, what are steps?


Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<javascript:_e(%7B%7D,'cvml','agupta(a)pivotal.io');>>
Date: Thursday, February 18, 2016 at 6:02 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<javascript:_e(%7B%7D,'cvml','jayark(a)cisco.com');>>
Cc: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<javascript:_e(%7B%7D,'cvml','ngnanase(a)cisco.com');>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayarajan,

Many people use the generate_deployment_manifest script [1]. It supports manifest generation for AWS, OpenStack, vSphere, and vCloud Air. It's usage is documented in [2].

[1] https://github.com/cloudfoundry/cf-release/blob/master/scripts/generate_deployment_manifest
[2] http://docs.cloudfoundry.org/deploying/common/create_a_manifest.html

Best,
Amit


On Thu, Feb 18, 2016 at 5:13 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<javascript:_e(%7B%7D,'cvml','jayark(a)cisco.com');>> wrote:
Hi Amit,

We are planning to move to the latest available Cloud Foundry public release. We built cf-230 and tried to deploy. But we are unable to complete deployment since it is complaining about missing entries in the deployment yml file. Our deployment yml file works for cf-205. But it is not compatible with cf-230.

Could you please let me know how to create a working yml file for cf-230. I have some custom changes in the haproxy.cfg file which is used while starting the haproxy job.
I need to put this change in the cf release and build and deploy it. Please help!

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<javascript:_e(%7B%7D,'cvml','agupta(a)pivotal.io');>>
Date: Thursday, February 18, 2016 at 4:29 PM
To: Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<javascript:_e(%7B%7D,'cvml','jayark(a)cisco.com');>>

Subject: Re: [cf-dev] Reg the dev release of cf-205

Hi Jayaraj,

What you're describing sounds fairly unsustainable. Do you plan on maintaining a fork for several years? There have been critical CVEs addressed in recent releases which you are vulnerable to if you're using v205. Since you have changed things and are not actually building off the SHA you said in your original email, I'm not sure how to debug the issues you're hitting.

Have you changed stuff about the uaa part of cf-release that's affecting the prepackaging?

Amit

On Thu, Feb 18, 2016 at 2:54 PM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<javascript:_e(%7B%7D,'cvml','jayark(a)cisco.com');>> wrote:
Hi Amit,

Thanks a lot for the reply!

Currently we have deployed cf-205 using an yml file and it is in production. For our deployment we are using dynamic IP and the yml generation is very complex with static IPs and we are running into issues. We could never generate an yml successfully and use it for the deployment.

Using the same yml file we are unable to deploy later versions of Cloud Foundry. We have to make some changes in the cf release to replace some config files and build another release.
Could you help us building cf-205 with some custom changes which are required for our use case and deploy.

Really appreciate your quick reply as we are completely stuck.

Regards
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<javascript:_e(%7B%7D,'cvml','agupta(a)pivotal.io');>>
Date: Thursday, February 18, 2016 at 11:35 AM
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<javascript:_e(%7B%7D,'cvml','cf-dev(a)lists.cloudfoundry.org');>>
Cc: Rohit Kumar <rokumar(a)pivotal.io<javascript:_e(%7B%7D,'cvml','rokumar(a)pivotal.io');>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<javascript:_e(%7B%7D,'cvml','jayark(a)cisco.com');>>
Subject: Re: [cf-dev] Reg the dev release of cf-205

Why not just use v206? It's the same thing as the SHA you're checking out.

http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=206

On Thu, Feb 18, 2016 at 3:22 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<javascript:_e(%7B%7D,'cvml','ngnanase(a)cisco.com');>> wrote:
Hi Rohit

Kindly forward this to the related person/mailer, if you are not associated with this clarification, as it is a show-stopper issue for us.

I tried to build a development release on top of cf-205.yml. I am facing many issues while creating the bosh release.
I have listed them below.. We cloned the git repo and checked out a detached branch of cf-205 release


• git clone https://github.com/cloudfoundry/cf-release.git


• git checkout -b branch1 3c790dfd
Issues below:


1. Error: Missing package spec

I removed the empty folder (packages/ruby 2.1.4)



2. Building login...

Package 'login' has a glob that resolves to an empty file list: login/**/*



I removed the packages/login folder to get through the error



3. Building uaa…



+ export JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/j
> + JAVA_HOME=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java

> + export PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/br/local/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/

> + PATH=/tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/java/bin:/usr/rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/rvm/bin:/usr/local/sbin:/usr/loc

> + cd /tmp/d20160218-11264-35gw8p/d20160218-11264-f4nh18/uaa

> + ./gradlew assemble

> pre_packaging: line 35: ./gradlew: No such file or directory

'uaa' pre-packaging failed


I am struck with this… Please let me know how can I resolve this and the above issues


Please note:

I got following error while checking out. So I removed the directories manually except collector,cloud_controller_ng,loggregator,smoke-tests

$ git checkout -b branch1 3c790dfd
warning: unable to rmdir src/cf-routing-release: Directory not empty
warning: unable to rmdir src/consul-release: Directory not empty
warning: unable to rmdir src/dea-hm-workspace: Directory not empty
warning: unable to rmdir src/etcd-release: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry-incubator/route-registrar<http://github.com/cloudfoundry-incubator/route-registrar>: Directory not empty
warning: unable to rmdir src/github.com/cloudfoundry/cf-acceptance-tests<http://github.com/cloudfoundry/cf-acceptance-tests>: Direct ory not empty
warning: unable to rmdir src/github.com/cloudfoundry/gorouter<http://github.com/cloudfoundry/gorouter>: Directory not emp ty
warning: unable to rmdir src/statsd-injector: Directory not empty
warning: unable to rmdir src/uaa-release: Directory not empty
M src/cloud_controller_ng
M src/collector
M src/loggregator
M src/smoke-tests
Switched to a new branch 'branch1'

Background:
I installed the below to make the packaging work to some extent…

sudo apt-get install libgmp3-dev
ruby -version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]






Regards
Nithiyasri


Specifying a Default Domain for an Org

Stephen Byers
 

I have a shared domain that spans all orgs and is currently the default domain used when I push an app. I have created a private domain in an org that is specific for, say, integration. Is there a way to set the private domain of a particular org to the default one that is used when none is specified in the manifest? This would allows us to use the same manifest but push to one org for a sandbox/dev area and another org from the CI pipeline without having host collisions in the same Cloud Foundry installation.

If there is another way I should be thinking about this, that is welcome also.

Thanks in advance.


Re: Proposal to end-of-life the varz nozzle

Marco Voelz
 

Dear Jim,

I understand that you want to get rid of a deprecated approach. However, I'm not sure if there is a parity for the new approach yet and if we've seen a grace period allowing people to switch.

Can you give us an up-to-date overview about which metrics are available over the firehose and which *only* over /varz? For example, for quite a long time the metrics of DEAs were not available in the firehose. I know that this has recently changed [1], but there hasn't been a cf-release include these changes.

As this is only one example I remember from the top of my head I'd like to

* be sure that we actually have everything available in the firehose that we're getting from /varz today
* after that is the case wait some time so people can switch and use the new approach

Thanks and warm regards
Marco

[1] https://github.com/cloudfoundry/dea_ng/commit/a1aa10a887c5facb10270f82bba6214529fcfa3d#diff-9edf5787563a04c03ce32d85b1f6d7ab

On 19/02/16 01:21, "Jim CF Campbell" <jcampbell(a)pivotal.io<mailto:jcampbell(a)pivotal.io>> wrote:

The initial implementation of CF metrics used the Collector to poll /varz endpoints of various components and then emit them to consumers such as Datadog, Graphite and others. With the implementation of Loggregator and the firehose, the default metric path became nozzles attached to the firehose.

The varz nozzle was created to consume metrics from the firehose and then present them via polled /varz endpoints to the Collector to allow backward compatibility. This is a long-deprecated technique and the Loggregator team is proposing to end support and maintenance of the varz nozzle.

This will be followed soon by an effort to end-of-life the Collector itself.

We would like community input on this.

--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963


Re: Required manifest changes for Cloud Foundry

Mike Youngstrom
 

* In this case a release for each buildpack will reduce release download
sizes significantly. My org only uses Java and Node.
* Easily knowing what releases changed and which didn't will be nice. (Not
useful when everything is actively developed but more useful when
components grow more mature)
* If a bug is found in one release near an internal deploy deadline it is
easier to upgrade and test a single component with a fix instead than
waiting for the orchestration of an entirely new cf release with
potentially many more changes.
* Much easier to reuse releases outside of CF (e.g. UAA in bosh, etcd or
consul for internal projects)
* If using CF components like etcd, consul, or nats for in house CF
extensions it is easier for CF to sunset without forcing everyone who uses
it to migrate off. (On that note I'd like to see an independent Nats
release before it is removed from CF release)
* Easier to set up build environments if it ever becomes necessary to do an
internal fork of a release.

On the other hand it doesn't seem like documenting which combination of
components went into a given PWS deploy doesn't seem like that difficult of
a problem to solve. Also, as CF and its associated components mature I'd
imagine that tightly coupled release versions will become less of a problem.

Just a couple of thoughts.

Thanks,
Mike

On Fri, Feb 19, 2016 at 4:58 AM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:

Why are you looking forward to independent releases?
A single release option appears pretty straightforward. Single release
that includes the correct dependent versions.
What are the advantages of breaking them out?

Thanks,
Tom

On Thu, Feb 18, 2016 at 5:28 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

This is excellent! I love the decomposition of the buildpacks. I look
forward to the day when cf-release disappears and we just have a bunch of
small independent releases. Hopefully that day is getting closer and
closer.

Mike

On Thu, Feb 18, 2016 at 11:31 AM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hey developers,

The buildpacks team has recently extracted the buildpacks as separate
releases. As we transition to deploying CF via a bunch of composed
releases, for now we're making the change more transparent, by submoduling
and symlinking the buildpacks releases back into cf-release. This requires
some manifest changes: buildpacks are now colocated with cloud controller,
rather than package dependencies of cloud controller.

If you are using spiff to generate manifests, and are not overriding the
templates/jobs colocated on the api_zN jobs, you can ignore this email. If
you are overriding the api_zN templates in your stub, or if you are not
using spiff, you will need to add the following:

templates:
- name: consul_agent
release: cf
+ - name: go-buildpack
+ release: cf
+ - name: binary-buildpack
+ release: cf
+ - name: nodejs-buildpack
+ release: cf
+ - name: ruby-buildpack
+ release: cf
+ - name: php-buildpack
+ release: cf
+ - name: python-buildpack
+ release: cf
+ - name: staticfile-buildpack
+ release: cf
- name: cloud_controller_ng
release: cf

Please see this commit (
https://github.com/cloudfoundry/cf-release/commit/549e5a8271bbf0d30efdb84f381f38c8bf22099d)
for more details.

Best,
Amit


Re: Automatic routing to maintenance pages

Christopher Piraino <cpiraino@...>
 

Hi Jan,

We added functionality for wildcard routes in the routing layer. By
declaring an app with a "*.example.com" route, it will act as a fallback
application to any request not routed to another app on that subdomain.
This sounds like it would solve your usecase.

The docs page
<http://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html> has
a section called "Create Route With Wildcard Hostname".

Let us know if you have any more questions!

- Chris

On Fri, Feb 19, 2016 at 4:28 AM, Jan Rudert <rudi(a)gehts-uns-gut.de> wrote:

Hi,

we were thinking about the possibility to automatically forward all routes
to a maintenance page in case the application is completely failing (not
accepting connections, all instances not starting, CF continuously
restarting the app, ...)

Currently it seems that we have to do this manually during such downtimes
like this:

$ cf map-route maint-app example.com -n coolapp
$ cf unmap-route my-app example.com -n coolapp

But I found those slides from CF summit 2014:
http://de.slideshare.net/Pivotal/cloud-foundry-summit-2014-cloud-foundry-roadmap.
It contains the promising bullet point "CF Route custom maintenance / error
pages" on Slide #15.

We are wondering if CF devs have plans to build something like this in the
routing layer.

Could look like this.

$ cf map-maintenance-route maint-app example.com -n coolapp

OR

$ cf bind-maintenance-page domain.com -n hostname
$ cf maintenance-page some-random-html


Or is there already some other way to achieve this?

Looking forward to your feedback.

Jan

5461 - 5480 of 9330