24 hours.
Let's wait with other features, and extend FF to Monday, 03 of November. As
we are in green in almost all the features we planned to land in, it should
be fine.
Thanks,
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStac
//wiki.openstack.org/wiki/Fuel/6.0_Release_Schedule
[2] https://wiki.openstack.org/wiki/FeatureFreeze
[3] https://fuel-jenkins.mirantis.com/, 6.0 tab, last two builds
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.
k Engineer
>> tnapier...@mirantis.com
>>
>>
>>
>>
>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/o
lease candidates.
[1] https://wiki.openstack.org/wiki/Fuel/6.0_Release_Schedule
Thanks,
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
needs an attention.
Thanks,
On Wed, Nov 12, 2014 at 12:17 PM, Mike Scherbakov
wrote:
> Folks,
> as we all getting hurry with features landing before Feature Freeze
> deadline, we destabilize master. Right after FF, we must be focused on
> stability, and bug squashing.
> Now we
d it
in the next day or two, we will have to postpone the update to 6.1. Let's
focus on this task and bring new kernel in.
[1] https://wiki.openstack.org/wiki/Fuel/Soft_Code_Freeze
[2] https://wiki.openstack.org/wiki/Fuel/6.0_Release_Schedule
--
https://blueprints.launchpad.net/mos/+spec/sahara-create-default-templates
>>> >
>>> > ___
>>> > OpenStack-dev mailing list
>>> > OpenStack-dev@lists.openstack
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Vitaly Kramskikh,
>> > Software Engineer,
>> > Mirantis, Inc.
>> >
>> > ___
>> > OpenStack-dev mailing list
>> > OpenStack-dev@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Vitaly Kramskikh,
> Software Engineer,
> Mirantis, Inc.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
wanter.com/images/article-images/mirantis-35-blog-780x.png
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
, but the question
> is
> > can we do anything to fix it in the current release?
> >
> > [1]
> >
> http://ehaselwanter.com/en/blog/2014/10/15/deploying-openstack-with-mirantis-fuel-5-1/
> > [2]
> http://ehaselwanter.com/images/article-images/mirantis-35-b
iled there are probably deployment-specific, but still I bet there is
>> a lot of bugs in OS projects you run into. If you could tag those
>> using OS projects names (e.g. you already have the 'neutron' tag, but
>> not 'nova' one) when triaging new bugs, tha
Actually I agree on tagging bugs as Roman suggests.
If no one against, we can create official tags for every project (nova,
neutron, etc.) - as long as it simplifies life and easy to use, I'm all for
it.
On Thu, Jun 19, 2014 at 6:26 AM, Mike Scherbakov
wrote:
> +1 to this approach.
&g
edeployed from master on daily basis
[1]
http://docs.mirantis.com/fuel-dev/develop/nailgun/development/env.html#running-nailgun-in-fake-mode
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.opens
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailin
ct tags can still be useful due to Launchpad advanced
> search limitations.
>
> Thanks,
> Roman
>
> On Thu, Jun 19, 2014 at 5:29 AM, Mike Scherbakov
> wrote:
> > Actually I agree on tagging bugs as Roman suggests.
> > If no one against, we can create official tags for ev
I'll
let Dmitry Borodaenko to lead all bugs related activities, he is Bug Master
for this release :)
[1]
http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-06-19-16.00.log.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2014-June/037746.html
Thanks,
--
Mik
t;
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Andrew
> Mirantis
> Ceph community
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
t;>
>> >>
>> >>
>> >>
>> >> --
>> >> Andrew
>> >> Mirantis
>> >> Ceph community
>> >
>> >
>> >
>> >
>> > --
>> > Andrew
>> > Mirantis
>> >
/+spec/mellanox-features-support
[3]
https://blueprints.launchpad.net/fuel/+spec/neutron-nsx-plugin-integration
[4] https://review.openstack.org/#/c/103280/
[5] https://blueprints.launchpad.net/fuel/+spec/galera-improvements
Let me quickly know if I miss anything.
--
Mike Scherbakov
#mihgen
openrc file has to be up to date for some of the HA scripts to
>>>>> work, we could just source that.
>>>>>
>>>>> On Fri, Jun 20, 2014 at 12:12 AM, Sergii Golovatiuk
>>>>> wrote:
>>>>> > +1 for #2.
>>>>> >
&g
://wiki.openstack.org/wiki/Fuel/5.1_Release_Schedule
Let me know if anything blocks us from doing SCF on 24th.
Thanks,
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
ed from the release. We could address
> this by having a review deadline the day prior to SCF, or watch excepted
> intently for revision the day after SCF.
>
>
>
> On Tue, Jul 22, 2014 at 8:08 AM, Mike Scherbakov > wrote:
>
>> Hi Fuelers,
>> Looks like we are more or
> +7 (903) 156-0836
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
orry that first step may be quite hard to implement, here we need
> expertise from Fuel team.
>
>
>
> On Wed, Jul 23, 2014 at 5:53 PM, Mike Scherbakov > wrote:
>
>> Hi Serg,
>> what needs to be done in order to include Alembic-related stuff into 5.1?
>> The thin
I'm not against creating bugs initially with such a title to make visual
search easier.
However I think that re-titling existing bugs is not needed, as at leads to
spam.
Mike Scherbakov
#mihgen
On Jul 23, 2014 4:24 AM, "Dmitry Borodaenko"
wrote:
> +1
>
> To provi
Sorry, we did the best to get it in... Risk looks high to me. We also
update OpenStack itself from stable/icehouse, which is also risky; +
Mellanox & NSX. To avoid broken master, I'd go with merged, seems to be
working version of ML2, and merge Andrew's patchset into 6.0.
Mike Sche
/1337823
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
Op
__
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
se move the bug to 6.0.
Now, let's focus on Critical and High bugs. We just have 2 weeks to squash
them.. let's work collaboratively, regroup when needed in order to make
Fuel stable!
Thanks all for the hard work!
--
Mike Scherbakov
#mihgen
t runs there in fake mode. Keystone mode is
>> enabled only on iso. If you want to test it locally you have to install
>> keystone and configure nailgun as Kamil explained.
>>
>> Regards,
>>
>>
>> On Thu, Jul 24, 2014 at 3:57 PM, Mike Scherbakov <
>>
ntis.ru
>> vkuk...@mirantis.com
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
tioned in
>>> > release notes
>>> >
>>> >
>>> >
>>> > ___
>>> > OpenStack-dev mailing list
>>> > OpenStack-dev@lists.openstack.org
>>> > http://lists.opensta
, Russia,
> www.mirantis.com <http://www.mirantis.ru/>
> www.mirantis.ru
> vkuk...@mirantis.com
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to : fuel-...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help : https://help.launchpad.net/ListHelp
>
>
--
Mike Scherbakov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
pad.net/~fuel-dev
>>>> Post to : fuel-...@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Yours Faithfully,
>
___
>>> 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
>>>
>> --
&g
the most robust way is to build a
> single container which
> has everything user needs.
>
> Regarding the spec our plan is to start writing spec after we have working
> POC.
>
> Thanks,
>
>
> On Tue, Oct 20, 2015 at 4:43 AM, Mike Scherbakov > wrote:
>
>> T
rg/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lis
of file[0] is correct.
>
>
> Nastya.
> [0] https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS
>
> On Wed, Oct 21, 2015 at 2:15 AM, Mike Scherbakov > wrote:
>
>> Simon,
>> I believe that it's a mistake in fuel-qa. Valid structure is in fuel-web.
&
edorova
> Fuel CI Engineer
> bookwar
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstac
we need one bug per project or do we
> piggy-back on the fuel-qa bug?
> BR,
> Simon
> [0] https://bugs.launchpad.net/fuel/+bug/1508449
> [1] https://review.openstack.org/#/c/238039/
>
> On Wed, Oct 21, 2015 at 8:11 AM, Mike Scherbakov > wrote:
>
>> Nastya,
>>
questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not
ole': 'management',
>>> > 'namespace': 'haproxy',
>>> > 'ipaddr': '10.10.10.10',
>>> > 'node_roles': ['controller']
>>> > },...
>>> > ]
>>
t / extend Stackalytics to make it..?
Thanks!
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
f you're
>> interested:
>>
>> http://blog.bitergia.com/2015/10/22/understanding-the-code-review-proce
>> ss-in-openstack/
>> <http://blog.bitergia.com/2015/10/22/understanding-the-code-review-proce%0Dss-in-openstack/>
>>
>> Saludos,
>>
>&
gest to get
together on FF day, Wednesday, and go over all the items we have been
working on in 8.0. What do you think folks? For instance, in #fuel-dev IRC
at 8am PST (4pm UTC)?
[1] https://wiki.openstack.org/wiki/Fuel/8.0_Release_Schedule
--
Mik
ck.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack
> Vitaly Parakhin.
> CI Engineer | Mirantis, Inc. | http://www.mirantis.com
> IRC: brain461 @ chat.freenode.net | Slack: vparakhin
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: opensta
>
>
> 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 don't quite understand how repo is organized. I see a lot of
>> > Python code regarding
it in there.
Thanks,
On Tue, Dec 1, 2015 at 1:37 AM Vladimir Kuklin wrote:
> Mike I think, it is rather good idea. I guess we can have a couple of
> requests still - although everyone is shy, we might get a little storm of
> FFE's. BTW, I will file at least one.
>
> On
12-02
Thanks,
On Wed, Dec 2, 2015 at 6:37 AM Igor Kalnitsky
wrote:
> Sheena,
>
> Yeah, we will have a meeting in #fuel-dev IRC channel. :)
>
> - Igor
>
> On Wed, Dec 2, 2015 at 4:25 PM, Sheena Gregson
> wrote:
> > Is the meeting at 8am PST today?
> >
> >
st that we don't push any exception further down, and if
something is not done by second deadline - it has to be disabled / reverted
in 8.0.
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage que
ailing 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 Develop
e
> disabled
> > by default and it will require specific actions for a user to start using
> > this feature. In meanwhile we will test this feature at Scale Lab and
> > against swarm and custom tests. And by SCF we may decide whether to
> switch
> > to it based on the reported results. If i
___
> 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
>
--
Mike Scherbakov
#mihgen
___
e
> stabilized.
>
> I would like to ask engineering and QA leads to express their ideas on
> this.
>
> Thanks,
> Dmitry.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-
and proceed with bugfixing as usual. At this point CI team will
> > need to update the Fuel ISO used for deployment tests in our CI to
> > this same ISO.
> >
> > One way or the other, we will be able to
usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Adam Heczko
> Security Engineer @ Mirantis Inc.
> __
>> bookwar
>>
>> ______
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.opensta
__
>> > 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
>>
>&g
On Wed, Dec 2, 2015 at 10:47 AM Mike Scherbakov
wrote:
> Hi all,
> we ran a meeting and made a decision on feature freeze exceptions. Full
> log is here:
> https://etherpad.openstack.org/p/fuel-8.0-FF-meeting
>
> The following features were granted with feature freeze exception
k 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
> >
> >
> >
> >
> _
s://etherpad.openstack.org/p/fuel-8.0-FF-meeting, line 428
[3]
http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html
[4]
http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-12-10-16.00.log.
c 2, 2015 at 7:47 PM, Mike Scherbakov
> wrote:
>
>> Hi all,
>> we ran a meeting and made a decision on feature freeze exceptions. Full
>> log is here:
>> https://etherpad.openstack.org/p/fuel-8.0-FF-meeting
>>
>> The following features were granted with
_
>> > >> >> OpenStack Development Mailing List (not for usage questions)
>> > >> >> Unsubscribe:
>> > >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >
;>>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org
>>>>>>>> ?subject:unsubscribe
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>>
>>>>>>>>
>>
'm getting tired of many (not relevant to me) bugs
flowing in my inbox, and stop paying attention. I'll have to create filter.
And if someone needs my attention in particular bug, subscribes me to it -
I'll miss it, as it will be filtered by the same way.
Thank you,
--
good
ideas, but didn't attract enough attention from cores and didn't land into
master as a result.
Anyway, I think we need to keep our review queues in better health. Can we
enable auto-abandon back again, if patch is hanging out for a month or more?
--
Mike Sch
uestions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Ma
..@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
__
> 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
>
epository is going to look like this
>>>>> https://github.com/kozhukalov/fuel-agent i.e. there is no additional
>>>>> sub-directory fuel_agent. In fact, I don't think it is a big deal to
>>>>> update
>>>>> all fuel agent related review
>
> See [1] for details.
>
> [1] https://help.launchpad.net/Bugs/Subscriptions
>
> On Tue, Jul 7, 2015 at 11:27 PM, Mike Scherbakov
> wrote:
> > Hi folks,
> > DevOps guys - when someone assigns bug to "Fuel for OpenStack", message
> is
> > b
rectory.
>>
>>
>> [1] https://github.com/stackforge/fuel-agent.git
>>
>> Vladimir Kozhukalov
>>
>> On Wed, Jul 15, 2015 at 2:19 AM, Mike Scherbakov <
>> mscherba...@mirantis.com> wrote:
>>
>>> Thanks Vladimir. Let's ensure t
hat's a very good plan ("Initial feedback/triage") Mike.
>>
>> thanks,
>> dims
>>
>> On Thu, Jul 9, 2015 at 3:23 PM, Mike Scherbakov
>> wrote:
>> > +1 for just reusing existing script, and adjust it on the way. No need
>> to
>> >
i Golovatiuk,
> Skype #golserge
> IRC #holser
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-b
: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for us
ure.
[1] https://blueprints.launchpad.net/fuel/+spec/ssl-endpoints
[2] https://blueprints.launchpad.net/fuel/+spec/fuel-ssl-endpoints
Stas, as you've been working on it, can you please provide current status?
Thanks,
--
Mik
>>
>>>
>>> On Thu, Jul 9, 2015 at 6:27 PM Stanislaw Bogatkin <
>>> sbogat...@mirantis.com> wrote:
>>>
>>>> 2 weeks seems too small for me. We easy can be in situation when fix
>>>> for medium bug is done, but SCF starts. And gap between
ome tests for it writing my QA - not all of them are done yet.
>
> I'll update blueprints as soon as possible. Sorry for inconvenience.
>
> On Mon, Jul 20, 2015 at 8:44 PM, Mike Scherbakov > wrote:
>
>> Hi guys,
>> did we enable SSL for Fuel Master node and OpenSt
uld document this as a known
>> user experience and provide instructions for users to swap out the
>> self-signed certificates that are enabled by default for their own internal
>> CA certificates/3rd party certificates.
>>
>>
>>
>> *From:* Mike Scherbakov
___
>> 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
>>
>>
>
03602/
> [4] https://review.openstack.org/#/c/201217/
>
> --
> Best regards,
> Aleksey Kasatkin
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.or
.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..
rnet tokens support.
> To: Vitaly Sedelnik , Eugene Bogdanov <
> ebogda...@mirantis.com>, Igor Marnat , Ilya
> Elterman , Mike Scherbakov <
> mscherba...@mirantis.com>, Roman Alekseenkov
>
>
> Colleagues,
>
> I would like to request an exception from the Fea
ack-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/listin
2015-07-23-16.00.html
>> --
>>
>> --
>>
>> Andrew Woodward
>>
>> Mirantis
>>
>> Fuel Community Ambassador
>>
>> Ceph Community
>>
> --
>
> --
>
> Andrew Woodward
>
> Mirantis
>
> Fuel Community Amba
ng List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
___
on controller nodes.
>
> We need 1 DevOps engineer and 1 QA engineer to be engaged for this work.
>
> So I think it's ok to accept this feature as an exception for feature
> freeze.
>
> Regards,
> Andrian Noga
> Project manager
> Partner Centric Engineering
&g
to be good to go...
I still think that additional Ceilometer support should be moved to the
next release.
Thanks,
On Thu, Jul 23, 2015 at 1:56 PM Mike Scherbakov
wrote:
> Hi Andrian,
> this is High priority blueprint [1] for 7.0 timeframe. It seems we still
> didn't merge the main pa
[4] https://review.openstack.org/#/c/203847/
> --
> --
> Andrew Woodward
> Mirantis
> Fuel Community Ambassador
> Ceph Community
>
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing L
_
> 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
>
--
Mike Scherbakov
#mihgen
_
atch and it matches an acceptance criteria for the feature
>> with some not critical known issues that already converted to launchpad
>> tickets.
>>
>> I believe we can land it in master tomorrow with +1 from SME.
>>
>> BTW, I see no intersection in reviewers wit
>
> Skype: MAKAPOB.AJIEKCAHDP
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi
for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
__
I could go
>>>>>>>>>>>> about
>>>>>>>>>>>> modifying the existing build system to be able to run
>>>>>>>>>>>> librarian-puppet to
>>>>>>>>>>>> prepare the sour
>> [2]
>> http://lists.openstack.org/pipermail/openstack-dev/2015-July/069744.html
>> [3] https://blueprints.launchpad.net/fuel/+spec/fuel-puppet-librarian
>>
>> --
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
>>
>> _
t;>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinf
of a user to use it. We want Fuel to be
flexible, and not too prescriptive.
Thanks,
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
ing underlay to only reflect customers
> who absolutely require it.
>
>
>
> There is not sufficient value in supporting nova-network for other use
> cases.
>
>
>
> *From:* Mike Scherbakov [mailto:mscherba...@mirantis.com]
> *Sent:* Wednesday, July 29, 2015 12:47 P
101 - 200 of 256 matches
Mail list logo
