Re: [openstack-dev] [Fuel] UI code freeze

2016-03-10 Thread Vladimir Kozhukalov 
​Evge​niy,

Right. There is only nailgun python project, development documentation [1]
and some minor scripts [2] which are outdated. Our further plan is to move
nailgun itself to a separate repo fuel-nailgun, remove outdated code, and
then move development doc pages to corresponding git repos.

[1] https://github.com/openstack/fuel-web/tree/master/docs
[2] https://github.com/openstack/fuel-web/tree/master/bin
__
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

Re: [openstack-dev] [Fuel] UI code freeze

2016-03-09 Thread Evgeniy L 
Hi,

Thank you for your work, really happy to see it done. So as far as I can
see from now on in fuel-web repository we have only Nailgun project. Is it
correct?

On Fri, Feb 26, 2016 at 3:53 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> We are ready for moving UI javascript code to a separate git repository.
> Since now all review requests for fuel-web@master that are related to UI
> must be marked -2 and later abandoned. Once new project fuel-ui is created
> those changes should be backported to this new repository.
>
> Checklist:
>
>
>- Launchpad UI bug: https://bugs.launchpad.net/fuel/+bug/1471763
>- openstack-infra
>   - project-config https://review.openstack.org/#/c/260455 (ON REVIEW)
>   - governance https://review.openstack.org/#/c/285270/ (ON REVIEW)
>- fuel-ci job https://review.fuel-infra.org/#/c/15487 (ON REVIEW)
>- label jenkins slaves for the new job (ci team)
>- UI directory freeze (DONE)
>- prepare upstream https://github.com/kozhukalov/fuel-ui.git (DONE)
>- waiting for openstack-infra patches to be merged
>- .gitreview .gitignore MAINTAINERS (TODO)
>- rpm spec (TODO)
>- custom ci jobs (TODO)
>- fuel-main (TODO)
>- packaging ci (TODO)
>- remove old files (TODO)
>
>
> Vladimir Kozhukalov
>
> __
> 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

Re: [openstack-dev] [Fuel] UI code freeze

2016-03-04 Thread Vladimir Kozhukalov 
Vitaly,

As we decided yesterday custom job with fuel-ui and fuel-web refspec
parameters could help here. Is it not enough for our case? In general, the
case when two PRs depends on each other was deliberately denied to be
handled automatically. Please read this thread [1] for details.

[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-February/056515.html




Vladimir Kozhukalov

On Thu, Mar 3, 2016 at 7:01 PM, Vitaly Kramskikh 
wrote:

> Fuel UI code has been completely removed from fuel-web repo and CI jobs to
> verify fuel-web RR with fuel-ui code and fuel-ui RR with fuel-web code have
> been set up. So the code separation can be considered as done.
>
> Though there is one thing needs to be done and we don't know how to solve
> that task properly: how do we test and merge RRs to fuel-web and fuel-ui
> which are dependent on each other? Example of such RR:
> https://review.openstack.org/#/c/286547/. It has -1 from CI because this
> change needs to be tested against corresponding RR to fuel-web repo.
>
> If you have any ideas, feel free to tell us.
>
> 2016-03-01 16:09 GMT+07:00 Vitaly Kramskikh :
>
>> The new repo has been created: https://github.com/openstack/fuel-ui.
>> Please move all change requests there. Fuel UI code in fuel-web repo is
>> going to be removed soon.
>>
>> 2016-02-26 19:53 GMT+07:00 Vladimir Kozhukalov 
>> :
>>
>>> Dear colleagues,
>>>
>>> We are ready for moving UI javascript code to a separate git repository.
>>> Since now all review requests for fuel-web@master that are related to
>>> UI must be marked -2 and later abandoned. Once new project fuel-ui is
>>> created those changes should be backported to this new repository.
>>>
>>> Checklist:
>>>
>>>
>>>- Launchpad UI bug: https://bugs.launchpad.net/fuel/+bug/1471763
>>>- openstack-infra
>>>   - project-config https://review.openstack.org/#/c/260455 (ON
>>>   REVIEW)
>>>   - governance https://review.openstack.org/#/c/285270/ (ON REVIEW)
>>>- fuel-ci job https://review.fuel-infra.org/#/c/15487 (ON REVIEW)
>>>- label jenkins slaves for the new job (ci team)
>>>- UI directory freeze (DONE)
>>>- prepare upstream https://github.com/kozhukalov/fuel-ui.git (DONE)
>>>- waiting for openstack-infra patches to be merged
>>>- .gitreview .gitignore MAINTAINERS (TODO)
>>>- rpm spec (TODO)
>>>- custom ci jobs (TODO)
>>>- fuel-main (TODO)
>>>- packaging ci (TODO)
>>>- remove old files (TODO)
>>>
>>>
>>> Vladimir Kozhukalov
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> Vitaly Kramskikh,
>> Fuel UI Tech Lead,
>> Mirantis, Inc.
>>
>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
> __
> 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

Re: [openstack-dev] [Fuel] UI code freeze

2016-03-03 Thread Vitaly Kramskikh 
Fuel UI code has been completely removed from fuel-web repo and CI jobs to
verify fuel-web RR with fuel-ui code and fuel-ui RR with fuel-web code have
been set up. So the code separation can be considered as done.

Though there is one thing needs to be done and we don't know how to solve
that task properly: how do we test and merge RRs to fuel-web and fuel-ui
which are dependent on each other? Example of such RR:
https://review.openstack.org/#/c/286547/. It has -1 from CI because this
change needs to be tested against corresponding RR to fuel-web repo.

If you have any ideas, feel free to tell us.

2016-03-01 16:09 GMT+07:00 Vitaly Kramskikh :

> The new repo has been created: https://github.com/openstack/fuel-ui.
> Please move all change requests there. Fuel UI code in fuel-web repo is
> going to be removed soon.
>
> 2016-02-26 19:53 GMT+07:00 Vladimir Kozhukalov :
>
>> Dear colleagues,
>>
>> We are ready for moving UI javascript code to a separate git repository.
>> Since now all review requests for fuel-web@master that are related to UI
>> must be marked -2 and later abandoned. Once new project fuel-ui is created
>> those changes should be backported to this new repository.
>>
>> Checklist:
>>
>>
>>- Launchpad UI bug: https://bugs.launchpad.net/fuel/+bug/1471763
>>- openstack-infra
>>   - project-config https://review.openstack.org/#/c/260455 (ON
>>   REVIEW)
>>   - governance https://review.openstack.org/#/c/285270/ (ON REVIEW)
>>- fuel-ci job https://review.fuel-infra.org/#/c/15487 (ON REVIEW)
>>- label jenkins slaves for the new job (ci team)
>>- UI directory freeze (DONE)
>>- prepare upstream https://github.com/kozhukalov/fuel-ui.git (DONE)
>>- waiting for openstack-infra patches to be merged
>>- .gitreview .gitignore MAINTAINERS (TODO)
>>- rpm spec (TODO)
>>- custom ci jobs (TODO)
>>- fuel-main (TODO)
>>- packaging ci (TODO)
>>- remove old files (TODO)
>>
>>
>> Vladimir Kozhukalov
>>
>> __
>> 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
>>
>>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>



-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
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

Re: [openstack-dev] [Fuel] UI code freeze

2016-03-01 Thread Vitaly Kramskikh 
The new repo has been created: https://github.com/openstack/fuel-ui. Please
move all change requests there. Fuel UI code in fuel-web repo is going to
be removed soon.

2016-02-26 19:53 GMT+07:00 Vladimir Kozhukalov :

> Dear colleagues,
>
> We are ready for moving UI javascript code to a separate git repository.
> Since now all review requests for fuel-web@master that are related to UI
> must be marked -2 and later abandoned. Once new project fuel-ui is created
> those changes should be backported to this new repository.
>
> Checklist:
>
>
>- Launchpad UI bug: https://bugs.launchpad.net/fuel/+bug/1471763
>- openstack-infra
>   - project-config https://review.openstack.org/#/c/260455 (ON REVIEW)
>   - governance https://review.openstack.org/#/c/285270/ (ON REVIEW)
>- fuel-ci job https://review.fuel-infra.org/#/c/15487 (ON REVIEW)
>- label jenkins slaves for the new job (ci team)
>- UI directory freeze (DONE)
>- prepare upstream https://github.com/kozhukalov/fuel-ui.git (DONE)
>- waiting for openstack-infra patches to be merged
>- .gitreview .gitignore MAINTAINERS (TODO)
>- rpm spec (TODO)
>- custom ci jobs (TODO)
>- fuel-main (TODO)
>- packaging ci (TODO)
>- remove old files (TODO)
>
>
> Vladimir Kozhukalov
>
> __
> 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
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
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-dev] [Fuel] UI code freeze

2016-02-26 Thread Vladimir Kozhukalov 
Dear colleagues,

We are ready for moving UI javascript code to a separate git repository.
Since now all review requests for fuel-web@master that are related to UI
must be marked -2 and later abandoned. Once new project fuel-ui is created
those changes should be backported to this new repository.

Checklist:


   - Launchpad UI bug: https://bugs.launchpad.net/fuel/+bug/1471763
   - openstack-infra
  - project-config https://review.openstack.org/#/c/260455 (ON REVIEW)
  - governance https://review.openstack.org/#/c/285270/ (ON REVIEW)
   - fuel-ci job https://review.fuel-infra.org/#/c/15487 (ON REVIEW)
   - label jenkins slaves for the new job (ci team)
   - UI directory freeze (DONE)
   - prepare upstream https://github.com/kozhukalov/fuel-ui.git (DONE)
   - waiting for openstack-infra patches to be merged
   - .gitreview .gitignore MAINTAINERS (TODO)
   - rpm spec (TODO)
   - custom ci jobs (TODO)
   - fuel-main (TODO)
   - packaging ci (TODO)
   - remove old files (TODO)


Vladimir Kozhukalov
__
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