Le 6 févr. 2016 20:39, "Steven Dake (stdake)" a écrit :
>
>
>
> On 2/5/16, 1:14 AM, "Eric LEMOINE" wrote:
>
> >On Thu, Feb 4, 2016 at 5:13 PM, Jeff Peeler wrote:
> >I totally agree with you Jeff.
> >
> >It is to be noted that we (my team at Mirantis) want to avoid
> >duplicating our Lua plugins,
If you compare the number of people that come to mid-cycles with the number
of people that come
to the summit and attend the design summit, i am sure (without knowing
exact numbers) that there is a big difference
in favor of the design summit.
I also think that its important that users/operators m
> This doesn't feel intentional, and is a good catch.
> https://review.openstack.org/#/c/276738/ was pushed this morning to fix it. I
> think that's fine (and can be backported)
> but needs tests.
Sean,
Thank you for your reply.
I will review the patch.
> It would be good to know if there were
Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT)
1) Patches/Reviews -
https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking
2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler
3) Opens
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/4
Hello guys,
S3 compatibility API is now maitained in openstack namespace, it is in the
external repository from original Swift though.
It works as Swift proxy middleware to translate S3 api into pure Swift api.
While the translation, Swift3 makes a credential to retrieve actual auth token
from
On Mon, Feb 8, 2016 at 1:51 AM, Monty Taylor wrote:
[snip]
> Fifth - if we do this, the real need for the mid-cycles we currently have
> probably goes away since the summit week can be a legit wall-to-wall work
> week.
>
[snip]
Another reply to a specific point...
I disagree strongly here, a
On Sun, Feb 7, 2016 at 8:07 PM, Jay Pipes wrote:
[snip]
> Many contributors submit talks to speak at the conference part of an
> OpenStack Summit because their company says it's the only way they will pay
> for them to attend the design summit. This is, IMHO, a terrible thing. The
> design summ
Hey Jay!
I was looking at implementing a few scheduling algorithms of my own
natively into OpenStack, and for that I went through the nova-scheduler.
After going through the scheduler, I felt that it was not very easy to
implement or extend and add new scheduling algorithms to the scheduler. The
o
On Mon, Feb 08, 2016 at 07:04:31AM +0500, Umar Yousaf wrote:
> I just did unstack.sh due to some reason and then afterwards when I run
> stack.sh I am getting following error
> i) Error: Service g-api is not running
> ii) Error: Service g-reg is not running
> iii) Error: Service h-api is not runni
I just did unstack.sh due to some reason and then afterwards when I run
stack.sh I am getting following error
i) Error: Service g-api is not running
ii) Error: Service g-reg is not running
iii) Error: Service h-api is not running
After a lot of struggle I found a resolution that when I reboot my
On 02/07/2016 02:07 PM, Jay Pipes wrote:
Hello all,
tl;dr
=
I have long thought that the OpenStack Summits have become too
commercial and provide little value to the software engineers
contributing to OpenStack.
I propose the following:
1) Separate the design summits from the conferences
On 02/07/2016 12:56 PM, Jim Meyer wrote:
On Feb 7, 2016, at 6:11 AM, Monty Taylor wrote:
Hey all,
We're working on getting per-region APT mirrors stood up for the nodepool nodes
to use in the gate. As part of working on this, it struck me that we currently
have restricted and multiverse enab
On 02/07/2016 07:30 AM, Jay Pipes wrote:
On 02/04/2016 06:38 AM, Sean Dague wrote:
What options do we have?
2) Have a registry of "common" names.
Upside, we can safely use common names everywhere and not fear collision
down the road.
Downside, yet another contention point.
A registry would
Colleagues,
I agree with this proposal: of course it's fun to receive some free
tee-shirts/magnets, but my main interest as a developer is to take part in
design summit.
It will be awesome if contributors working together will also work togeter
on design summits as those increase developers involv
Jay and others,
I’m not able to understand how the decoupled events will produce the desired
outcome. Here’s why. There will still be a limit on expenditure that companies
will be willing to undertake. If you were to decouple the two events, it isn’t
as though companies won’t do the “Conference
On Sun, Feb 7, 2016 at 12:07 PM, Jay Pipes wrote:
> Hello all,
>
> tl;dr
> =
>
> I have long thought that the OpenStack Summits have become too commercial
> and provide little value to the software engineers contributing to
> OpenStack.
>
> I propose the following:
>
> 1) Separate the design
On 02/07/2016 12:07 PM, Jay Pipes wrote:
Hello all,
tl;dr
=
I have long thought that the OpenStack Summits have become too
commercial and provide little value to the software engineers
contributing to OpenStack.
I propose the following:
1) Separate the design summits from the conferences
Hello all,
tl;dr
=
I have long thought that the OpenStack Summits have become too
commercial and provide little value to the software engineers
contributing to OpenStack.
I propose the following:
1) Separate the design summits from the conferences
2) Hold only a single OpenStack confere
On 02/04/2016 11:02 PM, Bhandaru, Malini K wrote:
Another thought, for such ephemeral/changing data, such as progress,
why not save the information in the cache (and flush to database at a
lower rate), and retrieve for display to active listeners/UI from the
cache. Once complete or aborted, of co
Apologies for the delayed responses. Comments inline.
On 01/27/2016 02:29 AM, Dhvanan Shah wrote:
Hey Jay!
Thanks for the clarification. There was another thing that I wanted to
know, is there any provision to pass extra arguments or some extra
specifications along with the VM request to nova.
> On Feb 7, 2016, at 6:11 AM, Monty Taylor wrote:
>
> Hey all,
>
> We're working on getting per-region APT mirrors stood up for the nodepool
> nodes to use in the gate. As part of working on this, it struck me that we
> currently have restricted and multiverse enabled in our sources.list file.
Guys,
Currently, I need to force:
CONSOLE_TYPE=SPICE
Otherwise, if "CONSOLE_TYPE=AUTO", Horizon does not auto-detect SPICE and
points to VNC, even if there is no VNC console configured in Nova.
Is this a bug?
Thanks!
Thiago
__
Hi,
As I am at the Designate mid cycle this week I will not make the IRC
meeting this week.
Can dougwig / johnsom take over, or will we skip this week?
Thanks,
Graham
__
OpenStack Development Mailing List (not for usage q
As most of us are in Galway at the mid cycle this week, we are going to
cancel the meeting this week.
Talk to you all tomorrow / next week.
Thanks
Graham
__
OpenStack Development Mailing List (not for usage questions)
Unsub
Hey all,
We're working on getting per-region APT mirrors stood up for the
nodepool nodes to use in the gate. As part of working on this, it struck
me that we currently have restricted and multiverse enabled in our
sources.list file.
I ran a quick test of removing both of them on a devstack-g
On 02/04/2016 06:38 AM, Sean Dague wrote:
What options do we have?
2) Have a registry of "common" names.
Upside, we can safely use common names everywhere and not fear collision
down the road.
Downside, yet another contention point.
A registry would clearly be under TC administration, thoug
On Fri, Feb 05, 2016 at 05:57:56PM +, Fox, Kevin M wrote:
>Might double check with the heat folks. I think they use some of it with
>wait conditions still?
Yes, we depend on the heat-api-cfn by default for many resources atm, which
requires the keystone ec2tokens API.
I started a thre
Hello all,
Since many members (and also myself) cant make it for tomorrows meeting,
we have decided to cancel it.
For any urgent matters, feel free to send your question to the mailing list.
We will have a meeting next week (2/15) as usual.
Thanks
Gal
___
28 matches
Mail list logo