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

the v1 helion product was a joke for deployment at scale. I still don't know whose hair brained idea it was to use OOO there and then. but it was hair brained at best. From my perspective the biggest issue with helion, was insane architecture decisions like that one being made with no adherence

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

On 4 August 2016 at 12:48, Sam Morrison wrote: > >> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote: >> >> We do something similar. We give everyone in the company an account on the >> internal cloud. By default they have a user- project. We have

[Openstack-operators] [recognition] AUC Recognition Meeting on 08/04/2016

Hi everyone, The AUC recognition WG will be meeting on August 4th, 2016 at 1900 UTC. The agenda can be found on our wiki page[1]. See you there! [1] https://wiki.openstack.org/wiki/AUCRecognition#Meeting_Information -- Thanks, Shamail Tahir t: @ShamailXD tz: Eastern Time

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

Yes, at Overstock our users don't provision instances directly out of horizon or nova. They use an orchestration tool we wrote in Django which among other things tracks a lease time, warns users about expiration, allows them to extend etc. Works great for us, but the same approach may not

Re: [Openstack-operators] nova resize on shared storage

On 1 August 2016 at 14:02, Blair Bethwaite wrote: > On 1 August 2016 at 13:30, Marcus Furlong wrote: >> Looks like there is a bug open which suggests that it should be using >> RPC calls, rather than commands executed over ssh: >> >>

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

See inline. Sent from my iPad > On Aug 3, 2016, at 8:49 PM, Sam Morrison wrote: > > >> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote: >> >> We do something similar. We give everyone in the company an account on the >> internal cloud. By

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

> On 4 Aug 2016, at 3:12 AM, Kris G. Lindgren wrote: > > We do something similar. We give everyone in the company an account on the > internal cloud. By default they have a user- project. We have a > Jenkins job that adds metadata to all vm’s that are in user-

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

I hear you, Matt. TripleO is great, and v useful for what it is. But I agree that in our (been-there-done-that) experience, it was never intended to be a production-ready environment - and it isn’t. Ø I like the idea of OOO I do too - we all do! But in a production environment it’s currently

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

Hi All, As a private cloud operatior who doesn't charge internal users, I'd really like a way to force users to set an exiration time on their instances so if they forget about them they go away. I'd though Blazar was the thing to look at and Chameleoncloud.org seems to be using it (any of you

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

We do something similar. We give everyone in the company an account on the internal cloud. By default they have a user- project. We have a Jenkins job that adds metadata to all vm’s that are in user- projects. We then have additional jobs that read that metadata and determine when the VM

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

[Openstack-operators] App Catalog IRC meeting Thursday August 4th

Join us Thursday for our weekly meeting, scheduled for August 4th 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 Tomorrow we will be

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

>I like the idea of OOO but it takes time to harden that sort of deployment >scenario. And trying to build a generic tool to hit hardware in the wild is >an exercise in futility, to a point. >Crowbar actually kind of made sense in so far as it was designed > to let you write the connector

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

On Wed, Aug 03, 2016 at 05:23:23PM +, Tim Bell wrote: : :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

[Openstack-operators] HowTo upgrade in production LBaaS V1 to LBaaS V2

Hello ! LBaaS V1 is deprecated in Liberty. I am aware of this documentation: http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html We are now running a public cloud, and some users deployed LBaaS V1 (with heat templates). How do we migrate to LBaaS V2 without delete users

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

Resource reservation is one of the key requirements OPNFV is driving for Telco NFV usecases. Today it is staged within "Promise" project as a shim layer, but the intention is to get a native support through OpenStack core services like nova, neutron, cinder. Here are some urls where the

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

Hi folks, I agree. HP(E) were major contributors to TripleO in the early days, and our V1 Helion product was based on it. But, as Dan says, we wrote a new OpenStack installer from scratch for V2+. Mostly in Ansible. The sources are up on GitHub with an Apache2 license - feel free to take and

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

We discussed Blazar fairly extensively in a couple of recent scientific-wg meetings. I'm having trouble searching out right the irc log to support this but IIRC the problem with Blazar as is for the typical virtualised cloud (non-Ironic) use-case is that it uses an old/deprecated Nova API