Re: CF deployment on BOSH-lite


Subhankar Chattopadhyay <subho.atg@...>
 

Hi David,

Sure, will do that. So far it works well for me on boshlite.

Regards,
Subhankar.

On Thu, 10 Aug 2017 at 11:24 PM, David Sabeti <dsabeti(a)pivotal.io> wrote:

Subhankar,

If you have any questions about cf-deployment, feel free to jump in the
#cf-deployment channel on the Cloud Foundry slack, or open a Github issue
on the repo. The RelInt team (which maintains cf-deployment) can help you
out there.

David

On Thu, Aug 10, 2017 at 10:40 AM Subhankar Chattopadhyay <
subho.atg(a)gmail.com> wrote:

Hi,

Thanks to all for your prompt reply. Surely, cf-deployment eases lot of
deployment complexity!

Regards,
Subhankar

On Thu, 10 Aug 2017 at 9:39 PM, Eric Malm <emalm(a)pivotal.io> wrote:

Hi, Subhankar,

That's likely the result of the consul certificates in the canned
BOSH-Lite CF manifest expiring after 2 years.
https://github.com/cloudfoundry/cf-release/pull/1229 fixes that, has
been merged, and should be in a new cf-release release-candidate and then
final CF release soon. In the meantime, you can also use
./scripts/generate-consul-certs in the cf-release to generate a new set of
certificates and then copy them into the appropriate BOSH properties in
templates/cf-infrastructure-bosh-lite.yml.

I second Natalie's advice to try using cf-deployment (
https://github.com/cloudfoundry/cf-deployment) to deploy CF to
BOSH-Lite instead of the older manifest-generation systems in cf-release
and diego-release.

Best,
Eric, CF Diego PM

On Thu, Aug 10, 2017 at 9:01 AM, Natalie Bennett <nbennett(a)pivotal.io>
wrote:

You should 100% be using cf-deployment for local development at this
point. Release Integration is now working with Pivotal CloudOps to
transition Pivotal's production CF instance to cf-deployment.

Once there's a running production instance of cf-deployment, RelInt
will begin the process of deprecating cf-release. If you can avoid
transitioning yourself, or learning cf-r's manifest generation, you should.

Exactly what's going on with consul depends on why Bosh lite crashed. I
personally wouldn't spend much time debugging it since consul is also in
the process of being removed.

A couple of possible steps for the consul problem:

1. That error output looks like a problem with certs, so those certs
might just be wrong. You won't have that problem with cf-d since it
generates its own certs.

2. When in doubt and not in production, scale consul down to 1, delete
its data directory (I think /var/vcap/store but I'd expect the consul
release repo to have instructions) and scale back up

3. Though what I'd do is tear the whole thing down and start over.

- Natalie

On Thu, Aug 10, 2017 at 7:53 AM Subhankar Chattopadhyay <
subho.atg(a)gmail.com> wrote:

Hi,

I used to deploy CF using the
cf-release(https://github.com/cloudfoundry/cf-release) and following
the steps mentioned in
http://docs.cloudfoundry.org/deploying/boshlite/create_a_manifest.html
.
It was working fine till my bosh-lite crashed and when I tried to re
install, consul_z1 was not running and I got the following error
inside the log

error during stop: dial tcp [::1]:8400: getsockopt: connection refused
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"
2017/08/09 04:23:24 [ERR] agent.client: Failed to decode response
header: EOF
2017/08/09 04:23:24 [ERR] agent.client: Failed to decode response
header: EOF
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"
2017/08/09 04:24:26 [ERR] agent.client: Failed to decode response
header: EOF
2017/08/09 04:24:26 [ERR] agent.client: Failed to decode response
header: EOF
error during start: timeout exceeded: "rpc error: failed to get conn:
x509: certificate has expired or is not yet valid"


Am I missing some steps here? Should I deploy with new certificates ?

I then deployed bosh and cf using
bosh-deployment(https://github.com/cloudfoundry/bosh-deployment) and
cf-deployment(https://github.com/cloudfoundry/cf-deployment). It
worked perfectly.

I am wondering if cf-deployment is the way to go for local bosh-lite
development or I should try with cf-release? Can someone help me with
this?



Regards,
Subhankar Chattopadhyay
Bangalore, India
--



Subhankar Chattopadhyay
Bangalore, India
--



Subhankar Chattopadhyay
Bangalore, India

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.