Open Stack

Hi Boris,
The network context creates one router per network , but i want only one
router per tenant and all network connect to that router.

Can you suggest if i can do this or should i approach the problem in some
other manner?

Thanks,
Akshay

On Fri, Mar 11, 2016 at 8:43 PM, Akshay Kumar Sanghai <
akshaykumarsanghai at gmail.com> wrote:

> Hi,
> Thanks Dina, Boris and others for helping me.
> auto_assign_nic worked. I tried that.
> I have two more concerns :
> - For now, Rally is creating one router per network . what i want is to
> have one router per tenant and all networks connect to that router. I added
> the quota section in context and defined router to be 1, but it goes out of
> quota when creating more than one network. How do i limit the number of
> router to be 1 and let network use that router?
>
> - How do i create traffic between the VMs created (between the VMs as well
> as to external world ) ?
>
> Can you help me these?
>
> Thanks
> Akshay
>
> On Fri, Mar 11, 2016 at 12:05 AM, Dina Belova <dbelova at mirantis.com>
> wrote:
>
>> Thanks Boris!
>>
>> Akshay, please try the variant proposed by Boris.
>>
>> Cheers,
>> Dina
>>
>> On Thu, Mar 10, 2016 at 9:34 PM, Boris Pavlovic <bpavlovic at mirantis.com>
>> wrote:
>>
>>> Dina,
>>>
>>> It's not Rally bug, however it's UX issue.
>>>
>>> There are many networks, so rally should pick one of them, to pick every
>>> time random network you should
>>> fix your sceanrio args to:
>>>
>>>
>>>  "NovaServers.boot_server": [
>>>         {
>>>             "args": {
>>>                 *"**auto_assign_nic": true*,
>>>                 "flavor": {
>>>                     "name": "m1.tiny"
>>>                 },
>>>                 "image": {
>>>                     "name": "cirros-0.3.4-x86_64"
>>>                 }
>>>             },
>>>
>>>
>>> Best regards,
>>> Boris Pavlovic
>>>
>>> On Thu, Mar 10, 2016 at 10:28 AM, Dina Belova <dbelova at mirantis.com>
>>> wrote:
>>>
>>>> Hm, sounds like a bug.. + Andrey and Boris - possibly they can tell
>>>> more..
>>>>
>>>> On Thu, Mar 10, 2016 at 9:04 PM, Edgar Magana <edgar.magana at workday.com
>>>> > wrote:
>>>>
>>>>> I am including one of our Rally expert to provide some guidance!
>>>>>
>>>>> Kyle, please provide any details that you may have in mind.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Edgar
>>>>>
>>>>> From: Akshay Kumar Sanghai <akshaykumarsanghai at gmail.com>
>>>>> Date: Thursday, March 10, 2016 at 9:43 AM
>>>>> To: Dina Belova <dbelova at mirantis.com>
>>>>> Cc: openstack-operators <openstack-operators at lists.openstack.org>
>>>>> Subject: Re: [Openstack-operators] [Rally] Scale testing of openstack
>>>>>
>>>>> Hi Dina,
>>>>> Thanks for the reference.
>>>>> I edited the sample boot.json file and added the network context. It
>>>>> gives an error while executing the task: "Error BadRequest: Multiple
>>>>> possible networks found, use a Network ID to be more specific". I think
>>>>> because I have multiple networks, its asking for which network to select.
>>>>> JSON file:
>>>>> {
>>>>>     "NovaServers.boot_server": [
>>>>>         {
>>>>>             "args": {
>>>>>                 "flavor": {
>>>>>                     "name": "m1.tiny"
>>>>>                 },
>>>>>                 "image": {
>>>>>                     "name": "cirros-0.3.4-x86_64"
>>>>>                 }
>>>>>             },
>>>>>             "runner": {
>>>>>                 "type": "constant",
>>>>>                 "times": 4,
>>>>>                 "concurrency": 2
>>>>>             },
>>>>>             "context": {
>>>>>                 "users": {
>>>>>                     "tenants": 3,
>>>>>                     "users_per_tenant": 2
>>>>>                 },
>>>>>                 "network": {
>>>>>                     "networks_per_tenant": 2,
>>>>>                     "subnets_per_network": 1
>>>>>                 }
>>>>>             }
>>>>>         }
>>>>>     ]
>>>>> }
>>>>>
>>>>> Can you please help me with this issue ?
>>>>>
>>>>> Thanks,
>>>>> Akshay
>>>>>
>>>>>
>>>>> On Thu, Mar 10, 2016 at 10:19 PM, Dina Belova <dbelova at mirantis.com>
>>>>> wrote:
>>>>>
>>>>>> Akshay,
>>>>>>
>>>>>> you may try to use
>>>>>> http://docs.openstack.org/developer/rally/plugin/plugin_reference.html#novaservers-boot-server-scenario and
>>>>>> specify two contexts in the scenario configuration: user context for tenant
>>>>>> creation and network context for networks creation for these tenants.
>>>>>> Scenario itself will be creating the VMs and link them to the networks.
>>>>>>
>>>>>> Cheers,
>>>>>> Dina
>>>>>>
>>>>>> On Thu, Mar 10, 2016 at 6:03 PM, Akshay Kumar Sanghai <
>>>>>> akshaykumarsanghai at gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> I have a openstack setup with 1 controller node, 1 network node and
>>>>>>> 2 compute nodes. I want to perform scale testing of the setup in the
>>>>>>> following manner:
>>>>>>>
>>>>>>> - Create 10 tenants
>>>>>>> - Create 1 router per tenant
>>>>>>> - Create 100 neutron networks across 10 tenants attached to the
>>>>>>> router
>>>>>>> - Create 500 VMs spread across 10 tenants attached to the networks
>>>>>>>
>>>>>>> Individually, I can create tenants, routers , networks ,vms , but I
>>>>>>> don't know how to keep them interconnected meaning the networks connecting
>>>>>>> to those existing router and then  VMs connecting to those networks.
>>>>>>>
>>>>>>> Please suggest me if some plugin is already available and  how to
>>>>>>> generate load from those VMs
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Akshay Sanghai
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OpenStack-operators mailing list
>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Dina Belova
>>>>>>
>>>>>> Software Engineer
>>>>>>
>>>>>> Mirantis Inc.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best regards,
>>>>
>>>> Dina Belova
>>>>
>>>> Software Engineer
>>>>
>>>> Mirantis Inc.
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Best regards,
>>
>> Dina Belova
>>
>> Software Engineer
>>
>> Mirantis Inc.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160314/5817b4c3/attachment.html>