Thanks Mark, Arvind & team for the work on Dashboard! Apologies that I just
got around to reviewing the blueprint. This should provide us with a great
demo vehicle for the upcoming OpenStack Design Summit!
The initial mocks look good for our Quantum Beta, I just have a few comments
around our inte
Thanks Salvatore!
On Fri, Aug 5, 2011 at 2:34 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi Somik,
>
> ** **
>
> Please see my replies inline.
>
> ** **
>
> *From:* Somik Behera [mailto:so...@nicira.com]
> *Sent:* 05 August 2011 21:41
>
> *To:* Salvatore Orlando
>
Hey guys!
Quantum tab is fixed. (and thanks for setting up jobs, Joe.)
Branch merging. This is part of a longer conversation - so go ahead and
buckle yourselves in ... :)
Managing and merging lp merge props is done via tarmac, which is
configured outside of jenkins. For the projects using that s
Hi Somik,
Please see my replies inline.
From: Somik Behera [mailto:so...@nicira.com]
Sent: 05 August 2011 21:41
To: Salvatore Orlando
Cc: netstack@lists.launchpad.net
Subject: Re: [Netstack] Aligning the API code with the specification
Hi Salvatore,
Thanks for your continued contribution to get
Hi Salvatore,
Thanks for your continued contribution to getting our API house in order! I
am hoping after this we can figure a way to "lock" the wiki so that we
deliver this API and then try to work on the next rev.
I have two high-level points regarding the current spec as it stands today
and fe
Okay -
Merge request is in the pipeline for those of you who want to run the tests in
a virtual environment, and with Monty's help we now have a Quantum build slave
up and running. I've set up the dependencies that I know about to date and made
sure all the unit tests run and pass with those d
Awesome--thanks guys!
At Your Service,
--
Mark T. Voelker
On Fri, 2011-08-05 at 10:03 -0700, Joseph Heck wrote:
> I'm on it - be a good experience to work through Gerrit too...
>
> -joe
>
> On Aug 5, 2011, at 9:59 AM, Monty Taylor wrote:
> > Hey guys!
> >
> > We need to get a build slave s
I'm on it - be a good experience to work through Gerrit too...
-joe
On Aug 5, 2011, at 9:59 AM, Monty Taylor wrote:
> Hey guys!
>
> We need to get a build slave spun up for quantum.
>
> Normally - this would mean making sure that we had packaging and
> build-deps done properly ... but that's go
Hey guys!
We need to get a build slave spun up for quantum.
Normally - this would mean making sure that we had packaging and
build-deps done properly ... but that's going to be a little bit.
SO
If someone could grab the github.com/openstack/openstack-ci-puppet, add
something in manifests/site.p
On Fri, Aug 5, 2011 at 9:49 AM, Joseph Heck wrote:
> I've set up an initial job for you - "quantum" at
> https://jenkins.openstack.org/view/Nova/job/quantum/
>
> (Monty: I didn't know if I should make it's own tab/space for this or not,
> so I stuck it in Nova to start...)
>
> The pip-requires fi
I've set up an initial job for you - "quantum" at
https://jenkins.openstack.org/view/Nova/job/quantum/
(Monty: I didn't know if I should make it's own tab/space for this or not, so I
stuck it in Nova to start...)
The pip-requires file has a few little issues, so I've also made a branch to
corr
Thanks Joe,
Basic build and unit tests are probably the best place to start. The
quantum dependencies should be very similar to nova and other openstack
projects. Things will get more complicated with functional/system test as
there are different quantum "plugins" that may have more exotic depen
Hey Carl,
(sorry all for the delay in replying)
I'm relatively uninformed about Quantum right now - does testing it require
anything special on a Jenkins host? If not, I'd be more than willing to help
setup up some initial jobs for you in Jenkins to run through code and unit
tests. I could eas
looping in Soren, who manages all the openstack packaging.
Soren, willing to help?
On 08/05/2011 10:13 AM, Tyler Smith wrote:
Hi Salvatore,
Yes, you're correct about the packages. The files I was referring are
(currently) quantum/common/wsgi.py, quantum/common/utils.py, and
quantum/utils.py. T
I agree we are definitely on the same page.
Please see my reply to your comments below.
Salvatore
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: 05 August 2011 16:14
To: Salvatore Orlando
Cc: netstack@lists.launchpad.net
Subject: Re: [Netstack] Quantum API resource status proposal
Great Salv
Great Salvatore, I think we're largely on the same page, a few comments
below.
dan
On Fri, Aug 5, 2011 at 2:34 AM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Thanks for your comments Dan.
>
> Replies inline.
>
> ** **
>
> Cheers,
>
> Salvatore
>
> ** **
>
> *Fr
Hi Salvatore,
Yes, you're correct about the packages. The files I was referring are
(currently) quantum/common/wsgi.py, quantum/common/utils.py, and
quantum/utils.py. There would also be a couple of others
(quantum/common/exceptions.py for example).
Basically, any code that is used by the
Hi Tyler,
I'm sorry I will not be able to help you a lot as I'm quite ignorant as far as
packaging is concerned.
However, if I read your proposal correctly we will have the following packages:
Quantum-common
Quantum-core
Quantum-client
+1 a distinct package for each plugin
Is that correct?
Al
Hi everyone,
I've been working on figuring out the best way to get packing for
Quantum going. Here is my proposal on how to proceed.
To keep in line with how Nova does things, I think we should use
Python's setuptools to manage building packages (with a supplemental
build script for Debian
Thanks for your comments Dan.
Replies inline.
Cheers,
Salvatore
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: 05 August 2011 01:25
To: Salvatore Orlando
Cc: netstack@lists.launchpad.net
Subject: Re: [Netstack] Quantum API resource status proposal
Great write-up Salvatore, comments inline.
20 matches
Mail list logo
