openstack team mailing list archive

[Nathanael Burton <nathanael.i.burton@xxxxxxxxx>]

While at a minimum this is a doc bug, I would suggest we do one of the
following:

1. Rename existing parameters that require the value to be an ip address
such as 'metadata_host' to 'metadata_host_ip' so that it is more obvious.
Make this a standard for all config parameters.

2. I agree with Lars, it would be even better if it was seamless
(regardless of what was set, host or IP) and where we require IP addresses,
do resolution.

Nate
On Jun 28, 2012 7:55 PM, "Matt Joyce" <matt.joyce@xxxxxxxxxxxxxxxx> wrote:

> +1
>
> On Thu, Jun 28, 2012 at 2:27 PM, Vishvananda Ishaya <vishvananda@xxxxxxxxx
> > wrote:
>
>> those are supposed to be ip addresses, so I would go with doc bug now
>> unless there is a good reason to change it.
>>
>> Vish
>>
>> On Jun 28, 2012, at 12:00 PM, Lars Kellogg-Stedman wrote:
>>
>> > Maybe I sent this out too late at night; I think it slipped below
>> > everyone's radar.  I'm interested in whether or not people think this
>> > behavior is a functional bug, or maybe just a documentation bug:
>> >
>> >> I ran into an issue earlier today where I had metadata_host set to the
>> >> *hostname* of our controller.  This got stuffed into an iptables rule
>> >> as...
>> >>
>> >>  -d os-controller.int.seas.harvard.edu/32
>> >>
>> >> ...which promptly failed.  Setting this to an ip address fixed this
>> >> particular error, leading me to wonder:
>> >>
>> >> - Is this expected behavior?
>> >> - Should I always use ip addresses for *_host values?
>> >> - Is this a bug?
>> >> - Should linux_net.py resolve hostnames?
>> >
>> > --
>> > Lars Kellogg-Stedman <lars@xxxxxxxxxxxxxxxx>       |
>> > Senior Technologist                                |
>> http://ac.seas.harvard.edu/
>> > Academic Computing                                 |
>> http://code.seas.harvard.edu/
>> > Harvard School of Engineering and Applied Sciences |
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>