Open Stack

Sorry here is the context


"context": {

                "users": {

                    "tenants": 1,

                    "users_per_tenant": 1

                }

                "neutron_network": {

                    "network_cidr": "10.%s.0.0/16",

                }

            }

Because I see this error
2014-08-29 14:56:23.769 5495 TRACE rally     "expected ',' or '}', but got %r" % token.id, token.start_mark)
2014-08-29 14:56:23.769 5495 TRACE rally ParserError: while parsing a flow mapping
2014-08-29 14:56:23.769 5495 TRACE rally   in "<string>", line 3, column 9:
2014-08-29 14:56:23.769 5495 TRACE rally             {
2014-08-29 14:56:23.769 5495 TRACE rally             ^
2014-08-29 14:56:23.769 5495 TRACE rally expected ',' or '}', but got '<scalar>'
2014-08-29 14:56:23.769 5495 TRACE rally   in "<string>", line 29, column 13:
2014-08-29 14:56:23.769 5495 TRACE rally                 "neutron_network": {
2014-08-29 14:56:23.769 5495 TRACE rally                 ^
2014-08-29 14:56:23.769 5495 TRACE rally


Ajay


From: Timur Nurlygayanov <tnurlygayanov at mirantis.com<mailto:tnurlygayanov at mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, August 29, 2014 at 1:54 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: "Harshil Shah (harsshah)" <harsshah at cisco.com<mailto:harsshah at cisco.com>>
Subject: Re: [openstack-dev] Rally scenario Issue

Hi Ajay,

looks like you need to use NeutronContext feature to configure Neutron Networks during the benchmarks execution.
We now working on merge of two different comits with NeutronContext implementation:
https://review.openstack.org/#/c/96300  and https://review.openstack.org/#/c/103306

could you please apply commit https://review.openstack.org/#/c/96300 and run your benchmarks? Neutron Network with subnetworks and routers will be automatically created for each created tenant and you should have the ability to connect to VMs. Please, note, that you should add the following part to your task JSON to enable Neutron context:
...
"context": {
    ...
    "neutron_network": {
        "network_cidr": "10.%s.0.0/16",
    }
}
...

Hope this will help.



On Fri, Aug 29, 2014 at 11:42 PM, Ajay Kalambur (akalambu) <akalambu at cisco.com<mailto:akalambu at cisco.com>> wrote:
Hi
I am trying to run the Rally scenario boot-runcommand-delete. This scenario has the following code
 def boot_runcommand_delete(self, image, flavor,
                               script, interpreter, username,
                               fixed_network="private",
                               floating_network="public",
                               ip_version=4, port=22,
                               use_floatingip=True, **kwargs):
  server = None
        floating_ip = None
        try:
            print "fixed network:%s floating network:%s" %(fixed_network,floating_network)
            server = self._boot_server(
                self._generate_random_name("rally_novaserver_"),
                image, flavor, key_name='rally_ssh_key', **kwargs)

            self.check_network(server, fixed_network)

The question I have is the instance is created with a call to boot_server but no networks are attached to this server instance. Next step it goes and checks if the fixed network is attached to the instance and sure enough it fails
At the step highlighted in bold. Also I cannot see this failure unless I run rally with –v –d object. So it actually reports benchmark scenario numbers in a table with no errors when I run with
rally task start boot-and-delete.json

And reports results. First what am I missing in this case. Thing is I am using neutron not nova-network
Second when most of the steps in the scenario failed like attaching to network, ssh and run command why bother reporting the results

Ajay


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--

Timur,
QA Engineer
OpenStack Projects
Mirantis Inc

[http://www.openstacksv.com/]<http://www.openstacksv.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140829/5124cbee/attachment.html>