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
|
