[openstack-announce] [release][tacker] python-tackerclient 0.3.0 release (mitaka)

We are eager to announce the release of: python-tackerclient 0.3.0: CLI and Client Library for OpenStack Tacker This release is part of the mitaka release series. With package available at: https://pypi.python.org/pypi/python-tackerclient For more details, please see below. Changes in

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

[openstack-announce] [release][solum] solum-dashboard 1.0.1 release (mitaka)

We are glad to announce the release of: solum-dashboard 1.0.1: Solum Dashboard This release is part of the mitaka release series. For more details, please see below. Changes in solum-dashboard 1.0.0..1.0.1 --- 03882e6 Cleanup Oslo Incubator Code 7c8c913

[openstack-announce] [release][solum] python-solumclient 2.0.1 release (mitaka)

We are content to announce the release of: python-solumclient 2.0.1: Client library for Solum API This release is part of the mitaka release series. For more details, please see below. Changes in python-solumclient 2.0.0..2.0.1 -- ea37d22 Remove unused

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] password in clear text

The difficulty with the environment variables is that the administrator of the box you are logged into can read the environment using ps aux. There has been some work done to support storing all the variables in a file (which would be an environment variable) such that the CLIs read from

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] password in clear text

We use Kerberos and X.509 in Keystone V3 for the end users. It works very nicely (although the python client-* CLIs often do not support it so you have to use the openstack OSC CLI) Tim From: Mike Smith > Date: Wednesday 23 March 2016 at

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

Re: [Openstack] password in clear text

Jagga Soorma wrote: >Currently when using the openstack api I have to save my password in clear >text in >the OS_PASSWORD environment variable.  Is there a more secure way to use the >openstack api without having to either store this password in clear text or >enter the >password manually every

Re: [Openstack-operators] Intel 10 GbE / bonding issue with hash policy layer3+4

Sascha, What version of the ixgbe driver are you using? Is it the same on both kernels? Have you tried the latest "out of tree driver" from E1000 to see if the issue goes away? I follow the E1000 mailing list and I seem to recall some rather recent posts regarding bonding and the ixgbe along

[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-operators] Manual router setup

Thanks. Will check that. When I create an instance in the public or private nets they ping. Why do router ports behave differently than instance ports? Only the Northbound router port is down and won't ping. Will check settings ASAP thanks Chris. Sent from my iPhone > On Mar 23, 2016,

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] password in clear text

Piggybacking on this question, I also would like to know if there is a solution to prevent storing passwords in the various service config files. We store our configs in subversion, and I hate that I have those passwords in there. Mike Smith Lead Cloud Systems Architect

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

Re: [Openstack] SSL cert issue on openstack client

Erik McCormick wrote: You may want to try updating the system CA certs. Download both the root and current intermediate certificate from Geotrust and copy them to /etc/pki/ca-trust/source/anchors/ and run update-ca-trust. I had some issues with newer GoDaddy certificates and this fixed me up.

[Openstack] password in clear text

Hi Guys, Currently when using the openstack api I have to save my password in clear text in the OS_PASSWORD environment variable. Is there a more secure way to use the openstack api without having to either store this password in clear text or enter the password manually every time I run a

[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-operators] [Contrail][DevStack] contrail-installer error

Hi Adam, Do you plan to use run your test/dev environment on Ubuntu? If yes you can have a look that project [1] which add a devstack plugin onto devstack (only supports Ubuntu for the moment). It's young but works for me. And don't hesitate to contribute. Same as contrail-installer, it starts

Re: [Openstack-operators] Manual router setup

Kevin; Thank you Very much. I'll check. I did a manual Liberty install so I may have done something wrong. I am using LinuxBridge (not OpenVSwitch) if that helps. Will post results to list soon. Would like to be able to use floating IPs, a more convenient form of ipTables basically.

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:

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

Jeremy Stanley wrote: On 2016-03-22 08:23:08 -0500 (-0500), JP Maxwell wrote: If anyone wants to approve this I am still happy to help. https://review.openstack.org/#/c/285641/1 Can you elaborate on how you intend to help which has to be done first with root access to the server (rather

Re: [Openstack-operators] Manual router setup

Do you have external_network_bridge set to an empty value in the l3 agent config? If not, the l3 agent will use a legacy mode of wiring up the port and it's status field may not be ACTIVE. The routers are tested thousands of times in the gate every day, so they work. It's just a matter of getting

[Openstack-operators] Manual router setup

Hi all; It appears that Liberty Neutron routers do not work. The Northbound port is always Down. What I'd like to do is dedicate an instance (CentOS) to routing between the Public net and other nets. Has anyone done this. Setting up the router is trivial. But I'm a little worried about

Re: [Openstack-operators] Intel 10 GbE / bonding issue with hash policy layer3+4

I'd definitely post this somewhere that Ubuntu kernel folks would read it. File a bug against that kernel. We're still on 3.13.0- stream so haven't seen this ourselves. On Wed, Mar 23, 2016 at 3:53 AM, Sascha Vogt wrote: > Hi all, > > I thought it might be of interest /

[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] SSL cert issue on openstack client

You may want to try updating the system CA certs. Download both the root and current intermediate certificate from Geotrust and copy them to /etc/pki/ca-trust/source/anchors/ and run update-ca-trust. I had some issues with newer GoDaddy certificates and this fixed me up. You'd need to do this on

[Openstack-operators] [kilo] [neutron-metadata-agent] Issue with neutron metadata-agent

Hello everybody! I'm facing a quite confusing problem with my kilo neutron-metadata-agent on network node. What's happening is that randomically, my metadata-agent stop working properly and causes instances to not be launched. The solution is to restart neutron-metadata-agent service, after a

[OpenStack-Infra] git-review 1.26 release

Hello, The last git-review release was 1.25.0 on Jun 12th 2015. Would it be possible to release a new version? I am specially interested in the opt-in "usepushurl" option so we no more need a second remote to be setup: https://review.openstack.org/#/c/109869/ My use case is that the second

[openstack-announce] [release][stable][ironic] ironic 5.1.0 release (mitaka)

We are amped to announce the release of: ironic 5.1.0: OpenStack Bare Metal Provisioning This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/ironic Please report issues through launchpad:

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-Infra] Request to enable IBM-GPFS-CINDER-CI account

Thanks Clark for clearing the confusion about accounts. We are planning to use Gerrit account with Gerrit ID of 12491 (username : ibm-gpfs-ci) Please delete the other account (Gerrit ID : 21058). The above mentioned gerrit id was created long back. Could you please make changes to the account so

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

Re: [openstack-dev] [Neutron]Debug with Pycharm

On Tue, Mar 22, 2016 at 11:36 PM, Nguyen Hoai Nam wrote: > Hi everybody, > Have you configured PyCharm to debug Neutron project. I confuged but it's > not ok. If you have any archive, could you please share it with openstacker > ?

Re: [openstack-dev] [nova] Trailing Slashes on URLs

I think it should be documented, at least so that tempest can test things that are actually known and documented behaviors Thanks, Shoham On Wed, Mar 23, 2016 at 1:07 PM, Sean Dague wrote: > On 03/22/2016 04:44 PM, Shoham Peller wrote: > > Thank you for your answer Sean. Well

Re: [Openstack] SSL cert issue on openstack client

On Tue, Mar 22, 2016 at 7:41 PM, Jagga Soorma wrote: > However my mac os x desktop does that without any issues. I was able > to get around this on my CentOS server by downloading the > GeoTrust_CA_Bundle.crt locally and using "export >

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

Mike Perez wrote: [...] A proposal I would like to make: * Clarify what cross-project specifications are [5]. - I do think specifications and best practices need to exist. + Specifications feel like they're required in my opinion. I think some cross-project things like service

Re: [openstack-dev] [Neutron]Debug with Pycharm

Hello, Nguyen! Do You want to remote debug? What actions do You want to debug? I debug openstack in PyCharm as usual python applications. On Wed, Mar 23, 2016 at 6:36 AM, Nguyen Hoai Nam wrote: > Hi everybody, > Have you configured PyCharm to debug Neutron project. I

Re: [openstack-dev] [puppet] Prefecting user and user_roles resources with domain-specific conf is failing.

Ok, so during the meeting yesterday, we have agree that prefetch should go away. I think that we have agree as well that LDAP setup for proper testing of multiple backends is required. I have started a very, very early non-working review there for the LDAP part[1]. I have chosen the camptocamp

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

Hi I wanted to start a discussion on how Fedora Atomic images are being built. Currently the process for generating the atomic images used on Magnum is described here: http://docs.openstack.org/developer/magnum/dev/build-atomic-image.html. The image needs to be built manually, uploaded to

Re: [openstack-dev] [nova] Trailing Slashes on URLs

On 03/22/2016 04:44 PM, Shoham Peller wrote: > Thank you for your answer Sean. Well understood. > However, I think that if not fix this issue, at least we should supply > guidelines on the matter. > > For example tempest's "test_delete_security_group_without_passing_id" > test actually checks

[openstack-dev] [all] Cross Project Session Day Planning

On the Tuesday (April 26th) before Project Specific Design Summit Sessions kick off, we'll again have a Cross Project Session Day. This is a time sliced out where we can tackle some of the issues that span across our OpenStack Community. We'll be doing proposals for this via etherpad, to match

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

Steven Dake (stdake) wrote: [...] Brain still booting this morning - 8am ftl. Thinking more clearly on this point, we could add a requirement that the software produce a functional out of the box working environment. This would easily apply to OSA and possibly even Puppet/Chef efforts. A stab

[openstack-dev] [TripleO] Announcing TripleO UI

Hi All, I am very pleased to inform you that, as of yesterday, TripleO UI is part of upstream OpenStack, under the TripleO program. If you'd like to learn more about TripleO UI, please read the spec [1]. The code repo [2], bug tracker [3], and review queue [4] are in usual places. TripleO UI

[Openstack] [Barbican] Mitaka RC1 available

Hi everyone, Last of the releaseteam-managed projects to issue a RC1 for the end of the Mitaka cycle is Barbican! You can find the RC1 source code tarball at: https://tarballs.openstack.org/barbican/barbican-2.0.0.0rc1.tar.gz Unless release-critical issues are found that warrant a release

[openstack-dev] [Barbican] Mitaka RC1 available

Hi everyone, Last of the releaseteam-managed projects to issue a RC1 for the end of the Mitaka cycle is Barbican! You can find the RC1 source code tarball at: https://tarballs.openstack.org/barbican/barbican-2.0.0.0rc1.tar.gz Unless release-critical issues are found that warrant a release

[openstack-dev] [Security] Newton Design Summit Etherpad

Hi Guys, Please take a few minutes to add ideas to https://etherpad.openstack.org/p/security-newton-summit-brainstorm These don’t have to be things you want to lead, just things you think would be valuable -Rob __

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

Dmitry Ilyin writes: > I've started my merging effort here > https://github.com/dmitryilyin/openstack-puppet-pacemaker Great, thanks. > > Can I change the interface of pcmk_resource? > > You have pcmk_constraint but I have pcmk_location/colocation/order > separately. I can

Re: [openstack-dev] [puppet] Prefecting user and user_roles resources with domain-specific conf is failing.

Adam Young writes: > On 03/21/2016 09:34 AM, Sofer Athlan-Guyot wrote: >> Hi, >> >> we have a big problem when using domain-specific configuration. The >> listing of all users is not supported by keystone when it's used[1][2]. >> >> What this means is that prefetch method in

Re: [Openstack-operators] [cinder] - some snapshots are there, but they are hidden in the snapshot-list

Hello, I upgraded to Kilo and I see the very same bug. What is the right way to fill a bug to Cinder, is it here ? https://bugs.launchpad.net/cinder Will it be considered if the Bug is in Kilo ? thank you Saverio 2016-03-16 13:42 GMT+01:00 Saverio Proto : > Hello there,

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

On Wed, Mar 23, 2016 at 2:33 PM, 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 wrote: >> > Let

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Thanks, Christopher (and the app-catalog team). On 21 March 2016 at 08:35, Christopher Aedo wrote: > On Sun, Mar 20, 2016 at 1:26 PM, Richard Jones > wrote: > > Unfortunately none of this discussion solves the substantive issue which > is > > that we

<    1   2