zVM Cloud Connector

IFL type of CPU define

Bug #1747830 reported by jichenjc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zVM Cloud Connector
Confirmed
Low
jichenjc
zVM Cloud Connector future

Bug Description

we have something like following in smutLayer/makeVM.py

 90 rh.printSysLog("Enter makeVM.createVM")
.....
 98 dirLines.append("CPU 00 BASE")

this means our CPU will always be created as CP and won't be able to switch to IFL

we have to do something like following to force IFLs in VM Mode LPAR with both CPs and IFLs:

USER user password 2048M 2048M G
   COMMAND SET VCONFIG MODE LINUX
   COMMAND DEFINE CPU 00 TYPE IFL
   MACHINE Z 32

so we need provide
1) default IFL if IFL exists in the LPAR
2) provide configuration to let user able to choose IFL / CP during deploy phase (default to IFL if IFL exist)

jichenjc (jichenjc)
Changed in python-zvm-sdk:
assignee: nobody → jichenjc (jichenjc)
Revision history for this message
Huang Rui (bjhuangr) wrote :

Can we just suggest user to add the IFL statement into profile, then all the userids can include it.

Revision history for this message
jichenjc (jichenjc) wrote :

maybe, through API input might provide better flexiblity ? don't yet, anyway, will provide some update after the busy season of release 1.0.0

Huang Rui (bjhuangr)
Changed in python-zvm-sdk:
milestone: none → future
jichenjc (jichenjc)
Changed in python-zvm-sdk:
status: New → Confirmed
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.