fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

Folks,
what are the use cases for this?


On Sat, Mar 15, 2014 at 9:15 PM, Oleg Gelbukh <ogelbukh@xxxxxxxxxxxx> wrote:

> Vladimir,
>
> FWIW, I also think this is absolutely viable idea. Moreover, it would be
> useful if parts of Fuel could be built, installed and used separately from
> each other.
>
> --
> Best regards,
> Oleg Gelbukh
>
>
> On Sat, Mar 15, 2014 at 12:47 AM, Vladimir Kozhukalov <
> vkozhukalov@xxxxxxxxxxxx> wrote:
>
>> Matt,
>>
>> Great to know that at least one person (except me) thinks it is a viable
>> idea to make user able to deploy master node not depending on ISO.
>>
>> AFAIK, both deb and rpm packages can run arbitrary scripts during
>> post-installation stage. And I remember when Ubuntu came out with their
>> Juju based openstack deployment scheme they used to rely totally on deb
>> post install scripts during deployment their Cobbler+Juju master node.
>> Besides, at least when you use deb packages it is possible to interact with
>> user using debconf dialog.
>>
>> Anyway, Docker containers seem to be an appropriate solution for this use
>> case, at least in a short term perspective.
>>
>>
>>
>>
>>
>>
>>
>>
>> Vladimir Kozhukalov
>>
>>
>> On Fri, Mar 14, 2014 at 7:34 AM, Matthew Mosesohn <mmosesohn@xxxxxxxxxxxx
>> > wrote:
>>
>>> Vladimir,
>>>
>>> This may be achievable as part of my work with moving Fuel master node
>>> services into individual Docker containers. See my blueprint here:
>>>
>>> https://blueprints.launchpad.net/fuel/+spec/fuel-containerization-of-services
>>>
>>> One big advantage of using these containers is you could use any Linux
>>> OS (with network namespaces support) to host these containers.
>>>
>>> The only concern I have with trying to install on an existing server
>>> is to make sure that there are no services listening on the ports we
>>> need to use for Fuel master (such as an existing web server).
>>>
>>> Installing Fuel from packages, however, would be really great for
>>> upstream distributions who think our code is cool enough to ship in
>>> mainstream OSes. The biggest drawback is we tune and apply changes to
>>> lots of services (Cobbler, rabbitMQ, postgres) in ways that really
>>> should never be done from a package manager. Instead, we would need to
>>> distribute a big script that an admin runs after install to apply the
>>> needed configuration. This script could be still in puppet, of course.
>>>
>>> On Fri, Mar 14, 2014 at 5:00 AM, Vladimir Kozhukalov
>>> <vkozhukalov@xxxxxxxxxxxx> wrote:
>>> > All,
>>> >
>>> > There is an interesting use case we do not cover at the moment. What if
>>> > someone wants to deploy master node on a server which is already in
>>> use and
>>> > has OS installed on it. Would it be great to have the possibility to
>>> deploy
>>> > master node from packages just running a script?
>>> >
>>> >
>>> > What do you think about it?
>>> >
>>> >
>>> > Vladimir Kozhukalov
>>> >
>>> > --
>>> > 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
>>> >
>>>
>>
>>
>> --
>> 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
>>
>>
>
> --
> 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
>
>


-- 
Mike Scherbakov
#mihgen