Cinder identity endpoint registration


#1

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but it
fails to register the v1 endpoint. Please help if you have any experience
in deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s | 7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s | b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s | 75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s | f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#2

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but it fails
to register the v1 endpoint. Please help if you have any experience in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s | 7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s | b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s | 75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s | f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#3

Thank you for the info. I have added the code to add new endpoint to the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The cookbook
registers only the v2 endpoint, so the cinder services are not added to the
dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] = 'http’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] = ‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’] =
nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but it
fails
to register the v1 endpoint. Please help if you have any experience in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#4

Also, I needed patches for other services too. For example , openstack uses
scripts from /etc/init to start the services on boot, but these cookbooks
creates scripts in /etc/init.d/. This was the patch I needed for my
platform(ubuntu):

if node[:platform] == ‘ubuntu’ && node[:platform_version] == ‘14.04’
[’<service_name>’].each do |monkey_patch|
svc = resources(service: monkey_patch)
svc.provider(::Chef::Provider::Service::Upstart)
end
end

I needed a lot of modification to get the cookbooks compiled.

On Thu, Feb 5, 2015 at 10:10 AM, Vijaya Bhaskar <
vijayabhaskar@sparksupport.com> wrote:

Thank you for the info. I have added the code to add new endpoint to the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The cookbook
registers only the v2 endpoint, so the cinder services are not added to the
dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] = 'http’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] = ‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’]
= nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but it
fails
to register the v1 endpoint. Please help if you have any experience in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#5

You’ve got me worried about the second email.

That should be resolved in Chef 12, you shouldn’t need that
monkey_patch anymore.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Wed, Feb 4, 2015 at 10:44 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Also, I needed patches for other services too. For example , openstack uses
scripts from /etc/init to start the services on boot, but these cookbooks
creates scripts in /etc/init.d/. This was the patch I needed for my
platform(ubuntu):

if node[:platform] == ‘ubuntu’ && node[:platform_version] == ‘14.04’
[’<service_name>’].each do |monkey_patch|
svc = resources(service: monkey_patch)
svc.provider(::Chef::Provider::Service::Upstart)
end
end

I needed a lot of modification to get the cookbooks compiled.

On Thu, Feb 5, 2015 at 10:10 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Thank you for the info. I have added the code to add new endpoint to the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The cookbook
registers only the v2 endpoint, so the cinder services are not added to the
dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] = 'http’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] = ‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’]
= nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but it
fails
to register the v1 endpoint. Please help if you have any experience in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#6

Initially, I tried to use chef 12, but I found it a bit difficult to get
started with, especially with getting keys. With the Gui I can easily do
this, but Gui is removed in version 12.

On Fri, Feb 6, 2015 at 4:28 AM, JJ Asghar jj@chef.io wrote:

You’ve got me worried about the second email.

That should be resolved in Chef 12, you shouldn’t need that
monkey_patch anymore.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Wed, Feb 4, 2015 at 10:44 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Also, I needed patches for other services too. For example , openstack
uses
scripts from /etc/init to start the services on boot, but these cookbooks
creates scripts in /etc/init.d/. This was the patch I needed for my
platform(ubuntu):

if node[:platform] == ‘ubuntu’ && node[:platform_version] == ‘14.04’
[’<service_name>’].each do |monkey_patch|
svc = resources(service: monkey_patch)
svc.provider(::Chef::Provider::Service::Upstart)
end
end

I needed a lot of modification to get the cookbooks compiled.

On Thu, Feb 5, 2015 at 10:10 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Thank you for the info. I have added the code to add new endpoint to the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The
cookbook

registers only the v2 endpoint, so the cinder services are not added to
the

dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] =
‘http’

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] = ‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’]

= nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but
it

fails
to register the v1 endpoint. Please help if you have any experience
in

deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#7

If you’re worried about the server, you can run the server as chef 11
with the gui, and have the client be chef 12 to work around that
monkey patch.

Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Fri, Feb 6, 2015 at 1:50 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Initially, I tried to use chef 12, but I found it a bit difficult to get
started with, especially with getting keys. With the Gui I can easily do
this, but Gui is removed in version 12.

On Fri, Feb 6, 2015 at 4:28 AM, JJ Asghar jj@chef.io wrote:

You’ve got me worried about the second email.

That should be resolved in Chef 12, you shouldn’t need that
monkey_patch anymore.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Wed, Feb 4, 2015 at 10:44 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Also, I needed patches for other services too. For example , openstack
uses
scripts from /etc/init to start the services on boot, but these
cookbooks
creates scripts in /etc/init.d/. This was the patch I needed for my
platform(ubuntu):

if node[:platform] == ‘ubuntu’ && node[:platform_version] == ‘14.04’
[’<service_name>’].each do |monkey_patch|
svc = resources(service: monkey_patch)
svc.provider(::Chef::Provider::Service::Upstart)
end
end

I needed a lot of modification to get the cookbooks compiled.

On Thu, Feb 5, 2015 at 10:10 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Thank you for the info. I have added the code to add new endpoint to
the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The
cookbook
registers only the v2 endpoint, so the cinder services are not added to
the
dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under
the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] =
‘http’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] =
‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’]
= nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook, but
it
fails
to register the v1 endpoint. Please help if you have any experience
in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


#8

Thanks , but when I bootstrap a node the client version installed is 11.xx.

On 2/6/15, JJ Asghar jj@chef.io wrote:

If you’re worried about the server, you can run the server as chef 11
with the gui, and have the client be chef 12 to work around that
monkey patch.

Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Fri, Feb 6, 2015 at 1:50 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Initially, I tried to use chef 12, but I found it a bit difficult to get
started with, especially with getting keys. With the Gui I can easily do
this, but Gui is removed in version 12.

On Fri, Feb 6, 2015 at 4:28 AM, JJ Asghar jj@chef.io wrote:

You’ve got me worried about the second email.

That should be resolved in Chef 12, you shouldn’t need that
monkey_patch anymore.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Wed, Feb 4, 2015 at 10:44 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Also, I needed patches for other services too. For example , openstack
uses
scripts from /etc/init to start the services on boot, but these
cookbooks
creates scripts in /etc/init.d/. This was the patch I needed for my
platform(ubuntu):

if node[:platform] == ‘ubuntu’ && node[:platform_version] == ‘14.04’
[’<service_name>’].each do |monkey_patch|
svc = resources(service: monkey_patch)
svc.provider(::Chef::Provider::Service::Upstart)
end
end

I needed a lot of modification to get the cookbooks compiled.

On Thu, Feb 5, 2015 at 10:10 AM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Thank you for the info. I have added the code to add new endpoint to
the
recipe myself. But Cinder(juno) needs two endpoints - v1 & v2. The
cookbook
registers only the v2 endpoint, so the cinder services are not added
to
the
dashboard. This is what I did to get it working:

Added the following to openstack-common/attributes/default.rb, under
the
cinder endpoint section:

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘host’] =
node[‘openstack’][‘endpoints’][‘host’]
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘scheme’] =
‘http’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘port’] =
‘8776’
default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘path’] =
’/v1/%(tenant_id)s’

default[‘openstack’][‘endpoints’][‘block-storage-api1’][‘bind_interface’]
= nil

Added the following to the
openstack-block-storage/recipes/identity_registration.rb file:

openstack_identity_register ‘Register Cinder V1 Volume Service’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_service
end

cinder_api_endpoint = endpoint ‘block-storage-api1’

openstack_identity_register ‘Register Cinder V1 Volume Endpoint’ do
auth_uri auth_uri
bootstrap_token bootstrap_token
service_name 'cinder’
service_type 'volume’
service_description 'Cinder Volume Service V1’
endpoint_region region
endpoint_adminurl ::URI.decode cinder_api_endpoint.to_s
endpoint_internalurl ::URI.decode cinder_api_endpoint.to_s
endpoint_publicurl ::URI.decode cinder_api_endpoint.to_s
action :create_endpoint
end

So this was a small patch, to get cinder working fully.

On Tue, Feb 3, 2015 at 11:21 PM, JJ Asghar jj@chef.io wrote:

Hi Vijaya,

So we are moving away from the openstack-chef-repo. We are in the
process of moving towards our testing-stack which should be pushed
up
into stackforge in the next few days.
https://github.com/jjasghar/chef-openstack-testing-stack

What version of the cinder cookbook are you using? We have a
dedicated
openstack-chef mailing list here too:
https://groups.google.com/forum/#!forum/opscode-chef-openstack

Please don’t hesitate to email me directly, jj@chef.io
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2

On Mon, Feb 2, 2015 at 11:25 PM, Vijaya Bhaskar
vijayabhaskar@sparksupport.com wrote:

Hello all,

I am trying to deploy openstack cinder through the official
openstack-chef-repo. I have installed cinder with the cookbook,
but
it
fails
to register the v1 endpoint. Please help if you have any
experience
in
deploying cinder using chef.:

Current:

root@controller1:~# keystone endpoint-list | grep 8776
| 7ec7e0a818fe42b688d7156da8113cf0 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
7a4fb65727304ee393561fcebac171fd
|
| 94885cd8d4c743db9419939e1ddfe0c5 | RegionOne |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
http://10.0.11.100:8776/v2/%(tenant_id)s |
b211d82a20e24692852f95f33bf7251b
|

expected:

root@controller:~# keystone endpoint-list | grep 8776
| 368afc818e12434ba1c99fd0ffa9e634 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
75529d583a9044269db2f5a4d46a2845 |
| 6c34d10008b54b34a394d31164d73ac6 | regionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
f00ce4c7e62048bc824eb84907eeeaca |

Please ignore the IP addresses or hostnames


Systems Engineer
SparkSupport