[openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.
Hi All, Creation of server with command 'nova boot --image image --flavor m1.medium --nic port-id=port-id --security-groups sec_grp name' fails to attach the security group to the port/instance. The response payload has the security group added but only default security group is attached to the instance. Separate action has to be performed on the instance to add sec_grp, and it is successful. Supplying the same with '--nic net-id=net-id' works as expected. Is this the expected behaviour / are there any other options which needs to be specified to add the security group when port-id needs to be attached during boot. Thanks, Parikshit Manur ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] Enabling vlan trunking on neutron port.
Hi All, I have a setup which has VM on flat provider network , and I want to reach VM on VLAN provider network. The packets are forwarded till veth pair and are getting dropped by br-int. Can neutron port be configured to allow vlan trunking? Thanks, Parikshit Manur ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
Hi Edgar, NetScaler CI is not listed in the report. NetScaler CI up and running and it is voting for patchsets which contains LBaaS changes, that's why you did not see it voting for the test change ref. Also, you can add me as a contact person and alias networking-cloudinteg...@citrix.com as email contact point for the NetScaler CI. Please let me know if you have any questions. Thanks, Parikshit Manur -Original Message- From: Edgar Magana [mailto:edgar.mag...@workday.com] Sent: Saturday, 16 August 2014 4:06 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to be run Importance: High Team, I did a quick audit on the Neutron CI. Very sad results. Only few plugins and drivers are running properly and testing all Neutron commits. I created a report here: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin _and_Drivers We will discuss the actions to take on the next Neutron IRC meeting. So please, reach me out to clarify what is the status of your CI. I had two commits to quickly verify the CI reliability: https://review.openstack.org/#/c/114393/ https://review.openstack.org/#/c/40296/ I would expect all plugins and drivers passing on the first one and failing for the second but I got so many surprises. Neutron code quality and reliability is a top priority, if you ignore this report that plugin/driver will be candidate to be remove from Neutron tree. Cheers, Edgar P.s. I hate to be the inquisitor hereŠ but someone has to do the dirty job! On 8/14/14, 8:30 AM, Kyle Mestery mest...@mestery.com wrote: Folks, I'm not sure if all CI accounts are running sufficient tests. Per the requirements wiki page here [1], everyone needs to be running more than just Tempest API tests, which I still see most neutron third-party CI setups doing. I'd like to ask everyone who operates a third-party CI account for Neutron to please look at the link below and make sure you are running appropriate tests. If you have questions, the weekly third-party meeting [2] is a great place to ask questions. Thanks, Kyle [1] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting [2] https://wiki.openstack.org/wiki/Meetings/ThirdParty ___ 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] [Devstack] q-svc fails to start in devstack.
Hi All, Start of q-svc in devstack fails with error message No type driver for tenant network_type: vxlan. Service terminated!. I have not choosen vxlan as ML2 type driver in localrc. I have added the details of localrc file for my setup below for reference. Can you please point out if I am missing any config or there is any workaround to fix the issue. Could you also point me to a separate mailing list for devstack related queries if there is any. localrc file contents: RECLONE=yes DEST=/opt/stack SCREEN_LOGDIR=/opt/stack/new/screen-logs LOGFILE=/opt/stack/new/devstacklog.txt DATABASE_PASSWORD=password RABBIT_PASSWORD= password SERVICE_TOKEN= password SERVICE_PASSWORD= password ADMIN_PASSWORD= password disable_service n-net enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3 enable_service q-meta enable_service q-lbaas enable_service neutron # Optional, to enable tempest configuration as part of devstack enable_service tempest Q_PLUGIN=ml2 Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch Q_ML2_PLUGIN_TYPE_DRIVERS=vlan,flat ML2_VLAN_RANGES=physnet1:1500:1600 ENABLE_TENANT_VLANS=True PHYSICAL_NETWORK=physnet1 OVS_PHYSICAL_BRIDGE=br-eth1 Thanks, Parikshit Manur ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Setting up compute node on XenServer.
Hi, * I have the Openstack setup working with KVM being one of the compute node. The compute node of type XenServer was added to the setup. The XenServer has Dom0 and DomU nodes with the DomU node running the nova -compute service. The xenserver is shown in nova hypervisor-list ommand. * The Openstack setup is backed by vlan and it is running neutron for the networking. * After issuing the nova boot command for XenServer compute node the request fails with the status of the vm is in Error state when nova list command is run. * The following is the log details which was captured pertaining to the instance where the error state is being set. 2013-10-18 19:43:31.704 21735 INFO nova.scheduler.filter_scheduler [req-9078a74a-5b32-4521-8398-fc582964cfed bc7a0e98500f4633a47546ba542585b2 1d770e03eb134f58977313cac6edef92] Attempting to build 1 instance(s) uuids: [u'b77060d3-050a-46d1-893e-43c9d6c1d48d'] 2013-10-18 19:43:31.736 21735 WARNING nova.scheduler.driver [req-9078a74a-5b32-4521-8398-fc582964cfed bc7a0e98500f4633a47546ba542585b2 1d770e03eb134f58977313cac6edef92] [instance: b77060d3-050a-46d1-893e-43c9d6c1d48d] Setting instance to ERROR state. Can you suggest any reason for the above error? Is there any way to enable detailed logging and to create vm on the xenserver Compute node? Thanks, Parikshit Manur ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
