Hi,
After some discussion, we have decided to change "openstack.node" to
"openstack.cluster" as the "type" of the openstack cluster in the graph, to
conform with the standard openstack terminology.
Alexey
__
OpenStack Deve
I must admit, I really like this idea of getting rid of all the devstack
params. It's always a mess looking up the functionality of the various
variables in the code when trying out something new.
I also understand the concern that was raised by somebody (couldn't find
it anymore) that the Neutron
On Tue, Apr 12, 2016 at 02:02:44AM +0800, Zhenguo Niu wrote:
> Maybe we can continue the discussion here, as there's no enough time in the
> irc meeting :)
Someone mentioned this would make a good summit session, as there's a
few competing proposals that are all good options. I do welcome
discussi
Hi Kevin, thanks for your input! See my comments in line
--
-
Andreas (IRC: scheuran)
On Di, 2016-04-12 at 04:12 -0700, Kevin Benton wrote:
> We can't change the host_id until after the migration or it will break
> l2pop other drivers that use the host as a location indicator (e.g.
> many
Hi,
We have weekly Nova API meeting tomorrow. The meeting is being held
Wednesday UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
> Another possible solution is to apply the same strategy we use for
> instance creation. Nova should wait to get a confirmation from Neutron
> before declaring the migration successful.
But that wouldn't solve the problem I think. The problem is, that the
protbidning happens after migration alr
Hi,
I just want to let the community know that the versioned notification
work we started in Mitaka is planned to be continued in Newton.
The planned goals for Newton:
* Transform the most important notification to the new format [1]
* Help others to use the new framework adding new notification
Xianshan wrote:
Hi, Duncan & michael,
Thanks a lot for your replies.
Definitely I agree with you that the microversion is the best approach to
solve the backwards compat,
and the neutron is also going to adopt it [1]. But it will take a long
time to totally introduce it into neutron I thin
On 12/04/2016 7:47 AM, Safka, JaroslavX wrote:
> *
> And my question is: How is connected the database table meter and the command
> metric-list?
i assume you mean meter-list. it uses a combination of data from meter
table and resource table[1]. this is because it lists all the meters and
On Tue, 12 Apr 2016, gordon chung wrote:
i'd be in favour of dropping the full cases -- never really understood
why we ran all the tests everywhere. ceilometer/aodh are present at the
end of the workflow so i don't think we need to be concerned with any of
the other tests, only the ones explicit
i'd be in favour of dropping the full cases -- never really understood
why we ran all the tests everywhere. ceilometer/aodh are present at the
end of the workflow so i don't think we need to be concerned with any of
the other tests, only the ones explicitly related to ceilometer/aodh.
On 12/04/
Hi, Duncan & michael,
Thanks a lot for your replies.
Definitely I agree with you that the microversion is the best approach to solve
the backwards compat,
and the neutron is also going to adopt it [1]. But it will take a long time to
totally introduce it into neutron I think.
So IMO, we can cont
Hi,
Can we disable 'full' tempest tests for ceilometer?
- gate-tempest-dsvm-ceilometer-mongodb-full
- gate-tempest-dsvm-ceilometer-mysql-full
- gate-tempest-dsvm-ceilometer-mysql-neutron-full
- gate-tempest-dsvm-ceilometer-postgresql-full
- gate-tempest-dsvm-ceilometer-es-ful
On Tue, Apr 12, 2016 at 7:45 AM, Marcus Furlong wrote:
> On 11 April 2016 at 22:15, Emilien Macchi wrote:
>> On Mon, Apr 11, 2016 at 1:57 AM, Marcus Furlong wrote:
>>> On 29 March 2016 at 09:53, Emilien Macchi wrote:
Puppet OpenStack team has the immense pleasure to announce the release
>>
On 12/04/16 13:47, Safka, JaroslavX wrote:
> Hi all,
>
> Second question how I can propagate the metrics to horizon dashboard
> "Resource usage"?
> (I'm able only see cpu metric from started worker image)
Jaroslav,
I would suggest you to look at gnocchi instead of ceilometer for Horizon
integr
Hi all,
I found strange behavior of command 'ceilometer metric-list' , ceilometer
database and horizon.
First the command 'ceilometer metric-list'.
It displays only "Name cpu.cpu" and that is all. But If I look into database of
ceilometer, then I see this:
MariaDB [ceilometer]> select * from met
On 11 April 2016 at 22:15, Emilien Macchi wrote:
> On Mon, Apr 11, 2016 at 1:57 AM, Marcus Furlong wrote:
>> On 29 March 2016 at 09:53, Emilien Macchi wrote:
>>> Puppet OpenStack team has the immense pleasure to announce the release
>>> of 24 Puppet modules.
>
>> Also (related to the above), are
We can't change the host_id until after the migration or it will break
l2pop other drivers that use the host as a location indicator (e.g. many
top of rack drivers do this to determine which switch port should be wired
up).
There is already a patch that went in to inform Neutron of the destination
张晨 wrote:
Thx for the answer, i finally locate the implementation in
nova.network.linux_net.create_ovs_vif_port
but how could nova execute the ovs-vsctl for the compute-node hypervisor
just in the control-node?
Nova still runs nova-compute service on your hypervisor to manage instances
On 04/12/2016 12:05 PM, Andreas Scheuring wrote:
> Hi together,
> I wanted to start discussion about Live Migration problem that currently
> exists in the nova neutron communication.
>
> Basics Live Migration and Nova - Neutron communication
>
Le 11/04/2016 22:49, Matt Riedemann a écrit :
A few people have been asking about planning for the nova midcycle for
newton. Looking at the schedule [1] I'm thinking weeks R-15 or R-11
work the best. R-14 is close to the US July 4th holiday, R-13 is
during the week of the US July 4th holiday,
Thanks everyone. I'm very glad to join the team.
I'm looking forward to meeting all in Austin.
On Tue, Apr 12, 2016 at 12:54 PM, Sam Betts (sambetts)
wrote:
> Congrats Anton!!!
>
> Sam
>
> On 12/04/2016 10:52, "Dmitry Tantsur" wrote:
>
> >On 04/05/2016 12:24 PM, Dmitry Tantsur wrote:
> >> Hi!
On Tue, Apr 12, 2016 at 11:34:48AM +0200, Thierry Carrez wrote:
> No, this cycle (Newton) is not affected. The proposed change would happen
> after the Barcelona summit (5-month Ocata cycle, new event inserted between
> the Barcelona and the North America summit in May). So feel free to plan
> mid
Hi together,
I wanted to start discussion about Live Migration problem that currently exists
in the nova neutron communication.
Basics Live Migration and Nova - Neutron communication
--
On a high level, Nova Live Migration happens in 3 stages.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/04/16 05:12, Tony Breeds wrote:
> On Thu, Apr 07, 2016 at 12:01:31PM +0200, Matthias Runge wrote:
>> Hello,
>>
>> I'm proposing Rob Cresswell to become stable core for Horizon. I
>> thought, in the past all PTL were in stable team, but this
>
Thank you Jay, Dmitry and Sean for your input! On the yesterday's ironic
meeting the consensus
was to leave the removal possibility in older api versions and not to
bikeshed with new microversions.
Vlad
On Mon, Apr 11, 2016 at 5:36 PM, Jay Pipes wrote:
> On 04/11/2016 10:11 AM, Sean Dague wrote
Congrats Anton!!!
Sam
On 12/04/2016 10:52, "Dmitry Tantsur" wrote:
>On 04/05/2016 12:24 PM, 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 t
On 04/05/2016 12:24 PM, 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 tempest).
Members of the current ironic-inspector-team and eve
Tony Breeds wrote:
On Mon, Apr 11, 2016 at 03:49:16PM -0500, Matt Riedemann wrote:
A few people have been asking about planning for the nova midcycle for
newton. Looking at the schedule [1] I'm thinking weeks R-15 or R-11 work the
best. R-14 is close to the US July 4th holiday, R-13 is during th
I've said in the past I'm not a fan of nitpicking docs. That said, I
feel it's important for spelling and grammar to be correct. The
quickstart guide is the first point of contact for many people to the
project, and rightly or wrongly it will give an overall impression of
the quality of the pro
Great news and good job!
On 04/11/2016 11:24 PM, Andrew Woodward wrote:
> It's been a while since we started the puppet-ceph module on stackforge
> as a friend of OpenStack. Since then Ceph's usage in OpenStack has
> increased greatly and we have both the puppet-openstack deployment
> scenarios as
Thx for the answer, i finally locate the implementation in
nova.network.linux_net.create_ovs_vif_port
but how could nova execute the ovs-vsctl for the compute-node hypervisor just
in the control-node?
At 2016-04-12 13:13:48, "Sławek Kapłoński" wrote:
>Hello,
>
>I don't know this ODL an
On Tue, Apr 12, 2016 at 12:01:39PM +1200, Steve Baker wrote:
>On 12/04/16 11:48, Jeremy Stanley wrote:
>
> On 2016-04-12 11:43:06 +1200 (+1200), Steve Baker wrote:
>
> Can I suggest a sub-team for
> os-collect-config/os-refresh-config/os-apply-config? I ask since
> these tools also make u
On 12 Apr 2016 12:19 AM, "Sean Dague" wrote:
>
> On 04/11/2016 10:08 AM, Ed Leafe wrote:
> > On 04/11/2016 08:38 AM, Julien Danjou wrote:
> >
> >> There's a lot of assumption in oslo.log about Nova, such as talking
> >> about "instance" and "context" in a lot of the code by default. There's
> >> e
Greetings guys,
I will have to step down from PTL responsibility. TBH I haven't have time to
work on Packstack lately and I probably won't have in the future because of my
other responsibilities. So from my point of view it is not correct to lead the
project (though I'd like to contribute/d
Matt,
Thanks for sharing the information about your benchmark. Indeed we need to
follow up on this topic (I'll attend the summit). Let's try to collect as
much information as possible prior Austin to have more facts to operate.
I'll try to figure out why local context cache did not work at least o
Hi,
> -Original Message-
> From: EXT Balázs Gibizer [mailto:balazs.gibi...@ericsson.com]
> Sent: Tuesday, April 12, 2016 10:14 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [Nova] RFC Host Maintenance
>
> > -Original Message---
> -Original Message-
> From: Juvonen, Tomi (Nokia - FI/Espoo) [mailto:tomi.juvo...@nokia.com]
> Sent: April 11, 2016 09:06
>
> Hi,
>
> Looking the discussion so far:
> -Suggestion to have extended information for maintenance to somewhere
> outside Nova.
> -Notification about Nova state c
Hi,
Here is the design of the Cinder datasource of Vitrage.
Currently Cinder datasource is handling only Volumes.
This datasource listens to cinder volumes notifications on the oslo bus, and
updates the topology accordingly.
Currently Cinder Volume can be attached only to instance (Cinder design
101 - 139 of 139 matches
Mail list logo
