> First, demo looked good!!!
> Just catching up on the deep dive from yesterday, a few comments in random
> * when creating a new host, all attributes in the primary tab are auto
> populated with the hostgroup excluding the realm, maybe since its less used
> feature move it to bellow the puppet fields?
I'd be fine with that change, we could even hide it when no realms are
configured, same as for some other fields.
> * network tab has a header called interfaces, are we going to show any non
> interface data in there? we can drop the header maybe?
Good point, Tomas?
> * table view of interfaces does not show the ip initially, but when you edit
> it, its already visible?
Probably just a JS issue, I'll check it.
> * do i really need to edit each time the primary interface? ideally i dont
> want to click on edit if i use the default?
No, you don't need to, if all the defaults are correct. I chose to
demo multi-nic provisioning just because thats the main usecase we're
trying to solve, but for a single-nic system with a hostgroup, you can
just carry on as normal and pretty much ignore the network tab
(excepting the annoying identifier matchup for libvirt/ovirt systems,
> * host/show nics details, is there a hover or text defining the interface
> type? at least until people learn how to recognize the icon?
There should be, if it doesn't show for you let us know
> * redirect problem ?
Known issue, we're not currently sure what's causing it.
> * something i didn't catch, did we move the build status to the primary
> interface or is it still an host attribute?
Still a host attribute, we felt it didn't make sense for 50% of a host
to be in build state
> * any idea how / if the API will change?
Untested yet, but should be similar to how we handle other collections
(eg puppet classes) via nested attributes. It's on my list for this
On 2 December 2014 at 08:59, Ohad Levy wrote:
On 2 December 2014 at 10:48, Claer email@example.com wrote:
Is it possible to add static routes for NIC properties when you dont use
DHCP for a specific interface ?
We’ve not added anything like that to the Nic model at this point -
there are some extra fields that I didn’t show for bonds/aliases, but
these won’t help your use case. I’m wary of making the Nic modal even
bigger than it already is, but if there’s demand for it, of course it
can be done
Thanks for the feedback guys