Hey Daniel, So your network json looks like it's in good shape. What's happening is that the conduit map for dual mode, intf1 maps to the 2nd NIC (?1g2), but, there is no 2nd NIC available.
Can you double check to make sure you have a 2nd NIC in the system? It's possible that you do have a 2nd NIC in the system, but that the OS is not seeing it due to driver issues, etc. Try running dmesg and search through the output for "eth" to see if you can find any related messages. Hope this helps! Chris Dell, Inc From: Daniel San Pedro [mailto:dsanpe...@mcna.net] Sent: Thursday, October 03, 2013 3:27 PM To: Dearborn, Chris Cc: Jakesch, Simon; crowbar; Jacob, Jacob Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal Here ya go.. Please note that this file was modified before crowbar install by following the below email: Hey Daniel, You definitely need to customize your bc-template-network.json file before installing crowbar. I finally managed to get some time with our network expert this morning to hash out the changes. It sounds like what you want to do is to put all network traffic on eth0 and leave eth1 open for GUI access. To do this install the OS on the admin node, then before running install, make a backup copy of your bc-template-network.json in a different directory, then proceed with customizing the original. The following summarizes the changes I believe you will need to make: 1. Search the entire file for "192.168.124" and change every instance to the subnet that you want. a. Note that if you need a different netmask, you will also need to update all instances of that. 2. Change the mode at the top of the file from "single" to "dual" a. This makes it use the "dual/.*/.*" section of the conduit map i. Take a look at the dual section of the conduit map ii. The intf0 conduit maps to ?1g1 1. "1g" means 1 gigabit and the last "1" means "use the first interface" which is usually eth0 2. The "?" means use the specified speed if available, but if not available, then use a faster speed if available (10g), and if a faster speed is not available then use a slower speed (preferring 100m over 10m). This will force it to use eth0 for the intf0 conduit regardless of the interface speed. iii. The intf1 conduit maps to ?1g2, which will force it to use the second interface (eth1) regardless of the interface speed. 3. In the networks section, change the conduit for every network to be "intf0" except for the public network which should be "intf1", and the bmc_vlan network, which should be "intf2" a. This will move all network traffic to eth0 except for the GUI traffic, which will be on the public network (eth1). 4. In the public network section, change "use_vlan" to false so it will use eth1 for the public network instead of eth1.300. After all these changes, run install to install the Crowbar software on the admin node. Once the admin node (with 2 network interfaces) is up and running, you will need to allocate a public IP address to the admin node manually since we don't allocate one automatically. To do this, ssh into the admin node (crowbar/crowbar), then: * sudo -i * crowbar network allocate_ip default <adminNodeDnsName> public host * Run chef-client and verify the network comes up and runs * Reboot the admin node to ensure the changes take This will return some json which contains the public IP address that was allocated to the admin node. You should then be able to access the Crowbar, Nagios, Ganglia GUI using that IP. Daniel San Pedro Systems Administrator MCNA Dental Plans dsanpe...@mcna.net<mailto:dsanpe...@mcna.net> Office: (800) 494-6262 Ext. 203 ------------------------ CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you. On 10/3/13 3:13 PM, christopher_dearb...@dell.com<mailto:christopher_dearb...@dell.com> wrote: Hey Daniel, This error: ================================================================================ Recipe Compile Error in /var/cache/chef/cookbooks/network/recipes/default.rb ================================================================================ ArgumentError ------------- Conduit mapping intf1 for #<Chef::Node::Attribute:0x7f6327310b50> is not sane: [nil] indicates that there's a misconfiguration in your /opt/dell/chef/data_bags/crowbar/bc-template-network.json. Can you send that along? Thanks, Chris Dell, Inc From: Daniel San Pedro [mailto:dsanpe...@mcna.net] Sent: Thursday, October 03, 2013 3:08 PM To: Dearborn, Chris Cc: Jakesch, Simon; crowbar; Jacob, Jacob Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal Attached. Daniel San Pedro Systems Administrator MCNA Dental Plans dsanpe...@mcna.net<mailto:dsanpe...@mcna.net> Office: (800) 494-6262 Ext. 203 ------------------------ CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you. On 10/3/13 3:01 PM, christopher_dearb...@dell.com<mailto:christopher_dearb...@dell.com> wrote: Hey Daniel, If Quantum itself is failing, then you should have logs in /var/log/quantum on whatever node you selected when deploying the quantum barclamp. You probably picked your controller node. It's possible that a failure occurred before this. In that case, look on your admin node in /opt/dell/crowbar_framework/log directory for a log file named <controllerDnsName>.chef_client.log. Thanks, Chris Dell, Inc From: crowbar-bounces On Behalf Of Daniel San Pedro Sent: Thursday, October 03, 2013 2:49 PM To: Dearborn, Chris Cc: Jakesch, Simon; crowbar; Jacob, Jacob Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal No network node, all I have is a controller node (which I'm trying to install quantum on) and the compute node. Daniel San Pedro Systems Administrator MCNA Dental Plans dsanpe...@mcna.net<mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net> Office: (800) 494-6262 Ext. 203 ------------------------ CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you. On 10/3/13 2:47 PM, christopher_dearb...@dell.com<mailto:christopher_dearb...@dell.com><mailto:christopher_dearb...@dell.com><mailto:christopher_dearb...@dell.com> wrote: Daniel, Glad to hear that you're past the Cinder issue! If you send along the logs from /var/log/quantum on the network node, I can take a look. Thanks, Chris Dell Inc From: crowbar-bounces On Behalf Of Daniel San Pedro Sent: Thursday, October 03, 2013 11:45 AM To: Jakesch, Simon Cc: crowbar; Jacob, Jacob Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal Good news! I was able to successfully apply the cinder barclamp: 1) I reinstalled the hardware (deleted it, booted via PXE, reinstalled OS via allocation) 2) I deactivated and deleted all the proposals 3) I performed the /opt/dell/bin/barclamp_install.rb cinder command 4) I recreated proposals and applied one at a time 5) Cinder installed fine according to the GUI (success message and light is green) I have run into another issue, however. Quantum now fails. I couldn't find a suitable log file with the error message (and I'm not sure which would be the right one), so I defer to you guys for guidance as to which log file I need to be looking at so that I may send you the error. Thanks once again. Daniel San Pedro Systems Administrator MCNA Dental Plans dsanpe...@mcna.net<mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net><mailto:dsanpe...@mcna.net> Office: (800) 494-6262 Ext. 203 ------------------------ CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you.
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
