-
On Folsom, heat-jeos will always try to delete the first available image before adding a new one. It should only delete the one with the same name, if it exists.
zaneb updated
11 years ago
-
It would be really nice if Oz exposed a reasonably stable API so that Python programs didn't have to shell out to build images.
It's already possible to import `oz.TDL` and `oz.GuestFactory` and do t…
-
This is a fork of the #1848 issue.
When importing the pool without the 'zvol_inhibit_dev' parameter, I get (after a few minutes) an oops from first zpool, txg_sync and then vol_id (from udev, NOT the…
-
Add more examples on tests.cfg, with pointers to online docs explaining better how to tune test sets to their likings.
-
unless you know the location of the images you don't know the location of it.
Also what is the point of register? Isn't using glance just as easy?
How about:
```
sudo -E heat-jeos image F16 x86_64 …
-
Steps:
Checkout the `usability` branch.
Build the image:
```
sudo -E ./bin/heat-jeos -d -y create F16-x86_64-cfntools-jeos --register-with-glance
```
Launch a stack:
```
./bin/heat -d create word…
-
This way we'll spare the user from a 4GB download and a lot of time executing the default test set.
-
Put those images on some directory that can be used by get_started.py to pull up them and get people started with kvm autotest. No more 4GB iso downloads.
-
I believe @clebergnu has some prior art on that. Putting this issue here to track the work.
-
Here's the log when this happened. The irc session was stuck, the bot tried to reconnect, but failed to register.
```
=ERROR REPORT==== 5-Oct-2010::00:43:28 ===
No activity for more than 180000 micro…