[RFE] Using multicast for image transfer

Bug #1526485 reported by Vladyslav Drok
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Won't Fix
Wishlist
Unassigned

Bug Description

In huge environments network is bottleneck during simultaneous node provisioning. By starting group deployment over multicast will minimize network utilization. And will minimize resource utilization on image storing servers.

Baremetal nodes that are spawned with the same user image may be grouped. Since user image is equal on all nodes there is no need to send it by unicast directly to each node. Rather ironic should wait until all nodes in the group are ready to receive user image. Once it is done "user image" should be transfered to all nodes simultaneously via multicast.

Tags: needs-spec rfe
Vladyslav Drok (vdrok)
Changed in ironic:
status: New → Confirmed
importance: Undecided → Wishlist
tags: added: rfe
Revision history for this message
Vladyslav Drok (vdrok) wrote :

Copy of whiteboard:

Gerrit topic: https://review.openstack.org/#q,topic:bp/multicast-provision,n,z

Addressed by: https://review.openstack.org/225570
    Using multicast for image transfer

Revision history for this message
Jim Rollenhagen (jim-rollenhagen) wrote :

Spec is abandoned, someone is welcome to pick this up

tags: added: needs-spec
Revision history for this message
Seamanhanshan (yaojun) wrote :

I have some questions about this spec, if someone still work on it, maybe we could have a discussion.

Q1: Which multicast mode is considered? Any Source Multicast or Source Specific Multicast.
Q2: How many group address will be used? For example, One user image uses one group address(or channel).
Q3: How to control the receiver, not all the baremetal nodes can receive the user image.
Q4: Multicast isn't reliable, how about RMTP?

Changed in ironic:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.