https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Lucas+Alvares+Gomes&feedformat=atomOpenStack - User contributions [en]2024-03-29T02:33:05ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Meetings/InfraTeamMeeting&diff=182965Meetings/InfraTeamMeeting2023-04-04T15:39:00Z<p>Lucas Alvares Gomes: /* Upcoming Project Renames */</p>
<hr />
<div><br />
<!-- ## page was renamed from Meetings/CITeamMeeting --><br />
= Weekly Project Infrastructure team meeting =<br />
<br />
The OpenDev Team holds public weekly meetings in <code><nowiki>#opendev-meeting</nowiki></code> on OFTC, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.<br />
<br />
Please feel free to add agenda items (and your IRC nick in parenthesis).<br />
<br />
== Agenda for next meeting ==<br />
<br />
* Announcements<br />
<br />
* Actions from last meeting<br />
<br />
* Specs Review<br />
<br />
* Topics<br />
** Docker Hub Team shutdown (clarkb 20230404)<br />
*** Docker has decided not to follow through with their plan afterall<br />
**** I think we should continue as planned just with a bit less urgency (which is nice)<br />
*** https://review.opendev.org/q/topic:tag-deletion Changes to handle publication to registries generically.<br />
*** TODO need to implement promote from intermediate registry path or use tag deletion role.<br />
** Bastion host (ianw 20230404)<br />
*** https://review.opendev.org/q/topic:prod-bastion-group Remaining changes are part of parallel ansible runs on bridge<br />
*** https://review.opendev.org/q/topic:bridge-backups<br />
** Mailman 3 (clarkb 20230404)<br />
*** https://etherpad.opendev.org/p/mm3migration<br />
*** Need to change site domains<br />
** Gerrit Upgrade and Project Renames (ianw 20230404)<br />
*** Projects renames and Gerrit 3.7.2 upgrade April 6 at 22:00 UTC<br />
**** If we rename after upgrade then reindex for renames can happen online shortening downtime<br />
**** Are we comfortable relying on jeeypb's cache believing old project names are created in Gerrit preventing recreation?<br />
**** Has the 3.7 -> 3.6 revert path been tested?<br />
** Upgrading Bionic servers to Focal/Jammy (clarkb 20230404)<br />
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades<br />
*** Nameserver planning has begun<br />
**** https://review.opendev.org/q/topic:jammy-dns<br />
**** https://etherpad.opendev.org/p/2023-opendev-dns<br />
*** Static and etherpad replacements are in process https://review.opendev.org/q/topic:add-static02<br />
*** launch-env on bridge cannot list rax volumes<br />
*** reverse rax dns doesn't get automatically populated<br />
** AFS volume quotas and utilization (clarkb 20230404)<br />
*** Fedora 36 to be cleaned up in the near future.<br />
** Gitea 1.19 Upgrade (clarkb 20230404)<br />
*** Gitea 1.19.0 has been released<br />
*** https://review.opendev.org/c/opendev/system-config/+/877541 Upgrade opendev.org to 1.19.0<br />
** Quo vadis storyboard (frickler 20230404)<br />
*** ML thread https://lists.opendev.org/pipermail/service-discuss/2022-October/000370.html<br />
*** Some projects decided to move back to launchpad at the most recent PTG<br />
<br />
* Open discussion<br />
<br />
== Upcoming Project Renames ==<br />
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)<br />
Changes should have their topic set to project-rename.<br />
<br />
* Rename foo/example -> bar/example: https://review.opendev.org/123456<br />
* Rename x/xstatic-angular-fileupload->openstack/xstatic-angular-fileupload: https://review.opendev.org/c/openstack/project-config/+/873843<br />
* Rename x/virtualpdu -> openstack/virtualpdu https://review.opendev.org/c/openstack/project-config/+/876231<br />
* Rename x/ovn-bgp-agent -> openstack/ovn-bgp-agent https://review.opendev.org/c/openstack/project-config/+/879456<br />
<br />
== Previous meetings ==<br />
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=175012Networking-ovn2020-06-08T09:43:30Z<p>Lucas Alvares Gomes: Replaced content with "OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN."</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=172953Networking-ovn2019-11-01T14:40:57Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Port Forwarding || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || || Have a log file where security groups events are logged to be consumed by security department. Customer wants to have a way to check if an instance is trying to execute restricted operations or accessing restricted ports in remote servers.<br />
|-<br />
| Multicast support || || || Right now, multicast traffic is treated as broadcast when using ML2/OVN as the integration bridge is in FLOW mode so IGMP snooping is not available. In order to support this, core OVN must support IGMP snooping itself. This feature is on the roadmap but we don’t have a clear deadline, likely missing OVS 2.12 upstream release timeframe (mid Aug ‘19).<br />
|-<br />
| Baremetal Provisioning || || || Needs support for the "external ports" in core OVN. For iPXE the OVN DHCP server will need to be enhanced to be able to send different DHCP options based on the DHCP option 175<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-segment, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Fragmentation support / MTU mismatch || || || OVN does not yet support sending ICMP "fragmentation needed" packets so, larger ICMP/UDP packets that needs to be fragmented won't work as they would with the ML2/OVS driver implementation. TCP traffic should work due to the MSS mechanism however.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=172952Networking-ovn2019-11-01T14:39:53Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Port Forwarding || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || || Have a log file where security groups events are logged to be consumed by security department. Customer wants to have a way to check if an instance is trying to execute restricted operations or accessing restricted ports in remote servers.<br />
|-<br />
| Multicast support || || || Right now, multicast traffic is pretty much as broadcast when using ML2/OVN as the integration bridge is in FLOW mode so IGMP snooping is not available. In order to support this, core OVN must support IGMP snooping itself. This feature is on the roadmap but we don’t have a clear deadline, likely missing OVS 2.12 upstream release timeframe (mid Aug ‘19).<br />
|-<br />
| Baremetal Provisioning || || || Needs support for the "external ports" in core OVN. For iPXE the OVN DHCP server will need to be enhanced to be able to send different DHCP options based on the DHCP option 175<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-segment, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Fragmentation support / MTU mismatch || || || OVN does not yet support sending ICMP "fragmentation needed" packets so, larger ICMP/UDP packets that needs to be fragmented won't work as they would with the ML2/OVS driver implementation. TCP traffic should work due to the MSS mechanism however.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=168831Networking-ovn2019-03-14T14:30:31Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-segment, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Fragmentation support / MTU mismatch || || || OVN does not yet support sending ICMP "fragmentation needed" packets so, larger ICMP/UDP packets that needs to be fragmented won't work as they would with the ML2/OVS driver implementation. TCP traffic should work due to the MSS mechanism however.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=168828Networking-ovn2019-03-14T14:06:29Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-segment, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Fragmentation support || || || OVN does not yet support the sending ICMP "fragmentation needed" packets so, larger ICMP/UDP packets that needs to be fragmented won't work as they would with the ML2/OVS driver implementation. TCP traffic should work due to the MSS mechanism however.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166118Networking-ovn2018-10-19T12:46:00Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-segment, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Jumbo frames || || || OVN does not correctly support Jumbo frames for North/South traffic.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166117Networking-ovn2018-10-19T12:44:48Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Jumbo frames || || || OVN does not correctly support Jumbo frames for North/South traffic.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166116Networking-ovn2018-10-19T12:42:53Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|-<br />
| SRIOV || || || A limitation exists for this scenario where OVN needs to support VLAN tenant networks and Neutron DHCP Agent has to be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent.<br />
|-<br />
| Jumbo frames || || || OVN does not correctly support Jumbo frames for North/South traffic.<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166115Networking-ovn2018-10-19T12:41:07Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes. As a workaround Neutron DHCP Agent could be deployed. The goal is to include support in OVN to get rid of Neutron DHCP agent in the future.<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166114Networking-ovn2018-10-19T12:39:37Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || || The OVN built-in DHCP server currently can not be used to provision baremetal nodes<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=166112Networking-ovn2018-10-19T12:37:58Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Blueprint/Bug link !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| Per port DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || ||<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=165663Networking-ovn2018-10-09T12:13:51Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch !! Other<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || ||<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=162814Networking-ovn2018-07-17T08:36:31Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch !! Other<br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged) ||<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || ||<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|-<br />
| Security group logging || https://blueprints.launchpad.net/neutron/+spec/security-group-logging || ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161710Networking-ovn2018-06-07T12:39:45Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch !! Other<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || https://review.openstack.org/#/c/572782/ ||<br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged) ||<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/ ||<br />
|-<br />
| DHCP Options || || ||<br />
|-<br />
| Serving DHCP to a provider network || || ||<br />
|-<br />
| API extensions || || || Missing extensions are: agent, dhcp_agent_scheduler, empty-string-filtering, fip-port-details, flavors, ip-substring-filtering, l3-flavors, logging, metering, net-mtu-writable, qos, qos-fip, port-security-groups-filtering, segment, service-type, standard-attr-revisions, standard-attr-segment, standard-attr-timestamp, standard-attr-tag, trunk-details<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161702Networking-ovn2018-06-07T09:02:31Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || https://review.openstack.org/#/c/572782/<br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged)<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/<br />
|-<br />
| DHCP Options || TODO || <br />
|-<br />
| Serving DHCP to a provider network || TODO ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161639Networking-ovn2018-06-05T10:00:29Z<p>Lucas Alvares Gomes: /* List of features required in ML2/OVN to achieve feature parity with ML2/OVS */</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || <br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged)<br />
|-<br />
| Support FIP QoS || || https://review.openstack.org/#/c/539826/<br />
|-<br />
| DHCP Options || TODO || <br />
|-<br />
| Serving DHCP to a provider network || TODO ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161638Networking-ovn2018-06-05T09:58:49Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || <br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged)<br />
|-<br />
| DHCP Options || TODO || <br />
|-<br />
| Serving DHCP to a provider network || TODO ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161637Networking-ovn2018-06-05T09:58:26Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || <br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged)<br />
|-<br />
| DHCP Options || TODO || <br />
| Serving DHCP to a provider network || TODO ||<br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161636Networking-ovn2018-06-05T09:57:28Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.<br />
<br />
== List of features required in ML2/OVN to achieve feature parity with ML2/OVS ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! Bug ticket !! Code patch<br />
|-<br />
| Router port marked as DOWN || https://bugs.launchpad.net/networking-ovn/+bug/1715126 || <br />
|-<br />
| Agent APIs || https://bugs.launchpad.net/networking-ovn/+bug/1719574 || https://review.openstack.org/#/q/topic:agent_list+(status:open+OR+status:merged)<br />
|-<br />
| DHCP Options || TODO || <br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic&diff=161495Ironic2018-05-29T11:07:50Z<p>Lucas Alvares Gomes: /* Pixie Boots, the Ironic drummer bear */</p>
<hr />
<div>= OpenStack Bare Metal Provisioning Program =<br />
<br />
OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in order to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [https://docs.openstack.org/ironic/latest/user/index.html Introduction to Ironic].<br />
<br />
= Projects =<br />
<br />
Ironic is governed by the OpenStack Technical Committee. The complete list of deliverables (and associated tags) that are officially under the Ironic umbrella is available [http://governance.openstack.org/reference/projects/ironic.html here].<br />
<br />
Some of the deliverables (or projects) are described below.<br />
<br />
== ironic ==<br />
<br />
The '''ironic''' project includes the ironic-api and ironic-conductor processes.<br />
<br />
{| border="1" cellpadding="2"<br />
| Official name<br />
| '''OpenStack Bare Metal Provisioning'''<br />
|-<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/ironic<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/ironic/latest/<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/943<br />
|-<br />
| Feature tracker<br />
| https://storyboard.openstack.org/#!/project/943<br />
|-<br />
| Specifications<br />
| http://specs.openstack.org/openstack/ironic-specs<br />
|-<br />
| Weekly meetings<br />
| https://wiki.openstack.org/wiki/Meetings/Ironic<br />
|-<br />
| Testing<br />
| https://wiki.openstack.org/wiki/Ironic/Testing<br />
|-<br />
| Drivers<br />
| https://wiki.openstack.org/wiki/Ironic/Drivers<br />
|}<br />
<br />
== python-ironicclient ==<br />
<br />
'''python-ironicclient''' is a package that includes the python client and CLI.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/python-ironicclient<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/959<br />
|-<br />
| Feature tracker<br />
| https://storyboard.openstack.org/#!/project/959<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/python-ironicclient/latest/<br />
|}<br />
<br />
== ironic-python-agent ==<br />
<br />
'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/ironic-python-agent<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/947<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/ironic-python-agent/latest/<br />
|-<br />
| Wiki page<br />
| https://wiki.openstack.org/wiki/Ironic-python-agent<br />
|}<br />
<br />
== ironic-inspector ==<br />
<br />
'''ironic-inspector''' is a hardware introspection tool.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/ironic-inspector<br />
|-<br />
| Bug Tracker<br />
| https://storyboard.openstack.org/#!/project/944<br />
|-<br />
| Feature tracker<br />
| https://storyboard.openstack.org/#!/project/944<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/ironic-inspector/latest/<br />
|}<br />
<br />
== bifrost ==<br />
<br />
'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/bifrost<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/941<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/bifrost/latest/<br />
|}<br />
<br />
== networking-baremetal ==<br />
<br />
'''networking-baremetal''' is a Neutron plugin that covers bare metal use cases; it provides deep Ironic/Neutron integration.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/networking-baremetal<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/955<br />
|}<br />
<br />
== ironic-lib ==<br />
<br />
'''ironic-lib''' is a common library of functions used exclusively by the projects under the [http://governance.openstack.org/reference/projects/ironic.html Ironic governance].<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/ironic-lib<br />
|-<br />
| Bug tracker<br />
| https://storyboard.openstack.org/#!/project/946<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/ironic-lib/latest/<br />
|}<br />
<br />
== ironic-ui ==<br />
<br />
'''ironic-ui''' is a horizon plugin for ironic.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://git.openstack.org/cgit/openstack/ironic-ui<br />
|-<br />
| Bug Tracker<br />
| https://storyboard.openstack.org/#!/project/952<br />
|-<br />
| Documentation<br />
| https://docs.openstack.org/ironic-ui/latest/<br />
|}<br />
<br />
= People =<br />
<br />
'''PTL''': Julia Kreger (TheJulia)<br />
<br />
'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam<br />
<br />
'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons<br />
<br />
= Status =<br />
<br />
Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.<br />
<br />
Release notes for Ironic are available at http://docs.openstack.org/releasenotes/ironic/.<br />
<br />
Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing.<br />
<br />
For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI].<br />
<br />
= Etherpads =<br />
<br />
Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.<br />
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]<br />
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]<br />
<br />
= IRC =<br />
<br />
Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!<br />
<br />
= Developers =<br />
<br />
Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines<br />
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]<br />
<br />
<br />
= Pixie Boots, the Ironic drummer bear =<br />
<br />
Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [http://lucasgom.es Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.<br />
<br />
High-resolution PNGs versions are available by clicking on the images below:<br />
<br />
<gallery><br />
Ironic_mascot_color.png|Colored<br />
Ironic_mascot_outline.png|Outlined<br />
bear metal.svg|Icon<br />
</gallery><br />
<br />
You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]<br />
<br />
All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].<br />
<br />
Pixie Boots rockin': \m/ ʕ•͡ᴥ•ʔ \m/<br />
<br />
= Misc. =<br />
<br />
* [[Ironic/IPv6|Ironic + IPv6]]<br />
<br />
= Outside the OpenStack Bare Metal Provisioning Program =<br />
<br />
== Out-of-tree Ironic drivers ==<br />
<br />
Drivers that can be used with Ironic but that aren't in the [https://git.openstack.org/cgit/openstack/ironic ironic] repository, may be found in the [https://git.openstack.org/cgit/openstack/ironic-staging-drivers ironic-staging-drivers] repository.<br />
== Vendor-specific tools ==<br />
<br />
Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are not maintained by the ironic core team and are not under the governance of the OpenStack Technical Committee. Vendors themselves should be contacted for features requests/bug fixes.<br />
<br />
{| border="1" cellpadding="2"<br />
| Developer doc<br />
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc<br />
|-<br />
| List of third party vendor tools<br />
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList<br />
|}<br />
<br />
<br />
[[category: baremetal]]<br />
[[category: ironic]]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Networking-ovn&diff=161435Networking-ovn2018-05-24T14:29:26Z<p>Lucas Alvares Gomes: Created page with "OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN."</p>
<hr />
<div>OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=152480Meetings/Ironic2017-03-20T16:48:59Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
<br />
The next meeting will be on March 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170320T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
** ironic-{core, release} groups were added to sushy-{core, release} groups respectively now that we decided to have it under the ironic umbrella! Happy hacking :D<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Deciding on priorities for the coming week<br />
** Stuck specs for current and potential priorities<br />
** Appointing a bug liaison for the next week<br />
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
* RFE review<br />
* Open discussion<br />
** Some interesting information https://bugs.launchpad.net/ironic/+bug/1672457 (mjturek)<br />
** Having one or two config properties for SSL cert verification in the redfish driver: https://review.openstack.org/#/c/438982/11/ironic/drivers/modules/redfish/utils.py ; see comment at L48 (lucasagomes)<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV<br />
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=152472Meetings/Ironic2017-03-20T12:29:13Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Dmitry Tantsur (dtantsur), Jim Rollenhagen (jroll), and Julia Kreger (TheJulia).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
<br />
The next meeting will be on March 20, 2017 at 1700 UTC (https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170320T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
** ironic-{core, release} groups were added to sushy-{core, release} groups respectively now that we decided to have it under the ironic umbrella! Happy hacking :D<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Deciding on priorities for the coming week<br />
** Stuck specs for current and potential priorities<br />
** Appointing a bug liaison for the next week<br />
* Specs that are stuck on contentious items. (This is NOT for specs that are stuck because they aren't getting reviews.)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
* RFE review<br />
* Open discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* Boot From Volume meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-BFV<br />
* UI meeting: https://wiki.openstack.org/wiki/Meetings/Ironic-ui</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=133916Meetings/Ironic2016-09-28T13:59:58Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
<br />
The next meeting will be on October 3, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161003T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
** (jroll) discuss proposed summit session ideas: https://etherpad.openstack.org/p/ironic-ocata-summit<br />
** (lucasagomes) Whole disk image inconsistency between pxe_* and agent_* drivers. Which approach to take ? (See comments at https://review.openstack.org/#/c/375481/)<br />
* RFE review<br />
* Open discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic_v2_API Ironic v2 API workgroup meets weekly on Tuesdays at 1800 UTC.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=132508Meetings/Ironic2016-09-05T15:45:15Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
<br />
The next meeting might be on September 12, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160905T1700). It is a holiday in US and Canada; if not enough people show up, the meeting will be cancelled.<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
* RFE review<br />
* Open discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic_v2_API Ironic v2 API workgroup meets weekly on Tuesdays at 1800 UTC.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=128994Meetings/Ironic2016-07-25T14:21:11Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
<br />
The next meeting will be on July 25, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160725T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
** ironic officially supports-upgrade and follows-standard-deprecation (https://review.openstack.org/340335)<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
# Alternatives for the proposed approach at https://review.openstack.org/#/c/331564/11/specs/approved/boot-params.rst (lucasagomes)<br />
* RFE review<br />
* Open discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic_v2_API Ironic v2 API workgroup meets weekly on Tuesdays at 1800 UTC.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/IPv6&diff=127073Ironic/IPv62016-06-21T09:43:42Z<p>Lucas Alvares Gomes: /* Ironic and IPv6 */</p>
<hr />
<div>{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0.5em; background-color:#FABFBF;"<br />
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]<br />
| '''Warning''' | <br />
'''This page is just a vision statement, so do not trust it fully, I (lucasagomes) haven't got Ironic yet working with IPv6.'''<br />
|}<br />
<br />
== Ironic and IPv6 ==<br />
<br />
<big>Here are the things to consider when thinking about Ironic and IPv6:</big><br />
<br />
<br />
==== PXE Boot ====<br />
<br />
According to Intel ([http://www.intel.com/support/network/sb/CS-028553.htm link]) it seems that IPv6 for PXE boot is only supported when used with UEFI.<br />
<br />
iPXE on the other hand does support IPv6 already* ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html link]), but that kinda means that we need to have iPXE flashed in the NIC ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html see]) otherwise we would still need IPv4 to fetch the iPXE ROM from the TFTP server and chain load it.<br />
<br />
NOTE: iPXE doesn't seem to enable IPv6 by default, this is done by downloading the iPXE source from http://ipxe.org/download and then changing the NET_PROTO_IPV6 configuration in src/config/general.h defining (s/#undef/#define) NET_PROTO_IPV6.<br />
<br />
==== IPMI ====<br />
<br />
Configuring the OOBM with IPv6 seems to be vendor specific ([http://ipvsix.me/?p=159 see]), would be good to have a table here mapping which vendor, hardware model and firmware version does support it.<br />
<br />
<br />
==== Neutron ====<br />
<br />
Neutron seems to be fine with IPv6, apparently we only need to change Ironic to be able to specify the IP version when we pass the extra DHCP options to Neutron ([https://blueprints.launchpad.net/neutron/+spec/extra-dhcp-opts-ipv4-ipv6 link]).<br />
<br />
'''UPDATE''': Added a patch to be able to specify the IP version when passing the extra DHCP options to Neutron in Ironic ([https://review.openstack.org/231573 see])<br />
<br />
<br />
==== TFTP ====<br />
<br />
A quick look at xinetd and it seems that it supports IPv6 already ([http://www.embeddedsystemtesting.com/2012/10/how-to-enable-tftp-server-in-fedora.html link])<br />
<br />
== Other references ==<br />
<br />
* https://blog.toreanderson.no/2015/11/16/ipv6-network-boot-with-uefi-and-ipxe.html<br />
<br />
== Random thoughts ==<br />
<br />
IPv6 was created to solve a address space problem, it's very unlikely that we will ever hit that in a provision network so I would still recommend people wanting to run IPv6 to first consider having a dual-stack IPv6-IPv4 networking where IPv4 is used for the provisioning network.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/IPv6&diff=127072Ironic/IPv62016-06-21T09:37:41Z<p>Lucas Alvares Gomes: /* Ironic and IPv6 */</p>
<hr />
<div>{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0.5em; background-color:#FABFBF;"<br />
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]<br />
| '''Warning''' | <br />
'''This page is just a vision statement, so do not trust it fully, I (lucasagomes) haven't got Ironic yet working with IPv6.'''<br />
|}<br />
<br />
== Ironic and IPv6 ==<br />
<br />
<big>Here are the things to consider when thinking about Ironic and IPv6:</big><br />
<br />
<br />
==== PXE Boot ====<br />
<br />
According to Intel ([http://www.intel.com/support/network/sb/CS-028553.htm link]) it seems that IPv6 for PXE boot is only supported when used with UEFI.<br />
<br />
iPXE on the other hand does support IPv6 already* ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html link]), but that kinda means that we need to have iPXE flashed in the NIC ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html see]) otherwise we would still need IPv4 to fetch the iPXE ROM from the TFTP server and chain load it.<br />
<br />
NOTE: iPXE doesn't seem to enable IPv6 by default, this is done by downloading the iPXE source from http://ipxe.org/download and then changing the NET_PROTO_IPV6 configuration in src/config/general.h defining (s/#undef/#define) NET_PROTO_IPV6.<br />
<br />
==== IPMI ====<br />
<br />
Configuring the OOBM with IPv6 seems to be vendor specific ([http://ipvsix.me/?p=159 see]), would be good to have a table here mapping which vendor, hardware model and firmware version does support it.<br />
<br />
<br />
==== Neutron ====<br />
<br />
Neutron seems to be fine with IPv6, apparently we only need to change Ironic to be able to specify the IP version when we pass the extra DHCP options to Neutron ([https://blueprints.launchpad.net/neutron/+spec/extra-dhcp-opts-ipv4-ipv6 link]).<br />
<br />
'''UPDATE''': Added a patch to be able to specify the IP version when passing the extra DHCP options to Neutron in Ironic ([https://review.openstack.org/231573 see])<br />
<br />
<br />
==== TFTP ====<br />
<br />
A quick look at xinetd and it seems that it supports IPv6 already ([http://www.embeddedsystemtesting.com/2012/10/how-to-enable-tftp-server-in-fedora.html link])<br />
<br />
== Random thoughts ==<br />
<br />
IPv6 was created to solve a address space problem, it's very unlikely that we will ever hit that in a provision network so I would still recommend people wanting to run IPv6 to first consider having a dual-stack IPv6-IPv4 networking where IPv4 is used for the provisioning network.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=File:Bear_metal_white.svg&diff=125261File:Bear metal white.svg2016-05-13T14:34:03Z<p>Lucas Alvares Gomes: </p>
<hr />
<div></div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=IronicStagingDrivers&diff=103100IronicStagingDrivers2016-02-04T11:37:14Z<p>Lucas Alvares Gomes: Created page with "= Driver maintainers = {| class="wikitable" |- ! Driver Name !! Description !! Primary Contact Email and IRC handle |- | pxe_foo || blah blah blah || lucasagomes <lucasagomes..."</p>
<hr />
<div>= Driver maintainers =<br />
<br />
{| class="wikitable"<br />
|-<br />
! Driver Name !! Description !! Primary Contact Email and IRC handle<br />
|-<br />
| pxe_foo || blah blah blah || lucasagomes <lucasagomes@gmail.com><br />
|}</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=101453Meetings/Ironic2016-01-18T16:41:58Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Jim Rollenhagen (jroll), Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''' to give folks time to get context, and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion. Requests to have a patch reviewed should not be a topic and instead should be covered during the Open Discussion portion of the meeting.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting will be on January 18, 2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160118T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Stuck specs (Specs that are stuck on contentious items. This is NOT for specs that are stuck because they aren't getting reviews.)<br />
** Node's tags optimization should we do it or not ? https://review.openstack.org/#/c/253748/ (lucasagomes)<br />
* Discussion (Requests to have your patch reviewed should not be a 'Discussion' topic. If desired, please discuss during 'Open Discussion')<br />
* Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
* [https://wiki.openstack.org/wiki/Meetings/Ironic-QA Ironic-QA meets weekly on Wednesdays at 1700 UTC.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic&diff=91835Ironic2015-10-06T16:26:26Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>= OpenStack Bare Metal Provisioning Program =<br />
<br />
OpenStack bare metal provisioning a.k.a '''Ironic''' is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. For a general overview please see: [http://docs.openstack.org/developer/ironic/deploy/user-guide.html Introduction to Ironic].<br />
<br />
= Projects =<br />
<br />
== ironic ==<br />
<br />
The '''ironic''' project includes the ironic-api and ironic-conductor processes.<br />
<br />
{| border="1" cellpadding="2"<br />
| Official name<br />
| '''OpenStack Bare Metal Provisioning'''<br />
|-<br />
| Source code<br />
| https://github.com/openstack/ironic<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/ironic/<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/ironic<br />
|-<br />
| Specifications<br />
| http://specs.openstack.org/openstack/ironic-specs<br />
|-<br />
| Weekly meetings<br />
| https://wiki.openstack.org/wiki/Meetings/Ironic<br />
|-<br />
| Testing<br />
| https://wiki.openstack.org/wiki/Ironic/Testing<br />
|-<br />
| Drivers<br />
| https://wiki.openstack.org/wiki/Ironic/Drivers<br />
|}<br />
<br />
== python-ironicclient ==<br />
<br />
'''python-ironicclient''' is a package that includes the python client and CLI.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/python-ironicclient<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/python-ironicclient<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/python-ironicclient<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/python-ironicclient<br />
|}<br />
<br />
== ironic-python-agent ==<br />
<br />
'''ironic-python-agent''' is a small python application that is meant to be embedded in a deployment ramdisk.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-python-agent<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic tag: "agent"<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/ironic-python-agent<br />
|-<br />
| Wiki page<br />
| https://wiki.openstack.org/wiki/Ironic-python-agent<br />
|}<br />
<br />
== pyghmi ==<br />
<br />
'''pyghmi''' is an alternative to IPMItool.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/stackforge/pyghmi<br />
|}<br />
<br />
== ironic-inspector ==<br />
<br />
'''ironic-inspector''' is a hardware introspection tool.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-inspector<br />
|-<br />
| Bug Tracker<br />
| https://bugs.launchpad.net/ironic-inspector/<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/ironic-inspector/<br />
|}<br />
<br />
== bifrost ==<br />
<br />
'''bifrost''' consists of Ansible play books for running Ironic standalone (without other OpenStack components).<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/bifrost<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/bifrost<br />
|}<br />
<br />
== ironic-lib ==<br />
<br />
'''ironic-lib''' is a common library of functions used by the other ironic projects.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-lib<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic-lib<br />
|}<br />
<br />
== ironic-webclient ==<br />
<br />
'''ironic-webclient''' is a webclient for OpenStack Ironic.<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-webclient<br />
|}<br />
<br />
== other vendor-specific tools ==<br />
<br />
Third-party vendors are encouraged to share their tools/scripts which might help people using their hardware with '''ironic'''. These tools are as such are not maintained by the ironic core team, and vendors themselves should be contacted for features requests/bug fixes.<br />
<br />
{| border="1" cellpadding="2"<br />
| Developer doc<br />
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsDeveloperDoc<br />
|-<br />
| List of third party vendor tools<br />
| https://wiki.openstack.org/wiki/Ironic/ThirdPartyVendorToolsList<br />
|}<br />
<br />
= People =<br />
<br />
'''PTL''': Devananda van der Veen (devananda)<br />
<br />
'''Core teams''': https://wiki.openstack.org/wiki/Ironic/CoreTeam<br />
<br />
'''Cross-project liaisons''': https://wiki.openstack.org/wiki/CrossProjectLiaisons<br />
<br />
= Status =<br />
<br />
Ironic was first available as an incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic completed the project graduation review at the end of the "Juno" cycle, and began "Kilo" development cycle as an officially integrated OpenStack project.<br />
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse<br />
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
* Kilo, 2015.1: https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Bare_Metal_service_.28Ironic.29<br />
<br />
<br />
Information on the latest status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing<br />
<br />
For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]<br />
<br />
= Etherpads =<br />
<br />
Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.<br />
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]<br />
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]<br />
<br />
= IRC =<br />
<br />
Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net. This is a great place to jump in and start your ironic adventure. The channel is very welcoming to new users - no question is a wrong question!<br />
<br />
= Developers =<br />
<br />
Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines<br />
Please note that for any non-trivial change that is not a fix for a particular bug, you have to go through the [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]<br />
<br />
<br />
= Pixie Boots, the Ironic drummer bear =<br />
<br />
Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. An icon shadowcut of pixie boots is also available, courtesy of [https://plus.google.com/u/0/+MichaelKrotscheck Michael Krotscheck]. Feel free to use the images to make t-shirts or any other paraphernalia.<br />
<br />
High-resolution PNGs versions are available by clicking on the images below:<br />
<br />
<gallery><br />
Ironic_mascot_color.png|Colored<br />
Ironic_mascot_outline.png|Outlined<br />
bear metal.svg|Icon<br />
</gallery><br />
<br />
You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]<br />
<br />
All images are licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].<br />
<br />
<br />
= Misc. =<br />
<br />
* [[Ironic/IPv6|Ironic + IPv6]]<br />
<br />
<br />
[[category: baremetal]]<br />
[[category: ironic]]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/IPv6&diff=91834Ironic/IPv62015-10-06T16:22:02Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0.5em; background-color:#FABFBF;"<br />
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]<br />
| '''Warning''' | <br />
'''This page is just a vision statement, so do not trust it fully, I (lucasagomes) haven't got Ironic yet working with IPv6.'''<br />
|}<br />
<br />
== Ironic and IPv6 ==<br />
<br />
<big>Here are the things to consider when thinking about Ironic and IPv6:</big><br />
<br />
<br />
==== PXE Boot ====<br />
<br />
According to Intel ([http://www.intel.com/support/network/sb/CS-028553.htm link]) it seems that IPv6 for PXE boot is only supported when used with UEFI.<br />
<br />
iPXE on the other hand does support IPv6 already ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html link]), but that kinda means that we need to have iPXE flashed in the NIC ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html see]) otherwise we would still need IPv4 to fetch the iPXE ROM from the TFTP server and chain load it.<br />
<br />
<br />
==== IPMI ====<br />
<br />
Configuring the OOBM with IPv6 seems to be vendor specific ([http://ipvsix.me/?p=159 see]), would be good to have a table here mapping which vendor, hardware model and firmware version does support it.<br />
<br />
<br />
==== Neutron ====<br />
<br />
Neutron seems to be fine with IPv6, apparently we only need to change Ironic to be able to specify the IP version when we pass the extra DHCP options to Neutron ([https://blueprints.launchpad.net/neutron/+spec/extra-dhcp-opts-ipv4-ipv6 link]).<br />
<br />
'''UPDATE''': Added a patch to be able to specify the IP version when passing the extra DHCP options to Neutron in Ironic ([https://review.openstack.org/231573 see])<br />
<br />
<br />
==== TFTP ====<br />
<br />
A quick look at xinetd and it seems that it supports IPv6 already ([http://www.embeddedsystemtesting.com/2012/10/how-to-enable-tftp-server-in-fedora.html link])<br />
<br />
<br />
== Random thoughts ==<br />
<br />
IPv6 was created to solve a address space problem, it's very unlikely that we will ever hit that in a provision network so I would still recommend people wanting to run IPv6 to first consider having a dual-stack IPv6-IPv4 networking where IPv4 is used for the provisioning network.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/IPv6&diff=91832Ironic/IPv62015-10-06T16:16:41Z<p>Lucas Alvares Gomes: Created page with "{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0.5em; background-color:#FABFBF;" | style="padding:1em;width: 40px" | 40px..."</p>
<hr />
<div>{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0.5em; background-color:#FABFBF;"<br />
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]<br />
| '''Warning''' | <br />
'''This page is just a vision statement, so do not trust it fully, I (lucasagomes) haven't got Ironic yet working with IPv6.'''<br />
|}<br />
<br />
== Ironic and IPv6 ==<br />
<br />
<big>Here are the things to consider when thinking about Ironic and IPv6:</big><br />
<br />
<br />
==== PXE Boot ====<br />
<br />
According to Intel ([http://www.intel.com/support/network/sb/CS-028553.htm link]) it seems that IPv6 for PXE boot is only supported when used with UEFI.<br />
<br />
iPXE on the other hand does support IPv6 already ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html link]), but that kinda means that we need to have iPXE flashed in the NIC ([http://lists.ipxe.org/pipermail/ipxe-devel/2014-September/003752.html see]) otherwise we would still need IPv4 to fetch the iPXE ROM from the TFTP server and chain load it.<br />
<br />
<br />
==== IPMI ====<br />
<br />
Configuring the OOBM with IPv6 seems to be vendor specific ([http://ipvsix.me/?p=159 see]), would be good to have a table here mapping which vendor, hardware model and firmware version does support it.<br />
<br />
<br />
==== Neutron ====<br />
<br />
Neutron seems to be fine with IPv6, apparently we only need to change Ironic to be able to specify the IP version when we pass the extra DHCP options to Neutron ([https://blueprints.launchpad.net/neutron/+spec/extra-dhcp-opts-ipv4-ipv6 link]).<br />
<br />
'''UPDATE''': Added a patch to be able to specify the IP version when passing the extra DHCP options to Neutron in Ironic ([https://review.openstack.org/231573 see])<br />
<br />
<br />
==== TFTP ====<br />
<br />
A quick look at xinetd and it seems that it supports IPv6 already ([http://www.embeddedsystemtesting.com/2012/10/how-to-enable-tftp-server-in-fedora.html link])<br />
<br />
<br />
== Random thoughts ==<br />
<br />
IPv6 was created to solve a address space problem, it's very unlikely that we will ever hit that in a provision network so I would still recommend people wanting to run IPv6 to first consider having a dual-stack IPv6-IPv4 networking where, IPv4 still being used for their provisioning network.</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/Drivers&diff=90456Ironic/Drivers2015-09-17T09:50:32Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>== Drivers ==<br />
<br />
Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the [http://docs.openstack.org/developer/ironic/dev/architecture.html#drivers system architecture] description.<br />
<br />
Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity of a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the [[Ironic/Testing]] wiki page.<br />
<br />
Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints. Here is a list of known out-of-tree drivers:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Comments<br />
|-<br />
| Cisco UCS || https://communities.cisco.com/docs/DOC-56373<br />
|-<br />
| HP OneView || https://github.com/HewlettPackard/ironic-driver-oneview || This is a preview version that works within Kilo release. Upcoming versions are being developed in-tree.<br />
|}<br />
<br />
The table below describes the CI test coverage of the current set of drivers. Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested together, but we are striving to get test coverage for each interface in at least one driver. <br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Interface Type !! Interface Name !! Test coverage provided by driver name<br />
|-<br />
| deploy || agent || agent_ssh; agent_ipmitool is used in production for Rackspace OnMetal<br />
|-<br />
| deploy || pxe || pxe_ssh<br />
|-<br />
| deploy || iscsi || none<br />
|-<br />
| power || drac || None<br />
|-<br />
| power || ilo || None<br />
|-<br />
| power || ipminative || pxe_ipminative (provided by ibm-xcat-ci)<br />
|-<br />
| power || ipmitool || ** most widely used power driver in production, but lacks upstream CI<br />
|-<br />
| power || seamicro || None<br />
|-<br />
| power || snmp || None<br />
|-<br />
| power || ssh || pxe_ssh<br />
|-<br />
| power || amt|| None<br />
|-<br />
| power || irmc|| None<br />
|-<br />
| power || iboot || None<br />
|-<br />
| power || virtualbox || None<br />
|-<br />
| power || Wake-On-Lan || None<br />
|}<br />
<br />
<br />
Links to graphs of the CI system's current status should be included in the table below, when available.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Driver Name !! Primary Contact Email and IRC handle !! Testing Status<br />
|-<br />
| pxe_ssh || devananda (devananda dot vdv at gmail) / lucasagomes (lucasagomes at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]<br />
|-<br />
| pxe_ipminative || Yuan Y Bai <bybai at cn dot ibm dot com> / Long LA Cheng <chenglch at cn dot ibm dot com> / Jarrod Johnson (jjohnson2 at lenovo dot com) || Third-party CI: "ibm-xcat-ci" <xcat@cn.ibm.com><br />
|-<br />
| pxe_ipmitool || devananda (devananda dot vdv at gmail) / lucasagomes (lucasagomes at gmail) || used by TripleO, but not CI tested<br />
|-<br />
| agent_ssh || jroll (jim at jimrollenhagen dot com) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]<br />
|-<br />
| agent_ipmitool || jroll (jim at jimrollenhagen dot com) || used by Rackspace OnMetal, not CI tested upstream<br />
|-<br />
| PXEDracDriver || cdearborn Christopher Dearborn (Christopher_Dearborn at dell dot com) || Not CI tested<br />
|-<br />
| pxe_ipa || lucasagomes (lucasagomes at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]<br />
|}<br />
<br />
== 3rd Party Drivers ==<br />
<br />
iLO drivers: https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/Drivers&diff=89222Ironic/Drivers2015-08-31T21:39:21Z<p>Lucas Alvares Gomes: /* Drivers */</p>
<hr />
<div>== Drivers ==<br />
<br />
Ironic supports pluggable back-end drivers for different types of hardware to enable features specific to unique hardware platforms and leverage divergent capabilities via a common API . This API is divided into three sections: core, common, and vendor. While authors of vendor drivers may break new ground in the designated "vendor_passthru" section of the API, they are strongly encouraged to converge on a common API across vendors. More details may be found under the [http://docs.openstack.org/developer/ironic/dev/architecture.html#drivers system architecture] description.<br />
<br />
Hardware drivers must undergo CI testing so as to ensure their continued functionality. Some drivers will be tested upstream, while many will require third-party CI testing due to the unique nature of their hardware (and the unmanageable complexity of a single team required to maintain a test infrastructure encompassing hardware from many diverse vendors). Guidelines on that testing can be found on the [[Ironic/Testing]] wiki page.<br />
<br />
Out-of-tree drivers are supported by Ironic and may be loaded via python entrypoints. Here is a list of known out-of-tree drivers:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link<br />
|-<br />
| Cisco UCS || https://communities.cisco.com/docs/DOC-56373<br />
|}<br />
<br />
The table below describes the CI test coverage of the current set of drivers. Note that drivers are composed of more than one interface (eg, power and deploy). Not all combinations of interfaces are necessarily tested together, but we are striving to get test coverage for each interface in at least one driver. <br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Interface Type !! Interface Name !! Test coverage provided by driver name<br />
|-<br />
| deploy || agent || agent_ssh; agent_ipmitool is used in production for Rackspace OnMetal<br />
|-<br />
| deploy || pxe || pxe_ssh<br />
|-<br />
| deploy || iscsi || none<br />
|-<br />
| power || drac || None<br />
|-<br />
| power || ilo || None<br />
|-<br />
| power || ipminative || pxe_ipminative (provided by ibm-xcat-ci)<br />
|-<br />
| power || ipmitool || ** most widely used power driver in production, but lacks upstream CI<br />
|-<br />
| power || seamicro || None<br />
|-<br />
| power || snmp || None<br />
|-<br />
| power || ssh || pxe_ssh<br />
|-<br />
| power || amt|| None<br />
|-<br />
| power || irmc|| None<br />
|-<br />
| power || iboot || None<br />
|-<br />
| power || virtualbox || None<br />
|-<br />
| power || Wake-On-Lan || None<br />
|}<br />
<br />
<br />
Links to graphs of the CI system's current status should be included in the table below, when available.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Driver Name !! Primary Contact Email and IRC handle !! Testing Status<br />
|-<br />
| pxe_ssh || devananda (devananda dot vdv at gmail) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]<br />
|-<br />
| pxe_ipminative || Yuan Y Bai <bybai at cn dot ibm dot com> / Long LA Cheng <chenglch at cn dot ibm dot com> / Jarrod Johnson (jjohnson2 at lenovo dot com) || Third-party CI: "ibm-xcat-ci" <xcat@cn.ibm.com><br />
|-<br />
| pxe_ipmitool || devananda (devananda dot vdv at gmail) || used by TripleO, but not CI tested<br />
|-<br />
| agent_ssh || jroll (jim at jimrollenhagen dot com) || [http://no-carrier.net/~adam/openstack/ironic_gate_status.html tested in the upstream gate]<br />
|-<br />
| agent_ipmitool || jroll (jim at jimrollenhagen dot com) || used by Rackspace OnMetal, not CI tested upstream<br />
|-<br />
| PXEDracDriver || cdearborn Christopher Dearborn (Christopher_Dearborn at dell dot com) || Not CI tested<br />
|}<br />
<br />
== 3rd Party Drivers ==<br />
<br />
iLO drivers: https://wiki.openstack.org/wiki/Ironic/Drivers/iLODrivers</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=88154Meetings/Ironic2015-08-17T15:22:46Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting will be on August 17, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150817T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Scripts / add-ons that do not fit into Ironic or it's repo (NobodyCam)<br />
* Patches only adding copyright (see https://review.openstack.org/212973)<br />
* Is 25 characters enough for the driver's name? (see https://review.openstack.org/#/c/209605/) <br />
**Proposed: create a Wiki page list that links to repositories from those contributing the items to open source, however those items are not maintained by the Ironic community.<br />
<br />
* Open Discussion<br />
** Deleting instances at any stage of the deployment. Ideas about how to use the target_provision_state field ? (see deva's comment at https://review.openstack.org/#/c/204162/11)<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
<br />
== Future Meetings ==<br />
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).<br />
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).<br />
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).<br />
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).<br />
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).<br />
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).<br />
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).<br />
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).<br />
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).<br />
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).<br />
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).<br />
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).<br />
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).<br />
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).<br />
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).<br />
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).<br />
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).<br />
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).<br />
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).<br />
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).<br />
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).<br />
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).<br />
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).<br />
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).<br />
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).<br />
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).<br />
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).<br />
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).<br />
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).<br />
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=88153Meetings/Ironic2015-08-17T15:13:34Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting will be on August 17, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150817T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Scripts / add-ons that do not fit into Ironic or it's repo (NobodyCam)<br />
* Patches only adding copyright (see: https://review.openstack.org/212973)<br />
**Proposed: create a Wiki page list that links to repositories from those contributing the items to open source, however those items are not maintained by the Ironic community.<br />
<br />
* Open Discussion<br />
** Deleting instances at any stage of the deployment. Ideas about how to use the target_provision_state field ? (see deva's comment at https://review.openstack.org/#/c/204162/11)<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
<br />
== Future Meetings ==<br />
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).<br />
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).<br />
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).<br />
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).<br />
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).<br />
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).<br />
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).<br />
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).<br />
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).<br />
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).<br />
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).<br />
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).<br />
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).<br />
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).<br />
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).<br />
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).<br />
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).<br />
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).<br />
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).<br />
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).<br />
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).<br />
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).<br />
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).<br />
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).<br />
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).<br />
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).<br />
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).<br />
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).<br />
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).<br />
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=88133Meetings/Ironic2015-08-17T09:10:22Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! The one-hour weekly meetings start at 1700 UTC on Mondays, are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda van der Veen (devananda) or Chris Krelle (NobodyCam).<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
* [http://eavesdrop.openstack.org/calendars/ironic-bare-metal-team-meeting.ics ICS (Calendar) file] for the meeting. You can add this to your calendar.<br />
* [http://eavesdrop.openstack.org/#Ironic_%28Bare_Metal%29_Team_Meeting Eavesdrop meeting page]<br />
<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting will be on August 17, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150817T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Scripts / add-ons that do not fit into Ironic or it's repo (NobodyCam)<br />
* Patches only adding copyright (see: https://review.openstack.org/212973)<br />
**Proposed: create a Wiki page list that links to repositories from those contributing the items to open source, however those items are not maintained by the Ironic community.<br />
<br />
* Open Discussion<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
<br />
== Future Meetings ==<br />
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).<br />
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).<br />
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).<br />
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).<br />
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).<br />
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).<br />
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).<br />
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).<br />
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).<br />
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).<br />
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).<br />
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).<br />
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).<br />
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).<br />
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).<br />
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).<br />
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).<br />
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).<br />
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).<br />
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).<br />
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).<br />
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).<br />
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).<br />
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).<br />
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).<br />
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).<br />
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).<br />
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).<br />
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).<br />
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=85393Meetings/Ironic2015-07-08T10:42:17Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).<br />
<br />
The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
An ''unofficial'' Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&amp;showCalendars=0&amp;mode=WEEK&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&amp;color=%235229A3 Google Calendar] This calendar may only show things for the Pacific Time Zone :(<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting will be July13, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150713T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
** [BadCub] - Catering for Mid-Cycle - HP will cater lunch for the mid-cycle. Please use the following form to advise of food restrictions/allergies. http://goo.gl/forms/Zvts5VwWEV<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* API: Not all Conflicts (409) should be retry-able - https://bugs.launchpad.net/ironic/+bug/1472565<br />
* Open Discussion<br />
**<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]<br />
<br />
== Related meetings ==<br />
<br />
[https://wiki.openstack.org/wiki/Meetings/Ironic-neutron Ironic/Neutron integration meets weekly on Monday at 1600 UTC.]<br />
<br />
== Future Meetings ==<br />
* Meeting on 29-June-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150629T1700).<br />
* Meeting on 7-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150707T0500).<br />
* Meeting on 13-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150713T1700).<br />
* Meeting on 21-July-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150721T0500).<br />
* Meeting on 27-July-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150727T1700).<br />
* Meeting on 4-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150804T0500).<br />
* Meeting on 10-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150810T1700).<br />
* Meeting on 18-August-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150818T0500).<br />
* Meeting on 24-August-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150824T1700).<br />
* Meeting on 1-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150901T0500).<br />
* Meeting on 7-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T1700).<br />
* Meeting on 15-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150915T0500).<br />
* Meeting on 21-September-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150921T1700).<br />
* Meeting on 29-September-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150929T0500).<br />
* Meeting on 5-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151005T1700).<br />
* Meeting on 13-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151013T0500).<br />
* Meeting on 19-October-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151019T1700).<br />
* Meeting on 27-October-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151027T0500).<br />
* Meeting on 2-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151102T1700).<br />
* Meeting on 10-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151110T0500).<br />
* Meeting on 16-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151116T1700).<br />
* Meeting on 24-November-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151124T0500).<br />
* Meeting on 30-November-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151130T1700).<br />
* Meeting on 8-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151208T0500).<br />
* Meeting on 14-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151214T1700).<br />
* Meeting on 22-December-2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151222T0500).<br />
* Meeting on 28-December-2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151228T1700).<br />
* Meeting on 5-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160105T0500).<br />
* Meeting on 11-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160111T1700).<br />
* Meeting on 19-January-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160119T0500).<br />
* Meeting on 25-January-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160125T1700).<br />
* Meeting on 2-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160202T0500).<br />
* Meeting on 8-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160208T1700).<br />
* Meeting on 16-February-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160216T0500).<br />
* Meeting on 22-February-2016 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160222T1700).<br />
* Meeting on 1-March-2016 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160301T0500).</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=80438Meetings/Ironic2015-05-06T08:37:02Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).<br />
<br />
The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
A Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&amp;showCalendars=0&amp;mode=WEEK&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&amp;color=%235229A3&amp;ctz=America%2FLos_Angeles Google Calendar]<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting is scheduled for May 12th, 2015 at 0500 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150512T0500).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
* Summit planning [https://etherpad.openstack.org/p/liberty-ironic-design-summit-ideas etherpad]<br />
* Large number of ironic driver bugs in nova (Do we need a liaison to keep an eye on the Nova bugs associated with Ironic?) http://lists.openstack.org/pipermail/openstack-dev/2015-May/063365.html<br />
* Open Discussion<br />
**<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=78540Meetings/Ironic2015-04-29T14:08:04Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).<br />
<br />
The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
A Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&amp;showCalendars=0&amp;mode=WEEK&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&amp;color=%235229A3&amp;ctz=America%2FLos_Angeles Google Calendar]<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting is scheduled for May 4th, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150504T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
<br />
* Open Discussion<br />
**<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Meetings/Ironic&diff=78537Meetings/Ironic2015-04-29T13:55:17Z<p>Lucas Alvares Gomes: /* Agenda for next meeting */</p>
<hr />
<div>= Weekly Ironic Project Team Meeting =<br />
<br />
If you're interested in bare metal deployments within OpenStack, please join our weekly discussion about the [[Ironic|Ironic project]]! Meetings are held in the <code><nowiki>#openstack-meeting-3</nowiki></code> room on <code><nowiki>irc.freenode.net</nowiki></code>, and are chaired by Devananda or Chris Krelle (NobodyCam).<br />
<br />
The Meeting time alternates between '''1700 UTC on Monday''' and '''0500 UTC on Tuesday''', to accommodate contributors from around the world.<br />
<br />
NOTE: <span style="color:green">Meeting time is UTC based and may need to be adjusted based on local time zone changes, eg. as a result of daylight savings, which changes on different days in different countries.</span><br><br />
<br />
A Google Calendar for the meeting is here: [https://www.google.com/calendar/embed?showPrint=0&amp;showCalendars=0&amp;mode=WEEK&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=sodarock.com_fepuqkqe2333htb41n2n9qmue8%40group.calendar.google.com&amp;color=%235229A3&amp;ctz=America%2FLos_Angeles Google Calendar]<br />
<br />
Anyone is welcome to add topics to the agenda. However, topics should be posted '''at least two (2) days before the meeting''', and should include the IRC handle of the proposer and a link to further information. This gives everyone time to review any material ahead of time so we can use the meeting time for actual discussion.<br />
* Example topic: (devananda) Let's talk about zebras. Reference: http://en.wikipedia.org/wiki/Zebra<br />
<br />
== Next Meeting ==<br />
The next meeting is scheduled for May 4th, 2015 at 1700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150504T1700).<br />
<br />
== Agenda for next meeting ==<br />
* Announcements / Reminders<br />
**<br />
<br />
* Review [https://etherpad.openstack.org/p/IronicWhiteBoard subteam status reports] (capped at ten minutes)<br />
<br />
* Open Discussion<br />
** Less strictness for node names https://bugs.launchpad.net/ironic/+bug/1449979<br />
<br />
== Previous meetings ==<br />
<br />
[http://eavesdrop.openstack.org/meetings/ironic/ Logs from previous meetings can be found here.]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=HypervisorSupportMatrix&diff=77600HypervisorSupportMatrix2015-04-16T08:53:02Z<p>Lucas Alvares Gomes: /* Features */</p>
<hr />
<div>= Compute Drivers =<br />
<br />
OpenStack Compute (Nova) has an abstraction layer for compute drivers. This is what allows you to choose which hypervisor(s) to use for your Nova deployment. The reality is that the support of each of the options is not equal. They are not tested the same amount. They also do not all support the same features. The purpose of this page is to describe the current support state of each compute driver in terms of testing and functionality.<br />
<br />
== Driver Testing Status ==<br />
<br />
=== Group A ===<br />
<br />
These drivers are fully supported. Test coverage includes:<br />
* unit tests that gate commits<br />
* functional testing that gate commits<br />
<br />
<br />
Drivers in this group include:<br />
* libvirt (qemu/KVM on x86)<br />
<br />
=== Group B ===<br />
<br />
These drivers are in a bit of a middle ground. Test coverage includes:<br />
* unit tests that gate commits<br />
* functional testing providing by an external system that does not gate commits, but advises patch authors and reviewers of results in gerrit (the code review system).<br />
<br />
<br />
Drivers in this group include:<br />
* [http://wiki.cloudbase.it/hyperv-tempest-exclusions Hyper-V]<br />
* [[NovaVMware/Minesweeper| VMware]]<br />
* [[XenServer/XenServer_CI | XenServer 6.2]]<br />
<br />
=== Group C ===<br />
<br />
'''NOTE:''' Drivers in Group C will be deprecated by the Icehouse release. See [[HypervisorSupportMatrix/DeprecationPlan]] for details.<br />
<br />
These drivers have minimal testing and may or may not work at any given time. Use them at your own risk. Test coverage includes:<br />
* (maybe) unit tests that gate commits<br />
* no public functional testing<br />
<br />
<br />
Drivers in this group include.<br />
* baremetal<br />
* docker<br />
* Xen via libvirt<br />
* LXC via libvirt<br />
<br />
== Hypervisor feature support matrix ==<br />
<br />
This is an attempt to help new users decide on a hypervisor based on features that can be controlled through compute.<br />
<br />
Historically, most [[OpenStack]] development is done with the KVM hypervisor with which you are more likely to find community support for issues . All features that are currently supported in KVM are also supported in QEMU.<br />
<br />
[http://technet.microsoft.com/en-US/library/hh833684.aspx Microsoft Hyper-V] and VMware ESXi are gaining much support with Hyper-V now being available with a [http://windowsitpro.com/hyper-v/microsoft-free-hyper-v-server-2012-features free license]. ESXi can also be used with a free license however API support is limited as READ ONLY without vCenter and an Enterprise license.<br />
<br />
As far as the [[Xen]] hypervisor is concerned, it is worth noting the following definitions:<br />
* [[XenServer]]: Open Source but commercially supported product from Citrix (Free edition also available)<br />
* Xen Cloud Platform (XCP): Open-source equivalent of [[XenServer]] (and the development project for the toolstack). Everything said about [[XenServer]] below applies equally to XCP.<br />
* XenAPI: The management API exposed by [[XenServer]] and XCP.<br />
* XAPI: The primary daemon on [[XenServer]] and Xen Cloud Platform; the one that exposes the XenAPI.<br />
* [[Xen/Libvirt|Xen via Libvirt]]: Xen hypervisor management using the libvirt Xen driver.<br />
<br />
Nova has support for [[XenServer]] and XCP through the XenAPI virt layer. Note that this does not imply support for other Xen-based platforms such as those shipped with RHEL 6 or SUSE, which is provided via the libvirt layer (i.e. Xen via libvirt).<br />
<br />
As far as the [[Baremetal]] hypervisor is concerned, it is worth noting that [[Ironic]] will deprecate the baremetal driver upon its graduation. New features are being added to [[Ironic]].<br />
<br />
Please help keep this list up-to-date.<br />
<br />
'''Legend''': ✔ indicates support, ✗ indicates the feature is not supported, * indicates there is a caveat to the functionality (caveats need to be documented!), and a blank cell generally indicates more testing is needed to make a judgment.<br />
<br />
<br />
=== Features ===<br />
<br />
'''WARNING This table is no longer considered to be the canonical source of information about driver support status. For Kilo releases onwards, please consult the new [http://docs.openstack.org/developer/nova/support-matrix.html Nova Hypervisor Support Matrix]'''<br />
<br />
{| border="1" cellpadding="2" cellspacing="0"<br />
| '''Feature''' <br />
| '''[[XenServer|XenServer/XCP]] ''' <br />
| '''[http://libvirt.org/drvqemu.html KVM/libvirt on (x86)]''' <br />
| '''[http://libvirt.org/drvqemu.html QEMU/libvirt (x86)]''' <br />
| '''[http://libvirt.org/drvlxc.html LXC/libvirt]''' <br />
| '''[http://libvirt.org/drvxen.html Xen/Libvirt]'''<br />
| '''[http://docs.openstack.org/trunk/config-reference/content/vmware.html VMware]''' <br />
| '''[[Hyper-V]]'''<br />
| '''[[Baremetal]]'''<br />
| '''[[Ironic]]'''<br />
| '''[http://www.docker.io Docker]'''<br />
| '''[http://www.ibm.com/systems/power/software/linux/powerlinux/powerkvm PowerKVM]'''<br />
|-<br />
| Launch <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ *(12)<br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔ <br />
| ✔<br />
| ✔<br />
|-<br />
| Reboot <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔*(11) <br />
| ✔<br />
| ✔<br />
|-<br />
| Terminate <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔<br />
|-<br />
| Resize <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| style="color: red" | ✗<br />
| ✔<br />
|-<br />
| Rescue <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
| ✔ <br />
| <br />
| style="color: red" | ✗<br />
| <br />
| style="color: red" | ✗<br />
| ✔<br />
|-<br />
| Pause <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| style="color: red" | ✗ <br />
| ✔ <br />
| * (15)<br />
| * (15)<br />
| ✔<br />
| ✔<br />
|-<br />
| Un-pause <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| style="color: red" | ✗ <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| ✔<br />
| ✔<br />
|-<br />
| Suspend <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| style="color: red" | ✗<br />
| ✔<br />
|-<br />
| Resume <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| style="color: red" | ✗<br />
| ✔<br />
|-<br />
| Inject Networking <br />
| ✔*(1)(2) <br />
| ✔*(1) <br />
| ✔*(1) <br />
| <br />
|<br />
| ✔* <br />
| ✔ <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
|<br />
|<br />
|-<br />
| Inject File <br />
| ✔ <br />
| ✔* <br />
| ✔* <br />
| <br />
|<br />
| <br />
| style="color: red" | ✗*(6)<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
|<br />
|-<br />
| Serial Console Output <br />
| ✔(4) <br />
| ✔ <br />
| ✔ <br />
| style="color: red" | ✗ <br />
|<br />
| ✔ <br />
| ✔ <br />
| <br />
| <br />
| ✔<br />
|<br />
|-<br />
| VNC Console <br />
| ✔* <br />
| ✔* <br />
| ✔* <br />
| ✔ <br />
|<br />
| ✔ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
|<br />
|-<br />
| SPICE Console <br />
| style="color: red" | ✗ <br />
| ✔<br />
| ✔ <br />
| <br />
|<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
|-<br />
| RDP Console <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
| ✔ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
|<br />
|-<br />
| Attach Volume <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| style="color: red" | ✗ <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
|<br />
| <br />
| style="color: red" | ✗<br />
| ✔ <br />
|-<br />
| Detach Volume <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| style="color: red" | ✗ <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
|<br />
| <br />
| style="color: red" | ✗<br />
| ✔ <br />
|-<br />
| Live Migration <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| style="color: red" | ✗ (10) <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| style="color: red" | ✗<br />
| ✔ <br />
|-<br />
| Snapshot <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔ * (13)<br />
| ✔ <br />
| ✔ <br />
| * (15)<br />
| * (15) <br />
| ✔<br />
| ✔ <br />
|-<br />
| iSCSI <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
| ✔ <br />
| ✔ <br />
|<br />
| <br />
|<br />
| ✔ <br />
|-<br />
| iSCSI CHAP<br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| <br />
| <br />
| ✔<br />
| <br />
|<br />
|<br />
| ✔ <br />
|-<br />
| Fibre Channel<br />
| style="color: red" | ✗ <br />
| ✔ <br />
| ✔ <br />
| <br />
| <br />
| <br />
| <br />
|<br />
|<br />
|<br />
| ✔ <br />
|-<br />
| Set Admin Pass <br />
| ✔ <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗ <br />
| <br />
|<br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗*(6) <br />
| * (15)<br />
| * (15)<br />
| style="color: red" | ✗<br />
| <br />
|-<br />
| Get Guest Info <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
| ✔ <br />
| ✔ <br />
|<br />
| <br />
| ✔<br />
| ✔ <br />
|-<br />
| Get Host Info <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
| ✔ <br />
| ✔ <br />
|<br />
| <br />
| ✔<br />
| ✔ <br />
|-<br />
| Glance Integration <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔ <br />
| ✔<br />
| ✔ <br />
|-<br />
| Service Control <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
| ✔ <br />
| ✔ <br />
| <br />
|<br />
|<br />
| ✔ <br />
|-<br />
| VLAN Networking <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔ <br />
| style="color: red" | ✗*(7) <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗*(16)<br />
|<br />
| ✔ <br />
|-<br />
| Flat Networking <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔<br />
| ✔<br />
| ✔ <br />
|-<br />
| Security Groups <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| style="color: red" | ✗*(9) <br />
| style="color: red" | ✗*(7) <br />
|<br />
|<br />
| ✔<br />
| ✔ <br />
|-<br />
| Firewall Rules <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| style="color: red" | ✗ *(14) <br />
| style="color: red" | ✗*(7) <br />
| * (15)<br />
| * (15)<br />
|<br />
| ✔ <br />
|-<br />
| Routing <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| ✔ <br />
| style="color: red" | ✗*(7) <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
|<br />
|-<br />
| nova diagnostics <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| <br />
| ✔<br />
| ✔<br />
| <br />
|<br />
|<br />
| style="color: red" | ✗<br />
| ✔ <br />
|-<br />
| Config Drive <br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| ✔<br />
| ✔ <br />
| ✔ <br />
| ✔ <br />
| style="color: red" | ✗ <br />
| ✔<br />
| style="color: red" | ✗<br />
|<br />
|-<br />
| Auto configure disk <br />
| ✔ <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
| style="color: red" | ✗<br />
| ✔<br />
|<br />
| <br />
| style="color: red" | ✗<br />
|<br />
|-<br />
| Evacuate <br />
| ✔ <br />
| ✔ <br />
| <br />
| <br />
| ✔<br />
| <br />
| ✔ <br />
| style="color: red" | ✗<br />
| style="color: red" | ✗ <br />
|<br />
| ✔ <br />
|-<br />
| Volume swap<br />
| style="color: red" | ✗ <br />
| ✔<br />
| ✔<br />
| <br />
|<br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
|<br />
|<br />
| style="color: red" | ✗<br />
| ✔ <br />
|-<br />
| Volume rate limiting<br />
| style="color: red" | ✗ <br />
| ✔<br />
| ✔<br />
|<br />
| <br />
| style="color: red" | ✗ <br />
| style="color: red" | ✗<br />
|<br />
|<br />
| style="color: red" | ✗<br />
| ✔ <br />
|}<br />
<br />
# Inject Networking only works with nova-network in Flat mode, and only with Debian/Ubuntu based virtual machines, and only at boot time<br />
# [[XenServer]] integration also supports using a guest agent to inject networking settings, at any time when a VM has the guest agent installed, through an admin API extension<br />
# (unused)<br />
# XenAPI support for serial console [https://blueprints.launchpad.net/nova/+spec/xenapi-server-log was added in Havana]<br />
# (unsued)<br />
# Functionality provided by cloudbase-init for windows http://www.cloudbase.it/cloud-init-for-windows-instances/<br />
# Vlan and Routing is only supported on Hyper-V when using the Quantum / Neutron Hyper-V Agent; VlanManager mode is not supported with nova-network.<br />
# Support of Xen using Libvirt<br />
# Security Groups supported on VC/ESX Driver when using the Quantum NVP Plugin<br />
# https://bugs.launchpad.net/nova/+bug/1192192<br />
# Copy on write images are not suported (see bug https://bugs.launchpad.net/nova/+bug/1253571).<br />
# Only cold-snapshots are available.<br />
# https://bugs.launchpad.net/nova/+bug/1269448<br />
# Feature does not make sense for Baremetal / Ironic<br />
# Feature currently enabled by some Ironic drivers, but not all.<br />
<br />
=== Description of features ===<br />
<br />
==== Auto configure disk ====<br />
<br />
Automatically reconfigure the size of the partition to match the size of the flavor's root drive before booting.<br />
<br />
==== nova diagnostics ====<br />
<br />
The `nova diagnostics` command will provide some information about resource use associated with an instance. See the [http://docs.openstack.org/admin-guide-cloud/content/instance_usage_statistics.html OpenStack Cloud Administrator Guide] for more details.<br />
<br />
==== Set Admin Pass ====<br />
<br />
This feature is the use of a guest agent to change the administrative (root) password on an instance.<br />
<br />
== Known bugs, by hypervisor ==<br />
<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=kvm KVM-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver,xen XenApi-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+libvirt+&field.tags_combinator=ALL libvirt+Xen-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=qemu QEMU-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc LXC-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware VMware-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v Hyper-V-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=baremetal Baremetal-specific bugs]<br />
* [https://bugs.launchpad.net/nova/+bugs?field.tag=docker Docker-specific bugs]</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic/CoreTeam&diff=75478Ironic/CoreTeam2015-03-12T16:22:37Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>[[Category:Ironic]]<br />
<br />
= Teams =<br />
<br />
The [https://review.openstack.org/#/admin/groups/165,members ironic-core] team is responsible for reviewing all changes proposed to the following repositories:<br />
* openstack/ironic -- the primary services which comprise the OpenStack Ironic project<br />
* openstack/python-ironicclient -- our Python client library and CLI <br />
* openstack/ironic-python-agent -- the in-ramdisk Agent which we utilize for inband provisioning of hardware<br />
<br />
<br />
The [https://review.openstack.org/#/admin/groups/307,members ironic-python-agent-core] team is an additional team which leads the review effort on the below projects. Members of this team may or may not be members of ironic-core.<br />
* openstack/ironic-python-agent<br />
<br />
<br />
The [https://review.openstack.org/#/admin/groups/352,members ironic-specs-core] team is responsible for reviewing design specifications. Not all ironic-core members have the time to dedicate to design reviews (and some would just rather focus on code). Furthermore, some operators routinely contribute to the design process, but don't have the time to regularly review code, and as such they are not members of ironic-core.<br />
* openstack/ironic-specs<br />
<br />
<br />
The [https://review.openstack.org/#/admin/groups/481,members ironic-discoverd-core] team is responsible for the following projects:<br />
* stackforge/ironic-discoverd<br />
<br />
<br />
Note that everyone is encouraged to help review changes, even if you are not a member of one of these teams. All reviews are very useful and are taken into account by the core team members. Participating in the review process is the most critical task on the road to joining any of the teams.<br />
<br />
= Adding or Removing Members =<br />
<br />
Each review group above should reflect active participation in the respective team. The ironic-core and ironic-specs-core teams are led by the project PTL, whereas ironic-python-agent-core and ironic-discoverd-core are delegated to JayF and dtantsur, respectively.<br />
<br />
The addition of new members, or removal of existing members, should be discussed amongst existing cores periodically, and any changes should be paired with an email to the openstack-dev mailing list. Such a discussion may be initiated by any core at any time. A member of the team may be removed at any time by the PTL. This is typically due to a drop off of involvement by the member such that they are no longer meeting expectations to maintain team membership. There is no need for a vote either when adding or removing members, though it is customary to get input from the existing team when making any changes to the team structure.<br />
<br />
Note that discussing concerns about a nominee openly can have negative ramifications for the nominee. The effects of being nominated and then publicly -1'd are unpleasant at best and harmful at worst. Therefor, it is preferable to have an initial informal round of discussion amongst the existing core team to ensure that there is enough consensus and desire to work with the nominee, prior to a public vote. <br />
<br />
It is also customary to reach out to the nominee privately to confirm their willingness to accept the position prior to any public discussion, though, as one can infer from the review activity an existing level of commitment to the project, this is not necessary.<br />
<br />
= Membership Expectations =<br />
<br />
Membership in the core review team is a significant commitment and should not be taken lightly. Maintaining membership on this team takes a lot of time. Further, it is important that the time invested is ''consistent''. It is harmful to the team and the project overall for the core team members' participation to be inconsistent.<br />
<br />
Team members are expected to participate in code reviews on a regular (near daily) basis. Members are also expected to stay on top of discussions happening within the project, primarily on the openstack-dev mailing list and IRC. Note that IRC is used quite heavily, so members should be in <tt>#openstack-ironic</tt> as much as they can. These activities are critical to be able to provide high quality reviews based on the current state of the project that are consistent with the reviews being done by others on the team and consistent with the [http://docs.openstack.org/infra/manual/developers.html#peer-review documented review guidelines].<br />
<br />
One metric used to determine the level of participation in reviews is just the number of reviews being done. While there is no hard line for an expectation on the number of reviews you are doing, members are generally expected to be in the same ballpark as the majority of the rest of the team. You can find stats on that here:<br />
<br />
* [http://russellbryant.net/openstack-stats/ironic-reviewers-30.txt Last 30 Days]<br />
* [http://russellbryant.net/openstack-stats/ironic-reviewers-90.txt Last 90 days]<br />
* [http://russellbryant.net/openstack-stats/ironic-reviewers-180.txt Last 180 Days]<br />
<br />
The number of reviews is certainly not the only important thing. It is also important that reviews are high quality, such that you gain respect from the other core team members over time. This is done by regularly providing high quality constructive criticism. Your well thought out recommendations for changes are what build credibility for your +1 of a patch.<br />
<br />
All of these things are important, but the most important thing of all is to gain trust from the majority of the core team. There's not a well defined list of things you must do to gain this trust, but all of the expectations described here are a starting point.<br />
<br />
= Review Prioritization =<br />
<br />
Not all reviews are created equal. Team members should take care in prioritizing where they invest their review time. In general, priority should be based on the priority of the bug or blueprint the patch is associated with. Beyond that, older reviews should get priority. Take a look at the [[ReviewWorkflowTips]] page for tips on how to work prioritization into your workflow.<br />
<br />
= Other notes =<br />
<br />
* A -2 is not overridable by any other core, so be very sparing with them. It's a way to signal "this is so bad, I'm going to unilateral veto it"<br />
* Try to avoid approving patches of people from the same company (particularly large features)<br />
* Do not approve your own patches<br />
* Approving a patch required at least 2 +2<br />
* Try to review at least 1 patch per day</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=ReleaseNotes/Kilo&diff=72880ReleaseNotes/Kilo2015-02-03T15:16:10Z<p>Lucas Alvares Gomes: /* Key New Features */</p>
<hr />
<div>{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0; background-color:#FFFFFF;font-size:95%; vertical-align:middle;"<br />
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]<br />
| '''Release Under Development'''<br />
This release of OpenStack is under development and has yet to be completed. It will be released on April 30, 2015<br />
<br />
The information on this page may not accurately reflect the state of release at the current point in time.<br />
|}<br />
<br />
= OpenStack 2015.1 (Kilo) Release Notes =<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== General Upgrade Notes ==<br />
<br />
* TBD<br />
<br />
== OpenStack Object Storage (Swift) ==<br />
<br />
=== Key New Features ===<br />
<br />
=== Known Issues ===<br />
None<br />
<br />
=== Upgrade Notes ===<br />
<br />
== OpenStack Compute (Nova) ==<br />
<br />
=== Key New Features ===<br />
<br />
==== Upgrade Support ====<br />
<br />
* TBD<br />
<br />
==== Compute Drivers ====<br />
<br />
===== Hyper-V =====<br />
<br />
* TBD<br />
<br />
===== Libvirt (KVM) =====<br />
<br />
* TBD<br />
<br />
===== VMware =====<br />
<br />
* TBD<br />
<br />
===== XenServer =====<br />
<br />
* TBD<br />
<br />
===== Ironic =====<br />
<br />
* Add config drive support ( https://review.openstack.org/#/c/144792/ )<br />
<br />
==== API ====<br />
<br />
* TBD<br />
<br />
==== Scheduler ====<br />
<br />
* TBD<br />
<br />
==== Other Features ====<br />
<br />
* TBD<br />
<br />
=== Known Issues ===<br />
<br />
* TBD<br />
<br />
=== Upgrade Notes ===<br />
<br />
* TBD<br />
<br />
== OpenStack Image Service (Glance) ==<br />
=== Key New Features ===<br />
* TBD<br />
<br />
=== Known Issues ===<br />
<br />
=== Upgrade Notes ===<br />
<br />
== OpenStack Dashboard (Horizon) ==<br />
<br />
=== Key New Features ===<br />
* TBD<br />
<br />
=== Known Issues ===<br />
<br />
=== Upgrade Notes ===<br />
<br />
== OpenStack Identity (Keystone) ==<br />
<br />
=== Key New Features ===<br />
<br />
* TBD<br />
<br />
=== Known Issues ===<br />
<br />
* TBD<br />
<br />
=== Upgrade Notes ===<br />
<br />
* XML support in Keystone has been removed as of Kilo. When upgrading from Juno to Kilo, it is recommended that references to XML and XmlBodyMiddleware be removed from the [https://github.com/openstack/keystone/blob/master/etc/keystone-paste.ini Keystone Paste configuration]. This includes removing the XML middleware filters and there references from the public_api, admin_api, api_v3, public_version_api, admin_version_api and any other pipelines that may contain the XML filters.<br />
<br />
== OpenStack Network Service (Neutron) ==<br />
=== Key New Features ===<br />
<br />
=== Known Issues ===<br />
None yet.<br />
<br />
=== Upgrade Notes ===<br />
<br />
From Havana, Neutron no longer supported an explicit lease database (https://bugs.launchpad.net/bugs/1202392). This caused https://bugs.launchpad.net/grenade/+bug/1345947 instead. In order to address the issue, a change to the dhcp.filter is required, so that line:<br />
<br />
'''dnsmasq: EnvFilter, dnsmasq, root, NEUTRON_NETWORK_ID='''<br />
<br />
Be replaced by:<br />
<br />
'''dnsmasq: EnvFilter, dnsmasq, root, HOSTS_FILE='''<br />
<br />
This avoids the DHCPNAK flood.<br />
<br />
== OpenStack Block Storage (Cinder) ==<br />
=== Key New Features ===<br />
<br />
=== Known Issues ===<br />
None yet<br />
<br />
=== Upgrade Notes ===<br />
* The 'host' config option for multiple-storage backends in cinder.conf is renamed to 'backend_host' in order to avoid a naming conflict with the 'host' to locate redis. If you use this option, please ensure your configuration files are updated.<br />
<br />
== OpenStack Telemetry (Ceilometer) ==<br />
=== Key New Features ===<br />
* TBD<br />
<br />
=== Known Issues ===<br />
* TBD<br />
<br />
=== Upgrade Notes ===<br />
<br />
== OpenStack Orchestration (Heat) ==<br />
=== Key New Features ===<br />
<br />
=== Known Issues ===<br />
None yet<br />
<br />
=== Upgrade Notes ===<br />
None yet<br />
<br />
== OpenStack Database service (Trove) ==<br />
=== Key New Features ===<br />
<br />
=== Known Issues ===<br />
None yet<br />
<br />
=== Upgrade Notes ===<br />
None yet<br />
<br />
== OpenStack Documentation ==<br />
<br />
=== Key New Features ===<br />
<br />
* TBD<br />
<br />
=== Known Issues ===<br />
<br />
=== Upgrade Notes ===<br />
None yet</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic&diff=70870Ironic2014-12-22T16:45:12Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>= OpenStack Bare Metal Provisioning Program =<br />
<br />
== Projects ==<br />
<br />
=== Ironic ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Official name<br />
| '''OpenStack Bare Metal Provisioning'''<br />
|-<br />
| Source code<br />
| https://github.com/openstack/ironic<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/ironic/<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/ironic<br />
|-<br />
| Specifications<br />
| http://specs.openstack.org/openstack/ironic-specs<br />
|-<br />
| Latest Release Notes<br />
| https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
|-<br />
| Weekly meetings<br />
| https://wiki.openstack.org/wiki/Meetings/Ironic<br />
|}<br />
<br />
=== python-ironicclient ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/python-ironicclient<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/python-ironicclient<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/python-ironicclient<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/python-ironicclient<br />
|}<br />
<br />
=== ironic-python-agent ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-python-agent<br />
|-<br />
| Bug Tracker<br />
| https://bugs.launchpad.net/ironic tag: "agent"<br />
|}<br />
<br />
=== pyghmi ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/stackforge/pyghmi<br />
|}<br />
<br />
<br />
== Status ==<br />
<br />
Ironic was first available as an Incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic is officially Integrated with OpenStack beginning with the "Kilo" release.<br />
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse<br />
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
<br />
<br />
Information on the status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing<br />
<br />
For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]<br />
<br />
== Etherpads ==<br />
<br />
Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.<br />
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]<br />
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]<br />
<br />
== IRC ==<br />
<br />
Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net<br />
<br />
== Developers ==<br />
<br />
Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines<br />
Please note that for any non-trivial change that does not fix some bug, you have to go through [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]<br />
<br />
== Pixie Boots, the Ironic drummer bear ==<br />
<br />
Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.<br />
<br />
High-resolution PNGs versions are available by clicking on the images below:<br />
<br />
<gallery><br />
Ironic_mascot_color.png|Colored<br />
Ironic_mascot_outline.png|Outlined<br />
</gallery><br />
<br />
You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]<br />
<br />
All images is licensed [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic&diff=70814Ironic2014-12-19T18:11:45Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>= OpenStack Bare Metal Provisioning Program =<br />
<br />
== Projects ==<br />
<br />
=== Ironic ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Official name<br />
| '''OpenStack Bare Metal Provisioning'''<br />
|-<br />
| Source code<br />
| https://github.com/openstack/ironic<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/ironic/<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/ironic<br />
|-<br />
| Specifications<br />
| http://specs.openstack.org/openstack/ironic-specs<br />
|-<br />
| Latest Release Notes<br />
| https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
|-<br />
| Weekly meetings<br />
| https://wiki.openstack.org/wiki/Meetings/Ironic<br />
|}<br />
<br />
=== python-ironicclient ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/python-ironicclient<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/python-ironicclient<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/python-ironicclient<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/python-ironicclient<br />
|}<br />
<br />
=== ironic-python-agent ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-python-agent<br />
|-<br />
| Bug Tracker<br />
| https://bugs.launchpad.net/ironic tag: "agent"<br />
|}<br />
<br />
=== pyghmi ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/stackforge/pyghmi<br />
|}<br />
<br />
<br />
== Status ==<br />
<br />
Ironic was first available as an Incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic is officially Integrated with OpenStack beginning with the "Kilo" release.<br />
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse<br />
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
<br />
<br />
Information on the status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing<br />
<br />
For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]<br />
<br />
== Etherpads ==<br />
<br />
Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.<br />
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]<br />
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]<br />
<br />
== IRC ==<br />
<br />
Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net<br />
<br />
== Developers ==<br />
<br />
Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines<br />
Please note that for any non-trivial change that does not fix some bug, you have to go through [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]<br />
<br />
== Pixie Boots, the Ironic drummer bear ==<br />
<br />
Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.<br />
<br />
High-resolution PNGs versions are available by clicking on the images below:<br />
<br />
<gallery><br />
Ironic_mascot_color.png|Colored<br />
Ironic_mascot_outline.png|Outlined<br />
</gallery><br />
<br />
You can also download the Inkscape SVG vector file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]<br />
<br />
All images is licended [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].</div>Lucas Alvares Gomeshttps://wiki.openstack.org/w/index.php?title=Ironic&diff=70813Ironic2014-12-19T18:08:30Z<p>Lucas Alvares Gomes: </p>
<hr />
<div>= OpenStack Bare Metal Provisioning Program =<br />
<br />
== Projects ==<br />
<br />
=== Ironic ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Official name<br />
| '''OpenStack Bare Metal Provisioning'''<br />
|-<br />
| Source code<br />
| https://github.com/openstack/ironic<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/ironic/<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/ironic<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/ironic<br />
|-<br />
| Specifications<br />
| http://specs.openstack.org/openstack/ironic-specs<br />
|-<br />
| Latest Release Notes<br />
| https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
|-<br />
| Weekly meetings<br />
| https://wiki.openstack.org/wiki/Meetings/Ironic<br />
|}<br />
<br />
=== python-ironicclient ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/python-ironicclient<br />
|-<br />
| Bug tracker<br />
| https://bugs.launchpad.net/python-ironicclient<br />
|-<br />
| Feature tracker<br />
| https://blueprints.launchpad.net/python-ironicclient<br />
|-<br />
| Developer doc<br />
| http://docs.openstack.org/developer/python-ironicclient<br />
|}<br />
<br />
=== ironic-python-agent ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/openstack/ironic-python-agent<br />
|-<br />
| Bug Tracker<br />
| https://bugs.launchpad.net/ironic tag: "agent"<br />
|}<br />
<br />
=== pyghmi ===<br />
<br />
{| border="1" cellpadding="2"<br />
| Source code<br />
| https://github.com/stackforge/pyghmi<br />
|}<br />
<br />
<br />
== Status ==<br />
<br />
Ironic was first available as an Incubated project in the "Icehouse" release. The following "Juno" release saw improved integration with Nova, as well as many stability and feature improvements. Ironic is officially Integrated with OpenStack beginning with the "Kilo" release.<br />
* Icehouse, 2014.1: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Icehouse<br />
* Juno, 2014.2: https://wiki.openstack.org/wiki/Ironic/ReleaseNotes/Juno<br />
<br />
<br />
Information on the status of Ironic's test suite can be found here: https://wiki.openstack.org/wiki/Ironic/Testing<br />
<br />
For a list of current drivers and the status of their CI testing, see the [https://wiki.openstack.org/wiki/Ironic/Drivers wiki page we maintain] and the [http://stackalytics.com/report/driverlog?project_id=openstack%2Fironic Stackalytics page which tracks third-party CI]<br />
<br />
== Etherpads ==<br />
<br />
Our project teams frequently share ideas and coordinate by using etherpads, some of which stick around for a while. Those are listed here.<br />
* [https://etherpad.openstack.org/p/IronicWhiteBoard General-purpose "white board"]<br />
* [https://etherpad.openstack.org/p/IronicReviewDay Coordination point during "review days"]<br />
<br />
== IRC ==<br />
<br />
Discussion of the project also takes place in '''#openstack-ironic''' on irc.freenode.net<br />
<br />
== Developers ==<br />
<br />
Guidelines for developers can be found here: https://wiki.openstack.org/wiki/Ironic/Developer_guidelines<br />
Please note that for any non-trivial change that does not fix some bug, you have to go through [https://wiki.openstack.org/wiki/Ironic/Specs_Process specs review process]<br />
<br />
== Pixie Boots, the Ironic drummer bear ==<br />
<br />
Pixie Boots is the mascot of the "'''Bear Metal'''" Provisioning Program for OpenStack, a.k.a Ironic. It was drawn by [https://plus.google.com/u/0/+LucasAlvaresGomes/ Lucas Alvares Gomes] and two versions of it are available: One colored and one outlined. Feel free to use the images to make t-shirts or any other paraphernalia.<br />
<br />
High-resolution PNGs versions are available by clicking on the images below:<br />
<br />
<gallery><br />
Ironic_mascot_color.png|Colored<br />
Ironic_mascot_outline.png|Outlined<br />
</gallery><br />
<br />
Download the .svg file: [https://wiki.openstack.org/wiki/File:Ironic_mascot.svg Ironic_mascot.svg]<br />
<br />
All images is licended [http://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA].</div>Lucas Alvares Gomes