[Openstack-operators] Duplicates and confusion in nova policy.json files

Now that policy files in nova Liberty apparently work I’m going through the stock example one and see that there are duplicate entries in the policy.json like compute:create:forced_host os_compute_api:servers:create:forced_host Which one do I use to change who can do forced_host? both or a

[Openstack-operators] [app-catalog] App Catalog IRC meeting Thursday June 16th

Join us Thursday for our weekly meeting, scheduled for June 16th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog In addition to status

Re: [Openstack-operators] NOVA build timeout: Time to fail a vm from build state

Ack. I'm picking my worst case with a 2T volume create and then doubling. On Wed, Jun 15, 2016 at 11:25 AM, Matt Riedemann wrote: > On 6/15/2016 12:09 PM, David Medberry wrote: > >> So, there is a nova.conf setting: >> >> instance_build_timeout (default to 0, never

Re: [Openstack-operators] Keystone to drop support for driver versioning…

Operators, We did not receive any feedback that dropping Keystone driver versioning would negatively impact anyone. Thus, the Keystone team met yesterday and decided to drop support for driver versioning. However, we will continue to support current legacy drivers. Moving forward though,

Re: [Openstack-operators] NOVA build timeout: Time to fail a vm from build state

On 6/15/2016 12:09 PM, David Medberry wrote: So, there is a nova.conf setting: instance_build_timeout (default to 0, never timeout) Does anyone have a "good" value they use for this? In my mind it falls very much into the specific-to-your-cloud-implementation bucket but just wondered what

[Openstack-operators] NOVA build timeout: Time to fail a vm from build state

So, there is a nova.conf setting: instance_build_timeout (default to 0, never timeout) Does anyone have a "good" value they use for this? In my mind it falls very much into the specific-to-your-cloud-implementation bucket but just wondered what folks were usign for this setting (if any). 10

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

> +1 to everything Daniel said. Nova really expects release-to-release > upgrades. We do online data migrations between releases. Maybe one > reason you're getting this to work is we have a nova-manage command to > force the migration of data between releases rather than doing the > online data

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

On 6/15/2016 10:30 AM, Daniel P. Berrange wrote: On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote: I'll offer a counter point. We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty. The database migrations to get from Kilo to Mitaka have ran

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote: > I'll offer a counter point. > > We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping > over Liberty. > > The database migrations to get from Kilo to Mitaka have ran smoothly for us. While it is great

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

I'll offer a counter point.   We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty.   The database migrations to get from Kilo to Mitaka have ran smoothly for us.   https://github.com/blueboxgroup/ursula/blob/master/upgrade.yml -jlk     - Original message

Re: [Openstack-operators] Mid-Cycle Ops Meetup venue choice - please make your voice heard!

Hi Saverio, I just checked my calendar and it seems that if a strong preference for one of the venues emerges by next Tuesday, we may be able to lock in that venue in time, since if that happens, there will be plenty of time (more than 8 weeks) after that decision for obtaining a visa. I hope

[Openstack-operators] Issue running Controllers as virtual machines on Vmware hosts

Hi all, I'm trying to virtualize some controllers on Vmware hosts, however I have an issue with networking. When tripleo enables promiscuous mode on the interfaces inside the VM operating system, I lose connectivity to the network. I already permitted promiscuous mode on vmware vswitch. Anyone

Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka

Hello, first of all I suggest you read this article: http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions > What is the best way to performe an upgrade from Juno to Mitaka? I would go for the in place upgrade, but I always upgraded without jumping

Re: [Openstack-operators] Mid-Cycle Ops Meetup venue choice - please make your voice heard!

Hello all, I will need a visa to come to the US for the Mid-Cycle Ops Meetup. The process to obtain a Visa can take up to 8 weeks, and I cannot apply until dates and venue are decided. please set a date at least 8 weeks ahead, or few people that can't make it on time to apply for visa will not

[Openstack-operators] Upgrade OpenStack Juno to Mitaka

Hi, my name is Michael, I am working at the Baden-Wuerttemberg Cooperative State University Mannheim. We have an installation of OpenStack with roundabout 14 nodes each 32 cores (1 controller (glance,keystone, etc.), 1 neutron, 2 objectstores, 1 blockstore, 9 compute nodes) the blockstore, the