Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
by Walter Valenti
Yes, I've installed.
----- Messaggio originale -----
> Da: Yogev Rabl <yrabl(a)redhat.com>
> A: Walter Valenti <waltervalenti(a)yahoo.it>
> Cc:
> Inviato: Giovedì 15 Gennaio 2015 16:30
> Oggetto: Re: [Rdo-list] Problem with Cinder (Juno) and Ceph
>
> did you install ceph-common & python-ceph?
>
>
> ----- Original Message -----
>> From: "Walter Valenti" <waltervalenti(a)yahoo.it>
>> To: "Yogev Rabl" <yrabl(a)redhat.com>
>> Sent: Thursday, January 15, 2015 5:08:51 PM
>> Subject: Re: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph
>>
>> Yes, with enabled_backends = rbd,
>> Cinder-Volume tries to use Ceph, but now I've
>> got the following error:
>>
>> WARNING cinder.volume.manager [-] Unable to update volume replication
> status,
>> RBDDriver -1.1.0 (config name rbd) driver is uninitialized.
>>
>>
>>
>> Walter
>>
>>
>>
>>
>>
>>
>> ----- Messaggio originale -----
>> > Da: Yogev Rabl <yrabl(a)redhat.com>
>> > A: waltervalenti(a)yahoo.itYe
>> > Cc:
>> > Inviato: Giovedì 15 Gennaio 2015 14:18
>> > Oggetto: Fwd: [Rdo-list] Problem with Cinder (Juno) and Ceph
>> >
>> > Hi Walter,
>> >
>> > You this configuration is incorrect from what I know.
>> >
>> > try this:
>> >
>> > [DEFAULT]
>> >
>> > enabled_backends = rbd
>> >
>> > [rbd]
>> > volume_driver=cinder.volume.drivers.rbd.RBDDriver
>> > rbd_pool=volumes
>> > rbd_ceph_conf=etc/ceph/ceph.conf
>> > rbd_flatten_volume_from_snapshot=false
>> > rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf747
>> > rbd_max_clone_depth=5
>> > rbd_store_chunk_size=4
>> > rados_connect_timeout=-1
>> >
>> >
>> > In addition, I've just finish to write a small tool in python that
>> > configures Ceph in Openstack components configuration files (and set
> the
>> > pools +
>> > keyrings in the Ceph server).
>> > You can have a look at it in github:
>> > https://github.com/yorabl/Openstack-Ceph
>> >
>> > Good luck,
>> > Yogev Rabl
>> > Quality Engineer,
>> > RHOS storage
>> > Red Hat
>> >
>> >> ----- Forwarded Message -----
>> >> From: "Walter Valenti" <waltervalenti(a)yahoo.it>
>> >> To: rdo-list(a)redhat.com
>> >> Sent: Thursday, January 15, 2015 1:04:58 PM
>> >> Subject: [Rdo-list] Problem with Cinder (Juno) and Ceph
>> >>
>> >> Hi,
>> >> we're trying Juno with Ceph (Giant) integration on Centos7.
>> >>
>> >> The problem is that Cinder-Volume ignores, the directives
>> >> for use rbd protocol, but every uses LVM.
>> >>
>> >> This is our rbd configuration in cinder.conf:
>> >>
>> >> [DEFAULT]
>> >>
>> >> volume_driver=cinder.volume.drivers.rbd.RBDDriver
>> >> [rbd]
>> >> rbd_pool=volumes
>> >> rbd_user=cinder
>> >> rbd_ceph_conf=etc/ceph/ceph.conf
>> >> rbd_flatten_volume_from_snapshot=false
>> >> rbd_secret_uuid=ac94d7df-4271-4080-b1fd-8cf577bf7471
>> >> rbd_max_clone_depth=5
>> >> rbd_store_chunk_size=4
>> >> rados_connect_timeout=-1
>> >>
>> >> We also tried with all configuration in "rdb" section,
> and
>> >> with all configuration in DEFAULT section, but the problem is the
> same.
>> >>
>> >>
>> >> Any ideas??
>> >>
>> >> Thanks
>> >> Walter
>> >>
>> >> _______________________________________________
>> >> Rdo-list mailing list
>> >> Rdo-list(a)redhat.com
>> >> https://www.redhat.com/mailman/listinfo/rdo-list
>> >>
>> >
>>
>
9 years, 11 months
[Rdo-list] networking issues on JUNO redhead openstack.
by Ns, Rushi
Hi Support,
I have a problem that a launched instance from openstack cannot connect to SSH or PING
First of all I have dump question whether my system should be NOVA network or Neutron network. Well to keep everyone on the same page. Here is my history.
1. I did install RDO (allinone host) using the bellow steps https://openstack.redhat.com/Quickstart
2. Then I have used the following steps for floating IP https://openstack.redhat.com/Floating_IP_range.
My situtation is as follows.
* Floating IP address assignment:
I have assigned a floating IP , I did follow this steps.
https://openstack.redhat.com/Floating_IP_range
* Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it is eno1 name)is on the same bridge as the compute host
Yes, ethernet device on 10.48.146.78 address and br-ex interface on 10.48.146.112
* DHCP configuration: Yes, DHCP configuration is set and Neutron hearing and responding to DHCP
requests and the instance is getting IP from 10.48.146.113 (next hop) however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed
rule on default security group)
Here is the little diagram of my system.
[cid:EB813931-0B05-459C-A0B6-DE7C98D3D2FA]
Can someone help to find what is missing.
Best Regards,
Rushi.
Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race
9 years, 11 months
Re: [Rdo-list] networking issues on JUNO redhead openstack.
by Marius Cornea
As Kashyap kindly suggested we're not a support line and information here
should be available for all the community members. First, I don't see how
you can ping the br-ex IP address from an external network since it doesn't
contain any physical interface. Make sure that 10.48.146.112 isn't used by
other host on you network segment. You can do the following to remove the
ip address from the physical interface and add it to the br-ex bridge.
Please make sure that you've got console access to the server before doing
this as you may lose connectivity.
# ip addr del 10.48.146.77/24 dev eno1; ovs-vsctl add-port br-ex eno1
You should then follow the documentation[1] to recreate the public/tenant
networks and router. In your case FLOATING_IP_START, FLOATING_IP_END should
be part of the 10.48.146.0/24 network. Let's say you wish to allocate IP
addresses of the 10.48.146.200 - 10.48.146.210 range to your Openstack
routers/instances, then FLOATING_IP_START=10.48.146.200 and
FLOATING_IP_END=10.48.146.210. EXTERNAL_NETWORK_GATEWAY should be set to
what 'ip r | grep default | awk {'print $3'}' outputs
and EXTERNAL_NETWORK_CIDR is 10.48.146.0/24.
Note that the instance will get an IP address of the tenant network. By
assigning a floating IP you will be able to access it through an IP address
from your physical network segment.
[1]
http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_...
On Fri, Jan 9, 2015 at 10:52 PM, Ns, Rushi <rushi.ns(a)sap.com> wrote:
> Hi Marius,
>
> Here are the outputs. Is it possible to reach you on phone so that I can
> explain more than email. You can call me at 650 849 3915 or let me know
> your number.
>
> #ip a
>
> [root@lspal117 network-scripts(keystone_admin)]# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
> 1000
> link/ether d8:9d:67:29:c6:94 brd ff:ff:ff:ff:ff:ff
> inet 10.48.146.77/24 brd 10.48.146.255 scope global eno1
> valid_lft forever preferred_lft forever
> inet6 fe80::da9d:67ff:fe29:c694/64 scope link
> valid_lft forever preferred_lft forever
> 3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
> qlen 1000
> link/ether d8:9d:67:29:c6:95 brd ff:ff:ff:ff:ff:ff
> 4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
> qlen 1000
> link/ether d8:9d:67:29:c6:96 brd ff:ff:ff:ff:ff:ff
> 5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
> qlen 1000
> link/ether d8:9d:67:29:c6:97 brd ff:ff:ff:ff:ff:ff
> 6: ens1f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN qlen 1000
> link/ether 38:ea:a7:8f:bf:b4 brd ff:ff:ff:ff:ff:ff
> 7: ens1f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN qlen 1000
> link/ether 38:ea:a7:8f:bf:b5 brd ff:ff:ff:ff:ff:ff
> 8: ens2f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN qlen 1000
> link/ether 38:ea:a7:8f:bf:40 brd ff:ff:ff:ff:ff:ff
> 9: ens2f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN qlen 1000
> link/ether 38:ea:a7:8f:bf:41 brd ff:ff:ff:ff:ff:ff
> 10: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> link/ether 16:02:ac:3f:05:f4 brd ff:ff:ff:ff:ff:ff
> 11: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UNKNOWN
> link/ether be:8b:24:03:a9:47 brd ff:ff:ff:ff:ff:ff
> inet 10.48.146.112/24 brd 10.48.146.255 scope global br-ex
> valid_lft forever preferred_lft forever
> inet6 fe80::bc8b:24ff:fe03:a947/64 scope link
> valid_lft forever preferred_lft forever
> 12: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> link/ether 02:35:a4:7c:e5:4c brd ff:ff:ff:ff:ff:ff
> 16: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> link/ether fe:61:30:fb:a3:47 brd ff:ff:ff:ff:ff:ff
> 17: qbr63bd6704-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP
> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff
> inet6 fe80::3822:bcff:fe6a:b74f/64 scope link
> valid_lft forever preferred_lft forever
> 18: qvo63bd6704-47: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500
> qdisc pfifo_fast master ovs-system state UP qlen 1000
> link/ether a2:fe:04:5f:04:b4 brd ff:ff:ff:ff:ff:ff
> 19: qvb63bd6704-47: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500
> qdisc pfifo_fast master qbr63bd6704-47 state UP qlen 1000
> link/ether 8e:fe:6e:19:61:5c brd ff:ff:ff:ff:ff:ff
> 22: tap63bd6704-47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> pfifo_fast master qbr63bd6704-47 state UNKNOWN qlen 500
> link/ether fe:16:3e:d9:5e:ba brd ff:ff:ff:ff:ff:ff
> inet6 fe80::fc16:3eff:fed9:5eba/64 scope link
> valid_lft forever preferred_lft forever
>
> # ovs-vsctl show
>
> [root@lspal117 network-scripts(keystone_admin)]# ovs-vsctl show
> c5bcc161-86cd-4004-9729-c1ba05d28569
> Bridge br-ex
> Port br-ex
> Interface br-ex
> type: internal
> Port "qg-c3a1b534-36"
> Interface "qg-c3a1b534-36"
> type: internal
> Bridge br-int
> fail_mode: secure
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port "tape386c0cb-d8"
> tag: 1
> Interface "tape386c0cb-d8"
> type: internal
> Port br-int
> Interface br-int
> type: internal
> Port "qvo63bd6704-47"
> tag: 1
> Interface "qvo63bd6704-47"
> Port "tap44dd465f-d4"
> tag: 4095
> Interface "tap44dd465f-d4"
> type: internal
> Port "qr-e0ac3c25-2b"
> tag: 2
> Interface "qr-e0ac3c25-2b"
> type: internal
> Bridge br-tun
> Port br-tun
> Interface br-tun
> type: internal
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> ovs_version: “2.1.3"
>
> # neutron net-list
> [root@lspal117 network-scripts(keystone_admin)]# neutron net-list
>
> +--------------------------------------+---------+------------------------------------------------------+
> | id | name | subnets
> |
>
> +--------------------------------------+---------+------------------------------------------------------+
> | 5abe660b-52da-4d36-8275-4c1488df88b4 | public |
> 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a 172.24.4.224/28 |
> | d825e820-66e5-44b1-a91d-0c660aa822a5 | private |
> f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 10.0.0.0/24 |
> | 6eb6d123-8fec-4984-986a-5eeabf895883 | sap |
> ea2b21e0-bf9f-4195-b210-b75b6f9f7943 10.48.146.0/24 |
>
> +--------------------------------------+---------+------------------------------------------------------+
>
> # neutron subnet-list
> [root@lspal117 network-scripts(keystone_admin)]# neutron subnet-list
>
> +--------------------------------------+----------------+-----------------+----------------------------------------------------+
> | id | name | cidr
> | allocation_pools |
>
> +--------------------------------------+----------------+-----------------+----------------------------------------------------+
> | 79ee8c72-4c60-4b39-9b53-e6a3e9591e6a | public_subnet | 172.24.4.224/28
> | {"start": "172.24.4.226", "end": "172.24.4.238"} |
> | f0fc905d-ad3b-4ba6-8094-bf4dbbc55cd9 | private_subnet | 10.0.0.0/24
> | {"start": "10.0.0.2", "end": "10.0.0.254"} |
> | ea2b21e0-bf9f-4195-b210-b75b6f9f7943 | sap_local | 10.48.146.0/24
> | {"start": "10.48.146.112", "end": "10.48.146.120"} |
>
> +--------------------------------------+----------------+-----------------+——————————————————————————+
>
> #neutron router-list
> [root@lspal117 network-scripts(keystone_admin)]# neutron router-list
>
> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
> | id | name | external_gateway_info
>
>
> | distributed | ha |
>
> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
> | d6325c88-e5b0-448e-8ab1-af5908a189d4 | router1 | {"network_id":
> "5abe660b-52da-4d36-8275-4c1488df88b4", "enable_snat": true,
> "external_fixed_ips": [{"subnet_id":
> "79ee8c72-4c60-4b39-9b53-e6a3e9591e6a", "ip_address": "172.24.4.226"}]} |
> False | False |
>
> +--------------------------------------+---------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+———+
>
> In my system I have IP address for BR-ex and ENO1 (interface connecting
> ), should I disable eno1 as I can ping both (br-ex and eno1) from my
> network to reach to this host ? Probably its a dump question.
>
> Here are the outputs.
>
> br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 10.48.146.112 netmask 255.255.255.0 broadcast 10.48.146.255
> inet6 fe80::bc8b:24ff:fe03:a947 prefixlen 64 scopeid 0x20<link>
> ether be:8b:24:03:a9:47 txqueuelen 0 (Ethernet)
> RX packets 10 bytes 864 (864.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 25 bytes 3767 (3.6 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> br-int: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether 02:35:a4:7c:e5:4c txqueuelen 0 (Ethernet)
> RX packets 135 bytes 7574 (7.3 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> br-tun: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether fe:61:30:fb:a3:47 txqueuelen 0 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 10.48.146.77 netmask 255.255.255.0 broadcast 10.48.146.255
> inet6 fe80::da9d:67ff:fe29:c694 prefixlen 64 scopeid 0x20<link>
> ether d8:9d:67:29:c6:94 txqueuelen 1000 (Ethernet)
> RX packets 467319 bytes 48391354 (46.1 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 14794 bytes 5238733 (4.9 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 32
>
>
> Best Regards,
>
>
>
> Rushi.
>
> Success is not a matter of being the best & winning the race. Success is a
> matter of handling the worst & finishing the race
>
>
> From: Marius Cornea <marius(a)remote-lab.net>
> Date: Friday, January 9, 2015 at 1:46 PM
> To: SAP SAP <rushi.ns(a)sap.com>
> Subject: Re: [Rdo-list] networking issues on JUNO redhead openstack.
>
> Hi Rushi,
>
> Can you provide the output of the following commands on your node ?
>
> # ip a
> # ovs-vsctl show
> # neutron net-list
> # neutron subnet-list
> # neutron router-list
>
> Please note that only the br-ex bridge requires an IP address, the
> interface that's part of it shouldn't have one assigned. Also the floating
> IP addresses will be used for DNAT on the tenant router. You can check the
> documentation here[1] that describes the use of floating IPs.
>
> You can also check the upstream documentation[2] on how to create the
> networks.
>
> [1]
> https://openstack.redhat.com/Difference_between_Floating_IP_and_private_IP
> [2]
> http://docs.openstack.org/juno/install-guide/install/yum/content/neutron_...
>
>
> Tnx,
> Marius
>
> On Fri, Jan 9, 2015 at 10:22 PM, Ns, Rushi <rushi.ns(a)sap.com> wrote:
>
>> Hi Support,
>>
>> I have a problem that a launched instance from openstack cannot
>> connect to SSH or PING
>>
>> First of all I have dump question whether my system should be NOVA
>> network or Neutron network. Well to keep everyone on the same page. Here is
>> my history.
>>
>>
>> 1. I did install RDO (allinone host) using the bellow steps
>> https://openstack.redhat.com/Quickstart
>> 2. Then I have used the following steps for floating IP
>> https://openstack.redhat.com/Floating_IP_range.
>>
>> My situtation is as follows.
>> * Floating IP address assignment:
>> I have assigned a floating IP , I did follow this steps.
>> https://openstack.redhat.com/Floating_IP_range
>>
>> * Bridge configuration:My Ethernet device eth0(actually in Redhat 7 it
>> is eno1 name)is on the same bridge as the compute host
>> Yes, ethernet device on 10.48.146.78 address and br-ex interface on
>> 10.48.146.112
>>
>> * DHCP configuration: Yes, DHCP configuration is set and Neutron
>> hearing and responding to DHCP
>> requests and the instance is getting IP from 10.48.146.113 (next hop)
>> however I cannot ping/ssh to that IP address (ICMP/SSH is added allowed
>> rule on default security group)
>>
>> Here is the little diagram of my system.
>>
>> Can someone help to find what is missing.
>>
>>
>>
>> Best Regards,
>>
>>
>>
>> Rushi.
>>
>> Success is not a matter of being the best & winning the race. Success is
>> a matter of handling the worst & finishing the race
>>
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>>
>
9 years, 11 months
[Rdo-list] [meeting] RDO Packaging meeting minutes (2015-01-14)
by Haïkel
========================================
#rdo: RDO Packaging meeting (2015-01-15)
========================================
Meeting started by number80 at 15:00:44 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/rdo/2015-01-14/rdo.2015-01-14-15.00.log....
.
Meeting summary
---------------
* roll call (number80, 15:00:59)
* pending RDO updates (number80, 15:07:00)
* LINK: https://etherpad.openstack.org/p/RDO-Packaging (rbowen,
15:07:44)
* LINK: https://etherpad.openstack.org/p/RDO-Packaging (number80,
15:08:22)
* apevec will post update on what's in the queue until RDO CI goes
public (number80, 15:09:25)
* RDO CI: phase1: smoke test, phase2: full tempest run, and then there
is one more CI on the stage repo before pushing (apevec, 15:12:21)
* public trello board for tracking task (number80, 15:13:00)
* https://trello.com/b/HhXlqdiu/rdo (apevec, 15:13:14)
* EL6 Juno (number80, 15:15:03)
* ACTION: apevec moving forward the EL6/Juno discussion to the list
(number80, 15:19:04)
* ACTION: apevec contact RH Legal about patch sent through
mailing-list (number80, 15:20:55)
* LINK:
https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement
(number80, 15:24:03)
* rdopkg update CI public (number80, 15:29:21)
* ACTION: apevec eggmaster jruzicka to switch rdo-update.git to public
gerrit next week (apevec, 15:45:01)
* LINK: http://wiki.centos.org/QaWiki/PubHardware (number80,
15:49:28)
* Kilo milestone packages (number80, 15:50:26)
* ACTION: kbsingh to work with weshay to get rdo-ci access to a node
on ci.centos.org (rbowen, 15:54:28)
* ACTION: gchamoul to look at making Packstack working against
Delorean repo for Kilo snapshots (apevec, 15:55:59)
* public RDO call (number80, 15:57:26)
* ACTION: slinaber to start email thread describing current rdopkg CI
setup (eggmaster, 15:59:59)
* RDO irc weekly status will be every wednesday at 15:00 UTC on
#rdo@freenode (number80, 16:00:29)
* ACTION: apevec to post conf# details to try Bluejeans next week
(apevec, 16:00:50)
* open discussions (number80, 16:01:51)
Meeting ended at 16:03:43 UTC.
Action Items
------------
* apevec moving forward the EL6/Juno discussion to the list
* apevec contact RH Legal about patch sent through mailing-list
* apevec eggmaster jruzicka to switch rdo-update.git to public gerrit
next week
* kbsingh to work with weshay to get rdo-ci access to a node on
ci.centos.org
* gchamoul to look at making Packstack working against Delorean repo for
Kilo snapshots
* slinaber to start email thread describing current rdopkg CI setup
* apevec to post conf# details to try Bluejeans next week
Action Items, by person
-----------------------
* apevec
* apevec moving forward the EL6/Juno discussion to the list
* apevec contact RH Legal about patch sent through mailing-list
* apevec eggmaster jruzicka to switch rdo-update.git to public gerrit
next week
* apevec to post conf# details to try Bluejeans next week
* eggmaster
* apevec eggmaster jruzicka to switch rdo-update.git to public gerrit
next week
* gchamoul
* gchamoul to look at making Packstack working against Delorean repo
for Kilo snapshots
* jruzicka
* apevec eggmaster jruzicka to switch rdo-update.git to public gerrit
next week
* kbsingh
* kbsingh to work with weshay to get rdo-ci access to a node on
ci.centos.org
* weshay
* kbsingh to work with weshay to get rdo-ci access to a node on
ci.centos.org
* **UNASSIGNED**
* slinaber to start email thread describing current rdopkg CI setup
People Present (lines said)
---------------------------
* apevec (100)
* number80 (61)
* eggmaster (44)
* kashyap (26)
* weshay (25)
* rbowen (19)
* kbsingh (17)
* jruzicka (16)
* zodbot (12)
* gchamoul (7)
* mrunge (1)
* chandankumar (1)
* DV (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years, 11 months
[Rdo-list] RDO at the CentOS Dojo in Brussels, pre-FOSDEM
by Rich Bowen
In case you're not on the various CentOS mailing lists:
If you're coming to FOSDEM in a few weeks, you should make time to come
to the CentOS Dojo on Friday, where there will be, among other great
content, the following:
OpenStack Quickstart with RDO on CentOS :: Haïkel Guemar
CentOS Linux 7 is a great platform for running OpenStack and in this two
hour session we will introduce the basics of OpenStack and run through a
demo of installing !RDO ( http://openstack.redhat.com ) on CentOS Linux
7. The session will run in a tutorial format, so everyone with a laptop
in the audience will be able to join and implement their own OpenStack
in a VM. The focus will be on ensuring everyone has a basic setup, to
include:
Nova : The OpenStack Compute platform
Glance : The OpenStack image delivery service
Keystone : The OpenStack identity and authentication service
Horizon : The OpenStack Web based management interface
We will finish the session with a 15 min speaker session on how to get
involved with RDO development, packaging and testing and what the CentOS
Cloud SIG is doing in this area.
In order to run the tutorial on your machine, we recommend a VM on your
laptop that has 20GB+ of disk space, 2GB of ram and atleast 1 dedicated
cpu core. If your laptop has the ability to run nested-virt, please
enable that and use it. It will make a large difference to performance
of the overall setup. We would also like to request everyone to setup
these VMs ahead of time, in either KVM or Xen or any other
virtualisation technology you might use. A basic CentOS-7 minimal
install is sufficient to start from.
More details about the CentOS Dojo may be found at
http://wiki.centos.org/Events/Dojo/Brussels2015
We hope to see you there!
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
9 years, 11 months
[Rdo-list] [Manila] Don't see python-manilaclient package
by Deepak Shetty
Hi,
I installed RDO juno-1 (2 weeks back) on a 3-node setup.
I don't see the python-manilaclient package per the `yum search` i did,
hence cannot use Manila from command line. I don't think Manila is yet
integrated into horizon, so have to use manila cmdline to test the validity
of some of the glusterfs drivers that recently went into Manila
NOTE: manila specific packages were installed using `yum install ...` after
RDO 3 node setup was created. I understand that Manila is still a tech
preview/beta but i think manilaclient python package is missing.. Can
someone confirm pls ?
Below is some data from my setup:
==========================
[root@rhsdev1 ~]# yum search manila
Loaded plugins: fastestmirror, langpacks, priorities
Loading mirror speeds from cached hostfile
* base: mirror-fpt-telecom.fpt.net
* epel: mirror.nus.edu.sg
* extras: mirror.nbrc.ac.in
* updates: mirror.nbrc.ac.in
============================================================================================================
N/S matched: manila
============================================================================================================
openstack-manila.noarch : OpenStack Shared Filesystem Service
openstack-manila-doc.noarch : Documentation for OpenStack Shared Filesystem
Service
openstack-manila-share.noarch : An implementation of OpenStack Shared
Filesystem Service
python-manila.noarch : Python libraries for OpenStack Shared Filesystem
Service
[root@rhsdev1 ~]# rpm -qa| grep rdo
rubygem-rdoc-4.0.0-22.el7_0.noarch
rdo-release-juno-1.noarch
[root@rhsdev1 ~]# rpm -qa| grep cinder
python-cinderclient-1.1.1-1.el7.centos.noarch
openstack-cinder-2014.2.1-1.el7.centos.noarch
python-cinder-2014.2.1-1.el7.centos.noarch
[root@rhsdev1 ~]# rpm -qa| grep manila
openstack-manila-2014.2-0.3.el7.centos.noarch
python-manila-2014.2-0.3.el7.centos.noarch
openstack-manila-doc-2014.2-0.3.el7.centos.noarch
openstack-manila-share-2014.2-0.3.el7.centos.noarch
[root@rhsdev1 ~]# yum install python-manilaclient
Loaded plugins: fastestmirror, langpacks, priorities
Loading mirror speeds from cached hostfile
* base: mirror.nbrc.ac.in
* epel: mirror.nus.edu.sg
* extras: mirror.nbrc.ac.in
* updates: mirror.nbrc.ac.in
No package python-manilaclient available.
Error: Nothing to do
[root@rhsdev1 ~(keystone_admin)]# cinder list
+----+--------+--------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+----+--------+--------------+------+-------------+----------+-------------+
+----+--------+--------------+------+-------------+----------+-------------+
[root@rhsdev1 ~(keystone_admin)]# manila list
-bash: manila: command not found
[root@rhsdev1 ~(keystone_admin)]#
[root@rhsdev1 ~(keystone_admin)]# file /usr/bin/cinder
/usr/bin/cinder: Python script, ASCII text executable
[root@rhsdev1 ~(keystone_admin)]# file /usr/bin/manila
/usr/bin/manila: cannot open (No such file or directory)
[root@rhsdev1 ~(keystone_admin)]#
thanx,
deepak
9 years, 11 months
[Rdo-list] Hangouts: Request for speakers
by Rich Bowen
I'd like to start doing some hangouts in the coming months leading up to
Kilo, covering what we can expect to see coming in that release. If
you're willing to give a 30 minute (or more) presentation on a
particular OpenStack project, please let me know off-list, so that we
can begin to schedule these and begin to educate people on what they can
expect in April.
Thanks.
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
9 years, 11 months
