Re: [openstack-dev] [third-party]Time for Additional Meeting for third-party
anteaya, UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time for china. if there is no time slot there, just pick up any time between UTC 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and dinner.) Yongi He -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Tuesday, December 02, 2014 4:07 AM To: openstack Development Mailing List; openstack-in...@lists.openstack.org Subject: [openstack-dev] [third-party]Time for Additional Meeting for third-party One of the actions from the Kilo Third-Party CI summit session was to start up an additional meeting for CI operators to participate from non-North American time zones. Please reply to this email with times/days that would work for you. The current third party meeting is on Mondays at 1800 utc which works well since Infra meetings are on Tuesdays. If we could find a time that works for Europe and APAC that is also on Monday that would be ideal. Josh Hesketh has said he will try to be available for these meetings, he is in Australia. Let's get a sense of what days and timeframes work for those interested and then we can narrow it down and pick a channel. Thanks everyone, Anita. ___ 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] [sriov] Could create sriov vm on one host successfully but failed on another host
This is a message from pci stats, it means scheduler select a host actually not meeting the request. But make sure you do enable the PCI filter in the scheduler first. Yongli He -Original Message- From: yujie [mailto:judy_yu...@126.com] Sent: Friday, January 8, 2016 12:43 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [sriov] Could create sriov vm on one host successfully but failed on another host Hi all, I have two hosts. Host1 run services of controller/compute/network, and host2 run services of compute. The network type is vlan. When creating port with direct type and booting a vm using this port on host2, the vm works well. But when create the vm on host1 using same way, the vm state is error. And the nova-compute log says: ERROR nova.pci.stats [req-4af9b36d-8a0c-43d5-8535-fbf9e8d1b857 06172a48a7254dda934a729f4a58d2ec 894880b2f31046d7b8a83bc3783df070 - - -] Failed to allocate PCI devices for instance. Unassigning devices back to pools. This should not happen, since the scheduler should have accurate information, and allocation during claims is controlled via a hold on the compute node semaphore Any suggestion will be grateful. Thanks. Yu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] PCI CI is down
This bug and another related block bug: https://bugs.launchpad.net/nova/+bug/1536509 been merged recently, PCI-CI now is back online. Regards Yongli He -Original Message- From: Nikola Đipanov [mailto:ndipa...@redhat.com] Sent: Wednesday, January 20, 2016 10:41 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Nova] PCI CI is down Hey Nova, It seems the a bug [1] sneaked in that made the PCI CI jobs fail 100% of the time so they got turned off. Fix for the bug should be making it's way through the queue soon, but it was hinted on the review that there may be further problems. I'd like to help fix these issues ASAP as the regression seems fairly fresh, but debugging is hard since the CI is offline (instead of just non-voting) so I can't really access any logs. It'd be great if someone from the team helping out with the Intel PCI CI would bring it back online as a non-voting job so that we can have feedback which will surely help us fix it more quickly. Cheers, Nikola [1] https://bugs.launchpad.net/nova/+bug/1535367 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Intel PCI CI down today due to testing scripts bug
Hello OpenStackers! The Intel PCI CI, due to test scripts bug( recently added) is failing to report results to OpenStack Jenkins third-party tests. We had identify this bug and the scripts had rolled back to verified version. Now we are discussing this with infra team to bring it back ASAP. Sorry for the inconvenience and your patience. Regards Yongli He __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Testing support for PCI passthrough
Hi, You can following this wiki page: https://wiki.openstack.org/wiki/Pci_passthrough From: Irena Berezovsky [mailto:ire...@mellanox.com] Sent: Tuesday, September 03, 2013 2:55 AM To: Jiang, Yunhong; youngli...@intel.com Cc: OpenStack Development Mailing List Subject: [openstack-dev] [Nova] Testing support for PCI passthrough Hi guys, Great work on adding PCI pass-through support to nova. We would like to test the support for PCI pass-through. We thought to use devstack (nova) on physical machine with SR-IOV devices and apply patches that are still under review. Can you please advise what should be defined in nova.conf and what should be requested on nova-boot command in order to create VM with PCI device? Is it according to documented at https://wiki.openstack.org/wiki/Enhanced-platform-awareness-pcie? Can you please help me to identify the use cases that merged patches support? Thank you very much, Irena ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
