> On Jan 22, 2014, at 7:09 AM, Jaromir Coufal wrote:
>
> >
> >
> > On 2014/22/01 10:00, Jaromir Coufal wrote:
> >>
> >>
> >> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
> >>> Hiya - Resource is actually a Heat term that corresponds to what we're
> >>> deploying within
> >>> the Overcloud Stack
On Jan 22, 2014, at 7:09 AM, Jaromir Coufal wrote:
>
>
> On 2014/22/01 10:00, Jaromir Coufal wrote:
>>
>>
>> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
>>> Hiya - Resource is actually a Heat term that corresponds to what we're
>>> deploying within
>>> the Overcloud Stack - i.e., if we specif
On Jan 22, 2014, at 9:52 AM, Dougal Matthews wrote:
> On 22/01/14 14:31, Tzu-Mainn Chen wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
>
>
> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
>> Hiya - Resource is actually a Heat term that corresponds to what we're
>> deplo
On Jan 22, 2014, at 4:02 AM, Jaromir Coufal wrote:
>
>
> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
>> Hiya - Resource is actually a Heat term that corresponds to what we're
>> deploying within
>> the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
>> Controller
>> and
It's worth noticing that elastic recheck is signalling bug 1253896 and bug
1224001 but they have actually the same signature.
I found also interesting that neutron is triggering a lot bug 1254890,
which appears to be a hang on /dev/nbdX during key injection; so far I have
no explanation for that.
Le 22/01/2014 15:57, Mike Spreitzer a écrit :
Is that enough? Remember that some of us are concerned with business
workloads, rather than HPC jobs. While it might be acceptable in a
business workload to plan on regularly recycling every individual
instance, it is definitely not acceptable t
On 01/22/2014 09:38 AM, Sean Dague wrote:
> Things aren't great, but they are actually better than yesterday.
>
> Vital Stats:
> Gate queue length: 107
> Check queue length: 107
> Head of gate entered: 45hrs ago
> Changes merged in last 24hrs: 58
>
> The 58 changes merged is actually a go
Jay Pipes wrote on 01/21/2014 08:50:36 PM:
...
> On Tue, 2014-01-21 at 14:28 +, Day, Phil wrote:
> > > >
> > > > I think there is clear water between this and the existing
> aggregate based
> > > isolation. I also think this is a different use case from
> reservations. It's
> > > *mostly*
> From: Sylvain Bauza
>
> Le 22/01/2014 02:50, Jay Pipes a écrit :
> >
> > Yup, agreed. It's difficult to guess what the capacity implications
> > would be without having solid numbers on customer demands for this
> > functionality, including hard data on how long such instances would
> > typical
On 22/01/14 14:31, Tzu-Mainn Chen wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1 Con
Things aren't great, but they are actually better than yesterday.
Vital Stats:
Gate queue length: 107
Check queue length: 107
Head of gate entered: 45hrs ago
Changes merged in last 24hrs: 58
The 58 changes merged is actually a good number, not a great number, but
best we've seen in a numb
> > On 2014/22/01 10:00, Jaromir Coufal wrote:
> > >
> > >
> > > On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
> > >> Hiya - Resource is actually a Heat term that corresponds to what we're
> > >> deploying within
> > >> the Overcloud Stack - i.e., if we specify that we want an Overcloud
> > >> with 1
On 22/01/14 07:32 -0500, Sean Dague wrote:
On 01/22/2014 05:19 AM, Julien Danjou wrote:
On Tue, Jan 21 2014, Joe Gordon wrote:
I would like to propose having a integration test job in Oslo incubator
that syncs in the code, similar to how we do global requirements.
I don't think that would be
- Original Message -
>
>
> On 2014/22/01 10:00, Jaromir Coufal wrote:
> >
> >
> > On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
> >> Hiya - Resource is actually a Heat term that corresponds to what we're
> >> deploying within
> >> the Overcloud Stack - i.e., if we specify that we want an O
That's a fair question; I'd argue that it *should* be resources. When we
update an overcloud deployment, it'll create additional resources.
Mainn
- Original Message -
>
>
> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
> > Hiya - Resource is actually a Heat term that corresponds to what w
Thanks for your input, Carl. You're right, it seems the more appropriate
place for this is _validate_subnet(). It checks ip version, gateway,
etc... but not the size of the subnet.
Carl Baldwin wrote on 01/21/2014 09:22:55 PM:
> From: Carl Baldwin
> To: OpenStack Development Mailing List
,
Sounds great! Let's do it on Thursday.
--Robert
On 1/22/14 12:46 AM, "Irena Berezovsky"
mailto:ire...@mellanox.com>> wrote:
Hi Robert, all,
I would suggest not to delay the SR-IOV discussion to the next week.
Let’s try to cover the SRIOV side and especially the nova-neutron interaction
points
On 01/22/2014 05:19 AM, Julien Danjou wrote:
> On Tue, Jan 21 2014, Joe Gordon wrote:
>
>> I would like to propose having a integration test job in Oslo incubator
>> that syncs in the code, similar to how we do global requirements.
>
> I don't think that would be possible as a voting job, since t
On 01/22/2014 06:23 AM, Pavlo Shchelokovskyy wrote:
> Hi all,
>
> we have an approved blueprint that concerns reducing number of ignored
> PEP8 and openstack/hacking style checks for heat
> (https://blueprints.launchpad.net/heat/+spec/reduce-flake8-ignored-rules).
> I've been already warned that e
On Wed, Jan 22, 2014 at 01:23:05PM +0200, Pavlo Shchelokovskyy wrote:
> Hi all,
>
> we have an approved blueprint that concerns reducing number of ignored PEP8
> and openstack/hacking style checks for heat (
> https://blueprints.launchpad.net/heat/+spec/reduce-flake8-ignored-rules).
> I've been al
Hello, Jaromir
On Wed, Jan 22, 2014 at 4:09 PM, Jaromir Coufal wrote:
>
> I am leaning towards Role. We can be more specific with adding some extra
> word, e.g.:
> * Node Role
>
We use this term a lot internally for the very similar purpose, so it looks
reasonable to me.
Just my 2c.
--
Best re
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1 Controller
and 3 Compute, Heat will create
On 21 January 2014 22:46, Veiga, Anthony wrote:
>
>Hi, Sean and Xuhan:
>
> I totally agree. This is not the ultimate solution with the assumption
> that we had to use “enable_dhcp”.
>
> We haven’t decided the name of another parameter, however, we are open
> to any suggestions. As we mention
On 22 January 2014 12:01, Robert Collins wrote:
> > Getting the MTU *right* on all hosts seems to be key to keeping your hair
> > attached to your head for a little longer. Hence the DHCP suggestion to
> set
> > it to the right value.
>
> I certainly think having the MTU set to the right value i
On 01/22/2014 03:27 AM, Robert Collins wrote:
> On 22 January 2014 10:50, Kashyap Chamarthy wrote:
>> [CC'ed libguestfs author, Rich Jones]
>>
>> Heya,
>>
>>
>> On 01/21/2014 07:59 AM, Robert Collins wrote:
>>> I was reminded of this while I cleaned up failed file injection nbd
>>> devices on ci-o
On 22/01/14 11:40 +0100, Chmouel Boudjnah wrote:
On Wed, Jan 22, 2014 at 11:17 AM, Julien Danjou wrote:
On Tue, Jan 21 2014, ZhiQiang Fan wrote:
> six 1.5.2 has been released on 2014-01-06, it provides urllib/urlparse
> compatibility. Is there any plan to upgrade six to 1.5.2? (since
Current EDP config-hints are not only plugin specific. Several types of jobs
must have certain key/values and without it job will fail. For instance,
MapReduce (former Jar) job type requires Mapper/Reducer classes parameters
to be set[1]. Moreover, for such kind of jobs we already have separated
Hi all,
we have an approved blueprint that concerns reducing number of ignored PEP8
and openstack/hacking style checks for heat (
https://blueprints.launchpad.net/heat/+spec/reduce-flake8-ignored-rules).
I've been already warned that enabling some of these rules will be quite
controversial, and pe
Hello Team:
As some of you are aware, I've been working on a couple of reviews to add
Trove testing support to devstack-gate (viz.
https://review.openstack.org/#/c/65040/, and
https://review.openstack.org/#/c/65065/). Hopefully these will be merged
soon.
The next part of the integration plan is t
On 22 January 2014 21:28, Ian Wells wrote:
> On 22 January 2014 00:00, Robert Collins wrote:
>>
>> I think dropping frames that can't be forwarded is entirely sane - at
>>
>> a guess it's what a physical ethernet switch would do if you try to
>> send a 1600 byte frame (on a non-jumbo-frame switch
On Wed, Jan 22, 2014 at 11:17 AM, Julien Danjou wrote:
> On Tue, Jan 21 2014, ZhiQiang Fan wrote:
>
> > six 1.5.2 has been released on 2014-01-06, it provides urllib/urlparse
> > compatibility. Is there any plan to upgrade six to 1.5.2? (since it is
> > fresh new, may need some time to test)
> >
Le 22/01/2014 01:37, Dugger, Donald D a écrit :
Sylvain-
Tnx, that worked great.
(Now if I can just find a way to get the affinity tests working, all
the other tests pass. I only have 17 tests failing out of 254.)
I'm pretty busy these days with Climate 0.1 to deliver, but if I find
so
Le 22/01/2014 02:50, Jay Pipes a écrit :
Yup, agreed. It's difficult to guess what the capacity implications
would be without having solid numbers on customer demands for this
functionality, including hard data on how long such instances would
typically live (see my previous point about re-using
On Tue, Jan 21 2014, Joe Gordon wrote:
> I would like to propose having a integration test job in Oslo incubator
> that syncs in the code, similar to how we do global requirements.
I don't think that would be possible as a voting job, since the point of
oslo-incubator is to be able to break the A
On Tue, Jan 21 2014, ZhiQiang Fan wrote:
> six 1.5.2 has been released on 2014-01-06, it provides urllib/urlparse
> compatibility. Is there any plan to upgrade six to 1.5.2? (since it is
> fresh new, may need some time to test)
>
> six 1.4.1 is lack of urllib/urlparse support, so oslo-incubator/py
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
Controller
and 3 Compute, Heat will create a Stack that contains 1 Controller and 3 Com
Hi All,
I have two questions ...
1) Glance v1 APIs can take a --location argument when creating an image
but v2 APIs can't - bug or feature? (Details below)
2) How should glanceclient (v2 commands) handle reserved attributes?
a) status quo: (Apparently) let the user se
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
Controller
and 3 Compute, Heat will create a Stack that contains 1 Controller and 3 Com
On 22 January 2014 00:00, Robert Collins wrote:
> I think dropping frames that can't be forwarded is entirely sane - at
>
a guess it's what a physical ethernet switch would do if you try to
> send a 1600 byte frame (on a non-jumbo-frame switched network) - but
> perhaps there is an actual standar
Hi Dong,
Can you elaborate an example of what you get, and what you were expecting
exactly?.
I have a similar problem within one operator, where they assign you sparse
blocks
of IP addresses (floating IPs), directly routed to your machine, and they also
assign the virtual mac add
On 21/01/14 13:14 -0500, Joe Gordon wrote:
On Jan 17, 2014 12:24 AM, "Flavio Percoco" wrote:
On 16/01/14 17:32 -0500, Doug Hellmann wrote:
On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec wrote:
On 2014-01-16 13:48, John Griffith wrote:
Hey Everyone,
A review came up today th
101 - 141 of 141 matches
Mail list logo
