Re: [openstack-dev] [devstack] image create mysql error
Hi, Looks like the password supplied wasn't correct. Have you changed the pasword given in local.conf after a devstack installation? If yes, you need to purge mysql credentials stores in your machine. Regards, Vineet Menon On 1 December 2014 at 01:33, liuxinguo liuxin...@huawei.com wrote: When our CI run devstack, it occurs error when run “ image create mysql”. Log is pasted as following: 22186 2014-11-29 21:11:48.611 | ++ basename /opt/stack/new/devstack/files/mysql.qcow2 .qcow2 22187 2014-11-29 21:11:48.623 | + image_name=mysql 22188 2014-11-29 21:11:48.624 | + disk_format=qcow2 22189 2014-11-29 21:11:48.624 | + container_format=bare 22190 2014-11-29 21:11:48.624 | + is_arch ppc64 22191 2014-11-29 21:11:48.628 | ++ uname -m 22192 2014-11-29 21:11:48.710 | + [[ i686 == \p\p\c\6\4 ]] 22193 2014-11-29 21:11:48.710 | + '[' bare = bare ']' 22194 2014-11-29 21:11:48.710 | + '[' '' = zcat ']' 22195 2014-11-29 21:11:48.710 | + openstack --os-token 5387fe9c6f6d4182b09461fe232501db --os-url http://127.0.0.1:9292 image create mysql --public --container-format=bare --disk-format qcow2 22196 2014-11-29 21:11:57.275 | ERROR: openstack html 22197 2014-11-29 21:11:57.275 | head 22198 2014-11-29 21:11:57.275 | title401 Unauthorized/title 22199 2014-11-29 21:11:57.275 | /head 22200 2014-11-29 21:11:57.275 | body 22201 2014-11-29 21:11:57.275 | h1401 Unauthorized/h1 22202 2014-11-29 21:11:57.275 | This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.br /br / 22203 2014-11-29 21:11:57.275 | 22204 2014-11-29 21:11:57.276 | /body 22205 2014-11-29 21:11:57.276 | /html (HTTP 401) 22206 2014-11-29 21:11:57.344 | + exit_trap · Any one can give me some hint? · Thanks. ___ 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
Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'
Thanks Vladik for the reply. Jay Lau directed me to your patch. But what I don't get is.. Shouldn't NotImplementedException be removed? I mean, if other drivers are implementing set_host_enabled method, shouldn't libvirt also implement the same? Regards, Vineet Menon On 26 November 2014 at 16:07, Vladik Romanovsky vladik.romanov...@enovance.com wrote: - Original Message - From: Vineet Menon mvineetme...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Wednesday, 26 November, 2014 5:14:09 AM Subject: Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status' Hi Kevin, Oh. Yes. That could be the problem. Thanks for pointing that out. Regards, Vineet Menon On 26 November 2014 at 02:02, Chen CH Ji jiche...@cn.ibm.com wrote: are you using libvirt ? it's not implemented ,guess your bug are talking about other hypervisors? the message was printed here: http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/hosts.py#n236 Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC Vineet Menon ---11/26/2014 12:10:39 AM---Hi, I'm trying to reproduce the bug https://bugs.launchpad.net/nova/+bug/1259535 . From: Vineet Menon mvineetme...@gmail.com To: openstack-dev openstack-dev@lists.openstack.org Date: 11/26/2014 12:10 AM Subject: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status' Hi Vinet, There are two methods in the API for changing the service/host status. nova host-update and nova service-update. Currently, in order to disable the service one should use the nova service-update command, which maps to service_update method in the manager class. nova host-update maps to set_host_enabled() methodin the virt drivers, which is not implemented in the libvirt driver. Not sure what is the purpose of this method, but libvirt driver doesn't implement it. For a short period of time, this method was implemented, for a wrong reason, which was causing the bug in the title, however, it was fix with https://review.openstack.org/#/c/61016 Let me know if you have any questions. Thanks, Vladik Hi, I'm trying to reproduce the bug https://bugs.launchpad.net/nova/+bug/1259535 . While trying to issue the command, nova host-update --status disable machine1, an error is thrown saying, ERROR (HTTPNotImplemented): Virt driver does not implement host disabled status. (HTTP 501) (Request-ID: req-1f58feda-93af-42e0-b7b6-bcdd095f7d8c) What is this error about? Regards, Vineet Menon ___ 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 ___ 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
Re: [openstack-dev] Compute Node lost the net-connection after spawning vm
Please post the all the relevant files including local.conf. If you believe that it's a bug, then you can report a bug as well.. Regards, Vineet Menon On 27 November 2014 at 14:15, Aman Kumar amank3...@gmail.com wrote: Hi, I am using DevStack since 4 months and it was working fine but 2 days back i got some problem and i tried to re-install devstack by cloning it again from git, and it got successfully installed, my both compute node got up. After that i spawned vm from horizon, my spawned vm got ip and it is running successfully, but my compute node lost the net connection and i am not able to ssh that node from putty. I checked all the settings there is no problem in my VM setting i think there is some problem with devstack because i tried 5-6 times with my old setup and also with new vm configurations. every time only compute node is getting lost net connection but spawned vm will be running and also compute node will be enabled. can anyone please help me, thanks in advance Regards Aman Kumar HP Software India ___ 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
Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'
Hi Kevin, Oh. Yes. That could be the problem. Thanks for pointing that out. Regards, Vineet Menon On 26 November 2014 at 02:02, Chen CH Ji jiche...@cn.ibm.com wrote: are you using libvirt ? it's not implemented ,guess your bug are talking about other hypervisors? the message was printed here: http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/hosts.py#n236 Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC [image: Inactive hide details for Vineet Menon ---11/26/2014 12:10:39 AM---Hi, I'm trying to reproduce the bug https://bugs.launchpad.n]Vineet Menon ---11/26/2014 12:10:39 AM---Hi, I'm trying to reproduce the bug https://bugs.launchpad.net/nova/+bug/1259535. From: Vineet Menon mvineetme...@gmail.com To: openstack-dev openstack-dev@lists.openstack.org Date: 11/26/2014 12:10 AM Subject: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status' -- Hi, I'm trying to reproduce the bug *https://bugs.launchpad.net/nova/+bug/1259535* https://bugs.launchpad.net/nova/+bug/1259535. While trying to issue the command, nova host-update --status disable machine1, an error is thrown saying, ERROR (HTTPNotImplemented): Virt driver does not implement host disabled status. (HTTP 501) (Request-ID: req-1f58feda-93af-42e0-b7b6-bcdd095f7d8c) What is this error about? Regards, Vineet Menon ___ 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'
Hi, I'm trying to reproduce the bug https://bugs.launchpad.net/nova/+bug/1259535. While trying to issue the command, nova host-update --status disable machine1, an error is thrown saying, ERROR (HTTPNotImplemented): Virt driver does not implement host disabled status. (HTTP 501) (Request-ID: req-1f58feda-93af-42e0-b7b6-bcdd095f7d8c) What is this error about? Regards, Vineet Menon ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tempest] How to run tempest tests
Hi, Thanjs for clearing that up... I had a hard time understanding the screws before I went with testr. Regards, Vineet On 25 Nov 2014 17:46, Matthew Treinish mtrein...@kortar.org wrote: On Mon, Nov 24, 2014 at 10:49:27AM +0100, Angelo Matarazzo wrote: Sorry for my previous message with wrong subject Hi all, By reading the tempest documentation page [1] a user can run tempest tests by using whether testr or run_tempest.sh or tox. What is the best practice? run_tempest.sh has several options (e.g. ./run_tempest.sh -h) and it is my preferred way, currently. Any thought? So the options are there for different reasons and fit different purposes. The run_tempest.sh script exists mostly for legacy reasons as some people prefer to use it, and it predates the usage of tox in tempest. It also has some advantages like that it can run without a venv and provides some other options. Tox is what we use for gating, and we keep most of job definitions for gating in the tox.ini file. If you're trying to reproduce a gate run locally using tox is what is recommended to use. Personally I use it to run everything just because I often mix unit tests and tempest runs and I like having separate venvs for both being created on demand. Calling testr directly is just what all of these tools are doing under the covers, and it'll always be an option. One thing we're looking to do this cycle is to add a single entry point for running tempest which will hopefully clear up this confusion, and make the interface for interacting with tempest a bit nicer. When this work is done, the run_tempest.sh script will most likely disappear and tox will probably just be used for gating job definitions and just call the new entry-point instead of testr directly. BR, Angelo [1] http://docs.openstack.org/developer/tempest/overview.html#quickstart -Matt Treinish ___ 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
Re: [openstack-dev] [tempest] How to run tempest tests
Hi, I cannot comment on the best practice. But I can point to you a few more methods and links. 1. https://dague.net//presentations/tempest-101/#/ 2. http://www.slideshare.net/kamesh001/open-stack-qa-and-tempest?next_slideshow=1 3. https://docs.google.com/presentation/d/1M3XhAco_0u7NZQn3Gz53z9VOHHrkQBzEs5gt43ZvhOc/edit#slide=id.p Regards, Vineet Menon On 24 November 2014 at 10:49, Angelo Matarazzo angelo.matara...@dektech.com.au wrote: Sorry for my previous message with wrong subject Hi all, By reading the tempest documentation page [1] a user can run tempest tests by using whether testr or run_tempest.sh or tox. What is the best practice? run_tempest.sh has several options (e.g. ./run_tempest.sh -h) and it is my preferred way, currently. Any thought? BR, Angelo [1] http://docs.openstack.org/developer/tempest/overview.html#quickstart ___ 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
Re: [openstack-dev] Installing multinode(control node)--[any_updates]
HI, Are you trying to install devstack? or actual deployment version of openstack? Basically, control nodes need everything except n-cpu, AFAIK. Regards, Vineet Menon On 20 November 2014 08:55, Chhavi Kant/TVM/TCS chhavi.k...@tcs.com wrote: - Original Message - From: Chhavi Kant/TVM/TCS chhavi.k...@tcs.com To: openstack-dev@lists.openstack.org Sent: Wed, 19 Nov 2014 16:32:55 +0530 (IST) Subject: [openstack-dev] Installing multinode(control node) Hi, I want to install multinode in openstack, i need some guidence on what all are the services that i need to enable for installing control node. Attached is the localrc. -- Thanks Regards Chhavi Kant =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Thanks Regards Chhavi Kant ___ 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
[openstack-dev] Tempest basic
Hi, I'm trying to run a single tempest test on openstack but things aren't working as expected. My pwd is tempest root. This is what I'm trying to do, 'nosetests -v tempest.scenario.test_minimum_basic.py', but it throws error. I tried 'nosetests -v tempest/scenario/test_minimum_basic.py' as well, but again errors are being thrown. I'm following ' https://docs.google.com/presentation/d/1M3XhAco_0u7NZQn3Gz53z9VOHHrkQBzEs5gt43ZvhOc/edit#slide=id.gcc7522_3_13' presentation as guide. Regards, Vineet Menon ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova]Can't run tests
Hi, You should install mysql-dev for your distro using apt-get or yum. Regards, Vineet Menon On 18 November 2014 09:16, Eduard Matei eduard.ma...@cloudfounders.com wrote: Hi, I'm trying to run nova's unittests to validate some changes we made for a LibvirtVolumeDriver class, but i only got errors: with virtual env: ... Downloading/unpacking MySQL-python (from -r /opt/stack/nova/test-requirements.txt (line 13)) Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded Running setup.py (path:/opt/stack/nova/.venv/build/MySQL-python/setup.py) egg_info for package MySQL-python sh: 1: mysql_config: not found Traceback (most recent call last): File string, line 17, in module File /opt/stack/nova/.venv/build/MySQL-python/setup.py, line 17, in module metadata, options = get_config() File setup_posix.py, line 43, in get_config libs = mysql_config(libs_r) File setup_posix.py, line 25, in mysql_config raise EnvironmentError(%s not found % (mysql_config.path,)) EnvironmentError: mysql_config not found Complete output from command python setup.py egg_info: sh: 1: mysql_config: not found Traceback (most recent call last): File string, line 17, in module File /opt/stack/nova/.venv/build/MySQL-python/setup.py, line 17, in module metadata, options = get_config() File setup_posix.py, line 43, in get_config libs = mysql_config(libs_r) File setup_posix.py, line 25, in mysql_config raise EnvironmentError(%s not found % (mysql_config.path,)) EnvironmentError: mysql_config not found Cleaning up... Command python setup.py egg_info failed with error code 1 in /opt/stack/nova/.venv/build/MySQL-python Storing debug log for failure in /root/.pip/pip.log Command tools/with_venv.sh pip install --upgrade -r /opt/stack/nova/requirements.txt -r /opt/stack/nova/test-requirements.txt failed. None without virtual env: :/opt/stack/nova# ./run_tests.sh -N Running ` python -m nova.openstack.common.lockutils python setup.py testr --testr-args='--subunit --concurrency 0 '` Non-zero exit code (2) from test listing. error: testr failed (3) Ran 0 tests in 4.792s OK Running flake8 ... **WARNING**: Running flake8 without virtual env may miss OpenStack HACKING detection bash: flake8: command not found nova-manage --version 2014.2.1 Any idea how to fix this? Thanks, Eduard -- *Eduard Biceri Matei, Senior Software Developer* www.cloudfounders.com | eduard.ma...@cloudfounders.com *CloudFounders, The Private Cloud Software Company* Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee or an employee or agent responsible for delivering this message to the named addressee, you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this email in error we request you to notify us by reply e-mail and to delete all electronic files of the message. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the content of this message, and shall have no liability for any loss or damage suffered by the user, which arise as a result of e-mail transmission. ___ 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
Re: [openstack-dev] Devstack start
Hi Rim, Please share the local.conf file. Or if you don't have any special task to perform and want to install a plain vanilla devstack then use this as local.conf. [[local|localrc]] ADMIN_PASSWORD=secrete DATABASE_PASSWORD=$ADMIN_PASSWORD RABBIT_PASSWORD=$ADMIN_PASSWORD SERVICE_PASSWORD=$ADMIN_PASSWORD SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50 This is in accordance with minimal configuration as mentioned in http://docs.openstack.org/developer/devstack/configuration.html#minimal-configuration Regards, Vineet Menon On 6 November 2014 14:48, Rim Chol (rimc) r...@zhaw.ch wrote: Greetings! I am sending this email because I have some problems with starting the devstack. I cloned the devstack repository in my laptop and ran ./stack.sh in the devstack directory. But the konsole complains about that and some of the error messages are shown below. + screen -S stack -p g-api -X stuff '/usr/local/bin/glance-api --config-file=/etc/glance/glance-api.conf echo $! /opt/stack/status/stack/g-api.pid; fg || echo g-api failed to start | tee /opt/stack/s'atus/stack/g-api.failure + echo 'Waiting for g-api (160.85.231.43:9292) to start...' Waiting for g-api (160.85.231.43:9292) to start... + wait_for_service 60 http://160.85.231.43:9292 + local timeout=60 + local url=http://160.85.231.43:9292 + timeout 60 sh -c 'while ! curl -k --noproxy '\''*'\'' -s http://160.85.231.43:9292 /dev/null; do sleep 1; done' + die 317 'g-api did not start' + local exitcode=0 + set +o xtrace [Call Trace] ./stack.sh:1186:start_glance /home/chol/OpenStack/devstack/lib/glance:317:die [ERROR] /home/chol/OpenStack/devstack/lib/glance:317 g-api did not start Error on exit World dumping... see ./worlddump-2014-11-06-133528.txt for details\ I can not find any helpful materials on this over the Internet. Could anyone of you help me fix this? I would really appreciate your help Chol. ___ 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
[openstack-dev] Multi host devstack
Hi, Has anyone successfully installed devstack as multi-node setup using this tutorial? http://docs.openstack.org/developer/devstack/guides/multinode-lab.html I'm unable to do so. Regards, Vineet Menon ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Cells conversation starter
Hi Andrew, Since you have mentioned one approach to solve the flavor meta data to driver.spawn. I want to draw your attention to this code review thread as well, https://review.openstack.org/#/c/108238/. I didn't want to edit your etherpad notes, hence this email. Regards, Vineet Menon On 30 October 2014 22:08, Andrew Laski andrew.la...@rackspace.com wrote: I have written up some points on an etherpad to use during the summit session https://etherpad.openstack.org/p/kilo-nova-cells . Please read this over if possible before the session. There is an alternate approach to this work proposed and I expect we'll spend some time discussing it. If anyone would like to discuss it before then please reply here. On 10/20/2014 02:00 PM, Andrew Laski wrote: One of the big goals for the Kilo cycle by users and developers of the cells functionality within Nova is to get it to a point where it can be considered a first class citizen of Nova. Ultimately I think this comes down to getting it tested by default in Nova jobs, and making it easy for developers to work with. But there's a lot of work to get there. In order to raise awareness of this effort, and get the conversation started on a few things, I've summarized a little bit about cells and this effort below. Goals: Testing of a single cell setup in the gate. Feature parity. Make cells the default implementation. Developers write code once and it works for cells. Ultimately the goal is to improve maintainability of a large feature within the Nova code base. Feature gaps: Host aggregates Security groups Server groups Shortcomings: Flavor syncing This needs to be addressed now. Cells scheduling/rescheduling Instances can not currently move between cells These two won't affect the default one cell setup so they will be addressed later. What does cells do: Schedule an instance to a cell based on flavor slots available. Proxy API requests to the proper cell. Keep a copy of instance data at the global level for quick retrieval. Sync data up from a child cell to keep the global level up to date. Simplifying assumptions: Cells will be treated as a two level tree structure. Plan: Fix flavor breakage in child cell which causes boot tests to fail. Currently the libvirt driver needs flavor.extra_specs which is not synced to the child cell. Some options are to sync flavor and extra specs to child cell db, or pass full data with the request. https://review.openstack.org/#/c/126620/1 offers a means of passing full data with the request. Determine proper switches to turn off Tempest tests for features that don't work with the goal of getting a voting job. Once this is in place we can move towards feature parity and work on internal refactorings. Work towards adding parity for host aggregates, security groups, and server groups. They should be made to work in a single cell setup, but the solution should not preclude them from being used in multiple cells. There needs to be some discussion as to whether a host aggregate or server group is a global concept or per cell concept. Work towards merging compute/api.py and compute/cells_api.py so that developers only need to make changes/additions in once place. The goal is for as much as possible to be hidden by the RPC layer, which will determine whether a call goes to a compute/conductor/cell. For syncing data between cells, look at using objects to handle the logic of writing data to the cell/parent and then syncing the data to the other. A potential migration scenario is to consider a non cells setup to be a child cell and converting to cells will mean setting up a parent cell and linking them. There are periodic tasks in place to sync data up from a child already, but a manual kick off mechanism will need to be added. Future plans: Something that has been considered, but is out of scope for now, is that the parent/api cell doesn't need the same data model as the child cell. Since the majority of what it does is act as a cache for API requests, it does not need all the data that a cell needs and what data it does need could be stored in a form that's optimized for reads. Thoughts? ___ 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Cells conversation starter
On 22 October 2014 06:24, Tom Fifield t...@openstack.org wrote: On 22/10/14 03:07, Andrew Laski wrote: On 10/21/2014 04:31 AM, Nikola Đipanov wrote: On 10/20/2014 08:00 PM, Andrew Laski wrote: One of the big goals for the Kilo cycle by users and developers of the cells functionality within Nova is to get it to a point where it can be considered a first class citizen of Nova. Ultimately I think this comes down to getting it tested by default in Nova jobs, and making it easy for developers to work with. But there's a lot of work to get there. In order to raise awareness of this effort, and get the conversation started on a few things, I've summarized a little bit about cells and this effort below. Goals: Testing of a single cell setup in the gate. Feature parity. Make cells the default implementation. Developers write code once and it works for cells. Ultimately the goal is to improve maintainability of a large feature within the Nova code base. Thanks for the write-up Andrew! Some thoughts/questions below. Looking forward to the discussion on some of these topics, and would be happy to review the code once we get to that point. Feature gaps: Host aggregates Security groups Server groups Shortcomings: Flavor syncing This needs to be addressed now. Cells scheduling/rescheduling Instances can not currently move between cells These two won't affect the default one cell setup so they will be addressed later. What does cells do: Schedule an instance to a cell based on flavor slots available. Proxy API requests to the proper cell. Keep a copy of instance data at the global level for quick retrieval. Sync data up from a child cell to keep the global level up to date. Simplifying assumptions: Cells will be treated as a two level tree structure. Are we thinking of making this official by removing code that actually allows cells to be an actual tree of depth N? I am not sure if doing so would be a win, although it does complicate the RPC/Messaging/State code a bit, but if it's not being used, even though a nice generalization, why keep it around? My preference would be to remove that code since I don't envision anyone writing tests to ensure that functionality works and/or doesn't regress. But there's the challenge of not knowing if anyone is actually relying on that behavior. So initially I'm not creating a specific work item to remove it. But I think it needs to be made clear that it's not officially supported and may get removed unless a case is made for keeping it and work is put into testing it. While I agree that N is a bit interesting, I have seen N=3 in production [central API]--[state/region1]--[state/region DC1] \-[state/region DC2] --[state/region2 DC] --[state/region3 DC] --[state/region4 DC] I'm curious. What are the use cases for this deployment? Agreeably, root node runs n-api along with horizon, key management etc. What components are deployed in tier 2 and tier 3? And AFAIK, currently, openstack cell deployment isn't even a tree but DAG since, one cell can have multiple parents. Has anyone come up any such requirement? Plan: Fix flavor breakage in child cell which causes boot tests to fail. Currently the libvirt driver needs flavor.extra_specs which is not synced to the child cell. Some options are to sync flavor and extra specs to child cell db, or pass full data with the request. https://review.openstack.org/#/c/126620/1 offers a means of passing full data with the request. Determine proper switches to turn off Tempest tests for features that don't work with the goal of getting a voting job. Once this is in place we can move towards feature parity and work on internal refactorings. Work towards adding parity for host aggregates, security groups, and server groups. They should be made to work in a single cell setup, but the solution should not preclude them from being used in multiple cells. There needs to be some discussion as to whether a host aggregate or server group is a global concept or per cell concept. Have there been any previous discussions on this topic? If so I'd really like to read up on those to make sure I understand the pros and cons before the summit session. The only discussion I'm aware of is some comments on https://review.openstack.org/#/c/59101/ , though they mention a discussion at the Utah mid-cycle. The main con I'm aware of for defining these as global concepts is that there is no rescheduling capability in the cells scheduler. So if a build is sent to a cell with a host aggregate that can't fit that instance the build will fail even though there may be space in that host aggregate from a global perspective. That should be somewhat straightforward to
[openstack-dev] Cell Initialization
/opt/stack/nova/nova/cells/messaging.py, line 406, in process 2014-10-17 12:05:29.500 TRACE nova.cells.messaging next_hop = self._get_next_hop() 2014-10-17 12:05:29.500 TRACE nova.cells.messaging File /opt/stack/nova/nova/cells/messaging.py, line 375, in _get_next_hop 2014-10-17 12:05:29.500 TRACE nova.cells.messaging raise exception.CellRoutingInconsistency(reason=reason) 2014-10-17 12:05:29.500 TRACE nova.cells.messaging CellRoutingInconsistency: Inconsistency in cell routing: destination is cell1!toplevel but routing_path is cell1!cell1 2014-10-17 12:05:29.500 TRACE nova.cells.messaging Any ideas? Regards, Vineet Menon ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
