Open Stack

For the package-based deployment, we need to get rid of 'deployment script'
whatsoever. All configuration stuff should be done in package specs, or by
the user later on (maybe via some fuelmenu-like lightweight UI, or via
WebUI).

Thus, fuel package must install everything that is required for running
base Fuel as it's dependencies (or dependencies of it's dependencies, as it
could be more complicated with cross-deps between our components).

--
Best regards,
Oleg Gelbukh

On Fri, Dec 11, 2015 at 10:45 PM, Vladimir Kozhukalov <
vkozhukalov at mirantis.com> wrote:

> Dear colleagues,
>
> At the moment part of the Fuel master deployment logic is located in ISO
> kickstart file, which is bad. We'd better carefully split provisioning and
> deployment stages so as to install base operating system during
> provisioning stage and then everything else on the deployment stage. That
> would make it possible to deploy Fuel on pre-installed vanilla Centos 7.
> Besides, if we have deb packages for all Fuel components it will be easy to
> support Fuel deployment on pre-installed Ubuntu and Debian.
>
> We (Fuel build team) are going to do this ASAP [0]. Right now we are on
> the stage of writing design spec for the change [1].
>
> Open questions are:
> 1) Should fuel package have all other fuel packages like nailgun, astute,
> etc. as its dependencies? Or maybe it should install only puppet modules
> and deployment script that then could be used to deploy everything else?
>
> 2) bootstrap_admin_node.sh runs fuelmenu and then puppet to deploy Fuel
> components. Should we run this script as post-install script or maybe we
> should leave this up to a user to run this script later when fuel package
> is already installed?
>
> Anyway, the final goal is to make ISO just one of possible delivery
> schemes. Primary delivery approach should be rpm/deb repo, not ISO.
>
> [0]
> https://blueprints.launchpad.net/fuel/+spec/separate-fuel-node-provisioning
> [1] https://review.openstack.org/#/c/254270/
>
> Vladimir Kozhukalov
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151211/8a61e169/attachment.html>