[Rdo-list] [package announce] openstack clients update
by Pádraig Brady
Havana and Icehouse RDO client packages have been updated as follows:
python-cinderclient-1.0.7-2
Add search_opts into the method list() for VolumeTypeManager (rhbz#1048326)
python-openstackclient-0.3.0-1
Update to upstream 0.3.0
New dependencies: python-six, python-requests
Restore compatibility with old EPEL python-keyring
python-heatclient-0.2.6-2
Add support for resource_types
In addition there have been these upstream rebases in the Icehouse repositories:
python-keystoneclient-0.4.1 -> 0.4.2
python-neutronclient-2.3.1 -> 2.3.3
10 years, 10 months
[Rdo-list] [package announce] openstack-packstack update
by Pádraig Brady
Havana and Icehouse RDO packstack has been updated as follows.
openstack-packstack-2013.2.1-0.29.dev956
- Fix qpid SSL installation errors (rhbz#1052163, rhbz#1048705)
- Open Keystone port for ALL (rhbz#1041560)
- Move to the upstream puppet-vswitch module
- Add missing example options (rhbz#971745)
- Install php only with nagios (rhbz#1039660)
- Change puppet-qpid module to upstream (rhbz#1029576)
- Update puppet-neutron to stable/havana which contains fixes for Puppet 3.4+ (lp#1267488)
- Updat puppet-swift to stable/havana (rhbz#1039981)
- Don't set libvirt_vif_driver nova config, deprecated by Havana and disallowed by Icehose (rhbz#1048315)
10 years, 10 months
[Rdo-list] Enabling 'ovs_use_veth' for DHCP/L3 agents breaks Neutron on recent versions of RHEL/CentOS
by Steve Gordon
Hi all,
I was asked to take a look at this bug for the openstack-manuals project - "Enabling 'ovs_use_veth' for DHCP/L3 agents breaks Neutron on recent versions of CentOS":
https://bugs.launchpad.net/openstack-manuals/+bug/1268806
"After assisting someone with troubleshooting networking, I determined that setting 'ovs_use_veth = True' in dhcp_agent.ini and l3_agent.ini breaks Neutron (at least with GRE) on recent versions of CentOS... perhaps because the kernel seems to fully support namespaces. This issue probably also affects Scientific Linux. Can anyone confirm whether recent RHEL kernels fully support namespaces? I would like to clarify this step and similar steps in other sections for all distributions."
Questions I have are:
a) Is it likely/expected that enabling ovs_use_veth = True will cause issues when using a kernel that supports netns?
b) Is there any downside at this point to setting ovs_use_veth = False?
Thanks,
Steve
10 years, 10 months
[Rdo-list] Neutron fails to connect to AMQP Server on Fedora 20 ( at startup) 3
by Boris Derzhavets
Next fresh install F20 & Havana via native repo.
Issue seems to be related to https://bugzilla.redhat.com/show_bug.cgi?id=1051593
Straight forward `packstack --alinone` install via native Havana repo with no problems.
Openstack-status is fine immediately after RDO setup
Recreating external network, OVS bridge "br-ex" and p37p1 as OVS port for "br-ex"
Reboot.
Openstack-status reports server errors
1.)
[root@openstack1 neutron(keystone_admin)]# nova net-list
reports server error
2)
[root@openstack1 neutron(keystone_admin)]# nova service-list
shows state down every where
3)
/var/log/neutron/server.log.gz is attached.
I believe to fix it , but it's just a hack
[boris@openstack1 ~]$ sudo su -
[sudo] password for boris:
Last login: Sun Jan 12 17:35:21 MSK 2014 on pts/0
[root@openstack1 ~]# ls -l /etc/neutron/neutron.conf
-rw-r-----. 1 root neutron 14386 Jan 12 16:15 /etc/neutron/neutron.conf
[root@openstack1 ~]# vi /etc/neutron/neutron.conf
Uncommented :
# Paste configuration file
api_paste_config = api-paste.ini
Updated /etc/rc.d/rc.local :-
[root@openstack1 neutron(keystone_admin)]# cat /etc/rc.d/rc.local
#!/bin/sh
losetup -f /var/lib/cinder/cinder-volumes && vgchange -a y cinder-volumes && systemctl restart openstack-cinder-volume.service
ifdown br-ex ;
ifup br-ex ;
service network restart ;
# Three times would be enough in general , but may be less
systemctl restart qpidd.service ;
systemctl restart qpidd.service ;
systemctl restart qpidd.service ;
service openstack-nova-compute restart ;
exit 0
Then in openstack-status report instead of server errors I get :-
[root@openstack1 neutron(keystone_admin)]# nova service-list
+------------------+------------------------+----------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at Disabled Reason |
+------------------+------------------------+----------+---------+-------+----------------------------+-----------------+
| nova-consoleauth | openstack1.localdomain | internal | enabled | up | 2014-01-12T14:01:20.000000 | None |
| nova-scheduler | openstack1.localdomain | internal | enabled | up | 2014-01-12T14:01:20.000000 | None |
| nova-conductor | openstack1.localdomain | internal | enabled | up | 2014-01-12T14:01:21.000000 | None |
| nova-cert | openstack1.localdomain | internal | enabled | up | 2014-01-12T14:01:20.000000 | None |
| nova-compute | openstack1.localdomain | nova | enabled | up | 2014-01-12T14:01:19.000000 | None |
+------------------+------------------------+----------+---------+-------+----------------------------+-----------------+
[root@openstack1 neutron(keystone_admin)]# nova net-list
+--------------------------------------+---------+------+
| ID | Label | CIDR |
+--------------------------------------+---------+------+
| 54aa7248-072d-4d2d-a953-916894946c23 | private | None |
| d8760dfb-0619-4cd1-a033-51bb04eeb402 | public | None |
+--------------------------------------+---------+------+
Neutron brought back to life
[root@openstack1 neutron(keystone_admin)]# neutron net-list
+--------------------------------------+---------+-----------------------------------------------------+
| id | name | subnets |
+--------------------------------------+---------+-----------------------------------------------------+
| 54aa7248-072d-4d2d-a953-916894946c23 | private | ec123834-0cae-43b7-b85a-b6329dcc5e88 10.0.0.0/24 |
| d8760dfb-0619-4cd1-a033-51bb04eeb402 | public | 87c37096-1186-4c67-8548-fb6c88839636 192.168.1.0/24 |
+--------------------------------------+---------+-----------------------------------------------------+
[root@openstack1 neutron(keystone_admin)]# neutron subnet-list
+--------------------------------------+----------------+----------------+--------------------------------------------------+
| id | name | cidr | allocation_pools |
+--------------------------------------+----------------+----------------+--------------------------------------------------+
| ec123834-0cae-43b7-b85a-b6329dcc5e88 | private_subnet | 10.0.0.0/24 | {"start": "10.0.0.2", "end": "10.0.0.254"} |
| 87c37096-1186-4c67-8548-fb6c88839636 | public_subnet | 192.168.1.0/24 | {"start": "192.168.1.57", "end": "192.168.1.97"} |
+--------------------------------------+----------------+----------------+--------------------------------------------------+
[root@openstack1 neutron(keystone_admin)]# ovs-vsctl show
d3454efb-b3d9-42d2-a277-913d5cf755fe
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "qg-ce79686e-b8"
Interface "qg-ce79686e-b8"
type: internal
Port "p37p1"
Interface "p37p1"
Bridge br-int
Port "qvo10bf42f7-82"
tag: 1
Interface "qvo10bf42f7-82"
Port "qr-01bdcf4b-05"
tag: 1
Interface "qr-01bdcf4b-05"
type: internal
Port "tapf8c3475f-f0"
tag: 1
Interface "tapf8c3475f-f0"
type: internal
Port br-int
Interface br-int
type: internal
Port "qvofee768e5-64"
tag: 1
Interface "qvofee768e5-64"
ovs_version: "2.0.0"
10 years, 10 months
[Rdo-list] Summary/Minutes from today's RDO bug triage [15-JAN-2014]
by Kashyap Chamarthy
Thanks all, for your participation.
Synopsis: 23 bugs out of 61 triaged (thanks larsks for looking up the
number!)
Notes from etherpad
-------------------
============
- Many PackStack issues - beginning to go stale, not sure
how much effort Packstack maintainers are will to put
given Foreman/Astopher (in near future) are being
driven as future installers
- But note that packstack is still maintained and bugs that
prevent successful installs should be addressed
- Foreman is not currently available for Fedora20
- Fedora OpenStack supports arches other than x86_64 just supported
by RDO but theforeman.org only seems to have x86_64 packages.
So we may put an exclusive arch in the RDO
openstack-foreman package.
- Need rotating volunteers to keep notes/chair the meeting.
- There's a rough consensus of triaging twice/month cadence.
============
============
#rdo Meeting
============
Meeting started by kashyap at 14:00:08 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/rdo/2014-01-15/rdobugtriage.2014-01-15-1...
.
Meeting summary
---------------
* LINK: https://etherpad.openstack.org/p/RDO-BugTriage (kashyap,
14:00:43)
* LINK: List of un-triaged bugs (NEW state) -- http://goo.gl/NqW2LN
(kashyap, 14:01:10)
* http://openstack.redhat.com/DeveloperTips (kashyap, 14:17:57)
* bug 1052311 assigned to jruzicka and marked triaged (mburned,
14:23:06)
* LINK: https://review.openstack.org/#/c/27251/ (larsks, 14:25:56)
* bug 958411 has patch merged in https://review.openstack.org/#/c/27251/
(mburned, 14:30:36)
* asked reported to try with latest packages (mburned, 14:30:47)
* LINK:
http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/
(mburned, 14:33:59)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=995570 is an RFE
from pixelb (kashyap, 14:59:20)
* LINK:
http://jenkins.rhev.lab.eng.brq.redhat.com:8080/view/RDO-Havana/job/packs...
(weshay, 15:16:47)
* LINK:
https://prod-rdojenkins.rhcloud.com/view/RDO-Havana/job/packstack-rdo-hav...
(kashyap, 15:19:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1014627 is also an
upstream bug. I'm going to reuse your verbage... (larsks, 15:54:29)
* 23 out of 61 bugs addressed (kashyap, 16:07:54)
* IDEA: We can have a rotating volunteers to keep notes/run the zodbot
commands? (kashyap, 16:08:24)
Meeting ended at 16:12:23 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* kashyap (164)
* larsks (113)
* mburned (55)
* weshay (35)
* russellb (11)
* xqueralt (7)
* jruzicka (6)
* ndipanov (5)
* zodbot (5)
* pixelb (5)
* bcrochet (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
/kashyap
10 years, 10 months
[Rdo-list] Formatting tip for RDO wiki pages
by Ryan O'Hara
In the recent LBaaS wiki page I wrote, I need to show output from
various command-line clients. The problem I ran into is that the wiki
page will wrap anything enclosed in <pre> tags, so I ended up with the
following solution:
<pre style="white-space: pre; overflow-x: auto; word-wrap: normal">
...
</pre>
This will add a horizontal scrollbar to the bottom of the preformatted
text box, which is the best solution I could come up with for handling
wide blocks of text. I've tested this with Firefox, IE, and Chrome and
it seems to render correctly on each.
Ryan
10 years, 10 months
Re: [Rdo-list] Rdo-list Digest, Vol 10, Issue 17
by Walter Derezinski
unsubscribe
--
WALTER DEREZINSKI
System Manager
Ericsson Television Inc.
Solution Area Media
4500 River Green Pkwy
Duluth, GA 30096, USA
Phone +1-678-404-1432
walter.derezinski(a)ericsson.com
www.ericsson.com
This Communication is Confidential. We only send and receive email on the
basis of the terms set out atwww.ericsson.com/email_disclaimer
On 1/14/14, 10:35 AM, "rdo-list-request(a)redhat.com"
<rdo-list-request(a)redhat.com> wrote:
>Send Rdo-list mailing list submissions to
> rdo-list(a)redhat.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/rdo-list
>or, via email, send a message with subject or body 'help' to
> rdo-list-request(a)redhat.com
>
>You can reach the person managing the list at
> rdo-list-owner(a)redhat.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Rdo-list digest..."
>
>
>Today's Topics:
>
> 1. Re: RDO Bug triage: 15JAN2014; UTC 14:00 (Rich Bowen)
> 2. Re: New RDO page for LBaaS (Lars Kellogg-Stedman)
> 3. Re: Formatting tip for RDO wiki pages (P?draig Brady)
> 4. Enabling 'ovs_use_veth' for DHCP/L3 agents breaks Neutron on
> recent versions of RHEL/CentOS (Steve Gordon)
> 5. First IRC RDO community meeting (Rich Bowen)
> 6. Re: First IRC RDO community meeting (Rich Bowen)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 13 Jan 2014 12:29:47 -0500
>From: Rich Bowen <rbowen(a)redhat.com>
>To: rdo-list(a)redhat.com
>Subject: Re: [Rdo-list] RDO Bug triage: 15JAN2014; UTC 14:00
>Message-ID: <52D4228B.40509(a)redhat.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>On 01/13/2014 10:06 AM, Kashyap Chamarthy wrote:
>>>> Kashyap, can you please send an invitation. (if it is not in a
>>>>calendar it'll probably be missed)
>>> >
>>> >I'm afraid, as of now I don't think (maybe I'm wrong) there's a
>>>sensible
>>> >way to send calendar invitations to public list. For now, I
>> Oops, truncated sentence, I meant - For now, I hope mailing list invite
>> would do & folks who are interested to participate would just remember.
>>
>One possibility is to create the event in Google Calendar, and send an
>invite from there to the list. I can moderate it through from there.
>
>--Rich
>
>--
>Rich Bowen - rbowen(a)redhat.com
>OpenStack Community Liaison
>http://openstack.redhat.com/
>
>
>
>------------------------------
>
>Message: 2
>Date: Mon, 13 Jan 2014 13:07:03 -0500
>From: Lars Kellogg-Stedman <lars(a)redhat.com>
>To: "Ryan O'Hara" <rohara(a)redhat.com>
>Cc: rdo-list(a)redhat.com
>Subject: Re: [Rdo-list] New RDO page for LBaaS
>Message-ID: <20140113180703.GA30987(a)redhat.com>
>Content-Type: text/plain; charset="us-ascii"
>
>On Mon, Jan 13, 2014 at 09:03:30AM -0600, Ryan O'Hara wrote:
>> I've written a guide for deploying LBaaS with RDO Havana, which also
>> covers some simple tests. The guide can be found here:
>
>That looks like a really nice guide. Thanks!
>
>--
>Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
>Cloud Engineering / OpenStack | " " @ twitter
>
>
10 years, 10 months
