[one-users] [Docs] Problem with OpenVSwitch and some questions about Ceph
Jon
three18ti at gmail.com
Mon Apr 8 11:55:09 PDT 2013
Hello All,
So I'm a bit stumped, is this actaully a bug in OpenNebula or is the issue
more localized (e.g. PEBCK)?
I'm not finding anywhere where I've deviated from the instructions, but
that doesn't mean that I've inadvertently screwed something up.
Where else should I be looking?
Thanks,
Jon A
On Mon, Apr 1, 2013 at 7:48 PM, Jon <three18ti at gmail.com> wrote:
> Hello,
>
> I know that previous versions of opennebula required openvswitch-brcompat
>
> >>
> http://opennebula.org/documentation:rel3.8:openvswitch#hosts_configuration
>
> but the 4.0 docs seem to indicate that with KVM brcompat is not required:
>
> >>
> http://opennebula.org/documentation:rel4.0:openvswitch#ovswitch_and_ovswitch_brcompat
>
> Anyway, I did install the openvswitch-brcompat package, but got the same
> error.
> (looking at the docs now, it seems that you have to tell the OpenNebula to
> use a different openvswitch driver,
> specifically openvswitch_brcompat, so I think this test may have been
> incomplete)
>
> Then I attempted to run the ovs command at the command line, when I do so,
> I get the following error:
>
> >> root at loki:~# sudo /usr/bin/ovs-ofctl add-flow ovsbr0
> in_port=,dl_src=02:00:44:47:83:44,priority=40000,actions=normal
> >> ovs-ofctl: dl_src=02:00:44:47:83:44: bad syntax for in_port
>
> I think this might be the root cause of the issue? Where is "in_port"
> defined?
> I don't see it in the onevnet template, but that doesn't mean I didn't
> just miss it.
>
> One other question I had while going through the docs again, I see on the
> openvswitch page:
>
> >> The sudoers file must be configured so oneadmin can execute ovs_vsctl
> in the hosts.
>
> How do you recommend doing this? I thought the oneadmin was set up to
> execute commands with sudo when installing the packages...
> I didn't see the oneadmin user in any of the sudo groups (sudoers, wheel,
> root) so I added the
>
> I did add the oneadmin user to the sudo group also without any success:
>
> >> root at loki:~# addgroup oneadmin sudo
> >> Adding user `oneadmin' to group `sudo' ...
> >> Adding user oneadmin to group sudo
> >> Done.
>
> The only thing else I can think to do would be to set no passwords in the
> sudoers file:
>
> >> oneadmin ALL=NOPASSWD: ALL
>
> But this seems less than ideal. Also, I think the incorrect syntax is the
> root cause of the issue, if there are other issues.
>
> What steps can I try next?
>
> Thanks,
> Jon A
>
>
>
> On Thu, Mar 28, 2013 at 2:56 PM, Jaime Melis <jmelis at opennebula.org>wrote:
>
>> 3) Documentation
>>
>> The fact that install_novnc.sh is being installed to two separate
>> locations is a bug that has already been fixed.
>>
>> With regard to the "/usr/share/opennebula" issue, I'm afraid that's
>> because of the Debian/Ubuntu packaging policy. For other distros (CentOS
>> and openSUSE for example) the path is the one that appears in the
>> documentation.
>>
>> To makes things easier for users I think this should be reflected in the
>> README.debian file, and in the platform notes in the documentation. So
>> thanks a lot for pointing this out.
>>
>> I created this feature to follow this problem:
>> http://dev.opennebula.org/issues/1844
>>
>> cheers,
>> Jaime
>>
>> On Thu, Mar 28, 2013 at 1:06 PM, Jon <three18ti at gmail.com> wrote:
>>
>>> Hello All,
>>>
>>> I've just installed OpenNebula 3.9.80 and I have to say this is
>>> amazing. Everything works so smoothly.
>>>
>>> Anyway, down to business.
>>>
>>> OpenVSwitch:
>>>
>>> I've installed and configured OpenVSwitch and am able to manually add
>>> the OVS config using libvirt, then launch a VM,
>>>
>>> >> <interface type='bridge'>
>>> >> <source bridge='ovsbr0'/>
>>> >> <virtualport type='openvswitch'>
>>> >> </virtualport>
>>> >> <model type='virtio'/>
>>> >> <address type='pci' domain='0x0000' bus='0x00' slot='0x05'
>>> function='0x0'/>
>>> >> </interface>
>>>
>>> Which creates the device in ovs:
>>>
>>> >> system at ovsbr0:
>>> >> lookups: hit:1346333 missed:46007 lost:0
>>> >> flows: 8
>>> >> port 0: ovsbr0 (internal)
>>> >> port 1: eth0
>>> >> port 2: br0 (internal)
>>> >> port 7: vnet0
>>>
>>>
>>> However, when I attempt to create a virtual network without assigning
>>> an IP and instantiate the template I get the error:
>>>
>>> >> [TemplateInstantiate] Error allocating a new virtual machine. Cannot
>>> get IP/MAC lease from virtual network 0.
>>>
>>> The template of the virtual network is:
>>>
>>> >> oneadmin at loki:~$ onevnet show testnet1
>>> >> VIRTUAL NETWORK 0 INFORMATION
>>> >> ID : 0
>>> >> NAME : testnet1
>>> >> USER : oneadmin
>>> >> GROUP : oneadmin
>>> >> CLUSTER : -
>>> >> TYPE : FIXED
>>> >> BRIDGE : ovsbr0
>>> >> VLAN : No
>>> >> USED LEASES : 0
>>> >>
>>> >> PERMISSIONS
>>> >> OWNER : um-
>>> >> GROUP : ---
>>> >> OTHER : ---
>>> >>
>>> >> VIRTUAL NETWORK TEMPLATE
>>> >>
>>> >>
>>> >> VIRTUAL MACHINES
>>> >>
>>>
>>> If I add an IP to the vnet, I get the following template and error
>>> logs (full vm log attached, I think I've identified the relevant
>>> line):
>>>
>>> >> Thu Mar 28 10:34:05 2013 [VMM][E]: post: Command "sudo
>>> /usr/bin/ovs-ofctl add-flow ovsbr0
>>> in_port=,dl_src=02:00:44:47:83:43,priority=40000,actions=normal" failed.
>>>
>>> >> oneadmin at loki:~$ onevnet show testnet1
>>> >> VIRTUAL NETWORK 0 INFORMATION
>>> >> ID : 0
>>> >> NAME : testnet1
>>> >> USER : oneadmin
>>> >> GROUP : oneadmin
>>> >> CLUSTER : -
>>> >> TYPE : FIXED
>>> >> BRIDGE : ovsbr0
>>> >> VLAN : No
>>> >> USED LEASES : 1
>>> >>
>>> >> PERMISSIONS
>>> >> OWNER : um-
>>> >> GROUP : ---
>>> >> OTHER : ---
>>> >>
>>> >> VIRTUAL NETWORK TEMPLATE
>>> >>
>>> >>
>>> >> USED LEASES
>>> >> LEASE=[ MAC="02:00:44:47:83:43", IP="192.168.0.2",
>>> IP6_LINK="fe80::400:44ff:fe47:8343", USED="1", VID="7" ]
>>> >>
>>> >> VIRTUAL MACHINES
>>> >>
>>> >> ID USER GROUP NAME STAT UCPU UMEM HOST
>>> TIME
>>> >> 7 oneadmin oneadmin template-4-7 fail 0 0K
>>> 0d 00h00
>>>
>>> >> root at loki:~# cat /var/log/openvswitch/ovs-vswitchd.log
>>> >> Mar 28 10:34:04|00081|bridge|INFO|created port vnet1 on bridge ovsbr0
>>> >> Mar 28 10:34:07|00082|netdev_linux|WARN|ethtool command ETHTOOL_GSET
>>> on network device vnet1 failed: No such device
>>> >> Mar 28 10:34:07|00083|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
>>> vnet1 device failed: No such device
>>> >> Mar 28 10:34:07|00084|netdev|WARN|failed to get flags for network
>>> device vnet1: No such device
>>> >> Mar 28 10:34:07|00085|netdev|WARN|failed to retrieve MTU for network
>>> device vnet1: No such device
>>> >> Mar 28 10:34:07|00086|netdev|WARN|failed to get flags for network
>>> device vnet1: No such device
>>> >> Mar 28 10:34:07|00087|bridge|INFO|destroyed port vnet1 on bridge
>>> ovsbr0
>>>
>>> I attempted to run the command but I never set a password for the
>>> oneadmin user, but I don't think it's a permissions / sudo access
>>> problem.
>>>
>>> Not really sure where to look next. Any ideas are appreciated.
>>>
>>> CEPH:
>>>
>>> I'm trying to use a Ceph datastore with a RBD instead of a cephFS
>>> (it's an option).
>>> When I try to create a Ceph datastore with a RBD type, I get a state
>>> of "Error",
>>> but I'm not sure where to look for relevant logs, oned.log didn't seem
>>> to have anything,
>>> or maybe I'm just grepping for the wrong string.
>>>
>>> As a work around, I have been creating the directory, creating the rbd
>>> then manually mounting it,
>>> this seems to work in my test environment, but doesn't seem very
>>> scalable, how are others using CEPH?
>>>
>>> Documentation:
>>>
>>> I've noticed some errors in the documentation, namely the location of
>>> the install scripts,
>>>
>>> The docs state they are in:
>>> >> /usr/share/one/install_gems
>>> >> /usr/share/one/sunstone/install_novnc.sh
>>>
>>> However, I found them in:
>>> >> /usr/share/opennebula/install_gems
>>> >> /usr/share/opennebula/install_novnc.sh
>>> >> /usr/share/opennebula/sunstone/install_novnc.sh
>>>
>>> Is there some repository of the documentation somewhere that we can
>>> contribute to?
>>> It's a small thing, but when I'm going through the instructions, I
>>> like to copy / paste;
>>> I figured it out, but I know if it caused me problems, it might cause
>>> others problems too.
>>>
>>> Thanks again, I can't wait for the final release of OpenNebula!
>>>
>>> Best Regards,
>>> Jon A
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>>
>> --
>> Jaime Melis
>> Project Engineer
>> OpenNebula - The Open Source Toolkit for Cloud Computing
>> www.OpenNebula.org | jmelis at opennebula.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130408/e0b82b25/attachment-0002.htm>
More information about the Users
mailing list