x27;t
manage to implement this. Maybe in Ocata.
Vladimir Kozhukalov
On Mon, Sep 19, 2016 at 9:33 AM, Guo, Ruijing wrote:
> Hi, Vladimir
>
>
>
> Any guide to install from rpm?
>
>
>
> Thanks,
>
> -Ruijing
>
> *From:* Vladimir Kozhukalov [mailto:vkozhuka...@mi
tool and I'm looking forward for other Fuel team members to run for PTL
role.
Thanks.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
+1
Vladimir Kozhukalov
On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk
wrote:
> Hello,
>
> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to
> his significant contribution to the project [1] and [2]. He is the second
> reviewer and for the last half of th
tron/
[5]
https://ci.fuel-infra.org/job/master.fuel-astute.pkgs.ubuntu.review_astute_patched/
Vladimir Kozhukalov
On Thu, Sep 1, 2016 at 1:13 PM, Roman Prykhodchenko wrote:
> This is so awesome! Thanks!
>
> On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes wrote:
>
>> On 08/16/2
nd holiday tolerance)
2) It will be easier to manage single core group (promote new members,
remove not active members)
Cons:
1) Less of flexibility. Permissions will be the same for all core reviewers
in all Fuel projects.
What
Thanks for you efforts, FFE is granted, please go ahead. I hope we'll get
it merged by 09/09/2016.
Vladimir Kozhukalov
On Fri, Sep 2, 2016 at 1:02 PM, Dmitry Klenov wrote:
> Hi Fuelers,
>
> I would like to ask for a FFE for "Role Decomposition" feature. The spec
> is
ext Friday 09/09/2016.
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/mailma
Although I am not a core in fuel-library, I am voting +1.
Vladimir Kozhukalov
On Fri, Aug 26, 2016 at 1:27 PM, Ivan Berezovskiy wrote:
> +1, great job!
>
> 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya :
>
>> +1
>>
>> On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
&g
https://etherpad.openstack.org/p/fuel-ocata-summit-planning
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
in a consistent way. So, I prefer option #3. Let's write a spec for this.
[0]
https://github.com/openstack/fuel-agent/blob/master/fuel_agent/manager.py#L961
[1]
https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/boothook_fuel_9.0_ubuntu.jinja2#L91
Vladimir Kozhukalov
O
pport
our own ISO build code. That will allow us to make Fuel admin node
deployment more flexible.
I will infrom about our next steps here in the thread.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for
We are working on this. Will fix soon.
Vladimir Kozhukalov
On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko wrote:
> If it’s not possible to fix this job during next few hours, let’s mark in
> as non-voting until the bug(s) are fixed.
>
> > 8 серп. 2016 р. о 11:48 Roma
jobs stable
again.
Thanks.
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
d it is a part of development process. Not all these
repos are to become a part of Big tent.
Vladimir Kozhukalov
On Thu, Jul 28, 2016 at 7:45 AM, Steven Dake (stdake)
wrote:
>
>
> On 7/27/16, 2:12 PM, "Jay Pipes" wrote:
>
> >On 07/27/2016 04:42 PM, Ed Leafe wrote:
&
>
> Few Q:
> - Is the stable/mitaka the only stable branch in the scope of the changes?
>
Yes, this announce is only about Mitaka branch. All other stable branches
are to be treated as usual, i.e. no feature backports, bug fixes only
following "master first" policy, etc.
>
> - As the master and s
tly (not
all features but those are to be backported onto stable branch).
[1] http://docs.openstack.org/project-team-guide/stable-branches.html
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage question
Please review this patch [1]. It is to remove the code from master branch.
We still need test jobs for stable branches.
[1] https://review.openstack.org/#/c/335868/
Vladimir Kozhukalov
On Mon, Jun 27, 2016 at 1:14 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Fuel-mirr
Yet another patch [1] that makes fuel-upgrade read only.
[1] https://review.openstack.org/#/c/335841/
Vladimir Kozhukalov
On Wed, Jun 29, 2016 at 6:42 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> This is yet another related patch [1], that removes the code from master
This is yet another related patch [1], that removes the code from master
branch and adds retirement warning. Review is welcome.
[1] https://review.openstack.org/#/c/334949/
Vladimir Kozhukalov
On Wed, Jun 29, 2016 at 4:00 PM, Ilya Kharin wrote:
> Hi Vladimir,
>
> This change is r
This patch [1] is a part of project retirement procedure [2]. Review is
welcome.
[1] https://review.openstack.org/#/c/335085/
[2] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
Vladimir Kozhukalov
On Tue, Jun 28, 2016 at 1:41 PM, Vladimir Kozhukalov <
vkozh
[3].
Fuel-upgrade will stay available for a while perhaps for about a year or so
in case some of Fuel users want to build upgrade tarball.
[1] https://github.com/openstack/fuel-upgrade
[2] https://github.com/openstack/fuel-octane
[3] https://review.openstack.org/#/c/334903/
Vladimir Kozhukalov
As far as I understand, Rally is pluggable and one can implement any
scenario we need in pure Python (totally out of Tempest). See for example
[1].
[1] http://rally.readthedocs.io/en/latest/plugins/scenario_plugin.html
Vladimir Kozhukalov
On Mon, Jun 27, 2016 at 4:46 PM, Igor Kalnitsky
wrote
refer
Fuel users to rely on Rally user interface (both CLI and dashboard).
What do you think? Are there any volunteers to implement this?
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
U
building deb/rpm packages and repositories.
Sincing these repos over multiple locations as well as tracking repository
snapshots will be a matter of Trsync project (Fuel infra team project).
Vladimir Kozhukalov
On Mon, Jun 27, 2016 at 11:38 AM, Igor Kalnitsky
wrote:
> Vladimir,
>
> Thanks fo
) OpenStack projects don't use
'openstack' prefix. Besides, many Fuel users already got used to #fuel and
deprecating it would introduce extra efforts and inconveniencies.
Vladimir Kozhukalov
On Mon, Jun 27, 2016 at 11:42 AM, Igor Kalnitsky
wrote:
> > On Jun 25,
Nice. #fuel-infra is to merged as well.
Vladimir Kozhukalov
On Fri, Jun 24, 2016 at 1:50 PM, Aleksandra Fedorova wrote:
> And +1 for #fuel-infra
>
> As of now it will be more useful if infra issues related to project will
> be visible for project developers. We don't have m
Ok, let's then start from merger of
#fuel-dev
#fuel-python
#fuel-ui
#fuel-library
into a single channel #fuel. #fuel-infra is to stay separate for a while.
Vladimir Kozhukalov
On Fri, Jun 24, 2016 at 1:41 PM, Andrew Maksimov
wrote:
> +1 for merging #fuel #fuel-dev #fuel-python a
Dear colleagues,
We have a few IRC channels but the level of activity there is quite low.
#fuel
#fuel-dev
#fuel-python
#fuel-infra
My suggestion is to merge all these channels into a single IRC channel
#fuel.
Other #fuel-* channels are to be deprecated.
What do you think of this?
Vladimir
is [2] patch.
[0] https://wiki.openstack.org/wiki/Packetary
[1] https://github.com/openstack/python-fuelclient
[2] https://review.openstack.org/#/c/326435/
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for
Dear colleagues,
We are approaching 9.0.1 release and for higher level of stability we are
going to pin [1] upstream puppet modules temporarily. Once 9.0.1 tag is
created we will unpin upstream to make it possible to get upstream fixes.
[1] https://review.openstack.org/#/c/325807/
Vladimir
Absolutely agree with Jay. Fuel is a community project.
Please keep discussion public including technical details.
Anyway, integration is welcome, please go ahead and
create BP (btw, spec review request is the best place to
discuss technical details).
Vladimir Kozhukalov
On Fri, May 13, 2016
Done.
Wed 11:00-11:40 Finalizing of HA reference architecture with event-based
control and fencing
Thu 11:00-11:40 Fuel UI Modularization approaches discussion
Vladimir Kozhukalov
On Mon, Apr 25, 2016 at 10:14 PM, Vladimir Kuklin
wrote:
> Fuelers
>
> I am OK with the proposed change
/mos-repos/ubuntu/9.0/
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
, one of the ideas was to use Fuel task capabilities
to gather diagnostic snapshot.
Vladimir Kozhukalov
On Thu, Mar 31, 2016 at 1:32 PM, Evgeniy L wrote:
> Hi,
>
> Problems which I see with current Shotgun are:
> 1. Luck of parallelism, so it's not going to fetch data fast enough
t would be great to
invite there people from Mistral and Heat.
My suggestion is as follows:
Wed:
9:50 Astute -> Mistral/Heat/???
Thu:
9.00 Fuel/Ironic/Ironic-inspector
If there are any objections, please let me know asap.
Vladimir Kozhukalov
On Fri, Apr 1, 2016 at 9:47 PM, Vladimir Kozhukal
east Puppet, UI, REST&Orchestration SMEs.
It is also a responsibility of Fuel-specs core group
to involve other SMEs if needed.
[1] https://review.openstack.org/#/c/301194/
Vladimir Kozhukalov
On Thu, Mar 31, 2016 at 6:47 PM, Serg Melikyan
wrote:
> Hi fuelers,
>
> only few hou
fixes for High and Critical
bugs. Backporting procedure is described here [2].
[1] https://wiki.openstack.org/wiki/Fuel/Soft_Code_Freeze
[2]
https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series
Vladimir Kozhukalov
-17:30
[1]
http://lists.openstack.org/pipermail/openstack-dev/attachments/20160331/d59d38b7/attachment.pdf
[2] https://wiki.openstack.org/wiki/Design_Summit
[3] https://etherpad.openstack.org/p/fuel-newton-summit-planning
[4] https://wiki.openstack.org/wiki/Design_Summit/Planning
Thanks.
Vladimir
certainly do this.
[1] https://blueprints.launchpad.net/fuel/+spec/deploy-rdo-using-fuel
[2] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
Vladimir Kozhukalov
On Wed, Mar 30, 2016 at 8:41 PM, Aleksandra Fedorova wrote:
> Hi, Vladimir,
>
> this is a great feature, which
gs to identify
the content of env. This report could also be
used to reproduce env and then fight a bug.
I'd like we to have this kind of report.
Is it possible to implement such a feature
using Ansible? If yes, then let's switch to Ansible
as soon as possible.
Vladimir Kozhukalov
On We
right now. I'd really like to
see here in this ML thread opinions of our current
CLs and other people.
Vladimir Kozhukalov
On Tue, Mar 29, 2016 at 11:21 PM, Dmitry Borodaenko <
dborodae...@mirantis.com> wrote:
> On Tue, Mar 29, 2016 at 03:19:27PM +0300, Vladimir Kozhukalov wrote:
&g
On Wed, Mar 30, 2016 at 11:01 AM, Thierry Carrez
wrote:
> John Dickinson wrote:
>
>> On Thursday, I'd like to proposed swapping Swift's 1:30pm session with
>> Fuel's 2:20pm session. This will give Swift a contiguous time block in the
>> afternoon, and Fuel's session would line up right after thei
test succeeds,
get this package (not re-building it) and put it into the
current master package repo.
Feel free to leave your comments.
[1]
https://docs.google.com/document/d/1Yp63s3ctO0FNRhqrWNpLmXxMOaJT2tb8H0W80Jr_kjM
Vladimir Kozhu
are welcome. You can contact Fuel team here in [openstack-dev]
maling list or in #fuel IRC channel. It would be nice to see more people
from different backgrounds contributing to Fuel.
Vladimir Kozhukalov
__
OpenStack
gt;
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html
> [2]
> https://github.com/openstack/governance/blob/master/reference/projects.yaml#L593
> [3]
> https://github.com/openstack/fuel-specs/blob/master/policy/team-structure.rst#code-review-workflow
>
&
Oleg and team,
Thanks very much for your efforts to make this happened. I'm sure this
experience will help us to implement thorough "Day 2" maintenance flow in
future Fuel releases.
Vladimir Kozhukalov
On Tue, Mar 29, 2016 at 12:06 PM, Oleg Gelbukh
wrote:
> Greetin
, volunteers are needed to drive Shotgun project. We need to inspect
its possible use cases, we should make it even more generic, convenient
and well documented. We also need to figure out what
we can improve in the project and how and then create roadmap.
Vladimir Kozhukalov
Guys, you are awesome. Thank you all very much.
Vladimir Kozhukalov
On Mon, Mar 28, 2016 at 11:50 PM, Alexey Shtokolov
wrote:
> Fuelers!
>
> I'm glad to announce that all patches [0] were merged!
>
> Many thanks to all of you who help us to make Fuel more flex
Granted. New deadline is 21:00 UTC 03/28/2016.
Vladimir Kozhukalov
On Fri, Mar 25, 2016 at 8:17 PM, Alexey Shtokolov
wrote:
> Fuelers!
>
>
> We are very close to landing our feature "Unlock Settings Tab". But we
> still have a set of reviews [0] to be merged due to sev
think?
Vladimir Kozhukalov
On Thu, Mar 24, 2016 at 11:58 PM, Dmitry Borodaenko <
dborodae...@mirantis.com> wrote:
> Serg,
>
> Thanks for agreeing to officiate this cycle's component lead elections
> for us!
>
> --
> Dmitry Borodaenko
>
>
> On Thu, Mar 24,
of long report, I don't know
what motivation was for this change except their convenience. Probably
short report is to be used for internal QA team purposes only.
Vladimir Kozhukalov
On Mon, Mar 21, 2016 at 11:20 PM, Alex Schultz
wrote:
>
> On Mon, Mar 21, 2016 at 1:59 PM
ou run some tests against this lab and manually do some experiments to
kill the bug
Vladimir Kozhukalov
On Mon, Mar 21, 2016 at 5:28 PM, Alex Schultz wrote:
>
>
> On Mon, Mar 21, 2016 at 7:21 AM, Volodymyr Shypyguzov <
> vshypygu...@mirantis.com> wrote:
>
>> Hi, all
&
it and request will
continue to wait for a lock to be released until lock_timeout is exceeded.
[1] http://www.postgresql.org/docs/9.3/static/runtime-config-locks.html
Vladimir Kozhukalov
On Mon, Mar 21, 2016 at 7:39 PM, Roman Prykhodchenko wrote:
> Folks,
>
> We have been analyzing a
Sorry, typo:
*cloud case does NOT assume running any kind of agent
inside user instance
Vladimir Kozhukalov
On Fri, Mar 18, 2016 at 7:26 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> >Well, there's a number of reasons. Ironic is not meant only for an
> >
ing stevedore. About ironic-inspector
the case is the same. Whether we are going to run it inside 'user instance'
or inside ramdisk it does not affect ironic-inspector itself. If Ironic
team is
open for merging "non-cloud" features (of course 'opt-in') we'll be hap
CLI.
As for DEB packaging, as Thomas wrote, he is currently working on making
this possible to build DEB packages (including Fuel) using OpenStack
Infrastructure.
[1] https://wiki.openstack.org/wiki/Packetary
Vladimir Kozhukalov
On Fri, Mar 18, 2016 at 12:11 AM, Thomas Goirand wrote:
> On
It would be great if at least one Fuel slot did not overlap with Ironic
sessions.
Vladimir Kozhukalov
On Fri, Mar 18, 2016 at 6:26 PM, Jeremy Stanley wrote:
> On 2016-03-18 08:53:11 +0530 (+0530), Armando M. wrote:
> > It's be nice if Neutron didn't overlap as much with N
group&metric=commits
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
discovery component (btw
written in python) and I can't see any reason why we should continue
putting efforts in nailgun agent and not try to switch to ironic-inspector.
Vladimir Kozhukalov
On Mon, Mar 14, 2016 at 7:41 PM, Evgeniy L wrote:
> Hi Alexander, thanks for bringing this up.
Evgeniy,
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
://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 fu
Andrew,
I think everything will be ready by Wednesday 03/09/2016. We have just
fixed one critical bug in Packetary, now it seems working.
Vladimir Kozhukalov
On Wed, Mar 2, 2016 at 4:21 PM, Andrew Maksimov
wrote:
> Hi Vladimir,
>
> Till what date do you want FFE ?
>
> Re
merge fuel-main patch and
declare this new job as our product ISO job
4) We will create custom jobs with this new set of variables
[0] https://blueprints.launchpad.net/fuel/+spec/use-packetary-in-fuel
[1] https://review.openstack.org/#/c/286576
[2] https://review.openstack.org/#/c/283
)
- 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
://review.openstack.org/#/c/283265 (ON REVIEW)
- .gitignore file https://review.openstack.org/#/c/283265 (ON REVIEW)
- MAINTAINERS file https://review.openstack.org/#/c/283265 (ON REVIEW)
- remove old files from fuel-main https://review.openstack.org/#/c/283272
(ON REVIEW)
Vladimir Kozhukalov
On Wed
rtualbox directory is declared freezed and all changes
in this directory that are currently in work should be later backported to
the new git repository (fuel-virtualbox).
Vladimir Kozhukalov
__
OpenStack Development Mailing L
uel packages at the
ISO build time and instead download them from Fuel Packaging CI.
Vladimir Kozhukalov
On Wed, Feb 3, 2016 at 6:03 PM, Vladimir Kuklin
wrote:
> +1
>
>
> On Wed, Feb 3, 2016 at 4:45 PM, Igor Kalnitsky
> wrote:
>
>> No objections from my side. Let's do it
+1 to enable it ASAP.
It will also affect our deployment tests (~1 hour vs. ~2.5 hours).
Vladimir Kozhukalov
On Mon, Feb 8, 2016 at 7:35 PM, Bulat Gaifullin
wrote:
> +1.
>
> Regards,
> Bulat Gaifullin
> Mirantis Inc.
>
>
>
> > On 08 Feb 2016, at 19:05, Igor K
custom ci jobs (TODO) Vladimir
- fuel-main (TODO) Vladimir
- packaging ci (TODO) Vladimir
- remove old files (TODO) Vitaly + Vladimir
We shared the whole set of tasks with Vitaly Kramskikh. I will keep this
thread up to date. ETA for this to finish is mid Janua
create stable branch master becomes open. That was our primary intention to
open master earlier than later when we decided to move stable branch
creation.
Vladimir Kozhukalov
On Wed, Dec 16, 2015 at 8:28 PM, Vladimir Kuklin
wrote:
> Vladimir
>
> I am pretty much for removing docker,
-1
We already discussed this and we have made a decision to move stable branch
creation from HCF to SCF. There were reasons for this. We agreed that once
stable branch is created, master becomes open for new features. Let's avoid
discussing this again.
Vladimir Kozhukalov
On Wed, Dec 16,
ies, but I think
a deployment script should be a root of the package dependency tree.
Vladimir Kozhukalov
On Mon, Dec 14, 2015 at 12:53 PM, Igor Kalnitsky
wrote:
> Vladimir,
>
> Thanks for raising this question. I totally support idea of separating
> provisioning and deployment s
i.org/doc/debconf-doc/tutorial.html
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 11:14 PM, Oleg Gelbukh
wrote:
> For the package-based deployment, we need to get rid of 'deployment
> script' whatsoever. All configuration stuff should be done in package
> specs, or by the user later on
hemes. Primary delivery approach should be rpm/deb repo, not ISO.
[0]
https://blueprints.launchpad.net/fuel/+spec/separate-fuel-node-provisioning
[1] https://review.openstack.org/#/c/254270/
Vladimir Kozhukalov
__
Open
https://bugs.launchpad.net/fuel/+bug/1525323
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 5:48 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> BTW, here you can see an example http://demo.fuel-infra.org:8000 Just go
> to any cluster and see Repositories section on
BTW, here you can see an example http://demo.fuel-infra.org:8000 Just go to
any cluster and see Repositories section on the settings tab.
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 5:46 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> I'd like this module
> h
don't suggest to change this. I suggest to use something
similar of what we have on Web UI in our fuel-menu.
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 5:10 PM, Alexander Kostrikov <
akostri...@mirantis.com> wrote:
> Hello, Vladimir.
> Seems nothing is better for end-user i
rusty-my-favorite-updates my-favorite-section
While we (for some reasons) limited our UI to define only base url and base
suite. That should be fixed.
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 2:33 PM, Igor Kalnitsky
wrote:
> > Do we really need a custom format? Why can not we use na
directly configured.
[0]
https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L2006-L2053
Vladimir Kozhukalov
On Fri, Dec 11, 2015 at 1:56 PM, Aleksandr Mogylchenko <
amogylche...@mirantis.com> wrote:
> There are common practices developed b
fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L2006-L2053
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
Mike,
Yes, probably the best place to describe further plans is README file. I'll
create a patch.
Vladimir Kozhukalov
On Tue, Dec 1, 2015 at 8:30 PM, Mike Scherbakov
wrote:
> Vladimir,
> if you've been behind of this, could you please share further plans in
> separate emai
/
[2] https://review.openstack.org/#/c/248650/
[3] https://review.openstack.org/#/c/248814/
Vladimir Kozhukalov
On Mon, Nov 30, 2015 at 11:19 PM, Fox, Kevin M wrote:
> Is that because of trying to shoehorn docker containers into rpm's though?
> I've never seen anyone else try a
ed in the future to avoid functionality
duplication.
Those were the reasons not to put them separately. (C) "There can be only
one".
Vladimir Kozhukalov
On Tue, Dec 1, 2015 at 1:25 PM, Thomas Goirand wrote:
> On 12/01/2015 09:25 AM, Mike Scherbakov wrote:
> > 4. I do
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,
&g
-> systemd).
Vladimir Kozhukalov
On Tue, Nov 24, 2015 at 1:57 AM, Igor Kalnitsky
wrote:
> Hey Dmitry,
>
> Thank you for your effort. I believe it's a huge step forward that
> opens number of possibilities.
>
> > Every container runs systemd as PID 1 process instead of
[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
ETA:
experimental ISO w/o docker: tonight
spec: tomorrow night
Vladimir Kozhukalov
On Mon, Nov 23, 2015 at 9:25 AM, Anastasia Urlapova
wrote:
> @Vova,
> thanks for bringing this up.
> The new approach without docker containers on master node really has many
> advantage
n time? And please do not confuse
these two cases: switching from plain deployment to containers is
complicated, but switching from docker to plain is much simpler.
Vladimir Kozhukalov
On Fri, Nov 20, 2015 at 6:47 PM, Bogdan Dobrelya
wrote:
> On 20.11.2015 15:10, Timur Nurlygayanov wrote
me a chance to do this ASAP (during 8.0), I know it is a huge risk for
the release, but still I think I can do this.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
Looks like most people thing that building backup/re-install approach is
more viable. So, we certainly need to invent completely new upgrade from
and thus my suggestion is disable building/testing upgrade tarball right
now, because anyway it makes no sense.
Vladimir Kozhukalov
On Fri, Nov 6
ecision about how we are going to upgrade the
master node ASAP. Probably my tarball related work should be reduced to
just throwing tarball away.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage qu
Dear colleagues,
I'm glad to announce that network-checker is a separate project now. All
related patches have been merged. Thanks everyone for your efforts to make
this happen.
Vladimir Kozhukalov
On Thu, Oct 29, 2015 at 6:42 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wro
hich are (ON REVIEW), please help.
Vladimir Kozhukalov
On Tue, Oct 20, 2015 at 6:45 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Dear colleagues,
>
> As you might know I'm working on splitting multiproject fuel-web
> repository into several sub-proj
://review.openstack.org/239410 (DONE)
- deprecate shotgun directory https://review.openstack.org/239407 (DONE)
- fix verify-fuel-web-docs job (it installs shotgun for some reason)
https://review.fuel-infra.org/#/c/13194/ (DONE)
- remove old shotgun package (DONE)
Vladimir Kozhukalov
On Wed, Oct 21
(DONE???)
Vladimir Kozhukalov
On Fri, Oct 23, 2015 at 7:06 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Dear colleagues,
>
> I'd like to update the status of the activity (moving fuelmenu to a
> separate repo).
>
>
>- Launchpad bug http
erged.
Vladimir Kozhukalov
On Tue, Oct 20, 2015 at 7:05 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> Igor,
>
> Thank you for your help. I'd say ETA is today/tomorrow and depends on how
> quickly this project-config patch [1] will be reviewed and merged. I'll
e currently on review will need to
be backported to the new git repository.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
Igor,
Thank you for your help. I'd say ETA is today/tomorrow and depends on how
quickly this project-config patch [1] will be reviewed and merged. I'll ask
openstack-infra guys to do this ASAP.
[1] https://review.openstack.org/#/c/235177
Vladimir Kozhukalov
On Tue, Oct 20, 2015
ill
need to be backported to the new git repository.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists
view will
need to be backported to the new git repository.
Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
1 - 100 of 167 matches
Mail list logo
