fuel-dev team mailing list archive

[<samuel.bartel@xxxxxxxxxx>]

Hello Dimitry, 
Thanks it help a lot. I managed to adapt this script to add my .deb and auto rebuild the repo (pool+dists).
unfortunately, I'have got 2 new problems
We have developped puppet module and include its init.pp manifest in the site.pp

the init.pp manifest include 3 manifest
config.pp seting up the config files
frontend.pp installing the front end package
backend.pp installing the backend package and starting the service

the problems are :
-our module seems to be deployed before openstack modules so some requierements are not met (neutron.conf file is missing and openstack-dashboard is not setup)
-our backend module need flask-sqlalchimy. This is missing from precise repo so we are using pip in order to install it but even with http and https proxies setting up in the puppet.conf, and etc/profile puppet seems to not be able to access pip repo

how can you be sure that our modules will be deployed at the end of the deployement process?
how can we set up properly http proxy?

Thanks by advance

Samuel


________________________________________
De : Dmitry Borodaenko [dborodaenko@xxxxxxxxxxxx]
Date d'envoi : mardi 18 mars 2014 19:34
À : BARTEL Samuel NRS
Cc : fuel-dev@xxxxxxxxxxxxxxxxxxx; fweyns@xxxxxxxxxxxx; ALLES David IMT/OLPS
Objet : Re: [Fuel-dev] question about package repository on fuel 4.1

Hi Samuel,

Here's how the deb package repository for Fuel master node is
generated during ISO build:
https://github.com/stackforge/fuel-main/blob/master/mirror/ubuntu/createchroot.mk

You can adapt this script to re-create an APT repository that includes
your packages on an already deployed master node.

Alternatively, you can rebuild your own ISO (make sure to use the
stable/4.1 branch of fuel-main.git) with additional deb or rpm
packages. For deb packages, copy them to
fuel-main/mirror/ubuntu/files/; for rpm, to
local_mirror/centos/os/x86_64/Packages/ (local_mirror is a cache
directory, if you don't already have it, run "make iso" once).

Instructions on building Fuel ISO image can be found here:
http://docs.mirantis.com/fuel-dev/develop/env.html#building-the-fuel-iso

Hope this helps,
-DmitryB

On Tue, Mar 18, 2014 at 7:43 AM,  <samuel.bartel@xxxxxxxxxx> wrote:
> Hello,
>
>
>
> I am working on a project for Orange in France Using fuel to deploy
> openstack. We are in relation with Frank Weyns.
>
> I have several question about fuel :
>
>
> We have developped two new modules that we planed to deploy on the controler
> nodes :
> -a front end module : extension for horizon inluding new panels
> -a back end module : withnew api services
>
> following these documentations:
> http://docs.mirantis.com/fuel-dev/develop/module_structure.html#the-puppet-modules-structure
> http://docs.mirantis.com/fuel-dev/develop/fuel_settings.html
>
> we add new module in puppet, setup it to be executed only for controler
> role, and include it in the main site.pp.
>
> The problem is on the .deb packages. We would like to add them in the
> package repository on the fuel master ndoe (I guess it is the repository
> avalaible here on the master node : /var/www/nailgun/ubuntu/fuelweb/x86_64/)
>  we try to manually add the .deb file and modify the associated Packages
> file but with no success.
>
> How can you add our custome packages to fue fuel package repository on the
> fuel master node? is it possible or should set up an other repository and
> declare it on the source.list of the deployed node? in the case we have to
> modify source.list, is there an easiest way to proceed than modifying
> ubuntu-1204.preseed.erb in cobbler module
>
>
>
>
> regards
>
>
>
> Samuel BARTEL
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>



--
Dmitry Borodaenko
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.