UCS Manager plugin should be able to get the Service Profile association from the UCS Manager

Bug #1496941 reported by Sandhya Dasu on 2015-09-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sandhya Dasu

Bug Description

Currently, the ML2 UCS Manager plugin requires the user to specify the Hostname to Service profile association via "ucsm_host_mapping" in the ml2_conf_cisco.ini file. This information can become difficult to configure when the cloud has a considerable number of UCS Servers.
The plugin should be able to learn this association directly from the UCS Manager instead of getting it from the cloud admin.

Sandhya Dasu (sadasu) on 2015-09-21
Changed in networking-cisco:
assignee: nobody → Sandhya Dasu (sadasu)

Fix proposed to branch: master
Review: https://review.openstack.org/229517

Changed in networking-cisco:
status: New → In Progress

Reviewed: https://review.openstack.org/229517
Committed: https://git.openstack.org/cgit/openstack/networking-cisco/commit/?id=a237807ecb67129206bc45b9727d4e16f25ac339
Submitter: Jenkins
Branch: master

commit a237807ecb67129206bc45b9727d4e16f25ac339
Author: Sandhya Dasu <email address hidden>
Date: Wed Sep 30 12:08:56 2015 -0400

    Get the hostname to Service Profile association from UCS Manager

    These set of changes enhances the UCS Manager plugin to retrieve
    the service profile associated with a host directly from the UCS
    Manager instead of having the user specify it as config to the

    Change-Id: I24fc2cd150ea5171e1d998c6e62435a8b1cc4c8a
    Closes-Bug: #1496941

Changed in networking-cisco:
status: In Progress → Fix Committed
Sam Betts (sambetts) on 2015-11-04
Changed in networking-cisco:
milestone: none → 2.0.0
importance: Undecided → Medium
Abishek Subramanian (absubram) wrote :

Would like to back port this to stable/kilo branch.
Back port of bug 1491025 to stable/kilo is critical because of scale reasons. That patch however is dependent on this being back ported first.

tags: added: kilo-backport-potential
Abishek Subramanian (absubram) wrote :

Removing proposal for backporting to stable/kilo. Realize this change cannot be accepted as a candidate.

tags: removed: kilo-backport-potential

Change abandoned by Abishek Subramanian (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/246026
Reason: Removing proposal for backporting to stable/kilo. Realize this change cannot be accepted as a candidate.
Hence abandoning this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers