[openstack-dev] [Keystone] Token invalidation in deleting role assignments

Hi all, When deleting role assignments, not only tokens that are related with deleted role assignments but also other tokens that the(same) user has are invalidated in stable/icehouse(2014.1.1). For example, A) Role assignment between domain and user by OS-INHERIT(*1) 1. Assign a role(For example

Re: [openstack-dev] [Neutron][ServiceVM] servicevm IRC meeting reminder (June 28 Tuesday 5:00(AM)UTC-)

As action items, I've moved API spec to google-doc until stackforge repo is created. Here is the link https://docs.google.com/document/d/10v818QsHWw5lSpiCMfh908PAvVzkw7_ZUL0cgDiH3Vk/edit?usp=sharing thanks, On Mon, Jun 23, 2014 at 11:25:03PM +0900, Isaku Yamahata wrote: > Hi. This is a reminde

Re: [openstack-dev] [Fuel] Support for plugins in fuel client

As i mentioned cliff uses similar approach, extending app by means of entry points, and written by same author. So i think stevedore will be used in cliff, or maybe already used in newer versions. But apart of stevedore-like dynamic extensions - cliff provides modular layers for cli app, it is kind

Re: [openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

On Tue, Jun 24, 2014 at 9:54 PM, Adrian Otto wrote: > Hello, > > Solum has run into a constraint with the current scheme for requirements > management within the OpenStack CI system. We have a proposal for dealing > with this constraint that involves making a contribution to openstack-infra. >

[openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

Hello, Solum has run into a constraint with the current scheme for requirements management within the OpenStack CI system. We have a proposal for dealing with this constraint that involves making a contribution to openstack-infra. This message explains the constraint, and our proposal for addre

Re: [openstack-dev] [Nova] [ironic]nova scheduler and ironic

On Jun 24, 2014 7:02 PM, "Jander lu" wrote: > > hi, guys, I have two confused issue when reading source code. > > 1) can we have ironic driver and KVM driver both exist in the cloud? for example, I have 8 compute nodes, I make 4 of them with compute_driver = libvirt and remaining 4 nodes with comp

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi, I second Stephen's suggestion with the status matrix. I have heard of (provisional) status, operational status, admin status -- I am curious what states exists and how an object would transition between them. Libra uses only one status field and it transitions as follows: BUILDING -> ACTI

[openstack-dev] [Neutron] validation of input against column-size specified in schema

Hi, Is there any way in current neutron codebase that can be used to validate the length of a string attribute against the max column size specified in the schema for that attribute. E.g. , in models_v2.py class Network(model_base.BASEV2, HasId, HasTenant): """Represents a v2 neutron network

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

Updated numbers from the end of the day: startdelta from 2014-06-17mid-daydelta from startenddelta from startdelta from 2014-06-17New17517011-6-1Incomplete25-621-422-3-9Critical/High for 5.1 140 135-528Critical/High for 5.1, Confirmed Triaged92 87-584-8 Medium/Low/Undefined for 5.1, Confirmed/Tr

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Alright y'all have convinced me for now. How the status is show on shared entities is still yet to be determined. However, we don't have any shared entities (unless we really want health monitors shareable right now) at this point so the status won't get complicated for this first iteration. Th

[openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

Hi all, I'm developing a new mechanism driver. I'd like to access ml2-related tables in create_port_precommit and create_port_postcommit. However I find it hard to do that because the two functions are both inside an existed database transaction defined in create_port function of ml2/plugin.py.

Re: [openstack-dev] [neutron][nova] nova needs a new release of neutronclient for OverQuotaClient exception

On Tue, 24 Jun 2014 02:46:33 PM Kyle Mestery wrote: > On Mon, Jun 23, 2014 at 11:08 AM, Kyle Mestery > > wrote: > > On Mon, Jun 23, 2014 at 8:54 AM, Matt Riedemann > > > > wrote: > >> There are at least two changes [1][2] proposed to Nova that use the new > >> OverQuotaClient exception in pytho

Re: [openstack-dev] [Keystone] Announcing Keystone Middleware Project

I expect that we will be releasing the 1.0.0 shortly here (or at the very least an alpha so we can move forward) to make sure we have time get the new package in use during Juno. As soon as we have something released (should be very soon), I’ll make sure we give a heads up to all the packagers.

Re: [openstack-dev] [Keystone] Announcing Keystone Middleware Project

On 25/06/14 07:24, Morgan Fainberg wrote: The Keystone team would like to announce the official split of python-keystoneclient and the Keystone middleware code. Over time the middleware (auth_token, s3_token, ec2_token) has developed into a fairly expansive code base and includes dependencies tha

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

Hi, Le 2014-06-24 20:12, Joe Gordon a écrit : Finally, assuming the customer had access to this 'unknown' state information, what would he be able to do with it ? Usually he has no lever to 'evacuate' or 'recover' the VM. All he could do is spawn another instance to replace the

Re: [openstack-dev] [Infra] Meeting Tuesday June 24th at 19:00 UTC

On Mon, Jun 23, 2014 at 9:39 AM, Elizabeth K. Joseph wrote: > Hi everyone, > > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting on Tuesday June 24th, at 19:00 UTC in #openstack-meeting Meeting minutes and log available here: Minutes: http://eavesdrop.openstack.org/meeti

Re: [openstack-dev] [All] Tempest testing for master is now running on Trusty

On Tue, Jun 24, 2014 at 8:49 PM, Clark Boylan wrote: > Hello everyone, > > The Infra team switched all Tempest testing (really all jenkins jobs > with names containing 'dsvm') for the master branch to Trusty slaves > today. This means that integration testing has access to new libvirt, > new mongo

[openstack-dev] [Nova] [ironic]nova scheduler and ironic

hi, guys, I have two confused issue when reading source code. 1) can we have ironic driver and KVM driver both exist in the cloud? for example, I have 8 compute nodes, I make 4 of them with compute_driver = libvirt and remaining 4 nodes with compute_driver=nova.virt.ironic.IronicDriver ? 2) if it

Re: [openstack-dev] [hacking] rules for removal

On 25/06/14 07:26, Mark McLoughlin wrote: > There's two sides to this coin - concern about alienating > non-english-as-a-first-language speakers who feel undervalued because > their language is nitpicked to death and concern about alienating > english-as-a-first-language speakers who struggle to un

[openstack-dev] [All] Tempest testing for master is now running on Trusty

Hello everyone, The Infra team switched all Tempest testing (really all jenkins jobs with names containing 'dsvm') for the master branch to Trusty slaves today. This means that integration testing has access to new libvirt, new mongodb, and new kernels among other things. Python27 unittesting for

Re: [openstack-dev] [Neutron] default security group rules in neutron

hi Mathieu: Glad to see there are a lot of people who are seeking solutions to address this issue (it's very great that you have already done some jobs), and I couldn’t wait to see this feature involved in upstream as soon as possible. So that, we could make it benefit to everyone. 2014-06-24 4:5

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Stephen, > Ultimately, as we will have several objects which have many-to-many > relationships with other objects, the 'status' of an object that is shared > between what will ultimately be two separate physical entities on the > back-end should be represented by a dictionary, and any 'reduc

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Ultimately, as we will have several objects which have many-to-many relationships with other objects, the 'status' of an object that is shared between what will ultimately be two separate physical entities on the back-end should be represented by a dictionary, and any 'reduction' of this on behalf

Re: [openstack-dev] [Neutron] default security group rules in neutron

Hi Lingxian, I've definitely experienced this problem first hand when new tenants are allowed access to our openstack cloud. I understand that nova has an extension to do this but I'm curious if part of the tenant onboarding script if the desired security group rules could be set. I'm not opposed

[openstack-dev] [nova][pci] A couple of questions

Hi, Robert, Irenab does your patches are properly seting up the topic, like pci-passthrough-sriov? all SRIOV patch need this tag i think , help people find this set of patch to review. https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/pci-passthrough-s

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

I don't think we should be flipping states for instances on a potentially downed compute. We definitely should not set an instance to ERROR. I think a time associated with the last power state check might be nice and be good enough. - Chris > On Jun 24, 2014, at 5:17 PM, Joe Gordon wrote: >

Re: [openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

Making sure all drivers support the features offered in Neutron LBaaS means we are stuck going with the 'least common denominator' in all cases. While this ensures all vendors implement the same things in the functionally the same way, it also is probably a big reason the Neutron LBaaS project has

Re: [openstack-dev] [DevStack] neutron config not working

On 25/06/14 10:59, Rob Crittenden wrote: Before I get punted onto the operators list, I post this here because this is the default config and I'd expect the defaults to just work. Running devstack inside a VM with a single NIC configured and this in localrc: disable_service n-net enable_service

[openstack-dev] [Mistral] Small questions re executor

Got some questions while fixing a bug https://review.openstack.org/#/c/102391/: * We must convey the action ERROR details back to the engine, and to the end user. Log is not sufficient. How exactly? Via context? Via extra parameters to convey_execution_results? Need a field in the model. https:

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Tue, Jun 24, 2014 at 5:12 PM, Joe Gordon wrote: > > > > On Tue, Jun 24, 2014 at 4:16 PM, Ahmed RAHAL wrote: > >> Le 2014-06-24 17:38, Joe Gordon a écrit : >> >>> >>> On Jun 24, 2014 2:31 PM, "Russell Bryant" >> > wrote: >>> >> >> > There be dragons here. Just bec

Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be set through separate API/model?

Evgeny-- Two minor nits: * Your spec lists the new SNI related settings 'sni_list' (and it contains more than just IDs, so calling it 'sni_container_ids_list' is misleading). Please be precise in the terms you use, and don't switch them mid discussion. :) * Also, I personally really hate long tab

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Tue, Jun 24, 2014 at 4:16 PM, Ahmed RAHAL wrote: > Le 2014-06-24 17:38, Joe Gordon a écrit : > >> >> On Jun 24, 2014 2:31 PM, "Russell Bryant" > > wrote: >> > > > There be dragons here. Just because Nova doesn't see the node >> reporting >> > in, doesn't mean the

[openstack-dev] [Murano] environment deletion

Is there any reason the system Environment class doesn't implement destroy? Without it, the pieces of the heat stack not owned by other resources get left lying around. It looks like it was once implemented as part of deploy, but that no longer seems to execute. _

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

Your comments are fair. I think perhaps at this point we should defer discussion of the further away deadlines until the mid cycle meetup -- that will give us a chance to whiteboard the flow for that period of the release. Or do you really want to lock this down now? Michael On Wed, Jun 25, 2014

[openstack-dev] [Keystone] Announcing Keystone Middleware Project

The Keystone team would like to announce the official split of python-keystoneclient and the Keystone middleware code. Over time the middleware (auth_token, s3_token, ec2_token) has developed into a fairly expansive code base and includes dependencies that are not necessarily appropriate for the

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

Le 2014-06-24 17:38, Joe Gordon a écrit : On Jun 24, 2014 2:31 PM, "Russell Bryant" mailto:rbry...@redhat.com>> wrote: > There be dragons here. Just because Nova doesn't see the node reporting > in, doesn't mean the VMs aren't actually still running. I think this > needs to be left to lo

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

I think there is significant value in having status on the listener object even in the case of HAProxy. While HAProxy can support multiple listeners in a single process, there is no reason it needs to be deployed that way. Additionally in the case of updating a configuration with an additional list

[openstack-dev] [DevStack] neutron config not working

Before I get punted onto the operators list, I post this here because this is the default config and I'd expect the defaults to just work. Running devstack inside a VM with a single NIC configured and this in localrc: disable_service n-net enable_service q-svc enable_service q-agt enable_service

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On 06/24/2014 02:53 PM, Steve Gordon wrote: - Original Message - From: "Rick Jones" To: "OpenStack Development Mailing List (not for usage questions)" On 06/24/2014 02:38 PM, Joe Gordon wrote: I agree nova shouldn't take any actions. But I don't think leaving an instance as 'active'

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Brandon, Eugene, Doug, During the hackathon, I remember that we had briefly discussed how listeners would manifest themselves on the LB VM/device, and it turned out that for some backends like HAProxy it simply meant creating a frontend entry in the cfg file whereas on other solutions it could

Re: [openstack-dev] [cinder][glance] Update volume-image-metadata proposal

Hi Facundo, Can you attend the Glance meeting this week at 20:00 UTC on Thursday in #openstack-meeting-alt ? I may be misunderstanding what's at stake, but it looks like: - Glance holds the image metadata (some user-modifiable, some not) - Cinder copies the image metadata to use as volume metada

Re: [openstack-dev] [hacking] rules for removal

On Tue, 2014-06-24 at 22:26 +0100, Mark McLoughlin wrote: > There's two sides to this coin - concern about alienating > non-english-as-a-first-language speakers who feel undervalued because > their language is nitpicked to death and concern about alienating > english-as-a-first-language speakers wh

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

- Original Message - > From: "Rick Jones" > To: "OpenStack Development Mailing List (not for usage questions)" > > > On 06/24/2014 02:38 PM, Joe Gordon wrote: > > I agree nova shouldn't take any actions. But I don't think leaving an > > instance as 'active' is right either. I was think

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Jun 24, 2014 2:47 PM, "Rick Jones" wrote: > > On 06/24/2014 02:38 PM, Joe Gordon wrote: >> >> I agree nova shouldn't take any actions. But I don't think leaving an >> instance as 'active' is right either. I was thinking move instance to >> error state (maybe an unknown state would be more accu

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On 06/24/2014 02:38 PM, Joe Gordon wrote: I agree nova shouldn't take any actions. But I don't think leaving an instance as 'active' is right either. I was thinking move instance to error state (maybe an unknown state would be more accurate) and let the user deal with it, versus just letting the

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Jun 24, 2014 2:31 PM, "Russell Bryant" wrote: > > On 06/24/2014 04:42 PM, Joe Gordon wrote: > > > > On Jun 18, 2014 3:03 PM, "Chris Friesen" > > wrote: > >> > >> The output of "nova list" and "nova show" reflects the current status > > in the database, not t

Re: [openstack-dev] [hacking] rules for removal

On Tue, 2014-06-24 at 13:56 -0700, Clint Byrum wrote: > Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0700: > > On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote: > > > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > > > > On 06/22/2014 02:49 PM, Duncan Tho

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On 06/24/2014 04:42 PM, Joe Gordon wrote: > > On Jun 18, 2014 3:03 PM, "Chris Friesen" > wrote: >> >> The output of "nova list" and "nova show" reflects the current status > in the database, not the actual state on the compute node. >> >> If the instances in qu

[openstack-dev] [sahara] Upgrade of Hadoop components inside released version

Hi Team, I want to raise topic about upgrade of components in Hadoop version that is already supported by released Sahara plugin. The question is raised because of several change requests [1] and [2]. Topic was discussed in Atlanta ([3]), but we didn't come to the decision. All of us agreed that

Re: [openstack-dev] [Barbican] Barebones CA

Yeah pretty much. That¹s something I¹d be interested to work on, if work isn¹t ongoing already. -Rob On 24/06/2014 18:57, "John Wood" wrote: >Hello Robert, > >I would actually hope we have a self-contained certificate plugin >implementation that runs 'out of the box' to enable certificate

Re: [openstack-dev] [hacking] rules for removal

Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0700: > On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote: > > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > > > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > > > On 22 June 2014 14:41, Amrith Kumar wrote:

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Jun 18, 2014 3:03 PM, "Chris Friesen" wrote: > > The output of "nova list" and "nova show" reflects the current status in the database, not the actual state on the compute node. > > If the instances in question are on a compute node that is currently "down", then the information is stale and po

Re: [openstack-dev] [hacking] community consensus and removing rules

On 06/24/2014 04:49 AM, Mark McLoughlin wrote: > On Mon, 2014-06-23 at 19:55 -0700, Joe Gordon wrote: > >> * Add a new directory, contrib, for local rules that multiple >> projects use but are not generally considered acceptable to be >> enabled by default. This way we can re

Re: [openstack-dev] [nova] Set compute_node:hypervisor_nodename as unique and not null

On Jun 18, 2014 11:40 AM, "Manickam, Kanagaraj" wrote: > > Hi, > > > > This mail is regarding the required model change in nova. Please fine more details below: > > > > As we knew, Nova db has the table “compute_nodes” for modelling the hypervisors and its using the “hypervisor_hostname” field to

Re: [openstack-dev] [FUEL] OpenStack patching and FUEL upgrade follow-up meeting minutes

I think, Vladimir means, that we need to improve our scheduling of the CI jobs over available CI resources. As I know, now we have a dedicated server groups for separate tests and we cannot use free resources of other server groups in case of overbalanced load. On Thu, Jun 5, 2014 at 6:52 PM, Jes

Re: [openstack-dev] [Nova][Scheduler]

On Jun 24, 2014 9:00 AM, "Abbass MAROUNI" wrote: > > Hi, > > I was wondering if there's a way to set a tag (key/value) of a Virtual Machine from within a scheduler filter ? The scheduler today is just for placement. And since we are in the process of trying to split it out, I don't think we want

Re: [openstack-dev] [Fuel] Support for plugins in fuel client

Why not to use stevedore? On Wed, Jun 18, 2014 at 1:42 PM, Igor Kalnitsky wrote: > Hi guys, > > Actually, I'm not a fun of cliff, but I think it's a good solution to use > it in our fuel client. > > Here some pros: > > * pluggable design: we can encapsulate entire command logic in separate > pl

[openstack-dev] [NFV] Specific example NFV use case - ETSI #5, virtual IMS

Hello all Following on from my contribution last week of a specific NFV use case (a Session Border Controller) here's another one, this time for an IMS core (part of ETSI NFV use case #5). As we touched on at last week's meeting, this is not making claims for what every example of a virtual IMS c

Re: [openstack-dev] [hacking] rules for removal

On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote: > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > > On 22 June 2014 14:41, Amrith Kumar wrote: > > >> In addition to making changes to the hacking rules, why don't we manda

Re: [openstack-dev] [neutron][nova] nova needs a new release of neutronclient for OverQuotaClient exception

On Mon, Jun 23, 2014 at 11:08 AM, Kyle Mestery wrote: > On Mon, Jun 23, 2014 at 8:54 AM, Matt Riedemann > wrote: >> There are at least two changes [1][2] proposed to Nova that use the new >> OverQuotaClient exception in python-neutronclient, but the unit test jobs no >> longer test against trunk-

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

+1 to what Eugene just iterated: * Different types of statuses * Not every status on every object * Status should be API call Thanks, Vivek From: Eugene Nikanorov mailto:enikano...@mirantis.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:opensta

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

Mid-day numbers update: startdelta from 2014-06-17mid-daydelta from startenddelta from startdelta from 2014-06-17New1751701705Incomplete25-621-421-4-10Critical/High for 5.1 140 140 33Critical/High for 5.1, Confirmed Triaged92 87-587-5 Medium/Low/Undefined for 5.1, Confirmed/Triaged238 230-8230-8

[openstack-dev] Cinder pools implementation

Hi, As per our discussions in the last meeting I have made an etherpad which details different pool implementations and at the end comparison between the approaches. Please go through it and be ready with any questions or opinions for tomorrow's meeting. Here is the link for etherpad: https:/

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Eugene, Thanks for the feedback. I have a feeling thats where we will end up going anyway so perhaps status on all entities for now is the proper way to build into that. I just want my objections to be heard. Thanks, Brandon On Tue, 2014-06-24 at 23:10 +0400, Eugene Nikanorov wrote: > Hi lbaas

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Doug & Brandon, 1) +1 Doug -- I like the status "Building" but that's a personal preference. It's entirely up to the driver (but it should be reasonable) and we should pick the states up front (as we already do with constants) 2) We actually touched upon that with the distinction between sta

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

On Tue, 2014-06-24 at 18:53 +, Doug Wiegley wrote: > Hi Brandon, > > I think just one status is overloading too much onto the LB object (which > is perhaps something that a UI should do for a user, but not something an > API should be doing.) That is a good point and perhaps its another discu

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi lbaas folks, IMO a status is really an important part of the API. In some old email threads Sam has proposed the solution for lbaas objects: we need to have several attributes that independently represent different types of statuses: - admin_state_up - operational status - provisioning state N

Re: [openstack-dev] [Neutron][LBaaS] Which entities need status

Hi Brandon, I think just one status is overloading too much onto the LB object (which is perhaps something that a UI should do for a user, but not something an API should be doing.) > 1) If an entity exists without a link to a load balancer it is purely > just a database entry, so it would always

[openstack-dev] [cinder][glance] Update volume-image-metadata proposal

Hi folks, I started working on this blueprint [1] but the work to be done is not limited to cinder python client. Volume-image-metadata is immutable in Cinder and Glance has RBAC image properties and it doesn't provide any way to find out which are those protecte

[openstack-dev] [swift] Providing a potentially more open interface to statsd statistics

I've lamented for awhile that while swift/statsd provide a wealth of information, it's in a somewhat difficult to use format. Specifically you have to connect to a socket and listen for messages. Furthermore if you're listening, nobody else can. I do realize there is a mechanism to send the d

Re: [openstack-dev] [barbican] Juno Mid-cycle Meetup

Hi Everyone, Just a reminder that the Barbican mid-cycle meetup is just under two weeks away. I just wanted to send out a link to the etherpad we’re using to do some pre-planning of things that need to be covered during the meetup https://etherpad.openstack.org/p/barbican-juno-meetup Also, ple

[openstack-dev] [Neutron][LBaaS] Which entities need status

I think we missed this discussion at the meet-up but I'd like to bring it up here. To me having a status on all entities doesn't make much sense, and justing having a status on a load balancer (which would be a provisioning status) and a status on a member (which would be an operational status) ar

Re: [openstack-dev] [Neutron][LBaaS] Trouble with Devstack

Fawad, Thanks Fawad, that seems to have fixed my issue at this point. Amused me, since pip is supposed to replace easy_install, but I won't nitpick if it fixes it ha ha. -Trevor From: Fawad Khaliq [fa...@plumgrid.com] Sent: Tuesday, June 24, 2014 12:43 PM To: O

Re: [openstack-dev] [Barbican] Barebones CA

Hello Robert, I would actually hope we have a self-contained certificate plugin implementation that runs 'out of the box' to enable certificate generation orders to be evaluated and demo-ed on local boxes. Is this what you were thinking though? Thanks, John

Re: [openstack-dev] [Neutron][LBaaS] Trouble with Devstack

Hi Trevor, I ran into the same issue. I worked around quickly by doing the following: - After stack.sh uninstalls pip, and fails with the "pkg_resources.DistributionNotFound: pip==1.4.1" error, install pip from easy_install - # easy_install pip - And re - stack.sh Haven't done the

[openstack-dev] [Neutron][LBaaS] Trouble with Devstack

I'm running Ubuntu 14.04, and rather suddenly I'm unable to run "./stack.sh" successfully. Brandon, who is also running Ubuntu 14.04, is seeing no issues here. However, all the same, I'm at a loss as to understand what the problem is. At the bottom of my text is the terminal output from runni

Re: [openstack-dev] [Fuel] Removing old node logs

+1 to @Aleksandr On Tue, Jun 24, 2014 at 8:32 PM, Aleksandr Didenko wrote: > Yes, of course, snapshot for all nodes at once (like currently) should > also be available. > > > On Tue, Jun 24, 2014 at 7:27 PM, Igor Kalnitsky > wrote: > >> Hello, >> >> @Aleks, it's a good idea to make snapshot pe

Re: [openstack-dev] [Horizon] Quick Survey: Horizon Mid-Cycle Meetup

> On 6/20/14, 6:24 AM, "Radomir Dopieralski" wrote: > > >On 20/06/14 13:56, Jaromir Coufal wrote: > >> On 2014/19/06 09:58, Matthias Runge wrote: > >>> On Wed, Jun 18, 2014 at 10:55:59AM +0200, Jaromir Coufal wrote: > My quick questions are: > * Who would be interested (and able) to get

Re: [openstack-dev] [TripleO] dib-utils Release Question

Whoops, sorry, I didn't realize a tox.ini was required to release the project. We do actually need to push this to pypi because it's going to be a dep of diskimage-builder, so although there is currently no Python code in the project it needs to be pip installable anyway (similar to tripleo-image-

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

On 06/11/2014 02:34 AM, Mark Washenberger wrote: I think the tasks stuff is something different, though. A task is a (potentially) long-running operation. So it would be possible for an action to result in the creation of a task. As the proposal stands today, the actions we've been looking at are

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

On 06/11/2014 12:25 AM, Brian Rosmaita wrote: > That said, I prefer to have resources actually be things that the software creates. An action > isn't created. It is performed. > > I would prefer to replace the term "action(s)" with the term "task(s)", as is proposed for Nova [1]. Glance alre

Re: [openstack-dev] [hacking] rules for removal

Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700: > On 06/22/2014 02:49 PM, Duncan Thomas wrote: > > On 22 June 2014 14:41, Amrith Kumar wrote: > >> In addition to making changes to the hacking rules, why don't we mandate > >> also > >> that perceived problems in the commit messa

Re: [openstack-dev] [Fuel] Removing old node logs

Yes, of course, snapshot for all nodes at once (like currently) should also be available. On Tue, Jun 24, 2014 at 7:27 PM, Igor Kalnitsky wrote: > Hello, > > @Aleks, it's a good idea to make snapshot per environment, but I think > we can keep functionality to make snapshot for all nodes at once

Re: [openstack-dev] [Fuel] Removing old node logs

Hello, @Aleks, it's a good idea to make snapshot per environment, but I think we can keep functionality to make snapshot for all nodes at once too. - Igor On Tue, Jun 24, 2014 at 6:38 PM, Aleksandr Didenko wrote: > Yeah, I thought about diagnostic snapshot too. Maybe it would be better to > i

Re: [openstack-dev] Periodic Security Checks

On Sat, Jun 21, 2014 at 11:33 AM, Alexandr Naumchev wrote: > Hello! > We have blueprints here: > > https://blueprints.launchpad.net/horizon/+spec/periodic-security-checks > > and here: > > https://blueprints.launchpad.net/nova/+spec/periodic-security-checks/ > > And we already have some code. Is

[openstack-dev] Stackalytics 0.6 released!

Hi Stackers, More then a year ago Mirantis announced Stackalytics as a public resource for the OpenStack community. Initially it was an internal tool for our performance tracking, but later resource became de-facto standard for measuring contribution statistics. We've started with several POCs on

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On Tue, Jun 24, 2014 at 9:56 AM, Duncan Thomas wrote: > On 24 June 2014 16:42, Avishay Traeger wrote: > > One more reason why block storage management doesn't really work on file > > systems. I'm OK with storing the format, but that just means you fail > > migration/backup operations with diffe

Re: [openstack-dev] [Neutron][LBaaS] Layer7 Switching - L7 Rule - comapre_type values

I brought this up on https://review.openstack.org/#/c/101084/. -Dustin On Tue, Jun 24, 2014 at 7:57 AM, Avishay Balderman wrote: > Hi Dustin > > I agree with the concept you described but as far as I understand it is > not currently supported in Neutron. > > So a driver should be fully compa

[openstack-dev] [Nova][Scheduler]

Hi, I was wondering if there's a way to set a tag (key/value) of a Virtual Machine from within a scheduler filter ? I want to be able to tag a machine with a specific key/value after passing my custom filter Thanks, -- -- Abbass MAROUNI VirtualScale __

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On Tue, Jun 24, 2014 at 9:42 AM, Avishay Traeger wrote: > One more reason why block storage management doesn't really work on file > systems. I'm OK with storing the format, but that just means you fail > migration/backup operations with different formats, right? > ​+1... so nice that someb

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

On 24 June 2014 16:42, Avishay Traeger wrote: > One more reason why block storage management doesn't really work on file > systems. I'm OK with storing the format, but that just means you fail > migration/backup operations with different formats, right? Actually I think storing the format *fixes

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

On 24/06/14 10:55 -0400, Jordan OMara wrote: On 20/06/14 16:26 -0400, Charles Crouch wrote: Any more takers for the tripleo mid-cycle meetup in Raleigh? If so, please sign up on the etherpad below. The hotel group room rate will be finalized on Monday Jul 23rd (US time), after that time you wi

Re: [openstack-dev] [Cinder] About storing volume format info for filesystem-based drivers

One more reason why block storage management doesn't really work on file systems. I'm OK with storing the format, but that just means you fail migration/backup operations with different formats, right? On Mon, Jun 23, 2014 at 6:07 PM, Trump.Zhang wrote: > Hi, all: > > Currently, there are

Re: [openstack-dev] [hacking] rules for removal

On Tue, Jun 24, 2014 at 11:28 AM, Jay Pipes wrote: > > """ > This is a summary. > > And this is a description > """ > > will result in a failure of H404, due to the "This is a summary." not > being on the first line, like this: > > """This is a summary. > > And this is a description > """ > > It

Re: [openstack-dev] [Fuel] Removing old node logs

What about to gzip old logs by Astute and place them to a special directory, which will be managed under logrotate.d, and logrotate will remove untouched logs after 1 month. On Tue, Jun 24, 2014 at 6:57 PM, Aleksandr Didenko wrote: > Hi, > > If user runs some experiments with creating/deleting

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

On 06/24/2014 07:32 AM, Daniel P. Berrange wrote: On Tue, Jun 24, 2014 at 10:55:41AM +, Day, Phil wrote: -Original Message- From: John Garbutt [mailto:j...@johngarbutt.com] Sent: 23 June 2014 10:35 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [opens

Re: [openstack-dev] [Fuel] Removing old node logs

Hi guys, What about our diagnostic snapshot? I mean we're going to make snapshot of entire /var/log and obviously this old logs will be included in snapshot. Should we skip theem or such situation is ok? - Igor On Tue, Jun 24, 2014 at 5:57 PM, Aleksandr Didenko wrote: > Hi, > > If user run

[openstack-dev] [Barbican] Barebones CA

Hi all, I’m sure this has been discussed somewhere and I’ve just missed it. Is there any value in creating a basic ‘CA’ and plugin to satisfy tests/integration in Barbican? I’m thinking something that probably performs OpenSSL certificate operations itself, ugly but perhaps useful for some thin

Re: [openstack-dev] [Fuel] Removing old node logs

Yeah, I thought about diagnostic snapshot too. Maybe it would be better to implement per-environment diagnostic snapshots? I.e. add diagnostic snapshot generate/download buttons/links in the environment actions tab. Such snapshot would contain info/logs about Fuel master node and nodes assigned to

Re: [openstack-dev] [hacking] rules for removal

On 06/24/2014 10:34 AM, Robert Collins wrote: On 23 June 2014 07:04, Jay Pipes wrote: I would also love to get rid of H404, otherwise known as the dumb rule that says if you have a multiline docstring, that there must be a summary line, then a blank line, then a detailed description. It makes

  1   2   >