Re: [openstack-dev] How to get openstack bugs data for research?
Hi, you could take a look at Stackalytics and how this website communicates with launchpad. https://wiki.openstack.org/wiki/Stackalytics/HowToRun Best, Angelo On 03/12/2014 13:41, Louis Taylor wrote: On Wed, Dec 03, 2014 at 08:20:45PM +0800, zfx0...@gmail.com wrote: Hi, all I am a graduate student in Peking University, our lab do some research on open source projects. This is our introduction: https://passion-lab.org/ Now we need openstack issues data for research, I found the issues list: https://bugs.launchpad.net/openstack/ I want to download the openstack issues data, Could anyone tell me how to download the data? Or is there some link or API for download the data? And I found 9464 bugs in https://bugs.launchpad.net/openstack/ ??is this all? why so few? That is the number of currently open bugs. There are 47733 bugs including closed ones. Launchpad has an API [1], which can probably list the bugs filed against a project. [1] https://help.launchpad.net/API ___ 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] [NFV][Telco] pxe-boot
Hi all, my team and I are working on pxe boot feature very similar to the Discless VM one in Active blueprint list[1] The blueprint [2] is no longer active and we created a new spec [3][4]. Nova core reviewers commented our spec and the first and the most important objection is that there is not a compelling reason to provide this kind of feature : booting from network. Aside from the specific implementation, I think that some members of TelcoWorkingGroup could be interested in and provide a use case. I would also like to add this item to the agenda of next meeting Any thought? Best regards, Angelo [1] https://wiki.openstack.org/wiki/TelcoWorkingGroup#Active_Blueprints [2] https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe [3] https://blueprints.launchpad.net/nova/+spec/boot-order-for-instance [4] https://review.openstack.org/#/c/133254/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tempest]
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] [tempest] How to run tempest tests
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
Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses
Hi It is a great idea. +1 On 19/11/2014 00:27, Vishvananda Ishaya wrote: It looks like this has not been reported so a bug would be great. It looks like it might be as easy as adding the NoMoreFixedIps exception to the list where FixedIpLimitExceeded is caught in nova/network/manager.py Vish On Nov 18, 2014, at 8:13 AM, Edgar Magana edgar.mag...@workday.com mailto:edgar.mag...@workday.com wrote: Hello Community, When a network subnet runs out of IP addresses a request to create a VM on that network fails with the Error message: No valid host was found. There are not enough hosts available. In the nova logs the error message is: NoMoreFixedIps: No fixed IP addresses available for network: Obviously, this is not the desirable behavior, is there any work in progress to change it or I should open a bug to properly propagate the right error message. Thanks, Edgar ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org mailto: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][doc] python-novaclient doc not updated
Hi doc team, I think that in the official doc of python-novaclient [1] there is a Contributing section not synchronized with the doc in git repository: [2] In details the section Contributing--||Testing is not up to date I tried to improve this page following gerrit workflow but I'm not very expert with doc tools and I don't know how to contribute. Is this a bug? How could I report this? Cheers, Angelo [1] http://docs.openstack.org/developer/python-novaclient/ [2] http://git.openstack.org/cgit/openstack/python-novaclient/tree/doc/source/index.rst ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [devstack] keystone doesn't restart after ./unstack
Hi Chmouel, I'll create it in case it is a real bug. Thank you Angelo On 05/11/2014 05:35, JunJie Nan wrote: I think it's a bug, rejion should work after unstack. And stack.sh is need after clean.sh instead of unstack.sh. Hi, If you do ./unstack.sh you probably want to do ./stack.sh back again to restack, ./rejoin-stack.sh is here when you have your screen session killed and want to rejoin it without having to ./stack.sh the full shenanigan again. Cheers, Chmouel On Tue, Nov 4, 2014 at 1:52 PM, Angelo Matarazzo angelo.matara...@dektech.com.au mailto:angelo.matara...@dektech.com.au wrote: Hi all, sometimes I use devstack (in a VM with Ubuntu installed) and I perform ./unstack command to reset my environment. When I perform rejoin-stack.sh keystone endpoint doesn't work. Following http://www.gossamer-threads.com/lists/openstack/dev/41939 suggestion I checked /etc/apache2/sites-enabled and symbolic link to ../sites-available/keystone.conf and doesn't exist. If I recreate the symbolic link keystone works.. what is the correct workflow after I have performed ./unstack.sh Should I perform ./stack.sh or this is a bug? Cheers, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org mailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org mailto: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] [devstack] keystone doesn't restart after ./unstack
Hi Dean, I think that a lot of developers use devstack installed on a VM. So the right WoW after perfroming ./unstack.sh is : 1)If you don't want that stack.sh overwrite your local configuration set RECLONE=no in local.conf 2)perform ./stack.sh 3)perform ./rejoin-stack.sh Right? Thank you beforehand Angelo On 05/11/2014 08:41, Dean Troyer wrote: On Tue, Nov 4, 2014 at 10:35 PM, JunJie Nan nanjun...@gmail.com mailto:nanjun...@gmail.com wrote: I think it's a bug, rejion should work after unstack. And stack.sh is need after clean.sh instead of unstack.sh. As Chmouel said, rejoin-stack.sh is meant to only re-create the screen sessions from the last stack.sh run. As services are configured to run under Apache's mod_wsgi they will not be handled by rejoin.stack.sh http://rejoin.stack.sh. dt -- Dean Troyer dtro...@gmail.com mailto:dtro...@gmail.com ___ 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] keystone doesn't restart after ./unstack
Hi all, sometimes I use devstack (in a VM with Ubuntu installed) and I perform ./unstack command to reset my environment. When I perform rejoin-stack.sh keystone endpoint doesn't work. Following http://www.gossamer-threads.com/lists/openstack/dev/41939 suggestion I checked /etc/apache2/sites-enabled and symbolic link to ../sites-available/keystone.conf and doesn't exist. If I recreate the symbolic link keystone works.. what is the correct workflow after I have performed ./unstack.sh Should I perform ./stack.sh or this is a bug? Cheers, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][doc]
Hi all, I have a question for you devs. I don't understand the difference between this link http://git.openstack.org/cgit/openstack/governance/tree/reference/ project-testing-interface.rst and https://wiki.openstack.org/wiki/ProjectTestingInterface Some parts don't match (e.g. unittest running section). If the git link is the right doc should we update the wiki page? I found the reference to the wiki page here: https://lists.launchpad.net/openstack/msg08058.html Best regards, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][doc] project testing interface
Hi all, I have a question for you devs. I don't understand the difference between this link http://git.openstack.org/cgit/openstack/governance/tree/reference/project-testing-interface.rst and https://wiki.openstack.org/wiki/ProjectTestingInterface Some parts don't match (e.g. unittest running section). If the git link is the right doc should we update the wiki page? I found the reference to the wiki page here: https://lists.launchpad.net/openstack/msg08058.html Best regards, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Virtual_machine for devstack
Hi all, I have prepared a virtual machine with ubuntu installed for devstack In the /media/nas/nfs_shares/projects/Cloud/Openstack/devstack8_10_14/ There are devstack8_10_14.ova for virtual box import local.conf --configuration file for devstack README_8_10_14 -- instructions pls, read the instructions and for installing read carefully following sections Prerequisites Install devstack == Other sections: Run devstack Shutdown devstack Install Liclipse = Use of Liclipse = Reinstall devstack === Connect to devstack = Git usage == Any review or comment is very welcome cheers, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Virtual_machine for devstack
Hi all, sorry... I made mistake. wrong mailing list Cheers, Angelo On 08/10/2014 10:27, Angelo Matarazzo wrote: Hi all, I have prepared a virtual machine with ubuntu installed for devstack In the /media/nas/nfs_shares/projects/Cloud/Openstack/devstack8_10_14/ There are devstack8_10_14.ova for virtual box import local.conf --configuration file for devstack README_8_10_14 -- instructions pls, read the instructions and for installing read carefully following sections Prerequisites Install devstack == Other sections: Run devstack Shutdown devstack Install Liclipse = Use of Liclipse = Reinstall devstack === Connect to devstack = Git usage == Any review or comment is very welcome cheers, Angelo ___ 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] Create an instance with a custom uuid
Hi all, while I was working on blueprint Pasquale addressed this issue. In the use case explained both features are involved but the user defined UUID does not depend strictly on original blueprint but it can be a new one. If there is no objection I could write a blueprint/specification regarding to last solution. Any thought? BR, Angelo On 01/10/2014 18:07, Joe Gordon wrote: On Wed, Oct 1, 2014 at 8:29 AM, Solly Ross sr...@redhat.com mailto:sr...@redhat.com wrote: (response inline) - Original Message - From: Pasquale Porreca pasquale.porr...@dektech.com.au mailto:pasquale.porr...@dektech.com.au To: openstack-dev@lists.openstack.org mailto:openstack-dev@lists.openstack.org Sent: Wednesday, October 1, 2014 11:08:50 AM Subject: Re: [openstack-dev] [nova] Create an instance with a custom uuid Thank you for the answers. I understood the concerns about having the UUID completely user defined and I also understand Nova has no interest in supporting a customized algorithm to generate UUID. Anyway I may have found a solution that will cover my use case and respect the standard for UUID (RFC 4122 http://www.ietf.org/rfc/rfc4122.txt ) . The generation of the UUID in Nova make use of the function uuid4() from the module uuid.py to have an UUID (pseudo)random, according to version 4 described in RFC 4122. Anyway this is not the only algorithm supported in the standard (and implemented yet in uuid.py ). In particular I focused my attention on UUID version 1 and the method uuid1(node=None, clock_seq=None) that allows to pass as parameter a part of the UUID ( node is the field containing the last 12 hexadecimal digits of the UUID). So my idea was to give the chance to the user to set uiid version (1 or 4, with the latter as default) when creating a new instance and in case of version 1 to pass optionally a value for parameter node . I would think that we could just have a node parameter here, and automatically use version 1 if that parameter is passed (if we decided to go the route of changing the current UUID behavior). From what I gather this requested change in API is based on for your blueprint https://blueprints.launchpad.net/nova/+spec/pxe-boot-instance. Since your blueprint is not approved yet discussing further work to improve it is a bit premature. Any thoughts? On 09/30/14 14:07, Andrew Laski wrote: On 09/30/2014 06:53 AM, Pasquale Porreca wrote: Going back to my original question, I would like to know: 1) Is it acceptable to have the UUID passed from client side? In my opinion, no. This opens a door to issues we currently don't need to deal with, and use cases I don't think Nova should support. Another possibility, which I don't like either, would be to pass in some data which could influence the generation of the UUID to satisfy requirements. But there was a suggestion to look into addressing your use case on the QEMU mailing list, which I think would be a better approach. 2) What is the correct way to do it? I started to implement this feature, simply passing it as metadata with key uuid, but I feel that this feature should have a reserved option rather then use metadata. On 09/25/14 17:26, Daniel P. Berrange wrote: On Thu, Sep 25, 2014 at 05:23:22PM +0200, Pasquale Porreca wrote: This is correct Daniel, except that that it is done by the virtual firmware/BIOS of the virtual machine and not by the OS (not yet installed at that time). This is the reason we thought about UUID: it is yet used by the iPXE client to be included in Bootstrap Protocol messages, it is taken from the uuid field in libvirt template and the uuid in libvirt is set by OpenStack; the only missing passage is the chance to set the UUID in OpenStack instead to have it randomly generated. Having another user defined tag in libvirt won't help for our issue, since it won't be included in Bootstrap Protocol messages, not without changes in the virtual BIOS/firmware (as you stated too) and honestly my team doesn't have interest in this (neither the competence). I don't think the configdrive or metadata service would help either: the OS on the instance is not yet installed at that time (the target if the network boot is exactly to install the OS on the instance!), so it won't be able to mount it. Ok, yes, if we're considering the DHCP client inside the iPXE BIOS blob, then I don't see any currently viable options besides UUID. There's no mechanism for
[openstack-dev] [nova] Choice of Series goal of a blueprint
Hi all, Can create a blueprint and choose a previous Series goal (eg:Icehouse)? I think that it can be possible but no reviewer or driver will be interested in it. Right? Best regards, Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] libvirt boot parameters
Hi, I think that this variable is useful for me cfg.IntOpt(reboot_timeout, default=0, help=Automatically hard reboot an instance if it has been stuck in a rebooting state longer than N seconds. Set to 0 to disable.), cfg.IntOpt(instance_build_timeout, but it seems that Eli is right: lbvirt driver doesn't implement this function def poll_rebooting_instances(self, timeout, instances): pass BTW I'm developing a feature: booting from network. In my scenario sometimes the the booting instance pauses because the boot source ( PXE) cannot answer on time. Look at 6.4. Installing guest virtual machines with PXE https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html I'll investigate on reboot_timeout and I'll inform you but thanks for the tips BR Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] libvirt boot parameters
Hi all, I need to add the option rebootTimeout when the instance boots. If you use the*qemu-kvm*, boot parameter/|reboot-timeout|/allows a virtual machine to retry booting if no bootable device is found: /*# qemu-kvm --boot reboot-timeout=1000*/ Ref: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html In Openstack a new boot parameter should be entered into Libvirt XML attributes where required: bios rebootTimeout=5000 / under the os in the libvirt.xml file. My idea is to add an option to nova boot command changing (nova API, nova base,python-novaclient) but I would like to know what you think about that? Thank you beforehand Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] bp/pxe boot
Hi folks, I would add the pxe boot capability to Nova/libvirt and Horizon too. Currently, compute instances must be booted from images (or snapshots) stored in Glance or volumes stored in Cinder. Our idea (as you can find below) is already described there [1] [2] and aims to provide a design for booting compute instances from a PXE boot server, i.e. bypassing the image/snapshot/volume requirement. There is already a open blueprint but I would want to register a new one because it has no update since 2013. https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe https://wiki.openstack.org/wiki/Nova/Blueprints/pxe-boot-instance https://wiki.openstack.org/wiki/Nova/Blueprints/pxe-boot-instance What do you think? Thanks beforehand Angelo -- Angelo Matarazzo DEK Technologies Via dei Castelli Romani, 22 00040 Pomezia (Roma) E-mail: angelo.matara...@dektech.com.au WEB: www.dektech.com.au ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] bp/pxe boot
Hi folks, I would add the pxe boot capability to Nova/libvirt and Horizon too. Currently, compute instances must be booted from images (or snapshots) stored in Glance or volumes stored in Cinder. Our idea (as you can find below) is already described there [1] [2] and aims to provide a design for booting compute instances from a PXE boot server, i.e. bypassing the image/snapshot/volume requirement. There is already a open blueprint but I would want to register a new one because it has no update since 2013. https://blueprints.launchpad.net/nova/+spec/libvirt-empty-vm-boot-pxe https://wiki.openstack.org/wiki/Nova/Blueprints/pxe-boot-instance What do you think? Thanks beforehand Angelo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
