<div dir="ltr">Hi Zhijiang<div><br></div><div>I think you can put Daisy into docker, then use ansible or kolla deploy Daisy.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 31, 2016 at 9:43 AM, <span dir="ltr"><<a href="mailto:hu.zhijiang@zte.com.cn" target="_blank">hu.zhijiang@zte.com.cn</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">Hi All,</font>
<br>
<br><font size="2" face="sans-serif">I would like to introduce to you a new
OpenStack installer project Daisy(project name: daisycloud-core). Daisy
used to be a closed source project mainly developed by ZTE, but currently
we make it a OpenStack related project(</font><a href="http://www.daisycloud.org/" target="_blank"><font size="2" face="sans-serif">http://www.daisycloud.org</font></a><font size="2" face="sans-serif">,
</font><a href="https://github.com/openstack/daisycloud-core" target="_blank"><font size="2" face="sans-serif">https://github.com/openstack/daisycloud-core</font></a><font size="2" face="sans-serif">).
</font>
<br>
<br><font size="2" face="sans-serif">Although it is not mature and still
under development, Daisy concentrates on deploying OpenStack fast and efficiently
for large data center which has hundreds of nodes. In order to reach that
goal, Daisy was born to focus on many features that may not be suitable
for small clusters, but definitely conducive to the deployment of big clusters.
Those features include but not limited to the following: </font>
<br>
<br><font size="2" face="sans-serif">1. Containerized OpenStack Services
</font>
<br><font size="2" face="sans-serif">In order to speed up installation and
upgrading as a whole, Daisy decides to use Kolla as underlying deployment
module to support containerized OpenStack services. </font>
<br>
<br><font size="2" face="sans-serif">2. Multicast </font>
<br><font size="2" face="sans-serif">Daisy utilizes multicast as much as
possible to speed up imaging work flow during the installation. For example,
instead of using centralized Docker registry while adopting Kolla, Daisy
multicasts all Docker images to each node of the cluster, then creates
and uses local registries on each node during Kolla deployment process.
The Same things can be done for OS imaging too. </font>
<br>
<br><font size="2" face="sans-serif">3. Automatic Deployment </font>
<br><font size="2" face="sans-serif">Instead of letting users decide if a
node can be provisioned and deserved to join to the cluster, Daisy provide
a characteristics matching mechanism to recognize if a new node has the
same capabilities as a current working computer nodes. If it is true, Daisy
will start deployment on that node right after it is discovered and make
it a computer node with the same configuration as that current working
computer nodes. </font>
<br>
<br><font size="2" face="sans-serif">4. Configuration Template </font>
<br><font size="2" face="sans-serif">Using precise configuration file to
describe a big dynamic cluster is not applicable, and it is not able to
be reused when moving to another approximate environment either. Daisy’s
configuration template only describes the common part of the cluster and
the representative of the controller/compute nodes. It can be seen as a
semi-finished configuration file which can be used in any approximate environments.
During deployment, users only have to evaluate few specific parameters
to make the configuration template a final configuration file. </font>
<br>
<br><font size="2" face="sans-serif">5. Your comments on anything else that
can brings unique value to the large data center deployment? </font>
<br>
<br><font size="2" face="sans-serif">As the project lead, I would like to
get feedback from you about this new project. You are more than welcome
to join this project! </font>
<br>
<br><font size="2" face="sans-serif">Thank you </font>
<br><font size="2" face="sans-serif">Zhijiang<br>
</font>
<br><pre><font color="blue">
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
</font></pre><br>
<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>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Shake Chen<br><br></div>
</div>