[openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Hello all, I'd like you all to consider making a few changes to our IRC meeting infrastructure TL;DR: I think we need to add #openstack-meeting-5 and make sure people are using it rather then per-project channels Slightly longer version . Capacity I think we've

Re: [openstack-dev] [devstack] How to source openrc?

On Mon, Nov 23, 2015 at 12:17:13PM +0800, Wilence Yao wrote: > Hi all, > > In devstack stable/liberty, error is : > > source openrc admin admin > openrc:90: unknown condition: -v > > the line 90 and code block in openrc is > ``` > # Set OS_CACERT to a default CA certificate chain if it exists.

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

On Wed, Nov 18, 2015 at 05:44:38PM +0100, Ihar Hrachyshka wrote: > Hi all, > > as per [1] I imply that all projects under stable-maint-core team > supervision must abide the stable policy [2] which limits the types of > backports for N-2 branches (now it’s stable/kilo) to "Only critical bugfixes

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On Wed, Nov 18, 2015 at 11:46:40AM +, Daniel P. Berrange wrote: > On Wed, Nov 18, 2015 at 05:18:28PM +1100, Tony Breeds wrote: > > On Tue, Nov 17, 2015 at 03:32:45PM -0800, Jay Pipes wrote: > > > On 11/17/2015 11:10 AM, Markus Zoeller wrote:

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On Tue, Nov 17, 2015 at 03:32:45PM -0800, Jay Pipes wrote: > On 11/17/2015 11:10 AM, Markus Zoeller wrote: > >Background > >== > >The blueprint [1] wants to utilize the *virtlogd* logging deamon from > >libvirt. Among others to solve bug [2], one of our oldest ones. The > >funny part is,

Re: [Openstack-operators] [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 05:15:18PM +1100, Tony Breeds wrote: > Hello all, > > I'll start by acknowledging that this is a big and complex issue and I > do not claim to be across all the view points, nor do I claim to be > particularly persuasive ;P > > Having stated t

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 05:15:18PM +1100, Tony Breeds wrote: > Hello all, > > I'll start by acknowledging that this is a big and complex issue and I > do not claim to be across all the view points, nor do I claim to be > particularly persuasive ;P > > Having stated t

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On Thu, Nov 12, 2015 at 02:40:19PM +0100, Alan Pevec wrote: > AFAICT there are at least two blockers for 2014.2.4: > - horizon - django_openstack_auth issue Tony mentions in > https://review.openstack.org/172826 Horizon itself is fine BUT gets caught up in a mess of g-r updates. The issue at

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: > 4. Create a capabilitioes API of some description, that can be queried so > that > consumers (horizon) can known Thanks everyone for the input. I'm going to go with the simple first step that Sean described as it s

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 02:42:20PM -0500, Sean Dague wrote: > The upstream strategy has been make upgrades unexciting, and then folks > can move forward easily. > > I would really like to unpack what those various reasons are that people > are trapped. Because figuring out why they feel that way

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 10:12:21AM -0800, Clint Byrum wrote: > The argument in the original post, I think, is that we should not > stand in the way of the vendors continuing to collaborate on stable > maintenance in the upstream context after the EOL date. We already have > distro vendors doing

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 06:42:05PM +, Jeremy Stanley wrote: > On 2015-11-06 10:12:21 -0800 (-0800), Clint Byrum wrote: > [...] > > Note that it's not just backporters though. It's infra resources too. > > Aye, there's the rub. We don't just EOL these branches for fun or > because we hate old

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 09:20:08AM -0600, Matt Riedemann wrote: > It also extends the life and number of tests that need to be run against > things in Tempest, which already runs several dozen jobs per change proposed > today (since Tempest is branchless). Okay this is something that I hadn't

Re: [openstack-dev] [nova][api]

On Fri, Nov 06, 2015 at 12:30:19PM +, John Garbutt wrote: > Ideally, I would like us to fill out that pagination part first. It seems the person leading this within the API-WG is AWOL so ... > If we can't get global agreement quickly, we should at least get a > Nova API wide standard

[openstack-dev] [nova][policy] Exposing hypervisor details to users

Hello all, I came across [1] which is notionally an ironic bug in that horizon presents VM operations (like suspend) to users. Clearly these options don't make sense to ironic which can be confusing. There is a horizon fix that just disables migrate/suspened and other functaions if the

[openstack-dev] [stable][all] Keeping Juno "alive" for longer.

Hello all, I'll start by acknowledging that this is a big and complex issue and I do not claim to be across all the view points, nor do I claim to be particularly persuasive ;P Having stated that, I'd like to seek constructive feedback on the idea of keeping Juno around for a little longer.

Re: [openstack-dev] [devstack] Logging - filling up my tiny SSDs

On Thu, Nov 05, 2015 at 09:52:07PM +, Sean M. Collins wrote: > I'll make sure to name the variable appropriately. Some ideas: > > SEAN_COLLINS_CREEPY_BASEMENT_DEVSTACK_LAB > SEANS_DISCOUNT_DEVSTACK_EMPORIUM > ANT_SIZED_SSD ALL_YOUR_DISK_ARE_BELONG_TO_SCREEN? Yours Tony. pgp8xQipI_y6j.pgp

[openstack-dev] [nova][api]

Hi All, Around the middle of October a spec [1] was uploaded to add pagination support to the os-hypervisors API. While I recognize the use case it seemed like adding another pagination implementation wasn't an awesome idea. Today I see 3 more requests to add pagination to APIs [2] Perhaps

Re: [openstack-dev] [nova][api] Pagination in thre API

On Thu, Nov 05, 2015 at 01:09:36PM +1100, Tony Breeds wrote: > Hi All, > Around the middle of October a spec [1] was uploaded to add pagination > support to the os-hypervisors API. While I recognize the use case it seemed > like adding another pagination implementation wasn't an

Re: [Openstack-operators] [tags] recurring meetings

On Tue, Nov 03, 2015 at 03:49:14PM -0500, Shamail Tahir wrote: > Hi everyone, > > Per our conversation at the summit, the ops-tags team will now start > holding regular meetings with the hopes of increasing participation and/or > number of reviews. The team will meet the second Thursday of every

Re: [OpenStack-Infra] logstash URL queries.

On Fri, Oct 16, 2015 at 11:37:45AM -0400, Sean Dague wrote: > It turns out new kibana is more strict on quotes. > project:"openstack/requirements" with your query works correctly. Ah okay. Thanks Sean. Yours Tony. pgpjypd5agHb9.pgp Description: PGP signature

Re: [openstack-dev] [stable/liberty] [requirements]/[oslo] ceilometer jobs failing.

On Sat, Oct 17, 2015 at 08:56:01AM +1100, Tony Breeds wrote: > We actually need both https://review.openstack.org/233854 > and https://review.openstack.org/#/c/235536 to land at this point. Okay https://review.openstack.org/233854 has merged https://review.openstack.org/#/c/235536 is in

Re: [openstack-dev] [stable/liberty] [requirements]/[oslo] ceilometer jobs failing.

On Fri, Oct 16, 2015 at 03:32:21PM -0400, Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2015-10-16 22:21:27 +1100: > > Hi All, > > We have an issue for any review that causes a new commit to ceilometer, > > it > > will fail with[1]: > > > > ValueError: git history

[openstack-dev] [stable/liberty] [requirements]/[oslo] ceilometer jobs failing.

Hi All, We have an issue for any review that causes a new commit to ceilometer, it will fail with[1]: ValueError: git history requires a target version of pbr.version.SemanticVersion(5.0.1), but target version is pbr.version.SemanticVersion(5.0.0) Switching to post-versioning[2]

[openstack-dev] logstash URL queries.

Hi Everybody, So it looks to me like we recently updated logstash.openstack.org to a newer version of kibabna? I'll very openly admit that my logstash fu is wanting but I'm having a little trouble 1) I can't work out how to after performing my query/filtering share the results (for

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to take

Re: [openstack-dev] Error Installing KILO release on powerpc

On Thu, Oct 08, 2015 at 11:08:06PM +0530, Rahul Arora wrote: > Hi Team > > I am trying to run Openstack KILO release on my powerpc platform.I am able > to cross compile all the KILO related packages using yocto framework.But > while running the following command i am getting below error messages.

Re: [Openstack] [openstack-dev] Error Installing KILO release on powerpc

On Thu, Oct 08, 2015 at 11:08:06PM +0530, Rahul Arora wrote: > Hi Team > > I am trying to run Openstack KILO release on my powerpc platform.I am able > to cross compile all the KILO related packages using yocto framework.But > while running the following command i am getting below error messages.

[openstack-dev] [all][elections] Magum PTL Election Conclusion and Results

Hello all, Voting has now closed in the Magnum PTL election. Thanks again to Adrian and Hongbin for running. Please join me in extending congratulations Adrian in retaining is role as PTL. The results can be seen here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_306b9309f2f39e38

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Fri, Oct 02, 2015 at 03:34:47PM +1300, Robert Collins wrote: > On 2 October 2015 at 12:00, Kevin L. Mitchell > wrote: > > On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote: > >> On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote: > >> > It looks like

[openstack-dev] [Magnum]: PTL Voting is now open

If you are a Foundation individual member and had a commit in one of Magnum's projects[0] over the Kilo-Liberty timeframe (September 18, 2014 06:00 UTC to September 18, 2015 05:59 UTC) then you are eligible to vote. You should find your email with a link to the Condorcet page to cast your vote in

Re: [OpenStack-Infra] [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, Oct 01, 2015 at 05:48:25PM -0500, Kevin L. Mitchell wrote: > It looks like Pillow (pulled in by blockdiag, pulled in by > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > others) had a 3.0.0 release today, and now the gate is breaking because > libjpeg isn't available

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, Oct 01, 2015 at 05:48:25PM -0500, Kevin L. Mitchell wrote: > It looks like Pillow (pulled in by blockdiag, pulled in by > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > others) had a 3.0.0 release today, and now the gate is breaking because > libjpeg isn't available

[openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

Candidate proposals for the Technical Committee positions (6 positions) are now open and will remain open until October 1, 05:59 UTC. All candidacies must be submitted as a text file to the openstack/election repository as explained on the wiki[0]. Candidates for the Technical Committee

Re: [openstack-dev] [all][stable][release] 2015.1.2

On Wed, Sep 23, 2015 at 08:47:31PM -0400, Chuck Short wrote: > Hi, > > We would like to do a stable/kilo branch release, next Thursday. In order > to do that I would like to freeze the branches on Friday. Cut some test > tarballs on Tuesday and release on Thursday. Does anyone have an opinnon on

[openstack-dev] Election tools work session in Tokyo

Hi All, As most of you will have seen we used a gerrit based workflow for this PTL election (and will use the same system for the upcoming TC election). As a trial it went well, Tristan and I wrote a few tools to help the process along. However I'd like to take advantage of a work session in

Re: [openstack-dev] [all][gate] grende jobs failing.

On Thu, Sep 17, 2015 at 03:34:30PM +1000, Tony Breeds wrote: > On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote: > > Hi all, > > The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo. > > The > > juno global-requirements for Babel are

Re: [openstack-dev] [all][gate] grende jobs failing.

On Thu, Sep 17, 2015 at 06:22:47AM -0400, Davanum Srinivas wrote: > Tony, > Looks like the ban is holding up: > https://review.openstack.org/#/c/224429/ Sorry yes. Robert Collins pointed out that my new quicker plan wasn't going to work so we went back to the original ban 1.4.1 solution. It

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 10:05:20AM -0500, Douglas Mendizábal wrote: > I think someone jumped the gun on this thread. According to the wiki > [1] the cutoff time is not until 5:59 UTC, which > doesn't happen for another few hours. [2] > > Am I missing something? From the wiki[0]: --- Timeline

Re: [openstack-dev] [Nova] Design Summit Topics for Nova

On Wed, Sep 16, 2015 at 11:40:28AM -0700, melanie witt wrote: > Today I was informed that google forms are blocked in China [1], so I wanted > to mention it here so we can consider an alternate way to collect submissions > from those who might not be able to access the form. I'll act as an

[openstack-dev] [all][gate] grende jobs failing.

Hi all, The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo. The juno global-requirements for Babel are not compatible with kilo so nothing can get through grenade :( We're working it https://bugs.launchpad.net/oslo.utils/+bug/1496678 Yours Tony. [1]

Re: [openstack-dev] [all][gate] grende jobs failing.

On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote: > Hi all, > The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo. > The > juno global-requirements for Babel are not compatible with kilo so nothing can > get through grenade :( > > We'

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

On Tue, Sep 15, 2015 at 12:52:40PM -0400, Doug Hellmann wrote: > I've created the branches for oslo.utils and oslotest, as requested. > There are patches up for each to update the .gitreview file, which will > make it easier to land the patches to update whatever requirements > settings need to

[openstack-dev] [all][elections] Last hours for PTL candidate announcements

A quick reminder that we are in the last hours for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions on the wikipage and make sure we know your intentions: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 Make sure your candidacy have

[openstack-dev] [all][Elections] Nominations for OpenStack PTLs (Program Technical Leads) are now open

Nominations for OpenStack PTLs (Program Technical Leads) are now open and will remain open until September 17, 05:59 UTC. All candidacies must be submitted as a text file to the openstack/election repository as explained on the wiki[0]. In order to be an eligible candidate (and be allowed to

[openstack-dev] [ceilometerclient] Updating global-requirements caps.

Hi all, In trying to fix a few stable/juno issues we need to release a new version of ceilometerclient for stable/juno. This email is to try and raise awareness so that if the proposal is bonkers [1] we can come up with something better. This isn't currently possible due to the current caps

[openstack-dev] [oslo][release] stable/juno branch creation

On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote: > Tony, > > Thanks for digging into this! > > I should be able to help, but right now we're ramping up for the L3 > feature freeze and there are a lot of release-related activities going > on. Can this wait a few weeks for things to

Re: [openstack-dev] [all][Elections] Nominations for OpenStack PTLs (Program Technical Leads) are now open

On Fri, Sep 11, 2015 at 10:24:17AM +1000, Tony Breeds wrote: > Nominations for OpenStack PTLs (Program Technical Leads) are now open and will > remain open until September 17, 05:59 UTC. > > All candidacies must be submitted as a text file to the openstack/election > reposito

[openstack-dev] [libraries] gate-tempest-dsvm-neutron-src test and major version bumps

Hi All, We have the test in $subject that is used for most (if not all) libraries via the 'lib-forward-testing' job-group it's aim to to "test their proposed commits to ensure they don't break OpenStack on their next release." [1] This is of course a good idea. The problem I;'m having is

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

On Fri, Aug 28, 2015 at 11:12:43AM +1200, Robert Collins wrote: I'm pretty sure it *will* be EOL'd. OTOH thats 10 weeks of fixes folk can get. I think you should do it if you've the stomach for it, and if its going to help someone. I can aid by cutting library releases for you I think

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote: Tony, Thanks for digging into this! No problem. It seemed like such a simple thing :/ I should be able to help, but right now we're ramping up for the L3 feature freeze and there are a lot of release-related activities going

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

On Mon, Aug 24, 2015 at 08:03:38AM -0400, Davanum Srinivas wrote: Tony, +1 to open Bugs and Reviews. I'll help move things along. Hi Dims, I've created: https://bugs.launchpad.net/oslo.messaging/+bug/1488737 https://bugs.launchpad.net/oslo.utils/+bug/1488746

[openstack-dev] [oslo] Help with stable/juno branches / releases

Hi All, Firstly I apologise for the rambling nature of this email. There's a lot of context/data here and I'm not sure of the best way to present it. In [1] we discovered that stable/juno devstack is broken. After a little digging we opened [2] This required creating a stable/juno branch

Re: [openstack-dev] [openstack-deb] Devstack stable/juno fails to install

On Thu, Aug 20, 2015 at 02:12:44PM +0300, Eduard Matei wrote: Hi, ATM our workaround is to manually pip install futures==2.2.0 before running stack.sh Yeah that's what I did. You can also add that command to tools/fixup.sh Any idea when an official fix will be available? We're workign

Re: [openstack-dev] [openstack-deb] Devstack stable/juno fails to install

On Tue, Aug 18, 2015 at 10:04:56PM +, Jeremy Stanley wrote: On 2015-08-18 15:48:08 -0500 (-0500), Matt Riedemann wrote: [...] You'd also have to raise the cap on swiftclient in g-r stable/juno to python-swiftclient=2.2.0,2.4.0. [...] Followed by stable point releases of everything

Re: [openstack-dev] [openstack-deb] Devstack stable/juno fails to install

On Mon, Aug 17, 2015 at 03:51:46PM -0500, Matt Riedemann wrote: What version of taskflow is installed? Cinder 2014.2.3 requires this version of taskflow [1]: taskflow=0.4,0.7.0 Which should get you taskflow 0.6.2, and taskflow 0.6.2 has this requirement [2] for futures:

Re: [openstack-dev] [devstack] Restart openstack service

On Fri, Aug 14, 2015 at 04:00:23AM +, Guo, Ruijing wrote: I need to reboot hosts and restart openstack services. In this case, screen may not help. If you need to reboot the host then you shoudl re-run ./stack.sh Yours Tony. pgpVjQSWy881w.pgp Description: PGP signature

Re: [openstack-dev] [devstack] Restart openstack service

On Fri, Aug 14, 2015 at 11:31:07AM +0800, Rui Chen wrote: I use *screen* in devstack, Ctrl+c kill services, then restart it in console. Please try the following cmd in your devstack environment, and read some docs. *screen -r stack*

Re: [openstack-dev] [devstack] Restart openstack service

On Fri, Aug 14, 2015 at 04:01:20AM +, Guo, Ruijing wrote: Yes. I like this idea to restart all services including nova, neutron, cinder, etc:) You can *probably* use HOST=devstack.domain ./stack-smash.sh '.*' to restart all the services running under devstack. Note my list of windows

Re: [Openstack-operators] [openstack-dev] Gaining access to consoles.

On Mon, Aug 10, 2015 at 07:16:43PM -0600, Matt Fischer wrote: I'm not excited about making this the default until token revocations don't impact performance the way that they do now. I don't know how often this would get exercised though, but the impact of 100+ token revokes is noticeable on

Re: [Openstack-operators] [openstack-dev] Gaining access to consoles.

On Tue, Aug 11, 2015 at 08:24:10PM -0600, Matt Fischer wrote: It was covered some here: http://lists.openstack.org/pipermail/openstack-dev/2015-July/069658.html and some graphs here: http://www.mattfischer.com/blog/?p=672 tl;dr is that having revoked tokens affects keystone token validation

Re: [openstack-dev] [Openstack-operators] Gaining access to consoles.

On Mon, Aug 10, 2015 at 07:16:43PM -0600, Matt Fischer wrote: I'm not excited about making this the default until token revocations don't impact performance the way that they do now. I don't know how often this would get exercised though, but the impact of 100+ token revokes is noticeable on

Re: [openstack-dev] [Openstack-operators] Gaining access to consoles.

On Tue, Aug 11, 2015 at 08:24:10PM -0600, Matt Fischer wrote: It was covered some here: http://lists.openstack.org/pipermail/openstack-dev/2015-July/069658.html and some graphs here: http://www.mattfischer.com/blog/?p=672 tl;dr is that having revoked tokens affects keystone token validation

Re: [Openstack-operators] [openstack-dev] Gaining access to consoles.

On Mon, Aug 10, 2015 at 01:34:03PM -0400, Andrew Laski wrote: I'm only one data point, but we have a short TTL on tokens so it is not something that our users could reasonably due. And the Nova default TTL is 10 minutes, which is also out of bookmarking range IMO. So that's a good point. If

Re: [openstack-dev] Gaining access to consoles.

On Mon, Aug 10, 2015 at 01:34:03PM -0400, Andrew Laski wrote: I'm only one data point, but we have a short TTL on tokens so it is not something that our users could reasonably due. And the Nova default TTL is 10 minutes, which is also out of bookmarking range IMO. So that's a good point. If

[openstack-dev] Gaining access to consoles.

Hi All, Nova has bug: https://bugs.launchpad.net/nova/+bug/1447679 (service No-VNC (port 6080) doesn't require authentication). Which explains that if you know the 'token'[1] associated with an instances console you can get access to said console without otherwise proving that you should be

Re: [openstack-dev] How should we expose host capabilities to the scheduler

On Mon, Aug 03, 2015 at 04:49:59PM +0100, Alexis Lee wrote: Dugger, Donald D said on Mon, Aug 03, 2015 at 05:39:49AM +: Also note that, although many capabilities can be represented by simple key/value pairs (e.g. the presence of a specific special instruction) that is not true for all

Re: [openstack-dev] Segmentation Fault in nova-compute service on ARM platform.

On Thu, Jul 09, 2015 at 05:19:06PM +0530, Pradeep kumar wrote: Hi Hans, I did traced the function responsible for segmentation fault itz in file ceval.c. find below if (*next_instr == SETUP_FINALLY) { /* Make the last opcode before a try: finally:

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Thu, Jul 02, 2015 at 03:26:41AM +0200, Thomas Goirand wrote: Use the source, luke! Or write yourself a small shell script... I have, and I'm pretty sure that's where this conversation started. If you attempt to address this, you're making my life miserable. Please don't do it, thanks.

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Wed, Jul 01, 2015 at 03:28:06PM +, Ian Cordasco wrote: So for people using the clients to talk to arbitrary clouds from their personal computer (that can be running more than just linux) we need to fix this. The problem is that if the person is installing a wheel or using a new enough

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Wed, Jul 01, 2015 at 02:13:50PM +, Jeremy Stanley wrote: On 2015-07-01 12:08:46 +1000 (+1000), Tony Breeds wrote: Okay so I take you point no problem, but I'm not running distro packages and I still want completions. There must be a way to package the file to at least make it easier

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Wed, Jul 01, 2015 at 01:33:03PM +0200, Thomas Goirand wrote: The file has nothing to do in /usr/share/doc either. By per the debian policy manual: we shouldn't rely on /usr/share/doc, as it can be removed entirely by the users. /usr/share/python-novaclient could be a place, but really, the

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Wed, Jul 01, 2015 at 11:07:30PM +, Perry, Sean wrote: BTW, see dh_bash-completion from the debhelper package. When in doubt about packaging on a deb based distro look at the debhelper tools source (which is perl). -Original Message- From: Perry, Sean Sent: Wednesday, July

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On Wed, Jul 01, 2015 at 03:55:53AM +0200, Thomas Goirand wrote: Please don't do this. This is the kind of job to be done by package maintainers in distribution, because mostly, Python maintainers wouldn't know how to do things correctly. Here we've got a good example: the bash completion

[openstack-dev] [all][packaging] Adding files to /etc in a package

Hi All, I'm pretty new to this but I'll ask anyway. python-novaclient contains a bash completion script . When installed from pypi this script isn't packaged (and therefore it isn't installed). I created https://review.openstack.org/#/c/196919/ to gather feedback on: a) this this a thing we

[openstack-dev] [all] Gerrit based IRC meetings.

Hi All, We've been using the new gerrit based irc-meetings repo for about 3 week now. There have been teething troubles but by and large I think things are going well. People have identified some tooling changes/enhancements that we're workign on, buyt that's another thread. A couple of

Re: [OpenStack-Infra] Scheduling a monthly meeting

On Tue, Jun 16, 2015 at 04:00:52PM +0800, Tom Fifield wrote: Hi all, A couple of things I'm working on at the moment would like to meet on a monthly basis. From irc-meetings: Options for the `frequency` are `weekly`, `biweekly-even`, and `biweekly-odd` at the moment., and in

Re: [openstack-dev] Can not connect to host review.openstack.org port 29418

On Thu, Jun 11, 2015 at 11:33:14AM +0800, 苌智 wrote: I met problem when run git review. It says that ssh: connect to host review.openstack.org port 29418: No route to host . There is no response when I run telnet review.openstack.org 29418. And my screen only displays Trying

Re: [OpenStack-Infra] Nodepool for ubuntu vivid.

On Fri, Jun 05, 2015 at 11:49:58AM +1000, Ian Wienand wrote: There is not. First thing is probably to make it so diskimage-builder is creating vivid images (maybe it is already, I don't know) At that point, you should boot that image and try out the devstack-gate scripts to ensure that we

Re: [openstack-dev] [all] IRC meetings agenda is now driven from Gerrit !

On Fri, Jun 05, 2015 at 01:18:57AM +, Gareth wrote: As we could generate data dynamically, it is possible to develop a web UI for it which shows real-time and readable scheduler table, provides download link of custom meetings group, etc. Sure I'm working on the second part (albeit

Re: [openstack-dev] [all] IRC meetings agenda is now driven from Gerrit !

On Fri, May 29, 2015 at 10:42:58AM +0530, yatin kumbhare wrote: Great Work! New meetings or meeting changes would be proposed in Gerrit, and check/gate tests would make sure that there aren't any conflict. --Will this tell upfront, that in any given day of week, which are all meeting

Re: [openstack-dev] [all] IRC meetings agenda is now driven from Gerrit !

On Thu, May 28, 2015 at 01:18:01PM +0100, Daniel P. Berrange wrote: There are a huge number of openstack meetings now, but I think that each individual person will only be interested in a handful of them. Adding the irc-meetings.ical to a calendar app really pollutes your personal schedule,

Re: [openstack-dev] Add 'Ally Skills Workshop' to the sched.org Schedule.

On Thu, May 14, 2015 at 04:52:23PM +0200, Thierry Carrez wrote: So apparently the workshop has a max capacity of 40 people and folks have to register in advance - they can't just show up to the session without pre-registering. It would therefore be slightly counter-productive to add it the

[openstack-dev] [devstack] What's required to accept a new distro rlease?

Hi All, I have reasons but I need to use Ubuntu 15.04 and devstack. CLearly I can run: FORCE=yes ./stack.sh and with a couple of patches I get a devstack up and running *For my config/system* I'm wondering what are the requirements for accepting something like: -if [[ ! ${DISTRO} =~

Re: [openstack-dev] [devstack] What's required to accept a new distro rlease?

On Fri, May 15, 2015 at 01:35:06PM +1000, Ian Wienand wrote: On 05/15/2015 01:05 PM, Tony Breeds wrote: I'm wondering what are the requirements for accepting something like: -if [[ ! ${DISTRO} =~ (precise|trusty|7.0|wheezy|sid|testing|jessie|f20|f21|rhel7) ]]; then +if [[ ! ${DISTRO

[openstack-dev] Add 'Ally Skills Workshop' to the sched.org Schedule.

Hi All, Is there any chance we can get the Ally Skills Workshop added to the schedule (specifally the design summit schedule)? https://adainitiative.org/2015/04/register-now-ally-skills-workshop-at-openstack-summit-2015/ It'd be nice to see it on the schedule so I don't keep windering why

Re: [openstack-dev] [kolla] New Meeting Times Wednesday 1600UTC (even)/2200UTC (odd)

On Sun, May 10, 2015 at 08:49:11PM +, Steven Dake (stdake) wrote: I have closed the doodle poll for our new meeting times. We will be meeting in #openstack-meeting-3 (yes there is that much contention for our time slots – must be a reason ;). The times are: Weekly Wednesday 1600 UTC

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

On Thu, May 07, 2015 at 01:31:07PM +0300, Mikhail Dubov wrote: We have decided to stay in *#openstack-meeting* but have our meetings *on Mondays at 1400 UTC*. Hope that this time there will be no conflicts. We will also have the internal release meeting in *#openstack-rally* one hour before

Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

On Wed, May 06, 2015 at 12:11:16PM -0500, JJ Asghar wrote: Hey everyone! As we move forward with our big tent move[1] Jan suggested we move from our traditional IRC meeting in our main channel #openstack-chef to one of the official OpenStack meeting channels[2]. Sounds like a good idea :)

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

On Wed, May 06, 2015 at 05:09:07PM +0300, Mikhail Dubov wrote: many thanks for noticing it, I didn't see it for some reason while looking at the iCal file / checking the wiki. No problem. Seeing conflicts is non-trivial. with 90+meetings in 4+ IRC channels. We will use another time then.

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

On Tue, May 05, 2015 at 06:22:47PM +0300, Mikhail Dubov wrote: Hi Rally team, as mentioned in another message from me in this list, we have decided to use the meeting time on Wednesdays at 14:00 UTC for our *usual weekly meeting in #openstack-meeting*. This meeting time and channel will

Re: [openstack-dev] [nova] meaning of 'Triaged' in bug tracker

On Mon, Mar 30, 2015 at 10:00:44AM -0400, Sean Dague wrote: I've been attempting to clean up the bug tracker, one of the continued inconsistencies that are in the Nova tracker is the use of 'Triaged'. https://wiki.openstack.org/wiki/BugTriage If the bug contains the solution, or a patch,

Re: [openstack-dev] How to do once off/infrequent meetings?

On Wed, Mar 25, 2015 at 03:23:29PM +, Bailey, Darragh wrote: I was looking at using the meetings service (https://wiki.openstack.org/wiki/Meetings) to run and log a meeting on a stackforge project (git-upstream - http://git.openstack.org/cgit/stackforge/git-upstream), which seems to

[OpenStack-Infra] PTL election season?

Hi All, I have a quick question. I;m seeing some projects self announce candidates for PTL but I don't recall seeing a Election season is open email. Did I miss something or are these projects ahead of the game? Yours Tony. pgp9uHFcVIZA7.pgp Description: PGP signature

Re: [OpenStack-Infra] PTL election season?

On Thu, Mar 12, 2015 at 11:00:07PM +, Jeremy Stanley wrote: I'm not sure why this is an -infra ML topic, but from what I've seen those have all been unofficial projects which are trying to apply for official status with the TC under the new big tent model and as such need to meet the

Re: [openstack-dev] [nova] bp serial-ports *partly* implemented?

On Fri, Feb 20, 2015 at 06:03:46PM +0100, Markus Zoeller wrote: It seems to me that the blueprint serial-ports[1] didn't implement everything which was described in its spec. If one of you could have a look at the following examples and help me to understand if these observations are

Re: [openstack-dev] [cinder] qemu-img disk corruption bug to patch or not?

On Fri, Feb 20, 2015 at 12:40:34PM +0100, Philipp Marek wrote: Well, do you want fast or working/consistent images? Sure I often said I'll take slow and correct over fast and buggy anyday. Oh, okay... with the safe default being derived from the qemu version ;) Umm excuse my ignorance but

Re: [openstack-dev] [cinder] qemu-img disk corruption bug to patch or not?

On Fri, Feb 20, 2015 at 07:27:33AM +0100, Philipp Marek wrote: Potentially corrupted images are bad; depending on the affected data it might only be diagnosed some time after installation, so IMO the fix is needed. Sure but there is a (potentially hefty) performance impact. Only a minor

[openstack-dev] [cinder] qemu-img disk corruption bug to patch or not?

Hi all, In September I started working on a simple (but controvertial) fix in nova[1] to avoid some disk corruption issues. John kindly ran with a similar fix to cinder[2]. John's review ended up in merge conflict so I tried my own version [3]. While (trying) to add workarounds to nova

Re: [openstack-dev] [nova][libvirt] Block migrations and Cinder volumes

On Mon, Feb 16, 2015 at 01:39:21PM +1300, Robert Collins wrote: Just ran across this from bug https://bugs.launchpad.net/nova/+bug/1398999. Is there some way to signal to libvirt that some block devices shouldn't be migrated by it but instead are known to be networked etc? Or put another way,

<    2   3   4   5   6   7   8   >