[Rdo-list] Logging in with Google ID on RDO broken?
by Dave Neary
Hi,
I just tried to log into the wiki with my Google ID (as I have done in
the past), and got the following error:
Provider is required.
UniqueID is required.
The connection data has not been verified.
Did something change in the configuration of the connection to Google
recently? Has our API key expired or something?
Thanks,
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
10 years, 2 months
[Rdo-list] OpenStack speakers wanted for Ohio LinuxFest
by Rich Bowen
A friend of mine is on the committee for Ohio LinuxFest -
http://ohiolinux.org/ - October 24th and 25th - and although the CFP
isn't open just yet, he's asked me to poke around and see if anyone
around here might be interested in speaking to that crowd. It would
probably be introductory kind of content, since it's a general interest
event, rather than a deep OpenStack event.
So, if you're in that general area (it's in Columbus, Ohio), or will be
in late October, I'd be glad to make introductions. It's a fun
conference, and it's a great town.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 2 months
[Rdo-list] Neutron configuration files for a two node Neutron+GRE+OVS
by Kashyap Chamarthy
Heya,
Just in case if it's useful for someone, here are my working Neutron
configuration files (and iptables rules) for a two node set-up based on
IceHouse-M2 on Fedora-20,
- Controller node: Nova, Keystone (token-based auth), Cinder,
Glance, Neutron (using Open vSwitch plugin and GRE tunneling).
- Compute node: Nova (nova-compute), Neutron (openvswitch-agent)
Controller node Neutron configurations
======================================
1. neutron.conf
---------------
$ cat /etc/neutron/neutron.conf | grep -v ^$ | grep -v ^#
[DEFAULT]
core_plugin
=neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2
rpc_backend = neutron.openstack.common.rpc.impl_qpid
control_exchange = neutron
qpid_hostname = 192.169.142.49
auth_strategy = keystone
allow_overlapping_ips = True
dhcp_lease_duration = 120
allow_bulk = True
qpid_port = 5672
qpid_heartbeat = 60
qpid_protocol = tcp
qpid_tcp_nodelay = True
qpid_reconnect_limit=0
qpid_reconnect_interval_max=0
qpid_reconnect_timeout=0
qpid_reconnect=True
qpid_reconnect_interval_min=0
qpid_reconnect_interval=0
debug = False
verbose = False
[quotas]
[agent]
[keystone_authtoken]
admin_tenant_name = services
admin_user = neutron
admin_password = fedora
auth_host = 192.169.142.49
auth_port = 35357
auth_protocol = http
auth_uri=http://192.169.142.49:5000/
[database]
[service_providers]
[AGENT]
root_helper = sudo neutron-rootwrap /etc/neutron/rootwrap.conf
2. (OVS) plugin.ini
-------------------
$ cat /etc/neutron/plugin.ini | grep -v ^$ | grep -v ^#
[ovs]
tenant_network_type = gre
tunnel_id_ranges = 1:1000
enable_tunneling = True
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 192.169.142.49
[agent]
[securitygroup]
[DATABASE]
sql_connection = mysql://neutron:fedora@node1-controller/ovs_neutron
sql_max_retries=10
reconnect_interval=2
sql_idle_timeout=3600
[SECURITYGROUP]
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
3. dhcp_agent.ini
-----------------
$ cat /etc/neutron/dhcp_agent.ini | grep -v ^$ | grep -v ^#
[DEFAULT]
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
handle_internal_only_routers = TRUE
external_network_bridge = br-ex
use_namespaces = True
dnsmasq_config_file = /etc/neutron/dnsmasq.conf
4. l3_agent.ini
---------------
$ cat /etc/neutron/dhcp_agent.ini | grep -v ^$ | grep -v ^#
[DEFAULT]
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
handle_internal_only_routers = TRUE
external_network_bridge = br-ex
use_namespaces = True
dnsmasq_config_file = /etc/neutron/dnsmasq.conf
5. dnsmasq.conf
---------------
This logs dnsmasq output is to a file, instead of journalctl):
$ cat /etc/neutron/dnsmasq.conf | grep -v ^$ | grep -v ^#
log-facility = /var/log/neutron/dnsmasq.log
log-dhcp
6. api-paste.ini
----------------
$ cat /etc/neutron/api-paste.ini | grep -v ^$ | grep -v ^#
[composite:neutron]
use = egg:Paste#urlmap
/: neutronversions
/v2.0: neutronapi_v2_0
[composite:neutronapi_v2_0]
use = call:neutron.auth:pipeline_factory
noauth = extensions neutronapiapp_v2_0
keystone = authtoken keystonecontext extensions neutronapiapp_v2_0
[filter:keystonecontext]
paste.filter_factory = neutron.auth:NeutronKeystoneContext.factory
[filter:authtoken]
paste.filter_factory =
keystoneclient.middleware.auth_token:filter_factory
admin_user=neutron
auth_port=35357
admin_password=fedora
auth_protocol=http
auth_uri=http://192.169.142.49:5000/
admin_tenant_name=services
auth_host = 192.169.142.49
[filter:extensions]
paste.filter_factory =
neutron.api.extensions:plugin_aware_extension_middleware_factory
[app:neutronversions]
paste.app_factory = neutron.api.versions:Versions.factory
[app:neutronapiapp_v2_0]
paste.app_factory = neutron.api.v2.router:APIRouter.factory
7. metadata_agent.ini
---------------------
$ cat /etc/neutron/metadata_agent.ini | grep -v ^$ | grep -v ^#
[DEFAULT]
auth_url = http://192.169.142.49:35357/v2.0/
auth_region = regionOne
admin_tenant_name = services
admin_user = neutron
admin_password = fedora
nova_metadata_ip = 192.168.142.49
nova_metadata_port = 8775
metadata_proxy_shared_secret = fedora
Compute node Neutron configurations
===================================
1. neutron.conf
---------------
$ cat /etc/neutron/neutron.conf | grep -v ^$ | grep -v ^#
[DEFAULT]
core_plugin
=neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2
rpc_backend = neutron.openstack.common.rpc.impl_qpid
qpid_hostname = 192.169.142.49
auth_strategy = keystone
allow_overlapping_ips = True
qpid_port = 5672
debug = True
verbose = True
[quotas]
[agent]
[keystone_authtoken]
admin_tenant_name = services
admin_user = neutron
admin_password = fedora
auth_host = 192.169.142.49
[database]
[service_providers]
[AGENT]
root_helper = sudo neutron-rootwrap /etc/neutron/rootwrap.conf
2. (OVS) plugin.ini
-------------------
$ cat plugin.ini | grep -v ^$ | grep -v ^#
[ovs]
tenant_network_type = gre
tunnel_id_ranges = 1:1000
enable_tunneling = True
integration_bridge = br-int
tunnel_bridge = br-tun
local_ip = 192.169.142.57
[DATABASE]
sql_connection = mysql://neutron:fedora@node1-controller/ovs_neutron
[SECURITYGROUP]
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[agent]
[securitygroup]
3. metadata_agent.ini
---------------------
$ cat metadata_agent.ini | grep -v ^$ | grep -v ^#
[DEFAULT]
auth_url = http://localhost:5000/v2.0
auth_region = RegionOne
admin_tenant_name = %SERVICE_TENANT_NAME%
admin_user = %SERVICE_USER%
admin_password = %SERVICE_PASSWORD%
iptables rules on both Controller and Compute nodes
===================================================
iptables on Controller node
---------------------------
$ cat /etc/sysconfig/iptables
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m multiport --dports 3260 -m comment --comment "001
cinder incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 80 -m comment --comment "001
horizon incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 9292 -m comment --comment "001
glance incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 5000,35357 -m comment
--comment "001 keystone incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 3306 -m comment --comment "001
mariadb incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 6080 -m comment --comment "001
novncproxy incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 8770:8780 -m comment --comment
"001 novaapi incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 9696 -m comment --comment "001
neutron incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 5672 -m comment --comment "001
qpid incoming" -j ACCEPT
-A INPUT -p tcp -m multiport --dports 8700 -m comment --comment "001
metadata incoming" -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5999 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A INPUT -p gre -j ACCEPT
-A OUTPUT -p gre -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
iptables on Compute node
------------------------
$ cat /etc/sysconfig/iptables
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5999 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -p gre -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A OUTPUT -p gre -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
[1] Also here --
http://kashyapc.fedorapeople.org/virt/openstack/neutron-configs-GRE-OVS-t...
--
/kashyap
10 years, 2 months
[Rdo-list] Creating rpms for Tempest
by David Kranz
There has been a lot of interest in running tempest against real RDO
clusters. Having an rpm would make that a lot easier. There are several
issues peculiar to tempest that need to be resolved.
1. The way tempest configures itself and does test discovery depends
heavily on the tests being run from a directory containing the tests.
2. Unlike OpenStack python client libraries, tempest changes from
release to release in incompatible ways, so you need "havana tempest" to
test a havana cluster and an "icehouse tempest" to test icehouse.
The tempest group has little interest in changing either of these
behaviors. Additionally, it would be desirable if a tempest user could
install tempest rpms to test different RDO versions on the same machine.
Here is a proposal for how this could work and what the user experience
would be.
Dealing with these tempest issues suggests that the the tempest code
should be copied to /var/lib/tempest/{4.0,5.0, etc.} and the user should
configure a separate directory for each OpenStack cluster to be tested.
Each directory needs to contain:
.testr.conf
an etc directory containing the tempest.conf and logging.conf files
a symlink to the tempest test modules for the appropriate version
a copy of the test run scripts that are in the tools directory of tempest
To help the user create such directories, there should be a global
executable "configure-tempest-directory" that takes an optional version.
If multiple versions are present in /var/lib/tempest and no version is
specified then the user will be asked which version to configure.
User experience:
1. Install tempest rpm: yum install tempest-4.0
2. Run configure-tempest-directory
3. Make changes to tempest.conf to match the cluster being tested (and
possibly logging.conf and .testr.conf as well)
4. Run tempest with desired test selection using
tools/pretty_tox_serial.sh or tools/ pretty_tox_serial
Does any one have any comments/suggestions about this?
-David
10 years, 2 months
[Rdo-list] Weekly RDO meeting minutes -- 2014-02-11
by Mike Burns
Minutes:
http://meetbot.fedoraproject.org/rdo/2014-02-11/rdo.2014-02-11-14.02.html
Minutes (text):
http://meetbot.fedoraproject.org/rdo/2014-02-11/rdo.2014-02-11-14.02.txt
Log:
http://meetbot.fedoraproject.org/rdo/2014-02-11/rdo.2014-02-11-14.02.log....
========================
#rdo: RDO weekly meeting
========================
Meeting started by mburned at 14:02:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/rdo/2014-02-11/rdo.2014-02-11-14.02.log....
.
Meeting summary
---------------
* LINK: https://etherpad.openstack.org/p/rdo_community_manager_sync
(rbowen, 14:02:17)
* agenda (mburned, 14:02:29)
* LINK: https://etherpad.openstack.org/p/rdo_community_manager_sync
(mburned, 14:02:36)
* Test Day (mburned, 14:04:58)
* test day was held Feb 4-5 (mburned, 14:05:16)
* LINK:
https://www.redhat.com/archives/rdo-list/2014-February/msg00034.html
(kashyap, 14:06:27)
* fair number of issues reported that are being triaged and handled
(mburned, 14:08:05)
* LINK:
https://www.redhat.com/archives/rdo-list/2014-February/msg00033.html
(mburned, 14:08:12)
* LINK:
https://www.redhat.com/archives/rdo-list/2014-February/msg00034.html
(mburned, 14:08:15)
* ACTION: rbowen will get the Fedora test day wiki page set up for the
M3 test day. (rbowen, 14:08:53)
* IDEA: for future releases, go to M1 and M3 for test day and skip M2
(too many test days, too quick cadence) (mburned, 14:19:39)
* debate on whether to do test day for final (mburned, 14:19:51)
* also should investigate fedora test day process more (mburned,
14:20:04)
* Icehouse M3 is 6-March (mburned, 14:20:21)
* tentatively set test day for March 18-19 (mburned, 14:20:49)
* Hangout (mburned, 14:21:42)
* LINK: http://openstack.redhat.com/Hangouts (mburned, 14:21:54)
* next scheduled for Feb 27 with larsks (mburned, 14:22:04)
* featuring a multinode setup demo (mburned, 14:22:20)
* rbowen will hopefully be scheduling a few more in the coming days
(mburned, 14:22:50)
* if you have a proposal or would like to volunteer, please see this
etherpad (mburned, 14:23:20)
* LINK: https://etherpad.openstack.org/p/rdo_hangouts (mburned,
14:23:24)
* or contact rbowen (mburned, 14:23:34)
* Newsletter (mburned, 14:23:52)
* February newsletter sent yesterday (was sent earlier to incorrect
list) (mburned, 14:24:12)
* topics for the march newsletter can be proposed here:
https://etherpad.openstack.org/p/rdo_mar_2014_newsletter (mburned,
14:24:36)
* Conference review (mburned, 14:25:19)
* FOSDEM Infrastructure.Next and Config Mgmt camp were held last week
(mburned, 14:25:38)
* rbowen interviewed Ohad about foreman, should be published soon
(mburned, 14:26:02)
* LINK:
https://www.redhat.com/archives/rdo-list/2014-February/msg00049.html
(mburned, 14:27:39)
* the newsletter ^^ (mburned, 14:27:48)
* good content on many topics (mburned, 14:28:41)
* iaas/cloud room was packed the entire time (mburned, 14:28:53)
* rbowen spoke at Infrastrucutre.next about ceilometer (mburned,
14:30:19)
* generated a lot of comments on what ceilometer is doing wrong
(mburned, 14:30:38)
* rbowen hoping to bring them into openstack community to help
improve (mburned, 14:31:08)
* ACTION: rbowen to summarize and post to rdo-list soon (mburned,
14:31:44)
* printed RDO materials unfortunately did not show up, plans underway
to fix this in the future (mburned, 14:35:55)
* Upcoming events (mburned, 14:36:13)
* SCALE will be held next weeking in LA, RDO will have a table
(mburned, 14:36:58)
* also another Infrastructure.Next event (rbowen will present a
re-written ceilometer talk there) (mburned, 14:37:41)
* if you will be in attendance and are will to help with the RDO
table, please contact rbowen (mburned, 14:38:01)
* ACTION: rbowen to update http://openstack.redhat.com/Events
(mburned, 14:39:45)
* ACTION: rbowen and mburned to review list of upcoming "cloud"
events, and talk next week about where we might want to have a
presence. (rbowen, 14:41:10)
* CentOS Cloud SIG (mburned, 14:41:58)
* not much action in the last week or 2 on this (mburned, 14:42:09)
* mburned meeting with kbsingh this week to start really driving this
forward (mburned, 14:42:29)
* mburned has been asked to a driving role in the SIG (mburned,
14:42:49)
* should have more updates next week (mburned, 14:43:05)
* Cloud Instance SIG is also up and running and mburned will be
participating there as well (mburned, 14:43:39)
* Cloud Instance is about generating centos images for use in a cloud
infrastructure (mburned, 14:44:15)
* Bug Triage (mburned, 14:44:22)
* next scheduled one is Feb 19 (mburned, 14:44:35)
* Forum questions (mburned, 14:45:29)
* currently 35 unanswered posts (mburned, 14:46:08)
* need to start driving that down (mburned, 14:46:14)
* test day structure (revisited) (mburned, 14:49:17)
* we currently loosely use the Fedora test day structure (mburned,
14:49:32)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2013-10-08_Virtualization
(mburned, 14:49:39)
* nothing radically new (mburned, 14:49:45)
Meeting ended at 15:00:31 UTC.
Action Items
------------
* rbowen will get the Fedora test day wiki page set up for the M3 test
day.
* rbowen to summarize and post to rdo-list soon
* rbowen to update http://openstack.redhat.com/Events
* rbowen and mburned to review list of upcoming "cloud" events, and talk
next week about where we might want to have a presence.
Action Items, by person
-----------------------
* mburned
* rbowen and mburned to review list of upcoming "cloud" events, and
talk next week about where we might want to have a presence.
* rbowen
* rbowen will get the Fedora test day wiki page set up for the M3 test
day.
* rbowen to summarize and post to rdo-list soon
* rbowen to update http://openstack.redhat.com/Events
* rbowen and mburned to review list of upcoming "cloud" events, and
talk next week about where we might want to have a presence.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mburned (109)
* rbowen (91)
* kashyap (55)
* morazi (8)
* eggmaster (6)
* larsks (3)
* zodbot (3)
* pmyers (2)
* dneary (1)
* zsun (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 2 months
[Rdo-list] [Rdo-newsletter] February RDO Community Newsletter
by Rich Bowen
My apologies. I sent this last week, and addressed it to the wrong
place. So the first few paragraphs are somewhat out of date.
Thanks for being part of the RDO community!
Upcoming Conferences
This week I'm traveling in Belgium for FOSDEM and several other
nearby events. It's a busy few days.
FOSDEM - https://fosdem.org/2014/ - was in Brussels, Belgium, and
around 5000 attendees were expected to attended, including a good
contingent of the RDO and OpenStack community. There was a lot of
great OpenStack content, which you can see listed at
http://fnords.wordpress.com/2014/01/09/openstack-fosdem-14/
Immediately following FOSDEM, Config Management Camp is currently
ongoing in the nearby town of Ghent, February 3 and 4. That's where I
am right now, as I write this, You can read more about this event at
http://cfgmgmtcamp.eu/ Config Management Camp doesn't have content
directly about OpenStack, but of course Packstack is built on top of
Puppet, and you can also deploy RDO with The Foreman, and there's
a number of talks about both of those projects here.
Following Config Management Camp, Red Hat is sponsoring
Infrastructure.next, a one-day event - February 5 - around 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). You can see the
schedule of talks at http://lanyrd.com/2014/infranext/
Later in February, RDO will have a booth at SCALE - Southern
California Linux Expo. That's February 21-23, in Los Angeles. You can
find out more about SCALE at https://www.socallinuxexpo.org/scale12x
On the 21st - the first day of SCALE - Red Hat will be sponsoring
another Infrastructure.Next, where I'll be reprising my Ceilometer
talk, and there will again be a lot of great content for people
thinking about moving their services to a cloud infrastructure.
Other Upcoming Events
With the OpenStack Icehouse milestone 2 out on January 23rd, we'll be
conducting another RDO test day on February 4th and 5th to hammer out
any problems with this release. Find out more, and sign up to
participate, at
http://openstack.redhat.com/RDO_test_day_Icehouse_milestone_2
Derek Higgins will be presenting "Deploying OpenStack with Triple-O
and Tuskar" at the OpenStack France Meet-up in Paris on February
11th: http://www.meetup.com/OpenStack-France/events/161704432/
On Thusday, February 27th, Lars Kellogg-Stedman will be leading a
Google Hangout in which he will be doing a walk-through of a
multinode deployment with packstack.See
http://openstack.redhat.com/Hangouts#Upcoming_Hangouts for details of
this event, or follow us on Twitter (@rdocommunity) for a reminder
closer to the event.
CentOS Cloud SIG
In January, Red Hat announced new involvement in the CentOS project.
You can read more about that announcement at
http://www.redhat.com/about/news/press-archive/2014/1/red-hat-and-centos-...
On the heels of that announcement, OpenStack and other cloud
infrastructure projects have started talking about what this means
for us, and how we can create variants of CentOS that make it easier
to deploy these infrastructures.
This conversation is happening on the centos-devel mailing list (
http://lists.centos.org/mailman/listinfo/centos-devel ) so please
join that list if you want to participate in the effort. You can also
watch the "Office Hours" hangout at
http://www.youtube.com/watch?v=VKKYY_5SOWw in which members of the
various cloud infrastructure projects discuss the way forward in
creating a Cloud SIG (Special Interest Group) to produce these
variants and liveCD distributions.
IRC Meetings
We've started several regular IRC meetings, to move what we're doing
more into the public view.
The weekly community team meeting, which had been happening on the
phone, has moved to IRC. If you'd like to see what the community team
is up to, come to the #rdo channel on Freenode at 9am Eastern USA
time, each Tuesday. We also post a meeting summary to the rdo-list
mailing list ( http://www.redhat.com/mailman/listinfo/rdo-list ) for
anyone who can't make it to the meeting.
We've also started a bug triage meeting on IRC, in which we attempt
to at least assign all of the open bugs that nobody's working on yet.
The first of these was on Wednesday January 15th, and upcoming ones
will be announced on the rdo-list mailing list until we figure out
what the right cadence is for those meetings.
Community events like these are posted on the RDO Community Google
calendar. If you use Google Calendar, you can paste the following
into the entry box under "Other calendars" where it says "Add a
friend's calendar" -
6m0up994frfg2td6dpmubtn31s(a)group.calendar.google.com
If you use some other calendaring software, you can subscribe using the
ICS address:
http://www.google.com/calendar/ical/6m0up994frfg2td6dpmubtn31s%40group.ca...
OpenStack Foundation elections
The OpenStack foundation recently held elections for the board of
directors.
We'd like to extend a special congratulations to Mark McLoughlin who
was elected as an Individual Director. You can see the full board at
http://lists.openstack.org/pipermail/foundation/2014-January/001616.html
One of the cool things about OpenStack is that although the directors
represent various companies, they first represent OpenStack, and make
decisions that benefit the project and the foundation first, and
their companies come after. So we're proud that someone from the RDO
community is on the board, and we're thrilled that he considers the
well-being of the project to be the first priority.
In Closing
Thanks again for being part of the RDO community. We've hardly had a
moment to catch our breath this year, and it looks like the pace is
going to continue. So bring your friends and colleagues along to
share the work, and to help take this exciting technology to the next
level.
Once again, you can keep up with what's going by following us on
Twitter - @rdocommunity - or the rdo-list mailing list -
http://www.redhat.com/mailman/listinfo/rdo-list
--
Rich Bowen, for the RDO community
rbowen(a)redhat.com
http://openstack.redhat.com/
@rdocommunity
_______________________________________________
Rdo-newsletter mailing list
Rdo-newsletter(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-newsletter
10 years, 2 months
[Rdo-list] RDO test day (4,5-FEB-2014) -- IRC meeting minutes log
by Kashyap Chamarthy
================================
#rdo: RDO test day; 4,5-FEB-2014
================================
Thanks everyone for participating in the test days, here's the summary
(& URL to full logs) of IRC meeting minutes over the last 2 days.
Meeting started by kashyap at 07:57:42 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/rdo/2014-02-04/rdo-test-day-5feb2014.201...
.
Meeting summary
---------------
* RDO-test-day-5FEB2014 (kashyap, 07:58:11)
* LINK: https://etherpad.openstack.org/p/rdo_test_day_feb_2014
(kashyap, 08:52:00)
* LINK:
http://adam.younglogic.com/2013/07/troubleshooting-pki-middleware/
(kashyap, 09:11:04)
* To debug Neutron issues -- refer lines 7 to 13 here:
https://etherpad.openstack.org/p/rdo_test_day_feb_2014 (kashyap,
09:16:43)
* LINK: Workarounds page
http://openstack.redhat.com/Workarounds_2014_02 (kashyap, 10:36:42)
* LINK:
http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/epel-7/
??? (afazekas, 10:47:04)
* For all new workarounds, please add them here --
http://openstack.redhat.com/Workarounds_2014_02 (kashyap, 10:49:26)
* LINK: http://pastebin.com/ydPPezCg (ohochman, 11:38:47)
* LINK:
http://openstack.redhat.com/TestedSetups#Advanced_Installs_.28Foreman_Bas...
(jayg, 14:39:59)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1017210 (jayg,
14:40:06)
* LINK: http://titanpad.com/k3fUnioHQN (lon, 14:56:58)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1061045 (weshay,
15:05:58)
* LINK:
http://grokbase.com/p/gg/puppet-users/1387v5yek8/puppet-first-run-timing-out
(jayg, 15:59:32)
* LINK:
http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/epel-6/
I do not see new swift package for el6 (afazekas, 16:38:08)
* LINK:
http://docs.openstack.org/user-guide-admin/content/specify-host-to-boot-i...
(anand, 12:14:39)
* [Heads-up] There's a regression in libvirt F20 (_if_ you're using
polkit ACLS. Shouldn't affect the test day) --
https://bugzilla.redhat.com/show_bug.cgi?id=1058839 (kashyap,
14:03:58)
* LINK: http://pastebin.com/xUZJJG5a (ohochman, 15:08:17)
Meeting ended at 05:33:13 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* ohochman (110)
* kashyap (94)
* jayg (64)
* apevec (42)
* lon (40)
* rook (34)
* panda (33)
* ayoung (29)
* ukalifon (27)
* afazekas (22)
* yfried (21)
* psedlak (16)
* verdurin (15)
* larsks (14)
* mmagr (12)
* Pursuit[LT] (10)
* morazi (10)
* jistr (10)
* anand (7)
* nlevinki (7)
* beagles (7)
* giulivo (6)
* weshay (6)
* kitp (5)
* blinky_ghost (5)
* nmagnezi (5)
* mflobo (5)
* pixelb (5)
* yrabl (5)
* DG_ (4)
* mpavlase (4)
* ranjan (4)
* xqueralt (3)
* zodbot (3)
* defishguy (3)
* tshefi (2)
* oblaut (2)
* ajeain (1)
* eharney (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
/kashyap
10 years, 2 months
