Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Jul 18, 2016, at 12:39 PM, Fox, Kevin M wrote: > I'm arguing the opposite. It should be a requirement to use the OpenStack > Secret Store. > > Instead, we're trying to make it optional and either reimplementing large > swaths of it in individual projects to make it

Re: [openstack-dev] [mistal] Mistral logo ideas?

> On 18 Jul 2016, at 19:54, Ryan Brady wrote: > > On Mon, Jul 18, 2016 at 12:44 AM, Renat Akhmerov > wrote: > On choosing a mascot for Mistral. Let’s choose one till next Monday. > > To start this discussion I’d

Re: [openstack-dev] [glance] selecting project mascot

The etherpad poll has been closed and the votes and the top 3 candidates in the preferential order have been sent for further evaluation. We will most likely be selecting one of the 3 candidates mentioned at the near bottom of the etherpad. More to come once selection has been made. On 7/12/16

[openstack-dev] 答复: [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

+1 周亚 Zhou Ya 虚拟化南京一部NIV Nanjing Dept.Ⅰ R Building, ZTE Plaza, #6 Huashen Ave. Yuhuatai District, Nanjing, P.R.China, 210012 T: +86 13951010061 M: +86 13772010248 E: zhou...@zte.com.cn www.zte.com.cn 发件人: 胡智江180967/user/zte_ltd 收件人:

[openstack-dev] 答复: [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

+1 孙静 Sun Jing 虚拟化南京一部/无线研究院 NIV Nanjing dept.I / Wireless Product R Institute 南京市花神大道6号中兴通讯二期5楼 ZTE Corporation, No6, Huashendadao Road Yuhuatai District, Nanjing, P.R.China, 210012 T:+86 M: +86 18551731425 E: sun.jin...@zte.com.cn www.zte.com.cn 胡智江180967/user/zte_ltd 2016/07/19

[openstack-dev] [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

Hi Team, I would like to propose adding Wei Kong(kong.w...@zte.com.cn) to the daisycloud-core core team. He has good experience on openstack development, previously he lead another team finished a BP of a cinder driver and his current commitment is on testing, ci for daisycloud-core. Until

[openstack-dev] [daisycloud-core] Nnominate Wei Kong as core for daisycloud-core project

Hi Team, I would like to propose adding Wei Kong(kong.w...@zte.com.cn) to the daisycloud-core core team. He has good experience on openstack development, previously he lead another team finished a BP of a cinder driver and his current commitment is on testing, ci for daisycloud-core. Until

[openstack-dev] OpenStack: Happy 6th Birthday:)

__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

+1 to apply I'd like to be the volunteer. On Mon, Jul 18, 2016 at 9:04 PM, Swapnil Kulkarni (coolsvap) wrote: > On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke wrote: >> Hi Steve, >> >> +1 to applying. I'll volunteer for the backport team also. >> >>

Re: [openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

Hi Erno, For the size of team I am in I think it would work well but it feels like I am putting the security of Nova in the hands of Glance. What I was more after was a setting in Nova that says 'this hypervisor does not allow guest sockets and will ignore any attempt to create them', 'this

Re: [openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

Hi Daniel, You might want to have look on the Glance Property Protections [0]. I'd assume that would do it for you? [0] http://docs.openstack.org/developer/glance/property-protections.html Best, Erno On Tue, Jul 19, 2016 at 12:43 AM, Daniel Russell wrote: > Hi, > > >

Re: [openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

I also happened to be looking at this today and was wondering about this as well. From the multi-places that talk about how to enable the qemu guest agent for quiescing drives during snapshots, they all have a warning that this should be enabled on trusted guests only. [1] [2] [3] So, I am

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

I applaud this (since I know this kind of question and work is really really hard). So thanks for starting and keeping 'hard' questions going because without someone pushing the limit here (and/or raising the questions) I too fear what u fear and that we may be obsoleting ourselves by

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 07/04/2016 05:36 AM, Sean McGinnis wrote: On Mon, Jul 04, 2016 at 01:59:09PM +0200, Thierry Carrez wrote: [...] The issue here is that oslo.rootwrap uses config files to determine what to allow, but those are not really configuration files as far as the application using them is concerned.

Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project

On 07/07/2016 01:12 PM, Davanum Srinivas wrote: Folks, The nova-docker project[1] is barely alive[2]. So i'll kick off the process of retiring the project [3] Thanks, Dims [1] http://git.openstack.org/cgit/openstack/nova-docker/ [2] http://stackalytics.com/report/contribution/nova-docker/30

[openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

Hi, We are running a public cloud and allow customers to upload their own images. A concern we have is that a customer could set hw_qemu_guest_agent=yes in the image metadata and then get a socket to the hypervisor created when running. For us, this is a bit of a security concern and I'm not

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

Also to go further into a little mini-retrospective we did during our meeting. This got released and passed through the periodic jobs we run before releasing in oslo due to primarily a timing glitch. When the patch[0] was proposed to the release repo the nova periodic jobs were fine and

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On 07/14/2016 08:07 AM, Kevin L. Mitchell wrote: The original concept of quota classes was to allow the default quotas applied to a tenant to be a function of the type of tenant. That is, say you have a tiered setup, where you have gold-, silver-, and bronze-level customers, with gold having

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

You can create a new ocata directory if one is not present On Jul 18, 2016 7:24 PM, "Adrian Turjak" wrote: > > > On 19/07/16 03:31, Steve Martinelli wrote: > > I think the change you posted could very much just > > replace the existing password plugin in keystone ( > >

Re: [openstack-dev] [Nova] About deleting keypairs

On 07/18/2016 08:14 AM, Matt Riedemann wrote: Nova doesn't actually validate the user_id passed into the keypairs API is valid, does it? Like flavor access and quotas, Nova is given an ID but doesn't validate it with Keystone. So we don't actually need Keystone to find these do we? I'm not

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

On 19/07/16 03:31, Steve Martinelli wrote: > I think the change you posted could very much just > replace the existing password plugin in keystone ( > https://review.openstack.org/#/c/343422/) and not be it's own plugin. > > How about a specification instead? >

[openstack-dev] [keystone] project mascot -- turtle!

We have decided it will be a turtle. (hard shell, security, get it!) A poll was created, anyone who had 2 or more commits in a keystone project during the Mitaka or Newton release had a vote. The options were made by active keystone developers during a meeting. Poll results are here [1], in case

Re: [openstack-dev] [Horizon] Angular action services and initScope

On 18 July 2016 at 11:49, Rob Cresswell wrote: > Maybe I'm missing the point, but the schema stuff just defines a model and > passes it to the schema directive via ctrl; doesn't that remove any issues > with workflows? ui-bootstraps modal and modalinstance already

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

On 19/07/16 01:49, David Stanek wrote: > On Mon, Jul 18, 2016 at 9:13 AM, Adrian Turjak > wrote: >> We need an MFA solution, and this doesn't seem like too terrible an option. > > > One thing to note here is that the credentials for TOTP stored in the > keystone

Re: [openstack-dev] [Horizon] Angular action services and initScope

On 18 July 2016 at 11:34, Tripp, Travis S wrote: > TL;DR, I’ll be quite happy to get rid of the need for initScope and like > exploring a common way to share model other than events. > > |From: Richard Jones > | Date: Sunday, July 17, 2016 at 6:55

Re: [openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

> I'm glad to see some interest. I've proposed a time slot for the new > meeting here: > > https://review.openstack.org/#/c/343871/ > > which is currently Thursdays, 2000 UTC. I realize the timing isn't > ideal, but given how widely distributed regular contributors are it's > not easy to pick a

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

Hi All, For Oslo libraries we ensure that API's are backward compatible for 1+ releases. When an Oslo API adds a new class attribute (as in this example of is_admin_project and 4 other attributes) added to Oslo Context in 2.6.0, these are added to ensure this API is also forward compatible with

[openstack-dev] [Infra] Meeting Tuesday July 19th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday July 19th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Mon, Jul 18, 2016 at 4:11 PM, Andreas Jaeger wrote: > You're welcome to send a patch for openstack-infra/project-config repo > and update zuul/layout.yaml to add the job to the check queue of nova. Done, thanks for pointing me in the right direction!

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Fox, Kevin M wrote: [...] I feel like I'm just the messenger here. Please don't shoot me. I'm generally trying to provide good, though hard feedback to better a perceived problem. Many others would just stay silent or leave rather then have the difficult discussion. And I think we all

[openstack-dev] [tacker] Mascot for Tacker

Tackers: Please provide your inputs to select a Mascot for Tacker in the etherpad. This is based on the recent initiative from OpenStack marketing team, see http://www.openstack.org/project-mascots for more details. There is already an exciting logo proposal in the etherpad below :)

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 7/15/2016 8:06 PM, Alex Xu wrote: Actually I still think aggregates isn't good for Manage Caps, just as I said in previous reply about Aggregates. One of reason is just same with #2 you said :) And It's totally not managable. User is even no way to query a specific host in which

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/12/2016 01:33 PM, Truman, Travis wrote: > Jean-Philippe has been providing great code reviews and patches for some > time. His recent commitment to running bug triage every week shows his > willingness to step up and take responsibilities

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

The current incarnation of the Instance User spec: https://review.openstack.org/#/c/93/ Thanks, Kevin From: Michael Still [mi...@stillhq.com] Sent: Monday, July 18, 2016 10:13 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [tc][all]

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Kfox> Responding to this inline. Sorry, its outlook. Not my choice. :/ -Original Message- From: Thomas Herve [mailto:the...@redhat.com] Sent: Saturday, July 16, 2016 1:22 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc][all] Big tent?

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 07/18/2016 10:03 PM, Diana Clarke wrote: > On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote: >> In general, I think coverage jobs should be run as check job so >> that you know how the coverage changes. Running them only in the post >> job means that in practice nobody sees

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote: > In general, I think coverage jobs should be run as check job so > that you know how the coverage changes. Running them only in the post > job means that in practice nobody sees the output of the job. I look at the post queue

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Mon, Jul 18, 2016 at 7:13 PM, Michael Still wrote: > On 16 Jul 2016 1:27 PM, "Thomas Herve" wrote: >> >> On Fri, Jul 15, 2016 at 8:36 PM, Fox, Kevin M wrote: >> > The lack of Instance Users has caused lots of projects to try and work

Re: [openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

I'm glad to see some interest. I've proposed a time slot for the new meeting here: https://review.openstack.org/#/c/343871/ which is currently Thursdays, 2000 UTC. I realize the timing isn't ideal, but given how widely distributed regular contributors are it's not easy to pick a good time. I

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

I'm arguing the opposite. It should be a requirement to use the OpenStack Secret Store. Instead, we're trying to make it optional and either reimplementing large swaths of it in individual projects to make it optional, or skip security all together. If it wasn't optional, then: * Keystone

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

I don't object to the need of an OpenStack controller and a vm need to communicate. I object to every project coming up with their own solution for that communication channel, when there really is no benefit to them being different. It is one thing amongst many that has made being an Operator's

Re: [openstack-dev] [all] Reviewing coverage jobs set up

see inline comment On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote: > While looking at coverage jobs to enable them to allow use of > constraints in post jobs (something which has just been introduced and > needs some more testing before we take on the other jobs), I

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 2016-07-18 20:09:54 +0200 (+0200), Andreas Jaeger wrote: [...] > Btw. if you want to get the output of the post job, check the git SHA. > logs are found at ``http://logs.openstack.org/ commit SHA>/``. For example, if a change is committed with > the sha 'deadbeef123456', the logs will be found

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

For those needing this release soon, watch out for the announcement. Ref: https://review.openstack.org/#/c/343708 On 7/18/16 12:19 AM, Nikhil Komawar wrote: > Thanks Matt. I've scheduled for a release of the client this week. > > On 7/16/16 4:09 AM, Matt Riedemann wrote: >> This is more of a

Re: [openstack-dev] [Horizon] Angular action services and initScope

Maybe I'm missing the point, but the schema stuff just defines a model and passes it to the schema directive via ctrl; doesn't that remove any issues with workflows? ui-bootstraps modal and modalinstance already provides a way to pass that data back to the initial location (table etc) again

Re: [openstack-dev] [Horizon] Angular action services and initScope

TL;DR, I’ll be quite happy to get rid of the need for initScope and like exploring a common way to share model other than events. |From: Richard Jones | Date: Sunday, July 17, 2016 at 6:55 PM | I think this is a bad idea because in the angular world "factory" means

[openstack-dev] [all] Reviewing coverage jobs set up

While looking at coverage jobs to enable them to allow use of constraints in post jobs (something which has just been introduced and needs some more testing before we take on the other jobs), I noticed that we have quite a few coverage jobs that are failing. In general, I think coverage jobs

[openstack-dev] [fuel documentation] new cores in fuel-docs-core

Hey everyone, We've added new cores to the Fuel documentation project: https://review.openstack.org/#/admin/groups/657,members Thew new cores are: Olena Logvinova Mariia Zlatkova Over the past ~1,5 years they've contributed a lot of quality docs pieces to various openstack projects, including

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 17:57, Thierry Carrez wrote: > Hayes, Graham wrote: >> [...] >> The point is that we were supposed to be a level field as a community >> but if we have examples like this, there is not a level playing field. > > While I generally agree on your goals here (avoid special-casing some >

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On 16 Jul 2016 1:27 PM, "Thomas Herve" wrote: > > On Fri, Jul 15, 2016 at 8:36 PM, Fox, Kevin M wrote: > > Some specific things: > > > > Magnum trying to not use Barbican as it adds an addition dependency. See the discussion on the devel mailing list for

Re: [openstack-dev] [tc][all] Plugins for all

Hayes, Graham wrote: [...] The point is that we were supposed to be a level field as a community but if we have examples like this, there is not a level playing field. While I generally agree on your goals here (avoid special-casing some projects in generic support projects like Tempest), I

[openstack-dev] [mistral] Team meeting minutes - 07/18/2016

Thanks for the great meeting today! Meeting minutes and log: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-07-18-16.02.html

Re: [openstack-dev] [TripleO] Proposing Gabriele Cerami for tripleo-quickstart core

On Mon, Jul 18, 2016 at 11:06:53AM -0400, John Trowbridge wrote: > I would like to propose Gabriele (panda on IRC), for tripleo-quickstart > core. He has worked on some pretty major features for the project > (explicit teardown, devmode), and has a good understanding of the code base. +2 from me.

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On 07/18/2016 06:28 AM, Julie Pichon wrote: > Hi, > > On Friday Dougal mentioned on IRC that he hadn't realised there was a > separate project for tripleo-common bugs on Launchpad [1] and that he'd > been using the TripleO main tracker [2] instead. > > Since the TripleO tracker is also used for

Re: [openstack-dev] [Neutron] Add an extension "btree_gist" to Postgresql

Ihar Hrachyshka wrote: > That’s an interesting precedent. I understand that since we gate on > postgresql and mysql only, the solution is good enough to pass in the gate. > But are we ok fixing a bug just for those two backends, knowing that it’s > left exposed for other backends? Could you think

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

More comments inline. On Mon, Jul 18, 2016 at 9:13 AM, Adrian Turjak wrote: > Ok. So it sounds like I'm not entirely off track and this will probably be > the road we go down for our deployment until we have a better option. We > need an MFA solution, and this doesn't

Re: [openstack-dev] [TripleO] Proposing Gabriele Cerami for tripleo-quickstart core

On Mon, Jul 18, 2016 at 11:06 AM, John Trowbridge wrote: > Howdy, > > I would like to propose Gabriele (panda on IRC), for tripleo-quickstart > core. He has worked on some pretty major features for the project > (explicit teardown, devmode), and has a good understanding of the

Re: [openstack-dev] [Nova] About deleting keypairs

On 7/14/2016 3:04 AM, Zhenyu Zheng wrote: Hi All, We have meet some problems when trying to cleanup resources, keypairs in particular. The scenario is like this, we have several projects in our public cloud, each project have their own admin, they can create and delete users, and their users

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

On 7/18/2016 9:42 AM, Matt Riedemann wrote: On 7/18/2016 9:09 AM, Markus Zoeller wrote: Since yesterday, Nova uses "oslo.context" 2.6.0 [1] but the needed change [2] is not yet in place, which broke "gate-nova-python27-db"[3]. Logstash counts 70 hits/h [4]. Most folks will be at the midcycle in

[openstack-dev] [puppet] weekly meeting #87

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160719 Feel free to add topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien Macchi

[openstack-dev] [TripleO] Proposing Gabriele Cerami for tripleo-quickstart core

Howdy, I would like to propose Gabriele (panda on IRC), for tripleo-quickstart core. He has worked on some pretty major features for the project (explicit teardown, devmode), and has a good understanding of the code base. This will bring us to three dedicated core reviewers for

Re: [openstack-dev] [docs][nova] config options help texts: reviews by technical writers?

On 18.07.2016 16:03, Matt Kassawara wrote: > I think we can help. Do you want us to submit patches for config option > descriptions that benefit from rewording? Also, you might want to post to > the -docs list. Awesome, thanks! If you could submit the changes, that would be great. Let me skim

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On 15/07/16 18:36 +, Fox, Kevin M wrote: Some specific things: Magnum trying to not use Barbican as it adds an addition dependency. See the discussion on the devel mailing list for details. Horizon discussions at the summit around wanting to use Zaqar for dynamic ui updates instead of

Re: [openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

On 7/18/2016 9:09 AM, Markus Zoeller wrote: Since yesterday, Nova uses "oslo.context" 2.6.0 [1] but the needed change [2] is not yet in place, which broke "gate-nova-python27-db"[3]. Logstash counts 70 hits/h [4]. Most folks will be at the midcycle in Portland and won't be available for the next

Re: [openstack-dev] [kolla] our mascot - input needed

On 7/18/16, 6:12 AM, "Michał Jastrzębski" wrote: >I refuse to be cut out of this thread. It is my right to freely say >what's in my mind in this, very important for our glorious project, >issue! > >So here it is: > >Koala that holds openstack square'y logo and makes docker

Re: [openstack-dev] [craton] branch clean up and other stuff

Sean, sounds good. Today, among other things, we will be discussing the branch cleanup, which should be straightforward. We look forward to discussing more about OneOps, and I will briefly mention our thoughts to date on how this could work. https://etherpad.openstack.org/p/craton-meetings for

[openstack-dev] [craton] branch clean up and other stuff

I'm going to have to miss this mornings meeting again. Here out my outstanding issues - project patch https://review.openstack.org/#/c/332470/9, is pending a request to clean up the branches in the craton repo. Once the repo is moved, branch cleanup is expensive time wise. Branches are typically

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

Hi Greg, lbaas *v1* is required for magnum mitaka. Cheers, Spyros On 18 July 2016 at 16:16, Waines, Greg wrote: > Thanks Madhuri, > > > > This blueprint is ‘Accepted for Newton’. > > So in ‘Mitaka’ and before, LBAAS is required for Magnum ? > > > > Greg. > > > >

[openstack-dev] [murano] Mascot for murano

Let’s hop on the mascot craze train and choose one for murano, shall we? For those out of loop, please see http://www.openstack.org/project-mascots =) Feel free to add suggestions, leave +1/-1 votes here https://etherpad.openstack.org/p/murano-mascot  --  Kirill Zaitsev Murano Project Tech

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

Thanks Madhuri, This blueprint is ‘Accepted for Newton’. So in ‘Mitaka’ and before, LBAAS is required for Magnum ? Greg. From: "Kumari, Madhuri" Reply-To: "openstack-dev@lists.openstack.org" Date: Monday, July 18, 2016 at 10:07 AM

[openstack-dev] [nova] gate "gate-nova-python27-db" is broken due to oslo.context 2.6.0

Since yesterday, Nova uses "oslo.context" 2.6.0 [1] but the needed change [2] is not yet in place, which broke "gate-nova-python27-db"[3]. Logstash counts 70 hits/h [4]. Most folks will be at the midcycle in Portland and won't be available for the next 2h or so. If you can have a look at it and

Re: [openstack-dev] [Magnum] Following Magnum QuickStart page, how do i use Docker CLI directly to manage containers

Hi Greg, Yes we do have document that explains the steps to configure your docker client to to be able to interact to bays. Please follow this link https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst#building-and-using-a-swarm-bay Regards, Madhuri From: Waines, Greg

Re: [openstack-dev] Naming polls - and some issues

On 07/12/2016 04:40 AM, Monty Taylor wrote: > Hey all! > > The poll emails for the P and Q naming have started to go out - and > we're experiencing some difficulties. Not sure at the moment what's > going on ... but we'll keep working on the issues and get ballots to > everyone as soon as we can.

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

Hi Greg, Now it is not mandatory to have lbaas in Magnum. Here is blueprint in Magnum that aims to decouple lbaas from Magnum https://blueprints.launchpad.net/magnum/+spec/decouple-lbaas. You can use flag –master-lb-enabled in baymodel to specify whether you want lbaas or not. However it just

Re: [openstack-dev] [docs][nova] config options help texts: reviews by technical writers?

I think we can help. Do you want us to submit patches for config option descriptions that benefit from rewording? Also, you might want to post to the -docs list. On Mon, Jul 18, 2016 at 6:29 AM, Markus Zoeller wrote: > I'd like to ask the docs team if they see the

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

On Mon, Jul 18, 2016 at 9:13 AM, Adrian Turjak wrote: > We need an MFA solution, and this doesn't seem like too terrible an option. One thing to note here is that the credentials for TOTP stored in the keystone credentials backend are not encrypted. So a breach of your

Re: [openstack-dev] [tc][all] Plugins for all

On 07/17/2016 11:04 PM, Jay Pipes wrote: On 07/14/2016 12:21 PM, Hayes, Graham wrote: A lot of the effects are hard to see, and are not insurmountable, but do cause projects to re-invent the wheel. For example, quotas - there is no way for a project that is not nova, neutron, cinder to hook

Re: [openstack-dev] [kolla] our mascot - input needed

Another idea could me Koala lie down his back and juggling with logo of OpenStack, Docker and Kubernetes. Serguei   -Original Message- From: Michał Jastrzębski [mailto:inc...@gmail.com] Sent: Monday, July 18, 2016 9:12 AM To: OpenStack Development Mailing List (not for usage

[openstack-dev] [Magnum] Following Magnum QuickStart page, how do i use Docker CLI directly to manage containers

Was trying out Magnum in Devstack, following the instructions at http://docs.openstack.org/developer/magnum/dev/dev-quickstart.html I successfully created a swarmbay. test -f ~/.ssh/id_rsa.pub || ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa nova keypair-add --pub-key ~/.ssh/id_rsa.pub testkey magnum

Re: [openstack-dev] [Keystone] Multi-factor Auth with Keystone and TOTP

Ok. So it sounds like I'm not entirely off track and this will probably be the road we go down for our deployment until we have a better option. We need an MFA solution, and this doesn't seem like too terrible an option. Basically after a bunch of digging this was the only solution I found that

Re: [openstack-dev] [kolla] our mascot - input needed

I refuse to be cut out of this thread. It is my right to freely say what's in my mind in this, very important for our glorious project, issue! So here it is: Koala that holds openstack square'y logo and makes docker whale jumps through it See? No glue or any narcotics involved. Meanwhile I'll

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke wrote: > Hi Steve, > > +1 to applying. I'll volunteer for the backport team also. > > -Paul > > > On 18/07/16 13:07, Steven Dake (stdake) wrote: >> >> Hey Koalians, >> >> I'd like us to consider applying for the stable follows

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

Hi Steve, +1 to applying. I'll volunteer for the backport team also. -Paul On 18/07/16 13:07, Steven Dake (stdake) wrote: Hey Koalians, I'd like us to consider applying for the stable follows policy tag. Full details are here:

Re: [openstack-dev] [mistal] Mistral logo ideas?

On Mon, Jul 18, 2016 at 12:44 AM, Renat Akhmerov wrote: > On choosing a mascot for Mistral. Let’s choose one till next Monday. > > To start this discussion I’d like to propose a couple of ideas: > > >- *Octopus* (kind of symbolic to me). How do you like this beauty?

Re: [openstack-dev] [tc][all] Plugins for all

On 17/07/2016 22:08, Jay Pipes wrote: > On 07/14/2016 12:21 PM, Hayes, Graham wrote: >> A lot of the effects are hard to see, and are not insurmountable, but >> do cause projects to re-invent the wheel. >> >> For example, quotas - there is no way for a project that is not nova, >> neutron, cinder

[openstack-dev] [docs][nova] config options help texts: reviews by technical writers?

I'd like to ask the docs team if they see the possibility to have reviews of the merged config options help texts Nova has updated in the last months. Background: In Mitaka and Newton, Nova put a lot of effort in providing valuable help texts for their config options. They are written from

Re: [openstack-dev] [api] testing openstackdocstheme and os-api-ref for API reference info

On 15/07/2016 22:58, Anne Gentle wrote: > Hi -dev and -doc lists, and awesome devs Karen and Graham specifically - > > I want to figure out the best way to coordinate a release of both the > theme and the sphinx extension so that we can test and publish and > iterate on the new API reference

[openstack-dev] [keystone] meeting canceled this week (7/19/2015)

Many of us are traveling that day to get to the midcycle, so cancelling the meeting this week. Enjoy your time back! stevemar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko wrote: > +1 > > > On 15.07.16 16:25, Tatyana Leontovich wrote: > > +1 > > On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova < > aurlap...@mirantis.com> wrote: > >> +1 >> >> On Fri, Jul 15,

[openstack-dev] [kolla][vote] Applying for stable-follows tag

Hey Koalians, I'd like us to consider applying for the stable follows policy tag. Full details are here: http://github.com/openstack/governance/blob/master/reference/tags/stable_follows-policy.rst Because of the magic work we did to make liberty functional, it is possible that we may not be

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

On Mon, Jul 18, 2016 at 5:19 AM, Nikhil Komawar wrote: > Thanks Matt. I've scheduled for a release of the client this week. > > On 7/16/16 4:09 AM, Matt Riedemann wrote: >> This is more of a heads up than anything. >> >> Our internal CI is running Tempest with images that

[openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

I’m relatively new to looking at Magnum. Just recently played with Magnum in devstack on Newton. I noticed that the HEAT Stack used by Magnum created Load Balancer Pool and Load Balancer HealthMonitor. QUESTION … Is LBAAS support mandatory for MAGNUM ? or can it be used (configured) without it

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 01:59, Matt Riedemann wrote: > On 7/17/2016 4:13 PM, Jay Pipes wrote: >> On 07/15/2016 08:36 AM, Hayes, Graham wrote: >>> On 14/07/2016 21:20, Matt Riedemann wrote: And does this also include plugins within projects, like storage backends in cinder and hypervisor drivers in

[openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

Hi, On Friday Dougal mentioned on IRC that he hadn't realised there was a separate project for tripleo-common bugs on Launchpad [1] and that he'd been using the TripleO main tracker [2] instead. Since the TripleO tracker is also used for client bugs (as far as I can tell?), and there doesn't

[openstack-dev] [Magnum] Discussing approaches to build `Discovery options for bay types`

Hey All, Wanted to discuss integration of locally hosted discovery mechanisms, as proposed in the following blueprint https://blueprints.launchpad.net/magnum/+spec/bay-type-discovery-options. As suggested by Hongbin, taking inspiration from the etcd approach is good

[openstack-dev] [new][oslo] futurist 0.16.0 release (newton)

We are enthusiastic to announce the release of: futurist 0.16.0: Useful additions to futures, from the future. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/futurist With package available at:

Re: [openstack-dev] [Openstack] Openstack Mitaka Neutron LBaaS Question

There are lbaas packages in Ubuntu 16.04 so you don't need to pipinstall anything. I tried to install lbaasv2 but horizon does not manage it so I finally installed lbaasv1. I use OpenVSwitch. Look for "lbaas" in this file:

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

Rodolfo wrote: Hello: I’m working in the egress minimum bandwidth assurance qos policy rule. I made a POC using the following architecture: - Every time a new rule is created and assigned to a port: o A new queue is created in OVS. o

Re: [openstack-dev] [Openstack] Naming polls - and some issues

Thank you, Joshua and Serguei! Yep. I might have missed his mentions in this thread. I am now anticipating his new e-mails for P and Q votes. With many thanks, /Ian Joshua Hesketh wrote on 7/18/2016 1:03 PM: Hello Ian, My understanding of it is that you need to receive a new link. Monty

[openstack-dev] [new][congress] python-congressclient 1.4.0 release (newton)

We are exuberant to announce the release of: python-congressclient 1.4.0: Client for Congress This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/python-congressclient Please report issues through launchpad:

  1   2   >