The status is as follows:

1) Fuel-main [1] and fuel-library [2] patches can deploy the master node
w/o docker containers
2) I've not built experimental ISO yet (have been testing and debugging
manually)
3) There are still some flaws (need better formatting, etc.)
4) Plan for tomorrow is to build experimental ISO and to begin fixing
system tests and fix the spec.

[1] https://review.openstack.org/#/c/248649
[2] https://review.openstack.org/#/c/248650

Vladimir Kozhukalov

On Mon, Nov 23, 2015 at 7:51 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Colleagues,
>
> I've started working on the change. Here are two patches (fuel-main [1]
> and fuel-library [2]). They are not ready to review (still does not work
> and under active development). Changes are not going to be huge. Here is a
> spec [3]. Will keep the status up to date in this ML thread.
>
>
> [1] https://review.openstack.org/#/c/248649
> [2] https://review.openstack.org/#/c/248650
> [3] https://review.openstack.org/#/c/248814
>
>
> Vladimir Kozhukalov
>
> On Mon, Nov 23, 2015 at 3:35 PM, Aleksandr Maretskiy <
> amarets...@mirantis.com> wrote:
>
>>
>>
>> On Mon, Nov 23, 2015 at 2:27 PM, Bogdan Dobrelya <bdobre...@mirantis.com>
>> wrote:
>>
>>> On 23.11.2015 12:47, Aleksandr Maretskiy wrote:
>>> > Hi all,
>>> >
>>> > as you know, Rally runs inside docker on Fuel master node, so docker
>>> > removal (good improvement) is a problem for Rally users.
>>> >
>>> > To solve this, I'm planning to make native Rally installation on Fuel
>>> > master node that is running on CentOS 7,
>>> > and then make a step-by-step instruction how to make this installation.
>>> >
>>> > So I hope docker removal will not make issues for Rally users.
>>>
>>> I believe the most backwards compatible scenario is to keep the docker
>>> installed while removing the fuel-* docker things back to the host OS.
>>> So nothing would prevent user from pulling and running whichever docker
>>> containers he wants to put on the Fuel master node. Makes sense?
>>>
>>>
>> Sounds good
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to