Hi,
I agree with Matt here. This is not broad enough. One option is to have a
tempest class that overrides for various backend plugins. Then the test can be
haredednd for each driver. I am not sure if that is something that has been
talked about.
Thanks
Gary
From: Matt Riedemann mailto:mrie...@
Thanks Dolph and Mark for the welcome and guidance,
Will get start based on the pointers.
-Mayank
On Fri, Oct 11, 2013 at 8:06 PM, Mark McClain wrote:
>
> On Oct 11, 2013, at 9:14 AM, Dolph Mathews
> wrote:
>
>
> On Friday, October 11, 2013, Mayank Mittal wrote:
>
>> Hi Teams,
>>
>> Please su
Have you read the docs about nova baremetal ? The questions you're
asking - about bootstrapping and about a baremetal agent - don't make
any sense to me ;)
These are the needed steps:
- install openstack
- build a deploy ramdisk and kernel
- put them in glance
- configure nova baremetal as you
I wrote a vendor specific fwaas-driver for our firewall (I also wrote the
iptables reference fwaas driver).
As per my understanding, the driver demux happens in L3 agent. Since we
also wanted to enable our physical appliance for Fwaas, I had to extend L3
agent for insert the firewall into Neutron
There is also a tempest patch now to ease some of the libvirt-specific
keys checked in the new diagnostics tests there:
https://review.openstack.org/#/c/51412/
To relay some of my concerns that I put in that patch:
I'm not sure how I feel about this. It should probably be more generic but
I t
On Oct 12, 2013, at 5:59 PM, John Dickinson wrote:
> Co-reviewing each other's patches and discussing changes in #openstack-swift
> would be good ways to ensure that you are working in the same direction.
>
> --John
Kui ended up abandoning his changes and I'm going to review them to incorporat
On 13.10.2013, at 01:09, "Dan Smith" wrote:
>> 4) Periodically, code from the new project(s) must be merged into Nova.
>> Only Nova core reviewers will have obviously +2a rights here.
>> I propose to do it on scheduled days before every milestone, differentiated
>> per driver to distribute th
On 13.10.2013, at 01:26, "Joe Gordon"
mailto:joe.gord...@gmail.com>> wrote:
On Sat, Oct 12, 2013 at 12:21 PM, Alessandro Pilotti
mailto:apilo...@cloudbasesolutions.com>> wrote:
On 12.10.2013, at 20:22, "Dan Smith"
mailto:d...@danplanet.com>> wrote:
>> From the user perspective, splittin
Co-reviewing each other's patches and discussing changes in #openstack-swift
would be good ways to ensure that you are working in the same direction.
--John
On Oct 12, 2013, at 3:49 PM, Brian Curtin wrote:
> Hi,
>
> I just had a look at the python-swiftclient reviews in Gerrit and noticed
>
Hi,
I just had a look at the python-swiftclient reviews in Gerrit and noticed that
Kui Shi and I are working on the same stuff, but I'm guessing Kui didn't see
that I had proposed a number of Python 3 changes from a few weeks ago. Now that
there are reviews and a web of dependent branches being
On Sat, Oct 12, 2013 at 12:21 PM, Alessandro Pilotti <
apilo...@cloudbasesolutions.com> wrote:
>
>
> On 12.10.2013, at 20:22, "Dan Smith" wrote:
>
> >> From the user perspective, splitting off the projects seems to be
> >> focussing on the ease of commit compared to the final user
> >> experience
> 4) Periodically, code from the new project(s) must be merged into Nova.
> Only Nova core reviewers will have obviously +2a rights here.
> I propose to do it on scheduled days before every milestone, differentiated
> per driver to distribute the review effort (what about also having Nova core
>
From: Alessandro Pilotti [apilo...@cloudbasesolutions.com]
Sent: 12 October 2013 20:21
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Hyper-V] Havana status
> 1) All the drivers will still be part of Nova.
>
> 2) One official project
Thanks for the responses Nachi! I combined them into one message. See @PCM
inlineā¦
PCM (Paul Michali)
MAIL p...@cisco.com
IRC pcm_ (irc.freenode.net)
TW @pmichali
On Oct 11, 2013, at 5:40 PM, Nachi Ueno wrote:
> Hi Paul
>
> 2013/10/11 Paul Michali :
>> Hi folks,
>>
>> I have a bunch o
There are reviews up now to add user accounts for the TripleO run
OpenStack reference cloud
(https://wiki.openstack.org/wiki/TripleO/TripleOCloud).
To be eligible for an account, you need to be a TripleO ATC, or have
some use case which the TripleO PTL considers worthwhile (e.g. just
ask :)).
To
Hi folks,
> I was wondering in general how providers can customize service features,
> based on their capabilities (better or worse than reference). I could
create
> a Summit session topic on this, but wanted to know if this is something
that
> has already been addressed or if a different architec
On 12.10.2013, at 20:22, "Dan Smith" wrote:
>> From the user perspective, splitting off the projects seems to be
>> focussing on the ease of commit compared to the final user
>> experience.
>
> I think what you describe is specifically the desire that originally
> spawned the thread: making
> On 12.10.2013, at 20:04, "Tim Bell" wrote:
>
>
> From the user perspective, splitting off the projects seems to be focussing
> on the ease of commit compared to the final user experience. An 'extras'
> project without *strong* testing co-ordination with packagers such as SUSE
> and RedHat
Yup, it seems to be hypervisor specific. I have added in the Vmware support
following you correcting in the Vmware driver.
Thanks
Gary
From: Matt Riedemann mailto:mrie...@us.ibm.com>>
Reply-To: OpenStack Development Mailing List
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, October
FYI
On 10/10/13 9:43 PM, "Russell Bryant" wrote:
>Greetings,
>
>We already have more proposals for the Nova design summit track than
>time slots. Please get your proposals in as soon as possible, and
>ideally no later than 1 week from today - Thursday, October 17. At that
>point we will be foc
> From the user perspective, splitting off the projects seems to be
> focussing on the ease of commit compared to the final user
> experience.
I think what you describe is specifically the desire that originally
spawned the thread: making the merging of changes to the hyper-v driver
faster by ha
>From the user perspective, splitting off the projects seems to be focussing on
>the ease of commit compared to the final user experience. An 'extras' project
>without *strong* testing co-ordination with packagers such as SUSE and RedHat
>would end up with the consumers of the product facing th
> If the idea is to gate with nova-extra-drivers this could lead to a
> rather painful process to change the virt driver API. When all the
> drivers are in the same tree all of them can be updated at the same
> time as the infrastructure.
Right, and I think if we split those drivers out, then we
On Sat, Oct 12, 2013 at 8:59 AM, Nick Maslov wrote:
> Hi,
>
> I have following setup:
>
> 1) infrastructure node, IP in bond, hosting following KVM guests:
> 1.1) Postgres KVM guest
> 1.2) MQ KVM guest
> 1.3) DNS KVM guest
> 1.4) Control node with Nova API, Cinder API, Quantum Server, etc.
> ...
Hello Chris,
I thought it was a bug in SQLAlchemy code, so I wrote a snippet [1] to
check my assumption, but I haven't managed to reproduce the problem with
SQLAlchemy versions 0.7.9, 0.7.10 and 0.8.2.
I would suggest you to start from enabling logging of all SQL queries
SQLAlchemy issues [2] and
Hi,
Probably the last before Monday: due to various issues detected in RC1
testing, we just created a new Havana release candidate for OpenStack
Networking ("Neutron").
You can find the RC2 tarball and the list of fixed bugs at:
https://launchpad.net/neutron/havana/havana-rc2
This is hopefully
On 12 October 2013 21:35, Christopher Yeoh wrote:
> On Fri, 11 Oct 2013 08:27:54 -0700
> Dan Smith wrote:
>
> If the idea is to gate with nova-extra-drivers this could lead to a
> rather painful process to change the virt driver API. When all the
> drivers are in the same tree all of them can be
Really a good idea! It's painful for us to summit a patch, then waiting for
reviewing because of the time difference. It's more painful if we get a -1
after getting up. It's very appreciated that if someone could help, and we
can help others, too.
2013/10/12 Nikhil Manchanda
> Just wanted to ch
Happy Saturday everyone,
Due to major issues detected in key features during RC1 testing, we just
published new Havana release candidates for OpenStack Compute ("Nova")
and OpenStack Orchestration ("Heat").
You can find RC2 tarballs and lists of fixed bugs at:
https://launchpad.net/nova/havana/h
+1 for me. And I am willing to be a volunteer.
2013/10/12 Joe Gordon
> On Thu, Oct 10, 2013 at 4:47 AM, Vladik Romanovsky <
> vladik.romanov...@enovance.com> wrote:
>
>> Hello everyone,
>>
>> I have been recently working on a migration bug in nova (Bug #1233184).
>>
>> I noticed that compute se
On Fri, 11 Oct 2013 08:27:54 -0700
Dan Smith wrote:
>
> Agreed, a stable virt driver API is not feasible or healthy at this
> point, IMHO. However, it doesn't change that much as it is. I know
> I'll be making changes to virt drivers in the coming cycle due to
> objects and I have no problem subm
31 matches
Mail list logo