Re: [openstack-dev] Can I change the username for review.openstack.org?

review.openstack.org use lauchpad to login, you could change your setting here: https://login.launchpad.net/ On 2015年03月18日 13:41, Lily.Sing wrote: Hi all, I follow the account setup steps here and it says the username fo

[openstack-dev] Can I change the username for review.openstack.org?

Hi all, I follow the account setup steps here and it says the username for review.openstack.org should be the same as launchpad. But I input a mismatch one by mistake. Does it still work? If not, how can I change it? Thanks! B

Re: [openstack-dev] [murano] PTL elections

The PTL candidacy proposal time frame ended and we have only one candidate. So, Serg Melikyan, my congratulations! Results documented in https://wiki.openstack.org/wiki/Murano/PTL_Elections_Kilo_Liberty#PTL On Wed, Mar 11, 2015 at 2:04 AM, Sergey Lukjanov wrote: > Hi folks, > > due to the requ

[openstack-dev] [Sahara][Horizon] Can't open "Data Processing" panel after update sahara & horizon

Hi all, I'm working under Ubuntu14.04 with devstack. After the fresh devstack installation, I run a integration test to test the environment. After the test, cluster and tested edp jobs remains in my environment. Then I updated sahara to the lasted code. To make the newest code work, I also did

Re: [openstack-dev] [Horizon][DOA] Extending OpenStack Auth for new mechanisms (websso, kerberos, k2k etc)

- Original Message - > From: "Douglas Fish" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, March 18, 2015 2:07:56 AM > Subject: Re: [openstack-dev] [Horizon][DOA] Extending OpenStack Auth for new > mechanisms (websso, kerberos, k2k etc) > >

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

Hi Tim, I posted this comment on the doc. I am still pondering over a possibility of have a policy-driven scheduler workflow via the Solver Scheduler placement engine, which is also LP based like you describe in your doc. I know in your initial meeting, you plan to go over your proposal of buil

[openstack-dev] Gerrit downtime on 2015-03-21

Hi, Gerrit will be unavailable for a few hours starting at 1500 UTC on Saturday, March 21. Also, as Jeremy indicated in this email, its IP address will be changing: http://lists.openstack.org/pipermail/openstack-infra/2015-February/002425.html If you use Gerrit from a network with egress filt

Re: [openstack-dev] [Kolla] PTL Candidacy

Congratulations Steve! Regards, Daneyon Hansen Software Engineer Email: daneh...@cisco.com Phone: 303-718-0400 http://about.me/daneyon_hansen From: Angus Salkeld mailto:asalk...@mirantis.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@list

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

The voting here is now closed. The final count looks like: 1400UTC: 5 votes (3 core reviewers) 1500UTC: 6 votes (one core reviewer) Both: 5 votes (all core reviewers) Adding in some more subtle aspects like the ones mentioned in the previous email and the preference strength mentioned in the vo

Re: [openstack-dev] [Kolla] PTL Candidacy

There have been no other candidates within the allowed time, so congratulations Steve on being the new Kolla PTL. Regards Angus Salkeld On Thu, Mar 12, 2015 at 8:13 PM, Angus Salkeld wrote: > Candidacy confirmed. > > -Angus > > On Thu, Mar 12, 2015 at 6:54 PM, Steven Dake (stdake) > wrote: >

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

On 03/17/2015 04:17 PM, Robert Collins wrote: > On 17 March 2015 at 23:48, Sean Dague wrote: >> On 03/16/2015 10:56 PM, Robert Collins wrote: > ... >>> Better at the cost of forcing all existing users to upgrade just to >>> keep using code of their own that already worked. >>> >>> Not really 'bett

Re: [openstack-dev] [Keystone][FFE] - IdP ID (remote_id) registration and validation

I'd also be happy to sponsor this work. Thanks, Steve Martinelli OpenStack Keystone Core Marek Denis wrote on 03/17/2015 06:28:58 PM: > From: Marek Denis > To: > Date: 03/17/2015 06:35 PM > Subject: [openstack-dev] [Keystone][FFE] - IdP ID (remote_id) > registration and validation > > Hell

[openstack-dev] [Keystone][FFE] - IdP ID (remote_id) registration and validation

Hello, One very important feature that we have been working on in the Kilo development cycle is management of remote_id attributes tied to Identity Providers in keystone. This work is crucial for: - Secure OpenStack identity federation configuration. User is required to specify what Identi

[openstack-dev] Barbican : Unable to create the container with the POST request using the CURL command

Hi Douglas , Thanks a lot for your help .It worked . -- *Thanks and Regards,* *Asha Seshagiri* __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u

Re: [openstack-dev] [fuel] fuel-utils package

Andrew We would very appreciate if you figured it out. It is really easy to test - just migrate l3 agent and see whether OVS datapath to l3 agent MAC address switched to different port - it should digest gratuitous ARPs correctly. Otherwise, we will still need to flush database on migration of age

Re: [openstack-dev] [qa][neutron] Moving network api test development to Neutron repo

With the API tests being now available in the neutron repository - and being actively developed, I would also mandate in reviews that API tests are provided in lieu of the usual unit tests which at the end of the day do what the API tests are supposed to do. This will provide better validation, an

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

On 03/17/2015 02:33 PM, Joe Gordon wrote: Digging up this old thread because I am working on getting multi node live migration testing working (https://review.openstack.org/#/c/165182/), and just ran into this issue (bug 1398999). And I am not sure I agree with this statement. I think there is

[openstack-dev] [qa][neutron] Moving network api test development to Neutron repo

tl;dr; As per a discussion in Paris [1], development of Neutron's API tests is moving from the Tempest repo to the Neutron repo. If you are developing API tests for Neutron in Tempest, please be advised that, effective immediately, your efforts should be directed towards the Neutron repo. The curr

Re: [openstack-dev] [puppet] Release management and bug triage

Comments inline. On Tue, Mar 17, 2015 at 12:22 PM, Emilien Macchi wrote: > Hi, > > I wanted to start the discussion here about our bug/release management > system with Launchpad. > > A first question that comes in my mind is: should we continue to manage > every Puppet module in a different Laun

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

I will like to participate in the discussions. Thanks, Yathi. On 3/16/15, 11:05 AM, "Tim Hinrichs" mailto:thinri...@vmware.com>> wrote: Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone

[openstack-dev] [Keystone][FFE] - Reseller Implementation

Hi Folks, We’ve discussed a lot in the last Summit about the Reseller use case. OpenStack needs to grow support for hierarchical ownership of objects.This enables the management of subsets of users and projects in a way that is much more comfortable for private clouds, besides giving to public clo

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

On Thu, Jun 19, 2014 at 1:38 AM, Daniel P. Berrange wrote: > On Wed, Jun 18, 2014 at 11:09:33PM -0700, Rafi Khardalian wrote: > > I am concerned about how block migration functions when Cinder volumes > are > > attached to an instance being migrated. We noticed some unexpected > > behavior recen

Re: [openstack-dev] Deprecation warnings considered harmful?

On 18 March 2015 at 05:22, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 ... > That relatively short-lived issue already resulted in multiple > backports to stable branches with new namespaces being used. F.e. see: > > https://bugs.launchpad.net/nova/+bug/1432685 > > The

Re: [openstack-dev] [all] Capability Discovery API

> On Mar 17, 2015, at 1:02 PM, Davis, Amos (PaaS-Core) > wrote: > > All, > The Application EcoSystem Working Group realized during the mid-cycle meetup > in Philadelphia that there is no way to get the capabilities of an Openstack > cloud so that applications can measure their compatibility a

Re: [openstack-dev] [Keystone] Requesting FFE for last few remaining patches for domain configuration SQL support

On 03/17/2015 01:26 PM, Henry Nash wrote: Hi Prior to Kilo, Keystone supported the ability for its Identity backends to be specified on a domain-by-domain basis - primarily so that different domains could be backed by different LDAP servers. In this previous support, you defined the domain-sp

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

On 17 March 2015 at 23:48, Sean Dague wrote: > On 03/16/2015 10:56 PM, Robert Collins wrote: ... >> Better at the cost of forcing all existing users to upgrade just to >> keep using code of their own that already worked. >> >> Not really 'better' IMO. Different surely. >> >> We could (should) add

Re: [openstack-dev] [UX] contribution

Hi Liz. Thank you for your email. I will ping you in case I have a question. In the meantime I will check trystack.org. Regards, Luke On 17 March 2015 at 18:51, Liz Blanchard wrote: > Hi Luke, > > Thanks for your interest in OpenStack UX! > > Piet - would you be able to add Luke to the OpenSta

[openstack-dev] [all] Capability Discovery API

All, The Application EcoSystem Working Group realized during the mid-cycle meetup in Philadelphia that there is no way to get the capabilities of an Openstack cloud so that applications can measure their compatibility against that cloud. In other words, if we create an Openstack App Marketplac

[openstack-dev] [Keystone] Requesting FFE for last few remaining patches for domain configuration SQL support

Hi Prior to Kilo, Keystone supported the ability for its Identity backends to be specified on a domain-by-domain basis - primarily so that different domains could be backed by different LDAP servers. In this previous support, you defined the domain-specific configuration options in a separate c

[openstack-dev] [puppet] Release management and bug triage

Hi, I wanted to start the discussion here about our bug/release management system with Launchpad. A first question that comes in my mind is: should we continue to manage every Puppet module in a different Launchpad project? Or should we migrate all modules to a single project. So far this is wha

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

On Mon, Mar 16, 2015 at 6:06 PM, Ken'ichi Ohmichi wrote: > Hi Sean, > > 2015-03-16 23:15 GMT+09:00 Sean Dague : > > Our current top level shipped example paste.ini for Nova includes the > > following set of endpoint definitions: > > > > [composite:osapi_compute] > > use = call:nova.api.openstack.

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

I will also be glad to participate. Thanks, Ramki From: ruby.krishnasw...@orange.com [mailto:ruby.krishnasw...@orange.com] Sent: Tuesday, March 17, 2015 5:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

Re: [openstack-dev] [fuel] fuel-utils package

On Tue, Mar 17, 2015 at 12:58 AM, Vladimir Kuklin wrote: > Andrew > > Thank you for pointing this out. We are working on packaging all of the > fuel library components right now. We will make it happen in a couple of > weeks - me and other guys are currently working on > https://blueprints.launch

[openstack-dev] [release] oslo.db 1.7.1

The Oslo team is thrilled to announce the release of: oslo.db 1.7.1: oslo.db library This is a patch release intended for use with the Kilo series of projects. For more details, please see the git log history below and: http://launchpad.net/oslo.db/+milestone/1.7.1 Please report issues thr

Re: [openstack-dev] [Fuel] FFE python-fuelclient improvements

Roman, it would be great if you share the links. Thanks! On Tue, Mar 17, 2015 at 5:52 AM, Igor Kalnitsky wrote: > Yep, I think we can do merge them. +1 from my side. > > On Tue, Mar 17, 2015 at 12:50 PM, Evgeniy L wrote: > > +1, because those patches are simple don't look destructive. > > > > O

Re: [openstack-dev] [UX] contribution

Hi Luke, Thanks for your interest in OpenStack UX! Piet - would you be able to add Luke to the OpenStack Invision account? After you are added you will be able to see and comment on any designs we’ve posted so far for review. You can of course post any of your own designs for review as well.

[openstack-dev] Feature Freeze request for DB2 support in Trove

Hello, I would like to request a feature freeze for Trove for the following feature: Add DB2 support for Trove ( https://blueprints.launchpad.net/openstack/?searchtext=db2-plugin-for-trove ) These are the patches related to this blueprint: - https://review.openstack.org/#/c/164293/ - https:/

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/17/2015 05:22 PM, Ihar Hrachyshka wrote: > On 03/13/2015 04:36 PM, Doug Hellmann wrote: > > >> On Fri, Mar 13, 2015, at 07:25 AM, Ihar Hrachyshka wrote: On >> 03/13/2015 01:37 AM, Nikhil Manchanda wrote: > Looking back at the meeting eaves

[openstack-dev] Hyper-V Meeting Minutes

Hi All, Minutes from this weeks IRC meeting can be found here: Meeting ended Tue Mar 17 16:23:45 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-03-17-16.01.html Minutes (text):

Re: [openstack-dev] Deprecation warnings considered harmful?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2015 04:36 PM, Doug Hellmann wrote: > > > On Fri, Mar 13, 2015, at 07:25 AM, Ihar Hrachyshka wrote: On > 03/13/2015 01:37 AM, Nikhil Manchanda wrote: Looking back at the meeting eavesdrop, the primary reasons why we deferred this w

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

+1 for consistent time & 1400UTC is a bit more preferred. -Original Message- From: Cindy Pallares [mailto:cpalla...@redhat.com] Sent: Tuesday, March 17, 2015 4:29 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Glance] Proposal to change Glance meeting time. +1 for

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

+1 for consistent time and a slightly higher preference for 1500 UTC On 03/17/2015 02:15 AM, Koniszewski, Pawel wrote: +1 for consistent time (I prefer 1400UTC) *From:*Fei Long Wang [mailto:feil...@catalyst.net.nz] *Sent:* Sunday, March 15, 2015 9:00 PM *To:* openstack-dev@lists.openstack.org *

Re: [openstack-dev] [nova] looking for feedback on object versioning

On 03/16/2015 03:23 AM, Sylvain Bauza wrote: Le 14/03/2015 01:13, Chris Friesen a écrit : 1) Do I need to do anything special in obj_make_compatible()? Yes, you need to make sure that you won't provide the new field to a previous version of Service object. See other examples on other objects

Re: [openstack-dev] [Horizon][DOA] Extending OpenStack Auth for new mechanisms (websso, kerberos, k2k etc)

Steve Martinelli wrote on 03/17/2015 12:52:33 AM: > From: Steve Martinelli > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 03/17/2015 12:55 AM > Subject: Re: [openstack-dev] [Horizon][DOA] Extending OpenStack Auth > for new mechanisms (websso, kerberos, k2k etc

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

On 17 March 2015 at 14:44, Carl Baldwin wrote: > > On Mar 15, 2015 6:42 PM, "Salvatore Orlando" > > * the ML2 plugin overrides several methods from the base "db" class. > From what I gather from unit tests results, we have not yet refactored it. > I think to provide users something usable in Kilo

Re: [openstack-dev] [Magnum] Plans for heat-containers

Excellent news . I am interested Zee On Tue, Mar 17, 2015 at 3:26 PM, Adrian Otto wrote: > Team, > > Steven Dake and I met with Lars Kellogg-Stedman about introducing a new > Stackforge project named heat-container that will use heat-kubernetes at > the initial upstream repo. Magnum contributo

[openstack-dev] [Ironic] Weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Note that the weekly subteam status report wasn't discussed in yesterday's weekly Ironic meeting. The meeting focus was on kilo-3. Bugs (dtantsur) (As of Tu

[openstack-dev] [Magnum] Plans for heat-containers

Team, Steven Dake and I met with Lars Kellogg-Stedman about introducing a new Stackforge project named heat-container that will use heat-kubernetes at the initial upstream repo. Magnum contributors currently working on the templates will be added to this project, and we will treat it as a libra

Re: [openstack-dev] [TripleO][Tuskar] Common library for shared code

On 16/03/15 16:38, Ben Nemec wrote: On 03/13/2015 05:53 AM, Jan Provaznik wrote: On 03/10/2015 05:53 PM, James Slagle wrote: On Mon, Mar 9, 2015 at 4:35 PM, Jan Provazník wrote: Hi, it would make sense to have a library for the code shared by Tuskar UI and CLI (I mean TripleO CLI - whatever i

Re: [openstack-dev] [OSSG] Announcement: I'll be transitioning away from OpenStack

This is a big loss to the community, it’s been a real pleasure working with you over the last three years and I wish you all the best in the future! -Rob From: Bryan D. Payne [mailto:bdpa...@acm.org] Sent: 16 March 2015 21:53 To: OpenStack Development Mailing List Subject: [openstack-dev]

[openstack-dev] [oslo][pbr] fixing up pbr's master branch

Now that we have good processes in place for the other Oslo libraries, I want to bring pbr into the fold so to speak and start putting it through the same reviews and release procedures. We also have some open bugs that I'd like to find someone to help fix, but because we can't actually release fro

Re: [openstack-dev] [opnfv-tech-discuss] [Keystone][Multisite] Huge token size

On 03/17/2015 02:51 AM, joehuang wrote: It’s not reality to deploy KeyStone service ( including backend store ) in each site if the number, for example, is more than 10. The reason is that the stored data including data related to revocation need to be replicated to all sites in synchronizat

Re: [openstack-dev] [opnfv-tech-discuss] [Keystone][Multisite] Huge token size

On 03/17/2015 03:30 AM, David Chadwick wrote: Encryption per se does not decrease token size, the best it can do is keep the token size the same size. So using Fernet tokens will not on its own alter the token size. Fernet is striking a blanace. It is encruypting a subset of the data. Not th

Re: [openstack-dev] [nova] Block Device Mapping is Invalid error

Hello once more! It turned out that proper "body" arg will be generated if you add another --block-device param with source=image like this: nova boot qwe --flavor vm1 --image cent-os7-vm --block-device id=0af1f5a8-8172-4936-a958-90486759d598,source=volume,dest=volume,device=sdb,bootindex=1

Re: [openstack-dev] [Neutron] IPAM reference driver status and other stuff

On Mar 15, 2015 6:42 PM, "Salvatore Orlando" > * the ML2 plugin overrides several methods from the base "db" class. From what I gather from unit tests results, we have not yet refactored it. I think to provide users something usable in Kilo we should ensure the ML2 plugin at least works with the IP

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On 03/17/2015 09:07 AM, Monty Taylor wrote: > On 03/16/2015 08:32 PM, Robert Collins wrote: >> On 17 March 2015 at 13:22, Doug Hellmann wrote: >>> Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300: I've raised this in reviews 157135 and 153966, but I think it deserves a

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On 03/16/2015 08:32 PM, Robert Collins wrote: > On 17 March 2015 at 13:22, Doug Hellmann wrote: >> Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300: >>> I've raised this in reviews 157135 and 153966, but I think it deserves >>> a thread of its own. >>> >>> I think universal whee

Re: [openstack-dev] [Fuel] FFE python-fuelclient improvements

Yep, I think we can do merge them. +1 from my side. On Tue, Mar 17, 2015 at 12:50 PM, Evgeniy L wrote: > +1, because those patches are simple don't look destructive. > > On Mon, Mar 16, 2015 at 7:43 PM, Roman Prykhodchenko wrote: >> >> Hi folks, >> >> due to some technical issues we were unable

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

Hi I'd like to participate. By when will you fix the meeting date ? Ruby De : Tim Hinrichs [mailto:thinri...@vmware.com] Envoyé : lundi 16 mars 2015 19:05 À : OpenStack Development Mailing List (not for usage questions) Objet : [openstack-dev] [Congress] [Delegation] Meeting scheduling Hi all,

Re: [openstack-dev] [Fuel] FFE python-fuelclient improvements

+1, because those patches are simple don't look destructive. On Mon, Mar 16, 2015 at 7:43 PM, Roman Prykhodchenko wrote: > Hi folks, > > due to some technical issues we were unable to merge Cliff integration > patches to keep ISO build jobs alive. > Since now the problem is fixed and we are unbl

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

On 03/16/2015 10:56 PM, Robert Collins wrote: > On 17 March 2015 at 14:27, Ken'ichi Ohmichi wrote: > >>> I am worried about SDKs making requests that have additional JSON >>> attributes that were previously ignored by v2, but will be considered >>> invalid by the v2.1 validation code. If we were

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On Tue, Mar 17 2015, Julien Danjou wrote: > I'll try to write a patch on pbr to fix that. https://review.openstack.org/#/c/165015/ should fix that; tested against my Gnocchi patch and seems to do the trick. -- Julien Danjou # Free Software hacker # http://julien.danjou.info signature.asc Desc

Re: [openstack-dev] [opnfv-tech-discuss] [Keystone][Multisite] Huge token size

On Tuesday, March 17, 2015, David Chadwick wrote: > Encryption per se does not decrease token size, the best it can do is > keep the token size the same size. Correct. > So using Fernet tokens will not on > its own alter the token size. Reducing the size must come from putting > less informat

[openstack-dev] Cross-Project meeting, Tue March 17th, 21:00 UTC

Dear PTLs, cross-project liaisons and anyone else interested, We'll have a (likely short) cross-project meeting today at 21:00 UTC, with the following agenda: * Progress on Swift and Keystone developing next (incompatible) version of client libs in openstack-sdk * openstack-specs discussion * A

Re: [openstack-dev] [fuel] Fuel meeting participation.

> On 17 Mar 2015, at 01:12, Andrew Woodward wrote: > > The last couple of meetings have been visibly low on participation. Most > notably anyone not involved with the planned schedule is not participating. > Often I find that the discussion leeds to wanting to talk with more of the > devs, bu

Re: [openstack-dev] release note items ??

Manickam, Kanagaraj wrote: > Is there any process we follow to create the release notes (ex: > https://wiki.openstack.org/wiki/ReleaseNotes/Juno) for each release of > OpenStack, by collection details across different projects in OpenStack.? The release notes (see [1] for Kilo) are edited as a wik

Re: [openstack-dev] [keystone][congress][group-policy] Fetching policy from a remote source

Hi Adam prior art is the publish-subscribe mechanism. I dont know if Keystone already has this implemented or not, or if Python implementation exists or not, without doing some research regards David On 16/03/2015 18:08, Sumit Naiksatam wrote: > On Mon, Mar 16, 2015 at 8:10 AM, Adam Young wro

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On Tue, Mar 17 2015, Robert Collins wrote: > I think we should deprecate and remove the requirements-pyN files and > instead use environment markers directly in requirements.txt. That > will then flow into wheels and things should just work (plus we can > delete more pbr code). > > I haven't teste

Re: [openstack-dev] [opnfv-tech-discuss] [Keystone][Multisite] Huge token size

Hi Adam, The Fernet token and Project Kite looks very interesting, I think it might be helpful to work together to tackle the problem, shall we put this issue to the keystone design summit for further follow up discussion? On Tue, Mar 17, 2015 at 3:30 PM, David Chadwick wrote: > Encryption per

Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization Questions

Hi John, Thanks for your opinion. Fundamentally we cannot assume infinite storage space. To enhance the shelve/unshelve performance, I have proposed nova-specs [1], in which there are two challenges. A. This design is libvirt specific, currently I am using KVM hypervisor but I am open to make

Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization Questions

Hi John, Thanks for your opinion. Fundamentally we cannot assume infinite storage space. To enhance the shelve/unshelve performance, I have proposed nova-specs [1], in which there are two challenges. A. This design is libvirt specific, currently I am using KVM hypervisor but I am open to make

Re: [openstack-dev] [fuel] fuel-utils package

Andrew Thank you for pointing this out. We are working on packaging all of the fuel library components right now. We will make it happen in a couple of weeks - me and other guys are currently working on https://blueprints.launchpad.net/fuel/+spec/package-fuel-components to clean up our make system

Re: [openstack-dev] [opnfv-tech-discuss] [Keystone][Multisite] Huge token size

Encryption per se does not decrease token size, the best it can do is keep the token size the same size. So using Fernet tokens will not on its own alter the token size. Reducing the size must come from putting less information in the token. If the token recipient has to always go back to Keystone

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

+1 for consistent time (I prefer 1400UTC) From: Fei Long Wang [mailto:feil...@catalyst.net.nz] Sent: Sunday, March 15, 2015 9:00 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Glance] Proposal to change Glance meeting time. +1 for consistent time On 14/03/15 10:11,

Re: [openstack-dev] [TripleO] QuintupleO Overview

> On 17 March 2015 at 09:30, Ben Nemec > wrote: > > So I've successfully done a deployment to a QuintupleO environment. \o/ > > \o/ > Great news! Congrats! @Ben, are you planning to keep it up-to-date or create repo with README? I would also like to be involved in "TripleO wasn't confusing eno