Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
jclouds-dev (DEPRECATED)
Home
About this group
Contact owner to join
Message from discussion Virtualbox implementation
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post will appear after it is approved by moderators
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Adrian Cole  
View profile  
 More options Dec 14 2011, 12:05 pm
From: Adrian Cole <adrian.f.c...@gmail.com>
Date: Wed, 14 Dec 2011 09:05:33 -0800
Local: Wed, Dec 14 2011 12:05 pm
Subject: Re: Virtualbox implementation
Print | View thread | Show original | Report this message | Find messages by this author
Thanks for the update, Andrei.  and kudos to you and Mattias for
carrying this forward.

Thanks for the info about what works vs doesn't, and bringing
visibility to what you are doing.

comments inline.

On Wed, Dec 14, 2011 at 6:55 AM, Andrea <andrea.tu...@gmail.com> wrote:
> Since a bunch of months me, Adrian and Mattias are working hard to release
> the jclouds virtualbox api.

> I've finally discovered that vbox CLI used vbox API to offer all the
> operations - vboxmanage CLI - and probably this will speed up our
> implementation:

particularly where this is modeled in a way that we can switch to API later.

> In particular:

> VirtualBoxManager.getSessionObject().getConsole().getGuest().executeProcess (execName,
> flags, arguments, environment, userName, password, timeoutMS, pid)
> will be useful to export ip address instead of using a Statement like the
> one we have at the moment based on vboxmanage guestproperty enumerate
> "$VMNAME" --patterns "/VirtualBox/GuestInfo/Net/0/V4/IP" | awk '{ print $4
> }' | cut -c 1-14.
> and to remove the udev crap from the vm, for debian-based os.

The above seems like better modeled as an API call, as metadata such
as IP address info surely must be in a domain object somewhere, right?
 In general, I get the idea, though: progress before perfection.

I might consider making a version of RunScriptOnNode that works with
VBoxManager, too.

> Unfortunately it will not help us using:

> VirtualBoxManager.getSessionObject().getConsole().getGuest().updateGuestAdd itions(source,
> flags)
> cause according to the vbox devs this feature is buggy.

So, what's the alternative here?  running a script?

> Ciao,
> Andrea

> --
> You received this message because you are subscribed to the Google Groups
> "jclouds-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/jclouds-dev/-/jJ8t4mFo4PAJ.
> To post to this group, send email to jclouds-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> jclouds-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/jclouds-dev?hl=en.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google