StarlingX

  1. Bug #1846242
  2. Activity log

Activity log for bug #1846242

Date Who What changed Old value New value Message
2019-10-01 17:18:39 Tee Ngo bug added bug
2019-10-01 17:53:00 Tee Ngo summary Increase the limit of number of workers supported by AIODX Remove the limit of number of workers supported by AIODX
2019-10-01 17:55:56 Tee Ngo description Brief Description ----------------- Currently the max number of workers supported by AIODX system is limited 4. This limit seems low and needs to be revisited, especially when OpenStack app is not installed. In general, the limit should be raised until the benefits of AIODX+N config no longer outweigh the benefits of a Standard system config. Severity -------- Minor Steps to Reproduce ------------------ The value is obtained from Expected Behavior ------------------ Should be at least Actual Behavior ---------------- State what is the actual behavior Reproducibility --------------- N/A System Configuration -------------------- AIODX Branch/Pull Time/Commit ----------------------- Master Last Pass --------- N/A Timestamp/Logs -------------- N/A Test Activity ------------- N/A Brief Description ----------------- Currently the max number of workers supported by AIODX system is limited to 4. This limit and sematic checks to enforce it should be removed as they no longer apply in Kubernetes based platform. An AIO becomes a controller once all host CPUs have been assigned to the Platform from k8s perspective. Severity -------- Minor Steps to Reproduce ------------------ The value is obtained from Expected Behavior ------------------ Should be at least Actual Behavior ---------------- State what is the actual behavior Reproducibility --------------- N/A System Configuration -------------------- AIODX Branch/Pull Time/Commit ----------------------- Master Last Pass --------- N/A Timestamp/Logs -------------- N/A Test Activity ------------- N/A
2019-10-02 17:37:48 Ghada Khalil description Brief Description ----------------- Currently the max number of workers supported by AIODX system is limited to 4. This limit and sematic checks to enforce it should be removed as they no longer apply in Kubernetes based platform. An AIO becomes a controller once all host CPUs have been assigned to the Platform from k8s perspective. Severity -------- Minor Steps to Reproduce ------------------ The value is obtained from Expected Behavior ------------------ Should be at least Actual Behavior ---------------- State what is the actual behavior Reproducibility --------------- N/A System Configuration -------------------- AIODX Branch/Pull Time/Commit ----------------------- Master Last Pass --------- N/A Timestamp/Logs -------------- N/A Test Activity ------------- N/A Brief Description ----------------- Currently the max number of workers supported by AIODX system is limited to 4. This limit and sematic checks to enforce it should be removed as they no longer apply in Kubernetes based platform. An AIO becomes a controller once all host CPUs have been assigned to the Platform from k8s perspective. Severity -------- Minor Steps to Reproduce ------------------ Add 5th worker node on AIO-DX Expected Behavior ------------------ Should be allowed Actual Behavior ---------------- Request gets rejected Reproducibility --------------- N/A System Configuration -------------------- AIODX Branch/Pull Time/Commit ----------------------- Master Last Pass --------- N/A Timestamp/Logs -------------- N/A Test Activity ------------- N/A
2019-10-02 17:37:52 Ghada Khalil starlingx: importance Undecided Medium
2019-10-02 17:38:05 Ghada Khalil starlingx: assignee Tee Ngo (teewrs)
2019-10-02 17:38:10 Ghada Khalil bug added subscriber Bill Zvonar
2019-10-02 17:38:14 Ghada Khalil starlingx: status New Triaged
2019-10-02 17:38:23 Ghada Khalil tags stx.3.0 stx.config
2019-10-08 11:55:23 Bin Qian starlingx: assignee Tee Ngo (teewrs) Bin Qian (bqian20)
2019-10-08 11:55:38 Bin Qian starlingx: status Triaged In Progress
2019-10-09 12:38:25 OpenStack Infra starlingx: status In Progress Fix Released