You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Determine correct format for creating LX branded zones via VMAPI (documentation needed) [primary]
Recommend improved documentation [optional]
For OS machines, LX-branded zones and KVM, a quick getting started with an example command and insights on sources for required inputs (e.g. billing_uuid, owner_uuid), would allow new API users to ramp up quickly.
Recommend JSON equivalence across VMADM/VMAPI [optional]
While this may have been considered, being able to specify the same JSON for vmadm as vmapi would create for a much easier transition in using vmapi. Considerations for error messages based on each variable presented in vmadm create JSON (e.g. nics vs networks) would allow users to ramp up quickly.
The text was updated successfully, but these errors were encountered:
Thanks for the response/insights. This may be helpful, currently the docs suggest developing and/or integrating with vmapi is a desired goal. An update to the docs with a reference to the other APIs and a link to their documentation may make it easier to develop in the environment.
Currently, when issuing a command to Triton via VMAPI to create a LX branded zone, the POST fails with the following error:
Creating an OS VM with similar specified parameters works well.
See https://gist.github.com/kriss9/8534033c9ed2179bea807816312f680c
This request is to
Determine correct format for creating LX branded zones via VMAPI (documentation needed) [primary]
Recommend improved documentation [optional]
For OS machines, LX-branded zones and KVM, a quick getting started with an example command and insights on sources for required inputs (e.g. billing_uuid, owner_uuid), would allow new API users to ramp up quickly.
Recommend JSON equivalence across VMADM/VMAPI [optional]
While this may have been considered, being able to specify the same JSON for vmadm as vmapi would create for a much easier transition in using vmapi. Considerations for error messages based on each variable presented in
vmadm create
JSON (e.g. nics vs networks) would allow users to ramp up quickly.The text was updated successfully, but these errors were encountered: