rrow at 3pm UTC on
> #openstack-meeting4.
>
> https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack
>
> As usual, free free to bring topics in this etherpad:
> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160405
>
> We'll also have open discussion for bugs &a
>It is believed that reservation help to to reserve a set of resources
>beforehand and hence eventually preventing any other upcoming request
>(serial or parallel) to exceed quota if because of original request the
>project might have reached the quota limits.
>
>Questions :-
>1. Does reservation
On 05/04/16 06:43, Steven Hardy wrote:
On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote:
Why is imperative programming always brought up when discussing
conditionals in the templates? We are not wanting anything imperative. The
heat engine still picks the final ordering
All,
Just to document the discussion we had during the OSC IRC meeting last
week: I believe the consensus we reached was that it wasn't appropriate to
pretend "volume" before all Cinder commands but that it would be
appropriate to move in that direction to for any commands that may be
ambiguous
What about commands the become ambiguous in the future? I doubt there are
many operations or objects that are unique to Cinder - backup, snapshot,
transfer, group, type - these are all very much generic, and even if they
aren't ambiguous now, they might well become so in future...
On 5 April 2016
Duncan,
Agreed, but the OSC team is concerned about unnecessarily adding API names
into commands as much as the Cinder team wishes to make it clearer which
commands belong to our component. This is where we need to keep this
discussion open with the OSC team to find a good common ground. I am
Thank you for your awesome feedbacks!
> Another option is to add those tests to keystone itself (if you are not
>> including tests that triggers other components APIs). See
>> https://blueprints.launchpad.net/keystone/+spec/keystone-tempest-plugin-tests
>>
>>
>
>
knikolla and I are looking into
If you are subscribed to bug notifications from Trove, you'd have received a
lot of email from me over the past couple of days as I've gone through the LP
bug list for the project and attempted to do some spring cleaning.
Here's (roughly) what I've tried to do:
-many bugs that have been
Hirofumi Ichihara wrote:
Hi Ihar,
On 2016/04/05 7:57, Ihar Hrachyshka wrote:
Hi all,
in neutron, we have a bunch of configuration options to control advanced
filtering features for API, f.e. allow_sorting, allow_pagination,
allow_bulk, etc. Those options
Hi Sergey,
According to Matthew Mosesohn the plan is to delay branching of detach-*
plugins.
The only plugin scheduled for branching tomorrow seems to be a
fuel-plugin-murano.
--
Igor Belikov
Fuel CI Engineer
ibeli...@mirantis.com
> On 04 Apr 2016, at 15:11, Sergii Golovatiuk
On Tue, Apr 05, 2016 at 01:37:21PM +0100, Kiall Mac Innes wrote:
> Agreed on a separate repo.
>
> I'm honestly a little unsure how in-service-repo would ever work long
> term, given that tempest's requirements will match master, and may
> not be compatible with N releases ago's $service
On 01/04/16 12:31, Steven Hardy wrote:
On Fri, Apr 01, 2016 at 04:15:30PM +0200, Thomas Herve wrote:
On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote:
On 31/03/16 18:10, Zane Bitter wrote:
I'm in favour of some sort of variable-based implementation for a few
reasons.
Hi,
We are working on the possibility of including post-copy live migration
into Nova (https://review.openstack.org/#/c/301509/)
At libvirt level, post-copy live migration works as follow:
- Start live migration with a post-copy enabler flag
(VIR_MIGRATE_POSTCOPY). Note this does not
seems fine to me. we still don't have a story around events. we just
sort of store and dump it right now. i guess this could probably fit
into ceilometer split session... or maybe everyone is cool with just
pushing things to elasticsearch and letting users play with that + kibana.
On
Looks like the congress job is working now. We have a tarball for our
latest RC:
http://tarballs.openstack.org/congress/congress-3.0.0.0rc3.tar.gz
Thierry added the links back for the tarball.
https://github.com/openstack/releases/commit/beee35379b3b52ed7d444d93d7afd8b6603f69b6
So it looks
+1 to demand meetings and asynchronous way
On Thu, Mar 31, 2016 at 9:33 PM, Ildikó Váncsa
wrote:
> Hi Gordon,
>
> >
> > ie. the new PTL should checkpoint with subteam leads regularly to review
> spec status or identify missing resources on high-priority
> > items?
>
Thank you all for your awesome feedbacks!
On Sun, Apr 3, 2016 at 9:07 PM, Jamie Lennox wrote:
>
>
> On 2 April 2016 at 09:21, Rodrigo Duarte wrote:
>
>>
>>
>> On Thu, Mar 31, 2016 at 1:11 PM, Matthew Treinish
>> wrote:
>>
On Tuesday, April 5, 2016, Duncan Thomas wrote:
> What about commands the become ambiguous in the future? I doubt there are
> many operations or objects that are unique to Cinder - backup, snapshot,
> transfer, group, type - these are all very much generic, and even if
Having an extra node for FreeIPA spawn up by heat works for me. And it's
not a hard-requirement that we have to wire this into the TripleO CI. But
the most sustainable approach to having TLS everywhere (at least for the
admin and internal endpoints of Openstack, the message broker server nodes
and
I was trying to clean up the divergent logging definitions in devstack
as part of scrubbing out 'tenant' references -
https://review.openstack.org/#/c/301801/ and in doing so stumbled over
the fact that the extremely useful project_name and user_name fields are
not in base oslo.context.
On Tue, Apr 5, 2016 at 12:57 PM, Assaf Muller wrote:
> On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins
> wrote:
> > Russell Bryant wrote:
> >> because they are related to two different command line utilities
> >> (ovs-vsctl vs ovs-ofctl) that speak two
On 05/04/16 15:15 +, Amrith Kumar wrote:
If you are subscribed to bug notifications from Trove, you’d have received a
lot of email from me over the past couple of days as I’ve gone through the LP
bug list for the project and attempted to do some spring cleaning.
Here’s (roughly) what I’ve
On Tue, Apr 5, 2016 at 10:44 AM, Richard Theis wrote:
> Here are my preferences:
>
> 1. even week: E.1 or E.4
> 2. odd week: O.3
>
I really don't want to go against the API-WG but want to keep it on
Thursday if possible:
E.4
O.3
Thanks for doing this Sheel
dt
--
Dean
Sean,
I cannot speak to historically why there were not there, but I am working
through the app-agnostic-logging-parameters blueprint [1] right now and
it's very related to this. As part of this work I would be reviewing
attributes that are more commonly used in subclassed context objects for
Cool. Great.
In looking at this code a bit more I think we're missing out on some
commonality by the fact that this nice bit of common parsing -
https://github.com/openstack/oslo.context/blob/c63a359094907bc50cc5e1be716508ddee825dfa/oslo_context/context.py#L138-L161
is actually hidden behind a
Hi Monty,
Thanks for your guidance. I have appended your inputs to the blueprint [1].
[1] https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips
Best regards,
Honbgin
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: March-31-16 1:18 PM
To:
We're going to have a day of just cleaning out the launchpad bugs for
Nova on Monday 4/18.
This isn't a bug squashing day where people are proposing patches and
the core team is reviewing them.
This is purely about cleaning the garbage out of launchpad.
Markus Zoeller has a nice dashboard
I think the only thing standing in our way is this bug [1]. Ryan
Tidwell and I are working on this.
Carl
[1] https://bugs.launchpad.net/neutron/+bug/1543094
On Mon, Apr 4, 2016 at 3:48 PM, John Belamaric wrote:
> I was on vacation last week so I am just seeing this
Excerpts from Sean Dague's message of 2016-04-05 14:31:46 -0400:
> I was trying to clean up the divergent logging definitions in devstack
> as part of scrubbing out 'tenant' references -
> https://review.openstack.org/#/c/301801/ and in doing so stumbled over
> the fact that the extremely useful
On Tue, Apr 5, 2016, at 11:56 AM, Hochmuth, Roland M wrote:
> Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that
> I've caused.
>
> It sounds like all Python projects/deliverables are in reasonable shape,
> but if not, please let me know.
>
> Not sure what we should do
Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that I've
caused.
It sounds like all Python projects/deliverables are in reasonable shape, but if
not, please let me know.
Not sure what we should do about the jars at this point. We had started to
discuss a plan to
Hi all,
Thanks for your inputs. We discussed this proposal in our team meeting [1], and
we all agreed to support an option to remove the need of floating IPs. A
blueprint was created for implementing this feature:
https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips . Please
Egor,
I agree with you. I think Magnum should support another option to connect a bay
to an existing neutron private network instead of creating one. If you like, we
can discuss it separately in our next team meeting or in the design summit.
Best regards,
Hongbin
From: Guz Egor
As we discuss the glance v2 spec for nova, questions are coming up
around what to do about the nova images API which is a proxy for glance v1.
I don't want to add glance v2 support to the nova API since that's just
more proxy gorp.
I don't think we can just make the nova images API fail if
On Apr 5, 2016 2:49 PM, "Matt Riedemann" wrote:
>
> As we discuss the glance v2 spec for nova, questions are coming up around
what to do about the nova images API which is a proxy for glance v1.
>
> I don't want to add glance v2 support to the nova API since that's
On 04/05/2016 03:56 AM, Thierry Carrez wrote:
We seem to have a sahara-extra build alright:
http://tarballs.openstack.org/sahara-extra/
Please ignore the noise :)
ah, excellent!
thanks for the clarification Thierry
regards,
mike
Yeah, and they just deprecated vendor data plugins too, which eliminates my
other workaround. :/
We need to really discuss this problem at the summit and get a viable path
forward. Its just getting worse. :/
Thanks,
Kevin
From: Juan Antonio Osorio
On 05/04/16 16:33, Daniel P. Berrange wrote:
On Tue, Apr 05, 2016 at 05:17:41PM +0200, Luis Tomas wrote:
Hi,
We are working on the possibility of including post-copy live migration into
Nova (https://review.openstack.org/#/c/301509/)
At libvirt level, post-copy live migration works as follow:
All,
As discussed briefly today in our weekly meeting, I've started this
etherpad:
https://etherpad.openstack.org/p/newton-tripleo-sessions
We have two fishbowl sessions and 3 working sessions, plus a half-day
contributor meetup.
Please can everyone dump ideas of what topics you'd like to
I was planning to bring it up informally for TripleO. But it would be cool
to have a slot to talk about this.
BR
On 5 Apr 2016 18:51, "Fox, Kevin M" wrote:
> Yeah, and they just deprecated vendor data plugins too, which eliminates
> my other workaround. :/
>
> We need to
Here are my preferences:
1. even week: E.1 or E.4
2. odd week: O.3
Thanks,
Richard
> Dear All,
>
> This is regarding deciding meeting time for OSC team to facilitate
> appropriate time for APAC guys.
> We are planning to have meeting on alternate weeks for this purpose.
>
> Some of the
Akshay,
Note that version 6 is now released so please use the official image from the
OpenStack App Catalog and update your code to latest.
The doc has also been updated, you might want to have a look at the new arch
section and gallery - those should help you with the questions you had below
I am OK with any of the proposed times.
stevemar
From: Richard Theis
To:
Date: 2016/04/05 11:46 AM
Subject:[openstack-dev] [osc] Meeting time preferences for OSC team
Here are my preferences:
1. even week: E.1 or E.4
+1 from me :)
// jim
> On Apr 5, 2016, at 03:24, Dmitry Tantsur wrote:
>
> Hi!
>
> I'd like to propose Anton to the ironic-inspector core reviewers team. His
> stats are pretty nice [1], he's making meaningful reviews and he's pushing
> important things (discovery, now
On Mon, Apr 4, 2016 at 7:36 PM, Armando M. wrote:
>
>
> On 4 April 2016 at 17:08, Jay Pipes wrote:
>>
>> On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote:
>>>
>>> - why do we even need to control those features with configuration
>>> options? can we deprecate
> On Apr 2, 2016, at 05:46, Doug Hellmann wrote:
>
> Excerpts from Julia Kreger's message of 2016-04-01 18:21:24 -0400:
>>> On Fri, Apr 1, 2016 at 4:48 PM, Doug Hellmann wrote:
>>>
>>> Excerpts from Doug Hellmann's message of 2016-04-01 16:25:07
On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins wrote:
> Russell Bryant wrote:
>> because they are related to two different command line utilities
>> (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs
>> OpenFlow) that talk to two different daemons on the
On Tue, Apr 05, 2016 at 05:17:41PM +0200, Luis Tomas wrote:
> Hi,
>
> We are working on the possibility of including post-copy live migration into
> Nova (https://review.openstack.org/#/c/301509/)
>
> At libvirt level, post-copy live migration works as follow:
> - Start live migration with a
Russell Bryant wrote:
> because they are related to two different command line utilities
> (ovs-vsctl vs ovs-ofctl) that speak two different protocols (OVSDB vs
> OpenFlow) that talk to two different daemons on the system (ovsdb-server vs
> ovs-vswitchd) ?
True, they influence two different
Thanks Amrith.
I'll follow your lead and do some triaging as well.
We should organize bug triage days to make this process easier next time.
2016-04-05 14:44 GMT-03:00 Flavio Percoco :
> On 05/04/16 15:15 +, Amrith Kumar wrote:
>
>> If you are subscribed to bug
As a recent newcomer to using our client libraries, my only real objection
to this plan is that our client libraries as a mess [1][2]. The interfaces
we expect users to use are quite different for basic things like initial
auth between the various clients, and by introducing another library we
++!
2016-04-05 17:54 GMT-03:00 Amrith Kumar :
>
>
> *From:* Victoria Martínez de la Cruz [mailto:
> victo...@vmartinezdelacruz.com]
> *Sent:* Tuesday, April 05, 2016 4:35 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
>
-Original Message-
From: Michael Still
Reply: OpenStack Development Mailing List (not for usage questions)
Date: April 5, 2016 at 16:11:05
To: OpenStack Development Mailing List (not for usage questions)
On Wed, Apr 6, 2016 at 7:28 AM, Ian Cordasco wrote:
>
>
> -Original Message-
> From: Michael Still
> Reply: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Date: April 5, 2016 at 16:11:05
>
From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com]
Sent: Tuesday, April 05, 2016 4:35 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][trove] Trove bug scrub
Thanks Amrith.
I'll
-Original Message-
From: Michael Still
Reply: Michael Still
Date: April 5, 2016 at 16:30:36
To: Ian Cordasco
CC: OpenStack Development Mailing List (not for usage questions)
Subject:
I have created a version that use constructor arguments. [5]
I will review in more detail across projects the use of keystone middleware
to see if we can utilize a constructor environment attribute to simply
constructor usage.
[5] https://review.openstack.org/301918
Ronald Bradford
Web Site:
On Tue, 5 Apr 2016 13:58:44 +0100
"Daniel P. Berrange" wrote:
> Along similar lines we have proposals to add vGPU support to Nova,
> where the vGPUs may or may not be exposed using SR-IOV. We also want
> to be able to on the fly decide whether any physical GPU is assigned
>
Hi Keystone devs,
Blueprint [1] related to request-ids is approved for Mitaka and
its implementation [2] is up for review for quite a long time.
I would like to apply for a goal for this blueprint so that
it can be included in Newton.
[1]
I think in the interest of supporting the OSC effort, I am with
deprecating the CLI stuff (possibly glanceclient too -- BUT in a
different thread).
I believe removing the bindings/modules that support possibly OSC and
other libs might be lot trickier. (nova proxy stuff for glance may be an
We have a use case where we want to register a newly spawned Virtual
machine with an identity provider.
Heat also has a need to provide some form of Identity for a new VM.
Looking at the set of utilities right now, there does not seem to be a
secure way to do this. Injecting files does not
On Tue, Apr 5, 2016 at 4:35 PM, Ian Cordasco wrote:
> The goal is to centralize the server expertise and have that be combined
> with the folks who know how to better design a library for a good developer
> experience (kind of like with osc). That said, I think the SDK
Hi team,
As mentioned in the team meeting, Magnum team is using an etherpad [1] to
collaborate topics for design summit. If you interest to join us in the Newton
design summit, I would request your inputs in the etherpad. In particular, you
can do the followings:
* Propose new topics that you
Thanks for the pointer Clark. We will look into using that, although we were
running out of time on the Mitaka release to get something like that
implemented.
Craig Bryant is in the process of manually updating the versions in the pom
files to match the Mitaka tags. A couple of reviews are
On Tue, Apr 5, 2016 at 11:53 AM, Minying Lu wrote:
> Thank you for your awesome feedbacks!
>
>
>> Another option is to add those tests to keystone itself (if you are not
>>> including tests that triggers other components APIs). See
>>>
Armando M. wrote:
> I would like to understand if these need new owners (both assignees and
> approvers). Code submitted [5,6] has not been touched in a while, and
> whilst I appreciate people have been busy focussing on Mitaka (myself
> included), the Newton master branch has been open for a
Adam Young wrote:
We have a use case where we want to register a newly spawned Virtual
machine with an identity provider.
Heat also has a need to provide some form of Identity for a new VM.
Looking at the set of utilities right now, there does not seem to be a
secure way to do this. Injecting
Hello everyone,
Due to a release-critical issue spotted in Keystone during RC2 testing, a
new release candidate was created for Mitaka. You can find the RC3
source code tarball at:
https://tarballs.openstack.org/keystone/keystone-9.0.0.0rc3.tar.gz
Unless new release-critical issues are found
On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
> I finally have enough understanding of what is going on with Tripleo
> to
> reasonably discuss how to implement solutions for some of the main
> security needs of a deployment.
>
>
> FreeIPA is an identity management solution that can
On 04/05/2016 07:06 PM, Dan Prince wrote:
On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
I finally have enough understanding of what is going on with Tripleo
to
reasonably discuss how to implement solutions for some of the main
security needs of a deployment.
FreeIPA is an identity
from_environ was mine, it's reasonably new and at the time i was blocked
upon getting a release before pushing it out to services. Since then i've
been distracted with other things. The intent at the time was exactly this
to standardize the values on the context object, though in my case i was
On 04/05/2016 09:01 AM, Steven Hardy wrote:
On Tue, Apr 05, 2016 at 02:07:06PM +0300, Juan Antonio Osorio wrote:
On Tue, Apr 5, 2016 at 11:36 AM, Steven Hardy wrote:
On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote:
> I finally have enough
On 04/05/2016 08:02 AM, Hayes, Graham wrote:
On 02/04/2016 22:33, Adam Young wrote:
I finally have enough understanding of what is going on with Tripleo to
reasonably discuss how to implement solutions for some of the main
security needs of a deployment.
FreeIPA is an identity management
On 04/05/2016 09:06 PM, Dan Prince wrote:
On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
I finally have enough understanding of what is going on with Tripleo
to
reasonably discuss how to implement solutions for some of the main
security needs of a deployment.
FreeIPA is an identity
+1 from me, and congrats!
On Wed, Apr 6, 2016 at 12:45 AM, Jim Rollenhagen
wrote:
> +1 from me :)
>
> // jim
>
> > On Apr 5, 2016, at 03:24, Dmitry Tantsur wrote:
> >
> > Hi!
> >
> > I'd like to propose Anton to the ironic-inspector core reviewers
On 04/05/2016 05:07 PM, Michael Still wrote:
As a recent newcomer to using our client libraries, my only real
objection to this plan is that our client libraries as a mess [1][2].
The interfaces we expect users to use are quite different for basic
things like initial auth between the various
At Tue, 5 Apr 2016 12:57:33 -0400,
Assaf Muller wrote:
>
> On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins wrote:
> > Russell Bryant wrote:
> >> because they are related to two different command line utilities
> >> (ovs-vsctl vs ovs-ofctl) that speak two different protocols
On 04/05/2016 11:42 AM, Fox, Kevin M wrote:
Yeah, and they just deprecated vendor data plugins too, which
eliminates my other workaround. :/
We need to really discuss this problem at the summit and get a viable
path forward. Its just getting worse. :/
Thanks,
Kevin
Sorry the for delayed response on this message. Finishing out Mitaka has been
quite time consuming!
Cross region searching is a high priority item for Searchlight in Newton.
Steve has begun work on the spec [1] with initial prototyping. We also are
considering this as a likely candidate for
Emm... finally this is brought up. We from IBM have already done some
work on FPGA/GPU resource management [1]. Let me bring the SMEs into
this discussion and see if we together can work out a concrete roadmap
to land this upstream.
Fei and Yonghua, this is indeed very interesting a topic for us.
+1000. Totally in favor of this, if anything it seems overdue, I'm a bit
surprised that they aren't already deprecated. Two alternatives exist for
the CLI (osc and glanceclient), and two alternatives exist for python API
bindings (SDK and glanceclient).
This should follow the same case with the
Not an expert of Nova but I am really shocked by such a change. Because
I'm not a Nova expert, I don't have a say on the *huge* efforts in
maintaining some builtin/default flavors. As a user I don't care where
the data have been stored, but I do care that they are gone. They are
gone because they
On Wed, Apr 6, 2016 at 4:06 AM, Dan Prince wrote:
> On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
> > I finally have enough understanding of what is going on with Tripleo
> > to
> > reasonably discuss how to implement solutions for some of the main
> > security needs
Hi,
On Tue, Apr 5, 2016 at 8:58 PM, Daniel P. Berrange wrote:
>> As you can see, it seems not complicated at this point, however it
>> become more complex due to following things we also have to take into
>> consideration:
I agree with this. Many kinds of resources could be
On Wed, Apr 6, 2016 at 1:44 PM, Qiming Teng wrote:
> Not an expert of Nova but I am really shocked by such a change. Because
> I'm not a Nova expert, I don't have a say on the *huge* efforts in
> maintaining some builtin/default flavors. As a user I don't care where
>
michael mccune wrote:
On 04/01/2016 04:48 PM, Doug Hellmann wrote:
Excerpts from Doug Hellmann's message of 2016-04-01 16:27:42 -0400:
Sahara team,
We noticed in our audit of the links on
http://releases.openstack.org/mitaka/index.html that the links to
the build artifacts for sahara-extras
On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote:
> I finally have enough understanding of what is going on with Tripleo to
> reasonably discuss how to implement solutions for some of the main security
> needs of a deployment.
>
>
> FreeIPA is an identity management solution that can
I agree,
The client should pass the query
Eyal
On Tue, Apr 5, 2016 at 9:23 AM, Afek, Ifat (Nokia - IL) wrote:
> Hi,
>
> vitrage topology show has a different behavior for a tree and a graph.
>
> In case it is called with no query:
> * For a tree it returns the node,
Hello,
At the beginning of the work, we've taken fuel-agent driver from Ironic
team and customized it.
Here is main features, which were created during development for Cray (all
of them are now part of bareon-ironic):
1. deploy-config could be stored in multiple places (image meta,
Hi All,
As part of the cross project Quota library effort [1] there has been a
discussion around the need for reservations or getting rid of reservations
altogether.
It is believed that reservation help to to reserve a set of resources
beforehand and hence eventually preventing any other
Hi Fuelers!
I kindly ask you to review my patches [0] and [1].
There is a "big thing" going on there. I'm trying to decouple
Volume Manager from Nailgun. It's a first step towards
Fuel modularisation, which will also be an example for
other developers: "How to implement Nailgun extensions".
Dear All,
I am newbie for openstack development and trying to understand the flow using
code base.
As the code base is very huge need your support to understand it.
Please let me know if there are any such way to debug the code or analyse it.
Any kind of help will be appreciated.
Thanks &
Hi folks,
we've merged all the changes related to fixtures update [0] and bugfix to
unblock noop tests [1]. So if you see -1 from fuel_noop_tests [2] in tests
not related to your patch, then please rebase.
Regards,
Alex
[0] https://review.openstack.org/#/q/topic:update-fixtures-to-9.0
[1]
Hi!
I'd like to propose Anton to the ironic-inspector core reviewers team.
His stats are pretty nice [1], he's making meaningful reviews and he's
pushing important things (discovery, now tempest).
Members of the current ironic-inspector-team and everyone interested,
please respond with your
Davanum Srinivas wrote:
Please see below:
On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote:
Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +:
Hi Doug, You had mentioned issues with three repos:
1. monasca-ceilometer
2. monasca-log-api
3.
Hi,
We have a very good discussion about cross OpenStack L2 networking last week:
https://etherpad.openstack.org/p/TricircleCrossPodL2Networking
Let's continue the discussion and other topics in this weekly meeting.
IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every
Hi folks,
I've started to fill in the blank for our next design summit sessions.
The schedule is at:
https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Telemetry%3A
We still have the 2 first work sessions empty, because I ran out of
idea. I've used the Etherpad we
There are developers doc which can help you to understand particular
component framework and codes.
http://docs.openstack.org/developer/openstack-projects.html
Depends on project you want to deep dive you can check their doc. For
example Nova nova one can be found here -
Armando M. wrote:
On 4 April 2016 at 17:08, Jay Pipes wrote:
On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote:
- why do we even need to control those features with configuration
options? can we deprecate and remove them?
This would be my choice.
On Tue, 5 Apr 2016, Julien Danjou wrote:
Any items/ideas we could discussion in this remaining sessions?
Any project we could/should invite to discuss with us?
Nova has started work on versioned notifications:
1 - 100 of 121 matches
Mail list logo