No possibility to select Virtual Accelerator branch

Bug #1614405 reported by Adrian
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fuel-plugin-6wind-virtual-accelerator
Status tracked in Trunk
1.x.x
Low
Unassigned
2.x.x
Medium
Francesco Santoro
Trunk
Medium
Francesco Santoro

Bug Description

In the fuel plug-in, the branch of 6WIND Virtual Accelerator is hard-coded.
Currently it is 1.3 ( so all the maintenance versions are availables).

It would be good to have a fields in the webUI Virtual Accelerator section where a version can be indicated or a tag (e.g. "stable"). Otherwise a new plug-in have to be generated when a new branch is released.

Adrian (adrian-poiget)
summary: - No possibilty to select Virtual Accelerator branch
+ No possibility to select Virtual Accelerator branch
Changed in fuel-plugin-6wind-virtual-accelerator:
assignee: nobody → Francesco Santoro (francesco-santoro)
tags: added: 6wind
Changed in fuel-plugin-6wind-virtual-accelerator:
importance: Undecided → Medium
assignee: Francesco Santoro (francesco-santoro) → nobody
assignee: nobody → Francesco Santoro (francesco-santoro)
status: New → Triaged
Revision history for this message
Francesco Santoro (francesco-santoro) wrote :

This seems a good approach. If my understanding is correct this new field should contain a default value ('stable') that will point to the latest version of the product.
Implementing such behavior will require some (small) modifications on the infra side. The 6WIND Virtual Accelerator branch is used to build the complete path of repository URL.
Thus, as first step, we need to support the default case and manage URLs that use this 'stable' branch in the path (that should simply perform a redirection to the last stable product folder).

Revision history for this message
Francesco Santoro (francesco-santoro) wrote :

Monitor this patch for fix: https://review.openstack.org/#/c/359223/

Revision history for this message
Francesco Santoro (francesco-santoro) wrote :

Fixed in https://review.openstack.org/#/c/359223/. Fix available in next 2.0.1 milestone

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

Other bug subscribers