On Apr 11, 2012, at 12:28 AM, Dan Wendlandt wrote: > Tested with Essex release on Precise Beta2 using the OVS plugin. > > Would be great if someone with debian packaging experience could take a look > at this, as things currently seem pretty busted, though perhaps I'm doing > something wrong. > > Dan > > > root@ubuntu1:/etc/quantum/plugins/openvswitch# dpkg -l | grep quantum > ii python-quantum 2012.1-0ubuntu2 Quantum is a > virutal network service for Openstack. (python library) > ii python-quantumclient 2012.1-0ubuntu1 client - > Quantum is a virtual network service for Openstack > ii quantum-common 2012.1-0ubuntu2 common - > Quantum is a virtual network service for Openstack. > ii quantum-plugin-openvswitch 2012.1-0ubuntu2 Quantum is a > virtual network service for Openstack. (openvswitch plugin) > ii quantum-server 2012.1-0ubuntu2 server - > Quantum is a virtual network service for Openstack > > Here's a list of issues: > > Ran apt-get install quantum-server > > Could not install quantum-server > - chown: cannot access `/etc/quantum/' : No such file or directory > - chown: cannot access `/var/run/quantum/' : No such file or directory
I think these just need to be added to quantum-common.dirs file in the debian directory of the quantum package. If the proper process is to open a bug in launchpad against the quantum packaging I can go ahead and do that if it is not done already. -Ken > > Fixed this by making the directories manually > > - plugins.ini and quantum.conf should be copied from "etc" directory in > source to /etc/quantum . /etc/quantum is empty right now. > > - "service quantum-server start" doesn't work. No init scripts. > > - quantum-ryu-agent was installed in /usr/bin even though I didn't install > the ryu plugin. > > Ran apt-get install quantum-openvswitch-plugin > > - quantum-openvswitch-agent was installed into > /usr/bin/quantum-openvswitch-agent/quantum-openvswitch-agent, so it did not > show up in the path. > > - no logging to /var/log/quantum (at least server logging should go here, > ideally agents would have log as well) > > - mysql, python-mysqldb should be a dependency for the > quantum-openvswitch-plugin > > - I suspect agents should be separate packages from the main plugin packages. > Plugins correspond to code that is running on the main quantum controller > (i.e., the node running the API) . Agents run on each compute node, managing > the vswitch. > > - ovs quantum agent package should depend on python-mysqldb and > openvswitch-switch > > - ideally, agent would have init scripts as well. > > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira, Inc: www.nicira.com > twitter: danwendlandt > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
