Mostly FUDCon-ny stuff today.
Meeting started by jforbes at 19:05:38 UTC. The full logs are available
* Roll Call! (jforbes, 19:06:06)
* FUDCon (rbergeron, 19:08:27)
* please sign up for your wireless access for FUDCon. (rbergeron,
* cloud-init hackfest planned, likely for sunday morning, possibly 2
hours, by gholms (rbergeron, 19:32:32)
* possible openstack hackfest, depending on list of things to do,
mdomsch to look at markmc's last status mail (??) (rbergeron,
* ACTION: rbergeron to harass johnmark about any gluster activities
* Feature Submission deadline is quickly approaching on 2012-01-24
* Feature Freeze (testable/substantially complete) is 2012-02-07
* Open Floor (rbergeron, 19:47:05)
* LINK: http://fedoraproject.org/wiki/Schedule (rbergeron, 19:49:35)
Meeting ended at 19:55:05 UTC.
* rbergeron to harass johnmark about any gluster activities
Action Items, by person
* rbergeron to harass johnmark about any gluster activities
People Present (lines said)
* rbergeron (77)
* gholms (22)
* mdomsch (18)
* kkeithley (14)
* russellb (13)
* jforbes (12)
* Southern_Gentlem (9)
* jdarcy (7)
* zodbot (4)
* mull (3)
* gregdek (2)
* abadger1999 (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
On Mon, 9 Jan 2012 11:39:52 -0500
Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote:
> Looks good to me.. thought as a first time user of AWS, the process
> of creating an account and the verification was a bit slow.
> Also, when finally creating an account I've had no idea what to
> actually select. I saw something about free Amazon Micro EC2
> but no idea how to use it. Finally figured out that I am suppose
> to use the "Classic" workflow.
I see what you mean but I'm a little hesitant to add those kind of
details to the test case. It might be better to have a separate wiki
page for "getting started with EC2" instructions. I'll look around to
see if there is already a page like that.
> Perhaps adding in a comment saying: "As setting up a first-time AWS
> account can take sometimes a few hours, it is recommended that the
> user create this in advance."
It's been a while since I first created my account, so I had forgotten
> Also perhaps a link to do when nothing shows up. For example I just
> created an ami-5f16d836 and all lights are green but I can't connect
> to it. Perhaps some link to "how to get debug/bootup logs" from the
I wonder if your security group is set up to allow SSH. By default, no
traffic is allowed from outside EC2.
> Or how to add 'debug loglevel=8' to the kernel bootup? IF that is is
I'm honestly not sure how to do that, will look into whether or not
it's possible, though.
The getting started guide is missing the assignment to the em1 interface
in the initial ip address range setup. This results in flakey network
behavior when VMs are terminated.
Analysis of problem:
With default guide settings, assume two VMs are run via euca-run-instances.
The first VM will get a vnet with a mac address. It will then be added
directly into the bridge. The bridge will then take the MAC of the
vnet0 interface. Then the second VM will start and get a vnet1 with an
assigned MAC address.
Killing the first VM that was started (which has a MAC address equal to
the br0) will cause deletion of vnet0 and cause the bridge driver to
flush the arp table and choose a new bridge interface. This results in
disconnection of the remaining VM for 30-60 seconds. A simple solution
is to specify a physical bridge interface during bridge creation ie:
sudo nova-manage network create markmc 10.0.0.0/24 --bridge=br0
This is shown for the compute nodes, but not the controller nodes.
With this setting, br0 will always be assigned the MAC address of the
bridge interface. Then terminating VMs will not result in the arp table
being flushed, and loss of network connectivity.
This is shown in the "controller" section of the getting started guide
when using compute nodes, but not in the initial setup.
Note if vnet0 VM is killed, then the br0 will adopt the mac address of
vnet1. Then if vnet1 is killed the network will stall for 30-60 seconds
and lose the arp table (while killing the VM associated with vnet0 will
have no impact on the network).
This does raise the question what to do when em1 is taken out of
service. This will cause the bridge driver to flush the arp table and
pick a new device (vnet0) resulting in again flakey behavior with the
bridges when stopping virtual machines.
Just learning the ins and outs of bridges today I don't have a good
recommendation for a solution to this "em1 taken out of service" problem.
One idea I had was changing nova to add a "dummy" vnet0 before adding
em1 or any of the VM vnets (during br0 creation in nova-network). I'm
not sure if this would cause traffic to bridge out of the physical
interface properly, but it would fix the network connectivity issues and
arp table killing that occurs while a new bridge MAC is chosen.
Now off to PTO.
I realize many of us are on vacation this week but I'm shipping this
out in the hopes of getting something organized before the last
second, since I am pretty sure I will have plenty of other
ohgodlastsecond things to do come FUDCon time.
I know that Matt Domsch had previously sent an email about getting
together an OpenStack workshop/hackfest while we're at FUDCon. We also
presumably have folks planning on doing OTHER THINGS, so, feel free to
list your plans, wishes, hopes, dreams, and so forth.
Conveniently, I have a wiki page set up for this!
Once we have some stuff listed in the way of workshops/hackfests I'll
reserve our room spots for Friday and/or Sunday, hopefully in a
non-overlapping kind of way.
And so: Garrett, Andy, Greg, Perry, Russell, David, Mike, Matt, Clint,
Justin, John Mark, Marek, Karsten, Jeff, Kaleb (???), and anyone I
missed, (that's gholms, mull, gregdek, pmyers, drumkilla (I REFUSE TO
CALL YOU RUSSELLB), ke4qqq, mmcgrath, mdomsch, herlo, jforbes,
johnmark, mgoldmann, quaid, jdarcy, kkeithley for those playing along
at home) ......
Get your stuff listed! :)
In addition to the regular check-ins on things of cloudy nature, I
figured today would be a good time to see what everyone's plans are for
FUDCon next week.
When: 1900 UTC (2pm US Eastern, 11am US Pacific)
Where: #fedora-meeting on irc.freenode.net
P.S. There will be *no meeting* next week due to the volume of people at
This is a fairly significant openstack-nova update. Testing and karma
would be appreciated
-------- Forwarded Message --------
> From: updates(a)fedoraproject.org
> To: markmc(a)fedoraproject.org
> Subject: [Fedora Update] [new] openstack-nova-2011.3-18.fc16
> Date: Fri, 06 Jan 2012 14:23:20 +0000
> markmc has submitted a new update for Fedora 16
> Release: Fedora 16
> Status: pending
> Type: bugfix
> Karma: 0
> Bugs: 752709 - Failure to attach a volume
> Notes: This update includes ~50 patches from the upstream stable branch
> : and a fix for an issue with attaching volumes.
> Submitter: markmc
> Submitted: 2012-01-06 14:23:10