mirror of
https://github.com/clonos/control-pane.git
synced 2026-04-27 05:35:55 +03:00
[GH-ISSUE #19] Status view for fetching ISO #12
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/control-pane#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shithead on GitHub (Apr 5, 2019).
Original GitHub issue: https://github.com/clonos/control-pane/issues/19
For create a bhyve vm it doesnt show porgess of fetch iso image. That make sometimes confuse in which state clonos is for the VM.
@olevole commented on GitHub (Apr 5, 2019):
Yes, at the moment this problem exists. For this reason, this is mentioned here:
https://clonos.tekroutine.com/errata.html
Some commands already have a status update via queue ( CBSD used ws:// to send events directly in ClonOS ). But many commands do not yet have this support. Work is slow, but continues.
My current plan: make queue subsystem in CBSD more unversal, e.g. add queue.conf so that users can receive events in any backen - into redis, or AMQP (rabbit,beanstalk, zmq) or ws:// and so on and continue to implement support for progressbar/updates in atomic and long operations ( fetch, import, export, clone ..)
@olevole commented on GitHub (Apr 5, 2019):
By the way .. In CBSD there is a command fetch_iso ( https://www.bsdstore.ru/en/cbsd_fetch.html ) which can be used to pre-obtain images referenced by CBSD profiles,e.g:
(in latest CBSD, 12.0.8)
% cbsd fetch_iso dstdir=default keepname=0 cloud=0 ( for ISO )
% cbsd fetch_iso dstdir=default keepname=0 cloud=1 (for bhyve cloud images )
% cbsd fetch_iso dstdir=default keepname=0 cloud=1 conv2zvol=1 (for bhyve cloud images + auto convert them into ZVOL )
This can be used during the preparation of the hypervisor for work.