+1, this is great.
We do have a few issues with HA though which block us from further testing.
There is no evidence that this final patch enabling the feature caused
those, but let's focus on investigation. Please no code merges if it's not
related to basic BuildVerificationTests (BVT) we have.
I
In latest version of python-keystoneclient using admin_token in auth_token
middleware was depracted. So in future we need to create configuration
similar to openstack with nailgun_service user. In that configuration there
should be no problem with upgrades.
We can do it after 5.1.
On Mon, Jul 28,
Hello Maciej,
can I see your code somewhere? I have written an extension recently and I
might can help you. The blog post is quite similar of what I've done, so
you should be close to get it work.
Regards,
jaume
On 29 July 2014 08:28, Maciej Nabożny wrote:
> Hello!
> This is my first mail on
Hi together,
I found two blueprint templates for neutron
The .rst file on github
http://git.openstack.org/cgit/openstack/neutron-specs/tree/specs/template.rst
and the one on the openstack wiki page
https://wiki.openstack.org/wiki/Neutron/BlueprintTemplate
Are both templates still valid or is th
On 07/28/2014 04:04 AM, Chris Dent wrote:
> On Mon, 28 Jul 2014, Thomas Goirand wrote:
>
>> That's exactly the version which I've been looking at. The thing is,
>> when I run the unit test with that version, it just bombs on me because
>> mechanize isn't there.
>
> How would you feel about it bei
Now with the Juno efforts to provide IPv6 support and some features (provider
networks SLAAC, RADVD) already merged, is there any plan/patch to revert this
Icehouse change [1] and make the 'ra_mode' and 'ipv6_address_mode' consumable?
Thanks,
Nir
[1] https://review.openstack.org/#/c/85869/
___
Greetings fellow NFV'stas!
I would like to explain and solicit feedback on our plan to support a new
open source NFV system in Juno. This work is approved as
low-priority/best-effort for Juno-3. (Yes, we do understand that we are
fighting the odds in terms of the Juno schedule.)
We are developing
Glad to see that the Bp is hypervisor independent.
We'll provide the Hyper-V implementation, based on this TODO comment:
https://review.openstack.org/#/c/99916/3/nova/virt/hyperv/driver.py
Thanks,
Alessandro
> On 25.07.2014, at 03:08, "Michael Still" wrote:
>
> Yep, I think this one has wel
On Mon, Jul 28, 2014 at 09:30:24AM -0700, Vishvananda Ishaya wrote:
> I think we should discuss adding/changing this functionality. I have had
> many new users assume that booting from an iso image would give them a
> root drive which they could snapshot. I was hoping that the new block
> device ma
Hi Folks,
Are there any guide or examples to show how to produce a new event or
notification add add a handler for this event in ceilometer?
I am asked to implement OpenStack service monitoring which will send an event
and trigger the handler once a service, say nova-compute, crashes, in a shor
Yes, here is extension code:
http://pastebin.com/btYQjwnr
service plugin code:
http://pastebin.com/ikKf80Fr
and script, which makes requests to neutron:
from neutronclient.neutron import client
c = client.Client('2.0',
tenant_name='admin',
username='admin',
Hi
I am working on this bug [1] and [2] was submitted to try to
fix it, unfortunately seems both way I can image failed to pass Jenkins
test
Do anyone have any idea on how to handle this problem or any
mail has conclusion about it? Thanks for support ~
[1] https://bu
On Tue, Jul 29, 2014 at 11:15:45AM +0200, Maciej Nabożny wrote:
[Just a generic comment, not related to the extension code in question.]
> Yes, here is extension code:
> http://pastebin.com/btYQjwnr
> service plugin code:
> http://pastebin.com/ikKf80Fr
Pastebins expire, it's useful to provide UR
The code sprint was pretty productive and attended by current and new members:
https://wiki.openstack.org/wiki/Neutron/GroupPolicy/JunoCodeSprint
We were able to fix some of our DB migration issues, and also make
significant progress with the API intercept discussion.
The following is a status re
Maciej: have you loaded the service plugin in the neutron.conf?
service_plugins =
neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,neutron.services.loadbalancer.plugin.LoadBalancerPlugin,neutron.services.floatingports.FloatingPort
Neutron needs to know what plugins to load at start up t
On Tue, 29 Jul 2014, Thomas Goirand wrote:
Sorry, I couldn't reply earlier.
No problem.
However, from *your* perspective, I wouldn't advise that you keep using
such a dangerous, badly maintained Python module. Saying that it's
optional may look like you think mechanize is ok and you are vouc
Looking at the current review backlog I think that we have to
seriously question whether our stable branch review process in
Nova is working to an acceptable level
On Havana
- 43 patches pending
- 19 patches with a single +2
- 1 patch with a -1
- 0 patches wit a -2
- Stalest waiting 111
I deployed a single node devstack on Ubuntu 14.04.
This devstack belongs to Juno.
1) git clone https://github.com/openstack-dev/devstack.git
2)cd devstack
3)vi local.conf
[[local|localrc]]
ADMIN_PASSWORD=some_password
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASS
On 28 July 2014 11:37, Salvatore Orlando wrote:
> Therefore the likeness of your patch merging depends on the specific
> nature of the -1 you received.
>
This is really a key point.
Here is a pattern that's worth recognising:
If your code is in reasonable shape but there is no urgent need to c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 12:15, Daniel P. Berrange wrote:
> Looking at the current review backlog I think that we have to
> seriously question whether our stable branch review process in
> Nova is working to an acceptable level
>
> On Havana
>
> - 43 patches
You should be able to trace the failed request in the cinder-api and
cinder-volume logs to find out what caused the error. Grepping for
ERROR in both those logs is usually a good starting point.
On 29 July 2014 11:10, Nikesh Kumar Mahalka wrote:
> I deployed a single node devstack on Ubuntu 14.04
Nir Yechiel wrote:
> Now with the Juno efforts to provide IPv6 support and some features
> (provider networks SLAAC, RADVD) already merged, is there any plan/patch to
> revert this Icehouse change [1] and make the 'ra_mode' and
> 'ipv6_address_mode' consumable?
>
> Thanks,
> Nir
>
> [1] https://
Swartzlander, Ben a écrit :
> Manila has come a long way since we proposed it for incubation last autumn.
> Below are the formal requests.
>
> https://wiki.openstack.org/wiki/Manila/Incubation_Application
> https://wiki.openstack.org/wiki/Manila/Program_Application
>
> Anyone have anything to ad
Thank you very much! The constants list was the problem. I've also added
empty list as result for get_floatingports and it works perfectly :)
Maciek
W dniu 29.07.2014, 12:09, Jaume Devesa pisze:
Maciej: have you loaded the service plugin in the neutron.conf?
service_plugins =
neutron.services
Ihar Hrachyshka a écrit :
> On 29/07/14 12:15, Daniel P. Berrange wrote:
>> Looking at the current review backlog I think that we have to
>> seriously question whether our stable branch review process in
>> Nova is working to an acceptable level
>
>> On Havana
>
>> - 43 patches pending
>> - 1
On 07/29/2014 12:43 PM, Duncan Thomas wrote:
You should be able to trace the failed request in the cinder-api and
cinder-volume logs to find out what caused the error. Grepping for
ERROR in both those logs is usually a good starting point.
Also, from the log lines you posted it seems a snapshot
On Mon, Jul 28, 2014 at 6:45 PM, Matt Riedemann
wrote:
> Nove needs a python-neutronclient release to use the new
> MacAddressInUseClient exception type defined here [1].
>
I'll spin a new client release today Matt, and reply back on this
thread once that's complete.
Thanks,
Kyle
> [1] https://r
On Mon, Jul 28, 2014 at 1:42 PM, Hemanth Ravi wrote:
> Kyle,
>
> One Convergence CI has been fixed (setup issue) and is running without the
> failures for ~10 days now. Updated the etherpad.
>
Thanks for the update Hemanth, much appreciated!
Kyle
> Thanks,
> -hemanth
>
>
> On Fri, Jul 11, 2014 a
This all looks good to me. My only concern is that we need to land a
driver in Juno as well. The HA-proxy based, agent-less driver which
runs on the API node is the only choice here, right? Otherwise, the
scalable work is being done in Octavia. Is that correct?
On Mon, Jul 28, 2014 at 2:46 PM, Bra
On Tue, Jul 29, 2014 at 3:12 AM, Andreas Scheuring
wrote:
> Hi together,
> I found two blueprint templates for neutron
>
> The .rst file on github
> http://git.openstack.org/cgit/openstack/neutron-specs/tree/specs/template.rst
>
> and the one on the openstack wiki page
> https://wiki.openstack.org
Hi folks,
I'm working on a change for neutron LBaaS service.
Since there is a massive work done for LBaaS these days, my change depends on
other changes being reviewed in parallel in gerrit.
I don't have a big git knowledge and I'm failing in figuring out the right
procedure that should be follo
On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez wrote:
> Ihar Hrachyshka a écrit :
> At the dawn of time there were no OpenStack stable branches, each
> distribution was maintaining its own stable branches, duplicating the
> backporting work. At some point it was suggested (mostly by RedHa
Daniel P. Berrange wrote:
> The situation I'm seeing is that the broader community believe that
> the Nova core team is responsible for the nova stable branches. When
> stuff sits in review for ages it is the core team that is getting
> pinged about it and on the receiving end of the complaints the
On Tue, Jul 29, 2014 at 04:40:33AM EDT, Nir Yechiel wrote:
> Now with the Juno efforts to provide IPv6 support and some features (provider
> networks SLAAC, RADVD) already merged, is there any plan/patch to revert this
> Icehouse change [1] and make the 'ra_mode' and 'ipv6_address_mode' consumabl
+1, it sounds like the best approach for such situation.
On Sat, Jul 19, 2014 at 1:18 AM, Russell Bryant wrote:
> On 07/18/2014 11:38 AM, Thierry Carrez wrote:
>> Hi everyone,
>>
>> At the last cross-project/release meeting we discussed the need to track
>> yet-unapproved specs in milestone relea
Hi All,
Due to key members of our team travelling this week we will have to postpone
the meeting. We'll reconvene next week at the usual time.
Peter J. Pouliot CISSP
Sr. SDET OpenStack
Microsoft
New England Research & Development Center
1 Memorial Drive
Cambridge, MA 02142
P: 1.(857).4536436
E:
Hi all,
I have recently had a few people express concern to me that the current meeting
time is preventing their attendance at the meeting. As we're still using the
original meeting time we discussed using for a trial period immediately after
summit it is probably time we reassess anyway.
I ha
Hi Daniel,
Thanks for the feedback. I have two questions:
1. Is it available in Havana?
2. Is it possible to to say that the glance image should be fetched to a
CDROM device (and disk file named 'iso'), and the root disk should be
created blank according to the flavor settings (disk file named 'di
On 07/29/2014 02:05 AM, Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) wrote:
Hi Folks,
Are there any guide or examples to show how to produce a new event or
notification add add a handler for this event in ceilometer?
I am asked to implement OpenStack service monitoring which will send an
event an
Hi All,
Would making an nova-network mechanism driver for the ml2 plugin be possible?
I'm an operator not a developer so apologies if this has been
discussed and is either planned or impossible, but a quick web search
didn't hit anything.
As an operator I would envision this a a transition mecha
On 07/29/2014 11:03 AM, Daniel P. Berrange wrote:
> On Mon, Jul 28, 2014 at 09:30:24AM -0700, Vishvananda Ishaya wrote:
>> I think we should discuss adding/changing this functionality. I have had
>> many new users assume that booting from an iso image would give them a
>> root drive which they coul
- Original Message -
> From: "Luke Gorrie"
> To: "OpenStack Development Mailing List"
>
> Greetings fellow NFV'stas!
>
> I would like to explain and solicit feedback on our plan to support a new
> open source NFV system in Juno. This work is approved as
> low-priority/best-effort for Ju
On 07/29/2014 06:13 AM, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez wrote:
Ihar Hrachyshka a écrit :
At the dawn of time there were no OpenStack stable branches, each
distribution was maintaining its own stable branches, duplicating the
backporting work. At
At the mid-cycle meet-up yesterday we spent some time looking at our bug
dashboard (http://54.201.139.117/nova-bugs.html) and talking about things we
can do to help focus on bugs. We came up with the following ideas. I’d like
folks to weigh in on these i if you have some ideas or concerns.
On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote:
> On 07/29/2014 06:13 AM, Daniel P. Berrange wrote:
> >On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez wrote:
> >>Ihar Hrachyshka a écrit :
> >>At the dawn of time there were no OpenStack stable branches, each
> >>distribution was
On Tue, Jul 29, 2014 at 7:46 AM, Kyle Mestery wrote:
> On Mon, Jul 28, 2014 at 6:45 PM, Matt Riedemann
> wrote:
>> Nove needs a python-neutronclient release to use the new
>> MacAddressInUseClient exception type defined here [1].
>>
> I'll spin a new client release today Matt, and reply back on t
Hi all:
I've just pushed a new release of python-neutronclient out. This was
mainly to address the issue of Nova being able to use the new
MacAddressInUseClient exception [1]. In addition, the following,
changes are also a part of this release:
b21cafa Remove strict checking of encryption type
f9
Hi Evgeny,
I’m not sure I’m doing it in the most efficient way, so I’d love to hear
pointers, but what I’ve been doing:
First, to setup the dependent commit, the command is “git review –d”. I’ve
been using this guide:
http://www.mediawiki.org/wiki/Gerrit/Advanced_usage#Create_a_dependency
S
Yes. There is an outside chance that someone can re-add the agent after
we get the agent-less driver in, for Juno, but if v2 is not going to be
the default extension, I’m not sure it’s worth the effort, since some
version of Octavia should land in Kilo, during which I would also expect
v2 to becom
On 7/29/2014 9:15 AM, Kyle Mestery wrote:
On Tue, Jul 29, 2014 at 7:46 AM, Kyle Mestery wrote:
On Mon, Jul 28, 2014 at 6:45 PM, Matt Riedemann
wrote:
Nove needs a python-neutronclient release to use the new
MacAddressInUseClient exception type defined here [1].
I'll spin a new client rele
Hi Steve,
On 29 July 2014 17:21, Steve Gordon wrote:
> I've added the [third-party] tag as well to ensure this catches the
> broadest segment of relevant people.
>
Thanks!
> are any modifications to upstream Open vSwitch required to support Snabb?
>
Good question. No, this uses a separate vs
Hi,
When reviewing https://review.openstack.org/#/c/107954/ it occurred to me that
maybe we should consider having some kind of generic object wrapper that could
do notifications for objects. Any thoughts on this?
Thanks
Gary
___
OpenStack-dev mailing l
The Oslo team is pleased to announce the first release of oslo.utils,
the library that replaces several utils modules from oslo-incubator:
https://github.com/openstack/oslo.utils/tree/master/oslo/utils
The new library has been uploaded to PyPI, and there is a changeset in
the queue update the glob
On Thu, Jul 24, 2014 at 9:48 AM, Scott Devoid wrote:
> So it turns out that fixing this issue is not very simple. It turns out
> that there are stubbed out openstack.common.policy checks in the glance-api
> code, which are pretty much useless because they do not use the image as a
> target. [1] T
On Mon, Jul 28, 2014 at 8:12 AM, Tailor, Rajesh
wrote:
> Hi All,
>
> I have submitted the patch "Made provision for glance service to use
> Launcher" to the community gerrit.
> Pl refer: https://review.openstack.org/#/c/110012/
>
> I have also set the workflow to 'work in progress'. I will start
Keystone has a notifications module that is based on this idea. When
implementing notification in Keystone, we wanted it to be easy to deliver
notifications on new resources and extensions [1], which is where the idea
of the wrapper came from. With that framework in place, we wrap our CRUD
methods
On 29 July 2014 10:48, Luke Gorrie wrote:
> We are developing a practical open source NFV implementation for
> OpenStack. This is for people who want to run tens of millions of packets
> per second through Virtio-net on each compute node.
>
Incidentally, we do currently achieve ~ line rate with
- Original Message -
> From: "Luke Gorrie"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: "Nikolay Nikolaev"
> Sent: Tuesday, July 29, 2014 12:28:55 PM
> Subject: Re: [openstack-dev] [NFV][CI][third-party] The plan to bring up
> Snabb NFV CI for Juno-3
>
On 07/29/2014 11:43 AM, Tracy Jones wrote:
> 3. We have bugs that are really not bugs but features, or performance
> issues. They really should be a BP not a bug, but we don’t want these
> things to fall off the radar so they are bugs… But we don’t really know
> what to do with them. Should they
Gary Kotton wrote on 07/29/2014 12:43:08 PM:
> Hi,
> When reviewing https://review.openstack.org/#/c/107954/ it occurred
> to me that maybe we should consider having some kind of generic
> object wrapper that could do notifications for objects. Any thoughts on
this?
I am not sure what that wo
Just to put my $0.02 in: While it's a little disappointing that we won't
get everything into Juno that we'd like, I think the effort this team has
put into getting us to where we are is laudable. Although I would really
like to see L7 land as well, I have no problem with the prioritization as
laid
On 07/29/2014 11:48 AM, Russell Bryant wrote:
On 07/29/2014 11:43 AM, Tracy Jones wrote:
3. We have bugs that are really not bugs but features, or performance
issues. They really should be a BP not a bug, but we don’t want these
things to fall off the radar so they are bugs… But we don’t reall
On 07/29/2014 12:12 PM, Daniel P. Berrange wrote:
> Sure there was some debate about what criteria were desired acceptance
> when stable trees were started. Once the criteria are defined I don't
> think it is credible to say that people are incapable of following the
> rules. In the unlikely event
All:
I spent some time today cleaning up python-neutronclient in LP. I
created a 2.3 series, and created milestones for the 2.3.5 (June 26)
and 2.3.6 (today) releases. I also targeted bugs which were released
in those milestones to the appropriate places. My next step is to
remove the 3.0 series,
On 16:19 Thu 24 Jul , David Kranz wrote:
> I noticed that the cinder list-extensions url suffix is underneath
> the v1/v2 in the GET url but the returned result is the same either
> way. Some of the
> returned items have v1 in the namespace, and others v2.
For XML, the namespace is different.
Minesweeper for Neutron is now running again.
We updated the image for our compute nodes to ensure it is compliant with
commit [1].
We are still observing occasional infrastructure-related issues manifesting
as request timeout failures. We will soon whitelist those failures so that
mine sweeper wo
Hi Kyle,
I have a BP listed in https://blueprints.launchpad.net/python-neutronclient
and looks like it is targeted for 3.0 (it is needed fro juno-3) The code is
ready and in the review. Can it be a included for 2.3.7 release?
Thanks,
Nader.
On Tue, Jul 29, 2014 at 12:28 PM, Kyle Mestery wrote
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, July 31st at 17:00 UTC in the #openstack-meeting channel.
The agenda for Thursday's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to the
Hi everyone,
The raw template saved in the DB used to be the original template that
a user submits. With the recent fix for stack update, it now reflects the
template that is actually deployed, so it may be different from the
original template because some resources may fail to deploy. I wou
Last week at the TripleO midcycle we discussed the spec process that
we've adopted. Overall, I think most folks are liking the specs
themselves. I heard general agreement that we're helping to tease out
issues and potential implementation disagreements earlier in the
process, and that's a good thin
Hi folks,
I would add the pxe boot capability to Nova/libvirt and Horizon too.
Currently, compute instances must be booted from images (or snapshots)
stored in Glance or volumes stored in Cinder.
Our idea (as you can find below) is already described there [1] [2] and
"aims to provide a design for b
On Tue, Jul 29, 2014 at 3:50 PM, Nader Lahouti wrote:
> Hi Kyle,
>
> I have a BP listed in https://blueprints.launchpad.net/python-neutronclient
> and looks like it is targeted for 3.0 (it is needed fro juno-3) The code is
> ready and in the review. Can it be a included for 2.3.7 release?
>
Yes, y
On 11:08 Fri 25 Jul , Stefan Hajnoczi wrote:
> On Fri, Jul 25, 2014 at 10:47 AM, Nicholas A. Bellinger
> wrote:
> > As mentioned, we'd like the Nova folks to consider vhost-scsi support as
> > a experimental feature for the Juno release of Openstack, given the
> > known caveats.
>
> I think Op
Excerpts from Ton Ngo's message of 2014-07-29 13:53:12 -0700:
>
> Hi everyone,
> The raw template saved in the DB used to be the original template that
> a user submits. With the recent fix for stack update, it now reflects the
> template that is actually deployed, so it may be different fro
Hi all,
As I mentioned in a previous IRC, when writing our first few policies I had
trouble using the tables we currently use to represent external data sources
like Nova/Neutron.
The main problem is that wide tables (those with many columns) are hard to use.
(a) it is hard to remember what
As promised in Monday's Neutron IRC minutes [1], this mail is a "trip down
memory lane" looking at the history of the
Neutron GP project.. The original GP google doc [2] included specifying
policy via both a produce/consume 1-group
approach and as a link between two groups. There was an email t
Hello Everyone!
We were discussing the following blueprint in Glance:
Enhanced-Platform-Awareness-OVF-Meta-Data-Import
:https://review.openstack.org/#/c/104904/
The OVA format is very rich and the proposal here in its first incarnation is
to essentially Untar the ova package, andimport the firs
I've seen t-h failing on many patches today, most that aren't touching
the database migrations, but it's primarily catching my attention
because of the failure on this change:
https://review.openstack.org/#/c/109660/
It looks like a pretty simple issue of the decorator package not being
in wh
Hi Evgeny and Doug,
So the thing to keep in mind is that Gerrit determines a new review by
the change-id in the commit message. It then determines patch sets by
the commit hashes. This is my understanding of it at least. A commit's
hash gets changed on many actions such as cherry-picks, rebases
We bumped the minimum version of dnsmasq to 2.63 a while ago by this code
change:
https://review.openstack.org/#/c/105378/
However, currently we still "kind of" support earlier version of dnsmasq
because we only give a warning and don't exit the program when we find
dnsmasq version is less than t
On Tue, Jul 29, 2014 at 8:51 PM, Xuhan Peng wrote:
> We bumped the minimum version of dnsmasq to 2.63 a while ago by this code
> change:
>
> https://review.openstack.org/#/c/105378/
>
> However, currently we still "kind of" support earlier version of dnsmasq
> because we only give a warning and do
Its a good idea to have a generic way to handle object notifications.
Considering that different objects might have different payload and
different logic for handling payload, we may need some clear design for
this. Seems a bp is needed for this. Thanks.
2014-07-30 2:49 GMT+08:00 Mike Spreitzer :
Hi!
The Keystone team is looking for feedback from the community on what type of
Keystone Token is being used in your OpenStack deployments. This is to help us
understand the use of the different providers and get information on the
reasoning (if possible) that that token provider is being used
On Tue, 2014-07-29 at 13:38 +0200, Thierry Carrez wrote:
> Swartzlander, Ben a écrit :
> > Manila has come a long way since we proposed it for incubation last autumn.
> > Below are the formal requests.
> >
> > https://wiki.openstack.org/wiki/Manila/Incubation_Application
> > https://wiki.openstac
> When reviewing https://review.openstack.org/#/c/107954/ it occurred to
> me that maybe we should consider having some kind of generic object
> wrapper that could do notifications for objects. Any thoughts on this?
I think it might be good to do this in a repeatable, but perhaps not
totally autom
Hi Steve.
The timeslot of 5:00AM UTC(Tuesday) 30min clashes with it.
https://wiki.openstack.org/wiki/Meetings/ServiceVM
Please disable this time slot.
thanks,
On Tue, Jul 29, 2014 at 10:53:21AM -0400,
Steve Gordon wrote:
> Hi all,
>
> I have recently had a few people express concern to me tha
On 7/25/2014 2:38 PM, Clark Boylan wrote:
Hello,
The recent release of tox 1.7.2 has fixed the {posargs} interpolation
issues we had with newer tox which forced us to be pinned to tox==1.6.1.
Before we can remove the pin and start telling people to use latest tox
we need to address a new defau
On 28-Jul-14 22:37, Clint Byrum wrote:
> Excerpts from Zane Bitter's message of 2014-07-28 07:25:24 -0700:
>> On 26/07/14 00:04, Anant Patil wrote:
>>> When the stack is updated, a diff of updated template and current
>>> template can be stored to optimize database. And perhaps Heat should
>>> hav
On 07/29/2014 07:24 PM, Davanum Srinivas wrote:
> The Oslo team is pleased to announce the first release of oslo.utils,
> the library that replaces several utils modules from oslo-incubator:
> https://github.com/openstack/oslo.utils/tree/master/oslo/utils
>
> The new library has been uploaded to P
Greetings to All!
Your review / feedback is much awaited on the proposals in this blueprint.
Just wanted to let you know that we are planning to start implementing design
#3 later next week in case there isn't any further advice from you.
Appreciate your time here...
Many thanks!
Raghu
From:
On 07/30/2014 12:57 AM, Bhandaru, Malini K wrote:
> Hello Everyone!
>
> We were discussing the following blueprint in Glance:
> Enhanced-Platform-Awareness-OVF-Meta-Data-Import
> :https://review.openstack.org/#/c/104904/
>
> The OVA format is very rich and the proposal here in its first incarnat
91 matches
Mail list logo