Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

On Thu, Mar 24, 2016 at 6:17 AM, Doug Wiegley wrote: > Migration script has been submitted, v1 is not going anywhere from > stable/liberty or stable/mitaka, so it’s about to disappear from master. > > I’m thinking in this order: > > - remove jenkins jobs > - wait

[openstack-dev] [Glance] Block subtractive schema changes

Hi Glance Team, I have registered a blueprint [1] for blocking subtractive schema changes. Cinder and Nova are already supporting blocking of subtractive schema operations. Would like to add similar support here. Please let me know your opinion on the same. [1]

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

> On Wed, Mar 23, 2016 at 05:25:57PM +0300, Sergey Kraynev wrote: > >Hello, > >It looks similar on issue, which was discussed here [1] > >I suppose, that the root cause is incorrect using get_attr for your > >case. > >Probably you got "list"  instead of "string". > >F.e. if

Re: [openstack-dev] [Fuel][Nailgun] Random failures in unit tests

I finally got it passing all the tests, including performance: https://review.openstack.org/#/c/294976/. I'd appreciate if you guys can review/land it sooner than later: patch touches many tests, and it would be beneficial for everyone to be based on updated code. Thanks, On Mon, Mar 21, 2016 at

Re: [openstack-dev] [i18n][horizon][sahara][trove][magnum][murano] dashboard plugin release schedule

The trove-dashboard has its own stable/mitaka branch [1] as well. We have an RC1 release already and we can make sure to land the translations and cut an RC2 early next week (March 28). Thanks, Craig Vyvial [1] https://github.com/openstack/trove-dashboard/tree/stable/mitaka On Wed, Mar 23,

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

Hi Kevin, Its always nice idea as jacket has but not sure how feasible and valuable it would be. For doing API translation and gateway, there are many available and one I remember is Aviator (based on ruby gem) [1], not sure how active it is now. As your idea is more about consuming all

Re: [openstack-dev] [kolla] [vote] Managing bug backports to Mitaka branch

On Thu, Mar 24, 2016 at 12:10 AM, Steven Dake (stdake) wrote: > We had an emergency voting session on this proposal on IRC in our team > meeting today and it passed as documented in the meeting minutes[1]. I was > asked to have a typical vote and discussion on irc by one of the

Re: [openstack-dev] [i18n][horizon][sahara][trove][magnum][murano] dashboard plugin release schedule

Thank you all for your supports. We can see the progress of translations at [0] Shu, Magnum UI adopts the independent release model. Good to know you have stable/mitaka branch :) Once the stable branch is cut, let not only me but also the i18n team know it. openstack-i18n ML is the best place to

Re: [openstack-dev] [i18n][horizon][sahara][trove][magnum][murano] dashboard plugin release schedule

Hi Akihiro, Thank you for your announcement. We will create stable/mitaka branch for Magnum-UI in this week, and that will freeze strings. Thanks, Shu Muto __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 03/23/2016 03:11 PM, Fox, Kevin M wrote: If heat convergence worked (Is that a thing yet?), it could potentially be used instead of a COE like kubernetes. The thing ansible buys us today would be upgradeability. Ansible is config management, but its also a workflow like tool. Heats bad at

Re: [openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-23)

On Wed, Mar 23, 2016 at 07:52:10PM +, Amrith Kumar wrote: > The meeting bot died during the meeting and therefore the logs on eavesdrop > are useless. So I've had to get "Old-Fashioned-Logs(tm)". > > Action Items: > > #action [all] If you have a patch set that you intend to resume work >

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

On 24 March 2016 at 13:23, Dean Troyer wrote: > On Wed, Mar 23, 2016 at 3:03 PM, Doug Hellmann > wrote: >> >> Are you packaging unreleased things in RDO? Because those are the only >> things that will have similar version numbers. We ensure that whatever

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

On 24 March 2016 at 10:36, Ian Cordasco wrote: > > > The project will build wheels first. The wheels generated tend to look > something like 13.0.0.0rc2.dev10 when they're built because of pbr. > > If someone is doing CD with the openstack-ansible project and they deploy

Re: [openstack-dev] [magnum] Generate atomic images usingdiskimage-builder

1) ＋1 diskimage-builder maybe a better place to external consumption. 2) For the image size difference(big), I think we may need to know what's the issue for that. Maybe Redhat guys know something about it. Thanks Thanks Best Wishes,

Re: [openstack-dev] [release]how to release an non-official project in Mitaka

Hi, Thierry, This is quite clear, thanks a lot, would ask for more help if needed. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: Wednesday, March 23, 2016 9:04 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [all][infra] revert new gerrit

On Mar 23, 2016, at 16:56, melanie witt wrote: > I may have found a workaround for the scroll jumping after reading through > the upstream issue comments [1]: use the "Slow" setting in the preferences > for Render. Click the gear icon in the upper right corner of the diff

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

On Wed, Mar 23, 2016 at 3:03 PM, Doug Hellmann wrote: > Are you packaging unreleased things in RDO? Because those are the only > things that will have similar version numbers. We ensure that whatever > is actually tagged have good, non-overlapping, versions. > The

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

On 03/23/2016 12:49 PM, pnkk wrote: Joshua, We are performing few scaling tests for our solution and see that there are errors as below: Failed saving logbook 'cc6f5cbd-c2f7-4432-9ca6-fff185cf853b'\n InternalError: (pymysql.err.InternalError) (1205, u'Lock wait timeout exceeded; try

Re: [openstack-dev] [all][infra] revert new gerrit

On Mar 18, 2016, at 9:50, Andrew Laski wrote: > I've adapted to the new interface and really like some of the new > capabilities it provides, but having the page jump around while I'm > commenting has been a huge annoyance. I may have found a workaround for the scroll

[openstack-dev] [murano] HowTo: Compose a local bundle file

Hi wangzhh, You can use python-muranoclient in order to download bundle from apps.openstack.org and then use it somewhere else for the import: murano bundle-save app-servers you can find more about this option in corresponding spec [0]. Generally local bundle is not different from the remote

[openstack-dev] Deleting a cluster in Sahara SQL/PyMYSQL Error

Hello, When trying to delete a cluster in sahara, I'm getting the following error: > code 500 and message 'Internal Server Error' > 2016-03-23 17:25:21.651 18827 ERROR sahara.utils.api > [req-d797bbc8-7932-4187-a428-565f9d834f8b ] Traceback (most recent call last): > OperationalError:

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

Comments inline. - Douglas Mendizábal On 3/23/16 5:15 PM, Fox, Kevin M wrote: > So, this is where things start getting a little ugly and undefined... This is > what I've been able to gather so far, so please someone correct me if I'm > wrong. > > Barbican is the OpenStack secret manager. It

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 24/03/16 08:01, Doug Hellmann wrote: > Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000: >> Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I >> think it's great that you took this to the mailing list,

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 3/23/16, 2:36 PM, "Steven Hardy" wrote: >On Wed, Mar 23, 2016 at 01:01:03AM +, Fox, Kevin M wrote: >> +1 for TripleO taking a look at Kolla. >> >> Some random thoughts: >> >> I'm in the middle of deploying a new cloud and I couldn't use either >>TripleO or Kolla for

[openstack-dev] Launch of an instance from a bootable volume fails on Xen env

Launch of an instance from a bootable volume fails on Xen env. The root cause of this issue is that Nova is mapping the disk_dev /disk_bus to vda/virtio instead of xvda/xen. (Below is the session output showing the launch error) Has this been resolved? Is anyone working on this issue? Thanks,

[openstack-dev] [app-catalog] IRC Meeting Thursday March 24th at 17:00UTC

Join us Thursday for our weekly meeting, scheduled for March 24th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to get something on the agenda: https://wiki.openstack.org/wiki/Meetings/app-catalog Looking forward to seeing everyone there

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

+1. I'm going to keep my eye on the split stack stuff closely now. I think this could be very useful to our site. Thanks, Kevin From: Steven Hardy [sha...@redhat.com] Sent: Wednesday, March 23, 2016 3:00 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

So, this is where things start getting a little ugly and undefined... This is what I've been able to gather so far, so please someone correct me if I'm wrong. Barbican is the OpenStack secret manager. It provides a standard OpenStack api for users to be able store/retrieve secrets... Its

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Excerpts from Jim Rollenhagen's message of 2016-03-23 14:46:16 -0700: > On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I > > think it's great

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, Mar 23, 2016 at 10:42:17AM -0500, Michał Jastrzębski wrote: > Hello, > > So Ryan, I think you can make use of heat all the way. Architecture of > kolla doesn't require you to use ansible at all (in fact, we separate > ansible code to a different repo). Truth is that ansible-kolla is >

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000: > Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I > think it's great that you took this to the mailing list, especially seeing > the conversation that has ensued. > > More inline ... > > On 24/03/16

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

  -Original Message- From: Monty Taylor Reply: Monty Taylor Date: March 23, 2016 at 16:52:52 To: Ian Cordasco , OpenStack Development Mailing List (not for usage questions) Subject: 

[openstack-dev] [nova][novaclient] Responses for Deletion Events

There's been some discussion regarding a recent bug [1] where an issue was reported that no confirmation/success message is received from "nova agent-delete". This behavior is inconsistent from other novaclient delete commands which do provide a success message. There are a two issues that need

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

On 03/23/2016 04:45 PM, Ian Cordasco wrote: -Original Message- From: Monty Taylor Reply: OpenStack Development Mailing List (not for usage questions) Date: March 22, 2016 at 18:49:41 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Just throwing this out there: May be the sessions are open o_O? If you're using sqlalchemy to talk to the DB then may be open and close the sessions per transaction than keep them open for all threads? On 3/23/16 3:49 PM, pnkk wrote: > Joshua, > > We are performing few scaling tests for our

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

Can someone verify the code in the review is complete enough to do a full migration? Any steps missing or not documented? Is heat going to want to support v1 resources longer then neutron does? Its kind of nice to be able to run a newer dashboard/heat against an older something else. Thanks,

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I > think it's great that you took this to the mailing list, especially seeing > the conversation that

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

-Original Message- From: Monty Taylor Reply: OpenStack Development Mailing List (not for usage questions) Date: March 22, 2016 at 18:49:41 To: openstack-dev@lists.openstack.org Subject:  Re:

Re: [openstack-dev] [os-brick][nova][cinder] os-brick/privsep change is done and awaiting your review

On 3/22/2016 5:37 PM, Angus Lees wrote: On Sat, 19 Mar 2016 at 06:27 Matt Riedemann > wrote: I stared pretty hard at the nova rootwrap filter change today [1] and tried to keep that in my head along with the devstack

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, Mar 23, 2016 at 1:34 PM, Zane Bitter wrote: > On 23/03/16 07:54, Ryan Hallisey wrote: >> >> *Snip* >> >>> Indeed, this has literally none of the benefits of the ideal Heat >>> deployment enumerated above save one: it may be entirely the wrong tool >>> in every way for

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

  -Original Message- From: Doug Hellmann Reply: OpenStack Development Mailing List (not for usage questions) Date: March 23, 2016 at 15:04:15 To: openstack-dev Subject:  Re: [openstack-dev]

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, Mar 23, 2016 at 01:01:03AM +, Fox, Kevin M wrote: > +1 for TripleO taking a look at Kolla. > > Some random thoughts: > > I'm in the middle of deploying a new cloud and I couldn't use either TripleO > or Kolla for various reasons. A few reasons for each: > * TripeO - worries me for

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

Migration script has been submitted, v1 is not going anywhere from stable/liberty or stable/mitaka, so it’s about to disappear from master. I’m thinking in this order: - remove jenkins jobs - wait for heat to remove their jenkins jobs ([heat] added to this thread, so they see this coming

[openstack-dev] [nova] nova-specs review tracking etherpad

I've started an etherpad [1] similar to what we had in mitaka. There are some useful review links in the top for open reviews and fast-approve re-proposals. I'm also trying to keep a list of how many things we're re-approving since that's our backlog from mitaka (and some further back). I'd

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I think it's great that you took this to the mailing list, especially seeing the conversation that has ensued. More inline ... On 24/03/16 01:06, Mike Perez wrote: > Hey

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, Mar 23, 2016 at 03:58:02PM -0400, Ryan Hallisey wrote: > >>> Hello, > >>> > >>> So Ryan, I think you can make use of heat all the way. Architecture of > >>> kolla doesn't require you to use ansible at all (in fact, we separate > >>> ansible code to a different repo). Truth is that

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

On 23/03/16 13:35, Steven Hardy wrote: On Wed, Mar 23, 2016 at 05:25:57PM +0300, Sergey Kraynev wrote: Hello, It looks similar on issue, which was discussed here [1] I suppose, that the root cause is incorrect using get_attr for your case. Probably you got "list" instead of

[openstack-dev] Bots and Their Effects: Gerrit, IRC, other

Bots are very handy for doing repetitive tasks, we agree on that. Bots also require permissions to execute certain actions, require maintenance to ensure they operate as expected and do create output which is music to some and noise to others. Said output is often archieved somewhere which

Re: [openstack-dev] [neutron][stable] proactive backporting

On Wed, Mar 23, 2016 at 12:52 PM, Ihar Hrachyshka wrote: > Hey folks, > > some update on proactive backporting for neutron, and a call for action from > subteam leaders. > > As you probably know, lately we started to backport a lot of bug fixes in > latest stable branch

Re: [openstack-dev] [heat] Issue with validation and preview due to get_attr==None

On 23/03/16 13:14, Steven Hardy wrote: Hi all, I'm looking for some help and additional input on this bug: https://bugs.launchpad.net/heat/+bug/1559807 Hmm, I was wondering how this ever worked, but it appears you're making particularly aggressive use of the list_join and map_merge

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

+tags for stable and nova Hi Vladimir, comments inline. :) On 03/21/2016 05:16 AM, Vladimir Eremin wrote: Hey OpenStackers, I’ve recently found out, that changing of use neutron sriov-agent in Mitaka from optional to required[1] makes a kind of regression. While I understand that it is

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

Excerpts from Alan Pevec's message of 2016-03-22 20:19:44 +0100: > > The release team discussed this at the summit and agreed that it didn't > > really matter. The only folks seeing the auto-generated versions are those > > doing CD from git, and they should not be mixing different branches of a

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

Excerpts from Ian Cordasco's message of 2016-03-22 16:39:02 -0500: >   > > -Original Message- > From: Alan Pevec > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: March 22, 2016 at 14:21:47 > To: 

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

>>> Hello, >>> >>> So Ryan, I think you can make use of heat all the way. Architecture of >>> kolla doesn't require you to use ansible at all (in fact, we separate >>> ansible code to a different repo). Truth is that ansible-kolla is >>> developed by most people and considered "the way to deploy

[openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-23)

The meeting bot died during the meeting and therefore the logs on eavesdrop are useless. So I've had to get "Old-Fashioned-Logs(tm)". Action Items: #action [all] If you have a patch set that you intend to resume work on, please put an update in it to that effect so we don't go abandon it

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Joshua, We are performing few scaling tests for our solution and see that there are errors as below: Failed saving logbook 'cc6f5cbd-c2f7-4432-9ca6-fff185cf853b'\n InternalError: (pymysql.err.InternalError) (1205, u'Lock wait timeout exceeded; try restarting transaction') [SQL: u'UPDATE logbooks

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 23/03/16 15:00 -0400, Doug Hellmann wrote: Excerpts from Mike Perez's message of 2016-03-23 08:06:28 -0700: Hey all, I've been talking to a variety of projects about lack of install guides. This came from me not having a great experience with trying out projects in the big tent. Projects

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Wed, Mar 23, 2016 at 11:06 AM, Mike Perez wrote: > Hey all, > > I've been talking to a variety of projects about lack of install guides. > This > came from me not having a great experience with trying out projects in the > big > tent. > > Projects like Manila have proposed

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

Steven, Honestly I thought about it, but I am not sure, which behavior was before for both. I don't mind if we create such bug and investigate the root cause (unfortunately I had not time to do it yet). The my main point was to provide workable way for mentioned issue. p.s. there is

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

If heat convergence worked (Is that a thing yet?), it could potentially be used instead of a COE like kubernetes. The thing ansible buys us today would be upgradeability. Ansible is config management, but its also a workflow like tool. Heats bad at workflow. I think between Heat with

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Excerpts from Mike Perez's message of 2016-03-23 08:06:28 -0700: > Hey all, > > I've been talking to a variety of projects about lack of install guides. This > came from me not having a great experience with trying out projects in the big > tent. > > Projects like Manila have proposed install

Re: [openstack-dev] [release][horizon][i18n] can we release django-openstack-auth of stable/mitaka for translations

Excerpts from Akihiro Motoki's message of 2016-03-24 02:06:50 +0900: > 2016-03-22 20:08 GMT+09:00 Doug Hellmann : > > > >> On Mar 22, 2016, at 6:18 AM, Akihiro Motoki wrote: > >> > >> Hi release management team, > >> > >> Can we have a new release of

[openstack-dev] [kolla] [vote] Managing bug backports to Mitaka branch

We had an emergency voting session on this proposal on IRC in our team meeting today and it passed as documented in the meeting minutes[1]. I was asked to have a typical vote and discussion on irc by one of the participants of the vote, so please feel free to discuss and vote again. I will

Re: [openstack-dev] [heat] Issue with validation and preview due to get_attr==None

This is the same issue I ran into a few months ago regarding the nested parameter validation. Since it resolves to None at that time, there's no hook in our current nested parameters implementation to show that it will have a value passed in from the parent template. Unfortunately, I don't

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

On Wed, Mar 23, 2016 at 05:25:57PM +0300, Sergey Kraynev wrote: >Hello, >It looks similar on issue, which was discussed here [1]  >I suppose, that the root cause is incorrect using get_attr for your case. >Probably you got "list"  instead of "string". >F.e. if I do something

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 23/03/16 07:54, Ryan Hallisey wrote: *Snip* Indeed, this has literally none of the benefits of the ideal Heat deployment enumerated above save one: it may be entirely the wrong tool in every way for the job it's being asked to do, but at least it is still well-integrated with the rest of

Re: [openstack-dev] OpenStack Contributor Awards

On 3/22/2016 2:18 AM, Tom Fifield wrote: Reminder :) We'll probably stop taking entries at the end of next week. On 16/02/16 18:43, Tom Fifield wrote: Hi all, I'd like to introduce a new round of community awards handed out by the Foundation, to be presented at the feedback session of the

[openstack-dev] [heat] Issue with validation and preview due to get_attr==None

Hi all, I'm looking for some help and additional input on this bug: https://bugs.launchpad.net/heat/+bug/1559807 Basically, we have multiple issues due to the fact that we consider get_attr to resolve to None at any point before a resource is actually instantiated. It's due to this:

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Hi Yolanda, Thank you for making a huge improvement from the manual process of building the Fedora Atomic image. Although Atomic does publish a public OpenStack image that is being considered in this patch: https://review.openstack.org/#/c/276232/ in the past we have come to many situations

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Fox, Kevin M wrote: > +1 for TripleO taking a look at Kolla. > > Some random thoughts: > > I'm in the middle of deploying a new cloud and I couldn't use either TripleO > or Kolla for various reasons. A few reasons for each: > * TripeO - worries me for ever having to do a major upgrade of the

Re: [openstack-dev] [release][horizon][i18n] can we release django-openstack-auth of stable/mitaka for translations

2016-03-22 20:08 GMT+09:00 Doug Hellmann : > >> On Mar 22, 2016, at 6:18 AM, Akihiro Motoki wrote: >> >> Hi release management team, >> >> Can we have a new release of django-openstack-auth from stable/mitaka >> branch for translations? >> >> What is

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

- Original Message - > From: "Mike Perez" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, March 23, 2016 12:24:55 PM > Subject: Re: [openstack-dev] [docs] Our Install Guides Only Cover

Re: [openstack-dev] [neutron][stable] proactive backporting

Hey folks, some update on proactive backporting for neutron, and a call for action from subteam leaders. As you probably know, lately we started to backport a lot of bug fixes in latest stable branch (liberty atm) + became more systematic in getting High+ bug fixes into older stable

Re: [openstack-dev] [Fuel][Upgrade][FFE] Reassigning Nodes without Re-Installation

Hi guys, According to the last discussion on the Fuel Team Meeting [1] the second chance was provided to this feature because it is directly related to the cluster_upgrade extension and has a minimal impact on the core part. A separate bug report [2] was created to track a progress of this

Re: [openstack-dev] [Fuel] Wiping node's disks on delete

On Wed, 2016-03-23 at 18:22 +0300, Alexander Gordeev wrote: > Hello Dmitry, > > . >   > Yep, astute needs to be fixed as the way how it wipes the disks is > way too fragile, dangerous and not always reliable due to what you > mentioned above. > > Nope, I think that zeroing of 446 bytes is

Re: [openstack-dev] [infra][neutron][nova] publish and update Gerrit dashboard link automatically

On 03/22/2016 02:28 PM, Markus Zoeller wrote: >> From: Jeremy Stanley >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> Date: 02/18/2016 02:05 AM >> Subject: Re: [openstack-dev] [infra][neutron] publish and update

Re: [openstack-dev] [tricircle] Using in-memory database for unit tests

On 03/23/2016 01:33 AM, Vega Cai wrote: On 22 March 2016 at 12:09, Shinobu Kinjo > wrote: Thank you for your comment (inline for my message). On Tue, Mar 22, 2016 at 11:53 AM, Vega Cai

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Wed, Mar 23 2016, Mike Perez wrote: > As seen from the Manila review [1], the install docs team is suggesting these > to be put in their developer guide. > > I don't think this is a great idea. Mainly because they are for developers, > operators aren't going to be looking in there for install

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 12:05 Mar 23, Steve Gordon wrote: > Did you look at the link I provided above?: > > http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/manila.rst > > This content is merged. Thanks Steve. So is this no longer a requirement that a project has to be

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 23/03/2016 16:12, Steve Gordon wrote: > - Original Message - >> From: "Steve Gordon" >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> >> - Original Message - >>> From: "Graham Hayes"

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

- Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage questions)" > > > - Original Message - > > From: "Steve Gordon" > > To: "OpenStack Development

Re: [openstack-dev] [cross-project] What are specifications?

On 12:12 Mar 23, Thierry Carrez wrote: > Keeping both using the same template, in the same directories and the same > repositories is what created this grey area that paved the way for specs > without assignees and best practices asking for cross-project consensus that > they will never fully

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

- Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage questions)" > > > - Original Message - > > From: "Graham Hayes" ha...@hpe.com> > > To: "OpenStack Development Mailing List

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

- Original Message - > From: "Graham Hayes" > To: "OpenStack Development Mailing List (not for usage questions)" > > > On 23/03/2016 15:37, Steve Gordon wrote: > > - Original Message - > >> From: "Mike Perez"

[openstack-dev] [Horizon] Bug day

Bug day returns! Everyone welcome! We've had some success but still a long way to go. The next bug day will be on the 5th of April. The focus of the bug days is to triage our existing bugs, not to fix specific bugs or find new ones (for now). In the future, as the list progresses to an

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 23/03/2016 15:37, Steve Gordon wrote: > - Original Message - >> From: "Mike Perez" >> To: "OpenStack Development Mailing List" >> >> Hey all, >> >> I've been talking to a variety of projects about lack of install guides. This >>

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 11:34 Mar 23, Steve Gordon wrote: > Are there examples of projects that have this user orientated install > documentation written but are actively being rejected from including it in > the install guide (in the Magnum case it has been pushed out to Newton as it > was a late submission, not

[openstack-dev] [Horizon] Horizon Drivers meeting

Hi folks, With master now open for Newton development, I'm going to reopen the Horizon Drivers meeting. See https://wiki.openstack.org/wiki/Meetings/HorizonDrivers I intend to run the meeting both weeks for now (previously we had only held it every other week). The next meeting will be at

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 03/23/2016 11:42 AM, Michał Jastrzębski wrote: Hello, So Ryan, I think you can make use of heat all the way. Architecture of kolla doesn't require you to use ansible at all (in fact, we separate ansible code to a different repo). Truth is that ansible-kolla is developed by most people and

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Hello, So Ryan, I think you can make use of heat all the way. Architecture of kolla doesn't require you to use ansible at all (in fact, we separate ansible code to a different repo). Truth is that ansible-kolla is developed by most people and considered "the way to deploy kolla" by most of us,

[openstack-dev] [ironic] Keeping up with RFEs

Hey all, I just burned through every RFE we have filed. I've approved the ones that are trivial or have a spec approved already (by changing the tag to rfe-approved), asked for a spec on many others, and left the ones with an unmerged spec alone. Going forward, I plan to take a look at incoming

Re: [openstack-dev] [kloudbuster] authorization failed problem

Hi Akshay The URL you are using is a private address (http://192.168.138.51:5000/v2.0) and is likely the reason it does not work. If you run the kloudbuster App in the cloud, this app needs to have access to the cloud under test. So even if you can access 192.168.138.51 from your local browser

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

- Original Message - > From: "Mike Perez" > To: "OpenStack Development Mailing List" > > Hey all, > > I've been talking to a variety of projects about lack of install guides. This > came from me not having a great experience with

Re: [openstack-dev] [Fuel] Wiping node's disks on delete

Hello Dmitry, First of all, thanks for recovering the thread. Please read my comments inline. On Tue, Mar 22, 2016 at 1:07 PM, Dmitry Guryanov wrote: > > The first problem could be solved with zeroing first 512 bytes of each > disk (not partition). Even 446 to be

[openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Hey all, I've been talking to a variety of projects about lack of install guides. This came from me not having a great experience with trying out projects in the big tent. Projects like Manila have proposed install docs [1], but they were rejected by the install docs team because it's not in

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

Hello, It looks similar on issue, which was discussed here [1] I suppose, that the root cause is incorrect using get_attr for your case. Probably you got "list" instead of "string". F.e. if I do something similar: outputs: rg_1: value: {get_attr: [rg_a, rg_a_public_ip]} rg_2:

[openstack-dev] [kloudbuster] authorization failed problem

Hi, I am trying to use cloudbuster for the scale testing of openstack setup. I have a openstack setup with 1 controller, 1 network and 2 compute node. I am trying to use to use kloudbuster for scale testing of the setup. I created one VM with kloudbuster image. I accessed the web UI and clicked

Re: [openstack-dev] [release]how to release an non-official project in Mitaka

joehuang wrote: Thanks for the help. There is a plan for not only Tricircle but also Kingbird to do a release in Mitaka, both of them are not OpenStack official project yet. The question is whether these projects can leverage the facility https://github.com/openstack/releases to do a release, or

[openstack-dev] [Fuel] API changes for Nailgun cluster upgrade extension

Hi, fuelers! In accordance to policy of API changing in Fuel components established in this mail thread [1] the purpose of this notice is to inform everyone concerned about such modifications pertaining to Nailgun cluster upgrade extension that is going to be landed into upstream. New handler of

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

*Snip* > Indeed, this has literally none of the benefits of the ideal Heat > deployment enumerated above save one: it may be entirely the wrong tool > in every way for the job it's being asked to do, but at least it is > still well-integrated with the rest of the infrastructure. > Now, at the

  1   2   >