[Openstack-operators] OpenStack Developer Mailing List Digest November 7-13

Perma Link: http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151107/ New Management Tools and Processes for stable/liberty and Mitaka * For release management, we used a combination of launchpad mileston

[Openstack-operators] OpenStack Developer Mailing List Digest November 14-20

Perma Link: http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151114 Time to Make Some Assertions About Your Projects === * The technical committee defined a number of “assert” tags which allows a project team to to make

[Openstack-operators] Operators OSOps Monitoring/Tools Working Group - Meeting Notes (11/18/2015)

Meeting Notes - 11/18/2015 - 1900 UTC IRC Room: #openstack-meeting-4 Attendees: - j^2 - mdorman - klindgren - raginbajin - balajin # Pre-Agenda Topics - Group agreed to update the name of the working group to contain OSOps. - Group agreed to use the OSOps wiki page to host notes and ot

[Openstack-operators] OpenStack Weekly Community Newsletter (Nov. 14-20)

A primer on Magnum, OpenStack containers-as-a-service Adrian Otto, project team lead, on how Magnum works and what problems it can solve for you. OpenStack Mitaka release: what’s next for Ansible, Oslo

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/20/15 1:07 PM, Edgar Magana wrote: > I am confused! Are we asking for short license notice at the top of > the contributions as Tom mentioned or just this global one? The best way to describe it is this: osops-tools-contrib, defaults to Apach

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

I am confused! Are we asking for short license notice at the top of the contributions as Tom mentioned or just this global one? No preference at this moment but we should do things right from the beginning. Edgar On 11/20/15, 9:13 AM, "JJ Asghar" wrote: >-BEGIN PGP SIGNED MESSAGE-

Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly

Thanks I will remember this! Unfortunately the image is long gone but very good info to keep handy. What exactly does upstart do by the way (as I check the log on a known working image)? //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-f

Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly

Upstart is the startup system used by Ubuntu. It's been phased out "in favor" of systemd. ___ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: Adam Lawson mailto:alaw...@aqorn.com>> Date: Friday, November 20, 2015 at 11:16

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

I agree with the repo being licensed and everything in it being inherited, unless otherwise specified. Thanks for the quick movement on this, everyone! On 11/20/15 11:13 AM, JJ Asghar wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/19/15 10:40 PM, Joe Topjian wrote: Unless there

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/19/15 10:40 PM, Joe Topjian wrote: > Unless there's a reason why we *can't* do something like that (I have no > idea why, but I never assume anything when it comes to things like > licensing :) then I'm in favor of updating the README to state

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

First let me just say that I find nothing more infuriating than “software licensing.” We burn so much effort on this, when all we want to do is share the code to help others. I agree with Joe, I thought the agreement was stuff in “contrib” wouldn’t need license, specific formatting, test, et

Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly

> Yes, most likely is related to permissions. Another good source of > information for troubleshooting is /var/log/upstart/nova-compute.log > Ah yes! Much easier. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.o

[Openstack-operators] puppet-neutron Neutron::Keystone::Auth/Keystone::Resource::Service_identity Error

I'm trying to configure neutron keystone auth (with 6.1.0 branch of the puppet-keystone module) on a controller node and I receive the following error message: Error: /Stage[main]/Neutron::Keystone::Auth/Keystone::Resource::Service_identity[neutron]/Keystone_user[neutron]: Could not evalua

Re: [Openstack-operators] Migrating from nova-network to Neutron in Kilo?

Thanks Tom, this looks helpful. From: t...@openstack.org Subject: Re: [Openstack-operators] Migrating from nova-network to Neutron in Kilo? On 19/11/15 08:38, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote: > Hello operator friends, > > We're laying out our 2016 roadmaps now, and one of the projects the

Re: [Openstack-operators] openstack-ansible virt_type=lxc

Hello, On 11/18/2015 08:02 PM, Wade Holler wrote: > Just a little help needed. > on trusty > > > using openstack-ansible ( allinone ) > changed user_variables nova_virt_type to lxc > re-run os-nova-install > > Something else I need to do? > I've not played with the LXC hypervisor type in a long

Re: [Openstack-operators] [Nova] Question about starting nova as service versus directly

On Thu, 19 Nov 2015 18:37:30 -0700 Joe Topjian wrote: > Hi Adam, > > I've seen this happen due to permission issues. Regardless of running > with sudo, upstart is dropping to the "nova" user. > > I usually debug this by setting a shell on the nova user, > sudoing/su'ing to nova, then running no

Re: [Openstack-operators] Spec Review Time :)

On 20 November 2015 at 03:35, Tom Fifield wrote: > > > https://review.openstack.org/#/q/status:open+AND+project:openstack/nova-specs,n,z > > FYI, it's possible to use some regex in your query - for example this will give you all currently open specs in all specs repositories: https://review.ope