Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to add a serial port to a VM #25

Closed
JonKohler opened this issue Jan 30, 2019 · 0 comments · Fixed by #45
Closed

Ability to add a serial port to a VM #25

JonKohler opened this issue Jan 30, 2019 · 0 comments · Fixed by #45
Labels
v1.1.0 Provider Version 1.1.0

Comments

@JonKohler
Copy link
Collaborator

Moved from #159

The situation as reported by leonteq:

when using Ubuntu 16.04 cloud image, like the one you’d deploy in aws/azure/etc:

  • The image is built with enabled output on serial port; if the VM has no serial port, there’s a very long pause before it times out and moves on
  • We fixed it by removing the serial port dependency in the image
  • The other workaround is to manually create serial port on the VM and restart

Answer from Jon

We’ve got the ability to do this in the code already in the v3 API that will ship with AOS 5.9, which is due out later this year. When that hits, serial_port_list will be the array you’d call configure the serial_port, just like you’d do to configure a NIC with nic_list or DISK with disk_list

The particular feature that was tied too is unlikely to be backported to 5.6/5.8 (which BTW 5.8 is coming out this week), so we’ll need to wait for that API to have terraform hook into it.

This is similar to the issue about resizing disks, the API support is now there in 5.9+, and 5.10 as such, so we'll need to validate and make sure its documented correctly here.

@marinsalinas marinsalinas added the v1.1.0 Provider Version 1.1.0 label Apr 26, 2019
abhimutant added a commit that referenced this issue Dec 9, 2024
* address groups v4

* service groups

* resource for service groups

* crud for service groups

* CRUD for address groups

* data source for network security

* CRUD for network security

* microseg sdk pointing to internals

* datasource for directory services

* CRUD for directory service

* datasource for saml

* CRUD for idp

* delete Operation for directory service

* CRUD for user groups

* datasource for categories

* Crud and tcs for categories

* crud & test for images

* sdk versioning

* templates datasource

* datasource for template versions

* deploy templates

* spec for vms

* info for volume Groups

* add targetPrefix atrribute to volume group/s schema

* create Ops

* CRUD for volume group, Change the names of imported packages to more declarative names.

* CUD ops done

* Get VMs

* fix update for Volume group, working on volume disk -> info done, CRUD there is a bug on update func  CRD works as expected

* VMs

* CRUD for vm disks

* volume group disk CRUD done, fix schema attribute for Vg

* CRUD/ds serial ports

* cdrom CRUD

* insert/eject cdrom

* vm actions power

* List available iscsi clients + Attach/Detach iscsi client to vg

* merge conflict

* Revert "merge conflict"

This reverts commit 7b8edb9e177ed96b19d2d8e0fde52e37647502e8.

* List all the category details that are associated with the Volume Group.

* Attach/Detach an AHV VM from the given Volume Group.

* Iscsi Clients Provider, Fetch an iSCSI client details, List all the iSCSI clients.

* revert pushed unwanted changes

* revert pushed unwanted changes

* acc test for volume group data source and resource

* acceptance test for volume group data source

* volume group data source acctest is done

* acceptance test for volume resource modules, ->  acceptance test done

* Add Description for schema attribute's

* List all the VM attachments for a Volume Group INFO -> Development + Test

* Volume Group examples

* Doc for Volume groups & Attach/Dettach vg to vm

* Docs for Volume Group vm, volume group  iscsi client, available  iscsi clients, Volume Group disks and volume group category info

* refactor volumes test cases to use test_config_v4.json

* revert pushed unwanted changes

* add test_config_v4.json file

* refactor volumes test cases to use test_config_v4.json

* rename volume module from v4 to v2

* Refactor acceptance test cases to be more dynamic and reduce dependency on the JSON configuration file

* rename volume package to volumesv2

* remove other modules

* add examples

* add examples

* ignore vendor

---------

Co-authored-by: Abhishek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.1.0 Provider Version 1.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants