fuel-dev team mailing list archive

[Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>]

Dmitry, you can get more information on how we build packages and get them
into ISO from Roman Vyalov.
If you deploy the same infrastructure on your own, you can easily build
custom ISOs for your own purposes. This should not be very hard as we use
OpenSuse Build Service and you will need just to replace older OpenStack
code with newer one.
Currently, we are using private Mirantis gerrit to maintain changes to the
source code of packages including OpenStack ones. You can easily generate
change requests for OpenStack packages you want and our OSCI infra should
build them in the separate repos. All you will need to do is to generate
repos with these packages and use them for ISO building. I am not quite
sure that this will not bring our Infra down right now, but you can find a
way how to replicate it and run it on your own hardware.




On Fri, Feb 14, 2014 at 12:41 PM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx>wrote:

> If you can build the package, then you can replace it in the packages
> mirror, and build system will take your modified package.
> At the moment, we don't have packages specs open & build scripts for
> RPM/DEB packages, so you would need to rely on those you can find at
> Ubuntu/Fedora.
>
> Thanks,
>
>
> On Tue, Feb 11, 2014 at 4:15 AM, Dmitriy Novakovskiy <
> dnovakovskiy@xxxxxxxxxxxx> wrote:
>
>> Thanks Vladimir,
>>
>> I had some smart folks helping me figure out the right wording for
>> things, and turns out that instead of using word "trunk" I should use word
>> "stable community branch" :). This maps to case when customer doesn't want
>> to commit to specific "distro" vendor, but wants to use stable community
>> branch + Fuel to deploy the cloud.
>>
>> From what I understand so far, there's yet no straightforward way for
>> user to build master ISO by taking Fuel from github and mixing it w/
>> packages built locally from stable community branch + HA tools like
>> HAproxy, pacemaker etc. The only way to deploy is to take ISO from
>> software.mirantis.com (w/ which you're legally not allowed to deploy
>> more then 10 nodes)
>>
>> If that's not the case - please correct me.
>>
>>
>>
>> ---
>> Regards,
>> Dmitriy
>>
>>
>> On Sun, Feb 9, 2014 at 11:55 AM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>wrote:
>>
>>> Dmitry, this is not on our RoadMap at least for 4.1 release now. Anyone
>>> can do this by himself, but one should have his own test infrastructure
>>> which verifies that all components of OpenStack and underlying operating
>>> systems can work seamlessly, as there can be commits in trunk code of
>>> OpenStack that, for example, can break compatibility of Cinder code with
>>> old CentOS device-mapper utils. Official support for this feature is under
>>> discussion as some users are interested in it, but we are not going to
>>> support it out-of-box in 4.1 Both approaches you suggested can be applied
>>> but with no official warranty right now. Anyway, feel free to submit
>>> corresponding blueprint in FUEL launchpad space and report on your progress
>>> in trunk deployment.
>>>
>>>
>>> On Mon, Feb 3, 2014 at 8:24 PM, Dmitriy Novakovskiy <
>>> dnovakovskiy@xxxxxxxxxxxx> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I have 2 customers who are interested in using Fuel to deploy OpenStack
>>>> from trunk packages. Can you explain me what it would take (technically) to:
>>>>
>>>>    - A) Do it "true way" - Build an ISO for Fuel master using trunk
>>>>    packages (latest OpenStack release supported by Fuel) and Fuel (from "open"
>>>>    sources only, not using any MOS images from mirantis.com)
>>>>    - B) Do it "hack way" - Install MOS from mirantis.com ISO and then
>>>>    substitute packages w/ trunk
>>>>    - C) Something else - maybe i'm inventing wrong approaches :)
>>>>
>>>> I'm also looking for advice on how generally feasible any approach is,
>>>> given the end goal to be a working OpenStack cloud
>>>>
>>>> Thanks in advance,
>>>>
>>>> ---
>>>> Regards,
>>>> Dmitriy
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Yours Faithfully,
>>> Vladimir Kuklin,
>>> Senior Deployment Engineer,
>>> Mirantis, Inc.
>>> +7 (495) 640-49-04
>>> +7 (926) 702-39-68
>>> Skype kuklinvv
>>> 45bk3, Vorontsovskaya Str.
>>> Moscow, Russia,
>>> www.mirantis.com <http://www.mirantis.ru/>
>>> www.mirantis.ru
>>> vkuklin@xxxxxxxxxxxx
>>>
>>
>>
>> --
>> 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
>



-- 
Yours Faithfully,
Vladimir Kuklin,
Senior Deployment Engineer,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin@xxxxxxxxxxxx