Hammer and questions on --compute-attributes for Libvirt

Support
1

Hi,
I'm just starting using hammer (0.0.9) for creating hosts on a Libvirt
provider, and I stumbled upon a couple of details regarding the keys to be
used in the --compute-attributes argument:

  1. The doc (
    https://github.com/theforeman/hammer-cli-foreman/blob/master/doc/host_create.md)
    says that "start" is a boolean key, and the Success Story (
    Bug #3297: CLI success story tracker - Hammer CLI - Foreman) has an example using it as
    "start=true". But in my tests "start=true" did not automatically start the
    host, I had to use "start=1" instead.
    Should I file a issue about it? Or is it ok the way it is now, and should
    the Success Story be fixed instead? (And maybe the doc updated, too)

  2. The "memory" key is said to accept a string which represents the value
    in bytes. But can it also be written as e.g. "2G", "768M" and so on, just
    like the "capacity" key for the --volume option? If so, then maybe the
    docs/help should be updated to reflect this. On the other hand, if this
    kind of notation is not possible for this key, maybe I should file a
    request issue ;).

Thanks.
Marco

2

Hi Marco,
thanks for your feedback!

> Hi,
> I'm just starting using hammer (0.0.9) for creating hosts on a Libvirt
> provider, and I stumbled upon a couple of details regarding the keys
> to be used in the --compute-attributes argument:
>
> 1. The doc
> (https://github.com/theforeman/hammer-cli-foreman/blob/master/doc/host_create.md)
> says that "start" is a boolean key, and the Success Story
> (Bug #3297: CLI success story tracker - Hammer CLI - Foreman) has an example using it
> as "start=true". But in my tests "start=true" did not automatically
> start the host, I had to use "start=1" instead.
> Should I file a issue about it? Or is it ok the way it is now, and
> should the Success Story be fixed instead? (And maybe the doc updated,
> too)
Yes, please do, we should fix it one way or the other.

>
> 2. The "memory" key is said to accept a string which represents the
> value in bytes. But can it also be written as e.g. "2G", "768M" and so
> on, just like the "capacity" key for the --volume option? If so, then
> maybe the docs/help should be updated to reflect this. On the other
> hand, if this kind of notation is not possible for this key, maybe I
> should file a request issue ;).
The memory size really has to be specified in bytes. I must admit it is
awkward, so please file a feature request for this.

Thanks for helping us to improve hammer user experience,

Martin

··· On 11/28/2013 01:51 PM, zerozerounouno@gmail.com wrote:

Thanks.
Marco

You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.