Pavlo,I tried to deploy Ironic from Fuel 8.0 release (iso build fuel-community-8.0-83-2015-11-02_05-42-11)
4b1f91ad496c571e4cbc5931134db6479e582c8bAfter creating a fuel network-group as You suggested to Loic and configuring an Ironic deployment (4 nodes including controller, compute, cinder and Ironic) , I am getting an error during the deployment of firewall.pp on the controller node:
$$network_metadata["vips"]["baremetal"] is :undef, not a hash or array at /etc/puppet/modules/osnailyfacter/modular/firewall/firewall.pp:52 on node node-36.domain.tld
It seems the the vip for the baremetal network hasn't been created.Please note, I didn't deploy the Fuel-Plugin-Ironic Loic refers to (I tried it in 7.0, but it doesn't work anyway), but used the Ironic functionality available in 8.0.
Is there anyway I can make it work?? Best regards StanislawSubject: Re: [openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ? <http://markmail.org/message/uyw466nb5t6fmavu> permalink <http://markmail.org/message/uyw466nb5t6fmavu>
From: Pavlo Shchelokovskyy (pshc...@mirantis.com) Date: Oct 20, 2015 9:36:37 am List: org.openstack.lists.openstack-dev Hi Loic,the story of this plugin is a bit complicated. We've done it as PoC of integrating Ironic into Mirantis OpenStack/Fuel during 7.0 release. Currently we are working on integrating Ironic into core of Fuel targeting its 8.0 release. Given that, the plugin is not official in any sense, is not certified according to Fuel plugins guidelines, is not supported at all and has had only limited testing on a small in-house lab.
To successfully deploy Ironic with this plugin "as-is" you'd most probably need access to Mirantis package repositories as it relies on some patches to fuel-agent that we use for bootstrapping, and some of those are not merged yet, so we use repos created by our CI from Gerrit changes. Probably though you can hack on the code and disable such dependencies/building and uploading the custom bootstrap image, activate clear upstream Ironic drivers and then use upstream images with e.g. ironic-python-agent for bootstrapping baremetal nodes.
As to your network setup question - the baremetal network is somewhat similar to the public network in Fuel, which needs two ip ranges defined, one for service nodes, and the other for actual VMs to assign as floating ips. Thus networking setup for the plugin should be done as follows (naming it "baremetal" is mandatory):
fuel network-group --name baremetal --cidr 192.168.3.0/24 -c --nodegroup 1 --meta='{ip_range: ["192.168.3.2", "192.168.3.50"], notation: "ip_ranges"}'
where the ip range (I've put some example values) is for those service OpenStack nodes that host Ironic services and need to have access to this provider network where BM nodes do live (this range is then auto-filled to network.baremetal section of Networking settings tab in Fuel UI). The range for the actual BM nodes is defined then on the "Settings->Ironic" tab in Fuel UI once Ironic checkbox there is activated.
I admit we do need to make some effort and document the plugin a bit better (actually at all :) ) to not confuse people wishing to try it out.
Best regards, On Mon, Oct 19, 2015 at 6:45 AM, <loic...@orange.com> wrote: Hello,I’m currently searching for information about Ironic Fuel plugin : https://github.com/openstack/fuel-plugin-ironic I don’t find any documentation on it.
I’ve tried to install and deploy an Openstack environment with Fuel 7.0 and Ironic plugin but it failed. After adding ironic role to a node Fuel UI crashed, due to a missing network “baremetal” . When creating a network group
fuel network-group --create --node-group 1 --name \ "baremetal" --cidr 192.168.3.0/24UI works again, but I got some errors in the deployment, during network configuration. So I think I have to configure a network template, did someone already do this for this plugin ?
Regards, Loic_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informationsconfidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci. This message and its attachments may contain confidential or privilegedinformation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified. Thank you.__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: open...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--Dr. Pavlo Shchelokovskyy Senior Software Engineer Mirantis Inc www.mirantis.com
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: open...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<<attachment: sdalek.vcf>>
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
