linux/meta-cloud-services.git/meta-openstack/recipes-devtools/python/python-nova/websocketproxy-allow-empty-schemes-at-python-2.7.3.patch, branch wrynoseMirror of git.yoctoproject.org/meta-cloud-services.githttps://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=wrynose2018-04-09T14:48:37+00:00python-nova: uprev to latest openstack sable/pike release2018-04-09T14:48:37+00:00Mark Asselstinemark.asselstine@windriver.com2018-04-04T20:02:56+00:00urn:sha1:e7b4a0b965bb40861a487c13199755044919472a
This requires several new recipes and package uprevs (python-tooz,
python-os-brick, python-pypowervm, python-networkx,
python-microversion-parse, python-os-win, python-os-vif, and
python-os-traits). Along with updates to make things work with
systemd.
We also take steps to make setup/init use the directions from
https://docs.openstack.org/nova/pike/install/controller-install-ubuntu.html
After these changes we can validate that nova is operating nominally
using the command:
+-------+--------------------------------------+
| Name | UUID |
+-------+--------------------------------------+
| cell0 | 00000000-0000-0000-0000-000000000000 |
| cell1 | f547fa04-7c82-4498-95ee-210fc40abdb6 |
+-------+--------------------------------------+
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
nova: allow empty schemes at python 2.7.32014-11-05T17:11:39+00:00Bruce Ashfieldbruce.ashfield@windriver.com2014-11-05T17:11:39+00:00urn:sha1:ff7384602b97d6bf2e4588773fa9014d08a1db50
The upstream project is concerned with a bug in empty schemes with
2.7.3. But since Yocto is 2.7.3 and we get an empty scheme via websockify,
no VNC consoles are possible.
Rather than upreving python (big change), we aren't being hit by the
referenced bug, so we simply make sure that the condition can never
be true.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>