Re: [Rdo-list] F20 networking refuses to start on boot
by Lars Kellogg-Stedman
[I'm redirecting this to rdo-list for wider exposure.]
On Thu, Jan 09, 2014 at 10:22:36PM -0700, Pete Zaitcev wrote:
> On Thu, 9 Jan 2014 15:40:13 -0500
> Lars Kellogg-Stedman <lars(a)redhat.com> wrote:
>
> > On Thu, Jan 09, 2014 at 01:34:54PM -0700, Pete Zaitcev wrote:
>
> > > It feels like something simple enough, but... I installed RDO on F20
> > > as a part of Test Day on Tuesday. Then I added a flat network to it,
> > > and I found no better way to do it than to take the main Ethernet
> > > out of the control of NetworkManager by adding NM_CONTROLLED=no to
> > > ifcfg-br-ex and ifcfg-p4p1. Ever since, the box has no network on boot.
> > > I have to log in on console and do "ifdown br-ex; ifup br-ex".
> >
> > Have you installed and activate the "network" service?
> >
> > chkconfig network on
> >
> > This is the legacy /etc/init.d/network script that brings up
> > networking in the absence of NetworkManager.
>
> I have done it and it makes no difference:
Actually, it looks like I'm experiencing the same issue with br-ex on
my F20 openstack install. Given an interface configuration file
/etc/sysconfig/network-scripts/ifcfg-br-ex that looks like this:
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=172.24.4.225
NETMASK=255.255.255.240
ONBOOT=yes
After I boot the interface looks like this:
br-ex: flags=67<UP,BROADCAST,RUNNING> mtu 1500
inet6 fe80::888c:81ff:febd:d8b8 prefixlen 64 scopeid 0x20<link>
ether 3a:69:08:00:0f:40 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Running ifdown/ifup as Pete describes correctly configures the
interface.
I'm starting up another F20 system right now to see if this is a
general problem with OVS bridges or if there's something peculiar on
my install.
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
10 years, 10 months
[Rdo-list] FOSDEM and Infrastructure.next
by Rich Bowen
I'll be at FOSDEM ( https://fosdem.org/2014/) in a few weeks, and
wondered if any of you folks will be there. It would be cool to meet
some of you and maybe grab a few of the famed Belgian beers with you.
Also, in the days right after FOSDEM, there's going to be an event in
Ghent - a short train ride away - called Infrastructure.Next
From the blog post (
http://community.redhat.com/blog/2013/12/announcing-infrastructure-next/):
Infrastructure.Next is the event for people interested in the evolving
tools and projects for managing large-scale IT infrastructure. From
storage to configuration management to virtualization infrastructure,
all the way to Infrastructure-as-a-Service (IaaS).
So if you're interested in the "Virtualization and Iaas" track at
FOSDEM, you may also be interested in sticking around for a few more
days for Infrastructure.Next. And, just as importantly, if you want to
speak at Infrastructure.next, please get in touch either with me, or
with jzb(a)redhat.com
--
Rich Bowen -rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 10 months
[Rdo-list] RDO test day: Thanks!
by Rich Bowen
Thanks so much to all of you who found time to help us test RDO. You can
see some of what was accomplished at
http://openstack.redhat.com/TestedSetups_2014_01 and you've already seen
Kashyap's list of the 48 (!!) tickets that were opened over the last two
days. Once again, thanks for your help with this.
And a reminder that test day isn't the only time you're allowed to test,
it's just the time when there's the most people doing it. If you missed
the test day, or if you just want to spend some additional time testing,
please continue to use the above TestedSetups page as a reference, and
let's see if we can get through everything.
Meanwhile, we're already looking towards the next test day, and hope to
have dates and information for you in the coming weeks.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 10 months
[Rdo-list] HostingCon RFP closes tomorrow
by Rich Bowen
For the conference speakers among you, I wanted to remind you that the
RFP for HostinCon closes *TOMORROW*:
HostingCon, event date June 16-18 in Miami Beach, FL. Please submit
talks at
http://www.hostingcon.com/speakers/speaking-proposal-guidelines/, by
January 10.
The HostingCon audience tends to be very interested in OpenStack
content,and the conference speaker list tends to include speakers from
across the OpenStack ecosystem. It's a great place to get the message
out about RDO, or to learn what is going on with OpenStack in the
hosting space.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 10 months
[Rdo-list] Time-based mass bug update w/ stock responses for RDO bugs? (like Fedora)
by Kashyap Chamarthy
We're (pbrady, mrunge, me) having this discussion on IRC, just wanted to
post it to wider audience who're asleep/just waking up.
I was thinking (in future) if it makes sense to mass update RDO bugs
with stock responses (like please try w/ blah version, etc) when we move
from one version to another (e.g. how Fedora does) to humanly keep
up2date with stale bugs, unresponsive reporters, etc.
Points of view (slightly edited for readability)
--------------
- mrunge: "I like the idea on auto-updating or closing bugs. It's not
ideal, but helps to reduce the number of bugs, which were forgotten
for whatever reason."
- pbrady: "kashyap, I think your suggestion of more
involved RDO/Fedora bug triage would obviate the need for that.
We kinda got that (auto-updating) automatically when the bugs were
in Fedora bugzilla, and since openstack release cadence matched
Fedora's. But with the move to separate RDO product
(in bugzilla, i.e.) and with the diverging OpenStack
and Fedora release cadence, a similar separate mechanism
would be useful
Re: non openstack project bugs, I suppose fortnightly we could do
half the "packaging" call on #rdo to triage distro bugs"
Any other constructive opinions?
mrunge, pbrady: Don't hesitate to yell if I misrepresented your comments.
--
/kashyap
10 years, 10 months
[Rdo-list] Bitergia RDO stats
by Rich Bowen
A few months ago we talked with Bitergia about providing some statistics
around RDO. I expect that most of you are familiar with Bitergia. For
those of you who aren't, they're the people who do the stats for
Stackalytics - http://www.stackalytics.com/
The RDO stats are now available at *http://openstack.redhat.com/stats/*
and are updated every morning.
Bitergia has asked that we run this by you, the RDO community, and get
any comments you may have. They asked me to particularly ask:
* Check your company affiliation, if you have commits or ticket
activity, to ensure that we are attributing correctly. (This can be hard
depending on what email address you use in your various interactions.)
* Check that the stats seem to make sense, and correspond with what you
think they *should* look like.
* Tell us whether the information is presented clearly, or if there's
something that can be done better/differently to communicate what things
mean.
Thanks!
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 10 months
