I am trying to figure out how to script some vmadm commands in a bash script.
For a basic scenario, the bash script calls vmadm to create a VM and that works
fine. However, I am trying to capture the UUID of the newly created VM.
I receive the following message on the screen:
"Successfully
* On 2018-02-02 at 18:24 GMT, George Linn via smartos-discuss wrote:
> I am trying to figure out how to script some vmadm commands in a bash
> script. For a basic scenario, the bash script calls vmadm to create a VM and
> that works fine. However, I am trying to capture the UUID of the newly
In addition to looking it up, you can also set the "uuid" field in the
payload. The VM will be created using that UUID instead of generating
a new one. You can use the uuidgen program to generate a valid UUID
inside your shell script.
On Fri, Feb 2, 2018 at 10:46 AM, Jonathan Perkin
Gareth Howell writes:
> I rebooted in to recovery mode and swapped the pools as suggested. The
> system now boots using the new ones pool but it fails to start the local
> file system service and all those that rely on it.
> The cause is some cruft in the /zones folder that prevents /zones
Got it. Thank you.
George
On Friday, February 2, 2018, 2:08:06 PM EST, Cody Mello
wrote:
In addition to looking it up, you can also set the "uuid" field in the
payload. The VM will be created using that UUID instead of generating
a new one. You can use the uuidgen
On 2 Feb 2018, at 20:43, George Linn via smartos-discuss wrote:
Just out of curiosity, from a bash script the following works as
expected:
/usr/sbin/vmadm list | /usr/bin/grep myzonealias | /usr/bin/cut -d" "
-f1
This doesn't answer your question about additional processes, but the
above
On 2 February 2018 at 11:59, Paul Sture wrote:
> /usr/sbin/vmadm list -Ho uuid alias=myzonealias
Even better is probably: "vmadm lookup -1 alias=myzonealias"
--
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org
---
While this might be slightly off, these things can be handled in Ansible
in a fairly elegant manner OOTB now.
T.
On 2018-02-03 00:16, Cody Mello wrote:
> On Fri, Feb 2, 2018 at 11:43 AM, George Linn via smartos-discuss
> wrote:
>> The following does not work:
Building a new platform image using a fork of smartos-live that uncomments the
option for unfiltered promisc seems to solve the problem. A bit of a
complicated solution to the problem (I guess I am tying myself to a lifetime of
smartos compilations) but it works and seems less of a hack than
Quick update on this.
I rebooted in to recovery mode and swapped the pools as suggested. The
system now boots using the new ones pool but it fails to start the local
file system service and all those that rely on it.
The cause is some cruft in the /zones folder that prevents /zones mounting.
10 matches
Mail list logo