v1.0.36

New Features

• proliant oneview upgrade run: upload and stage an appliance software update image (.bin), then optionally install it. Pick an image interactively from a directory/share with --from-dir, or point at one with --image. Staging is the default; the reboot-inducing install is gated behind --execute plus a typed confirmation, and blocked when the readiness verdict is FAIL (override with --force).
• proliant oneview upgrade pending: show the currently staged appliance update.
• proliant oneview upgrade cancel: remove a stuck or aborted staged update.
• proliant oneview appliances describe [NAME]: show an appliance's General page — the active/standby Composer HA pair and their connection state, model, memory, per-node start time and uptime, firmware version/date, and the Composable Infrastructure Appliances inventory. Defaults to the active appliance; --json for scripting.
• proliant oneview firmware apply: roll out an SSP (Synergy Service Pack) firmware baseline that OneView orchestrates — shared infrastructure (logical enclosure: interconnects + frame link modules) and/or compute (server profiles), applied in that order. Pick a baseline with --baseline (defaults to the newest registered SSP) and a scope with --logical-enclosure/--all-enclosures and/or --server-profile/--all-profiles. The plan shows a source-backed OneView↔SSP compatibility note — whether the chosen SSP is recommended, supported, or not listed for the running OneView version (per HPE's Synergy Software Releases matrix), and warns before an unsupported apply. Default is a non-destructive plan; the hardware-rebooting apply is gated behind --execute plus a typed confirmation. The confirmation is scope-aware — an infrastructure-only apply states that no server profiles are included and compute modules will not be power-cycled. During --execute a live per-target progress bar tracks the underlying OneView task to completion, showing the current stage (e.g. "Update logical interconnect") and percent instead of returning the instant it starts.
• proliant oneview interconnects describe <name>: single-interconnect detail page matching OneView's GUI — General (logical interconnect, firmware baseline vs. installed version, management interface, stacking, IP addresses), Hardware (product, location, MAC, WWN, serial/part numbers, health), Interconnect Link Ports, Uplink Ports (type, speed, uplink set, connector, connected-to — showing the remote switch's actual hostname from LLDP, not just its chassis MAC like the GUI does), Downlink Ports (server hardware, adapter port, server profile — resolved from live port-neighbor wiring, not just profile assignment), live Utilization (CPU/memory/power/temperature), and Remote Support state.

Bug Fixes

• proliant oneview upgrade run --execute: fixed a false "Upgrade complete" that printed immediately when an install started. Progress is now read only from the appliance's own update-status feed, and completion is confirmed by the appliance actually rebooting onto the target build — not by a stale 100% left over from a prior firmware task.

Enhancements

• proliant oneview upgrade run: live progress display during long operations — a byte-level progress bar (size, speed, ETA) while the multi-GB image uploads, and a phase/percent bar while the appliance installs and reboots (e.g. "Swap active/standby nodes").
• proliant setup: adding a OneView appliance now prompts for a friendly alias (like the iLO flow), defaulting to the auto-generated oneview/oneview-2/… name so pressing Enter keeps the previous behavior.
• proliant ilo: removed the --raw flag (it had drifted inconsistent — a genuine unprocessed Redfish dump for some resources, but a no-op alias of the normal output for servers, serial, and license). --json is now the one consistent automation flag across ilo/com/oneview.

---