In a nutshell, the guide would be
0) install vanilla Centos 7
1) install fuel-release package (it configures necessary yum repos)
rpm -Uvh fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm
2) install fuel-setup package
yum install fuel-setup
3) run bootstrap script (be aware, that bootstrap script reconfigures some
of system parameters)
I'll describe the whole procedure on the Fuel wiki page. Fuel deployment
procedure is to be improved in Ocata.
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.
On Mon, Sep 19, 2016 at 9:33 AM, Guo, Ruijing <ruijing....@intel.com> wrote:
> Hi, Vladimir
> Any guide to install from rpm?
> *From:* Vladimir Kozhukalov [mailto:vkozhuka...@mirantis.com]
> *Sent:* Tuesday, August 16, 2016 4:58 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> *Subject:* [openstack-dev] [Fuel] Getting rid of ISO
> Dear colleagues,
> We finally have working custom deployment job that deploys Fuel admin node
> using online RPM repositories (not ISO) on vanilla Centos 7.0.
> 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.
> I will infrom about our next steps here in the thread.
> Vladimir Kozhukalov
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)