<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Absolutely agree with Jay. Fuel is a community project.</div><div class="gmail_default" style="font-family:monospace,monospace">Please keep discussion public including technical details. </div><div class="gmail_default" style=""><font face="monospace, monospace"><br></font></div><div class="gmail_default" style=""><span style="font-family:monospace,monospace">Anyway, integration is welcome, please go ahead and </span><br></div><div class="gmail_default" style="font-family:monospace,monospace">create BP (btw, spec review request is the best place to</div><div class="gmail_default" style="font-family:monospace,monospace">discuss technical details).</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Fri, May 13, 2016 at 4:43 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/13/2016 07:26 AM, Andrian Noga wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Deepti,<br>
<br>
We have already a vision about Fuel-UI implementation for RSA.<br>
<br>
I've replied already to you in private email.<br>
<br>
Let's continue this thread in private conversation.<br>
</blockquote>
<br></span>
Please, no.<br>
<br>
Fuel is an OpenStack Big Tent project. The Fuel roadmap, feature set, and development MUST be discussed in public channels. If not, then Fuel does not meet one of the requirements for being in the OpenStack Big Tent, which is that the project will abide by the four Opens of OpenStack:<br>
<br>
<a href="https://wiki.openstack.org/wiki/Open" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Open</a><br>
<br>
Please note that Open Design, Open Community and Open Development mean that communication about the Fuel roadmap and development must be done on public mailing lists and discussion areas. This is a non-negotiable condition for being a member project in OpenStack's Big Tent.<br>
<br>
Thanks,<br>
-jay<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Fri, May 13, 2016 at 2:08 PM, <<a href="mailto:deepti.ramakrishna@intel.com" target="_blank">deepti.ramakrishna@intel.com</a><br></span><span class="">
<mailto:<a href="mailto:deepti.ramakrishna@intel.com" target="_blank">deepti.ramakrishna@intel.com</a>>> wrote:<br>
<br>
Hello Fuel team,<br>
<br>
I am a software engineer working in the OpenStack team at Intel. You<br>
may have heard of Rack Scale Architecture [1] that Intel is<br>
pioneering. It is a new data center architecture that "simplifies<br>
resource management and provides the ability to dynamically compose<br>
resources based on workload-specific demands". It is supported by<br>
multiple industry partners.<br>
<br>
We would like to propose Fuel integration with this. The first step<br>
would be UI integration [2] and we would like to have a tab similar<br>
to the VMWare tab (whose visibility is controlled by a config flag)<br>
that talks to the Redfish API [3] for displaying resources such as<br>
pods, racks, etc as exposed by this API. Note that Redfish API is an<br>
open industry standard API supported by multiple companies.<br>
<br>
I plan to write up a blueprint/spec for the same, but I wanted to<br>
know if there is any immediate feedback on this idea before I even<br>
get started.<br>
<br>
Thanks,<br>
Deepti<br>
<br>
[1]<br>
<a href="http://www.intel.com/content/www/us/en/architecture-and-technology/intel-rack-scale-architecture.html" rel="noreferrer" target="_blank">http://www.intel.com/content/www/us/en/architecture-and-technology/intel-rack-scale-architecture.html</a><br>
[2] <a href="http://i.imgur.com/vLJIbwx.jpg" rel="noreferrer" target="_blank">http://i.imgur.com/vLJIbwx.jpg</a><br>
[3] <a href="https://www.dmtf.org/standards/redfish" rel="noreferrer" target="_blank">https://www.dmtf.org/standards/redfish</a><br>
<br>
<br>
<br>
<br></span>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>