As the discussion in https://review.openstack.org/179569 still
continues about whether this is "just" a bug fix, or an API change
that will need a new micro version, maybe it makes sense to take this
issue over here to the ML.
My personal opinion is undecided, I can see either option as being
vali
My vote doesn't count but as an operator i'd give Assaf +100 for all the
great knowledge he has and shared through his blog - incredible source of
information for everyone who wants to understand in a dummy way how Neutron
does things.
Dani
On Fri, May 29, 2015 at 4:13 AM, Akihiro Motoki wrote:
On Mon, May 25, 2015 at 11:37 PM, Chris Friesen
wrote:
>
>
> Also, I think that if nova can't schedule "max count" instances, but can
> schedule at least "min count" instances, then it shouldn't put the
> unscheduled ones into an error state--it should just delete them.
>
> Thoughts?
>
Frankly sp
I want to mention that there is another mesos framework named as chronos:
https://github.com/mesos/chronos , it is used for job orchestration.
For others, please refer to my comments in line.
2015-05-29 7:45 GMT+08:00 Adrian Otto :
> I’m moving this whiteboard to the ML so we can have some disc
On 05/28/2015 09:25 PM, Jay Pipes wrote:
On 05/26/2015 03:13 AM, Daniel P. Berrange wrote:
On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote:
Hi,
When someone calls nova volume-attach or the block-device-mapping parameter
at boot, it is possible to specify a device name for the guest.
Great Work!
"New meetings or meeting changes would be proposed in Gerrit, and
check/gate tests would make sure that there aren't any conflict."
--Will this tell upfront, that in any given day of week, which are all
meeting slots (time and irc meeting channels) are available? this could
bring dow
On 05/28/2015 11:25 PM, Jay Pipes wrote:
> On 05/26/2015 03:13 AM, Daniel P. Berrange wrote:
>> On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote:
>>> Hi,
>>>
>>> When someone calls nova volume-attach or the block-device-mapping
>>> parameter
>>> at boot, it is possible to specify a device
Hi Vivek,
Per our discussion about the migration of an in-use volume, I have done
the following tests:
I took KVM as the hypervisor and LVM as the backend for cinder.
Configure two c-vol nodes.
Create the image in glance.
Create a volume from this image.
Boot a VM from this volume, so the volume
At the summit we found time to squeeze in a revamp of the way we
manage requirements.txt, global-requirements and the versions of
packages we use in the CI system.
https://review.openstack.org/186635 is a cross projects spec, and
hopefully comprehensable :) There's a bunch of work being done
upstr
On 05/26/2015 03:13 AM, Daniel P. Berrange wrote:
On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote:
Hi,
When someone calls nova volume-attach or the block-device-mapping parameter
at boot, it is possible to specify a device name for the guest. However I
couldn't find any guest OS whic
+1
2015-05-28 22:42 GMT+09:00 Kyle Mestery :
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently become my testing Lieutenant. His influence and knowledge in
> testing will be cri
Hi Thai,
Thanks for writing that up! As I can tell the blueprint only has the
"whiteboard" which is kinda yuck, so here's my comments:
I'm already on the record for preferring markup approach 3 so we can avoid
having to write our own implementation of a translation engine. I really,
really don't
On 29/05/15 06:41, Haïkel wrote:
> Here's the main script to rebuild a RPM package.
> https://github.com/openstack-packages/delorean/blob/master/scripts/build_rpm.sh
>
> The script basically uses rpmbuild to build packages, we could have a
> build_deb.sh that uses
> sbuild and add dockerfiles for
Hi Sean,
> We have a *lot* of configuration knobs in DevStack for Neutron. I am not
> a smart man, so I think we may need to wrap our arms around this and
> simplify.
I agree with you. I want to fix the confused configure too.
PHYSICAL_NETWORK is a option in order to setup L2 public network only
Hi folks, Just drafted a blueprint on this topic so that we can all be on the same page. Its quite long, but hopefully you will take some time to read through it and provide some meaningful feedback. In the mean time, I will do some more investigation and keep you all posted. If you have questions
On 5/28/15, 18:01, "Kevin Carter" wrote:
>Hello,
>
>I would like to nominate Serge (svg on IRC) for the
>os-ansible-deployment-core team. Serge has been involved with the greater
>Ansible community for some time and has been working with the OSAD
>project for the last couple of months. He has bee
Kunal and I discussed and we think following time suggested by Doug should
work for most of us.
So lets plan to meet on Tuesday at 1600UTC (9am PST). We will use the
lbaas meeting slot in #openstack-meeting-4.
Thanks,
Vivek
On 5/28/15, 12:37 PM, "Doug Wiegley" wrote:
>
>> On May 28, 2015, at 12
This thread is awesome :) I love the conversation we've kicked off,
and it's touching on all the considerations we had in mind when we put
this together to begin with.
Regarding vision: I agree with a lot of what Monty, Kevin (and others)
have said. For me, what I want to see is the pace to go f
German,
Thanks for the initiative. From a Rackspace perspective, we would love to
participate and provide inputs on the use cases. As discussed during the
meeting at the summit (and as you alluded to in your email), it's about user
experience and clear separation of use cases between FWaaS and
First of all a reminder to everybody doing code reviews:
Avoid sarcasm and jokes
Those travel poorly across TCP/IP and don't translate well in different
languages. Just don't use them.
If you get a negative vote or comments you don't like/understand ask for
more explanations. Offer a place and
Nicola, i would add some words to Alexandre repsonse.
We (standalone ec2api project guys) have filed some bugs (the main is [1]),
but we don't know how to fix them since the way Nova's device names are
moved on is unclear for us. Neither BP, nor wiki you've mentioned above
don't explain what was h
I’m moving this whiteboard to the ML so we can have some discussion to refine
it, and then go back and update the whiteboard.
Source: https://blueprints.launchpad.net/magnum/+spec/mesos-bay-type
My comments in-line below.
Begin forwarded message:
From: hongbin mailto:hongbin...@huawei.com>>
Su
+1
From: Kevin Carter
Sent: Thursday, May 28, 2015 5:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Nominating Serge van Ginderachter to the
os-ansible-deployment core team
Hello,
I would like to nominate
Hello,
I would like to nominate Serge (svg on IRC) for the os-ansible-deployment-core
team. Serge has been involved with the greater Ansible community for some time
and has been working with the OSAD project for the last couple of months. He
has been an active contributor in the #openstack-ansi
All,
I’d like to thank everyone that came to the Vancouver Summit and our Official
Ops Meeting[1].
Since then we have officially been sanctioned[2] and made amazing progress with
true integration testing our cookbooks[3][4], including leveraging Rally[5] for
benchmarking.
Turns out after th
On Thu, May 28, 2015 at 01:18:01PM +0100, Daniel P. Berrange wrote:
> There are a huge number of openstack meetings now, but I think that
> each individual person will only be interested in a handful of them.
> Adding the irc-meetings.ical to a calendar app really pollutes your
> personal schedul
You could pass the cache through with a volume
As for what docker buys you, it would allow a vm (or my desktop) running centos
(as an example) to build packages for multiple distro's using the distro's own
native tools. I see that as a plus.
Thanks,
Kevin
___
+1
On Thu, May 28, 2015 at 6:42 AM, Kyle Mestery wrote:
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently become my testing Lieutenant. His influence and knowledge in
> testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/05/15 07:07, Steve Baker wrote:
> On 29/05/15 04:10, D'ANDREA, JOE (JOE) wrote:
>> [This was originally posted to openst...@lists.openstack.org by
>> accident. Reposting it to openstack-dev.]
>>
>> Calling all Heat neophytes, aficionados, and eve
We didn’t have an etherpad for the discussion at the summit, so I’ve posted the
pictures I took with transcriptions on my blog at
http://doughellmann.com/2015/05/28/openstack-requirements-handling.html
I didn’t really make any attempt to add detail to the transcription, since
Robert will be pos
Team,
i've published 0.13.1 of oslo.vmware with the revert from Gary and so
far the Nova jobs are good.
-- dims
On Thu, May 28, 2015 at 4:41 AM, Gary Kotton wrote:
> Hi,
> We have reverted the problematic patch (I suggest that you all add the word
> balagan to your lexicons).
> Anyways, the pla
On 05/28/2015 04:46 PM, Jeremy Stanley wrote:
> On 2015-05-28 13:30:44 -0700 (-0700), Clint Byrum wrote:
> [...]
>> Do we already have this hidden somewhere, or would it make sense to
>> maybe add this as something in openstack-infra/project-config along side
>> the jjb definition that creates the
Hi,
Sorry I missed the email…
Default template with ACL mechanism will definitely covers my use case.
Admin-only writable template is exactly what I am looking for. However, I saw
the blueprint and it is “Not started”. There is there anything I can help
implementing the ACL?
Right now I am us
Works for me too
From: Hayes, Graham
Sent: Thursday, May 28, 2015 2:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend
support
That works for me.
Is that
On 05/28/2015 09:58 PM, Paul Belanger wrote:
> Not sure I'm a fan of rdorpm, seems too specific to RDO and would not
> foster other people using the git repo for packaging. Personally, I
> simple say rpm- prefix, allowing for branches to be used for distro
> specific changes.
I full agree with tha
On 05/28/2015 02:53 PM, Derek Higgins wrote:
>
>
> On 28/05/15 12:07, Jaume Devesa wrote:
>> Hi Thomas,
>>
>> Delorean is a tool to build rpm packages from master branches (maybe any
>> branch?) of OpenStack projects.
>>
>> Check out here:
>> https://www.rdoproject.org/packaging/rdo-packaging.htm
On 29/05/15 04:10, D'ANDREA, JOE (JOE) wrote:
[This was originally posted to openst...@lists.openstack.org by accident.
Reposting it to openstack-dev.]
Calling all Heat neophytes, aficionados, and everyone in between ...
I've often thought it would be helpful to add a Heat Template Cookbook to
On 05/28/2015 04:32 PM, Haïkel wrote:
2015-05-28 21:58 GMT+02:00 Paul Belanger :
Personally, I'm a fan of mock. Is there plan to add support for it? Also,
currently containers are not being used in -infra. Not saying it is a show
stopper, but could see some initial planning that is required fo
On 2015-05-28 13:30:44 -0700 (-0700), Clint Byrum wrote:
[...]
> Do we already have this hidden somewhere, or would it make sense to
> maybe add this as something in openstack-infra/project-config along side
> the jjb definition that creates the job/class of job somehow?
[...]
We don't (yet anyway
2015-05-28 10:40 GMT+02:00 Thomas Goirand :
>
> I don't know delorean at all, but what should be kept in mind is that,
> for Debian and Ubuntu, we *must* use sbuild, which is what is used on
> the buildd networks.
>
> I also started working on openstack-pkg-tools to provide such sbuild
> based buil
On Thursday, May 28, 2015, Devananda van der Veen
wrote:
> Hi all,
>
> tl;dr;
>
> At the summit, the Ironic team discussed the challenges we've had with
> the current release model and came up with some ideas to address them.
> I had a brief follow-up conversation with Doug and Thierry, but I'd
>
Hi Sean,
I understand and share you point of view. The best and cleaner solution
would be to have the vxlan support out of the box. Unfortunatly it is not
the case for 6.0 and I doubt this feature can be available before HCF for
6.1 (planned in the next upcoming days).
That's why in my initial m
2015-05-28 21:58 GMT+02:00 Paul Belanger :
>
> Personally, I'm a fan of mock. Is there plan to add support for it? Also,
> currently containers are not being used in -infra. Not saying it is a show
> stopper, but could see some initial planning that is required for it.
>
>
Nothing prevents us to
Hi! While discussing the proposed oslo.messaging driver policy[1] at the
summit, we had a question about where we should document who the
appropriate respondents are for any particular gate job.
Do we already have this hidden somewhere, or would it make sense to
maybe add this as something in open
2015-05-27 23:26 GMT+02:00 Derek Higgins :
> On 27/05/15 09:14, Thomas Goirand wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi all,
>>
>> tl;dr:
>> - - We'd like to push distribution packaging of OpenStack on upstream
>> gerrit with reviews.
>> - - The intention is to bette
Hello!
It's that time - hopefully everyone has recovered from the summit by
now and is getting back in the swing of things.
I'd like to take a little of everyone's time to summarize the main
points we covered while in Vancouver (and record them here for folks
who didn't make it, were in other ses
On Thu, May 28, 2015 at 9:41 AM, Devananda van der Veen <
devananda@gmail.com> wrote:
> Hi all,
>
> tl;dr;
>
> At the summit, the Ironic team discussed the challenges we've had with
> the current release model and came up with some ideas to address them.
> I had a brief follow-up conversation
On 05/27/2015 05:26 PM, Derek Higgins wrote:
On 27/05/15 09:14, Thomas Goirand wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
tl;dr:
- - We'd like to push distribution packaging of OpenStack on upstream
gerrit with reviews.
- - The intention is to better share the workload, and
On Thu, May 28, 2015 at 12:54:58PM -0400, Monty Taylor wrote:
> On 05/28/2015 12:41 PM, Devananda van der Veen wrote:
> > Hi all,
> >
> > tl;dr;
> >
> > At the summit, the Ironic team discussed the challenges we've had with
> > the current release model and came up with some ideas to address them
That works for me.
Is that OK for everyone else?
- Sent from my phone
On 28 May 2015 8:39 pm, Doug Wiegley wrote:
> On May 28, 2015, at 12:47 PM, Hayes, Graham wrote:
>
> On 28/05/15 19:38, Adam Harwell wrote:
>> I haven’t seen any responses from my team yet, but I know we’d be
>> interested
Excerpts from Zane Bitter's message of 2015-05-28 11:24:33 -0700:
> On 28/05/15 03:35, Jan Provaznik wrote:
> > On 05/28/2015 01:10 AM, Steve Baker wrote:
> >> On 28/05/15 10:54, Richard Raseley wrote:
> >>> Zane Bitter wrote:
> Steve is working on a patch to allow package-based updates of ove
+1
On May 28, 2015 8:44 AM, "Doug Wiegley"
wrote:
> +1
>
> Doug
>
>
> On May 28, 2015, at 7:42 AM, Kyle Mestery wrote:
>
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently becom
Hi Ben,
Those approaches are still the ones in place, and they are implemented in
the prototype. Just to recap:
Approach #1: Driver migration, optimized from same vendor, like netapp =>
netapp. Driver should implement, does not require an additional DB row.
Approach #2: Generic Migration, when d
On May 28, 2015 2:51:56 PM EDT, Andrey Danin wrote:
>Hi, Sean,
>
>A plugin cannot modify Fuel UI but it actually can change a
>segmentation
>type after deployment. On UI it's still GRE but in fact it will be
>VxLAN. I
>know, it's ugly, but should work.
>
>On Thu, May 28, 2015 at 7:47 PM, Sean M. C
> On May 28, 2015, at 12:47 PM, Hayes, Graham wrote:
>
> On 28/05/15 19:38, Adam Harwell wrote:
>> I haven’t seen any responses from my team yet, but I know we’d be
>> interested as well — we have done quite a bit of work on this in the
>> past, including dealing with the Designate team on this
Sam, Welcome to the Kolla core team!
https://review.openstack.org/#/admin/groups/460,members
Regards
-steve
From: "Daneyon Hansen (danehans)"
mailto:daneh...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: T
On 05/28/2015 07:20 PM, Fox, Kevin M wrote:
I don't know AMQP very well. At the protocol level, are Exchanges, Queues, etc
things? Are fanout, durability, and other things required or optional to be
implemented?
AMQP 1.0 is very different from the pre 1.0 versions. Where 0.8/0.9
focus on def
Hi, Sean,
A plugin cannot modify Fuel UI but it actually can change a segmentation
type after deployment. On UI it's still GRE but in fact it will be VxLAN. I
know, it's ugly, but should work.
On Thu, May 28, 2015 at 7:47 PM, Sean M. Collins wrote:
> VxLAN support cannot be made as a plugin bec
On 28/05/15 19:38, Adam Harwell wrote:
> I haven’t seen any responses from my team yet, but I know we’d be
> interested as well — we have done quite a bit of work on this in the
> past, including dealing with the Designate team on this very subject. We
> can be available most hours between 9am-6pm
+1
From: "Steven Dake (stdake)" mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, May 25, 2015 at 11:59 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:opensta
On 28 May 2015 at 03:09, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I've heard that other projects come up with actual action lists and
> work assignments. I've heard Nova, Ironic, Oslo do it, and I witnessed
> just that in those Oslo sessions I had a chance to
The glance_store release management team is pleased to announce:
Release of glance_store version 0.6.0
Please find the details related to the release at:
https://launchpad.net/glance-store/liberty/0.6.0
Please report the issues through launchpad:
https://bugs.launchpad.net/glance-s
while more effort, you could write a script that took a package name, and gave
back the whole set of rpm/versions that it depended on, then write that to a
file. If the list of rpm/versions from the previous run changes, then have
puppet kick the process?
Thanks,
Kevin
_
I haven’t seen any responses from my team yet, but I know we’d be interested as
well — we have done quite a bit of work on this in the past, including dealing
with the Designate team on this very subject. We can be available most hours
between 9am-6pm Monday-Friday CST.
--Adam
https://keybase.
> As part of the work to object-ify the image metadata dicts, I'm looking
> at the current way the libvirt driver fetches image metadata for an
> instance, in cases where the compute manager hasn't already passed it
> into the virt driver API. I see 2 methods that libvirt uses to get the
> image me
Makes sense to me. Has the Glance Artifact Repository implemented enough bits
to have Heat and/or Murano artefacts yet? Also, has there been any work on
Exporting/Importing them through some defined format (tarball?) that doesn't
depend on the artefact type?
I've been talking with the Heat folk
Comments/praise in-line.
On 5/28/15 11:54 AM, Thierry Carrez wrote:
> Hi everyone,
>
> TL;DR:
>
> - In an effort to reduce useless work, in Liberty we'll switch from
> trying to accurately predict what will end up in milestones to reporting
> what actually landed.
Glad to hear.
> - We'll also repl
On 28/05/15 03:35, Jan Provaznik wrote:
On 05/28/2015 01:10 AM, Steve Baker wrote:
On 28/05/15 10:54, Richard Raseley wrote:
Zane Bitter wrote:
Steve is working on a patch to allow package-based updates of overcloud
nodes[1] using the distro's package manager (yum in the case of RDO,
but
conce
I don't know AMQP very well. At the protocol level, are Exchanges, Queues, etc
things? Are fanout, durability, and other things required or optional to be
implemented?
Thanks,
Kevin
From: Gordon Sim [g...@redhat.com]
Sent: Thursday, May 28, 2015 10:05 AM
ESWAR RAO wrote:
Hi All,
I am looking into taskflow userguide and examples.
http://www.giantflyingsaucer.com/blog/?p=4896
I also started aggregating these on:
https://wiki.openstack.org/wiki/TaskFlow#Blogs.2Ftutorials
If people know of more/others please add :-)
Thanks!
Can anyone pleas
On 05/28/2015 01:14 PM, Rodrigo Barbieri wrote:
For Share Migration, I am looking into integrating it with "Private
Driver Storage" as Valeriy mentioned. The purpose is in fact different
than not displaying the volume being migrated to the user, we are
attempting to not use a temporary DB entry
Btw, if u *do not* want to do a spec (using [1]) or blueprint let me
know and I'll probably make a spec so that we can ensure (and agree on)
the semantics of this because the specifics of what 'cancel' or 'abort'
means start to matter.
[1] https://github.com/openstack/oslo-specs/blob/master/sp
Hello there!
First, for those of you who hadn't been at Horizon design session where I
was telling & showing the Merlin framework, here is the related etherpad
[1] and the demo slides themselves [2]. Merlin wasn't the only thing shown
at that design session, I hope that some video of HotBuilder de
Hi Kunal,
I would like to participate as well.
Mon-Fri morning US Pacific time works for me.
Thanks,
Rakesh Saha
On Tue, May 26, 2015 at 8:45 PM, Vijay Venkatachalam <
vijay.venkatacha...@citrix.com> wrote:
> We would like to participate as well.
>
>
>
> Monday-Friday Morning US time works for
> On May 28, 2015, at 9:54 AM, Monty Taylor wrote:
>
> On 05/28/2015 12:41 PM, Devananda van der Veen wrote:
>> Hi all,
>>
>> tl;dr;
>>
>> At the summit, the Ironic team discussed the challenges we've had with
>> the current release model and came up with some ideas to address them.
>> I had a
This is great work guys. Can we add it to the wiki too? Also +2 on the
name from Emilien.
On Fri, May 22, 2015 at 6:12 PM, Emilien Macchi wrote:
>
>
> On 05/22/2015 04:53 PM, Sebastien Badia wrote:
> > Hi,
> >
> > During the Puppet session (during the Vancouver summit), we talked about
> > a bo
For Share Migration, I am looking into integrating it with "Private Driver
Storage" as Valeriy mentioned. The purpose is in fact different than not
displaying the volume being migrated to the user, we are attempting to not
use a temporary DB entry at all. I am not sure how this will play out,
espec
Hi Oleksii,
Thanks for putting together the slides, they are well done and extremely useful!
I find this 0MQ driver redesign proposal a much needed improvement over the
current design.
However it is worth debating the need to keep the proxy server and I would be
interested to hear from others a
On 05/28/2015 05:14 PM, Fox, Kevin M wrote:
Thats like saying you should implement a sql engine inside of
Berkeley DB since so many folks like sql... Not a good fit. If you
want AMQP, get an AMQP server. Zaqar's intentionally lighter weight
then that. Hardly any OpenStack services use but a fract
On 05/28/2015 12:41 PM, Devananda van der Veen wrote:
> Hi all,
>
> tl;dr;
>
> At the summit, the Ironic team discussed the challenges we've had with
> the current release model and came up with some ideas to address them.
> I had a brief follow-up conversation with Doug and Thierry, but I'd
> li
VxLAN support cannot be made as a plugin because plugins cannot modify
the initial networking wizard (based on conversations I've had in
#fuel-dev) where the choices between Neutron VLAN, Neutron GRE, and
nova-network are shown to the user.
I am currently working on this blueprint and have a WIP p
Hi all,
tl;dr;
At the summit, the Ironic team discussed the challenges we've had with
the current release model and came up with some ideas to address them.
I had a brief follow-up conversation with Doug and Thierry, but I'd
like this to be discussed more openly and for us (the Ironic dev
communi
+1
I've been placing mine out at:
https://github.com/EMSL-MSC/heat-templates/tree/master/cfn
I've split common patterns into a reusable library under:
https://github.com/EMSL-MSC/heat-templates/tree/master/cfn
so that users don't have to reimplement any of those things themselves. They
aren't p
Thats like saying you should implement a sql engine inside of Berkeley DB since
so many folks like sql... Not a good fit. If you want AMQP, get an AMQP server.
Zaqar's intentionally lighter weight then that. Hardly any OpenStack services
use but a fraction of AMQP though, so getting oslo.messagi
[This was originally posted to openst...@lists.openstack.org by accident.
Reposting it to openstack-dev.]
Calling all Heat neophytes, aficionados, and everyone in between ...
I've often thought it would be helpful to add a Heat Template Cookbook to the
developer documentation.
Like any helping
Feel free to add it, or open a blueprint, or make a spec to :)
Any of the above are ok with me.
I did start prototyping something @
https://review.openstack.org/#/c/184663/ (external cancellation) but it
might be going in the wrong direction (or a different direction); so
feel free to comment
Hi everyone,
TL;DR:
- In an effort to reduce useless work, in Liberty we'll switch from
trying to accurately predict what will end up in milestones to reporting
what actually landed.
- We'll also replace weekly release management 1:1 sync points with
office hours.
- For Liberty we'll have two r
On 05/27/2015 05:08 PM, Hayes, Graham wrote:
It was agreed that Zaqar would look at a oslo_messaging driver for the
services that did not agree with the 3 options presented.
Another option there would be to add amqp 1.0 support to zaqar, and then
you could use the amqp 1.0 driver with zaqar as
+1
Doug
> On May 28, 2015, at 7:42 AM, Kyle Mestery wrote:
>
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently become my testing Lieutenant. His influence and knowledge in
On 2015-05-28 11:58:43 +0300 (+0300), Eduard Matei wrote:
> We had some issues with jenkins/devstack so i updated both the jenkins
> version and the devstack.
> When starting nodepool it tries to create a new image but it fails after ~5
> minutes:
>
> 2015-05-28 10:49:21,509 ERROR nodepool.image.b
On Thu, May 28, 2015 at 5:02 AM, Martin Mágr wrote:
>
> On 05/28/2015 10:47 AM, Jan Provaznik wrote:
>>
>> On 05/28/2015 10:25 AM, Martin Mágr wrote:
>>>
>>>
>>> On 05/28/2015 09:35 AM, Jan Provaznik wrote:
On 05/28/2015 01:10 AM, Steve Baker wrote:
>
> On 28/05/15 10:54, Richard
I know there were discussions during the summit on how to fix quota bugs, and
in particular the multi instance code was making the solution harder.
I agree with you though, if the api is to stay, the current behavior seems
broken.
Thanks,
Kevin
From: Chr
On 5/27/2015 7:21 PM, John Griffith wrote:
On Wed, May 27, 2015 at 12:15 PM, Joe Gordon mailto:joe.gord...@gmail.com>> wrote:
On Tue, May 26, 2015 at 8:45 AM, Daniel P. Berrange
mailto:berra...@redhat.com>> wrote:
On Fri, May 22, 2015 at 02:57:23PM -0700, Michael Still wro
Hey everyone!
We had an _excellent_ discussion in Vancouver, but with only 40 minutes to
discuss things we didn't reach consensus on many topics that we really
needed to hash out. In order to make sure that the rest of this list is
addressed, I'm including a summary of the discussion here and will
+1
From: Oleg Bondarev mailto:obonda...@mirantis.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 28, 2015 at 5:31 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] Proposing Assaf Muller for the N
+1
Great addition to the team! Yeah!
Edgar
From: Kyle Mestery mailto:mest...@mestery.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 28, 2015 at 6:42 AM
To: "OpenStack Development Mailing List (not f
+1
On Thu, May 28, 2015 at 5:01 PM, Henry Gessau wrote:
> +1
>
> On Thu, May 28, 2015, Kyle Mestery wrote:
> > Folks, I'd like to propose Assaf Muller to be a member of the Neutron
> core
> > reviewer team. Assaf has been a long time contributor in Neutron, and
> he's
> > also recently become m
Thanks Doug!
On Thu, May 28, 2015 at 10:10 AM, Doug Hellmann wrote:
> Excerpts from Davanum Srinivas (dims)'s message of 2015-05-28 06:02:24 -0400:
>> That's right. The oslo team is OK with the liaison to other teams not
>> being a core reviewer.
>
> I've updated the wiki to reflect that.
>
> Dou
Excerpts from Davanum Srinivas (dims)'s message of 2015-05-28 06:02:24 -0400:
> That's right. The oslo team is OK with the liaison to other teams not
> being a core reviewer.
I've updated the wiki to reflect that.
Doug
__
Op
+1
On Thu, May 28, 2015, Kyle Mestery wrote:
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently become my testing Lieutenant. His influence and knowledge in
> testing will be cri
1 - 100 of 157 matches
Mail list logo
