I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
[“openstack-network::identity_registration”,
“openstack-network::linuxbridge”, “openstack-network::l3_agent”,
“openstack-network::dhcp_agent”, “openstack-network::metadata_agent”,
“openstack-network::server”]
Synchronizing Cookbooks:
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
which ends up the recipe compilation if the attribute
node['openstack']['compute']['network']['service_type'] is not 'quantum'
or 'neutron' (this attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's why
it ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can
give you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
Thank you, I think that must be the case. I'll take on from here. I have
found a workaround by adding the compute cookbook as the dependency for
this cookbook. The service_type is set as 'network'
which ends up the recipe compilation if the attribute node['openstack']['
compute']['network']['service_type'] is not 'quantum' or 'neutron' (this
attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's why it
ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can give
you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are
still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
Nice to see people are leveraging Chef and Openstack. As you
undoubtedly know Openstack in extremely interdependent on the
different projects and setting up just one thing usually is a
challenge.
and as you can see it heavily relies on the roles that we define.
If you have an specific questions or would like to bounce some ideas
don't hesitate to ping me directly jj@chef.io, or drop by our IRC
channel on freenode #openstack-chef.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
Thank you, I think that must be the case. I'll take on from here. I have
found a workaround by adding the compute cookbook as the dependency for this
cookbook. The service_type is set as 'network'
which ends up the recipe compilation if the attribute
node['openstack']['compute']['network']['service_type'] is not 'quantum' or
'neutron' (this attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's why it
ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can give
you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are
still
encrypted, but chef is not able to detect forged replies or man in the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use
the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
I have found the issue. The confidugration: default['openstack']['compute'][
'network']['service_type'] is set in a cookbook named openstack-common.
When I set the option correctly , deployment went fine. The openstack
cookbooks, I have used so far, keystone, glance are working fine. I have
not tested the neutron/nova deployment with chef. After the testing, I will
update the status, so that it will be a useful feedback to you, I think.
On Thu, Jan 22, 2015 at 10:58 PM, JJ Asghar jj@chef.io wrote:
Hi Vijaya,
Nice to see people are leveraging Chef and Openstack. As you
undoubtedly know Openstack in extremely interdependent on the
different projects and setting up just one thing usually is a
challenge.
If you have an specific questions or would like to bounce some ideas
don't hesitate to ping me directly jj@chef.io, or drop by our IRC
channel on freenode #openstack-chef.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
Thank you, I think that must be the case. I'll take on from here. I have
found a workaround by adding the compute cookbook as the dependency for
this
cookbook. The service_type is set as 'network'
which ends up the recipe compilation if the attribute
node['openstack']['compute']['network']['service_type'] is not
'quantum' or
'neutron' (this attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's
why it
ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can
give
you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are
still
encrypted, but chef is not able to detect forged replies or man in
the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use
the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent", "openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
Our hangout (live) status meeting are at 15:30 GMT 10:30 EST 07:30 PST
on Mondays and we post the links to the Google Group: Redirecting to Google Groups and our
IRC status meeting/office hours are at 15:30 GMT 10:30 EST 07:30 PST
on Thursdays we try to have as many core members here so we can
discuss topics or issues users are having
And would love to have you join
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
I have found the issue. The confidugration:
default['openstack']['compute']['network']['service_type'] is set in a
cookbook named openstack-common. When I set the option correctly ,
deployment went fine. The openstack cookbooks, I have used so far, keystone,
glance are working fine. I have not tested the neutron/nova deployment with
chef. After the testing, I will update the status, so that it will be a
useful feedback to you, I think.
On Thu, Jan 22, 2015 at 10:58 PM, JJ Asghar jj@chef.io wrote:
Hi Vijaya,
Nice to see people are leveraging Chef and Openstack. As you
undoubtedly know Openstack in extremely interdependent on the
different projects and setting up just one thing usually is a
challenge.
If you have an specific questions or would like to bounce some ideas
don't hesitate to ping me directly jj@chef.io, or drop by our IRC
channel on freenode #openstack-chef.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
Thank you, I think that must be the case. I'll take on from here. I have
found a workaround by adding the compute cookbook as the dependency for
this
cookbook. The service_type is set as 'network'
which ends up the recipe compilation if the attribute
node['openstack']['compute']['network']['service_type'] is not
'quantum' or
'neutron' (this attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's
why it
ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can
give
you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections are
still
encrypted, but chef is not able to detect forged replies or man in
the
middle
attacks.
To fix this issue add an entry like this to your configuration file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can use
the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent",
"openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
Our hangout (live) status meeting are at 15:30 GMT 10:30 EST 07:30 PST
on Mondays and we post the links to the Google Group: Redirecting to Google Groups and our
IRC status meeting/office hours are at 15:30 GMT 10:30 EST 07:30 PST
on Thursdays we try to have as many core members here so we can
discuss topics or issues users are having
And would love to have you join
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
I have found the issue. The confidugration:
default['openstack']['compute']['network']['service_type'] is set in a
cookbook named openstack-common. When I set the option correctly ,
deployment went fine. The openstack cookbooks, I have used so far,
keystone,
glance are working fine. I have not tested the neutron/nova deployment
with
chef. After the testing, I will update the status, so that it will be a
useful feedback to you, I think.
On Thu, Jan 22, 2015 at 10:58 PM, JJ Asghar jj@chef.io wrote:
Hi Vijaya,
Nice to see people are leveraging Chef and Openstack. As you
undoubtedly know Openstack in extremely interdependent on the
different projects and setting up just one thing usually is a
challenge.
and as you can see it heavily relies on the roles that we define.
If you have an specific questions or would like to bounce some ideas
don't hesitate to ping me directly jj@chef.io, or drop by our IRC
channel on freenode #openstack-chef.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
Thank you, I think that must be the case. I'll take on from here. I
have
found a workaround by adding the compute cookbook as the dependency
for
this
cookbook. The service_type is set as 'network'
which ends up the recipe compilation if the attribute
node['openstack']['compute']['network']['service_type'] is not
'quantum' or
'neutron' (this attribute is not set by default in this cookbook)
I suspect you're missing some attributes for this runlist and all the
recipes returns before defining any resource to be converged, that's
why it
ends up with 0 resources.
I can't help more on the subject, hope someone more used to this can
give
you a better hint/guide lines
I am trying to deploy openstack network with chef. When I run the
chef-client , it simply finishes with 0 resources:
root@controller1:~# chef-client
[2015-01-22T15:21:04+05:30] WARN:
SSL validation of HTTPS requests is disabled. HTTPS connections
are
still
encrypted, but chef is not able to detect forged replies or man in
the
middle
attacks.
To fix this issue add an entry like this to your configuration
file:
# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
# OR, Verify only connections to chef-server
verify_api_cert true
To check your SSL configuration, or troubleshoot errors, you can
use
the knife ssl check command like so:
knife ssl check -c /etc/chef/client.rb
Starting Chef Client, version 11.16.4
resolving cookbooks for run list:
["openstack-network::identity_registration",
"openstack-network::linuxbridge", "openstack-network::l3_agent",
"openstack-network::dhcp_agent",
"openstack-network::metadata_agent",
"openstack-network::server"]
Synchronizing Cookbooks:
