[ovs-dev] [PATCH 2/2] ovn: Support chassis hostname in requested-chassis.

[Miguel Angel Ajo Pelayo]

I was thinking that it could have been convenient to do it that way in:

https://github.com/openvswitch/ovs/blob/master/ovn/ovn-nb.ovsschema#L315

But we picked up chassis_name instead, not sure if it'd make any sense to
use the hostname instead, it'd be much nicer for listing, so you can just
see the host and avoid the mental exercise of cross referencing the uuid to
the chassis.

On Wed, Sep 6, 2017 at 11:16 PM, Russell Bryant <russell at ovn.org> wrote:

> On Tue, Sep 5, 2017 at 3:45 PM, Lance Richardson <lrichard at redhat.com>
> wrote:
> >> From: "Russell Bryant" <russell at ovn.org>
> >> To: dev at openvswitch.org
> >> Cc: lrichard at redhat.com, "Russell Bryant" <russell at ovn.org>
> >> Sent: Friday, September 1, 2017 9:14:10 PM
> >> Subject: [PATCH 2/2] ovn: Support chassis hostname in requested-chassis.
> >>
> >> Previously, OVN expected the Chassis "name" in the "requested-chassis"
> >> option for a Logical_Switch_Port.  It turns out that in the two OVN
> >> integrations I've checked with that plan to use this option,
> >> specifying the Chassis "hostname" is much more convenient.  This patch
> >> extends the "requested-chassis" option to support both the Chassis
> >> name or the hostname as a value.
> >>
> >> Signed-off-by: Russell Bryant <russell at ovn.org>
> >> ---
> >
> > LGTM.
> >
> > Acked-by: Lance Richardson <lrichard at redhat.com>
>
> Thanks.  I added a note to NEWS and then applied this to master and
> branch-2.8.
>
> --
> Russell Bryant
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>