ent 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
>>
>>
at 12:22 AM Mike Scherbakov <mscherba...@mirantis.com>
wrote:
> FakeUI, which is based on fake threads, is obviously needed for
> development purposes.
> Ideally we need to refactor our integration tests, so that we don't run
> whole pipeline in every test. To start, I suggest t
enstack-dev
> >
> >
> >
> >
> > --
> > Vitaly Kramskikh,
> > Fuel UI Tech Lead,
> > Mirantis, Inc.
> >
> >
> __
> > OpenStack Development Mailing List (not for usage ques
before we do this we should have clear
> migration plan. According to this thread, some parts are still not clear.
>
> 2016-03-11 22:00 GMT+03:00 Mike Scherbakov <mscherba...@mirantis.com>:
>
>> Deprecation warning for Fuel Mitaka:
>> https://bugs.launchpad.net/fuel/+bug
ribe what we should do in order
> to remove logs from UI and Nailgun? I also propose to file a bug about
> adding a deprecation warning to Mitaka release of Fuel.
>
>
> 11 бер. 2016 р. о 16:55 Bogdan Dobrelya <bdobre...@mirantis.com>
> написав(ла):
>
>
> On 03/11
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/listinfo/openstack-dev
> >>>
> >>
> >>
> ___
ting "releases" list.
>
> Regards,
> Alex
>
> [0]
> https://github.com/openstack/fuel-plugin-external-lb/blob/68fc91a2d3360f19605180d7c3d8683227c8d5b1/metadata.yaml#L11-L21
>
>
> On Thu, Mar 10, 2016 at 10:22 AM, Bogdan Dobrelya <bdobre...@mirantis.com&
t; https://review.openstack.org/#/c/287286/
> >> #2 - Requires a blueprint and new docs, but okay.
> >> #3 - Yes! We have very poor CI for fuel plugin builder. All it does is
> >> ensure it makes a plugin, not that it can be installed and deployed.
> >>
> >
gt;>>> >> >>> Please share your opinions and let's decide which way to go
>>>>> with this
>>>>> >> >>> bug[2]
>>>>> >> >>>
>>>>> >> >>> [0]
>>>>> https://github.com/openstack/fu
lugin code (no code duplication, single repo for multiple
releases).
Thoughts?
[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-March/088211.html
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not
mediately*. If you are able to stick
> to this plan, there is still time to complete the transition today
> without requiring an FFE.
>
> --
> Dmitry Borodaenko
>
>
> On Wed, Mar 02, 2016 at 05:53:53PM +, Mike Scherbakov wrote:
> > Formally, we can merge it today. Hist
gt;> >>> > http://www.mirantis.com
>>> >>> >
>>> >>> >
>>> >>> >
>>> ______
>>> >>> > OpenStack Development Mailing List (not for
ack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> __
>>>
; >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> > >> >>
>> > >> >
>> > >> >
>> > >> >
>> _
t; Hi all,
>
> On Wed, Dec 2, 2015 at 7:47 PM, Mike Scherbakov <mscherba...@mirantis.com>
> 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-F
5 at 10:47 AM Mike Scherbakov <mscherba...@mirantis.com>
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 fr
ad.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.html,
16:3
_
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.open
_________
> 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
_
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-dev-requ...@lists.openstack.o
is acceptable, we lift the merge freeze straight
> > away 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 resume bugfixing on Monday
> > Is the meeting at 8am PST today?
> >
> >
> >
> > From: Mike Scherbakov [mailto:mscherba...@mirantis.com]
> > Sent: Wednesday, December 02, 2015 1:57 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > <openstack-
sults. If it happens before SCF, we will be
> > able to significantly ramp up our development and bugfixing velocity.
> >
> > --
> > Yours Faithfully,
> > Vladimir Kuklin,
> > Fuel Library Tech Lead,
> > Mirantis, Inc.
> > +7 (495) 640-49-04
> > +7 (926
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 questions)
Unsubscribe:
pment 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
>
--
Mike Scherbakov
#mihgen
___
c 1, 2015 at 10:28 AM, Mike Scherbakov <mscherba...@mirantis.com
> > wrote:
>
>> Hi Fuelers,
>> we are couple of days away from FF [1]. I have not noticed any request
>> for feature freeze exception, so I assume that we pretty much decided what
>> is going into
e".
>
>
>
>
>
> Vladimir Kozhukalov
>
> On Tue, Dec 1, 2015 at 1:25 PM, Thomas Goirand <z...@debian.org> 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
>>
qu...@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-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List
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
--
Mike Scherbakov
#mihgen
nly have complete changeset values, check if 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/>
>>
>>
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.org/cgi-bin
er-defined value
>>> or to
>>> > None (null in YAML).
>>> > When it is set to None, IP address will be allocated automatically.
>>> When the
>>> > user runs GET
>>> > request for the first time, all 'ipaddr' fields are equal to None. So,
usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mike Scherbakov
#mihgen
__
OpenStack Developm
istinfo/openstack-dev
> >
>
>
> --
> Aleksandra Fedorova
> Fuel CI Engineer
> bookwar
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.open
e. Do you think 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 <mscherba...@miranti
be:
>> 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)
>
implest and 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 <mscherba
y,
> structure 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 <mscherba...@mirantis.com
> > wrote:
>
>> Simon,
>> I believe that it's a mistake in fuel
gt;>>>
>>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>
com <http://www.mirantis.ru/>
> www.mirantis.ru
> vkuk...@mirantis.com
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
mail,
> it contains your personal unique token for the voting.
>
> The estimated date for the voting end is Oct 22.
>
> Thanks.
>
> On Tue, Oct 13, 2015 at 4:05 PM, Tomasz Napierala <tnapier...@mirantis.com
> > wrote:
>
>> Congrats Dmitry! Well deserved.
>
>
> > If you have any questions/suggestion don't hesitate to ask.
> >
> > Thanks,
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
>
___
> 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
#mihg
e help by posting comments to our existing user
> story[2].
>
>
> [1] https://wiki.openstack.org/wiki/ProductTeam
> [2]
> http://specs.openstack.org/openstack/openstack-user-stories/user-stories/draft/lifecycle_management.html
>
> Thanks,
> Shamail
>
> > On Oct 14,
you,
--
Mike Scherbakov
#mihgen
__
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.org/p/fuel-bugs-taxonomy
>
> Feel free to ask questions.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://list
;> +7 (926) 702-39-68
>>> Skype kuklinvv
>>> 35bk3, Vorontsovskaya Str.
>>> Moscow, Russia,
>>> www.mirantis.com <http://www.mirantis.ru/>
>>> www.mirantis.ru
>>> vkuk...@mirantis.com
>>>
>>>
>>> _
is thread:
> https://review.openstack.org/230195
>
> Please review carefully. Note that I intentionally didn't touch any of
> the plugins ACLs, primarily to save time for us and the
> openstack-infra team until after the stackforge->openstack namespace
> migration.
>
> On
;
>> > According to the description of the role, I wouldn't say that the role
>> is less architectural than
>> > political, since PTL should review designs and resolve conflicts
>> between cores (which are
>> > usually technical), PTL should also have strong skills in
Wed, Sep 30, 2015 at 5:48 PM Mike Scherbakov <mscherba...@mirantis.com>
wrote:
> Vladimir,
> we may mix technical direction / tech debt roadmap and process, political,
> and people management work of PTL.
>
> PTL definition in OpenStack [1] reflects many things which P
Hi team,
where do we stand with it now? I remember there was a plan to remove
nova-network support in 7.0, but we've delayed it due to vcenter/dvr or
something which was not ready for it.
Can we delete it now? The early in the cycle we do it, the easier it will
be.
Thanks!
--
Mike Scherbakov
gt; 35bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com <http://www.mirantis.ru/>
> www.mirantis.ru
> vkuk...@mirantis.com
> __
> OpenStack Development Mailing List (not for usage question
ards,
> Oleg Gelbukh
>
> On Sun, Sep 20, 2015 at 11:56 PM, Mike Scherbakov <
> mscherba...@mirantis.com> wrote:
>
>> Hi all,
>> as of my larger proposal on improvements to code review workflow [1], we
>> need to have cores for repositories, not for the whole F
1,members
[13] https://review.openstack.org/#/admin/groups/662,members
[14] https://review.openstack.org/#/admin/groups/663,members
[15] https://review.openstack.org/#/admin/groups/624,members
[16] http://stackalytics.com/report/contribution/fuel-specs/180
--
Mike Scher
l Library Tech Lead,
>> > > Mirantis, Inc.
>> > > +7 (495) 640-49-04
>> > > +7 (926) 702-39-68
>> > > Skype kuklinvv
>> > > 35bk3, Vorontsovskaya Str.
>> > &
penstack-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 usage
> >> connectivity, but they are related. Any changes to remove a local
> repository
> >> and only provide an internet based solution makes internet connectivity
> >> something that needs to be included in the discussion. I just want to
> make
>
improved process to
>>> allow for people to provide in place modifications for an environment, we
>>> can't do away with the rsync.
>>>
>>> If we want to go completely down the package route (and we probably
>>> should), we need to make sure that all of the other pieces that cu
- Updates on progress in other areas not related to bugs
Thanks,
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
List (not for usage questions)
> >> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> __
> > OpenSt
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
...@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-dev-requ
__
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
?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-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 usage questions)
Unsubscribe: openstack-dev-requ
/03/27/checklist-performing-openstack-code-reviews/
[19] http://stackalytics.com/report/contribution/fuel-group/180
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
__
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
master node console?)
Thanks,
[1] http://irclog.perlgeek.de/fuel-dev/2015-08-17
On Mon, Aug 17, 2015 at 10:08 AM Mike Scherbakov mscherba...@mirantis.com
wrote:
Hi all,
what is the current status of the feature in terms of readiness for
production use? I'm wondering as I see a number of bugs
)
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 for usage
?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-dev-requ
/mailman/listinfo/openstack-dev
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
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 PM
*To:* OpenStack Development Mailing List (not for usage questions)
openstack-dev
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.openstack.org
(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
__
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
__
OpenStack Development
...@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-dev
SME.
BTW, I see no intersection in reviewers with this patch
https://review.openstack.org/#/c/204321/.
Thank you,
Julia
On Thu, Jul 23, 2015 at 9:40 PM Mike Scherbakov mscherba...@mirantis.com
wrote:
-1
My concerns are the following:
1. This feature is of a High priority
/listinfo/openstack-dev
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
-dev
--
Mike Scherbakov
#mihgen
__
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
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
__
OpenStack Development
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 mscherba...@mirantis.com
wrote:
Hi Andrian,
this is High priority blueprint [1] for 7.0 timeframe. It seems we still
didn't merge the main
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
Mirantis, Inc
Mob.phone: +38 (063) 966-21-24
Email: an...@mirantis.com
Skype: bigfoot_ua
--
Mike Scherbakov
#mihgen
Woodward
Mirantis
Fuel Community Ambassador
Ceph Community
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
__
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
/listinfo/openstack-dev
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-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
--
Mike Scherbakov
#mihgen
for
Fernet tokens support.
To: Vitaly Sedelnik vsedel...@mirantis.com, Eugene Bogdanov
ebogda...@mirantis.com, Igor Marnat imar...@mirantis.com, Ilya
Elterman ielter...@mirantis.com, Mike Scherbakov
mscherba...@mirantis.com, Roman Alekseenkov ralekseen...@mirantis.com
Colleagues,
I would like
)
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 for usage
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
__
OpenStack
__
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
- 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 mscherba...@mirantis.com
wrote:
Hi guys,
did we enable SSL for Fuel Master node and OpenStack REST API endpoints
by default? If not, let's
out the
self-signed certificates that are enabled by default for their own internal
CA certificates/3rd party certificates.
*From:* Mike Scherbakov [mailto:mscherba...@mirantis.com]
*Sent:* Wednesday, July 22, 2015 1:12 AM
*To:* Stanislaw Bogatkin; Sheena Gregson
*Cc:* OpenStack Development
be extremely
conservative, for example: CR has a negative vote from a core reviewer AND
there were no comments or positive votes from anyone after that AND it has
not been touched in any way for 2 months.
On Wed, Jul 15, 2015 at 5:10 PM Mike Scherbakov mscherba...@mirantis.com
wrote:
Folks
://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,
--
Mike Scherbakov
#mihgen
__
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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
(Initial feedback/triage) Mike.
thanks,
dims
On Thu, Jul 9, 2015 at 3:23 PM, Mike Scherbakov
mscherba...@mirantis.com wrote:
+1 for just reusing existing script, and adjust it on the way. No need
to
immediately switch from infinite time to a couple of weeks, we can
always
adjust it later
believe it gonna be fine until there are more than one fuel-agent
packages in rpm repository.
Next step is to remove stackforge/fuel-web/fuel_agent directory.
[1] https://github.com/stackforge/fuel-agent.git
Vladimir Kozhukalov
On Wed, Jul 15, 2015 at 2:19 AM, Mike Scherbakov
mscherba
1 - 100 of 244 matches
Mail list logo
