[Rdo-list] OpenStack Summit booth
by Rich Bowen
For those that are going to OpenStack Summit, a few details about the
RDO booth.
The Red Hat booth at summit is divided in half, with one half being RDO
and other community things (oVirt, Atomic, Gluster, etc), and the other
half being Red Hat commercial products, especially Red Hat Enterprise
Linux OpenStack Platform.
On our end of the table, we have several people who have said that they
want to spend some time in the booth, and perhaps run various demos of
the stuff they've been working on.
If you're willing to spend some time in the booth, please let me or Mike
Burns know, so that we can have decent coverage. In particular, Monday
evening for the Booth Crawl is an important time to be sure we have
knowledgeable people at the booth to answer questions.
Thanks!
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years
[Rdo-list] Openstack-sahara broken on rhel6
by Dalmais Maxence
Hi,
The installation of Openstack-sahara on RHEL6 is broken while installing with RDO repositories.
Current available version is 2014.1.0-3.
Regarding the changelog , 2014.1.0-4 fix this : - Correcting bug with rhel6 init script
- Adding local variable for rhel6 tests
Currently EPEL testing use openstack-sahara-2014.1.0-6, while last version is openstack-sahara-2014.1.0-10
Do you have any plan to update quickly ?
Maxence
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
10 years
[Rdo-list] Open vSwitch issues....
by Erich Weiler
Hi Y'all,
I recently began rebuilding my OpenStack installation under the latest
RDO icehouse release (as of two days ago at least), and everything is
almost working, but I'm having issues with Open vSwitch, at least on the
compute nodes.
I'm use the ML2 plugin and VLAN tenant isolation. I have this in my
compute node's /etc/neutron/plugin.ini file
----------
[ovs]
bridge_mappings = physnet1:br-eth1
[ml2]
type_drivers = vlan
tenant_network_types = vlan
mechanism_drivers = openvswitch
[ml2_type_flat]
[ml2_type_vlan]
network_vlan_ranges = physnet1:200:209
----------
My switchports that the nodes connect to are configured as trunks,
allowing VLANs 200-209 to flow over them.
My network that the VMs should be connecting to is:
# neutron net-show cbse-net
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 23028b15-fb12-4a9f-9fba-02f165a52d44 |
| name | cbse-net |
| provider:network_type | vlan |
| provider:physical_network | physnet1 |
| provider:segmentation_id | 200 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | dd25433a-b21d-475d-91e4-156b00f25047 |
| tenant_id | 7c1980078e044cb08250f628cbe73d29 |
+---------------------------+--------------------------------------+
# neutron subnet-show dd25433a-b21d-475d-91e4-156b00f25047
+------------------+--------------------------------------------------+
| Field | Value |
+------------------+--------------------------------------------------+
| allocation_pools | {"start": "10.200.0.2", "end": "10.200.255.254"} |
| cidr | 10.200.0.0/16 |
| dns_nameservers | 121.43.52.1 |
| enable_dhcp | True |
| gateway_ip | 10.200.0.1 |
| host_routes | |
| id | dd25433a-b21d-475d-91e4-156b00f25047 |
| ip_version | 4 |
| name | |
| network_id | 23028b15-fb12-4a9f-9fba-02f165a52d44 |
| tenant_id | 7c1980078e044cb08250f628cbe73d29 |
+------------------+--------------------------------------------------+
So those VMs on that network should send packets that would be tagged
with VLAN 200.
I launch an instance, then look at the compute node with the instance on
it. It doesn't get a DHCP address, so it can't talk to the neutron node
with the dnsmasq server running on it. I configure the VM's interface
to be a static IP on VLAN200, 10.200.0.30, and netmask 255.255.0.0. I
have another node set up on VLAN 200 on my switch to test with
(10.200.0.50) that is a real bare-metal server.
I can't ping my bare-metal server. I see the packets getting to eth1 on
my compute node, but stopping there. Then I figure out that the packets
are *not being tagged* for VLAN 200 as they leave the compute node!! So
the switch is dropping them. As a test I configure the switchport
with "native vlan 200", and voila, the ping works.
So, Open vSwitch is not getting that it needs to tag the packets for
VLAN 200. A little diagnostics on the compute node:
ovs-ofctl dump-flows br-int
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=966.803s, table=0, n_packets=0, n_bytes=0,
idle_age=966, priority=0 actions=NORMAL
Shouldn't that show some VLAN tagging?
and a tcpdump on eth1 on the compute node:
# tcpdump -e -n -vv -i eth1 | grep -i arp
tcpdump: WARNING: eth1: no IPv4 address assigned
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size
65535 bytes
11:21:50.462447 fa:16:3e:94:b3:63 > Broadcast, ethertype ARP (0x0806),
length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 10.200.0.50
tell 10.200.0.30, length 28
11:21:51.462968 fa:16:3e:94:b3:63 > Broadcast, ethertype ARP (0x0806),
length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 10.200.0.50
tell 10.200.0.30, length 28
11:21:52.462330 fa:16:3e:94:b3:63 > Broadcast, ethertype ARP (0x0806),
length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 10.200.0.50
tell 10.200.0.30, length 28
11:21:53.462311 fa:16:3e:94:b3:63 > Broadcast, ethertype ARP (0x0806),
length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 10.200.0.50
tell 10.200.0.30, length 28
11:21:54.463169 fa:16:3e:94:b3:63 > Broadcast, ethertype ARP (0x0806),
length 42: Ethernet (len 6), IPv4 (len 4), Request who-has 10.200.0.50
tell 10.200.0.30, length 28
That tcpdump also confirms the ARP packets are not being tagged 200 as
they leave the physical interface.
This worked before when I was testing icehouse RC1, I don't know what
changed with Open vSwitch... Anyone have any ideas?
Thanks as always for the help!! This list has been very helpful.
cheers,
erich
10 years
[Rdo-list] [Rdo-newsletter] RDO Community Newsletter: May 2014
by Rich Bowen
Thanks for being part of the RDO community! Be sure to tell your
friends and colleagues to sign up, at
http://www.redhat.com/mailman/listinfo/rdo-newsletter
We'd also like to hear your thoughts on how we can improve the newsletter
in the coming months. There's a very quick survey (2-5 minutes) at
http://tm3.org/rdosurvey Thanks!
OpenStack Summit
Of course the big news in May is the OpenStack Summit, Juno edition,
which will take place in Atlanta Georgia in next week. You can see
the great lineup of talks and events at http://openstack.org/summit
and it's still not too late to register. You'll have the chance to
meet many of the RDO engineers, and attend 20+ talks by people from
the Red Hat OpenStack team - http://tm3.org/rdosummit
On Wednesday night, come have a drink on us at the World of Coca-Cola,
and rub elbows with the RDO team over hors d'oeuvres -
http://tm3.org/summitparty
And we'll be in the Red Hat booth all day, doing demos of RDO, as
well as Red Hat Enterprise Linux OpenStack Platform. Drop by for the
Booth Crawl on Monday evening to tell us what you're doing with
OpenStack.
LinuxCon Tokyo
On May 20-22, the week after the OpenStack Summit, we'll be in Tokyo for
LinuxCon Japan, Gluster Community Day, and CloudOpen Japan. Stop by
the Red Hat booth to find out about the Icehouse release of RDO, and what
coming in the Juno release later this year.
Icehouse Release
OpenStack Icehouse released on April 17th
http://openstack.org/icehouse/ - and it's better than ever, with 350
new features contributed by more than 1,200 developers from around
the world. To get started using OpenStack Icehouse today, go to the
RDO QuickStart page at http://openstack.redhat.com/Quickstart and
follow the steps. If you're already running an earlier version of
OpenStack, the upgrading doc at
http://openstack.redhat.com/Upgrading_RDO_To_Icehouse is the way to
go. (See
https://www.redhat.com/archives/rdo-list/2014-April/msg00105.html for
the more detailed list of what's in those packages.)
Over the coming months, we'll be hosting hangouts to talk about
what's new in Icehouse, and we started with a presentation by Steve
Baker about what's new in Heat. If you missed it, you can still watch
it at https://plus.google.com/u/1/events/ckhqrki6iepg12vkqk5vnt7ijd0
And in May, we're going to have a hangout about TripleO, and advances
in OpenStack's ease of installation and deployment. Follow us on
Twitter - @rdocommunity - to find out exact date and time
information.
New HowTos and Wiki Articles
The RDO engineers have been really busy the last few months working
on the Icehouse code. With the code freeze leading up to the release,
some of them had a moment to catch up on their writing, and we've
gotten some great content showing up in the weeks since the release.
The following new HowTo articles have been added to the RDO wiki:
* TripleO VM Setip - http://openstack.redhat.com/TripleO_VM_Setup
* Using MariDB+Galera Cluster with RDO Havana -
http://openstack.redhat.com/TripleO_VM_Setup
* Upgrading RDO To Icehouse -
http://openstack.redhat.com/Upgrading_RDO_To_Icehouse
* Deploying RDO using Instack -
http://openstack.redhat.com/Deploying_RDO_using_Instack
* Setting up High Availability -
http://openstack.redhat.com/Setting_up_High_Availability
If you're interested in contributing to the RDO documentation, just
roll up your sleeves and get started - It's a wiki. Register at
http://openstack.redhat.com/forum/entry/register and start writing.
Or, if you prefer to write it somewhere else, just drop me a note at
rbowen(a)redhat.com and we'll link to it.
Welcome Ceph!
Last week we announced that Red Hat has agreed to acquire Inktank, the
provider of the Ceph filesystem. You can read the full press release at
http://tm3.org/redhatinktank
RDO welcomes Ceph to the Red Hat storage family, and we're looking
forward to working more closely with the Ceph community in the coming
years.
Stay in Touch
Thanks for reading this far. We really want to know if the newsletter
is worth your time, whether you read it at all, and what we can do to
make it more useful. Please consider filling out the (very short!) survey
at http://tm3.org/rdosurvey to help us make it better. Thanks!
Meanwhile, the best ways to keep up with what's going on in the RDO
community are:
* Follow us on Twitter - http://twitter.com/rdocommunity
* Google+ - http://tm3.org/rdogplus
* rdo-list mailing list - http://www.redhat.com/mailman/listinfo/rdo-list
* This newsletter - http://www.redhat.com/mailman/listinfo/rdo-newsletter
Thanks again for being part of the RDO community!
--
Rich Bowen, for the RDO team
http://community.redhat.com/
_______________________________________________
Rdo-newsletter mailing list
Rdo-newsletter(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-newsletter
10 years
[Rdo-list] Glance problems...
by Erich Weiler
Hi Y'all,
I was able to set up RDO Openstack just fine with Icehouse RC1, and then
I wiped it out and am trying again with the official stable release
(2014.1) and am having weird problems. It seems there were many changes
between this and RC1 unless I'm mistaken.
The main issue I'm having now is that I can't seem to create the glance
database properly, and I was able to do this before no problem. I do:
$ mysql -u root -p
mysql> CREATE DATABASE glance;
mysql> GRANT ALL PRIVILEGES ON glance.* TO 'glance'@'localhost' \
IDENTIFIED BY 'GLANCE_DBPASS';
mysql> GRANT ALL PRIVILEGES ON glance.* TO 'glance'@'%' \
IDENTIFIED BY 'GLANCE_DBPASS';
(Obviously 'GLANCE_DBPASS' is replaced with the real password).
Then:
su -s /bin/sh -c "glance-manage db_sync" glance
And it creates the 'glance' database and only one table,
"migrate_version". I can't get it to create the rest of the tables it
needs. I've tried also:
openstack-db --init --service glance --password GLANCE_DBPASS
And that returned success but in reality nothing happened... Any idea
what's going on?
In the api.conf and registry.conf the correct database credentials are
listed, and I can connect to the database as the mysql glance user on
the command line just fine using those credentials.
When I run any glance commands I get this in the registry log:
ProgrammingError: (ProgrammingError) (1146, "Table 'glance.images'
doesn't exist") 'SELECT anon_1.anon_2_images_created_at AS
anon_1_anon_2_images_created_at, anon_1.anon_2_images_updated_at AS
anon_1_anon_2_images_updated_at, anon_1.anon_2_images_deleted_at AS
anon_1_anon_2_images_deleted_at, anon_1.anon_2_images_deleted AS
anon_1_anon_2_images_deleted, anon_1.anon_2_images_id AS
anon_1_anon_2_images_id, anon_1.anon_2_images_name AS
anon_1_anon_2_images_name, anon_1.anon_2_images_disk_format AS
anon_1_anon_2_images_disk_format, anon_1.anon_2_images_container_format
AS anon_1_anon_2_images_container_format, anon_1.anon_2_images_size AS
anon_1_anon_2_images_size, anon_1.anon_2_images_virtual_size AS
anon_1_anon_2_images_virtual_size, anon_1.anon_2_images_status AS
anon_1_anon_2_images_status, anon_1.anon_2_images_is_public AS
anon_1_anon_2_images_is_public, anon_1.anon_2_images_checksum AS
anon_1_anon_2_images_checksum, anon_1.anon_2_images_min_disk AS
anon_1_anon_2_images_min_disk, anon_1.anon_2_images_min_ram AS
anon_1_anon_2_images_min_ram, anon_1.anon_2_images_owner AS
anon_1_anon_2_images_owner, anon_1.anon_2_images_protected AS
anon_1_anon_2_images_protected, image_properties_1.created_at AS
image_properties_1_created_at, image_properties_1.updated_at AS
image_properties_1_updated_at, image_properties_1.deleted_at AS
image_properties_1_deleted_at, image_properties_1.deleted AS
image_properties_1_deleted, image_properties_1.id AS
image_properties_1_id, image_properties_1.image_id AS
image_properties_1_image_id, image_properties_1.name AS
image_properties_1_name, image_properties_1.value AS
image_properties_1_value, image_locations_1.created_at AS
image_locations_1_created_at, image_locations_1.updated_at AS
image_locations_1_updated_at, image_locations_1.deleted_at AS
image_locations_1_deleted_at, image_locations_1.deleted AS
image_locations_1_deleted, image_locations_1.id AS image_locations_1_id,
image_locations_1.image_id AS image_locations_1_image_id,
image_locations_1.value AS image_locations_1_value,
image_locations_1.meta_data AS image_locations_1_meta_data,
image_locations_1.status AS image_locations_1_status \nFROM (SELECT
anon_2.images_created_at AS anon_2_images_created_at,
anon_2.images_updated_at AS anon_2_images_updated_at,
anon_2.images_deleted_at AS anon_2_images_deleted_at,
anon_2.images_deleted AS anon_2_images_deleted, anon_2.images_id AS
anon_2_images_id, anon_2.images_name AS anon_2_images_name,
anon_2.images_disk_format AS anon_2_images_disk_format,
anon_2.images_container_format AS anon_2_images_container_format,
anon_2.images_size AS anon_2_images_size, anon_2.images_virtual_size AS
anon_2_images_virtual_size, anon_2.images_status AS
anon_2_images_status, anon_2.images_is_public AS
anon_2_images_is_public, anon_2.images_checksum AS
anon_2_images_checksum, anon_2.images_min_disk AS
anon_2_images_min_disk, anon_2.images_min_ram AS anon_2_images_min_ram,
anon_2.images_owner AS anon_2_images_owner, anon_2.images_protected AS
anon_2_images_protected \nFROM (SELECT images.created_at AS
images_created_at, images.updated_at AS images_updated_at,
images.deleted_at AS images_deleted_at, images.deleted AS
images_deleted, images.id AS images_id, images.name AS images_name,
images.disk_format AS images_disk_format, images.container_format AS
images_container_format, images.size AS images_size, images.virtual_size
AS images_virtual_size, images.status AS images_status, images.is_public
AS images_is_public, images.checksum AS images_checksum, images.min_disk
AS images_min_disk, images.min_ram AS images_min_ram, images.owner AS
images_owner, images.protected AS images_protected \nFROM images \nWHERE
images.deleted = %s AND images.status IN (%s, %s, %s, %s, %s) AND
images.is_public = %s UNION SELECT images.created_at AS
images_created_at, images.updated_at AS images_updated_at,
images.deleted_at AS images_deleted_at, images.deleted AS
images_deleted, images.id AS images_id, images.name AS images_name,
images.disk_format AS images_disk_format, images.container_format AS
images_container_format, images.size AS images_size, images.virtual_size
AS images_virtual_size, images.status AS images_status, images.is_public
AS images_is_public, images.checksum AS images_checksum, images.min_disk
AS images_min_disk, images.min_ram AS images_min_ram, images.owner AS
images_owner, images.protected AS images_protected \nFROM images \nWHERE
images.owner = %s AND images.deleted = %s AND images.status IN (%s, %s,
%s, %s, %s) UNION SELECT images.created_at AS images_created_at,
images.updated_at AS images_updated_at, images.deleted_at AS
images_deleted_at, images.deleted AS images_deleted, images.id AS
images_id, images.name AS images_name, images.disk_format AS
images_disk_format, images.container_format AS images_container_format,
images.size AS images_size, images.virtual_size AS images_virtual_size,
images.status AS images_status, images.is_public AS images_is_public,
images.checksum AS images_checksum, images.min_disk AS images_min_disk,
images.min_ram AS images_min_ram, images.owner AS images_owner,
images.protected AS images_protected \nFROM images INNER JOIN
image_members ON images.id = image_members.image_id \nWHERE
images.deleted = %s AND images.status IN (%s, %s, %s, %s, %s) AND
image_members.deleted = %s AND image_members.member = %s) AS anon_2
ORDER BY anon_2.images_name ASC, anon_2.images_created_at ASC,
anon_2.images_id ASC \n LIMIT %s) AS anon_1 LEFT OUTER JOIN
image_properties AS image_properties_1 ON anon_1.anon_2_images_id =
image_properties_1.image_id LEFT OUTER JOIN image_locations AS
image_locations_1 ON anon_1.anon_2_images_id =
image_locations_1.image_id ORDER BY anon_1.anon_2_images_name ASC,
anon_1.anon_2_images_created_at ASC, anon_1.anon_2_images_id ASC' (0,
'active', 'saving', 'queued', 'pending_delete', 'deleted', 1,
'7c1980078e044cb08250f628cbe73d29', 0, 'active', 'saving', 'queued',
'pending_delete', 'deleted', 0, 'active', 'saving', 'queued',
'pending_delete', 'deleted', 0, '7c1980078e044cb08250f628cbe73d29', 20)
Sure, enough, all the rest of the tables are missing from mysql so it
complains.
Also, I tried this:
keystone user-create --name=glance --pass=GLANCE_PASS --tenant=service
--email=glance(a)myco.com
exceptions must be old-style classes or derived from BaseException, not
NoneType (HTTP 400)
Creating the glance user was easy last time, now it doesn't work... Any
insight would be greatly appreciated!!
cheers,
erich
10 years
Re: [Rdo-list] RHEL 7 rc cloud guest image available
by Arash Kaffamanesh
Sorry Rich, I wrote inadvertently to your redhat email.
The atomic image works now (I deleted the image and added it again to
glance and it worked suddenly).
But I'm still curious how to get docker running on RHEL 7 RC.
Thanks,
-Arash
On Thu, May 1, 2014 at 4:57 PM, Arash Kaffamanesh <ak(a)cloudssky.com> wrote:
> Rich, thanks for sharing!
>
> Just added the guest image to glance on RDO Havana and ran an instance
> successfully and thought I'd get docker pre installed on it and since that
> was not the case googled a bit and found this:
>
> https://access.redhat.com/site/discussions/734363
>
> It seems some kind of registration or pinging the TAM is required and
> since I've no TAM and don't know how to become one tried to test the atomic
> image here:
>
> http://www.projectatomic.io/download/
>
> and saw RDO is supported, yuppi :-)
>
> Added the image to glance with:
>
> glance add name="Atomic" is_public=true container_format=bare
> disk_format=qcow2 < 20140414.1.qcow2
>
> and got the error status after launching the instance.
>
> So now my question is: what is the right way to test docker on RHEL 7 or
> on an Atomic image on RDO?
>
> Thanks,
> -Arash
>
>
>
>
> On Tue, Apr 29, 2014 at 10:41 PM, Rich Bowen <rbowen(a)redhat.com> wrote:
>
>> FYI - RHEL 7 guest image available: ftp://ftp.redhat.com/redhat/
>> rhel/rc/7/GuestImage/
>>
>> --Rich
>>
>> --
>> Rich Bowen - rbowen(a)redhat.com
>> OpenStack Community Liaison
>> http://openstack.redhat.com/
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>
>
10 years