Re: [openstack-dev] Swift3 Plugin Development

On Thu, Jun 08, 2017 at 10:52:53PM -0600, Pete Zaitcev wrote: > On Thu, 8 Jun 2017 17:06:02 +0530 > Venkata R Edara wrote: > > > we are looking for S3 plugin with ACLS so that we can integrate gluster > > with that. > > Did you look into porting Ceph RGW on top of Gluster?

Re: [openstack-dev] Swift3 Plugin Development

On Thu, 8 Jun 2017 17:06:02 +0530 Venkata R Edara wrote: > we are looking for S3 plugin with ACLS so that we can integrate gluster > with that. Did you look into porting Ceph RGW on top of Gluster? -- P

Re: [openstack-dev] [all] etcd3 as base service - update

Julien Danjou wrote: On Thu, Jun 08 2017, Mike Bayer wrote: So far I've seen a proposal of etcd3 as a replacement for memcached in keystone, and a new dogpile connector was added to oslo.cache to handle referring to etcd3 as a cache backend. This is a really simplistic / minimal kind of use

Re: [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 6/8/2017 6:17 PM, John Griffith wrote: ​The attachment_update call could do this for you, might need some slight tweaks because I tried to make sure that we weren't having attachment records be modified things that lived forever and were dynamic. This particular case seems like a descent

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 6/8/2017 1:39 PM, melanie witt wrote: On Thu, 8 Jun 2017 08:58:20 -0500, Matt Riedemann wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Thanks for everything jroll and best wishes on your new endeavors! On Thu, Jun 8, 2017 at 8:45 PM, Jim Rollenhagen wrote: > Hey friends, > > I've been mostly missing for the past six weeks while looking for a new > job, so maybe you've forgotten me already, maybe not.

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Jim, Though I wasn't involved Ironic too much, I know you're one of the best Ironicer. Good luck! 2017-06-09 9:33 GMT+08:00 phuon...@vn.fujitsu.com : > Hi Jim, good luck to you. Remember the time we discussed right after you > waked up in the morning. :) > > > >

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Hi Jim, good luck to you. Remember the time we discussed right after you waked up in the morning. :) Phuong. From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Thursday, June 08, 2017 7:45 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev]

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Flavio: I think your right. k8s configmaps and confd are doing very similar things. The one thing confd seems to add is dynamic templates on the host side. This is still accomplished in k8s with a sidecar watching for config changes with the templating engine in it and an emptyDir. or

Re: [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On Thu, Jun 8, 2017 at 7:58 AM, Matt Riedemann wrote: > Nova stores the output of the Cinder os-initialize_connection info API in > the Nova block_device_mappings table, and uses that later for making volume > connections. > > This data can get out of whack or need to be

[openstack-dev] [keystone] Specification Freeze

Happy Stanley-Cup-Playoff-Game-5 Day, Sending out a quick reminder that tomorrow is specification freeze. I'll be making a final push for specifications that target Pike work tomorrow. I'd also like to merge others to backlog as we see fit. By EOD tomorrow, I'll go through and put procedural

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Thu, Jun 8, 2017, 19:14 Doug Hellmann wrote: > Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > > On 08/06/17 18:23 +0200, Flavio Percoco wrote: > > >On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > > >>On 06.06.2017 18:08, Emilien Macchi wrote: >

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Thu, Jun 8, 2017, 19:51 Steven Dake (stdake) wrote: > Flavio, > > Atleast for the kubernetes variant of kolla, bindmounting will always be > used as this is fundamentally how configmaps operate. In order to maintain > maximum flexilbility and compatibility with kubernetes,

Re: [openstack-dev] [all][api] POST /api-wg/news

On Jun 8, 2017, at 11:59 AM, Chris Dent wrote: > > The naming issue related to an optional field we want to add to the > microversion discovery document. Some projects wish to be able to signal that > they are intending to raise the minimum microversion at a point in

Re: [openstack-dev] [all] etcd3 as base service - update

On Thu, Jun 8, 2017 at 3:21 PM, Emilien Macchi wrote: > On Thu, Jun 8, 2017 at 7:34 PM, Lance Bragstad > wrote: > > After digging into etcd a bit, one place this might be help deployer > > experience would be the handling of fernet keys for token

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Because tools to manipulate json and or yaml are very common. Tools to manipulate a psudo ini file format that isn't standards compliant are not. :/ Thanks, Kevin From: Doug Hellmann [d...@doughellmann.com] Sent: Thursday, June 08, 2017 1:39 PM To:

[openstack-dev] [tripleo] pike m2 has been released

We have a new release of TripleO, pike milestone 2. All bugs targeted on Pike-2 have been moved into Pike-3. I'll take care of moving the blueprints into Pike-3. Some numbers: Blueprints: 3 Unknown, 18 Not started, 14 Started, 3 Slow progress, 11 Good progress, 9 Needs Code Review, 7 Implemented

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 8, 2017, at 4:29 PM, Fox, Kevin M wrote: > > That is possible. But, a yaml/json driver might still be good, regardless of > the mechanism used to transfer the file. > > So the driver abstraction still might be useful. Why would it be useful to have oslo.config

Re: [openstack-dev] [all] etcd3 as base service - update

On Thu, Jun 8, 2017 at 4:07 PM, Drew Fisher wrote: > > > On 6/7/17 4:47 AM, Davanum Srinivas wrote: >> Team, >> >> Here's the update to the base services resolution from the TC: >> https://governance.openstack.org/tc/reference/base-services.html >> >> First request is to

Re: [openstack-dev] [all] etcd3 as base service - update

See the footer at the bottom of this email. From: jimi olugboyega [jimiolugboy...@gmail.com] Sent: Thursday, June 08, 2017 1:19 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] etcd3 as base service - update

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

There are two issues conflated here maybe? The first is a mechanism to use oslo.config to dump out example settings that could be loaded into a reference ConfigMap or etcd or something. I think there is a PS up for that. The other is a way to get the data back into oslo.config. etcd is one

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Emilien Macchi's message of 2017-06-08 22:20:34 +0200: > On Thu, Jun 8, 2017 at 8:49 PM, Doug Hellmann wrote: > > Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +: > >> Doug, > >> > >> In short, a configmap takes a bunch of config

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

That is possible. But, a yaml/json driver might still be good, regardless of the mechanism used to transfer the file. So the driver abstraction still might be useful. Thanks, Kevin From: Doug Hellmann [d...@doughellmann.com] Sent: Thursday, June 08, 2017

Re: [openstack-dev] [all] etcd3 as base service - update

hmm... a very interesting question I would think control plane only. Thanks, Kevin From: Drew Fisher [drew.fis...@oracle.com] Sent: Thursday, June 08, 2017 1:07 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] etcd3 as base

Re: [openstack-dev] [all] etcd3 as base service - update

On Thu, Jun 08 2017, Mike Bayer wrote: > So far I've seen a proposal of etcd3 as a replacement for memcached in > keystone, and a new dogpile connector was added to oslo.cache to handle > referring to etcd3 as a cache backend. This is a really simplistic / minimal > kind of use case for a

Re: [openstack-dev] [all] etcd3 as base service - update

On Thu, Jun 8, 2017 at 7:34 PM, Lance Bragstad wrote: > After digging into etcd a bit, one place this might be help deployer > experience would be the handling of fernet keys for token encryption in > keystone. Currently, all keys used to encrypt and decrypt tokens are kept

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Thu, Jun 8, 2017 at 8:49 PM, Doug Hellmann wrote: > Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +: >> Doug, >> >> In short, a configmap takes a bunch of config files, bundles them in a >> kubernetes object called a configmap, and then ships

Re: [openstack-dev] [all] etcd3 as base service - update

Hello all, I am wondering how I can unsubscribe from this mailing list. Regards, Olujimi Olugboyega. On Wed, Jun 7, 2017 at 3:47 AM, Davanum Srinivas wrote: > Team, > > Here's the update to the base services resolution from the TC: >

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Fox, Kevin M's message of 2017-06-08 20:08:25 +: > Yeah, I think k8s configmaps might be a good config mechanism for k8s based > openstack deployment. > > One feature that might help which is related to the etcd plugin would be a > yaml/json plugin. It would allow more native

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Yeah, I think k8s configmaps might be a good config mechanism for k8s based openstack deployment. One feature that might help which is related to the etcd plugin would be a yaml/json plugin. It would allow more native looking configmaps. Thanks, Kevin

Re: [openstack-dev] [all] etcd3 as base service - update

On 6/7/17 4:47 AM, Davanum Srinivas wrote: > Team, > > Here's the update to the base services resolution from the TC: > https://governance.openstack.org/tc/reference/base-services.html > > First request is to Distros, Packagers, Deployers, anyone who > installs/configures OpenStack: > Please

Re: [openstack-dev] [neutron][l2gw] OVS code currently broken

Can you file a bug against Neutron and reference it here? On Thu, Jun 8, 2017 at 8:28 AM, Ricardo Noriega De Soto wrote: > There is actually a bunch of patches waiting to be reviewed and approved. > > Please, we'd need core reviewers to jump in. > > I'd like to thank Gary

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

Oh, yes please! We've had to go through a lot of hoops to migrate ceph-mon's around while keeping their ip's consistent to avoid vm breakage. All the rest of the ceph ecosystem (at least that we've dealt with) works fine without the level of effort the current nova/cinder implementation

[openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

Hi all, Is your project ready for pylint 1.7.1? If you use pylint in your pep8 job, it is worth checked. Our current version of pylint is 1.4.5 but it is not safe in python 3.5. The global-requirements update was merged once [1], However, some projects (at least neutron) are not ready for pylint

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +: > Doug, > > In short, a configmap takes a bunch of config files, bundles them in a > kubernetes object called a configmap, and then ships them to etcd. When a > pod is launched, the pod mounts the configmaps using tmpfs

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On Thu, 8 Jun 2017 08:58:20 -0500, Matt Riedemann wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack or need to be refreshed, like if your

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Congrats on your new gig Jim, and best of luck! Chris D From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Thursday, June 8, 2017 8:45 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [ironic][nova]

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Jim, Wish you good luck for your new venture. -Anup From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Thursday, June 8, 2017 5:45 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [ironic][nova] Goodbye^W

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 8 June 2017 at 09:50, Michał Jastrzębski wrote: > On 8 June 2017 at 09:27, Flavio Percoco wrote: >> On 08/06/17 18:23 +0200, Flavio Percoco wrote: >>> >>> On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote:

Re: [openstack-dev] [all] etcd3 as base service - update

So, one thing to remember, I don't think etcd has an authz mechanism yet. You usually want your fernet keys to be accessible by just the keystone nodes and no others. This might require a etcd cluster just for keystone fernet tokens, which might work great. but is an operator overhead to

Re: [openstack-dev] [forum] Future of Stackalytics

On 2017-06-08 09:49:03 -0700 (-0700), Ken'ichi Ohmichi wrote: > 2017-06-08 7:19 GMT-07:00 Jeremy Stanley : [...] > > There is a foundation member directory API now which provides > > affiliation details and history, so if it were my project (it's > > not though) I'd switch to

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Doug, In short, a configmap takes a bunch of config files, bundles them in a kubernetes object called a configmap, and then ships them to etcd. When a pod is launched, the pod mounts the configmaps using tmpfs and the raw config files are available for use by the openstack services.

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Flavio, Atleast for the kubernetes variant of kolla, bindmounting will always be used as this is fundamentally how configmaps operate. In order to maintain maximum flexilbility and compatibility with kubernetes, I am not keen to try a non-configmap way of doing things. Regards -steve

Re: [openstack-dev] [all] etcd3 as base service - update

After digging into etcd a bit, one place this might be help deployer experience would be the handling of fernet keys for token encryption in keystone. Currently, all keys used to encrypt and decrypt tokens are kept on disk for each keystone node in the deployment. While simple, it requires

Re: [openstack-dev] [oslo.messaging]Optimize RPC performance by reusing callback queue

Hi, Keep in mind the rabbit driver creates a single reply queue per *transport* - that is per call to oslo.messaging's get_transport/get_rpc_transport/get_notification_transport. If you have multiple RPCClients sharing the same transport, then all clients issuing RPC calls over that transport

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > On 08/06/17 18:23 +0200, Flavio Percoco wrote: > >On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > >>On 06.06.2017 18:08, Emilien Macchi wrote: > >>>Another benefit is that confd will generate a configuration file when >

Re: [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

> On 08 Jun 2017, at 17:52, Matt Riedemann wrote: > > On 6/8/2017 10:17 AM, Arne Wiebalck wrote: >>> On 08 Jun 2017, at 15:58, Matt Riedemann >> > wrote: >>> >>> Nova stores the output of the Cinder

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On 06/08/2017 10:16 AM, Emilien Macchi wrote: On Thu, Jun 8, 2017 at 1:47 PM, Sofer Athlan-Guyot wrote: Hi, Alex Schultz writes: On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot wrote: Hi, Emilien Macchi

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Today's meeting was mostly devoted to two topics: Which of Monty's several patches were ready for freeze and some naming issues with raising the minimum microversion. We decided three of Monty's patches are ready, they are listed below in the "Freeze" section.

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 8 June 2017 at 09:27, Flavio Percoco wrote: > On 08/06/17 18:23 +0200, Flavio Percoco wrote: >> >> On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: >>> >>> On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file

Re: [openstack-dev] [tripleo] Ansible roles repo and how to inject them into the overcloud

On 06/07/2017 09:25 AM, Juan Antonio Osorio wrote: Hi folks! I would like to know if there are thoughts about where to put tripleo-specific ansible roles. I've been working lately on a role that would deploy ipsec tunnels for most networks in an overcloud [1]. And I think that would be quite

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 7:19 GMT-07:00 Jeremy Stanley : > On 2017-06-07 16:36:45 -0700 (-0700), Ken'ichi Ohmichi wrote: > [...] >> one of config files is 30KL due to much user information and that >> makes the maintenance hard now. I am trying to separate user part >> from the existing file

[openstack-dev] [OpenStack-Ansible][OSA] Next week's meeting is cancelled

Just wanted to give everyone a heads up that next week's meeting on 6/15 has been cancelled. Thanks all! Amy (spotz) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [tripleo] Install Kubernetes in the overcloud using TripleO

Hey y'all, Just wanted to give an updated on the work around tripleo+kubernetes. This is still far in the future but as we move tripleo to containers using docker-cmd, we're also working on the final goal, which is to have it run these containers on kubernetes. One of the first steps is to have

Re: [openstack-dev] [all] etcd3 as base service - update

On 06/08/2017 12:47 AM, Joshua Harlow wrote: So just out of curiosity, but do people really even know what etcd is good for? I am thinking that there should be some guidance from folks in the community as to where etcd should be used and where it shouldn't (otherwise we just all end up in a

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 08/06/17 18:23 +0200, Flavio Percoco wrote: On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file when the application will start. So if etcd is down *after* the app startup, it shouldn't

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file when the application will start. So if etcd is down *after* the app startup, it shouldn't break the service restart if we don't ask confd

[openstack-dev] [TripleO] PSA: Please WIP your WIP patches

This makes it easier to filter them out when looking for wayward patches. Right now the list of 15 oldest reviews includes at least 5 WIP patches that weren't marked as such in Gerrit. For anyone who's not aware, to mark a patch WIP in Gerrit you set Workflow -1 on it. Anyone can do that to

Re: [openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

Hi Emilien, I'll try and get a list of the Perf teams TripleO deployment bugs and bring them to the deployment hackfest. I look forward to participating! - Justin On Thu, Jun 8, 2017 at 11:10 AM, Emilien Macchi wrote: > On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpatrick

Re: [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 6/8/2017 10:17 AM, Arne Wiebalck wrote: On 08 Jun 2017, at 15:58, Matt Riedemann > wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making

Re: [openstack-dev] [neutron][l2gw] OVS code currently broken

There is actually a bunch of patches waiting to be reviewed and approved. Please, we'd need core reviewers to jump in. I'd like to thank Gary for all his support and reviews. Thanks Gary! On Tue, May 30, 2017 at 3:56 PM, Gary Kotton wrote: > Hi, > > Please note that the

[openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Hi everyone, Doug and I have written up a spec following on from the conversation [0] that we had regarding the documentation publishing future. Please take the time out of your day to review the spec as this affects *everyone*. See: https://review.openstack.org/#/c/472275/ I will be PTO

Re: [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 08 Jun 2017, at 15:58, Matt Riedemann > wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On Thu, Jun 8, 2017 at 1:47 PM, Sofer Athlan-Guyot wrote: > Hi, > > Alex Schultz writes: > >> On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot >> wrote: >>> Hi, >>> >>> Emilien Macchi writes: >>> On Wed,

[openstack-dev] [openstack-doc] [dev] Doc team meeting cancellation

Hi everyone, Next week, Thursday the 15th of June, the OpenStack manuals meeting is cancelled as I will be PTO. The next documentation team meeting will be the following bi-weekly allotment on the 29th of June. If anyone has any pressing concerns, please email me and I will get back to you

Re: [openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

On Thu, Jun 8, 2017 at 2:21 PM, Justin Kilpatrick wrote: > Morning everyone, > > I've been working on a performance testing tool for TripleO hardware > provisioning operations off and on for about a year now and I've been > using it to try and collect more detailed data about

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

Sorry for the top-post, but it seems that nobody has responded to this, and there are a lot of important questions that need answers. So I’m simply re-posting this so that we don’t get too ahead of ourselves, by planning implementations before we fully understand the problem and the

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

On 6/8/2017 3:36 AM, Narendra Pal Singh wrote: Does Ocata bits support adding custom resource monitor say network bandwidth? I don't believe so in the upstream code. There is only a CPU bandwidth monitor in-tree today, but only supported by the libvirt driver and untested anywhere in our

Re: [openstack-dev] [trove] Trove reboot meeting

Ok everyone here is the link to join. Please only join if you plan to participate as there are a limit on these calls https://hangouts.google.com/call/ncgjbzal5p7ttelna3ovzqu __ OpenStack Development Mailing List (not

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

On Thu, Jun 8, 2017 at 4:19 PM, Sagi Shnaidman wrote: > Hi, all > > Thanks for your attention and proposals for this hackathon. With full > understanding that optimization of deployment is on-going effort and should > not be started and finished in these 2 days only, we still

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

Ok - based on the responses in the thread here, I've re-proposed the global roles specification to keystone's backlog [0]. I'll start working on the implementation and get something in review as soon as possible. I'll plan to move the specification from backlog to Queens once development opens.

Re: [openstack-dev] [forum] Future of Stackalytics

On Thu, Jun 08, 2017 at 02:11:18PM +, Jeremy Stanley wrote: > On 2017-06-08 09:22:48 -0400 (-0400), Paul Belanger wrote: > [...] > > We also have another issue where we loose access to gerrit and our apache > > process pins CPU to 100%, these might also be low hanging friut for people > >

Re: [openstack-dev] [forum] Future of Stackalytics

On 2017-06-07 16:36:45 -0700 (-0700), Ken'ichi Ohmichi wrote: [...] > one of config files is 30KL due to much user information and that > makes the maintenance hard now. I am trying to separate user part > from the existing file but I cannot find the way to make a > consensus for such thing.

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

Hi, all Thanks for your attention and proposals for this hackathon. With full understanding that optimization of deployment is on-going effort and should not be started and finished in these 2 days only, we still want to get focus on these issues in the sprint. Even if we don't solve immediately

Re: [openstack-dev] [forum] Future of Stackalytics

On 2017-06-08 09:22:48 -0400 (-0400), Paul Belanger wrote: [...] > We also have another issue where we loose access to gerrit and our apache > process pins CPU to 100%, these might also be low hanging friut for people > wanting to get involved. [...] Wasn't that fixed with a new lower-bound on

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Le 08/06/2017 14:45, Jim Rollenhagen a écrit : > Hey friends, > > I've been mostly missing for the past six weeks while looking for a new > job, so maybe you've forgotten me already, maybe not. I'm happy to tell > you I've found one that I think is a great opportunity for me. But, I'm > sad to

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

On Jun 8, 2017, at 7:45 AM, Jim Rollenhagen wrote: > I've been mostly missing for the past six weeks while looking for a new job, > so maybe you've forgotten me already, maybe not. I'm happy to tell you I've > found one that I think is a great opportunity for me. But,

[openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack or need to be refreshed, like if your ceph server IP changes, or you need to recycle some secret

Re: [openstack-dev] [forum] Future of Stackalytics

On Wed, May 17, 2017 at 06:55:57PM +, Jeremy Stanley wrote: > On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: > [...] > > we need help with completing the migration to infra. If interested > > you can reach out to fungi (Infra team PTL) nor mrmartin (who > > currently helps with

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Jim, very sad to see you go :( Undeniably you played a major part in ironic and its community becoming what they are today - an awesome project made by awesome people. Hopefully we'll have a chance to work together again someday :) All the best in your new endeavors, Pavlo. On Thu, Jun 8, 2017

Re: [openstack-dev] [ironic][nova] Goodbye^W See you later

Best of luck, jroll! <3 milan čt 8. 6. 2017 v 14:46 odesílatel Jim Rollenhagen napsal: > Hey friends, > > I've been mostly missing for the past six weeks while looking for a new > job, so maybe you've forgotten me already, maybe not. I'm happy to tell you > I've found

[openstack-dev] [ironic][nova] Goodbye^W See you later

Hey friends, I've been mostly missing for the past six weeks while looking for a new job, so maybe you've forgotten me already, maybe not. I'm happy to tell you I've found one that I think is a great opportunity for me. But, I'm sad to tell you that it's totally outside of the OpenStack

Re: [openstack-dev] [EXTERNAL] Re: [Tripleo] deploy software on Openstack controller on the Overcloud

Updated https://github.com/abhishek-kane/puppet-veritas-hyperscale with the attempts to reuse puppet modules for keystone, rabbitmq and nova_flavor. Still doing some operation via scripts. Regards. On 6/7/17, 8:08 PM, "Abhishek Kane" wrote: Hi, On

Re: [openstack-dev] [vitrage-dashboard] Alarm Header Blueprint

Looks great ☺ Since you wrote a long and impressive description, it might be worthwhile to push it to gerrit after all. As I said, we usually don’t push vitrage-dashboard specs to gerrit, so it’s really up to you. Best Regards, Ifat. From: "Waines, Greg" Date:

[openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

Morning everyone, I've been working on a performance testing tool for TripleO hardware provisioning operations off and on for about a year now and I've been using it to try and collect more detailed data about how TripleO performs in scale and production use cases. Perhaps more importantly YODA

Re: [openstack-dev] [telemetry][ceilometer][gnocchi] Query on adding new meters to Gnocchi

On Thu, Jun 08, 2017 at 08:30:32AM +, Deepthi V V wrote: Thanks Mehdi for the information. I will soon upload a spec for adding the meters. We don't use spec, just open a bug, or directly send patches. Thanks, Deepthi -Original Message- From: Mehdi Abaakouk

[openstack-dev] [neutron] plumbing in request-id passing back to nova

We've now got Nova -> Glance, Neutron, Cinder. Cinder -> Nova, Glance is up for review. I started looking at the Neutron code for this, and it's wildly different, so need some help on what the right way forward is. It appears that the novaclient construction happens only once per run inside this

[openstack-dev] [vitrage-dashboard] Alarm Header Blueprint

I have registered a new blueprint in Vitrage-dashboard which leverages the proposed extensible headers of Horizon. https://blueprints.launchpad.net/vitrage-dashboard/+spec/alarm-header let me know your thoughts, Greg p.s proposed extensible header blueprint in horizon is here:

[openstack-dev] [horizon] Extensible Header Blueprint

I have registered a new blueprint to address the extensible header functionality discussed below. https://blueprints.launchpad.net/horizon/+spec/extensible-header interested in your feedback, Greg. From: David Lyle Reply-To: "openstack-dev@lists.openstack.org"

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

Hi, Alex Schultz writes: > On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot > wrote: >> Hi, >> >> Emilien Macchi writes: >> >>> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot >>> wrote: Hi,

[openstack-dev] Swift3 Plugin Development

Hello, we have storage product called Gluster which is file storage system, we are looking to support S3 APIs for it. openstack-swift project has the swift3 plugin to support S3 APIs , but according to https://github.com/openstack/swift3/blob/master/README.md we see that S3 ACL's are

Re: [openstack-dev] [all] etcd3 as base service - update

Josh, Of the initial targets, we have covered the use of tooz and oslo.cache with etcd already. One thing that remains is Jay's os-lively PoC [1]. So +1 to more knowledgeable folks chiming in with stuff that can be done and other scenarios. I'll let nature take its course here :) Thanks, Dims

Re: [openstack-dev] [QA] Proposed changes to the team meeting time

On Thu, Jun 8, 2017 at 4:04 PM, Andrea Frittoli wrote: > I proposed a change to irc-meetings [1] to move the meeting to 8:00 UTC. > The first 8:00 UTC meeting will be next week June 15th. > > [1] https://review.openstack.org/472194 > It will be helpful. Thanks,

Re: [openstack-dev] [QA] Proposed changes to the team meeting time

I proposed a change to irc-meetings [1] to move the meeting to 8:00 UTC. The first 8:00 UTC meeting will be next week June 15th. [1] https://review.openstack.org/472194 On Mon, May 29, 2017 at 6:01 AM Masayuki Igawa wrote: > Thanks Andrea, > > +1 > But my only one concern is

Re: [openstack-dev] [neutron] pep8 breakage

Hi, That patch will now need to be tweaked so that we can enable the requirements to be bumped. Gate is back to usual after the requirements were reverted. Thanks Gary On 6/7/17, 9:40 PM, "Ihar Hrachyshka" wrote: UPD: in case you wonder if that's fixed, we are waiting

[openstack-dev] [devstack] [nova] [kuryr] issue with host to cell mapping on ocata

Hi, I am working on testing kuryr-kubernetes plugin with opendaylight, using devstack-ocata, with a 3 node setup. I am hitting the below error when I execute "nova show ${vm_name} | grep OS-EXT-STS:vm_state", once the vm is booted. Keyword 'Verify VM Is ACTIVE' failed after retrying

[openstack-dev] [publiccloud-wg] Summary meeting 7th June

Hi folks, Here comes a summary from yesterdays meeting for the Public Cloud Working Group. The missing features document now got status and priority columns. Definitions for each column will be added during the week as well, but pretty self-explaining. We really encourage you all to add

Re: [openstack-dev] [all] etcd3 as base service - update

Joshua Harlow wrote: > So just out of curiosity, but do people really even know what etcd is > good for? I am thinking that there should be some guidance from folks in > the community as to where etcd should be used and where it shouldn't > (otherwise we just all end up in a mess). > > Perhaps a

[openstack-dev] [Nova][Scheduler]

Hello, Does Ocata bits support adding custom resource monitor say network bandwidth? Nova Scheduler should consider new metric data for cost calculation each filtered host. -- Regards, NPS. __ OpenStack Development Mailing

Re: [openstack-dev] [telemetry][ceilometer][gnocchi] Query on adding new meters to Gnocchi

Thanks Mehdi for the information. I will soon upload a spec for adding the meters. Thanks, Deepthi -Original Message- From: Mehdi Abaakouk [mailto:sil...@sileht.net] Sent: Thursday, June 08, 2017 1:44 PM To: OpenStack Development Mailing List (not for usage questions)

  1   2   >