Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
On 2014/15/07 20:29, Gregory Haynes wrote:
Excerpts from Jaromir Coufal's message of 2014-07-15 07:15:12 +:
On 2014/10/07 22:19, Gregory Haynes wrote:
Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
Hey folks,
after few rounds of reviews and feedbacks, I am sending wireframes,
which are ready for implementation in Juno:
http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf
Let me know in case of any questions.
Looks awesome!
I may be way off base here (not super familiar with Tuskar) but what
about bulk importing of nodes? This is basically the only way devtest
makes use of nodes nowdays, so it might be nice to allow people to use
the same data file in both places (nodes.json blob).
-Greg
Hi Greg,
thanks a lot for the feedback. We planned to provide a bulk import of
nodes as well. First we need to provide the basic functionality. I hope
we also manage to add import function in Juno but it depends on how the
progress of implementation goes. The challenge here is that I am not
aware of any standardized way for the data structure of the imported
file (do you have any suggestions here?).
We currently accept a nodes.json blob in the following format:
[{
"pm_password": "foo",
"mac": ["78:e7:d1:24:99:a5"],
"pm_addr": "10.22.51.66",
"pm_type": "pxe_ipmitool",
"memory": 98304,
"disk": 1600,
"arch": "amd64",
"cpu": 24,
"pm_user": "Administrator"
},
...
]
So this might be a good starting point?
-Greg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks Greg, that's a good starting point. We will need to create a
blueprint in Horizon's launchpad for it - would you mind to register one
with above mentioned format?
-- Jarda
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Hi Wan, thanks for great notes. My response is inline: On 2014/15/07 23:19, Wan-yen Hsu wrote: The "Register Nodes" panel uses "IPMI user" and "IPMI Password". However, not all Ironic drivers use IPMI, for instance, some Ironic drivers will use iLO or other BMC interfaces instead of IPMI. I would like to suggest changing "IPMI" to "BMC" or ""IPMI/BMC" to acomodate more Ironic drivers. The "Driver" field will reflect what power management interface (e.g., IPMI + PXE, or iLO + Virtual Media) is used so it can be used to correlate the user and password fields. We are already prepared for multiple drivers. If you look at the Driver field, there is a dropdown menu from which you can choose a driver and based on the selection the additional information (like IP, user, passw) will be changed. Also, myself and a few folks are working on Ironic UEFI support and we hope to land this feature in Juno (Spec is still in review state but the feature is on the Ironic Juno Prioritized list). In order to add UEFI boot feature, a "Supported Boot Modes" field in the hardware info is needed. The possible values are "BIOS Only", "UEFI Only", and "BIOS+UEFI". We will need to work with you to add this field onto hardware info. There is no problem to accommodate this change in the UI once the back-end supports it. So if there is a desire to expose the feature in the UI, when there is already working back-end solution, feel free to send a patch which adds that to the HW info - it's an easy addition and the UI is prepared for such types of expansions. Thanks! wanyen Cheers -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Hi Jaromir, > Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +: >> Hey folks, >> >> after few rounds of reviews and feedbacks, I am sending wireframes, >> which are ready for implementation in Juno: >> >> http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf >> >> Let me know in case of any questions. >> This looks great! I have a couple comments- The "Register Nodes" panel uses "IPMI user" and "IPMI Password". However, not all Ironic drivers use IPMI, for instance, some Ironic drivers will use iLO or other BMC interfaces instead of IPMI. I would like to suggest changing "IPMI" to "BMC" or ""IPMI/BMC" to acomodate more Ironic drivers. The "Driver" field will reflect what power management interface (e.g., IPMI + PXE, or iLO + Virtual Media) is used so it can be used to correlate the user and password fields. Also, myself and a few folks are working on Ironic UEFI support and we hope to land this feature in Juno (Spec is still in review state but the feature is on the Ironic Juno Prioritized list). In order to add UEFI boot feature, a "Supported Boot Modes" field in the hardware info is needed. The possible values are "BIOS Only", "UEFI Only", and "BIOS+UEFI". We will need to work with you to add this field onto hardware info. Thanks! wanyen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Excerpts from Jaromir Coufal's message of 2014-07-15 07:15:12 +:
> On 2014/10/07 22:19, Gregory Haynes wrote:
> > Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
> >> Hey folks,
> >>
> >> after few rounds of reviews and feedbacks, I am sending wireframes,
> >> which are ready for implementation in Juno:
> >>
> >> http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf
> >>
> >> Let me know in case of any questions.
> >>
> >
> > Looks awesome!
> >
> > I may be way off base here (not super familiar with Tuskar) but what
> > about bulk importing of nodes? This is basically the only way devtest
> > makes use of nodes nowdays, so it might be nice to allow people to use
> > the same data file in both places (nodes.json blob).
> >
> > -Greg
>
> Hi Greg,
>
> thanks a lot for the feedback. We planned to provide a bulk import of
> nodes as well. First we need to provide the basic functionality. I hope
> we also manage to add import function in Juno but it depends on how the
> progress of implementation goes. The challenge here is that I am not
> aware of any standardized way for the data structure of the imported
> file (do you have any suggestions here?).
>
>
We currently accept a nodes.json blob in the following format:
[{
"pm_password": "foo",
"mac": ["78:e7:d1:24:99:a5"],
"pm_addr": "10.22.51.66",
"pm_type": "pxe_ipmitool",
"memory": 98304,
"disk": 1600,
"arch": "amd64",
"cpu": 24,
"pm_user": "Administrator"
},
...
]
So this might be a good starting point?
-Greg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Hi Devananda, thank you for your great feedback and notes. Few reactions follow inline: On 2014/10/07 21:29, Devananda van der Veen wrote: Awesome! Glad to see the progress since the design summit. Some comments: - slide 1 shows some driver-specific input fields. We have work in progress to expose this list via the API which I'm hoping to land in J2 or very early in J3. https://review.openstack.org/#/c/102914/ That should help the UI keep up with new drivers and/or changes in driver-specific fields. Perfect, this will be very helpful. - I have proposed adding an additional "capabilities" field to node.properties, to enable users who wish to have more fine-grained control of instance placement than merely matching on cpu/ram/disk/arch. https://review.openstack.org/#/c/105802/ you may want to add this as an optional field. I am super excited that this field is getting in since we discussed this at the summit. We will build the basic set of fields first but I will keep an eye on adding this extra field as an extension later. But that's really great that we give user more fine-grained control! - on slide 1, the "NIC MAC address" field doesn't clearly indicate that it can accept more than one NIC's info, while this is demonstrated in the detail view on slide 6. Based on feedback, I provided text area instead of "+" button to adding more. But probably we should change naming on "NIC MAC Adresses" and we should also add a tooltip for the format of the input. - slides 5 and 6 shows data about "system load, cpu, and swap utilization" from provisioned nodes. AIUI, is a feature specific to Tuskar/TripleO that relies on an agent within the provisioned nodes, and is not a part of Ironic. While useful within that context, the UI for Ironic can not expect that information to be present, and in a non-TripleO environment using Ironic (eg, OnMetal, an HPC cluster, etc) it's not clear how the proposed UI for these two slides will look. So the thing is that these metrics are given by SNMP which is the source for them. If there are any other metrics or the Ceilometer agent is not available, the UI is modular, so the graphs can be extended, swapped or even removed if needed. We believe that these are basic metrics what we can easily get from Ceilometer and start with for now. We are very keen to extend those in the future. Cheers, Devananda Cheers, -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
On 2014/10/07 22:19, Gregory Haynes wrote: Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +: Hey folks, after few rounds of reviews and feedbacks, I am sending wireframes, which are ready for implementation in Juno: http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf Let me know in case of any questions. Looks awesome! I may be way off base here (not super familiar with Tuskar) but what about bulk importing of nodes? This is basically the only way devtest makes use of nodes nowdays, so it might be nice to allow people to use the same data file in both places (nodes.json blob). -Greg Hi Greg, thanks a lot for the feedback. We planned to provide a bulk import of nodes as well. First we need to provide the basic functionality. I hope we also manage to add import function in Juno but it depends on how the progress of implementation goes. The challenge here is that I am not aware of any standardized way for the data structure of the imported file (do you have any suggestions here?). -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +: > Hey folks, > > after few rounds of reviews and feedbacks, I am sending wireframes, > which are ready for implementation in Juno: > > http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf > > Let me know in case of any questions. > Looks awesome! I may be way off base here (not super familiar with Tuskar) but what about bulk importing of nodes? This is basically the only way devtest makes use of nodes nowdays, so it might be nice to allow people to use the same data file in both places (nodes.json blob). -Greg -- Gregory Haynes g...@greghaynes.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Awesome! Glad to see the progress since the design summit. Some comments: - slide 1 shows some driver-specific input fields. We have work in progress to expose this list via the API which I'm hoping to land in J2 or very early in J3. https://review.openstack.org/#/c/102914/ That should help the UI keep up with new drivers and/or changes in driver-specific fields. - I have proposed adding an additional "capabilities" field to node.properties, to enable users who wish to have more fine-grained control of instance placement than merely matching on cpu/ram/disk/arch. https://review.openstack.org/#/c/105802/ you may want to add this as an optional field. - on slide 1, the "NIC MAC address" field doesn't clearly indicate that it can accept more than one NIC's info, while this is demonstrated in the detail view on slide 6. - slides 5 and 6 shows data about "system load, cpu, and swap utilization" from provisioned nodes. AIUI, is a feature specific to Tuskar/TripleO that relies on an agent within the provisioned nodes, and is not a part of Ironic. While useful within that context, the UI for Ironic can not expect that information to be present, and in a non-TripleO environment using Ironic (eg, OnMetal, an HPC cluster, etc) it's not clear how the proposed UI for these two slides will look. Cheers, Devananda On Wed, Jul 9, 2014 at 12:51 AM, Jaromir Coufal wrote: > Hey folks, > > after few rounds of reviews and feedbacks, I am sending wireframes, which > are ready for implementation in Juno: > > http://people.redhat.com/~jcoufal/openstack/juno/2014- > 07-09_nodes-ui_juno.pdf > > Let me know in case of any questions. > > Cheers > -- Jarda > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno
Hey folks, after few rounds of reviews and feedbacks, I am sending wireframes, which are ready for implementation in Juno: http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf Let me know in case of any questions. Cheers -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
