Re: [Openstack-operators] [openstack-dev] Forum Schedule - Seeking Community Review

Jimmy, While it's not a clash within the forum, there are two sessions for Ironic scheduled at the same time on Tuesday at 14h20, each of which has Julia as a speaker. Tim -Original Message- From: Jimmy McArthur Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [Openstack-operators] [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal. To give it some context and the motivation: At CERN, we have more than 3000 users of the OpenStack cloud

Re: [Openstack-operators] [openstack-dev] [nova][publiccloud-wg] Proposal to shelve on stop/suspend

Found the previous discussion at http://lists.openstack.org/pipermail/openstack-operators/2016-August/011321.html from 2016. Tim -Original Message- From: Tim Bell Date: Saturday, 15 September 2018 at 14:38 To: "OpenStack Development Mailing List (not for usage ques

Re: [Openstack-operators] [openstack-dev] [nova][publiccloud-wg] Proposal to shelve on stop/suspend

One extra user motivation that came up during past forums was to have a different quota for shelved instances (or remove them from the project quota all together). Currently, I believe that a shelved instance still counts towards the instances/cores quota thus the reduction of usage by the user

Re: [Openstack-operators] [openstack-dev] [all] Consistent policy names

So +1 Tim From: Lance Bragstad Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, 12 September 2018 at 20:43 To: "OpenStack Development Mailing List (not for usage questions)" , OpenStack Operators Subject: [openstack-dev] [all] Consistent policy names

Re: [Openstack-operators] leaving Openstack mailing lists

Saverio, And thanks for all your hard work with the openstack community, especially the Swiss OpenStack user group (https://www.meetup.com/openstack-ch/) Hope to have a chance to work again together in the future. Tim From: Jimmy McArthur Date: Thursday, 6 September 2018 at 18:06 To: Amy Cc:

Re: [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

ch as preserving IP addresses etc. Sounds like a good topic for PTG/Forum? Tim -Original Message- From: Jay Pipes Date: Wednesday, 29 August 2018 at 22:12 To: Dan Smith , Tim Bell Cc: "openstack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] [nova][cinder]

Re: [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

I've not followed all the arguments here regarding internals but CERN's background usage of Cells v2 (and thoughts on impact of cross cell migration) is below. Some background at https://www.openstack.org/videos/vancouver-2018/moving-from-cellsv1-to-cellsv2-at-cern. Some rough parameters with t

Re: [Openstack-operators] [openstack-dev] [nova] Default scheduler filters survey

You may also need something like pre-emptible instances to arrange the clean up of opportunistic VMs when the owner needs his resources back. Some details on the early implementation at http://openstack-in-production.blogspot.fr/2018/02/maximizing-resource-utilization-with.html. If you're in Va

[Openstack-operators] 4K block size

Has anyone experience of working with local disks or volumes with physical/logical block sizes of 4K rather than 512? There seems to be KVM support for this (http://fibrevillage.com/sysadmin/216-how-to-make-qemu-kvm-accept-4k-sector-sized-disks) but I could not see how to get the appropriate f

Re: [Openstack-operators] OpenStack User Survey: Identity Service, Networking and Block Storage Drivers Answer Options

Allison, In the past, there has been some confusion on the ML2 driver since many of the drivers are both ML2 based and have specific drivers. Had you an approach in mind for this time? It does mean that the results won’t be directly comparable but cleaning up this confusion would seem worth it

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

Interesting debate, thanks for raising it. Would we still need the same style of summit forum if we have the OpenStack Community Working Gathering? One thing I have found with the forum running all week throughout the summit is that it tends to draw audience away from other talks so maybe we c

Re: [Openstack-operators] [openstack-dev] [nova] about rebuild instance booted from volume

Deleting all snapshots would seem dangerous though... 1. I want to reset my instance to how it was before 2. I'll just do a snapshot in case I need any data in the future 3. rebuild 4. oops Tim -Original Message- From: Ben Nemec Reply-To: "OpenStack Development Mailing List (not for us

Re: [Openstack-operators] How are you handling billing/chargeback?

We’re using a combination of cASO (https://caso.readthedocs.io/en/stable/) and some low level libvirt fabric monitoring. The showback accounting reports are generated with merging with other compute/storage usage across various systems (HTCondor, SLURM, ...) It would seem that those who needed

Re: [Openstack-operators] [openstack-dev] [nova] about rebuild instance booted from volume

Matt, To add another scenario and make things even more difficult (sorry (), if the original volume has snapshots, I don't think you can delete it. Tim -Original Message- From: Matt Riedemann Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday,

Re: [Openstack-operators] [Openstack-sigs] [openstack-dev] [keystone] [oslo] new unified limit library

usage questions)" , openstack-operators , "openstack-s...@lists.openstack.org" Subject: Re: [Openstack-sigs] [openstack-dev] [keystone] [oslo] new unified limit library This is certainly a feature will make Public Cloud providers very happy :) On Thu, Mar 8, 2018 at 12:33 AM, Tim

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

Labels can be one approach where you mount by disk label rather than device Creating the volume with the label # mkfs -t ext4 -L testvol /dev/vdb /etc/fstab then contains LABEL=testvol /mnt ext4 noatime,nodiratime,user_xattr0 0 You still need to be careful to not attach data disks

Re: [Openstack-operators] Custom libvirt fragment for instance type?

If you want to hide the VM signature, you can use the img_hide_hypervisor_id property (https://docs.openstack.org/python-glanceclient/latest/cli/property-keys.html) Tim -Original Message- From: jon Date: Tuesday, 16 January 2018 at 21:14 To: openstack-operators Subject: [Openstack-ope

Re: [Openstack-operators] Converting existing instances from virtio-blk to virtio-scsi

BTW, this is also an end user visible change as the VMs would see the disk move from /dev/vda to /dev/sda. Depending on how the VMs are configured, this may cause issues also for the end user. Tim From: Jean-Philippe Méthot Date: Thursday, 11 January 2018 at 08:37 To: openstack-operators Subj

Re: [Openstack-operators] CaaS with magnum

We use Magnum at CERN to provide Kubernetes, Mesos and Docker Swarm on demand. We’re running over 100 clusters currently using Atomic. More details at https://cds.cern.ch/record/2258301/files/openstack-france-magnum.pdf Tim From: Sergio Morales Acuña Date: Wednesday, 22 November 2017 at 01:01

Re: [Openstack-operators] It's time...

Tom, All the best for the future. I will happily share a beverage or two in Sydney, reflect on the early days and toast the growth of the community that you have been a major contributor to. Tim -Original Message- From: Tom Fifield Date: Wednesday, 4 October 2017 at 16:25 To: openstac

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

We use rebuild when reverting with snapshots. Keeping the same IP and hostname avoids some issues with Active Directory and Kerberos. Tim -Original Message- From: Clint Byrum Date: Tuesday, 3 October 2017 at 19:17 To: openstack-operators Subject: Re: [Openstack-operators] [nova] Should

[Openstack-operators] Pacemaker / Corosync in guests on OpenStack

Has anyone had experience setting up a cluster of VM guests running Pacemaker / Corosync? Any recommendations? Tim ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta

Re: [Openstack-operators] [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

+1 for Boris’ suggestion. Many of us use Rally to probe our clouds and have significant tooling behind it to integrate with local availability reporting and trouble ticketing systems. It would be much easier to deploy new functionality such as you propose if it was integrated into an existing pr

Re: [Openstack-operators] OpenStack User Survey Now Open

(2015.2) * … Tim From: Tim Bell Date: Thursday, 29 June 2017 at 08:40 To: Jimmy McArthur , openstack-operators Cc: Allison Price Subject: Re: [Openstack-operators] OpenStack User Survey Now Open All fixed now. My previous deployment is there too. Thanks, Tim From: Jimmy McArthur Date

Re: [Openstack-operators] OpenStack User Survey Now Open

All fixed now. My previous deployment is there too. Thanks, Tim From: Jimmy McArthur Date: Wednesday, 28 June 2017 at 23:14 To: openstack-operators Cc: Allison Price , Tim Bell Subject: Re: Fwd: [Openstack-operators] OpenStack User Survey Now Open Tim, You are correct that we have imported

Re: [Openstack-operators] OpenStack User Survey Now Open

Allison, Great to see in so many languages (although an incorrect flag seems to have been used for entering English ☺ When I get to the deployments, I’m registered with 0 currently. In the past, there was some ‘carry forward’ from previous surveys. I’m fine to put the data in again if this has

Re: [Openstack-operators] [User-committee] [scientific] IRC Meeting: Papers, Singularity, CephFS, upcoming events

I’ll try to join but just in case …. The CERN CephFS experience is at https://www.openstack.org/videos/boston-2017/manila-on-cephfs-at-cern-the-short-way-to-production. Happy with the solution as a POSIX compliant shared file system. Only slight concern is that the kernel client does not have

Re: [Openstack-operators] DB deadlocks due to connection string

One scenario would be to change the default and allow the exceptions to opt out (e.g. mysql-pymysql ( Tim On 23.05.17, 19:08, "Matt Riedemann" wrote: On 5/23/2017 11:38 AM, Sean McGinnis wrote: >> >> This sounds like something we could fix completely by dropping the >> use of t

Re: [Openstack-operators] DB deadlocks due to connection string

Would an automatic transform of mysql:// to mysql+pymysql:// be possible? Is there any reason to not have pymysql? Tim From: Arne Wiebalck Date: Tuesday, 23 May 2017 at 17:50 To: Sean McGinnis Cc: openstack-operators Subject: Re: [Openstack-operators] DB deadlocks due to connection string As

Re: [Openstack-operators] How do you determine remaining (cloud) capacity?

On 4 May 2017, at 19:26, Joshua Harlow mailto:harlo...@fastmail.com>> wrote: So just wanted to throw this email out there to explore the area a little bit (since it's an ongoing issue that keeps on getting raised at godaddy), The basic question is how as a cloud operator (or developer in a clo

Re: [Openstack-operators] looking for feedback on proposals to improve logging

There is an interesting proposal developing as part of https://review.openstack.org/460112 which it would be great to get more feedback on from other operators. My view is that OpenStack would benefit greatly from a troubleshooting guide. I remember my days with AIX (long ago) when a guide had

[Openstack-operators] [LDT] Scheduling of 'plan the week' at the summit

The Large Deployment Team meeting for ‘Plan the Week’ (https://www.openstack.org/summit/boston-2017/summit-schedule/events/18404/large-deployment-team-planning-the-week) seems to be on Wednesday at 11h00 and the Recapping the week is the next slot at 11h50 (https://www.openstack.org/summit/bos

Re: [Openstack-operators] [openstack-dev] [scientific][nova][cyborg] Special Hardware Forum session

I think there will be quite a few ops folk… I can promise at least one ☺ Blair and I can also do a little publicity in https://www.openstack.org/summit/boston-2017/summit-schedule/events/18751/future-of-hypervisor-performance-tuning-and-benchmarking which is on Tuesday. Tim From: Rochelle Grob

Re: [Openstack-operators] Boston Forum Schedule Online

:48, "Thierry Carrez" wrote: Tim Bell wrote: > Do you know if the Forum sessions will be video’d? As far as I know they won't (same as old Design/Ops summit sessions). It's difficult to produce, with people all over the room and not necess

Re: [Openstack-operators] Boston Forum Schedule Online

Tom, Do you know if the Forum sessions will be video’d? Tim On 13.04.17, 05:52, "Tom Fifield" wrote: Hello all, The schedule for our the Forum is online: https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 ==> Session moderators, please s

Re: [Openstack-operators] openstack operators meetups team meeting 2017-4-11

That looks great. Do we have dates for the Ops meetup? Tim From: Chris Morgan Date: Tuesday, 11 April 2017 at 17:53 To: openstack-operators Subject: [Openstack-operators] openstack operators meetups team meeting 2017-4-11 Today's meeting was very thinly attended (minutes and log below). I wo

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

Some combination of spot/OPIE and Blazar would seem doable as long as the resource provider reserves capacity appropriately (i.e. spot resources>>blazar committed along with no non-spot requests for the same aggregate). Is this feasible? Tim On 04.04.17, 19:21, "Jay Pipes" wrote: On 04/0

Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

The metadata settings on the images is important to inform KVM of the guest operating system. We’ve put our experiences with a recent issue at https://openstack-in-production.blogspot.ch/2017/02/ostype-property-for-windows-images-on.html Tim From: "Van Leeuwen, Robert" Date: Monday, 3 April 20

[Openstack-operators] FW: [quotas] Unified Limits Conceptual Spec RFC

For those that are interested in nested quotas, there is proposal on how to address this forming in openstack-dev (and any comments on the review should be made to https://review.openstack.org/#/c/363765). This proposal has the benefits (if I can summarise) that - Quota limits will be centrall

Re: [Openstack-operators] RFC - hierarchical quota models

> On 7 Mar 2017, at 11:52, Sean Dague wrote: > > One of the things that came out of the PTG was perhaps a new path > forward on hierarchical limits that involves storing of limits in > keystone doing counting on the projects. Members of the developer > community are working through all that righ

Re: [Openstack-operators] [User-committee] [openstack-dev] Large Contributing OpenStack Operators working group?

+1 for the WG summary and sharing priorities. Equally, exploring how we can make use of common collaboration tools for all WG would be beneficial. There is much work to do to get the needs translated to code/doc/tools and it would be a pity if we are not sharing to the full across WGs due to d

Re: [Openstack-operators] [openstack-community] User Survey - Deadline Feb 20th

I’m getting a too many redirect error on the user survey link. Tim On 01.02.17, 20:21, "Tom Fifield" wrote: Hi all, If you run OpenStack, please take a few minutes to respond to the latest User Survey or pass it along to your friends. This is the ninth survey, but if

Re: [Openstack-operators] Delegating quota management for all projects to a user without the admin role?

openstack-operators , Tim Bell Subject: Re: [Openstack-operators] Delegating quota management for all projects to a user without the admin role? I did some deep excavation and found out that Cinder is specifically the problem here. With "openstack quota show", it contacts both Nova a

Re: [Openstack-operators] Delegating quota management for all projects to a user without the admin role?

I think you could do something with policy.json to define which operations a given role would have access to. We have used this to provide the centre operator with abilities such as stop/start. The technical details are described at https://openstack-in-production.blogspot.fr/2015/02/delegation-

Re: [Openstack-operators] What would you like in Pike?

Blair, Sure. I’d also be happy for a second volunteer to share it with so that we get a rounded perspective, it is important that we don’t get too influenced by one organisation’s use cases. Tim From: Blair Bethwaite Date: Thursday, 19 January 2017 at 20:24 To: Tim Bell Cc: &q

Re: [Openstack-operators] What would you like in Pike?

woudl be very useful 3) Quota improvements -- this is important but we've learned to deal with it -Jon On Sat, Jan 14, 2017 at 10:10:40AM +, Tim Bell wrote: :There are a couple of items which have not been able to make it to the top priority for recent releases which would greatly simplif

Re: [Openstack-operators] What would you like in Pike?

> On 16 Jan 2017, at 18:00, Matt Riedemann wrote: > > On 1/14/2017 4:10 AM, Tim Bell wrote: >> >> oManual interventions are often required to sync the current usage >> with the OpenStack view > > See this spec in nova in ocata: > > https://specs.o

Re: [Openstack-operators] What would you like in Pike?

There are a couple of items which have not been able to make it to the top priority for recent releases which would greatly simplify our day to day work with the users and make the cloud more flexible. The background use cases are described in https://openstack-in-production.blogspot.fr/2016/04

Re: [Openstack-operators] Ops Meetups - paragraphs for the annual report

Can we also include a credit for the company that hosted the mid-cycle? Tim From: Lauren Sell Date: Monday, 2 January 2017 at 15:01 To: Melvin Hillsman Cc: openstack-operators Subject: Re: [Openstack-operators] Ops Meetups - paragraphs for the annual report Thanks, Melvin! I think this look

Re: [Openstack-operators] [openstack-dev] [puppet][fuel][packstack][tripleo] puppet 3 end of life

On 4 Nov 2016, at 06:31, Sam Morrison mailto:sorri...@gmail.com>> wrote: On 4 Nov. 2016, at 1:33 pm, Emilien Macchi mailto:emil...@redhat.com>> wrote: On Thu, Nov 3, 2016 at 9:10 PM, Sam Morrison mailto:sorri...@gmail.com>> wrote: Wow I didn’t realise puppet3 was being deprecated, is anyone

Re: [Openstack-operators] [nova] Does anyone use the os-diagnostics API?

> On 12 Oct 2016, at 07:00, Matt Riedemann wrote: > > The current form of the nova os-diagnostics API is hypervisor-specific, which > makes it pretty unusable in any generic way, which is why Tempest doesn't > test it. > > Way back when the v3 API was a thing for 2 minutes there was work done

Re: [Openstack-operators] Openstack team size vs's deployment size

It is a difficult calculation to make for me: - Shared services like Facilities/Hardware repair/Network… - Expectation for new functions since upstream has made them available - The user support effort has increased significantly as more users come online -

Re: [Openstack-operators] ElasticSearch on OpenStack

Thanks. How’s the storage handled ? We’re seeing slow I/O on local storage (which is also limited on space) and latencies with Ceph for block storage. Tim From: on behalf of David Medberry Date: Friday 2 September 2016 at 22:18 To: Tim Bell Cc: openstack-operators Subject: Re: [Openstack

[Openstack-operators] ElasticSearch on OpenStack

Has anyone had experience running ElasticSearch on top of OpenStack VMs ? Are there any tuning recommendations ? Thanks Tim ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [Openstack-operators] [openstack-dev] [Nova] Reconciling flavors and block device mappings

On 26 Aug 2016, at 17:44, Andrew Laski mailto:and...@lascii.com>> wrote: On Fri, Aug 26, 2016, at 11:01 AM, John Griffith wrote: On Fri, Aug 26, 2016 at 7:37 AM, Andrew Laski mailto:and...@lascii.com>> wrote: On Fri, Aug 26, 2016, at 03:44 AM,kostiantyn.volenbovs...@swisscom.com

Re: [Openstack-operators] Shelving

the user perspective, the expectation would be that the quota is available once the user request is completed (i.e. shelved). However, the resources are still being used at this point until the offload time is reached. Tim On Fri, Aug 19, 2016 at 3:50 AM, Tim Bell mailto:tim.b...@c

Re: [Openstack-operators] Shelving

e: On Thu, Aug 18, 2016 at 03:24:28PM +, Tim Bell wrote: : :We’re having a look at VM shelving for the CERN community and struggling to find a motivation for a private cloud user to shelve their instances (and free up resources they may be only using infrequently). : :The

[Openstack-operators] Shelving

We’re having a look at VM shelving for the CERN community and struggling to find a motivation for a private cloud user to shelve their instances (and free up resources they may be only using infrequently). The problem is that shelved instances seem to still be included in the user’s quota. Wit

[Openstack-operators] Tuning I/O with SSDs

Has anyone a good recipe for improving I/O performance when the hypervisor has SSDs ? The configuration is CentOS 7 for guest and hypervisor with KVM. Tim ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.opens

Re: [Openstack-operators] Blazar? (Reservations and/or scheduled termination)

When I last looked, Blazar allows you to reserve instances for a given time. An example would be - We are organizing a user training session for 100 physicists from Monday to Friday - We need that each user is able to create 2 VMs within a single shared project (as the images etc. are set up b

Re: [Openstack-operators] Who's using TripleO in production?

According to https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf, there is some usage of TripleO but it is in the other category with other deployment methods (<6% in production) on page 37. Tim On 02/08/16 18:57, "Curtis" wrote: Hi, I'm just curious who,

Re: [Openstack-operators] How do you handle purge of database tables ?

There are also some tools in the OSOps repository (Nova for example has https://github.com/openstack/osops-tools-generic/tree/master/nova) Tim From: Abel Lopez Date: Thursday 23 June 2016 at 00:03 To: Gilles Mocellin Cc: openstack-operators Subject: Re: [Openstack-operators] How do you handle

Re: [Openstack-operators] How are people dealing with API rate limiting?

On 14/06/16 18:28, "Edgar Magana" wrote: >Second that one! Feels like one of the best options, we are moving towards >that direction. > >Edgar > For completeness, Rackspace had a project called Repose which did rate limiting. Core is at https://github.com/rackerlabs/repose tim >On 6/14/16

Re: [Openstack-operators] Scaling Ceilometer compute agent?

On 14/06/16 18:00, "Matt Riedemann" wrote: >On 6/14/2016 10:14 AM, Kris G. Lindgren wrote: >> Cern is running ceilometer at scale with many thousands of compute >> nodes. I think their blog goes into some detail about it [1], but I >> don’t have a direct link to it. >> >> >> [1] - http://openst

Re: [Openstack-operators] [scientific-wg] Maximise resource utilisation (was Scientific Working Group IRC meeting, Weds @0700 UTC in #openstack-meeting)

Sorry, I got the project name wrong for cloud aware scheduler … it is Synergy (not Symphony). The description is at http://indico4.twgrid.org/indico/event/1/session/22/contribution/4.pdf, also part of the EU Indigo Datacloud project. Tim On 09/06/16 07:28, "Tim Bell" wrote: &g

Re: [Openstack-operators] [scientific-wg] Maximise resource utilisation (was Scientific Working Group IRC meeting, Weds @0700 UTC in #openstack-meeting)

Sorry I was not able to make it. To clarify on Blazar for CERN (http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-08-06.59.log.html), we’re interested in the overall problem of how to maximize the utilization of the resources in the private cloud rather than a spec

Re: [Openstack-operators] [craton] Versions of Python to support for Craton

Slight concern on how to deploy on a RHEL system base as software collections are non-trivial. If we can keep the client to be still python 2.X compatible, that would be a significant help. Getting good development productivity/deployments should probably outweigh these concerns though… Tim

Re: [Openstack-operators] Nova 2.1 and user permissions in the policy file

On 25/05/16 17:36, "Sean Dague" wrote: >On 05/23/2016 10:24 AM, Tim Bell wrote: >> >> >> Quick warning for those who are dependent on the "user_id:%(user_id)s" >> syntax for limiting actions by user. According to >> https://bu

Re: [Openstack-operators] Nova 2.1 and user permissions in the policy file

On 23/05/16 17:02, "Sean Dague" wrote: >On 05/23/2016 10:24 AM, Tim Bell wrote: >> >> >> Quick warning for those who are dependent on the "user_id:%(user_id)s" >> syntax for limiting actions by user. According to >> https://bu

[Openstack-operators] Nova 2.1 and user permissions in the policy file

Quick warning for those who are dependent on the "user_id:%(user_id)s" syntax for limiting actions by user. According to https://bugs.launchpad.net/nova/+bug/1539351, this behavior was apparently not intended according to the bug report feedback. The behavior has changed from v2 to v2.1 and t

Re: [Openstack-operators] [kolla] Moving from distro packages to containers (or virtualenvs...)

On 13/05/16 19:48, "Joshua Harlow" wrote: >Matthew Thode wrote: >> On 05/12/2016 04:04 PM, Joshua Harlow wrote: >>> Hi there all-ye-operators, >>> >>> I am investigating how to help move godaddy from rpms to a >>> container-like solution (virtualenvs, lxc, or docker...) and a set of >>> questions

Re: [Openstack-operators] [scientific] Ironic Summit recap - ops experiences

On 12/05/16 06:22, "Stig Telfer" wrote: >Hi All - > >Jim Rollenhagen from the Ironic project has just posted a great summit report >of Ironic team activities on the openstack-devs mailing list[1], which >included this item which will be of interest to the Scientific WG members who >are look

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

Does anyone see a good way to fix this to report KVM or QEMU/KVM ? I guess the worry is whether this would count as a bug fix or an incompatible change. Tim On 11/05/16 17:51, "Kashyap Chamarthy" wrote: >On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote: > >[...] > >> I'm

[Openstack-operators] [scientific][accounting] Resource management

Following the discussions last week, I have put down a blog on how CERN does it’s resource management for the accounting team on the Scientific Working group. The areas we looked at were 1. Lustre-as-a-Service in Manila 2. Bare metal management 3. Accounting 4. User Stories and Refe

Re: [Openstack-operators] Maintenance

The overall requirements are being reviewed in https://etherpad.openstack.org/p/AUS-ops-Nova-maint. A future tool may make its way in OSOps but I think we should keep the requirements discussion distinct from the available community tools and their tool repository. Tim From: Joseph Bajin mail

[Openstack-operators] [tags] Appealing for change of tags

Looking at projects like Barbican in the https://www.openstack.org/software/releases/liberty/components/barbican, they seem to have met some conditions which are currently marked as ‘no’. What is the mechanism to query these settings (either manual or automatic) ? As an example, there is signi

Re: [Openstack-operators] [nova] RFEs: communication channel and process

On 21/03/16 17:24, "Markus Zoeller" wrote: >Hello dear ops, > >I'd like to make you aware of discussion [1] on the openstack-dev ML. >I'm in the role of maintaining the bug list in Nova and was looking >for a way to gain an overview again over our ~950 open bug reports. >My idea was to redirect

Re: [Openstack-operators] RAID / stripe block storage volumes

From: joe mailto:j...@topjian.net>> Date: Monday 7 March 2016 at 07:53 To: openstack-operators mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] RAID / stripe block storage volumes We ($work) have been researching this topic for the past few weeks and I wanted t

Re: [Openstack-operators] [gnocchi][ceilometer] Taking Scientific WG Ops Meetup Feedback back to Ceilometer

On 04/03/16 16:40, "gordon chung" wrote: >> One part of the documentation set that we were missing was a guide to how to >> migrate from ceilometer to a ceilometer/gnocchi combination (which I >> understand is the ultimate architecture). We would like to migrate the >> historical data we

Re: [Openstack-operators] libvirt cpu type per instance

There is a better explanation in the OpenStack docs :-) with an example how to get 50% slower (not something my users ask for often) cpu_quota & cpu_period seems to give it according to http://docs.openstack.org/admin-guide-cloud/compute-flavors.html Tim On 04/03/16 15:59, "Jonathan Proul

Re: [Openstack-operators] [openstack-community] Recognising Ops contributions

From: Matt Joyce mailto:m...@nycresistor.com>> Date: Thursday 3 March 2016 at 18:35 To: Robert Starmer mailto:rob...@kumul.us>> Cc: openstack-operators mailto:openstack-operators@lists.openstack.org>>, "commun...@lists.openstack.org" mailto:commun...@lists

Re: [Openstack-operators] Taking Scientific WG Ops Meetup Feedback back to Ceilometer

We’re starting to have a look at gnocchi in order to address the large storage volumes. We plan on using the Ceph backend for storage. One part of the documentation set that we were missing was a guide to how to migrate from ceilometer to a ceilometer/gnocchi combination (which I understand is

Re: [Openstack-operators] [openstack-dev] OpenStack Contributor Awards

Just to check, does OpenStack run on a Raspberry Pi ? Could cause some negative comments if it was not compatible/sized for a basic configuration. Tim On 01/03/16 20:41, "Thomas Goirand" wrote: >On 03/01/2016 11:30 PM, Tom Fifield wrote: >> Excellent, excellent. >> >> What's the best pla

Re: [Openstack-operators] [nova][neutron] What are your cells networking use cases?

The CERN guys had some concerns on how dhcp was working in a segment environment. I’ll leave them to give details. Tim On 25/02/16 14:53, "Andrew Laski" wrote: > > >On Thu, Feb 25, 2016, at 05:01 AM, Tim Bell wrote: >> >> CERN info added.. Feel free to co

Re: [Openstack-operators] [nova][neutron] What are your cells networking use cases?

CERN info added.. Feel free to come back for more information if needed. Tim On 24/02/16 22:47, "Edgar Magana" wrote: >It will be awesome if we can add this doc into the networking guide :-) > > >Edgar > > > > >On 2/24/16, 1:42 PM, "Matt Riedemann" wrote: > >>The nova and neutron teams ar

Re: [Openstack-operators] kilo keystone with liberty nova

We’ve generally done staged upgrades (process documented in http://openstack-in-production.blogspot.com). For a smoother migration, we have split the changes to the service catalog to the latest API versions (e.g. Keystone V2 to V3) from the code upgrade. This allows you to have an easier rollb

Re: [Openstack-operators] Operational Director?

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: 24 November 2015 17:56 > To: openstack-operators@lists.openstack.org > Subject: Re: [Openstack-operators] Operational Director? > > Edgar Magana wrote: > > Is the Foundation aware of that? I mean you comment

Re: [Openstack-operators] Measuring how fast is my Cloud with OpenStack

How fast can be measured in a variety of ways: - How quickly a VM can be spawned and become available ? - How quickly it runs once it is available ? How many X workunits/second can be achieved with N cores ? Rally will help with the 1st case. For the second case, it is important to choose an ap

Re: [Openstack-operators] OPs Midcycle location discussion.

Multiple meetups in parallel does make it more difficult to get the PTLs and product working group involved. There have been many benefits from their work with operators and defining the roadmaps. It may be that not everyone can attend but there is also the opportunity for those who have neve

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

On 25/10/15 23:57, "Daniel P. Berrange" wrote: >On Sat, Oct 24, 2015 at 07:42:53AM +0000, Tim Bell wrote: >> Always having ephemeral disks as raw might make sense given that there >> is going to be little overlap with others (and therefore the qcow2 >> benef

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

gt;> > >> > On Thu, 2015-10-22 at 08:17 -0700, Abel Lopez wrote: >> > > I've actually looked for this for our RBD backed ephemeral instances, >> > > but found the options lacking. I last looked in Juno. >> > > >> > > On Th

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

> -Original Message- > From: Kashyap Chamarthy [mailto:kcham...@redhat.com] > Sent: 23 October 2015 12:37 > To: Tim Bell > Cc: Marc Heckmann ; openstack- > operat...@lists.openstack.org > Subject: Re: [Openstack-operators] raw ephemeral disks and qcow2 images > > On Fri,

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

On 22/10/15 20:01, "Marc Heckmann" wrote: >Hi, > >On Thu, 2015-10-22 at 08:17 -0700, Abel Lopez wrote: >> I've actually looked for this for our RBD backed ephemeral instances, >> but found the options lacking. I last looked in Juno. >> >>

[Openstack-operators] raw ephemeral disks and qcow2 images

Has anyone had experience with setting up Nova with KVM so it has raw ephemeral disks but qcow2 images for the VMs ? We've got very large ephemeral disks and could benefit from the performance of raw volumes for this. Tim smime.p7s Description: S/MIME cryptographic signature __

Re: [Openstack-operators] [openstack-dev] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: 07 October 2015 13:25 > To: Tim Bell > Cc: Sean Dague ; OpenStack Development Mailing List > (not for usage questions) ; openstack- > operat...@lists.openstack.org > Subject:

Re: [Openstack-operators] [openstack-dev] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: 07 October 2015 13:02 > To: Sean Dague > Cc: OpenStack Development Mailing List (not for usage questions) > ; openstack- > operat...@lists.openstack.org > Subject: Re: [Openstack-operators] [openstack-dev]

Re: [Openstack-operators] [ceilometer] OpenStack Telemetry user survey

> Sent: 28 September 2015 20:31 > To: Tim Bell ; openstack-operators@lists.openstack.org > Subject: Re: [Openstack-operators] [ceilometer] OpenStack Telemetry user > survey > > hi Tim, > > it's not our intention to over-survey the community -- i apologise if this is &g

Re: [Openstack-operators] Milti-site Keystone & Galera

CERN do the same…. The memcache functions on keystone are very useful for scaling it up. Tim From: Matt Fischer [mailto:m...@mattfischer.com] Sent: 28 September 2015 18:51 To: Curtis Cc: openstack-operators@lists.openstack.org; Jonathan Proulx Subject: Re: [Openstack-operators] Milti-s

Re: [Openstack-operators] [ceilometer] OpenStack Telemetry user survey

There seems to be a lot of overlap with the user survey which has just finished. Feel free to get in touch on the user-commit...@lists.openstack.org if you have questions to suggest to the survey or would like specific queries to be run on the anonymised data. There is a significant risk of ov

  1   2   >