fuel-dev team mailing list archive

[Andrew Woodward <xarses@xxxxxxxxx>]

Formerly "[Fuel-dev] fuel-deph-roles

Samuel

Thanks for the poke, I posted some of the changes that I had staged and
started some more of the items. These should at least be enough to work on.
I started branches for fuel-web [1] and fuel-library [2]. I also updated
the work items on the bp [3] as well as added you so you will be notified
of changes

As for what still needs to be done, the changes in [1] need the
corresponding tests updated. You can reference what was done for mongodb
[4] as it will be similar here. For the puppet side [2] further work needs
to be done to ensure the separation from controller, radosgw, and mon. For
started the changes in the branch are ad hoc and haven't been vetted.
Secondly the de-couple from the controller needs at least ceph and
ceph::config ran on the controllers again (if we have ceph oss services).
The decouple was also violent for radosgw which now needs apache defined
from somewhere.

Any help would be appreciated.

[1] https://github.com/xarses/fuel-library/tree/bp/fuel-ceph-roles
[2] https://github.com/xarses/fuel-web/tree/bp/fuel-ceph-roles
[3] https://blueprints.launchpad.net/fuel/+spec/fuel-ceph-roles
[4] https://review.openstack.org/#/c/71883/


On Tue, Apr 8, 2014 at 5:16 AM, <samuel.bartel@xxxxxxxxxx> wrote:

>  Hello,
>
> We need more information about the following blueprint:
>
> <A href="
> https://nantes.metagate.orange.com/fuel/+spec/spec/fuel-ceph-roles
>
>
>
> For our platforms using ceph we planned to  separate openstack controller
> and ceph-monitor
>
> According to this blueprint this is something  consider by mirrantis. Can
> you give us a little more visibility on the progression and the futur
> avalaibility of this blue print? will it be avalaible in 5.0?
>
> regards
>
>
>
> Samuel
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>


-- 
Andrew
Mirantis
Ceph community