Re: [openstack-dev] [solum] Consistency of development environment
Hello Adrian, thanks for the quick reply, and sorry for my delayed response. On 09/03/2014 04:42 PM, Adrian Otto wrote: We have noticed lately that our devstack setup does not always work. [...] We have discussed ways to mitigate this. One idea was to select a particular devstack from a prior OpenStack release to help cut down on the rate of change. [...] We also considered additional functional tests for devstack to run when new code is submitted. I suppose we could run testing continuously in loops in attempts to detect non-determinism. [...] All of the above are opportunities for us to improve matters going forward. There are probably even better ideas we should consider as well. I'm currently toying with the following approach: Clone all necessary repos locally (staging repos), and configure devstack to use them (via GIT_BASE). At fixed intervals, automatically update the staging repos, and start the provisioning of a dev env. If that goes well, run the Solum tests with it. If that is also successful, the state in the staging repos gets pulled into a second set of local repos (setup repos), which I can use for actual dev env provisioning. If things fail, we could give it a couple of retries (for the non-determinism you mentioned), or just wait for the next interval. So there should (hopefully) always be a fairly recent and usable state in the setup repos. How well this works will mostly depend on the interval, I guess. I.e., the shorter the interval, the higher the chance for filtering out a usable state. Of course, if things get broken permanently, the state in the setup repos would no longer advance and we'd need to look into the cause and take actions (see example below). This approach doesn't really solve the root cause, but could make setting up a dev env a bit more reliable. I got the first part in place, i.e. provisioning from staging repos. I'll now experiment with the second part, and let you know. For now, we would like to help you get past the friction you are experiencing so you can get a working environment up. I could resolve the two problems I mentioned manually and get the dev env working. However, this brings up a question: after devstack provisioned OS, q-dhcp and q-l3 were not running. The former refused to start due to an updated version requirement for dnsmasq (see https://bugs.launchpad.net/openstack-manuals/+bug/1347153) that was not met This problem is also described here: http://netapp.github.io/openstack/2014/08/15/manila-devstack/ While I installed dnsmasq 2.63 manually, they used Ubuntu 14.04 to get around the problem. Is it maybe time to upgrade the base for the dev env to 14.04, or would that cause many other problems? Have you tried that out? If you have a pointer to an appropriate 14.04 image I can configure in Vagrant, I'd like to play with that a bit. Maybe that would also solve the problem with openvswitch. Kind regards, Alex ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [solum] Consistency of development environment
While I installed dnsmasq 2.63 manually, they used Ubuntu 14.04 to get around the problem. Is it maybe time to upgrade the base for the dev env to 14.04, or would that cause many other problems? Have you tried that out? If you have a pointer to an appropriate 14.04 image I can configure in Vagrant, I'd like to play with that a bit. Maybe that would also solve the problem with openvswitch. We have actually recently upgraded our Vagrant environment to 14.04 so if you pull from master from https://github.com/rackerlabs/vagrant-solum-dev you should get a working 14.04 instance. We couldn¹t upgrade to 14.04 as quickly as we hoped as there is a bug that we had to resolve with ubuntu system packages - https://bugs.launchpad.net/solum/+bug/1365679 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [solum] Consistency of development environment
Hello, I've been looking at Solum for about a couple of months now, with the goal of eventually contributing to this project. First off, my apologies if this is the wrong place for my question. I'm currently getting familiar with project structure, source code, and also trying to set up the dev env via Vagrant, following the Quick Start Guide: http://solum.readthedocs.org/en/latest/getting_started/ Here I need some advice. During my most recent attempt to set up the dev env two days ago, I hit two problems: after devstack provisioned OS, q-dhcp and q-l3 were not running. The former refused to start due to an updated version requirement for dnsmasq (see https://bugs.launchpad.net/openstack-manuals/+bug/1347153) that was not met, the latter did not start due to problems with openvswitch. I resolved both issues manually in the VM, all the while thinking that I must be doing something wrong. (Well I'm pretty sure I am.) On the other hand, I had similar problems getting the dev env up during earlier tries. So what is the right way to get a consistent setup of a Solum dev env? Are the instructions from the Quick Start guide linked above not current? Do I need to configure different branches/tags, or use different repos all together? Sorry again if this is the wrong place to ask! I hope I can make useful contributions soon. Regards, Alex ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [solum] Consistency of development environment
Alex, Thanks for your question, and for your interest in Solum. Our current dev environment setup relies on devstack to produce a working OpenStack environment for Solum to run within. We have noticed lately that our devstack setup does not always work. Because we are checking out devstack code from a repo that is frequently changing, and there are not unit tests for everything devstack can configure, sometimes it does not work. Also we have noticed that there may be some things that devstack does that are not deterministic, so even if it does pass a test, there is no guarantee that it will work again if the same thing is repeated. Sometimes it is hard to tell if the problem is Solum, or devstack. We have discussed ways to mitigate this. One idea was to select a particular devstack from a prior OpenStack release to help cut down on the rate of change. We also considered additional functional tests for devstack to run when new code is submitted. I suppose we could run testing continuously in loops in attempts to detect non-determinism. All of the above are opportunities for us to improve matters going forward. There are probably even better ideas we should consider as well. For now, we would like to help you get past the friction you are experiencing so you can get a working environment up. I suggest finding us in #solum on Freenode IRC, and let's try to sort through it. Thanks, Adrian Otto Original message From: Alexander Vollschwitz Date:09/03/2014 4:33 AM (GMT-08:00) To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [solum] Consistency of development environment Hello, I've been looking at Solum for about a couple of months now, with the goal of eventually contributing to this project. First off, my apologies if this is the wrong place for my question. I'm currently getting familiar with project structure, source code, and also trying to set up the dev env via Vagrant, following the Quick Start Guide: http://solum.readthedocs.org/en/latest/getting_started/ Here I need some advice. During my most recent attempt to set up the dev env two days ago, I hit two problems: after devstack provisioned OS, q-dhcp and q-l3 were not running. The former refused to start due to an updated version requirement for dnsmasq (see https://bugs.launchpad.net/openstack-manuals/+bug/1347153) that was not met, the latter did not start due to problems with openvswitch. I resolved both issues manually in the VM, all the while thinking that I must be doing something wrong. (Well I'm pretty sure I am.) On the other hand, I had similar problems getting the dev env up during earlier tries. So what is the right way to get a consistent setup of a Solum dev env? Are the instructions from the Quick Start guide linked above not current? Do I need to configure different branches/tags, or use different repos all together? Sorry again if this is the wrong place to ask! I hope I can make useful contributions soon. Regards, Alex ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
