Instances in the vertica clusters are not using instance specific flavor

Bug #1452023 reported by Saurabh Surana on 2015-05-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
High
Unassigned

Bug Description

Instances in the vertica clusters are not honoring instance specific flavor and all the instances get provisioned with the same flavor as that of the first instance.

The code in vertica api strategy, sets a local variable for flavor_id by looking at only first instance and uses that to provision all the instances in the cluster.

summary: - Instances in the vertica clusters are not honoring instance specific
- flavor or disk sizes
+ Instances in the vertica clusters are not using instance specific flavor
Changed in trove:
assignee: nobody → Saurabh Surana (saurabh-surana)
Changed in trove:
status: New → In Progress
Sushil Kumar (sushil-kumar2) wrote :

Currently, the vertica clusters api supports the instances having same flavor and volume size only, which is why it does not matters that you select first one or any of them, because currently they all are equal.

For unequal Volumes, https://github.com/openstack/trove/blob/master/trove/common/strategies/cluster/experimental/vertica/api.py#L85-86

and unequal flavors, https://github.com/openstack/trove/blob/master/trove/common/strategies/cluster/experimental/vertica/api.py#L68-69

would raise respective exceptions.

Changed in trove:
importance: Undecided → High
milestone: none → liberty-2
Changed in trove:
milestone: liberty-2 → liberty-3
Changed in trove:
milestone: liberty-3 → ongoing
Amrith Kumar (amrith) on 2016-04-05
Changed in trove:
status: In Progress → Confirmed
assignee: Saurabh Surana (saurabh-surana) → nobody
milestone: ongoing → newton-1
Amrith Kumar (amrith) on 2016-09-18
Changed in trove:
milestone: newton-1 → ongoing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers