Install guide for installing CF on top of openstack


Dimuthu Upeksha
 

Hi

I have been going through this [1] tutorial to install CF on top of Openstack. But I guess that some of the links (Manifest stub [2]) that it directs are outdated and I was unable to complete the deployment. Is there a updated document that I can easily install CF on top of Openstack?

[1] https://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html
[2] https://docs.cloudfoundry.org/deploying/openstack/cf-stub-openstack.html

Thanks
Dimuthu


Marco Nicosia
 

Hi Dimuthu,

The document you're citing is community-owned and is being actively
maintained. If you are having problems with that doc, I'd suggest opening
an Issue for someone to notice and respond.

The right place to report an issue against those docs are here:
https://github.com/cloudfoundry/docs-deploying-cf/issues

If you can, please cite which specific files (ie,
install_cf_openstack.html) you're having trouble with, and what specific
links aren't working.

Thanks!

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
c: 650-796-2948


On Sun, Nov 8, 2015 at 3:08 AM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi

I have been going through this [1] tutorial to install CF on top of
Openstack. But I guess that some of the links (Manifest stub [2]) that it
directs are outdated and I was unable to complete the deployment. Is there
a updated document that I can easily install CF on top of Openstack?

[1]
https://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html
[2]
https://docs.cloudfoundry.org/deploying/openstack/cf-stub-openstack.html

Thanks
Dimuthu


Amit Kumar Gupta
 

Hi Dimuthu,

Yes, it's currently very difficult to keep those docs up to date. The main
difficulty comes in somehow enforcing that the dummy data in the example
stubs and the real data in the stubs we use in our real deployments, stay
somewhat similar in structure, while at the same time ensuring that the
dummy data doesn't have more configuration than it needs to have to get up
and working (whereas our real deployments have specialized data that a
generic deployment shouldn't care about). In the short run I will try and
improve some of the example stubs to be up-to-date and reflect a real
working stub.

Amit

On Mon, Nov 9, 2015 at 10:31 AM, Marco Nicosia <mnicosia(a)pivotal.io> wrote:

Hi Dimuthu,

The document you're citing is community-owned and is being actively
maintained. If you are having problems with that doc, I'd suggest opening
an Issue for someone to notice and respond.

The right place to report an issue against those docs are here:
https://github.com/cloudfoundry/docs-deploying-cf/issues

If you can, please cite which specific files (ie,
install_cf_openstack.html) you're having trouble with, and what specific
links aren't working.

Thanks!

--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
c: 650-796-2948


On Sun, Nov 8, 2015 at 3:08 AM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi

I have been going through this [1] tutorial to install CF on top of
Openstack. But I guess that some of the links (Manifest stub [2]) that it
directs are outdated and I was unable to complete the deployment. Is there
a updated document that I can easily install CF on top of Openstack?

[1]
https://docs.cloudfoundry.org/deploying/openstack/install_cf_openstack.html
[2]
https://docs.cloudfoundry.org/deploying/openstack/cf-stub-openstack.html

Thanks
Dimuthu


Dimuthu Upeksha
 

Hi Marco/ Amith,

I tried with the stub file in [1] to create a deployment manifest and tried to deploy it using "bosh deploy" command. Then I get an error mentioning deployment name not found. I have reported the issue in [2].
However what I need is a working stub file template for current version of bosh/ CF. Also there are some bolgs [3] describing the deployment of CF in a different way than the way document describe. Document instructs to generate the deployment manifest from the stub while that blog directly gives the deployment manifest without a stub. What is the correct way? I have a confusion of what is the latest method.

[1] https://docs.cloudfoundry.org/deploying/openstack/cf-stub-openstack.html
[2] https://lists.cloudfoundry.org/archives/list/cf-bosh(a)lists.cloudfoundry.org/thread/3J5FBVRE7AGAU5HPJGYRITQBM5SZ6ESM/
[3] https://ragss.wordpress.com/2015/03/20/cloud-foundry-on-openstack/

Thanks
Dimuthu


tang feixiong
 

hi
hope the following may help

bosh director (a VM create via microbosh) just like puppet master or
devops server, after created:

$ bosh upload stemcell
bosh-stemcell-3126-openstack-kvm-ubuntu-trusty-go_agent
# upload image into openstack glance, and registered in bosh director,
in deployment manifest, it will be used as whole cf nodes glance image
# the image can be download at http://bosh.io/

$ bosh upload release cf-release-223.tgz
# upload a about 2G cf release tarball into director, later
transferring suitable packages into each cf nodes when deploying
# the tarball can be download at
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=223

$ bosh deployment your-cf-deloyment.yml
# tell bosh where is your yaml file to deploy

$ bosh deploy
# do exactly deployment according previous yaml file

best regards

tangfx

On Tue, Nov 10, 2015 at 2:33 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Marco/ Amith,

I tried with the stub file in [1] to create a deployment manifest and
tried to deploy it using "bosh deploy" command. Then I get an error
mentioning deployment name not found. I have reported the issue in [2].
However what I need is a working stub file template for current version of
bosh/ CF. Also there are some bolgs [3] describing the deployment of CF in
a different way than the way document describe. Document instructs to
generate the deployment manifest from the stub while that blog directly
gives the deployment manifest without a stub. What is the correct way? I
have a confusion of what is the latest method.

[1]
https://docs.cloudfoundry.org/deploying/openstack/cf-stub-openstack.html
[2]
https://lists.cloudfoundry.org/archives/list/cf-bosh(a)lists.cloudfoundry.org/thread/3J5FBVRE7AGAU5HPJGYRITQBM5SZ6ESM/
[3] https://ragss.wordpress.com/2015/03/20/cloud-foundry-on-openstack/

Thanks
Dimuthu


Dimuthu Upeksha
 

Hi Tang

Many thanks for the steps. Where can I find a valid "your-cf-deloyment.yml" that will be working with cf-release-223?

Thanks
Dimuthu


tang feixiong
 

hi Dimuthu

Working for CF DevOps need more skills :)

In my story, there has not existed an suitable manifest for OpenStack.
every devops always do it by themselves.

You could reference from following link:

https://gist.github.com/frodenas

Notice, the manifest may not be available for different CF version, please
carefully review the notes of each version (
https://github.com/cloudfoundry/cf-release/releases)

b/r

tangfx

On Tue, Nov 10, 2015 at 5:04 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Tang

Many thanks for the steps. Where can I find a valid
"your-cf-deloyment.yml" that will be working with cf-release-223?

Thanks
Dimuthu


Amit Kumar Gupta
 

As I mentioned, keeping those docs properly up-to-date is a more difficult
process. To unblock you, here is a stub that should work with the latest
version of CF. You will of course have to replace IPs, credentials, keys,
and certs appropriately. Let me know if you have questions about any of the
values:

https://gist.github.com/Amit-PivotalLabs/04dd9addca704f86b3b7

This is taken directly from the stub used in our CI environment where we
deploy to OpenStack, with the credentials and other environment-specific
information changed.

On Tue, Nov 10, 2015 at 3:25 AM, tang feixiong <tangfx128(a)gmail.com> wrote:

hi Dimuthu

Working for CF DevOps need more skills :)

In my story, there has not existed an suitable manifest for OpenStack.
every devops always do it by themselves.

You could reference from following link:

https://gist.github.com/frodenas

Notice, the manifest may not be available for different CF version, please
carefully review the notes of each version (
https://github.com/cloudfoundry/cf-release/releases)

b/r

tangfx

On Tue, Nov 10, 2015 at 5:04 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Tang

Many thanks for the steps. Where can I find a valid
"your-cf-deloyment.yml" that will be working with cf-release-223?

Thanks
Dimuthu


Dimuthu Upeksha
 

Hi Amit,

Many thanks for the help. I created the deployment manifest using your stub and when I deploy it using bosh deploy I get this https://gist.github.com/DImuthuUpe/53c3d6b972f3a8c90934 error.

Bosh output : https://gist.github.com/DImuthuUpe/653d79a2f72843d2c5c6

What could be the reason for that?

Thanks
Dimuthu


Amit Kumar Gupta
 

Hi Dimuthu,

How much do you care about encryption of the internal Consul traffic? You
could modify the stub I recommended and disable Consul encryption.
Otherwise, one reason it is failing may be due to incorrect values for the
consul properties. You can read here for more on Consul security
configuration options:

https://docs.cloudfoundry.org/deploying/common/consul-security.html

Best,
Amit

On Thu, Nov 12, 2015 at 10:01 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Amit,

Many thanks for the help. I created the deployment manifest using your
stub and when I deploy it using bosh deploy I get this
https://gist.github.com/DImuthuUpe/53c3d6b972f3a8c90934 error.

Bosh output : https://gist.github.com/DImuthuUpe/653d79a2f72843d2c5c6

What could be the reason for that?

Thanks
Dimuthu


Dimuthu Upeksha
 

Hi Amith,

I disabled Consoul authentication as you have mentioned. But still the problem occurs. This is the deployment manifest I use
https://gist.github.com/DImuthuUpe/9f1837d1e237bc48a5e0

Thanks
Dimuthu


tang feixiong
 

hi

hope my own way cloud help you :)

first, ssh into cf node that consul reside, and show detailed log in such
directory
$bosh ssh ...
second, look at all job logs
$cd /var/vcap/sys/log
then check all consul logs
$tail -100 consul...log

I guess, consul don't work because it want to communicate with his server
according job control script.
Before I tried many ways to change consul working method but not succeed,
and later:

1) copy consul binary from /var/vcap/packages/consul-agent/
2) run a consul server in any available machine, like
$ ./consul agent -server -bootstrap-expect 1 -data-dir /tmp/consul
3) In deploy manifest properties, keep consul not use ssl:

properties:
...
consul:
require_ssl: false
encrypt_keys: []

4) In consul job (in my demo, consul packaged with haproxy job because it
help to monitor load balance). override properties and configure consul
client as:

jobs:
...
- name: haproxy
templates:
- name: haproxy
- name: consul
- name: metron_agent
...
properties:
...
consul:
agent:
mode: client
services: {}
servers:
lan: [<previous consul server ip if in same subnet>]
# wan: [<pervious consul server ip if not in LAN, I think>]

best regards

tangfx

On Fri, Nov 13, 2015 at 4:11 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Amith,

I disabled Consoul authentication as you have mentioned. But still the
problem occurs. This is the deployment manifest I use
https://gist.github.com/DImuthuUpe/9f1837d1e237bc48a5e0

Thanks
Dimuthu


Amit Kumar Gupta
 

What version of cf-release are you using to upload to the director when you
"bosh upload release" ?

What SHA of the cf-release repo are using when you use
"generate_deployment_manifest" to generate the manifest using your stub?

Can you ssh onto the consul_z1/0 VM, to sudo su -, and then see what "monit
summary" says (so we can see which processes are failing). Then, if you go
to /var/vcap/sys/log you get a directory of all the relevant process logs.
You can look for errors there, if you don't know where to look, I can help
you with that.

Best,
Amit

On Fri, Nov 13, 2015 at 8:15 AM, tang feixiong <tangfx128(a)gmail.com> wrote:

hi

hope my own way cloud help you :)

first, ssh into cf node that consul reside, and show detailed log in such
directory
$bosh ssh ...
second, look at all job logs
$cd /var/vcap/sys/log
then check all consul logs
$tail -100 consul...log

I guess, consul don't work because it want to communicate with his server
according job control script.
Before I tried many ways to change consul working method but not succeed,
and later:

1) copy consul binary from /var/vcap/packages/consul-agent/
2) run a consul server in any available machine, like
$ ./consul agent -server -bootstrap-expect 1 -data-dir /tmp/consul
3) In deploy manifest properties, keep consul not use ssl:

properties:
...
consul:
require_ssl: false
encrypt_keys: []

4) In consul job (in my demo, consul packaged with haproxy job because it
help to monitor load balance). override properties and configure consul
client as:

jobs:
...
- name: haproxy
templates:
- name: haproxy
- name: consul
- name: metron_agent
...
properties:
...
consul:
agent:
mode: client
services: {}
servers:
lan: [<previous consul server ip if in same subnet>]
# wan: [<pervious consul server ip if not in LAN, I think>]

best regards

tangfx

On Fri, Nov 13, 2015 at 4:11 PM, Dimuthu Upeksha <dimuthu(a)adroitlogic.com>
wrote:

Hi Amith,

I disabled Consoul authentication as you have mentioned. But still the
problem occurs. This is the deployment manifest I use
https://gist.github.com/DImuthuUpe/9f1837d1e237bc48a5e0

Thanks
Dimuthu