+1 to maintain example plugins. It is easy enough and really lowering
barriers for people who just begin create plugins.
On Fri, Mar 4, 2016 at 2:08 PM, Matthew Mosesohn
wrote:
> Igor,
>
> It seems you are proposing an IKEA approach to plugins. Take Fuel's
> example plugin, add in the current Fu
What are you facing?
On Fri, Mar 4, 2016 at 9:06 PM, John Spray wrote:
> Hi,
>
> What expectations should driver authors have about multiple instances
> of the driver being instantiated within different instances of
> manila-share?
>
> For example, should I assume that when one instance of a driv
> Hey Folks,
>
> I'm looking at doing some cleanups in our repo and I would like to start by
> deprecating the `run_tests` script and the contents in the `tools/` dir.
>
> As far as I can tell, no one is using this code - we're not even using it in
> the
> gate - as it was broken until recently,
Hi,
What expectations should driver authors have about multiple instances
of the driver being instantiated within different instances of
manila-share?
For example, should I assume that when one instance of a driver is
having ensure_share called during startup, another instance of the
driver might
Le 03/03/2016 13:05, Flavio Percoco a écrit :
Thanks for all your hard work as an Oslo PTL. You did amazing and I
think you'd
do an awesome mentor for other folks as well. It was an honor to have
you as a
PTL and I look forward to keep working with you as an Oslo contributor.
I concur with Flav
Hey Folks,
I'm looking at doing some cleanups in our repo and I would like to start by
deprecating the `run_tests` script and the contents in the `tools/` dir.
As far as I can tell, no one is using this code - we're not even using it in the
gate - as it was broken until recently, I believe. The
Le 04/03/2016 12:24, Ihar Hrachyshka a écrit :
Tony Breeds wrote:
On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote:
If you are interested to be a liaison and help translators,
input your information here:
https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n .
So https:/
On 04/03/16 09:14 +, Jethani, Ravishekar wrote:
Hi Glance 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 FFE for this blueprint so that it can be included in Mitaka.
For the cl
Tony Breeds wrote:
On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote:
If you are interested to be a liaison and help translators,
input your information here:
https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n .
So https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n
Igor,
It seems you are proposing an IKEA approach to plugins. Take Fuel's
example plugin, add in the current Fuel release, and then build it. We
maintained these plugins in the past, but now it should a manual step
to test it out on the current release.
What would be a more ideal situation that m
Hi,
The actual BP that links to the approved spec is here: [1] and 2
outstanding patches are [2][3].
Apart from the usual empathy-inspired reasons to allow this (code's been
up for a while, yet only had real review on the last day etc.) which are
not related to the technical merit of the work, th
Dmitry, Aleksandra,
thank you for help and support!
Regards,
Igor Marnat
On Fri, Mar 4, 2016 at 1:20 AM, Aleksandra Fedorova
wrote:
> As we agreed, we have switched ISO builds to latest CentOS 7.2 snapshots.
>
> You can see now that each ISO build (see for ex. [1]) produces several
> *_id.txt a
No, this is a wrong road to go.
What if in Fuel 10 we drop v1 plugins support? What should we do?
Remove v1 example from source tree? That doesn't seem good to me.
Example plugins are only examples. The list of supported releases must
be maintained on system test side, and system tests must injec
Ronald Bradford wrote on 03/02/2016 07:40:42 PM:
> From: Ronald Bradford
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 03/02/2016 07:41 PM
> Subject: [openstack-dev] [oslo][all] Documenting configuration options
lifespan
>
> After evaluation of oslo-config-ge
Vitaly,
As we decided yesterday custom job with fuel-ui and fuel-web refspec
parameters could help here. Is it not enough for our case? In general, the
case when two PRs depends on each other was deliberately denied to be
handled automatically. Please read this thread [1] for details.
[1]
http://
On 03/03, Ryan McNair wrote:
> Hey all,
>
> Nested quotas has officially started fighting back - while writing Tempest
> tests for the nested quota support [1], I hit a race-condition related to
> the nested quota -1 support that has me stumped. I opened a bug for it [2]
> with more details, but b
Hello,
I am currently looking into https://bugs.launchpad.net/heat/+bug/1442121 and
not quite sure how to tackle it, since the problematic code is used for lots of
things[0]: the root cause of the problem are API clients in resource plugins
that do not anticipate a resource with an entry in Heat'
On Thu, Mar 03 2016, Davanum Srinivas wrote:
Hey Dims,
Thanks for the job you've done since the beginning. You rock.
Hope we'll continue to see you around anyway. :)
Best,
> It has been great working with you all as PTL for Oslo. Looks like the
> nominations open up next week for elections and
Hi Glance 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 FFE for this blueprint so that it can be included in Mitaka.
Kindly consider the request.
Thank you.
[1]
https://blueprints
On 02.03.2016 16:27, Matthew Mosesohn wrote:
> Hi all,
>
> I would like to request a feature freeze exception for "Deploy with
> UCA packages" feature.
>
> I anticipate 2 more days to get tests green and add some depth to the
> existing test.
I vote to support this as that benefits community and
Hi Glance 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 FFE for this blueprint so that it can be included in Mitaka.
Kindly consider the request.
Thank you.
--
Best Regards,
Ravi
On 03/04/2016 01:00 PM, Doug Hellmann wrote:
> We have a handful of requirements changes for community releases
> that we need to land this week before fully freezing the repo. We're
> starting to see merge conflicts, so I've combined them all into one
> commit to make it easier to land the changes
Both of you, thanks for your insights. Greatly appreciated.
Le 04/03/2016 09:25, Cheng, Yingxin a écrit :
Hi,
First of all, many delayed thanks to Jay Pipes's benchmarking framework, learnt
a lot from it : )
Other comments inline.
On Friday, March 4, 2016 8:42 AM Jay Pipes wrote:
Hi again,
Hi,
First of all, many delayed thanks to Jay Pipes's benchmarking framework, learnt
a lot from it : )
Other comments inline.
On Friday, March 4, 2016 8:42 AM Jay Pipes wrote:
> Hi again, Yingxin, sorry for the delayed response... been traveling.
> Comments inline :)
>
> On 03/01/2016 12:34 AM,
> I'm looking forward to it :)
> Thanks
> ==
> I'd like to thank all the people who are working on this and making
> this possible. A special thanks goes to Ed Leafe, Esra Celik and
> Stephen Finucane. They put a tremendous amount of work in it.
Markus, it was a pleasure for me to work with y
101 - 125 of 125 matches
Mail list logo
