<div dir="ltr"><div style="font-family:monospace,monospace" class="gmail_default">Ruijing,<br><br></div><div style="font-family:monospace,monospace" class="gmail_default">In a nutshell, the guide would be <br></div><div style="font-family:monospace,monospace" class="gmail_default">0) install vanilla Centos 7<br></div><div style="font-family:monospace,monospace" class="gmail_default">1) install fuel-release package (it configures necessary yum repos)<br></div><div style="font-family:monospace,monospace" class="gmail_default">wget <a href="http://packages.fuel-infra.org/repositories/centos/master-centos7/snapshots/os-2016-09-19-093900/x86_64/Packages/fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm">http://packages.fuel-infra.org/repositories/centos/master-centos7/snapshots/os-2016-09-19-093900/x86_64/Packages/fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm</a><br></div><div style="font-family:monospace,monospace" class="gmail_default">rpm -Uvh fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm<br></div><div style="font-family:monospace,monospace" class="gmail_default">2) install fuel-setup package<br></div><div style="font-family:monospace,monospace" class="gmail_default">yum install fuel-setup<br></div><div style="font-family:monospace,monospace" class="gmail_default">3) run bootstrap script (be aware, that bootstrap script reconfigures some of system parameters)<br></div><div style="font-family:monospace,monospace" class="gmail_default">/usr/sbin/bootstrap_admin_node.sh<br><br></div><div style="font-family:monospace,monospace" class="gmail_default">I'll describe the whole procedure on the Fuel wiki page. Fuel deployment procedure is to be improved in Ocata. <br><br>Regarding your previous question about docker image, we are not planning to provide a single Fuel docker image (docker containers are not VMs). Container is an isolated process and Fuel assumes we run multiple processes (API, RPC, etc.). Given that, Fuel should be a set of docker containers. We used to run Fuel in containers, but those were kind of mess when we ran puppet when building images and we put those images inside rpms and inside ISO. We definitely don't want to have something like this again. But if you use Docker images that are built from pure Dockerfiles (not using puppet, from source code) and publishing them on docker registry that could be a way to provide development environment (for plugin developers it could be super convenient). Yes, that was in our plans for Newton, but we didn't manage to implement this. Maybe in Ocata.<br></div><div style="font-family:monospace,monospace" class="gmail_default"><br><br><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Mon, Sep 19, 2016 at 9:33 AM, Guo, Ruijing <span dir="ltr"><<a href="mailto:ruijing.guo@intel.com" target="_blank">ruijing.guo@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi, Vladimir<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Any guide to install from rpm?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-Ruijing<a name="m_5552778026586637271__MailEndCompose"><u></u><u></u></a></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vladimir Kozhukalov [mailto:<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@mirantis.<wbr>com</a>]
<br>
<b>Sent:</b> Tuesday, August 16, 2016 4:58 PM<span class=""><br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<wbr>openstack.org</a>><br>
</span><b>Subject:</b> [openstack-dev] [Fuel] Getting rid of ISO<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Courier New"">Dear colleagues,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">We finally have working custom deployment job that deploys Fuel admin node using online RPM repositories (not ISO) on vanilla Centos 7.0.
<br>
<br>
Currently all Fuel system and deployment tests use ISO and we are planning to re-implement all these jobs (including BVT, SWARM, and Fuel CI jobs) to exclude ISO from the pipeline. That will allow us to get rid of ISO as our deliverable and instead rely totally
on package repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are already delivered via ISO/qcow2/etc. images and we'd better stop reinventing a wheel and support our own ISO build code. That will allow us to make Fuel admin node deployment
more flexible.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">I will infrom about our next steps here in the thread.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New""><br clear="all">
<u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Vladimir Kozhukalov<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>