The transition is going to be difficult either way when you consider data
migrations..
Gary, I've scheduled a talk about the future of nova networking. I hope it
to be an open forum of ideas.
Also, for what it's worth, I'd like to keep quantum code and nova code as
separate as possible even if ovs
The Manchester Grand Hyatt is booked out for the conference. I made the
mistake of waiting to book hotel until I was surely going. Does anyone have
any reservations they can't keep?
thanks,
-tr3buchet
___
Mailing list: https://launchpad.net/~openstack
P
merge prop: https://review.openstack.org/#/c/6847/
now has both required +2s. I'll wait a day or two to approve just in case
there are any lingering objections.
-tr3buchet
On Thu, May 3, 2012 at 10:07 AM, Dan Prince wrote:
>
>
> - Original Message -
> > From: "John Garbutt"
> > To: "Da
2.8%)
> Dan Prince 84 (2.4%)
> Ziad Sawalha80 (2.3%)
> Jason Kölker 77 (2.2%)
> Mark McLoughlin 73 (2.1%)
> Jake Dahn 73 (2.1%)
> Rick Harris 71 (2.0%)
> Alex Meade 70
I agree with Soren.
On Sat, Jan 7, 2012 at 2:50 AM, Dan Wendlandt wrote:
> Context for openstack-mailing list:
>
> This is a thread from the netstack list about integrating VPN capability
> with Quantum. Wanted larger community feedback.
>
> -
>
> Hi Debo,
>
> Based on our disc
"I assume other developers are in the same boat as we often make better
tacticians than politicians."
+1
On Fri, Jan 6, 2012 at 1:43 PM, Todd Willey wrote:
> On Fri, Jan 6, 2012 at 5:26 AM, Mark McLoughlin wrote:
> > Hi Todd,
> >
> > On Thu, 2012-01-05 at 18:29 -0500, Todd Willey wrote:
> >> On
+1
On Fri, Dec 30, 2011 at 4:24 PM, Gabriel Hurley
wrote:
> Big +1 from me on using tox to manage testing across various Python
> versions. Another advantage it has over matrix builds in Jenkins is the
> fact that an ordinary developer can use it locally and verify the tests
> across versions *be
Fantastic! I've been tired of having to look up people to see what their
vote counted as. It's gotten hard to keep track of everyone.
-tr3buchet
On Tue, Dec 20, 2011 at 2:37 PM, Thierry Carrez wrote:
> James E. Blair wrote:
> > Monty and I have been working on a solution to a number of problems
This problem has to have been solved before. Anyone know how multinational
companies deal with meetings? Also, Soren, to be fair, I'm don't believe
I've heard anyone propose a meeting that wasn't on ~utc-7 business time,
yourself included. Maybe there should be some give and take here? Perhaps
this
Weekly status emails sent to whom? I think it could be a good idea but my
worry is that while the mailing list is efficient in terms of information
per second, it's an inefficient place for coordinating. Solve this and I'm
on board.
On Thu, Dec 8, 2011 at 7:26 AM, Soren Hansen wrote:
> 2011/12/8
excellent ideas. I especially like the standardized list of headers.
just to be sure, mondays at 2100utc? if so, no conflicts on my end
On Wed, Dec 7, 2011 at 4:51 AM, Thierry Carrez wrote:
> Vishvananda Ishaya wrote:
>
> > 2) *Closing down the team mailinglists.* Some of the lists have been a
I retract any concerns I brought up earlier as Soren gracefully answered
them in last week's meeting. +1 from me. I look forward to the review.
-tr3buchet
On Thu, Nov 24, 2011 at 3:30 AM, Soren Hansen wrote:
> 2011/11/24 Sandy Walsh :
> > haha ... worse email thread ever.
> >
> > I'll catch you
Add me as a +1 to ensuring that unittests are actually unittests instead of
a mix'n'match of different styles of test. This would make writing and
updating tests much more straightforward and actually catch problems in the
correct layer of tests, for example a change in network should not under
any
Mao, if you are familiar with launchpad, can you file a bug and assign it
to the nova-network team? You will be able to track the bug's status there
as well.
Thanks,
-tr3buchet
On Mon, Nov 14, 2011 at 8:04 AM, mao weijie wrote:
> Hi,
>
> I have found something maybe bug in nova-network
>
> ie:
+1
On Wed, Nov 9, 2011 at 9:35 AM, Sandy Walsh wrote:
> 9 * 3 - 26
>
>
>
> From:
> openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net[openstack-bounces+sandy.walsh=
> rackspace@lists.launchpad.net] on behalf of Brian Waldon [
> brian.wal.
There is now a network subteam as well.
https://launchpad.net/~nova-network
http://wiki.openstack.org/Teams
-tr3buchet
On Mon, Oct 17, 2011 at 12:56 AM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> I've been assimilating the plans from the design summit into blueprints.
> In the process i'v
I notices a gap -> networking
On Mon, Oct 17, 2011 at 12:56 AM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> I've been assimilating the plans from the design summit into blueprints.
> In the process i've noticed that we have a lot planned for the next few
> months. Some of these changes are
yeah repo is pretty nice. I've been using it in conjunction with regular git
commands. Really though, all these tools do is shorthand a few git commands.
Why not just use the git?
I don't think our official docs should reflect the use of a tool like
git-review; they should describe the entire git
+1
On Tue, Oct 11, 2011 at 3:59 PM, Brian Waldon wrote:
> I would like to propose we remove our implementation of OSAPI v1.0 from
> Nova for the following reasons:
>
> 1) Our implementation is incomplete, and there are no (visible) plans to
> complete it. Shared IP Groups and Backup Schedules hav
yep
On Thu, Sep 15, 2011 at 4:13 PM, Brian Waldon wrote:
> Chris (comstud) has been a great help with reviews lately and has quite a
> bit of knowledge of the system overall. I think he would add a great amount
> to the team, so I'm proposing we add him to nova-core.
>
> Brian Waldon
>
>
>
>
very nice!
On Mon, Sep 12, 2011 at 12:55 PM, Sandy Walsh wrote:
> Here's a wiki page of some screencasts I put together of recent Nova
> changes I've been working on.
>
> Please feel free to add your own.
>
> http://wiki.openstack.org/DemoVideos
>
> -S
> This email may include confidential inform
if you plan on using multiple networks, i would get into the habit of
specifying the bridge with the --bridge parameter to nova-manager network
create. If you rely on the flag and then create multiple networks they'll
all end up connected to the same bridge.
On Wed, Aug 17, 2011 at 7:17 PM, Joshua
I am!
On Thu, Aug 18, 2011 at 5:54 AM, Soren Hansen wrote:
> At the design summit, we agreed we'd work hard on improving our test
> coverage. Our friendly neighbourhood butler, Jenkins, keeps track of
> our test coverage:
>
>
> https://jenkins.openstack.org/job/nova-coverage/lastStableBuild/cobe
nice info there john \o/
2011/8/5 John Dickinson
> You only need a "-H 'Content-Length: 0'" in that command and it should
> work. For more infor on nested virtual directories, see
> http://programmerthoughts.com/programming/nested-folders-in-cloud-files/
>
> --John
>
>
> On Aug 5, 2011, at 4:24
I had to register my git email with gerrit as well, no problems after.
If you do a "git commit --amend" will the hook add the change-id after you
edit the commit message? I ask because it didn't when doing an interactive
rebase. I did it this morning but I pasted the change-id in myself.
-trey
O
On Tue, Aug 2, 2011 at 6:40 AM, Soren Hansen wrote:
> 2011/7/27 Trey Morris :
> > I'm fairly certain that in this particular case, without support from the
> > hypervisor and api lieutenants, and a testing guru or two, I would still
> be
> > trying to fit all th
*cheers*
On Mon, Aug 1, 2011 at 3:23 PM, Jay Pipes wrote:
> Hi Glance contributors,
>
> The time has come for us to move to the new code platform, using Git and
> Gerrit.
>
> I'd like to know what date you think is a good time for us to begin
> the transition?
>
> Everyone should read the docume
well I'm excited about it!
On Mon, Jul 18, 2011 at 4:20 PM, Monty Taylor wrote:
> On 07/18/2011 02:59 PM, Andy Smith wrote:
>
>> Jay and Monty, could you give the list an update on the status and
>> timeline of the GitHub migration?
>>
>
> Things are going quite swimingly. Proof of concept went
Just so we are all on the same page: step 3 refers to refactoring the
existing network managers to use melange, is the ultimate goal here for
melange to replace the current nova ip management scheme entirely?
On Wed, Jul 27, 2011 at 11:10 PM, Troy Toman wrote:
> At the Diablo summit, one of the
I'm fairly certain that in this particular case, without support from the
hypervisor and api lieutenants, and a testing guru or two, I would still be
trying to fit all the pieces together. Merging with broken pieces in this
case was necessary.
Some more thoughts to fuel discussion...
1) cooperati
The goal isn't for ec2 api to be a "second class citizen", but to keep it
from being a limiting factor since we don't have control over it. How does
the compatibility layer make it second class?
On Thu, Jul 7, 2011 at 10:53 AM, Soren Hansen wrote:
> 2011/7/7 Vishvananda Ishaya :
> > I think we s
If I had to choose between dropping or truncating UUIDs and failing feature
parity with the ec2 api, i'd go with the latter. Pros and cons for UUIDs
have already been discussed and decisions made. The EC2 api shouldn't get in
the way. A translation layer to sit in between the EC2 and OS APIs would
I like vish's idea. instead of 999, maybe it should be anything over 9000.
-tr3buchet
On Wed, Jun 1, 2011 at 1:47 PM, Brian Schott wrote:
> That's not crazy, but I'd recommend a range of numbers 900-999? There have
> been cases where larger branches have multiple migrate files.
>
> Brian Schot
I think timestamp is the way to go. File name conflict shouldn't be the way
we prevent ourselves from doing stupid things. If someone merge props a
change with a migration, it's the job of both the developer and the core
reviewers to make sure something horrible isn't happening in the database as
a
+1
On Wed, May 11, 2011 at 2:38 PM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> We have quite a large backlog of merge proposals here:
>
> https://code.launchpad.net/~rlane/nova/lp773690/+merge/59565
>
> I've been attempting to go through them to find some high priority ones to
> review. It
Keep in mind you can choose other hypervisors and still run the whole stack
on a single host.
-trey
On Sun, May 8, 2011 at 10:40 AM, Vishvananda Ishaya
wrote:
> If you are running inside of virtualbox, you will have to use nova in
> software mode (--libvirt_type=qemu) and it will be extremely sl
sweet. Is it possible to have white boards in and around these locations?
-tr3buchet
On Wed, Apr 20, 2011 at 3:13 AM, Thierry Carrez wrote:
> Hello everyone,
>
> There was a huge number of sessions submitted for the design summit ! We
> have only 3 days though, and we cannot be in two places at
or free when they
> create an instance.
>
>
>
> "Jesse Andrews" said:
>
> I like the simple solution (#3) as well.
> It gets parity for the APIs while leaving more advanced topics for the NaaS
> discussions.
>
> -- Sent from my Tandy 1000sx
> Jesse And
Appears my response got lost somehow. I vote for #3 as it's the most
configurable (and affects nothing contrariwise). In addition to believing we
use flags too often, I don't think having a flag solves the problem very
well. A couple of examples show why:
you want a few instances having floating IP
n the code so I just wanted to verify.
> > Ryu
> > On Tue, Mar 29, 2011 at 1:13 AM, Trey Morris
> > wrote:
> >>
> >> Ryu, the new mac_address table is going to associate a mac_address with
> an
> >> instance and a network. When the VIFs are created fo
, it makes a lot of sense now. Thanks.
>
> Does this mean that when an instance launches, all the MAC
> addresses/Networks that belong in the same project get assigned to that
> instance? I couldn't find this in the code so I just wanted to verify.
>
> Ryu
>
> On Tu
multi-nic model into this one.
>
> I hope this made sense. I apologize for the length.
>
> Thanks,
> Ryu
>
>
> On Tue, Mar 29, 2011 at 12:47 AM, Trey Morris
> wrote:
>
>> I've written a migration to handle moving the data in the current
>> instan
I've written a migration to handle moving the data in the current instances
table mac_address column into the new mac_address table before the column is
removed.
I agree with Jay, data should never be discarded when migrating forward. I
don't think there has been a case yet where data is migrated
ts.launchpad.net] on behalf of Sandy Walsh [
> sandy.wa...@rackspace.com]
> *Sent:* Friday, March 25, 2011 10:26 AM
> *To:* Trey Morris; openstack@lists.launchpad.net
> *Subject:* Re: [Openstack] core dev
>
> +1 for the Sprinkle-laden Trey Bucket.
>
>
> --
All, consider me as a nova core dev. Seems we could use a few more and I
need an excuse to spend more time reviewing code :)
Thanks,
-tr3buchet
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
ind
maybe I'm missing something, but if you don't want to run a recent API why
should you expect to be able to run it with a recent release of nova? I
think trying to support older and new versions at the same time would clip
our wings, or at the very least add some nastiness to the code. If someone
wa
@brian: the problem with a json field is that searching would be really
expensive if we ever need to pull mac addresses from the db to ensure
uniqueness.
@Ilya: If I make a table, I plan on putting mac address, instance id,
network id, and if zones are about ready, some sort of zone information in
Tracking mac addresses is going to have to change for multi-nic. Instances
are going to have more than one mac address. It's been proposed that we
don't need to track the mac address(es) but I think it's necessary in order
to determine whether a mac is unique or not. Mac addresses don't need to be
+1 for long term plan discussion at the summit
+1 for having this in the diablo release
+1 for short term goal: tool being under our control via fork I don't think
JKM will keep up (nothing against JKM, it's just a lot of work).
On Fri, Feb 25, 2011 at 3:20 AM, Thierry Carrez wrote:
> Thierry Car
congrats sandy!
On Fri, Feb 25, 2011 at 1:54 AM, Thierry Carrez wrote:
> Sandy Walsh wrote:
> > I'd like to help out on the review process as
> > per http://wiki.openstack.org/Governance/Approved/CoreDevProcess
> >
> > I like quiet walks in the park and black and white movies.
>
> +1s from: jaypi
of the network, ie cannot plug a vNic into
> a network after the VM is started.
>
> Just so we're all on the same page, in what cases is dhcp/ra not
> appropriate?
>
> Cheers,
> Dan
>
> On Feb 25, 2011 7:11 AM, "Trey Morris" wrote:
> > definitely not
:)
On Thu, Feb 24, 2011 at 7:36 PM, Jay Pipes wrote:
> All done, and waiting to be almost immediately out of date. :)
>
> Cheers,
> jay
>
> On Thu, Feb 24, 2011 at 7:06 PM, Andy Smith wrote:
> > Please summarize these on the wiki and add your information the wiki,
> that
> > is what the wiki pa
this, I'm going off what we did in the past, and I know things
> have changed some since then.
>
> -Eric
>
> On Thu, Feb 24, 2011 at 04:46:28PM -0600, Trey Morris wrote:
> >yikes! i assumed tarmac was running things locally merged with trunk
> to
> >
ly a human check in there to make sure variable results like
> performance testing are ok), staging gets pushed to the real trunk.
>
> -Eric
>
> On Thu, Feb 24, 2011 at 04:36:16PM -0600, Trey Morris wrote:
> >I see. So their use would in general be for the use of automated
either way. These extra "trunks" will not
> need to be managed, as tarmac/jenkins will control them.
>
> -Eric
>
> On Thu, Feb 24, 2011 at 04:24:11PM -0600, Trey Morris wrote:
> >I'm curious what the point of having a line of trunks for a commit to
> &
sounds like we agree then. Each service has it's own tool set, and services
which are made up of sub-services will have a tool set which can make calls
translating through the tool sets of its sub-services.
On Thu, Feb 24, 2011 at 3:30 PM, Jay Pipes wrote:
> On Thu, Feb 24, 2011 at 4:06 PM, Eric
I'm curious what the point of having a line of trunks for a commit to bounce
down on its way to trunk would gain us other than having to manage a line of
trunks. What's wrong with status quo branch management (other than tests)?
What's wrong with having the commit sit in its LP topic branch, which
definitely not fine to use dhcp in all cases.
On Thu, Feb 24, 2011 at 3:28 AM, Dan Mihai Dumitriu wrote:
> If we can dynamically plug (and presumably unplug) a vNIC into a
> vPort, and assign the IP at that time, does that imply that we cannot
> use the IP injection into the VM image? Is it fine
Instead of an unstable trunk, i think code should just be better vetted
before it lands in the trunk. If the difference between trunk and your
proposed unstable trunk is a set of automated tests, then those tests can
just as easily be run on a LP branch before it gets into current trunk. We
just ne
+10 for lowercase.
On Thu, Feb 24, 2011 at 12:00 PM, Eric Day wrote:
> I would encourage using all lowercase for command line tools
> (oscompute), I don't really care what the name is though. :)
>
> -Eric
>
> On Thu, Feb 24, 2011 at 05:42:56PM +, Sandy Walsh wrote:
> >Perfect.
> >Obj
+2 from me
On Wed, Feb 23, 2011 at 10:45 AM, Matt Dietz wrote:
> +1 to this!
>
> On 2/17/11 3:28 PM, "Soren Hansen" wrote:
>
> >+1! (Yup, that was +factorial(1), for those keeping score at home)
> >
> >2011/2/17 Sandy Walsh :
> >> I'd like to help out on the review process as
> >> per http://wik
+1 to improving reviews since I agree with sandy on it being our greatest
strength. I also I prefer sandy's approach (unless I'm mistaken), jump in
and see how it goes, we can update a wiki as things proceed. I don't
understand the need for a more formal documentation of process. I'd just
hate for
congratulations!
On Wed, Feb 23, 2011 at 2:55 AM, Soren Hansen wrote:
> This is now done.
> Den 21/02/2011 08.46 skrev "Soren Hansen" :
>
> > 2011/2/19 Rick Harris :
> >> Throwing my hat into the ring for nova-core membership. Eager to help
> knock
> >> down that merge-prop backlog we have at th
2011 at 2:55 AM, Thierry Carrez
> wrote:
> > Trey Morris wrote:
> >> I don't like that it currently only runs on ubuntu + the ppa. If it
> >> doesn't work with existing versions I think we're doing something wrong.
> >> Even when natty comes out, I
sounds like a good plan to me :)
On Thu, Feb 17, 2011 at 11:44 AM, Jay Pipes wrote:
> On Thu, Feb 17, 2011 at 12:19 PM, Trey Morris
> wrote:
> > I don't like that it currently only runs on ubuntu + the ppa. If it
> doesn't
> > work with existing versions I th
I don't like that it currently only runs on ubuntu + the ppa. If it doesn't
work with existing versions I think we're doing something wrong. Even when
natty comes out, I don't like the idea of having to ensure I have latest
ubuntu for openstack to run.
As far as stability goes, i think integration
"Also, good point to keep in mind: Membership to nova-core isn't a
privilege or even any fun. It's a responsibility and a duty to your
fellow contributors :)"
well said!
On Thu, Feb 17, 2011 at 9:59 AM, Jay Pipes wrote:
> On Thu, Feb 17, 2011 at 9:26 AM, Thierry Carrez
> wrote:
> > That said t
My original (and simple as paul states) plan for handling it is to allow
multiple networks to exist within a project, then for each network a vif
will get created on the instance. The network information for those vifs
will be placed into the xenstore as part of the process for spawning an
instance
to not force anyone implementing a new
> instance action to handle the state_lock field manually, as it would
> probably result in the same 3 or 4 lines of code copy-pasted everywhere.
> However, I'm largely unaware of what the "good" solutions are to this
> probl
Regarding https://blueprints.launchpad.net/nova/+spec/xs-suspend
We need suspend as a power state (ram goes to disk, instance is shut down)
as well as a locking suspend (ram goes to disk, instance is shut down,
instance is no longer customer bootable) which make sense from a billing
point of view.
70 matches
Mail list logo
