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
> -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,
> -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---
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
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
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
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
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
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
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
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
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
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
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
-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
>
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.
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
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!
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,
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
>
张晨 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
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
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
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 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
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
>>
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
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
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/
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
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
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
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
> 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,
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
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
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
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
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
We are tickled pink to announce the release of:
glance_store 0.13.1: OpenStack Image Service Store Library
This release is part of the mitaka stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/glance_store
With package available at:
https://pypi.p
We are content to announce the release of:
doc8 0.7.0: Style checker for Sphinx (or other) RST documentation
For more details, please see below.
Changes in doc8 0.6.0..0.7.0
a96c31f Skip long line check for rst definition list term
f6cb930 Remove argparse from requi
On Thu, Apr 07, 2016 at 06:36:20AM -0400, Sean Dague wrote:
> On 04/07/2016 03:26 AM, Juvonen, Tomi (Nokia - FI/Espoo) wrote:
> > Hi Nova, Ops, stackers,
> >
> > I am trying to figure out different use cases and requirements there
> > would be for host maintenance and would like to get feedback a
On Tue, Apr 5, 2016, at 09:57 AM, Ryan McNair wrote:
> >It is believed that reservation help to to reserve a set of resources
> >beforehand and hence eventually preventing any other upcoming request
> >(serial or parallel) to exceed quota if because of original request the
> >project might have r
We are satisfied to announce the release of:
pbr 1.9.0: Python Build Reasonableness
With source available at:
http://git.openstack.org/cgit/openstack-dev/pbr
Please report issues through launchpad:
http://bugs.launchpad.net/pbr
For more details, please see below.
Changes in pbr 1.8.1
On 2016-04-12 08:31, Andreas Jaeger wrote:
> On 2016-04-12 03:33, Nikhil Komawar wrote:
>> To close this:
>>
>> This has been fixed as a part of the earlier opened bug
>> https://bugs.launchpad.net/glance-store/+bug/1568767 and other is
>> duplicated.
>>
>
> Yes, it's fixed now.
And you have rele
Hey Cinder team (and those interested),
We've had a few informal conversations on the channel and in meetings,
but wanted to capture some things here and spread awareness.
I think it would be good to start planning for our Newton midcycle.
These have been incredibly productive in the past (at lea
Armando,
Is there any way we can move the "Neutron: Development track: future
of *-aas projects" session? I overlaps with the LBaaS talk:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/6893?goback=1
Michael
On Mon, Apr 11, 2016 at 9:56 PM, Armando M. wrote:
> Hi folks,
>
On Thu, Apr 07, 2016 at 02:42:09AM +, Jeremy Stanley wrote:
> On 2016-04-06 18:33:06 +0300 (+0300), Igor Belikov wrote:
> [...]
> > I suppose there are security issues when we talk about running
> > custom code on bare metal slaves, but I'm not sure I understand
> > the difference from running
This discussion needs to be happening on openstack-dev too, so
cc'ing that list in as well. The top of the thread is at
http://lists.openstack.org/pipermail/openstack/2016-April/015864.html
On Tue, 12 Apr 2016, Chris Dent wrote:
On Tue, 12 Apr 2016, Nadya Shakhat wrote:
I'd like to discus
On 11/04/16 16:53 +, Adrian Otto wrote:
Amrith,
I respect your point of view, and agree that the idea of a common compute API
is attractive… until you think a bit deeper about what that would mean. We
seriously considered a “global” compute API at the time we were first
contemplating Magnum.
Hi Nikhil,
2016-04-12 5:59 GMT+03:00 Nikhil Komawar :
> Hello,
>
> I was hoping to make some changes to the stackalytics dashboard
> specifically of this type [1] following my requested suggestions here
> [2]; possibly add a few extra columns for +0s and just Bot +1s. I think
> having this info g
On 11/04/16 18:05 +, Amrith Kumar wrote:
Adrian, thx for your detailed mail.
Yes, I was hopeful of a silver bullet and as we’ve discussed before (I think it
was Vancouver), there’s likely no silver bullet in this area. After that
conversation, and some further experimentation, I found that
I'll throw this out there: Fort Collins HPE site is available.
Scott D'Angelo (scottda)
From: Sean McGinnis [sean.mcgin...@gmx.com]
Sent: Tuesday, April 12, 2016 8:05 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Cinder] Newton Midcycle
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Mitaka for RPM-based distributions - CentOS
Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building
private, public, and hybrid clouds and Mitaka is the 13th release from
the OpenStack projec
On 04/11/2016 09:45 PM, 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 Jul
As a note, there will be a design session around the API refactor
efforts going on. Microversioning will be a topic.
On Tue, 2016-04-12 at 14:59 +0200, Ihar Hrachyshka wrote:
> Xianshan wrote:
>
> > Hi, Duncan & michael,
> > Thanks a lot for your replies.
> >
> > Definitely I agree with you tha
And I'll add Raleigh NC NetApp is available too. Nothing better than summer in
the South :)
-Original Message-
From: D'Angelo, Scott [mailto:scott.dang...@hpe.com]
Sent: Tuesday, April 12, 2016 10:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [ope
On 04/12/2016 10:05 AM, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and spread awareness.
>
> I think it would be good to start planning for our Newton midcycle.
Fixes have been proposed for both of these bugs.
Cheers,
--Morgan
On Tue, Apr 12, 2016 at 12:38 AM, Dina Belova wrote:
> 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 inform
Sorry Missed the copy/paste of links:
https://bugs.launchpad.net/keystone/+bug/1567403 [0]
https://bugs.launchpad.net/keystone/+bug/1567413 [1]
[0]
https://review.openstack.org/#/q/I4857cfe1e62d54c3c89a0206ffc895c4cf681ce5,n,z
[1] https://review.openstack.org/#/c/304688/
--Morgan
On Tue, Apr 12
HP facility just outside Dublin (ireland) is available again, depending on
dates
On 12 April 2016 at 17:05, Sean McGinnis wrote:
> Hey Cinder team (and those interested),
>
> We've had a few informal conversations on the channel and in meetings,
> but wanted to capture some things here and sprea
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160412
>
> We'll also have open discussion for bugs & reviews, so anyone is welcome
> to join.
We did our meeting, notes are available here:
http://eavesdrop.openstack.org/meetings/puppet_openstack/2016/puppet_op
Have a look at this script:
https://review.openstack.org/#/c/158003/1/bin/neutron-local-port
Nova does basically the same thing but plugs it into the vm.
Thanks,
Kevin
From: 张晨 [zhangchen9...@126.com]
Sent: Tuesday, April 12, 2016 1:16 AM
To: OpenStack Developmen
Yes, I think it would be good to have a summit session on that. However,
before the session, it would really be helpful if the folks with proposals
got together and/or reviewed each other's proposals, and summarized their
findings. You may find after reviewing the proposals, that eg only 2 are
real
Flavio, and whom'ever else who's available to attend,
We have a summit session for instance users listed here that could be part of
the solution:
https://www.openstack.org/summit/austin-2016/summit-schedule/events/9485
Please attend if you can.
--
+1 for a basic common abstraction.
Thank you Morgan for quick fixes proposed!
On Tue, Apr 12, 2016 at 6:19 PM, Morgan Fainberg
wrote:
> Sorry Missed the copy/paste of links:
>
> https://bugs.launchpad.net/keystone/+bug/1567403 [0]
> https://bugs.launchpad.net/keystone/+bug/1567413 [1]
>
> [0]
> https://review.openstack.org/#/q/I4
On 4/11/2016 5:54 PM, Michael Still wrote:
On Tue, Apr 12, 2016 at 6:49 AM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> 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
I'm definitely guilty of nit picking docs. I'm fine with holding back and
following up with a patch to fix any grammar/misspelling mistakes. +1
-Ryan
- Original Message -
From: "Paul Bourke"
To: openstack-dev@lists.openstack.org
Sent: Tuesday, April 12, 2016 4:49:09 AM
Subject: Re: [
Hello,
It's nova-compute service which is configuring it. This service is running on
compute node: http://docs.openstack.org/developer/nova/architecture.html
--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl
Dnia wtorek, 12 kwietnia 2016 16:16:25 CEST 张晨 pisze:
> Thx for the an
I've stubbed out the newton design summit etherpad wiki so people can
start populating this now.
https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
--
Thanks,
Matt Riedemann
__
OpenStack Development Mailing
On 04/12/2016 12:45 PM, Matt Riedemann wrote:
> I've stubbed out the newton design summit etherpad wiki so people can
> start populating this now.
>
> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
>
Keep in mind we still haven't fully addressed all the consequences of
the wiki sp
Hi,
We are nerdy to present this week's subteam report for Ironic. As usual,
this is pulled directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff with 04.04.2016):
- Ironic: 200 bugs (+4) + 163 wishlist items. 25 new, 136 in progress (+1),
0 critical,
- Original Message -
> From: "Calum Loudon"
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> "openstack-operators"
> Sent: Wednesday, April 6, 2016 6:09:16 AM
> Subject: Re: [openstack-dev] Telco Working Group meeting for Wednesday April
> 6th CANCELLED
>
>
Hi all,
We discussed this in our last team meeting, and we were in disagreement. Some
of us preferred option #1, others preferred option #2. I would suggest to leave
this topic to the design summit so that our team members would have more times
to research each option. If we are in disagreement
> On Apr 12, 2016, at 1:12 PM, Steve Gordon wrote:
>
>
>
> - Original Message -
>> From: "Calum Loudon"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>> ,
>> "openstack-operators"
>> Sent: Wednesday, April 6, 2016 6:09:16 AM
>> Subject: Re: [openstack-dev] T
On 2016-03-31 15:15:23 -0400 (-0400), michael mccune wrote:
[...]
> * what is the process for performing an analysis
>
> * how will an analysis be formally recognized and approved
>
> * who will be doing these analyses
I intentionally didn't specify when writing the
vulnerability:managed tag des
On 04/12/2016 01:05 PM, Anita Kuno wrote:
> On 04/12/2016 12:45 PM, Matt Riedemann wrote:
>> I've stubbed out the newton design summit etherpad wiki so people can
>> start populating this now.
>>
>> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads
>>
> Keep in mind we still haven't fu
On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
> If a team has already done a TA (e.g. as part of an internal
> product TA) (and produced all the documentation) would this meet
> the requirements?
>
> I ask, as Designate looks like it meets nearly all the current
> requirements - the
Hi Folks - I'm looking into the options for Intel to host in Hillsboro Oregon.
Stay tuned for more details.
Thanks
Carol
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, April 12, 2016 9:05 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [o
On 4/12/16, 10:37 AM, "Jeremy Stanley" wrote:
>On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks lik
On 2016-04-02 14:40:57 + (+), Steven Dake (stdake) wrote:
[...]
> IANAL and writing these things correctly is hard to do properly );
> involving the community around the pain points of the tagging
> process is what I'm after.
[...]
Nobody on the VMT is a lawyer either, and when I wrote the
On 12/04/2016 18:37, "Jeremy Stanley" wrote:
>On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks like
On 2016-04-05 00:45:20 -0400 (-0400), Jay Pipes wrote:
> The proposal is to have the hardware companies donate hardware and
> sysadmins to setup and maintain a *single* third-party CI lab
> environment running the *upstream infra CI toolset* in one
> datacenter at first, moving to multiple datacent
On 12/04/2016 18:39, Jeremy Stanley wrote:
> On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote:
>> If a team has already done a TA (e.g. as part of an internal
>> product TA) (and produced all the documentation) would this meet
>> the requirements?
>>
>> I ask, as Designate looks like it me
I'm definitely glad we got puppet-ceph to where it is today and I have
complete trust in the Puppet-OpenStack team to take it to the next
level.
With that announcement, I have to do one of my own -- I am stepping
down as a puppet-ceph core.
My day-to-day work does not involve Ceph anymore and as
On 12 April 2016 at 07:08, Michael Johnson wrote:
> Armando,
>
> Is there any way we can move the "Neutron: Development track: future
> of *-aas projects" session? I overlaps with the LBaaS talk:
>
> https://www.openstack.org/summit/austin-2016/summit-schedule/events/6893?goback=1
>
> Michael
>
Hello,
Separate job for testing live-migration with different storage
configurations(No shared storage/NFS/Ceph was implemented during Mitaka and
available to be executed using experimental pipeline.
The job is ready but shows same stability as
gate-tempest-dsvm-multinode-full.
Bugs like [1] [2]
Flavio Percoco wrote:
On 11/04/16 18:05 +, Amrith Kumar wrote:
Adrian, thx for your detailed mail.
Yes, I was hopeful of a silver bullet and as we’ve discussed before (I
think it
was Vancouver), there’s likely no silver bullet in this area. After that
conversation, and some further experi
On 4/11/2016 11:56 PM, Armando M. wrote:
Hi folks,
A provisional schedulefor the Neutron project is available [1]. I am
still working with the session chairs and going through/ironing out some
details as well as gathering input from [2].
I hope I can get something more final by the end of thi
Greetings,
I'm soliciting inputs, and if interested in this topic, your presence for
the upcoming BoF session on NFV Orchestration during the Austin summit,
https://www.openstack.org/summit/austin-2016/summit-schedule/events/8468
We had a packed session for a similar event in the Tokyo summit wi
On 12 April 2016 at 12:16, Matt Riedemann
wrote:
>
>
> On 4/11/2016 11:56 PM, Armando M. wrote:
>
>> Hi folks,
>>
>> A provisional schedulefor the Neutron project is available [1]. I am
>> still working with the session chairs and going through/ironing out some
>> details as well as gathering inp
On Mon, 2016-04-11 at 05:54 -0400, John Trowbridge wrote:
> Hola OOOers,
>
> It came up in the meeting last week that we could benefit from a CI
> subteam with its own meeting, since CI is taking up a lot of the main
> meeting time.
>
> I like this idea, and think we should do something similar f
On Mon, Apr 11, 2016 at 3:37 AM, Steven Dake (stdake) wrote:
> Hey folks,
>
> The reviewers in Kolla tend to nit-pick the quickstart guide to death during
> reviews. I'd like to keep that high bar in place for the QSG, because it is
> our most important piece of documentation at present. However
On 04/12/2016 03:23 PM, Armando M. wrote:
> On 12 April 2016 at 12:16, Matt Riedemann
> wrote:
>
>>
>>
>> On 4/11/2016 11:56 PM, Armando M. wrote:
>>
>>> Hi folks,
>>>
>>> A provisional schedulefor the Neutron project is available [1]. I am
>>> still working with the session chairs and going thro
On 4/1/2016 8:45 AM, Sean Dague wrote:
The glance v2 work is currently blocked as there is no active spec,
would be great if someone from the glance team could get that rolling again.
I started digging back through the patches in detail to figure out if
there are some infrastructure bits we co
I didn't see that mention. You mean about legacy volumes and snapshots?
On Mon, Apr 11, 2016 at 3:58 PM, Duncan Thomas
wrote:
> Ok, you're right about device naming by UUID.
>
> So we have two advantages compared to the existing system:
>
> - Keeping the same volume id (and therefore disk UUID)
Hi all,
In short, some Magnum team members proposed to store TLS certificates in
Keystone credential store. As Magnum PTL, I want to get agreements (or
non-disagreement) from OpenStack community in general, Keystone community in
particular, before approving the direction.
In details, Magnum le
I think part of the problem is containers are mostly orthogonal to vms/bare
metal. Containers are a package for a single service. Multiple can run on a
single vm/bare metal host. Orchestration like Kubernetes comes in to turn a
pool of vm's/bare metal into a system that can easily run multiple c
On 04/12/2016 03:37 PM, Matt Riedemann wrote:
>
>
> On 4/1/2016 8:45 AM, Sean Dague wrote:
>> The glance v2 work is currently blocked as there is no active spec,
>> would be great if someone from the glance team could get that rolling
>> again.
>>
>> I started digging back through the patches in
On 4/6/2016 6:15 AM, Mikhail Fedosin wrote:
Hello! Thanks for bring this topic up.
First of all, as I mentioned before, the great work was done in Mitaka,
so Glance v2 adoption in Nova it is not a question of "if", and not even
a question of "when" (in Newton), but the question of "how".
Ther
1 - 100 of 139 matches
Mail list logo
