We've got to figure out what external authentication plugins we're going to
provide in Keystone.
This is something that you'd think wouldn't be complicated, but somehow
it's gotten that way.
Since we've made mistakes in the past, let's try to be careful this time
and come up with what plugins are
I'm easy.
On 20 December 2013 00:47, Randy Tuttle wrote:
> Any of those times suit me.
>
> Sent from my iPhone
>
> On Dec 19, 2013, at 5:12 PM, "Collins, Sean" <
> sean_colli...@cable.comcast.com> wrote:
>
> > Thoughts? I know we have people who are not able to attend at our
> > current time.
>
Xuhan, check the other thread - would 1500UTC suit?
On 19 December 2013 01:09, Xuhan Peng wrote:
> Shixiong and guys,
>
> The sub team meeting is too early for china IBM folks to join although we
> would like to participate the discussion very much. Any chance to rotate
> the time so we can com
Per the discussions this evening, we did identify a reason why you might
need a dhcp namespace for v6 - because networks don't actually have to have
routers. It's clear you need an agent in the router namespace for RAs and
another one in the DHCP namespace for when the network's not connected to a
So a few people had been reporting recently that unstack no longer stops
nova processes, which I only got around to looking at today. It turns
out the new common.service stack from oslo takes SIGHUP and treats it as
a restart. Which isn't wrong, but is new, and is incompatible with
screen (the way
https://review.openstack.org/#/c/51793/ is a good instance of a behavior
I've seen a lot of recently, where someone approves a patch that last
ran CI on it a month ago (the last Jenkins pass on this patch was Nov 19th).
If you come across a patch like that, as a core reviewer, please
"recheck no b
On 19 December 2013 15:15, John Garbutt wrote:
> > Note, I don't see the person who boots the server ever seeing the
> pci-flavor, only understanding the server flavor.
> > [IrenaB] I am not sure that elaborating PCI device request into server
> flavor is the right approach for the PCI pass-thro
Hi,
I'm sorry I could not make it to meeting.
However, I can see clearly see the progress being made from gerrit!
One thing which might be worth mentioning is that some of the new jobs are
already voting.
However, in some cases the logs are either not accessible, and in other
cases the job seem t
On Thu, Dec 19, 2013 at 5:41 PM, Sean Dague wrote:
> https://review.openstack.org/#/c/51793/
Just curious, what about the possibility of automating this? In other
words, run through idle patches any time the gate volume gets below a
certain threshold. If you come across a patch that hasn't been
Another +1 for separate repos. Horizon's core focus should remain on
the integrated projects, but we also need to prepare better for when
incubated projects graduate, so their inclusion is less disruptive.
I also like Gabriel's suggestion of a non-gating CI job to catch any
integration issues betw
On Thu, Dec 19 2013, Sean Dague wrote:
> So please look for recent passes before +Aing anything.
What about making that automatic?
Same question for patchset that stays that for a month, finally got
approved and fails right away because they cannot be merged. It would be
cool to notify the submi
Jim and I have been talking about both of these ideas for months. We aren't
lacking clever solutions to make this better. However they are lacking
implementors. Volunteers welcomed.
Until such time, this is completely solvable problem by people taking and extra
5 seconds before approving a patc
Before starting this post I confess I did not read with the required level
of attention all this thread, so I apologise for any repetition.
I just wanted to point out that floating IPs in neutron are created
asynchronously when using the l3 agent, and I think this is clear to
everybody.
So when th
Hi, Ian:
The use case brought by Comcast team today during the ipv6 sub-team meeting
actually proved the point I made here, instead of against it. If I didn’t
explain it clearly in my previous email, here it is.
I was questioning the design with two namespaces and I believe we can use a
SINGLE
Shixiong,
I know you must have a typo in the 3rd paragraph. I think maybe you mean to
include the ns- interface in that list. So why not have qg- qr- and ns-
interfaces in the same namespace. Am I right?
Rnady
On Thu, Dec 19, 2013 at 8:31 PM, Shixiong Shang <
sparkofwisdom.cl...@gmail.com> wrot
Hi Arnaud,
It's really good to know that your team are proposing the vcenter driver with
OVA+glance datastore backend support. Thanks for sharing the information. OVA
would be a good choice which will benefit users by avoiding only use flat image
limited from current driver.
But in my opin
Reminder: Doc Bug Day is today.
On 13/12/13 08:16, Tom Fifield wrote:
> Reminder: Friday next week - Doc Bug Day.
>
> Current number of doc bugs: 505
>
> On 22/11/13 11:27, Tom Fifield wrote:
>> All,
>>
>> This month, docs reaches 500 bugs, making it the 2nd-largest project by
>> bug count in al
Hi, Randy:
Thanks a bunch for pointing it out! Yup, you are absolutely right. What I
wanted to say is why not put qg-, qr-, and ns- interfaces in the single
namespace.
I typed it on my small keyboard on iPhone. Sorry for the confusion. :(
Shixiong
On Dec 19, 2013, at 8:44 PM, Randy Tuttle
>From my some testing I did a couple of months ago, we decided to move to
XFS to avoid the issue
I was poking around with after my file system inadvertently filled and
> found that in ex3/4 all of the inodes in the file system have to be zeroed
> prior to mkfs completing (unless the kernel is abov
Hi,
We had some internal discussions on role of Domain and VPCs. I would like
to expand and understand community thinking of Keystone domain and VPCs.
Is VPC equivalent to Keystone Domain?
If so, as a public cloud provider - I create a Keystone domain and give it
to an organization which wants
Interesting. So you're suggesting we provision a single namespace (per
network, rather than subnet?) proactively, and use it for both routing and
DHCP. Not unreasonable. Also workable for v4, I think?
--
Ian.
On 20 December 2013 02:31, Shixiong Shang wrote:
> Hi, Ian:
>
> The use case brough
I second Rob and Greg- we need to not allow the instance table to have nulls
for the datastore version ID. I can't imagine that as Trove grows and evolves,
that edge case is something we'll always remember to code and test for, so
let's cauterize things now by no longer allowing it at all.
The
Hi, Devananda,
Thanks for your reply.
I totally agree with your thought, nova-compute could gathering such
information locally. And I think IPMI, using in-band connection, might be more
suitable to be used to collect these sensor data.
At the beginning, I thought it would better to put all IPMI p
Keep in mind that this approach is a direct departure from the IPv4 world.
Note that I'm not wholly against that, however there's something to keep in
mind.
Any kind of stack-agnostic interactions in Neutron will have to become stack
aware or have a translator to tell if they need to interact
Salvatore,
Agreed that a visible job-log should be a requirement, otherwise who knows what
was actually run.
-Shiv
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Thursday, December 19, 2013 4:50 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [opens
15UTC is 23PM in China, not ideal, but I am OK with that :-)
On Fri, Dec 20, 2013 at 8:20 AM, Ian Wells wrote:
> I'm easy.
>
>
> On 20 December 2013 00:47, Randy Tuttle wrote:
>
>> Any of those times suit me.
>>
>> Sent from my iPhone
>>
>> On Dec 19, 2013, at 5:12 PM, "Collins, Sean" <
>> sea
Hi all,
I'm planing to commit a new hypervisor Driver for Huawei-FusionCompute in
Icehouse.
And I've already submitted a bp & wiki to OpenStack.
BP:
https://blueprints.launchpad.net/nova/+spec/driver-for-huawei-fusioncompute
Wiki: https://wiki.openstack.org/wiki/FusionCompute
Now I'm not sure w
Ian, thanks for asking! I replied in the other thread. It works for me!
On Fri, Dec 20, 2013 at 8:23 AM, Ian Wells wrote:
> Xuhan, check the other thread - would 1500UTC suit?
>
>
> On 19 December 2013 01:09, Xuhan Peng wrote:
>
>> Shixiong and guys,
>>
>> The sub team meeting is too early fo
Cheers Gao
It definitely makes sense to collect additional metrics such as power and
temperature, and make that available for selective decisions you would want to
take. However, I am just wondering if you could realistically feed those
metrics as variables for scheduling, this is the main part
Yes, Alan, you got me.
Providing power/temperature to scheduler, set threshold or different weight,
then the scheduler can boot VM on the most suitable node.
Thanks
--fengqian
From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com]
Sent: Friday, December 20, 2013 11:58 AM
To: OpenStack Developm
I'm on holidays till 9th January. And I don't think I'll have an internet
access all the time on holidays.
p.s. By the way, I'll prefer Friday's evenings as new meeting time if it is
available - it only one day when I don't do my BJJ classes. Or we can move
to 1900-2000UTC. it looks fine for me. Or
On Thu, Dec 19, 2013 at 8:22 PM, Nikolay Markov wrote:
>
> I created a bug on launchpad regarding this:
> https://bugs.launchpad.net/swift/+bug/1262166
>
> Could anybody please participate in discussion on how to overcome it?
>
Hello.
I know you've decided to dig a bit deeper on IRC, but I've mad
Hi all,
When we tested windows guest OS, the time drift case was occured.
It meant the clock of windows mv gredually lost a few seconds per minute.
It occured especailly the CPUs are working hard.
For syncing between Hypervisor and windows vm, we need to other option into
libvirt template.
I subm
Excerpts from Sean Dague's message of 2013-12-19 16:33:12 -0800:
> So a few people had been reporting recently that unstack no longer stops
> nova processes, which I only got around to looking at today. It turns
> out the new common.service stack from oslo takes SIGHUP and treats it as
> a restart.
I don't think these patches are conflicting.
I will continue to work on this patch.
https://review.openstack.org/#/c/34903/
Thanks!
Best Regards
---
Hi Arnaud,
It's really good to know th
101 - 135 of 135 matches
Mail list logo
